I'm trying to set up my X-Touch Mini to control the Fenix autopilot commands using AAO. I've been able to create scripts that turn the knobs (Baro, Speed, Altitude, Headings, and VS) using variations of the following: 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Knob_Inc). I've also been able to use the following to push 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push) and pull 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Pull) the knobs. However, when I send the command 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push), the knob stays pushed in (or same thing for pulling the knob) and I have not been able to figure out how to get it to release the knob. If I click on the knob again with the mouse it will release the push animation when I release the mouse click. 

I have tried using different numeric values for the push command [ex: -1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push)] without success. I've tried using the variations of 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push_Inc); 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push_Dec); and 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push_Set), but these all just seem to send the same push command (the L:S_FCU_EFIS_BARO_STD variable decreases by one with each push command regardless of Push_Inc, Push_Dec, or Push_Set). In the fnx320_interior.xml file there is an EFIS_Baro_Push_Release event, but I haven't been able to figure out how to activate it (I tired 1·(>B:FNX320_Input_Knob_PushPull_E_FCU_EFIS1_BARO_Push_Release) but that did not work either).

I've looked through all the scripts I could find on flightsim.to, but they all use the L-var commands to manipulate the knobs, which don't trigger the knob animations. I was hoping to use the B-vars since the animations work when using these. If anyone has any ideas or knows how to get the knobs to properly release after being pushed or pulled I would appreciate any insights!

Thanks,

Brian

Does it make a functional difference if the knob is in or out?

In general, input events have nothing to do with animations. It is often possible to do the one without the other - if the knob moves or not is controlled by the code that the aircraft developer made, and if it is tied to the mouse alone (or only half, like in your case) then it behaves weird. You would have to ask Fenix - or take a look at how that animation is triggered exactly (in the behavior code) and try to replicate that.

Edit: I've taken a look at the behavior code, and I think that this on Fenix's end. I'm not sure that the input events have been implemented correctly. Unfortunately I don't see a way to force the animation in any way.

Edited November 11, 20232 yr by Lorby_SI

No functional difference, but just trying to replicate it as close to how it should be as possible and wanted to make sure I wasn't missing something. I appreciate you taking a look at it!