New TM HOTAS Warthog not recognized

[EagleDCC]

Hello All-

 

I just purchased a new (used, open box) Thrustmaster HOTAS Warthog off of Amazon. When I plugged them in, after installing the drivers & TARGET software, only the throttle side is recognized, not the joystick. When I plug it into either a USB 2.0 or 3.0, my system beeps seeing a USB device plugged in, but the software doesn't.

 

Any suggestions, quick fixes? Or should I just box it all up & send it back?

 

Thanks!

Mark

 

Edit: I'm running Win10

[dburne]

Does the joystick show up in game controllers in windows?

[hreich]

Maybe problem with firmware and bricked stick...just mail TM support they will send firmware upgrade tool

[firmek]

Did you connect throttle or joystick to the PC before installing the drivers?. If yes the drivers might have not installed correctly. In such case I would suggest to uninstall the software as also drivers. Stick/Throttle should be connected when installer asks to do it.

[EagleDCC]

Ok, uninstalled everything and rebooted. Downloaded the new driver from the TM website (2014_TMWH_1.exe), ran it and plugged both devices in when prompted. Each instance, my computer beeped that a USB device was plugged in. I check the game controller settings and it only showed the throttle.

 

Next I checked the firmware and it showed this:

[hreich]

Ok, uninstalled everything and rebooted. Downloaded the new driver from the TM website (2014_TMWH_1.exe), ran it and plugged both devices in when prompted. Each instance, my computer beeped that a USB device was plugged in. I check the game controller settings and it only showed the throttle.

 

Next I checked the firmware and it showed this:

 

It seems you need to upgrade stick firmware

[hansangb]

And use USB2.0 if you can. Some had issues with 3.0.

[SinusoidDelta]

Make sure the stick grip is correctly attached to the base.The connectors may not seated. I had a similar issue. After checking that try updating the bios.

 

If that's not the issue, I'd contact thrustmaster, maybe RMA.

[EagleDCC]

Thanks all for replying. I tried all of the above and no joy. I sent an e-mail to TM tech support, so we'll see what they say. I'm half tempted to open it up to make sure all of the inside connections are good, but don't want to void any returns or warrantees at this point.

 

This is what I get when I tried to update the firmware...

[1.JaVA_Platypus]

I have had several issues with USB devices not responding (anymore) in the past. Luckily, it is not my Warthog. Did you open-up the Warthog base or is the USB cable damaged? USB really does need the metal shielding in the cable.

[SinusoidDelta]

don't take anything apart until you speak with TM. The next thing I would try is going into your bios settings and turn off xHCI mode. Make sure you're using a rear USB port, see if the error is same, reinstall drivers and check again.

[Socket7]

This is probably why it was being sold in the first place. I'd return to the seller. TM isn't going to offer warranty service for a second hand owner. It's likely they'll make you pay for any parts you need.

[Vlerkies]

Give this a whirl bud.

thr_eng_00140 bootloader.pdf

[NeilWillis]

Those symptoms make me think you have either incorrectly connected the stick to the base, or you have a broken joystick unit.

 

Unscrew the stick from the base, and make sure none of the pins are bent or missing. If all is well, then refit the stick, tighten it all up properly, and try to update the firmware again. If that works, then you'll find the problem is solved.

 

If the problem persists, then I'd return the unit to the seller, and exchange it. It may be a broken main board, which if it is new, will obviously be a manufacturing defect. If however you have mounted the joystick incorrectly, and broken the pins, then you simply didn't follow the assembly instructions correctly. You'd better hope in that case that whoever you purchased it through doesn't realise that.

[Vlerkies]

Ihad an issue last year when I changed my usb hub after it blew, and the hog was not recognised anymore, even when plugged into the machine.

 

Try that bootloader procedure, it sorted me out.

[SinusoidDelta]

Check xHCI is off. If that is verified, remove the base plate. Verify the mini atx connectors are all attached.

[EagleDCC]

I've verified the connection to the base unit, and it seems good. I'll check the xHCI setting in the BIOS, and then I'll try the Bootloader procedure and let you guys know how it goes...

 

Thanks!

Mark

[hreich]

Just try the bootloader method per instructions ...i had the same problem twice...installing bulk driver while using my back side usb ports (not the front two) saved my bricked stick

Edited February 15, 2016 by hreich

[SinusoidDelta]

I meant internally, remove the steel plate from the bottom.

[EagleDCC]

Ok, I tried two other computers (Win10 & Win7) using the bootloader steps, no luck. Pulled the bottom plate off, the green USB wired was pinched, but still looked ok, everything looked ok & I checked all of the accessible connections.

 

Looks like I have a bad/ bricked stick :( I e-mailed TM customer support with the error code I get after the firmware update [ERROR: time-out device should had arrived in HID. (Code: 0x34100002)], maybe they have some other ideas.

 

I may just send it back...

[SinusoidDelta]

Dang, sorry to hear you didn't find anything. It could be many things, TM support may be able to shed some light on the error code. It might take a while to hear back. It's very likely some disconnection has occurred in the wiring. Was the stick purchased used? I would return it if possible. I wouldn't be surprised if something like this had happened:

 

I had your problem when I reassembled my warthog and pinched the ultra small gauge wife's running through the gimbal into the stick grip. I was able to resolder everything and got it working but I was pretty upset considering I broke it :/

[EagleDCC]

After much head scratching & frustration, I just RMA'd it back to Amazon. I have a new (new, unopened :) ) one being delivered tomorrow.

 

If it wasn't for the fact that it's so pricey, and it would have killed returning it, I would have completely opened it up to check all the connections.

 

Thanks to everyone that responded, you guys are awesome! :thumbup:

 

Looking forward to flying with some/ all of you on the NTTR!

 

r/Mark

[dburne]

After much head scratching & frustration, I just RMA'd it back to Amazon. I have a new (new, unopened :) ) one being delivered tomorrow.

 

:thumbup:

 

Smart move - a new Warthog should work just fine straight out of the box, hopefully your new replacement unit will be trouble free for you.

[Socket7]

After much head scratching & frustration, I just RMA'd it back to Amazon. I have a new (new, unopened :) ) one being delivered tomorrow.

 

 

 

Smart man. You get a full warranty now if anything happens in the future. If you ever have to RMA the new unit back to TM, make sure to ask them to reimburse you for shipping costs. They will happily do it, but only if you ask.

 

RMA's are so much less painful when they include free shipping. :thumbup:

[Tailhook]

Good to hear you got it sorted out. Remember to update the firmware of the new one.

 

Usually if you plug in the stick or throttle and Windows does the beep but doesn't show as a device but TM utilities detect the device, it is probably missing its firmware. Someone didn't know how to update it correctly and tried messing with it. It's not worth buying 'used' from unknown sources. ;)