HAS Anyone Looked inside the TM WH throttle?

[Ziggy]

I ask this question as I haven't as yet but have been given the option to replace/install a replacemant MoBo supplied be TM for my bricked throttle rather than sending it all the way to France from Oz or option 2 is, return to point of purchase which means sending it 2000km from Adelaide to Sydney...

The extract from my TM email will be of interest.....

To quote TM

"All Throttles that had this issue were having a computer with the ASUS P5 series mainbord, we have investigated this and developed a new firmware update."

Mine bricked on an Apple iMac! Go figure.....

 

Your info (if available) will be much appreciated! <S

Edited February 1, 2011 by Ziggy

[sndwv]

Interesting! Should I interpret this as firmware being the culprit after all, but in order to replace a throttle already 'damaged' by this, one needs to replace the whole motherboard with one with the new firmware loaded rather than being able to just flash the new firmware onto the existing motherboard?

[MTFDarkEagle]

Do you mean hardware-wise? Or software-wise?

 

In case of hardware: http://forums.eagle.ru/showthread.php?t=62564

 

In case of software, I don't know.

[Succellus]

Dark eagke i think Ziggy is speaking about the throttle innards, the link only contain stick innards.

Ziggy if i was to guess, its not a firrmware issue, unless the firmware is solded to the throttle mobo.

I think that they are trying to fix a hardware problem trought the firmware.

Since firmware 20 it seems throttle is only waking up when windows is loading and its start its shutdown when windows is being shut down (before computer).

Reading throught that i say:

Mobo component issue due to voltage/amperage spike/arcing while computer shutdown or wake up.

[Maverick]

To quote TM

"All Throttles that had this issue were having a computer with the ASUS P5 series mainbord, we have investigated this and developed a new firmware update."

Mine bricked on an Apple iMac! Go figure.....

 

Asus P5Q Deluxe mobo here. I have decided not to use the Warthog before we get more information. I've been afraid it goes dead everytime I plug it in.

[sobek]

Mobo component issue due to voltage/amperage spike/arcing while computer shutdown or wake up.

 

I'm pretty sure that if the usb ports supplied voltage spikes to fry the hardware, then other peripherals would die in the same instant. Still sounds like a firmware and not a hardware related issue to me.

[Ziggy]

Well guys, I've decided to go for the MoBo option mainly to get this thing sorted before the end of the year! (the throttle died 30.12.10!)

I had a quick look inside last night and it doesn't seem to be too difficult to replace the board. Can't see any damage (cooked bits) but if this is what the designers/builders of the hardware say needs replacing, I'll go with that.

IF TM send the MoBo straight away, I might be able to start flying again early next week.........fingers crossed.

As people are suggesting the firmware is being used to change the way these units shut down/start up to avoid a damaging (to the TMWH) power spike but once the damage is done the only way is to replace the board. I wonder if these new boards are in any way different to the originals?

Anyway, thanks for your responses. Hopefully the info from TM helps others.

[Succellus]

I'm pretty sure that if the usb ports supplied voltage spikes to fry the hardware, then other peripherals would die in the same instant. Still sounds like a firmware and not a hardware related issue to me.

Then what would be in the comercial firmware that isn t in the beta firmware, and that AMD system dont fubar? just speculating.

 

i find it strange that the firmware can t be hard reset to 0 and the mobo has to be changed.(but then i m no specialist)

The 2.0 version also seem to be avoiding computer wake and computer last energy moment.

[Slammin]

How many AMD systems are there out there vs. Intel systems? What is the ratio?

 

Now, what is the overall ratio of failed vs. non-failed throttles?

 

Do the math.

 

And if you are really aware, in the old days we used to home cook eeproms. Not something TM would expect anyone to be able to do at home these days.

[Succellus]

The day you proove me wrong with 1 AMD cooked warthog i ll change my mind, but so far you failed.

You ratio is useless again, and as ever, as you don know squat, and slowly numbers proove you wrong unfortunatly, as streak of bricked throttle are slowly appeareing with owner already victims of resent throttle bricking, (at least 2) and people are lost to what to do.

This case is getting worse worse because it shows TM weren t much knowing what was the problem as i thought they would, or aren t able to fix it, lets hope that 2.0 firmware eliminate the problem.

 

 

And what is your point about eeprom culinary exactly ?

[Slammin]

Mr. Suc,

 

Let's assume that out of 1000 WH throttles, 1 will fail. Now, let's put those 1000 throttles out in the wild, where 90% PC's are Intel, and 10% are AMD.

 

Is is coming any clearer to you now?

 

"i find it strange that the firmware can t be hard reset to 0 and the mobo has to be changed.(but then i m no specialist)"

 

TM offerered the customer the option of sending in the circuit board. I'd bet money that TM will not have to replace any component on the failed unit and will just reprogram it instead.

[aaron886]

And what is your point about eeprom culinary exactly ?

 

LOL. :D

[Succellus]

Mr. Suc,

 

Let's assume that out of 1000 WH throttles, 1 will fail. Now, let's put those 1000 throttles out in the wild, where 90% PC's are Intel, and 10% are AMD.

 

Is is coming any clearer to you now?

 

"i find it strange that the firmware can t be hard reset to 0 and the mobo has to be changed.(but then i m no specialist)"

 

TM offerered the customer the option of sending in the circuit board. I'd bet money that TM will not have to replace any component on the failed unit and will just reprogram it instead.

 

Your aguing is falacious because its based on thin air, sorry. A dozen times i asket you for facts and so far nothing.

About TM offering the option, afaik it hasn t happened, if you know this from a fact outside this forum or HQsim, it would have been elegant to bring it in and then bitchslap me if its the case.

Now i would be obliged to say: link it or its a lie, because so far, and this is me included, some people are more or less pissed to have to send the whole brick when the throttle mobo would be suficient.

 

Frankly, since i bashed TM on quality assurance and on post sale services you ve been gnawing at my heels like a dog willing to bites car tires.

I don t really care as i find it funny. But you are wasting your precious time.

There are more interesting things in life to try to bash me. (i hope)

BTW have you any TM share, are you TM employee or do you depend on TM for anything ?

It would explain your attitude. Its a pathetic question but hell, i never seen someone defending a company as you are without financial bond.

Unless i have hit some exposed nerve somewhere then i m sorry it wasn t intended.

 

Keep it coming if you like, but at least check your weapon, ammo, and learn to aim.

[Slammin]

You asked the question of why don't we see the throttles failing with AMD, and I attempted to explain it to you as best I could. I also incorrectly made the assumption that I was dealing with a person of reasonable or average intelligence.

 

Don't forget to put your helmet on next time because too many head injuries can have a culmulative effect on the brain, making you a difficult person to have a reasonable conversation with. :helpsmilie:

[Succellus]

I prefer thin foils hat.

[Wolf Rider]

the only position which can be determined from no AMD boards being involved in throttles bricking, is no AMD users have (as yet) spoken up.

[Slammin]

If there were the same number of AMD users out there as there are Intel, I'm betting we would have seen some failures from AMD users too. I think the reason we haven't yet is because there are not enough AMD users with the Hog, and the failure rate is not as high as some would make it out to be. Really, all this blaming Intel, Asus, and whatnot is kind of silly. The problem, bottom line, is something TM will need to address, not AMD, Intel or Asus.

 

Now, I am done with this subject as it seems I am making enemies.

 

Peace.

[Ziggy]

Agreed Slammin. The manufacturers of many USB peripherals have made them to withstand whatever spikes that might occur when PCs are powered up and down. I myself have several that haven't had ANY issues so I also believe(for what itsworth) this to be a TM issue. Now I wait.... Once again for an email informing me what TM will do and when I might have this otherwise fantastic kit working as it should.

[Geskes]

Doesnt the bricked apple case refute the intel theory?

 

Basic Karl Popper to me.

[Ziggy]

No. Actually. The iMac is powered by the intel i7 chip. TM maintains all bricked throttles were on ASUS p5 MoBos even though I stated my secondary ( superseded by the Mac) Pc had an Asus board but was used ONLY as a test bed AFTER the unit failed.

[Wolf Rider]

I've read where P6's were involved as well, both in bricking and not bricking

[Ziggy]

Wolf Rider,

That may be so but to once again quote TM......

"All Throttles that had this issue were having a computer with the ASUS P5 series mainbord, we have investigated this and developed a new firmware update."

[Wolf Rider]

sorry, I don't understand the point of your post

[Succellus]

the only position which can be determined from no AMD boards being involved in throttles bricking, is no AMD users have (as yet) spoken up.

 

Even with MAC failures reports (1 or 2 of them) thats are probably less than 1% of the systems here ?

 

I agree with you, but its looking each time less probable as time passes and numbers grow.

Its each time more looking like, its not because we havent seen a unicorn that they don t exist argument.

I hope i am right in this for the AMD WT owners sake, if only that.

 

I guess we will have a clearer picture of whats happening after firmware 2.0, since TM have delayed WT wake up to be parallel with windows load time, and speeded shut down to windows shutdows start, thus avoiding supposed spikes and arcing.

 

But if we continue to have no AMD failure, and 2.0 fails (more bricks) it may well be how Intel system distribute informations to the device. Its remote, improbable, but who knows.

 

Anyhow, it aint Intel faults.

 

As for the sending mobo instead of the entire throttle, i stand corrected and happily corrected, this is good news for me if my throttle bricks.

Edited February 3, 2011 by Succellus

[Teej]

I'm pretty sure that if the usb ports supplied voltage spikes to fry the hardware, then other peripherals would die in the same instant. Still sounds like a firmware and not a hardware related issue to me.

 

Not to mention the USB controllers on the motherboard itself.

 

As to the OP's quote from TM...as the OP said he is on an imac, not an Asus board. I recall reading at least 1 bricked unit was used with a Gigabyte mobo, too.