Hello all
I would like to control the FCU of the Fenix A320 with buttons and rotary encoders. With the FBW A320 this works quite well with Mobiflight. Now I want to control the Fenix via Axis and ohs. With the Elgato Stream deck this works already.
I have connected my Arduino board (actually Elegoo Mega 2560 R3) with Axis and ohs via "Arduino to AxisAndOhs Bridge 1.01 b02". The board is connected and in the observation tool RPN scripting you can also see that the commands arrive.
In the screenshot you can see in yellow the commands coming from the stream deck. These are working fine. In turquoise you can see the commands coming from the Elegoo board. The first "call" comes when you press the button and the second "call" when you release the button. Unfortunately, this is not how it works.
Do you see a bug somewhere?

Translated with www.DeepL.com/Translator (free version)

Not sure that I understand.

What is your question about? Is it about the script or is something wrong with how the bridge is operating? 

You can see that the stream deck sends 1 or 0 when pressing the button. When I press the button on the Arduino board, it sends 0 on press an 0 on release. But there is no configuration possibility in the button definition in the AAO Arduino Bridge software.

Additional info: I inserted the same script in the stream deck command and in the Arduino board command

Here boths scripts

10 hours ago, hennezmuc said:

You can see that the stream deck sends 1 or 0 when pressing the button. When I press the button on the Arduino board, it sends 0 on press an 0 on release. But there is no configuration possibility in the button definition in the AAO Arduino Bridge software.

The Arduino handles the key down and the key up events separately. This is by design, otherwise you wouldn't be able to create an actual switch (as opposed to a momentary button)

Your script is a Toggle, and used like this it fires every time you either "press" or "release" the Arduino input. Your script would have to take that into account, for example using the "arduinoval" parameter as it says below the textbox. Or use a standard Button assignment, which in this case would probably be the better solution. Using a button and assigning that in AAO you can reference the script in AAO and don't have to duplicate the code. If something changes in the implementation in the aircraft you would only have to adapt the one script. With your solution you would have to update two scripts.

On a side note - when you copy script code around, use the compiled code from the lower textbox on the editor dialog. Don't just copy&paste the code from the editor box, it contains markup characters (the dots) which are not valid when used in other apps. When you copy the compiled code, these dots (and all other markup) are removed automatically, and you get clean code when pasting it elsewhere.

Edited January 11, 20233 yr by Lorby_SI

Hi Lorby_SI

Thank you for your help. With button configuration it works fine.

 

I Like it with touching nobs, instead of scrolling with the mouse without any haptic