r/hotas•
jayeffaar

Brand new X-55 stick lost x and y axes after calibration.

Help

I was trying out the Saitek H.U.D. software after installing the drivers and software of my completely new X-55, and at that point, all 3 stick axes were registering fine. I hit the "Calibrate Axes" button in H.U.D.'s Settings menu, the UI went through a few normal-looking progress bars and... poof, no more X and Y axes on the stick.

Since then, I've tried every combiniation I can think of of re-calibrating, uninstalling/reinstalling drivers and software, trying the stick on another computer without any of the Saitek software, and then installing it there too... to no avail, the stick just doesn't register any movement on the X and Y axes anymore. As far as the Windows USB controllers app is concerned, both sticks are stuck at the max 16-bit value and do not budge.

The rotation axis and all buttons are fine, but main axes were calibrated out of existence (and in the stick itself, not on some calibration file stored locally on the first computers where it happened).

I never even got to use it in a game.

This has to be due to some garbage calibration info that got uploaded to the stick. Is there a known way to reset the stick to factory settings?

Posted Feb 4, 2016, 2:43 PM UTC · edited

63
TravisPM•

The stick doesn't have any memory or calibration info stored on it. If it doesn't work with a fresh driver install on another computer it's likely a hardware issue. Just return it for a new one.

1
ApolloFett•

Really weird! I've owned the x55 for almost 2 years and never had that happen. I would try different usb ports and definitely try it on another computer if you are able to. Fortunately since it's brand new you shouldn't have any trouble returning it as defective if you can't sort it out.

If you go into windows devices and printers and right click on the stick there and select remove device and then reinstall the drivers. If you just uninstalled the HUD software from remove and uninstall in Windows that won't remove the drivers.

1
waflhead•

I had a similar problem and was able to fix it by uninstalling the drivers and then uninstalling everything under Programming Support in Device Manager, then reinstall the drivers. The tests still didn't work perfectly in device properties, but it works perfectly in game.

1