Problem with Warthog Throttle

[Succellus]

So Firmware is progress(maybe) but it ain t a saver.... SAD news.

[Callsign.Vega]

Wow so the firmware WASN'T a saver then. I don't feel so stupid now. Still sucks we are all grounded.. or at least I am. :(

 

You positive you had the newest firmware installed before the throttle stopped working? I haven't heard of any throttles stop working after the newest firmware patched. Once your throttle stops working you cannot upgrade to the newest firmware. That is where 99% of the people are having issues.

Edited December 20, 2010 by Callsign.Vega

[ZaltysZ]

From TM docs I assume that you need to run firmware updater twice (once for stick and once for throttle). Dastardly, have you done that when you updated firmware?

[Teej]

What actually had me confused for a few minutes was when you download and "run" the utility...I wasn't paying sufficient attention and thought that was actually updating the firmware. It just installed the updater on the PC. Heh. Glad I went into target to verify.

[Yoni63]

No, I didn't have the newest firmware installed, but from what I've seen on other forums, multiple people who "have" had the new firmware installed have experienced this same failure with the throttle.

[topdog]

Some / a few have had problems when installing the firmware update, one (that I've seen so far) had the same major problem after the update. I think most who've had the problem, had it before the update, but that's not indicative at this time of the firmware's ability IMO - just too early to say and not everyone will install it anyway.

[RSharpe]

Maybe I missed it, but what is the serial number of your HOTAS? I'm just wondering if there's a batch problem.

[Succellus]

??? So you come here and upon hearsays says it did not work on you ?!!

Please post up your info correctly next time.

[Yoni63]

I've posted correctly, I think you misread what I posted. No hearsy to it, other than other's that have this issue, "some" have already had the firmware updated prior to the problem. Polite will get you everywhere with me Succellus.

[Yoni63]

Maybe I missed it, but what is the serial number of your HOTAS? I'm just wondering if there's a batch problem.

 

Sorry it took so long to reply, I had to get back and get the info for you. There is a batch number on my invoice. It reads 00000316.. not sure if that is a "shopbuilt" number or an actual TM batch number. My serial number on my throttle is 01544.

[WynnTTr]

No, I didn't have the newest firmware installed, but from what I've seen on other forums, multiple people who "have" had the new firmware installed have experienced this same failure with the throttle.

So far I've noted only one person (Dastardly in this thread) who claim that their throttle bricked after firmware. Loz in the other thread didn't get to complete the firmware - his stopped at 75% then refused to go further after which his throttle bricked, which leads me to suspect that it was on the way to be bricked regardless of firmware or not.

 

It would seem, just going from these forums, that the firmware is a positive fix for bricking.

[Yoni63]

Wynn, I did a search on some other forums, similar conversations going on as we have here. If I had it to do over again, I'd do the update. I know the update is not what caused mine because I didn't even see it until it was too late.:doh: Either way, if it's going to brick, you want it to do it now so you can be grounded and play cards with the rest of us. :smartass:

[WynnTTr]

Wynn, I did a search on some other forums, similar conversations going on as we have here. If I had it to do over again, I'd do the update. I know the update is not what caused mine because I didn't even see it until it was too late.:doh: Either way, if it's going to brick, you want it to do it now so you can be grounded and play cards with the rest of us. :smartass:

Care to quote the source?

Sorry, I'm a stickler for real data so we can see the spread of this problem. That's the first step in real feedback to TM and they can address (and hopefully fix) the issue once and for all.

 

But given the number of throttles that bricked before the firmware and after, so far it's pretty clear that the firmware was positive in that regard.

 

Which ofc doesn't help you - but it would seem the only recourse for you is to get a replacement.

 

Make sure you flash it asap :)

[Vullcan]

My throttle is doing this and I've only had it a week :\

 

Got it from Amazon in the US and installed the latest firmware just after plugging it in because I read about all the problems the old firmware caused. Guess the firmware didnt fix it.

 

Good luck getting a new throttle to me anytime soon with this christmas shipping backlog eh?

[emenance]

#^Q##(&Q(*Q(%#()%+()@*#$)##()#()@#(^&%$^%&^#%$^$*&*@*@*$&($*@$*_+!()*#(!#*+#+(@ BS industry cant do anything right.

[Yoni63]

Wynn, I'd have to go back and try to find them, seems like one of them was fighterops forum. I was in my patrol unit and was doing it from my MDT, so I wasn't staying on those sites very long. I mainly just wanted to see what all was being said. It's pretty much the same as on our forum here. I think I entered something like Thrustmaster throttle issues in the search. From that I just browsed around at the hits.

[Succellus]

My throttle is doing this and I've only had it a week :\

 

Got it from Amazon in the US and installed the latest firmware just after plugging it in because I read about all the problems the old firmware caused. Guess the firmware didnt fix it.

 

Good luck getting a new throttle to me anytime soon with this christmas shipping backlog eh?

 

Vulcan did you updated the stick AND the throttle ?

What was TARGET reading as firmware?

[Vullcan]

Yes of course (I update firmware all the time). Upon plugging my stick in for the first time I first started the thrustmaster utility to verify my firmware was indeed out of date, and it was.

 

Then holding my breath (because people mentioned the firmware update process bricking their throttle!) I updated the joystick and thottle and was relieved to see them all get to 100%.

 

I then verified the new version numbers were correct in the thurstmaster firmware update utility and in T.A.R.G.E.T.

 

Finally I played with the sticks for about 7-8 days until yesterday when starting my computer I noticed the throttle lights were out and upon booting into windows and unplugging / restarting a few times that the device was indeed "unrecognized" to windows and was the same problem everyone else was having :cry:

[Callsign.Vega]

Hmm, so thats at least a couple of reports of people having throttle issues after applying the updated firmware. Not good! Hopefully TM will address this as I am sure they will grow tired shipping peoples throttles across the Atlantic in short order.

[Succellus]

Could this issue have relation with voltage/amperage spiking in USB plugs ?

[TwoLate]

TM is not talking at all on this. Is it the firmware? Or some cheap electrical component in the Hotas that goes out?

[RogueRunner]

TM is not talking at all on this.

 

Nothing new there. TM never talked in public about problems with their sticks, and face it, everyone thus far had some quirks!

[topdog]

Nothing new there. TM never talked in public about problems with their sticks, and face it, everyone thus far had some quirks!

 

Ok I'll bite / tempt fate / jinx myself. I haven't had quirks with mine. Did you mean every user had quirks with the TMWH, or that every product has quirks?

[RogueRunner]

Every product.

[Midwestboi]

Could this issue have relation with voltage/amperage spiking in USB plugs ?

 

This is an interesting idea. I wonder whether there is a correlation between leaving the stick plugged in and having the failures vs those who unplug them after shutdown? Maybe something is getting corrupted during the initial boot if the stick is plugged in during startup... it's a thought.