I use a variation of this.
**************************************************
USE THR_RANGE (10% 90%)
THR 5 3 (0 2 98 100) Engine_Cycle ^ WEP_Cycle
-------------------------------
Engine_Cycle = /P e /R e
WEP_Cycle = /P p /R p
***************************************************
This cycles the engine on/off when you push the stick forward from its fully aft position or pull it back to the stops. WEP comes on when you push the stick fully forward and comes off when it's pulled back. I've also put the entire range of in-game throttle between 10% and 90% of the sticks physical throw. I've open up the throttle & moved the detents to match this.
This lets me free up a button that I'd otherwise have to use for Engine. Moving the detents & using THR_RANGE make sure I keep the throttle beween the detents during flight and don't accidentaly shut off the motors.
A coupla caveats with my setup. First off, you've gotta have the stick pulled all the way back when you hit the runway.
(Otherwise your engine presses will be backwards. You could always hit "e" to get started the first time, but that sorta defeats the purpose of a HOTAS doesn't it? Without getting too indepth with the programming, since the software can't report the axis' current physical position, this can't do EXACTLY what I want. I do have another idea that some of the TM gurus at Frugal's put forth to me, which I'll hafta play with to see if it works out any better for me.) Secondly, I use this only for flying single engine fighters. I haven't begun to set up my file for bombers and have no knowledge how useful it'd be for the buffs.
As with Revvin's, you've gotta do a manual calibration in order to use the THR_RANGE statement. After I've done this once, I just stick it back on Auto Calibrate.
I'm gonna finish fine tuning my programming file and post it here within the next day or two.