Gladiator NXT EVO L & R + SEM = No sliders/throttle wheel at Joysticks [Solved]

[Native]

And still you don't have a helping answer for me.
Slider, Throttle wheel, Axis... there is only one part at the joystick what can do this. So yeah, I am talking about this one thing.
If you don't have a helping answer for me, then don't reply please.

[Ron61]

In the configurator, open the Settings tab and activate the Partial Calibration checkbox. Run the calibration process and select only the 4th axis (analog throttle axis based on GNX Evo), show a screenshot of the Profile-Axes tab after calibration.

[Native]

okay, here is it

Partial Calibration: check.


calibration of the 4th axis only: check


Screenshot of the Profile-Axes tab: check

[Ron61]

Try changing the MPL value from 8 to 9, save it to the controller (by pressing Set) and calibrate this axis again. Repeat screenshot.

[Native]

All done and here the Screenshot:

But it still doesn't work.

[Ron61]

There is one peculiarity in your screenshots - the value KdHi=255 and does not change in any way when changing MPL. What is not good should not be so.
You can try checking the ACn checkbox, but then before calibration you will need to move the lever to the center (approximately) and calibrate.
Does this axis also not work correctly on the left base?

[Native]

I have tried it with ACn checkbox too now.
checked it, pressed Set, calibration. But there is no movement in the test. the point is now only close to the middle, but I can't move it.


And yes, I have got the same problem with the left joystick. I am not sure, but maybe it is because of the new firmware? It worked without any problems before i made had installed the SEM Modul and the new firmware.
Here is a screenshot from my left joystick.

[Ron61]

Please show only requested tabs. You can't determine anything from the Test tab.
The fact that the axis on the second base also stopped working may indicate other causes of the problem. Try cleaning the registry with USBDeview by uninstalling both databases and then reconnecting them to USB.
Try working with only one base, temporarily disabling the other.

[Native]

right now I have installed an older Firmware on the left stick and... now the throttle works without any problems. All axis are working now



So is the firmware broken or what is there wrong?

[Ron61]

How much can you write about the correspondence between the configurator version and the firmware?
Once again - in the configurator header (topmost line), in brackets, the recommended (minimum) firmware is indicated. Higher is possible, lower is not. Follow this simple rule.
You always have a choice - to stay on older, more stable firmware (and configurators), or to become a tester of the unknown with all the ensuing consequences. There can be thousands (if not hundreds of thousands) of user system configurations and it is not realistic to provide for all possible options.
And only God knows what is being done in the registry.

[Native]

You can see the used Firmware in the Screenshot before. That's all i can say to it.
but that's the problem: I was already happy to still have this old firmware. I wanted to use the latest one because of all the fixes and so on.
So the best way would be to have a list of all versions, so I can choose the last working version.

Is there a download directory somewhere with all firmware versions? Or something like a changelog page including the firmware version for download? So I can downgrade to the latest working firmware. I have found only the download section with the latest version, but this is broken for me.

Where can I report this error now so that VKB also sees it and checks it once in their current firmware and brings maybe a newer fixed version?

Oh, by the way...

You always have a choice - to stay on older, more stable firmware (and configurators), or to become a tester of the unknown with all the ensuing consequences.

I have only the choice, when there is a list of all firmware versions or maybe the latest 10 firmware versions. But there is only the latest version in the download section. So no, I don't really have a choice and the bad side, I don't have the old VKBDevCfg-C app anymore. Only the old firmware. So they are not compatible anymore.

[Ron61]

Look here, there is an archive folder.
And if there is no longer access to certain versions, then critical bugs were found in them, incompatible even for a beta test.

[Native]

Look here, there is an archive folder.
And if there is no longer access to certain versions, then critical bugs were found in them, incompatible even for a beta test.

thank you, so I could try them out and i am very confused now.
I have tried all of the firmware here in this screenshot:

But only my old v2_12_2 is working.
For just a very short moment the v2_16_8 worked too, but then I got a error from the VKBDevCfg-C_v0.92.88 after pressing on End Calibration and then none of the firmwares worked. Only my old one works fully.
I am very confused now. It seems like only my old firmware works, but it is not possible that all the other firmwares are broken. So other people would address the same problem here.

So I think it is not the firmware, it must be something different, but what?!

[fallout9]

Did you clicked the Default button after reflashing, followed by clicking Yes for the configure popup?

[Native]

I have tried now the one earlier version of the Device config App and after flashing my jostick with the newest firmware i got this Error