Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: Serenity on August 17, 2016, 04:45:33 PM
-
I'm beside myself at this point. This is just stupid. I'm having issues with my Saitek X-55 stick. It spikes like CRAZY, but not on the axis controls, but rather buttons and switches. Random switches CONSTANTLY fire off, for no apparent reason. I had this issue when I first got the stick, running windows 8. I complained to Saitek, they sent me a new stick and throttle, but the problem remained. Then, out of nowhere, the problem just went away one day. Then I got windows 10, and it still wasn't a problem, until suddenly it is again, for no apparent reason...
Stick: Saitek X-55 Stick and Throttle, connected to USB 3.0 ports (The blue ones are 3.0, right?)
OS: Windows 10.
I've tried connecting to a powered USB hub, with no change in issue. I also don't get ANY spiking of any kind on the axis controls. It's ONLY buttons/switches.
-
Sounds like a bad wire. Does it only happen when moving the stick?
-
Done any updates recently?
-
Check your controller mapping. It's possible that the game has somehow mapped some functions to your mouse, for example.
-
Sounds like a bad wire. Does it only happen when moving the stick?
No, it happens even when nothing is moving at all. And it happens with both of the X-55 throttles. (Meaning two separate units, the original, and the replacement they sent)
Done any updates recently?
More than I can count, I took a good couple of months off of flight sims, so it's hard to pinpoint when the problem started again.
Check your controller mapping. It's possible that the game has somehow mapped some functions to your mouse, for example.
I'll check, but again, it's not axis commands, it's buttons that spike, and far more button functions than I have mouse buttons lol.
-
Check your controller mapping. It's possible that the game has somehow mapped some functions to your mouse, for example.
Nope, not it.
-
Nope, not it.
It would have been too easy anyway...
-
Tried this driver? ftp://ftp.saitek.com/pub/software/beta/Windows10/
-
Some have been able to fix this issue with keeping the Saitek software open when playing.
-
Can you borrow a powered USB hub, plug it into a different USB plug on your computer than you are using for your gear, and try plugging joystick and throttle into that to see if it goes away?
I have had bizarre problems with USB ports on computers in the past when not using powered hubs (both with joysticks and other devices).
-
Yes powered hub :old:
-
Some have been able to fix this issue with keeping the Saitek software open when playing.
this an a powered usb. when I had the x52 I always had to have the software open.
semp
-
I had the same thing with my Saitek x55. I deleted the Saitekx55.jsm file in Aces high settings folder and it fixed it. You will have to reconfigure your buttons in Aces High after doing this for your stick because it will wipe out your settings but it may fix it.
-
Can you borrow a powered USB hub, plug it into a different USB plug on your computer than you are using for your gear, and try plugging joystick and throttle into that to see if it goes away?
I have had bizarre problems with USB ports on computers in the past when not using powered hubs (both with joysticks and other devices).
I've got two different powered hubs I've tried with no luck.
Tried this driver? ftp://ftp.saitek.com/pub/software/beta/Windows10/
A beta driver? I'll try that next.
Some have been able to fix this issue with keeping the Saitek software open when playing.
This will be the next attempt.
I had the same thing with my Saitek x55. I deleted the Saitekx55.jsm file in Aces high settings folder and it fixed it. You will have to reconfigure your buttons in Aces High after doing this for your stick because it will wipe out your settings but it may fix it.
Then this one. I hope it's not this one, because this problem exists in DCS as well as AH, and... well... if they even HAVE a file like that, remapping everything will be a nightmare lol.
-
Have you run the joystick with button test in W10?
-
Have you run the joystick with button test in W10?
I've never heard of such a thing...
-
I've never heard of such a thing...
Click on setting then devices then right click on the joystick. There under properties i think, you will find testing. You should be able to test every button.
-
Have you got an answer?
I would ask this, You said that the unit engages a button or buttons, could you be more specific?
Is it strictly the same button every time or is it multiple, and if multiple is it always the same ones?
Is it a selection point on a high hat switch?
I would go into windows controller game settings and just let it sit, does an input register, all items will blink when engaged, yes?
Does same issue occur with device drivers installed/uninstalled? only in game or all times?
Does disabling any game selection to said button end issue?
That's a HOSTAS, unplug the throttle unit from stick unit, same issue?
Basically see if you can discover which component is errant, isolate, then disable or fix. If you have no basic skills and knowledge in electronics, meter and soldering iron, you will prolly just disable and not use.
luck
-
You can check your stick buttons in The Saitek 'Rhino" Program. Once you launch the Rhino program 'select Programming' and 'select the Stick' and press each button. Example: Press the Trigger button and let go you should see it highlight then dim. Press it again and hold it should be constant until you let go, if its a bad button/connection it should register by flickering. Go through each button and check this should let you know if its your stick or throttle that is bad. Hope this helps.
-
Click on setting then devices then right click on the joystick. There under properties i think, you will find testing. You should be able to test every button.
So this doesn't seem to be available in Win 10, but I tested it using the Saitek software. As I move the throttle, EVERY SINGLE BUTTON ripple fires off in the throttle quadrant... Literally every one of them. Not all at once, they ripple around.
Have you got an answer?
I would ask this, You said that the unit engages a button or buttons, could you be more specific?
Is it strictly the same button every time or is it multiple, and if multiple is it always the same ones?
Is it a selection point on a high hat switch?
I would go into windows controller game settings and just let it sit, does an input register, all items will blink when engaged, yes?
Does same issue occur with device drivers installed/uninstalled? only in game or all times?
Does disabling any game selection to said button end issue?
That's a HOSTAS, unplug the throttle unit from stick unit, same issue?
Basically see if you can discover which component is errant, isolate, then disable or fix. If you have no basic skills and knowledge in electronics, meter and soldering iron, you will prolly just disable and not use.
luck
So, it happens with and without drivers. It's replicable in the saitek software. And it's every single button and switch on the throttle quadrant, all of them ripple firing off while the throttle is moving. When the throttle doesn't move, they're fine, but as soon as it's even tapped, SOMETHING random fires off.
-
Sounds like a shortcut, a wire grounding in a wrong place inside the throttle.
-
Sounds like a shortcut, a wire grounding in a wrong place inside the throttle.
Is that likely in two separate throttle units? (I have to complete X-55 setups with identical issues)
-
Sorry, I forgot you had two of them. If one is brand new, it would be highly unlikely. However, if both have been used it might be a "feature".
I just re-read your original post where you said Saitek sent you a new stick, so we're in the highly unlikely sector concerning shortcut wires.
What caught my eye is that you're using USB3 ports for your gear. That might be the culprit. Although they should be backwards compatible, they aren't. For example plugging an older printer into USB3 often gives a warning about incompatibility.
-
Sorry, I forgot you had two of them. If one is brand new, it would be highly unlikely. However, if both have been used it might be a "feature".
I just re-read your original post where you said Saitek sent you a new stick, so we're in the highly unlikely sector concerning shortcut wires.
What caught my eye is that you're using USB3 ports for your gear. That might be the culprit. Although they should be backwards compatible, they aren't. For example plugging an older printer into USB3 often gives a warning about incompatibility.
I've got 4 3.0 ports and 6 2.0 ports. I've rotated this damned thing through every single port on this computer...
-
So much for that brilliant idea. :(
-
I've got 4 3.0 ports and 6 2.0 ports. I've rotated this damned thing through every single port on this computer...
Hi Senerity,
This seems to be a power delivery issue to the USB ports on your mobo (not PSU related, mobo onboard USB power regulation) w\ the Saitek HOTAS plumbing and\or the powered hubs A-B side.
I had similar type issues w\ my Gigabyte X99M Gaming 5 mobo and my CH USB HOTAS thru a Belkin powered hub that I've been using for years. Couldn't use the USB 3.0 ports or the USB 2.0 ports on my mobo due to the power spikes and other POST issues. All my other USB equipment (keyboard, trackball, SB X7 DAC-AMP) works fine w\ all plugged into the mobo's USB 2.0 ports (I do still see a power spike now and then while using my trackball....pointer wanders a little). I don't have any USB devices plugged into the mobo's USB 3.0 ports.
Ended up installing a Gigabyte USB 3.1-to-PCI-E add-in card that's being powered from the PCI-E slot to fix it all to my CH HOTAS. Am currently looking at getting another USB 3.0-to-PCI-E add-in card to replace this 1 that has 4 ports available along w\ a cable to power the card off the PSU's 12v rail in addition to the PCI-E slot and do away w\ the Belkin powered hub for my CH HOTAS.
You might consider this alternative if you have an open PCI-E slot available on your mobo.
:salute
-
Grounding is shared. Sounds as if the whole unit has a ground fault/short.
Look at the cabling between units.
Look at the ports in the units. A bad solder joint will cause short ..