PDA

View Full Version : Massive Saitek Yoke Problems



Boeing 747 Flyer
08-20-2011, 07:18 AM
Hi everyone,

I am having major issues with my two Saitek Yokes.

Despite working fine for months, they have suddenly stopped working today.

Both Yokes, despite working perfectly in the Windows calibration window, and despite being recognised by FSX, will not allow their axis to be assigned to anything.

For example, if I try and assign the ailerons axis, I move the Yoke left and right... And FSX detects absolutely nothing. However, the Windows interface, and FSUIPC for that matter, all detect movement on BOTH yokes.

This morning, I managed to re-assign both Yokes (for some reason, FSX recognised the movements). However, after 5 minutes of working fine, after switching aircraft, the Yokes' movements were unrecognised by FSX, despite being recognised by FSUIPC and Windows.

Any ideas? The Yokes themselves are fine; it's just FSX isn't identifying their movements (but FSX does identify the Yokes as devices).

Cheers,

Jack

fordgt40
08-20-2011, 09:01 AM
Jack

Did you solve the problem with SIOC, if so, what was it? I ask because presumably the saitek yokes are connected via usb, as is the SIOC hardware. Pehaps a common issue here?

David

Ronson2k9
08-20-2011, 09:07 AM
Seems like more of an FSX problem then yoke. Did you recently have a power failure? Perhaps removing the yokes (USB direct or USB hub connection) to the computer and plugging them back in. I know that sometimes my stuff's recognition will be a bit wonky after a power failure.

Just to diagnose a bit farther you can try using the yoke in another game like a racing game or something to see if the yoke is loosing power. As you say it's recognized via windows and FSUIPC. It does seem more FSX related.

Boeing 747 Flyer
08-20-2011, 12:34 PM
Thanks for the replies everyone.

David, I did fix he SIOC issues (with the exception of the USBKeys Card, but I think this is electronically damaged, as windows identifies it as problem device). I doubt it's SIOC related, as only 2 OC products are currently plugged in, and SIOC is not started. The Yoke is entirely functional in FSUIPC and the Windows calibration interface, but not the FSX interface.

Ronson, I have no experienced a power failure, but did recently experience a BSOD when laying with the Yoke (although the problems were still occurring even before this BSOD). I think I agree with you when you say it's an FSX issue; as its ONLY the FSX interfaces that don't recognise the movements, whilst Windows and FSUIPC does.

Cheers,

Jack

fordgt40
08-20-2011, 02:02 PM
Jack

I was wondering whether it was a USB recognition problem. Presume you have tried swopping ports etc to see if problem follows. Sometimes it can nelp if you go into device manager and delete the majority of USB entries and let the system rebuild itself on reboot

Regards

David

Boeing 747 Flyer
08-20-2011, 02:52 PM
Hi David,

Thanks for that reply.

I have tried swapping the ports, etc, etc, but the fact that BOTH my Yokes are showing the same problem (which are obviously plugged into two separate USB ports) rules out the possibility of a Hub/Port failure.

Please may you expand upon the "deleting devices" idea? Do you mean disabling then re-enabling, or something else? I'd quite like to try deleting then rebooting, it could work.

Cheers,

Jack:D

fordgt40
08-20-2011, 03:02 PM
Jack

Sorry, just about to go out! Try a search on google for usb "unkown device" I had similar problems to your sioc once and it was machine dependent. I solved it by going into control panel/system/device manager and then click on view/show hidden devices. Then delete/remove the majority of the usb entries and let the computer rebuild them on reboot. There are a number of articles on the web - I just can`t remember or find them on my computer at present. It is a long shot but worth a try.

Regards

David

Boeing 747 Flyer
08-21-2011, 05:47 PM
Hi David,

Thanks so much for your idea. Deleting the entries and tehn restarting has fixed all problems; at least for now!!!

Cheers,

Jack

fordgt40
08-22-2011, 02:55 AM
Jack

Glad to help. I do not believe in co-incidences, so when all of a sudden you had two apparently unrelated problems it is worth looking for the common factor:)

Regards

David

Boeing 747 Flyer
08-22-2011, 04:09 PM
Thread has changed purpose!

I now have a problem with my Saitek Quadrant.

Despite working perfectly in the Windows device manager test page, all three levers on the quadrant are showing the same issue.

The levers are either "on" or "off" according to FSX. EG: If I set my flaps lever to 25%, it will set them to full. If I keep moving it up, nothing happens. However, if I pull it back to 0%, it will return to 0. In other words, it's either "all or nothing".

The exact same issue happens with the spoiler and throttle levers. Interestningly, FSUIPC rports the same problem when trying to calibrate from there.

However, if I got into device manager, and right click on the Yoke, and click "properties", I can move all three levers freely with absolutely no problems.

Arrghh!

Any ideas?

Cheers,

Jack

ridnum
09-03-2011, 12:20 AM
I think that your problem might be the settings in FSX. Since the throttle quadrant responds in windows device manager and you stated that it was " all or nothing".

1. Do you have a registered version of FSUIPC?
2. I think the quickest fix for this would be to go to the controls page in FSX and go to the axis page and try to reset the axis. Make sure that the quadrant is properly calibrated in FSX. Also make sure that the repeat slider is all the way to the left if somehow it is using a button press. The Saitek quadrant has a point where you could select "thrust reversers" if you slide the throttle all the way back, this might be the root cause.

Shawn
09-03-2011, 12:24 AM
Have you checked the null zone settings for those axis? and possibly the sensitivity settings? FS9 and even FSX has a weird way of resetting control assignments, seemingly at random.

Boeing 747 Flyer
09-03-2011, 07:12 AM
All fixed now guys, resetting through the device manager did the trick!