I have successfully managed to bind most of the Garmin G1000 auto pilot functions to my X-Touch Mini rotarys and buttons. They work for the Cessna 172 G1000 NXi, Bonanza and TBM but the BAe-146 seems to be a whole new ball game.

I read the thread @Cool “can't find AUTOPILOT RADIO ALTITUDE MODE control assignments “ to see if there were any clues for other auto pilot functions and tried to find your suggestion of “1 (>L:MCP_Alt_arm, Number)“ in the Local Simulator Variables list but couldn’t find it, (I was able to find “(L:MCP_Alt_arm_il, Number”). However when I put “1 (>L:MCP_Alt_arm, Number)” in a script and tested it I could see the ALT ARM button light up in the VC !

I am trying to bind the auto pilot Altitude setting and when I view the “Watch simulator events” and turn the knob in the VC I see this event has been triggered:

20: [66036]: 0 (>K:AP_VS_VAR_SET_ENGLISH)

I don’t know what to do now and some help would be appreciated.

Steve

4 hours ago, rC10B said:

but couldn’t find it

Not all LVars can be found with the "Read LVars from sim" feature, the sim is hiding some for whatever reason. You have to trust me that it exists, and if you don't want to use a script for your button, enter the variable manually (there is a chapter in the manual about how to add variables to the internal database - but this is not required to do this, RPN scripts always work)
But seeing that you were testing the script already, why not just assign that to your button and be done with it?

Furthermore, you cannot rely on what is shown in the event view. That is only (part of) the result of the action, not the trigger itself. Dozens of lines of code could have been triggered in the background. 

Aircraft like the 146 are indeed " a new ball game", because every aircraft developer does things differently. It is an endless vicious cycle of hunting for the correct ways to operate things in the cockpit - or if that is possible at all. RPN scripting is a must in most cases. If I'm not mistaken there are script collections available on the "dot to" site for AAO and the 146, maybe there is something in there for you. A StreamDeck profile will usually contain a collection of scripts too, so look for those if there is nothing else - you don't have to own a StreamDeck to import the scripts)

The situation will remain like this until the developers find it in their collective hearts to add some documentation to their product of how we are supposed to operate all the knobs and switches from the outside.
 

Edited June 5, 20224 yr by Lorby_SI

@Lorby_SI 

I was coming to the conclusion that I would have to go down the RPN scripting route.

Thanks for your explanations and suggestions.

Steve

I successfully binded the autopilot functions to my MCP combo II hardware with most of the default autopilot control key assignment in AAO.

There is also, as said by Lorby a profile for Streamdeck in "dot to" here

in which, there is xml script to import with a lot of commands

Pascal

On 6/5/2022 at 10:28 AM, Lorby_SI said:

A StreamDeck profile will usually contain a collection of scripts too, so look for those if there is nothing else - you don't have to own a StreamDeck to import the scripts)

Probably a stupid question but what software would I "import" the StreamDeck profile to ?

Steve

1 hour ago, rC10B said:

Probably a stupid question but what software would I "import" the StreamDeck profile to ?

Steve

The StreamDeck profile file itself doesn't concern you. It is the XML file with AAO scripts that you want, and you import that into AAO. If the author made one, that is.

Edited June 7, 20223 yr by Lorby_SI

On 6/6/2022 at 4:38 PM, Cool said:

I successfully binded the autopilot functions to my MCP combo II hardware with most of the default autopilot control key assignment in AAO.

There is also, as said by Lorby a profile for Streamdeck in "dot to" here

in which, there is xml script to import with a lot of commands

Pascal

I downloaded your scripts and they are amazing, however I do not see the AP functions you spoke of.  Things like ALT ARM and other things on the mode control panel.  What am I missing?