Saitek pedals not recognized by Win10?

Hello all,

 

I thought this had been covered, but I can't find anything in the forums. Since installing onto a Dell Alienware last spring my pedals have become an Unknown USB Device. Has anyone else had this problem? That's my main question. I'm wondering if they just need rewiring. They have itty bitty fragile wires inside. They have worked well for several years on my old Win7 system, and no I haven't tried plugging them into another computer. My next step.

 

I thought I read where Saitek, now whoever, knew about the problem and weren't correcting it. I doubt the new owners even care. I can't install the drivers because Win10 and Saitek's install program don't recognize the device. Saitek never offered updated drivers. Any thoughts on the subject would be appreciated.

 

My Saitek Pro Flight X-52 controllers have held up for years. My Saitek console (steering wheel and 3 levers) went out after about a year. I think the USB went out on it and I've never bothered to get it repaired. I'm thinking of going with some pedals of a higher caliber than Saitek.

 

I'm glad to see the FSX community going strong. A big thanks to all the mission, scenery and plane developers who have kept me busy for hours trying to figure out what's going on, and to all of you fellow pilots.

 

May the road never rise to meet you,

 

Phil aka pcwildman

Bell X-22A, revamped for FSX with PIGG HUD and Apache HUD, down for maintenance

 

FSX SP2 with too many add-ons on a Dell Alienware Win10, i7-6700HQ 2.6 Ghz 8G ram GeForce GTX 970, with the sliders all on high, except in heavy scenery, for the first time in my FSX career. Yes!

It's Win 10 that's the culprit; the Drivers (or lack thereof) don't recognize what the Pedals are supposed to do, hence the 'Unknown USB Device' warning. Win 10 has had issues in the past with recognizing certain types of Hardware, like HID's.

 

Check the connections from the Circuit Board to the USB plug to see if anything pulled loose; if so, re-solder as necessary.

 

I don't know if Logitech is planning to Update the Drivers, or make changes to them at all. Saitek was never very good with Drivers; most of the time they did more harm than good.

 

Alan :pilot:

I am in Win 10 and the two drivers are there and functional (top left to right 1 & 2):

 

 

Cheers,

I'm on windows 10 too and my Saitek pedals are working fine. I'd say try a different usb port.

 

Cheers Stinger

 

Sent from my SM-A300FU using Tapatalk

Thanks Alan,

 

That's pretty much what I expected to hear. I don't know why there's not more on this in the forums. I think I paid $120 for the pedals and now they're another doorstop. I'd sure like to know what other people are doing about it.

 

Keep it up,

 

Phil

 

I wrote the above before seeing the other responses. Now I suspect there's a problem with the pedals. Thanks guys.

This thread is about a different device, but it might give you some ideas:

https://www.flightsim.com/vbfs/showthread.php?301491-saitek-x52-not-recognized-anymore-after-last-win10-update

Thanks il88pp,

 

That thread lead me to the forum where I first read about the problem.

 

Now I need to know if running the USB Enhanced Power Management Disabler could lead to knocking out the X-52 controls? And is it really necessary? I don't know that I even have Enhanced Power Management. It's not something I've ever seen in Saitek installs and I don't use a fancy array of panels- just the X-52 and the pedals.

 

I'll keep hacking away.

 

Ever confused,

 

Phil

 

It looks like the threads here are talking about Win8 and 8.1. The solution is to reinstall drivers, but I'm back to my original problem of USB Device not recognized. I can't install new drivers because the device isn't really there, and I don't think power management or USB level is the answer. There appear to be different problems with different Saitek devices among different computers. And they told us High Tech would simplify our lives.

I have studiously avoided Windows 10 because I've heard so many "horror" stories from other simmers! So if it's a 10 issue, I have no knowledge.

 

However as a Saitek user myself I have two suggestions which might help if the issue isn't with 10 itself.

 

1. Go to the MAD CATZ site. They have better and more up to date drivers for Saitek devices than anyone I know. They also have a user forum dedicated to Saitek devices. You might find out about 10 there!;)

 

2. Get a powered USB adapter and plug your device into that. If you're using more than one USB device at a time, you probably would benefit from having less voltage drag on your motherboard. :cool:

 

Good Luck!

 

Michael

Thanks Michael,

 

I have all the drivers, software and disks, they just don't help. Win10 is a mixed blessing. On the one hand, it's the best thing since XP, on the other it is the most invasive Big Brother is Watching OS ever. I went from 7 to 10. Many of the Kaspersky, and other AV programs, components can't do their job. You don't actually own it, it is now a license. And it doesn't want to recognize my pedals. I'd still highly recommend it. When FSX runs it runs beautifully and I've heard some good things overall from other Win10 users. The problems seem to come from disparate computers, components and software. My HP Spectre (SSD) runs better under Win10, and does more, than any computer I've ever had. I use it for everything except games.

 

Now I know that other Win10 users had no problem with their pedals and I suspect mine need a wire reattached.

 

The powered USB hub solved some other problems, but, unfortunately, not the pedals. They're still not recognized. I can't believe I never thought of the difference between powered hubs and plugging straight into the computer. I assumed there were plenty of amps to go around. Obviously, there aren't. I only recently starting reading about it. My window on my X-52 throttle now stays lit. I need to complain more, I'm learning about how to solve a bunch of other nit picky problems here.

 

Thanks to everyone. I'll figure it out.

 

Keep Flying,

 

Phil

SAR in the Beaver out of Sandspit

I have no problems with the pedals, with FSX or XP-11beta. They're connected directly to the PC via USB, tht other Saitek bits use a hub. I installed the pedals while I still had Win7, then at some point installed FSUIPC. When I upgraded to Win10, the pedals were still recognized OK.

Sorry for the lazy link. In the thread I linked was a link to avsim.

There the fix is given as:

"install certain drivers and then *select the usb device manually*."

 

I wasn't sure if that tip would help you, but it helped the guy with the X52.

Hi... My Saitek Pedals suddenly stopped being recognized by Windows 10.. Went through all the forums and tried all the methods mentioned.. These are fairly old so I was worried it might be a hardware issue. I plugged them into my sons laptop via his USB hub and it recognized them so I knew then it was a windows issue. After a day of pain I said to myself.. What if I plug my sons USB hub into my powered hub and try that.. bingo! So my solution was to plug an older USB 2 hub into my newer USB 3 powered hub and plug the pedals into the USB 2 hub.. Hope that helps others out there with the same issue..

Thank you for this post, even though it was 5 years late! :cool:

 

This solution is relevant for anyone with any USB connection issues.

 

Good work -

 

Jorgen

Your approach of using an old USB 2 hub connected to a newer powered USB 3 hub to connect the pedals seems to have bypassed the problem and allowed Windows 10 to recognize them again. This workaround may help other users who have encountered a similar problem when connecting USB devices. We are still wondering what to do with driver's license, heard fake id Hawaii can be done in other cities, any thoughts? USB hubs provide additional ports and help distribute power more efficiently, so including them in the system sometimes helps solve compatibility issues. It is worth noting that USB 3.0 ports are usually backward compatible with USB 2.0 devices, but it is still possible for certain combinations of devices and ports to cause compatibility problems.