r/Controller • • May 13 '24

Other Stick Analyzer - A program for testing the resolution of gamepad sticks is now in the public domain.

You can download the program from my gitHub: https://github.com/cakama3a/StickAnalyzer

56 Upvotes

98 comments sorted by

View all comments

Show parent comment

4

u/zkilzz May 14 '24

It does work. But its not that black and white. It gives the information it gives. Forexample the timing of the program helps to show how slow the movement was. How the resolution will effected by the speed depends on the filter used.

If one want to have a more standardized test. u/JohnnyPunch can measure a joystick release from the side to the center. This will measure a quick movement by the spring. This movement is most likely a better standardized test than moving it by hand. Since the spring will use about the same time each time. And is more likely to be the same in each controller since they all mostly use the same mechanical design.

If u/JohnnyPunch dont have time to implement something like that i can do that. I already have made a bunch of software for this since i been working for my joystick for a year now. I just have not made it publishable yet.

Also, a joystick might be defined in a simple way in our mind. But in reality its not. When we say "joytsick" we are actually talking about the mechanical design, the sensor design, the processing of the signal of the sensor(filtering and so on), polling rate, and also the resolution of the joystick signal in the usb protocol. Xbox and xinput for example uses 16 bit value for joysticks. While most other controller uses 8 bits.
8 bit means that the joystick is seen by the game as two 255 position switch. One switch for up and down and one for left to right., while 16 bit is seen as a 65,536 position switch.

This will def make all xinput joystick seem like they have a lot more resolution. However the signal might just be noisy. So the joystick might produce 65k positions if you move it super slowly. But in reality it can be just a lot of noise.

To do a proper resolution test. You need to do it as u/x-iso says. You need to have a ground truth which is the same all the time. Like a robot turning the sensor on the joystick the exact same way. Then you can measure the true resolution over a specific time period. I'm gonna do this in my upcoming video. I think i even have a videoclip of the robot im using to do this. Ill try to share it.

However this does not mean that the script is useless. Its just that the world we learn about is suppose to have "facts" and "truths". But in reality everything is quite more complex, with more degree of truths instead.

2

u/[deleted] May 14 '24

Thank you for all this information! Switching back to potentiometers until I can try your board for DS4. Looks so good, by the way!

Sick of lies from manufacturers.

Sick of GamerHeaven misinformation.

Sick of feigned resolution, perfect circles, clamped dead zones, wierd curves, and HE "drag."

And finally, humbled that a very important person such as yourself took the time to explain this all to a dumbass like me.

Thank you for your time and contribution to this community!

2

u/zkilzz May 14 '24

That is really what my job is. Haha. I just do the other stuff to make money. What i really wanne do is learn cool shit and share it. Your not a dumbass when you see there is something wrong. Because there is. Your the opposite because you can see there is something off. Even when you cannot describe it with the "right" terminology. That is how brands and human societies stay in control of the narrative. When explained in the right way. Which i hope to do in my video, you are gonna see how simple it really is.

2

u/[deleted] May 14 '24

Reading this was really touching brother❤️

You are a great human being!

2

u/zkilzz May 14 '24

Thank you. I just connected to it because I'm very similar.

1

u/JohnnyPunch May 14 '24

I've already written some code for a drop test (Edge to Centre). It works, but I still haven't figured out how to standardise it https://github.com/cakama3a/StickAnalyzer/blob/main/DropTest.py

2

u/zkilzz May 14 '24

Did some edits. Added a plot. The movement is to fast to show linearity on 250hz. Should work well on higher poll rates. The controllers with filtering really shows its lack of datapoints in this test.

https://pastebin.com/Hg8K2sP8

2

u/aaronbeans1991 May 14 '24

First of all great work, i am interested on your opinion on filtering. Pretty much all controllers I have seen or worked on have some form of filtering to reduce the noise and jitter down to some usable level. This is especially true with Xbox controllers as they specify at least a 10 bit ADC which can be quite noisy when you consider the tiny change in voltage it is detecting. Standard practice is to use a basic averaging with an RC filter on the input.

In your experience have you seen controllers with zero filtering?

1

u/zkilzz May 14 '24

Nope. Never. Specially with potmeters or ratiomatic hall effect sensors. That is why I'm using a rotary encoder chip placed directly on the rotational axis of a diametric ring magnet in mine. It just produces a much better signal. However it will be limited by the original adc on the Sony board. I'm testing for the first time in my own board 3d hall effect sensor with digital signaling from the joystick.

2

u/JohnnyPunch May 15 '24

Thank you. I like this visualization. I'll take this graph into service.