Throttle as Keyboard using USE THR_RANGE Foxy Statement - is not working

[dodgerdog]

Hello, I’m trying to transform a Foxy file that has the following “USE THR_RANGE”, THR definition, but does not work when configuring Falcon v4.33 throttle as keyboard. Sure enough, if I just configure Falcon as “Cougar Thrustmaster” throttle, instead of “keyboard”, the throttle functions. Is there something I need to do to a configuration other than the UI in Falcon in order to make the below statement function properly?

Rem –-------------------------------
Rem DIGITAL THROTTLE
Rem ---------------------------------

Rem >> end of pasted code >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

DEF X28 DELAY (2000) X27 AND T6 AND S3
BTN X28 Idle_Detent

Rem >> Paste new code in this box >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

USE THR_RANGE (15%, 100%)
THR /U 5 4 (0 5 75 88 100) (/H Wheel_Brakes) UNLOCK (THR) LOCK (THR, 75%) UNLOCK (THR)
/M /I 5 5 (0 5 75 80 88 100) (/H Wheel_Brakes) UNLOCK (THR) (X28) LOCK (THR, 75%) UNLOCK (THR)
/O 5 4 (0 5 75 88 100) (/H Wheel_Brakes) UNLOCK (THR) LOCK (THR, 75%) UNLOCK (THR)
/D 5 4 (0 5 75 88 100) (/H Wheel_Brakes) UNLOCK (THR) LOCK (THR, 75%) UNLOCK (THR

[Arty]

This is an input axis from a specific device which uses a driver.
The keyboard uses different driver and doesn’t have analog axis.
So what u r trying to do isn’t doable.
U must use the keyboard specific commands for throttle.
What u might be able to do is for certain percentage of throttle to assign specific keyboard command but that again will need the throttle input and not the keyboard input.

Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk

[dodgerdog]

I’m not understand in the USE THROTTLE use to work even in very early BMS versions. The Cougar throttle is plugged into the Cougar joystick which in turn plugs into a USB port on the computer. The “wheelbrakes” macro for a key of “w” piece of the throttle statement does work. Is it just no longer feasible to use a calibrated statement like the above anymore? Thanks…

[Arty]

W is a keyboard command.
Throttle is an axis from 0 to 256 (example numbers).
Your keyboard has an axis?
If it does use it, no need for cougar throttle.

Sure it doesn’t have. So how can an axis from 0 to 256 be a few keyboard commands?

Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk

[dodgerdog]

I have solved the issue - forgot that there needs to be a valid “manual calibration” stored after flashing firmware. The values in this posts throttle statement are once again a calibrated precision.

[Arty]

Hmm nice.
I thought u wanted to use keyboard for throttle.
Got confused, another time.
Yeap calibration is good when changing axis like that.

Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk

[white_fang]

If he read the manual , he would know that. … otoh, … he maybe did

Notes
1.) To use the THR_RANGE statement, you must have performed a manual calibration at least once since the last firmware flash. You don’t have to be in manual calibration mode to use this statement – it’s just that the data collected from the manual calibration is required by the compiler to make this statement work.

Anyway, I would re-do this statement a bit different. … delete all and leave it clean full throttle axes , … use default S3 + T6 for idle_detent … it is not that you use it much… depends on sam/aaa cover
-remove wheel brakes from /U /D positions… you’ll rarely land in dogfight/mrm mode, maybe like never? - so you dont need brakes there
You already should have wheel brakes on S4 by default , check bms key config … down to the cougar/joystick/dx-shift section.

So, almost whole cougar is left as analogue axes… 99% S3 shifting is done by BMS, dx shift (+256 or 512)
eg. TG1 is DX 0 (dx-button1) and S3+TG1 is DX 256 (dx-button257) and so on …

I know it somewhat ‘kills’ old good programming which is btw a must to learn just because is … I dont know… , neat , cute and cool… and works oob (and written by Nutty )

[dodgerdog]

I’m happy with the statement as is - and I did have to read the Cougar syntax manual to “remember” - doh. However, I do appreciate the tips…