TWS cursor control - too many/fast moves by buttons

[ACME_WIdgets]

Just updated my 35 year old Thrustmast FCS stick/Mk2 HOTASa with Teensey2++ USB ($10 investment). Yes, I'm very cheap...but I like a challenge!

 

Joysticks work great.

All 16 buttons work great on things like flaps, gear, pulse rate..

 

 

BUT with a single button push on the TWS target up,dn,left,right they slew all the way up,dn, left,right with NO small increments - like I'm pushing the button 20+ times really fast.

Up/Down nose/elevator trim does the same thing.

I looked on the forums but don't see anyone else w/this issue.

 

 

 

I'm assuming DCS sees my hat (4 independent buttons now) moves without a leading or trailing edge single click only. But why only on these functions? Is there a .lua file setting somewhere for this?

 

 

 

On the Teensey s/w I'm using the simple Joystick commands. I am NOT running a Delay at the end of the program. I could try to add the Millisecond "delay" (so other commands can keep working).

 

 

If I have to I'll complicate my Teensey s/w by replacing the simple Joystick commands and go to a detect my hat buttons rising/falling edge, debounce, delay - but that limits my DCS software assigned keys.

 

Any suggestions ?

[David OC]

Ask the guy's in the home cockpit section. Someone there should know what's going on.

[ACME_WIdgets]

Problem Really Solved.

1- The Teensey library Joystick is not the same as the Arduino library.

 

 

2- For some reason the Teensey Joystick returns TRUE for Pin_HIGH (i.e. when internal PULL_UP is activated). So all my buttons where ON until I pressed one, then it went LOW or off. Hence my problem with "stuck" buttons in DCS (after I pressed a button one time).

 

 

 

3- PJRC (maker of Teensey) says to use this to trigger joystick on press (change to LOW), but this did not work for me: Joystick.button(pin_num, 1);

 

 

SOLUTION - add a "!" in front of the digitalRead(pin#) to flip the Boolean logic from TRUE to FALSE. So my button read statements look like this and it works perfect:

Joystick.button(pin_num, !digitalRead(pin_num))

Edited June 24, 2020 by ACME_Widgets
Found real solution, not prior one