Jump to content

Recommended Posts

Posted
AFAIK, no one has reported a throttle going belly-up while in use - it's always been either the PC boots and the Throttle fails to come online, or it fails to come online when it's connected to the USB port.
Bingo That is a very accurate statement.

[sIGPIC][/sIGPIC]

Posted
Bingo That is a very accurate statement.

 

Only in the sense that it never failed while in use and it always failed while idle. (Which imo is redundant).

But the AMD owners which had the failure seems to say that the throttle was OK then suddenly died.

 

Would it have died:

1) When going on sleep mode by itself ?

2) When USB not receiving imput send a "i gonna power off message" ?

3) Any other ocasion i can t think of.

 

Would it be a eeprom programing bug ? But if so, all the others Warthog would suffer the same problem. And we already had report of Throttle bricking on always powered USB ports (lights never going off until bricking).

 

Would some message from USB management erase eeprom, flash eeproom ?

 

Anyone have knowledge on USB interfacing does know if interface send a "reset like" message that could be interpreted by the eeprom like an "erase/flash" order ?

Something like:

USB interface: Hey i m going to reset myself, ok?

Throttle: You want me to reset myself ? OK

And Bingo...

 

I know it sound ridiculous.

HaF 922, Asus rampage extreme 3 gene, I7 950 with Noctua D14, MSI gtx 460 hawk, G skill 1600 8gb, 1.5 giga samsung HD.

Track IR 5, Hall sensed Cougar, Hall sensed TM RCS TM Warthog(2283), TM MFD, Saitek pro combat rudder, Cougar MFD.

Posted

Pretty sure the microcontroller in the throttle would be the only component with direct access to eeprom, if it even uses eeprom or some other persistent storage in the throttle. The only thing I can think of on the PC side is TARGET or the firmware update utility because they probably interface more deeply with the firmware, whereas vanilla windows only sees a USB HID device and can't flash new firmware or send configuration to the throttle or things like that. But I still don't think the PC is responsible at all, this seems to happen at random and as long as the thing is running, meaning the green lights are lit, it could brick at any time. This is just a gut feeling though... I'm in the dark like everyone else, I just don't see how external interfacing could cause the issue. It seems more likely that the problem exists completely within the throttle itself. Everyone wants to correlate the problem to external forces like what brand of MB or when do you plug/unplug it because those things are known to them and they have "control" over them. TM's initial reaction was a firmware update would take care of the issue. Well that didn't seem to pan out, but doesn't mean their intuition was wrong.

Posted

1. perhaps Spud could give us more detail?

 

2. sleep mode?

 

 

Suspend Current

 

Suspend mode is mandatory on all devices. During suspend, additional constrains come into force. The maximum suspend current is proportional to the unit load. For a 1 unit load device (default) the maximum suspend current is 500uA. This includes current from the pull up resistors on the bus. At the hub, both D- and D+ have pull down resistors of 15K ohms. For the purposes of power consumption, the pull down resistor at the device is in series with the 1.5K ohms pull up, making a total load of 16.5K ohms on a VTERM of typically 3.3v. Therefore this resistor sinks 200uA before we even start.

Another consideration for many devices is the 3.3V regulator. Many of the USB devices run on 3.3V. The PDIUSBD11 is one such example. Linear regulators are typically quite inefficient with average quiescent currents in the order of 600uA, therefore more efficient and thus expensive regulators are called for. In the majority of cases, you must also slow down or stop clocks on microcontrollers to fall within the 500uA limit.

Many developers ask in the USB Implementor's Forum, what are the complications of exceeding this limit? It is understood, that most hosts and hubs don’t have the ability to detect such an overload of this magnitude and thus if you drain maybe 5mA or even 10mA you should still be fine, bearing in mind that at the end of the day, your device violates the USB specification. However in normal operation, if you try to exceed the 100mA or your designated permissible load, then expect the hub or host to detect this and disconnect your device, in the interest of the integrity of the bus.

Of course these design issues can be avoided if you choose to design a self powered device.

Suspend currents may not be a great concern for desktop computers but with the introduction of the On-The-Go Specification we will start seeing USB hosts built into mobile phones and mobile organisers. The power consumption pulled from these devices will adversely effect the operating life of the battery.

 

http://www.beyondlogic.org/usbnutshell/usb2.shtml

 

hence my earlier question on; is the TM fully USB compliant?

City Hall is easier to fight, than a boys' club - an observation :P

"Resort is had to ridicule only when reason is against us." - Jefferson

"Give a group of potheads a bunch of weed and nothing to smoke out of, and they'll quickly turn into engineers... its simply amazing."

EVGA X99 FTW, EVGA GTX980Ti FTW, i7 5930K, 16Gb Corsair Dominator 2666Hz, Windows 7 Ultimate 64Bit, Intel 520 SSD x 2, Samsung PX2370 monitor and all the other toys

-

"I am a leaf on the wind, watch how I soar"

Posted (edited)

Reporting in: Throttle returned and it is the original SN that I sent out (phew).

 

Firmware 20 for me. Is it possible that " formerly bricked and now repaired" require FW 20, while Throttle with no issue only require FW 18?

Edited by Toadster
Spelling mistakes
Posted

Good news. Lets hope we can get you back up in the air. I'll be about tonight from 2100z I think, as will Smudge I reckon.

 

 

Three weeks later and all still working, that's 2 weeks 4 days longer than last time.

[sIGPIC][/sIGPIC]

487th Helicopter Attack Regiment, of the

VVS504 Red Hammers

  • 1 month later...
Posted

Can't configure the throttle,on DCS. On "game" settings works fine, but in "sim" settings, there are no "lines" at all for the TM warth throttle, what to do?

Posted

Delete the Throttle-HOTAS Warthog file in C:\Users\xxxx\Saved Games\DCS Warthog\Config\Input\A-10C\joystick

 

You will have to reconfigure everything by hand then though.

With the price of ammunition these days do not expect a warning shot.

Posted

By "lines" do you mean Curves? Did you assign throttle axis to WH in Sim as well as in game?

 

Edit: As above, but you may want to try re-loading WH throttle config from the menu.

[sIGPIC][/sIGPIC]

  • 3 weeks later...
Posted

My throttle just bricked the same way everyone elses did...

 

Funny part is, the new firmaware was released last night, and it died today... This is serious now... If its ahardware problem then all that needs to be done is wait for a new driver update to solve the problem no? Or will they have to replace the damn motherboard on the throttle completely? Cuz im afraid it will just happen again...

Posted
My throttle just bricked the same way everyone elses did...

 

Funny part is, the new firmaware was released last night, and it died today... This is serious now... If its ahardware problem then all that needs to be done is wait for a new driver update to solve the problem no? Or will they have to replace the damn motherboard on the throttle completely? Cuz im afraid it will just happen again...

 

 

A new firmware was released last night ?

 

I just checked so I could upgrade and its the same firmware version thats been available for the last month and a half, versions 20-11.

 

Is that the version you are speaking about or do you have a later version ?

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...