Gladiator Mk 2 PRO X-Axis doesn't work after cam change

[WheelwrightPL]

Hello
Yesterday my X-Axis cam spring broke so I replaced it. However after doing that I noticed that my X-Axis stopped working (it was only going to extreme left or right). So I went to Wizzo and re-calibrated the joystick, but now my maximum-left gives me almost 100% right and my maximum-right gives me 50% left.

[fallout9]

Hi there,

First please re-flash and re-calibrate to the latest software and firmware using this guide: https://youtu.be/8Ht8yMsdlCQ

[WheelwrightPL]

Sorry, I am afraid I will lose all my changes (I worked so hard to program) after firmware update and re-flashing.
This looks 100% like a hardware failure because my X-axis suddenly got reversed after I put a new spring on its corresponding cam.
I also had Y-axis spring break a couple months ago and had no problems on the Y-axis after the spring replacement.

[fallout9]

You could save all the changes you've made by saving your profile and loading that profile after you flashed and calibrated (do not load the previous calibration though).
Could you post VKBDevCfg screenshots with the Profile/ Axes/ Physical Axes panels visible?

[WheelwrightPL]

Thanks for your help so far.
In the "Physical Axes" view I unchecked R (under tooltip "Physical data inversion"), saved it (by clicking "Set"), and that fixed the X-Axis inversion problem. That's puzzling because I didn't check R myself, how did it happen ?
The only remaining problem is inability to go all the way to the right on the X-Axis (it doesn't want to go beyond 70-80%).
Same with the VKB Rudders which now don't want to go to the left beyond about 90%.

[fallout9]

It would be way easier to find out what happens in there by seeing the mentioned screenshots.

[WheelwrightPL]

I attach the image as per your request.

[fallout9]

From this point click on the Tools tab, then on the big Start Calibr button. Move the joystick on all axes end-to-end; don’t forget twist and throttle. When done press the End Calibr button.
This above is only calibrating the axes, as yours seem totally uncalibrated; you won’t be losing any changes you’ve made to the joystick by doing this. I recommend though saving your profile and reflashing to the latest firmware, as per the guide I’ve linked. Reflashing is only optional, calibration is a must.

[WheelwrightPL]

Calibration is the first thing I did after the cam change. The above screenshot is after the calibrations (which I did multiple times).

[fallout9]

There's something missing in your calibration process. Here's the step-by-step calibration procedure:
1. Open VKBDevCfg;
2. Click on the Test tab, then click on the Axes tab;
3. Click on the Tools tab;
4. Click on the big square Start Calibr button;
5. Move your joystick along X and Y axes, twist it, roll the throttle;
6. When done, press on the End Calibr button.

If you follow exactly these steps your joystick gets properly calibrated.If you still have problems afterwards reset the device to default - I see you made changes to the Threshold and maybe others that you forgot about them.

[WheelwrightPL]

First of all: thanks for your continuing support, but I know how to calibrate, so that's not the root cause.
Also: until now I didn't intentionally change anything for the axes or the rudder, so I assume it must have used default settings.
But today I started trying to figure this out: I increased "Multiplier" for this wonky X-Axis (it had jitter from the start) and slightly decreased "Bias zero point" for the rudder so it centres better (it shifted the center to the left).
Seems like this fixed my problems, albeit at some accuracy cost. Will see how it works in IL2-Sturmovik game tomorrow.

[fallout9]

No problem at all. I will just leave this here as a future reference, in case other users will bump into this thread for similar issues:
- try to keep up with the latest software and firmware posted in the Downloads section of vkbcontrollers.com;
- ALWAYS recalibrate your joystick after changing cams and springs. After recalibrating test your axes; if they have same values as the X axis in the image above (KdHi and KdLo 255) that means the axis is not calibrated and need to run the process again;
- do not modify values in the configurator before reading the manual about the effects of changing the values;
- if you've made any changes and want to revert to original state, press the Default button and recalibrate afterwards.