[4.34.1] [SOLVED] IdleDetentCutoff function for warthog
-
Momentary SimThrottleIdleDetentCutOff and SimThrottleRightIdleDetentCutOff are new for U1.
-
Hi
Can anyone explain step by step the procedure to get a working warthog throttle cutoff when using TARGET?
Do I have to mark the thickbox idle cutoff in BMS config?
Thank you and best regards -
I’ve now received a reply from TM: they ask me to update / flash the WT firmware. I’m just wondering if any of our hardware experts here might expect this to fix the problem? To me it looks more like a wiring issue with the cutoff buttons as opposed to something than something that could be fixed by a new firmware version….
@Caldero: Sorry, I’m avoiding TARGET and use DX only.
All the best,
Uwe
-
Even though it is a switch that sends a signal it is not the component that sends the signal back to the PC. There’s a micro controller in there that does that. So its possible that a firmware update will fix your issue. There is also a calibration tool from TH that I’d use instead of the one that is included with MS Windows.
-
Looks like my throttle firmware is already at the latest version (v23), can some other kind WT owner please confirm this? Thanks!
I re-installed the firmware just to be on the safe side but the behaviour of the cutoff buttons hasn’t changed apparently (buttons 29 & 30 lit in IDLE position and off in CUTOFF position)
All the best,
Uwe
-
Yep you are latest for throttle - 23 and not latest for stick - mine says 12.
-
I was just thinking… I replaced the stock TM microstick on the throttle with a deltasim electronics one a while back, could this have anything to do with it? I’d rather think not, as the microstick came with its own little circuit board and it was a drop in replacement for the old one (with better haptics,though). I think I’ll ask around with others using the same microstick upgrade if they have experienced similar problems with the idle / cutoff switches.
Sadly I only started fiddling with the idle / cutoff stuff after the replacement, so I couldn’t even begin to tell if the throttle buttons 29 & 30 behaved as expected with the stock microstick.
Cheers, Uwe
-
Hoover, if I were you I would just do a complete recalibration of the throttle. This might solve your issue as it is not physical buttons, but “logical” ones based on throttle position value.
-
Hi folks,
thanks to Damien of “Deltasim Electronics” I was able to resolve the issue (see quote below). Apparently, I made a mistake during calibration of the throttle after installing his most excellent microstick upgrade a few months ago; I didn’t put the throttle in the CUTOFF position when I should have done so. Needless to say I feel utterly stupid and I’m quite sorry for wasting everyone’s time… OTOH I’m happy to say that everything works “as advertised” now.
I will also close the ticket over on the TM customer support site.
Again, thanks to everyone who helped to get to the bottom of this, the next beers are on me. :drink:
All the best,
Uwe
"The idle/off buttons on the throttle are not real buttons, they are purely virtual signals generated by the throttle controller when the throttle axis reaches a certain value. So I can’t see any way they could be physically faulty.
The most likely reason I can think is that the calibration was done backwards, when you ran the calibration tool after installing the upgrade it will ask you to set the throttle axis to OFF and IDLE. It does that to store the axis values to trigger the virtual buttons as above. I think if you move the throttle to the wrong position during the calibration weird things can happen.
I also know there are some parameters in the A10_Calibration.txt config file that effect it, but in not sure exactly which ones or what they do. I would recommend making sure you are using the file unchanged from my website."
-
Good to know it is not real buttons and great you resolved it that easily.
-
Hi guys!
I have a similar problem.
When going to 3d, throttle is already in idle and cannot be set back to cutoff. So no ramp start possible.
In the BMS setup the CUTOFF command is activated when throttle goes to cutoff, but not in 3d (first picture)What I have checked from based on previous posts in this threat:
- Firmware HOTAS: check (second picture)
- .key configured right: check (I think)
- keys 29+30 activated when in cutoff: check (third picture)
- no modifications on my HOTAS: check
My key file: https://www.dropbox.com/s/vueavdrfj3lldhn/BMS%20-%20MICRO_Neu.key?dl=0
What I’m not sure about is the device ID. Should it be always 314?
Maybe someone has an idea.
Thank you!