Warthoggers: Updated firmware released

[kylania]

With PC powered off, if I unplug and plug the throttle back in the 5 LEDs flicker once.

 

If the backlights are ON when I shut down and restart they turn OFF as soon as the PC posts. They turn back on when my other USB devices light up, just after the "Starting Windows" animation finishes.

 

Sleep mode and shutting down does nothing, the backlight stays on till I unplug the USB cable or post again. This happens with both the front and rear (direct onboard) USB ports.

 

Drivers, TARGET and Firmware all updated:

 

[Sticky]

Updated, went smooth, everything works fine :) Yesterday I had the feeling of russian roulette and was thinking these guys got balls (the first people to update, like teej), but its really very easy to do and noone has had any problems sofar :)

 

*hands the revolver to the guy on my right*

Edited December 7, 2010 by Sticky

[Yskonyn]

Doesn't the power management page in you BIOS have several USB related settings? Have you checked those yet, kyl?

 

Do both the stick and throttle get updated?

[Sticky]

My throttle lights stay on also. Yes both units updated here. Lights stay on after I shut down the system.

[159th_Viper]

My throttle lights stay on also. Yes both units updated here. Lights stay on after I shut down the system.

 

Confirmed with Driver and Firmware update.

 

Have the Flight-stick and Throttle plugged into the G15 USB ports. G15 plugged into MB. At shut-down throttle remains lit up like a successful Gunpowder Plot.

 

Here's the kicker - At start-up however the lights extinguish, only to be lit up again when the G15 comes 'online'.

 

I'm beginning to wonder how difficult it is.......

 

 

Edit: Appears to conform with kylania as above.

Edited December 7, 2010 by 159th_Viper

[Yskonyn]

Just a loose shot from the hip, maybe we're confusing Hibernation with Standby?

AFAIK these are two different Windows states upon shutdown and might explain the different lighting effects on the throttle because we call both of them 'standby'?

 

Anyway, firmware update completed without any problems here. Glad it now has that 'HID write' protection! Gives me a warm fuzzy feeling! ;)

I'll put my pc in sleep mode and report in a minute.

 

EDIT: In 'sleep mode' (Win7)the throttle stays lit up like a Christmas tree indeed.

Now if someone could test Win XP Hibernate mode as opposed to Standby mode, please?

Edited December 7, 2010 by Yskonyn

[Sticky]

LOL no need to buy a Christmas tree this year then :) I KNEW it was gonna be worth it somehow ;)

[Yskonyn]

Yeah, though I don't like green lights in my green tree! ;)

Any way to make em another color?

[MTFDarkEagle]

change the led's inside :P

[Yskonyn]

With all the horror stories going on here about what happens when you open the WH up?! No way! ;)

[MTFDarkEagle]

True, but you asked how to change the colour, so I answered ;)

[DocSigma]

This is a stupid question but how do you update the firmware? I know in target their is a firmware update problem in the device windows but is it just clicking that link or is it just a matter of running the update by opening the file like you would any .exe? Also is flashing with additional controllers attached advisable like The cougar? Thanks

Edited December 7, 2010 by DocSigma

[kylania]

This is a stupid question but how do you update the firmware?

 

Follow the Instructions listed on the download page? :smartass:

[Pikas62]

Done...all good.

 

Over and out.

[DocSigma]

Follow the Instructions listed on the download page? :smartass:

 

Is it not advisable to update the firmware from within TARGET by clicking the the "update firmware" highlighted link in the GUI?

[Teej]

Just a loose shot from the hip, maybe we're confusing Hibernation with Standby?

 

My definitions:

 

Hibernate: Contents of RAM are written to disk and machine goes to a complete power-down state, can be disconnected from power for months without loss of data, etc. Maximal power savings as the system is shut completely off. On turning the machine back on, you get a full POST, may see "resuming windows", etc.

 

Sleep: System goes to a minimal power state - fans & drives shut down, etc, but not a full power off. RAM maintained under power (I think?). Loss of power results in loss of unsaved data, etc. Near total power savings because nothing is actually running. When activated it takes about 2 seconds from a silent system to having a desktop back.

 

Standby: Very little power savings - display shut off, fans keep running, etc. Also very quick to resume since nothing is actually shut down.

 

By those definitions, I use "sleep" mode, and if my throttle is plugged into the motherboard, the LEDs do go dark for me.

 

Here's a little more detail from: http://blogs.msdn.com/b/omars/archive/2004/05/11/129553.aspx

 

S0 - Working State

In this state, your PC is awake and working

S1- CPU Stopped

In this state, your PC is technically in standby and this is the default standby state if S3 is not supported. Power consumption is Five Watts to Thirty Watts of Power.

S3 - Suspend to RAM (context saved to RAM)

In this state, your PC in standby and all fans, hard drivers and other devices are powered down into a sleep state. Power consumption is less than Five Watts.

S4 - Suspend to Disk(Context saved to HDD)

Otherwise known as Hibernate, your PC has saved the contents of RAM to the hard disk and is pretty much tuned off. Power consumption is less than Five Watts. This isn’t very useful for desktop PCees and is mostly used in Laptops where battery drainage is far better than if you are in S3.

 

 

My lights go off in S3.

Edited December 7, 2010 by Teej

[Cali]

Confirmed with Driver and Firmware update.

 

Have the Flight-stick and Throttle plugged into the G15 USB ports. G15 plugged into MB. At shut-down throttle remains lit up like a successful Gunpowder Plot.

 

Here's the kicker - At start-up however the lights extinguish, only to be lit up again when the G15 comes 'online'.

 

I'm beginning to wonder how difficult it is.......

 

 

Edit: Appears to conform with kylania as above.

 

Your G15 supports them? I haven't really tried plugging anything into mine besides my camera to download pics. I did try something a while back and it wouldn't work. Also saw threads on Logitech forums talking about the low power to the USB ports.

[159th_Viper]

Your G15 supports them?

 

Correct.

 

Was in such a hurry when the Hogstick arrived that I plugged them in the first available holes I could find......To my surprise it worked and has been fine ever since - apart from the dayglo green tinge of the PC room, that is :D

[Teej]

Also saw threads on Logitech forums talking about the low power to the USB ports.

 

Don't have a G15, but I'm not surprised the sticks work plugged into it. I'd be concerned about the power if I was trying to charge something or use USB powered "toys" from the keyboard...but operating the sticks, even with LEDs, should be extremely low power.

[Loz]

If it's not broke then don't fix it .......DOH

 

Well I followed all the instructions listed above to the letter, and at 75% on the Joystick update it failed.

Now I have a Joystick that isn't recognised as one.

Where do I go from here, please.

It is seen by the system and calls itself "Thrustmaster HOTAS WARTHOG Joystick Bulk" but does not show as a game

controller, visible to either Windows or Target Device Analyzer

 

HELP>>>>>>>>>>>>>>>>> :joystick:

Edited December 7, 2010 by Loz

[Cali]

Correct.

 

Was in such a hurry when the Hogstick arrived that I plugged them in the first available holes I could find......To my surprise it worked and has been fine ever since - apart from the dayglo green tinge of the PC room, that is :D

 

Don't have a G15, but I'm not surprised the sticks work plugged into it. I'd be concerned about the power if I was trying to charge something or use USB powered "toys" from the keyboard...but operating the sticks, even with LEDs, should be extremely low power.

 

I guess I'll have to use mine. As I said before I saw many threads at their forums saying the power to the USB ports where to low. Some said they couldn't plug anything into them. Maybe just found the new place to plug my headset or external HD into.

[Sticky]

Well I followed all the instructions listed above to the letter, and at 75% on the Joystick update it failed.

Now I have a Joystick that isn't recognised as one.

Where do I go from here, please.

It is seen by the system and calls itself "Thrustmaster HOTAS WARTHOG Joystick Bulk" but does not show as a game

controller, visible to either Windows or Target Device Analyzer

 

HELP>>>>>>>>>>>>>>>>> :joystick:

 

:music_whistling:Russian roulette, first victim. Round two begins, who is next?:helpsmilie:

 

Try the obvious stuff, like rebooting, unplugg/plugging it back in, trying the software again. Otherwise idk, contact TM? It sounds really bad, since you probably did the update to prevent this from happening, and the update itself caused it.

[kylania]

Is it not advisable to update the firmware from within TARGET by clicking the the "update firmware" highlighted link in the GUI?

 

I never saw that till after I'd updated, but all that seems to do for me is change that text to show me the version number I'm using.

 

I think since they have just released the dedicated firmware tool linked in the first post of this thread you should probably use that to update firmware on your WH.

[swift]

Well I followed all the instructions listed above to the letter, and at 75% on the Joystick update it failed.

Now I have a Joystick that isn't recognised as one.

Where do I go from here, please.

It is seen by the system and calls itself "Thrustmaster HOTAS WARTHOG Joystick Bulk" but does not show as a game

controller, visible to either Windows or Target Device Analyzer

 

HELP>>>>>>>>>>>>>>>>> :joystick:

 

In ".\Program Files\Guillemot\tmfwupdater\firmware" (not sure about the exact location, I'm not in home) there's an updater log file somewhere. Post that file here, maybe we could see the culprit.

[Loz]

In ".\Program Files\Guillemot\tmfwupdater\firmware" (not sure about the exact location, I'm not in home) there's an updater log file somewhere. Post that file here, maybe we could see the culprit.

Here is detail from that tm_fwupdate_trace.log

 

[sTART SESSION]

 

16:28:22.545 Tuesday December 7, 2010

+00:00.000 Thrustmaster Firmware Updater (2.1.8.0)

+00:00.000 GUI size detection: 0

+00:00.000 GUI size after constraint: 0

+00:00.156 Initialization completed.

+00:16.193 Application will terminate.

 

[END SESSION]

 

---SMCH-

 

But I think that might be recording subsequent attempts to install it, or even the successful Throttle firmware update that I have done after the abortive Joystick try.

 

 

I've tried all the "rebooting, unplugg/plugging it back in, trying the software again" All no good.