Hi,

I have about 70% of the FBW A32NX FCU now working with the X-Touch Dials and button assignments.

The 'Mode' and 'Range' dials on the A320 (I am using the flybywire version) are unique in that they do not have increment/decrement triggers but are an incremental number from 1 to 5 I believe.

How do I script this against each rotary increment and decrement assignment using RPN if, else statements?

The script for these buttons looks like this:

:Rotary_2_Left
0 (>AIRLINER_ND_MAP_MODE_CPT) (END)

:Rotary_2_Right
1 (>AIRLINER_ND_MAP_MODE_CPT) (END)

:Rotary_3_Left
0 (>AIRLINER_ND_MAP_RANGE_CPT) (END)

:Rotary_3_Right
1 (>AIRLINER_ND_MAP_RANGE_CPT) (END)

Instead of 0 for decrement, I want it to be the value of the mode/range dial minus 1 unless the dial is at 0.

Instead of 1 for increment, I want it to be the value of the mode/range dial plus 1 unless the dial is at 5.

I have found scripts that do this already but I am trying to get this working inside my own templates and scripts which I want to develop further over time.

Those scripts aren't for/from AAO, right? They aren't really proper RPN code, the variable is missing the type and the Unit. I also don't recognize the name, the LVars that I know are different.

Anyway. There are two ways of doing this. 

1. As an Axis:
Assign the XT rotary encoder as an axis in AAO
set
Axis min to 0
Axis max to 4
Rounding to int
put "L:A32NX_EFIS_L_ND_MODE, Number" into the box where it says "Enter Variable".

or
Axis min to 0
Axis max to 5
Rounding to int
put "L:A32NX_EFIS_L_ND_RANGE, Number" into the box where it says "Enter Variable".

 

2. For INC/DEC action you have to create scripts:

Mode
INC
(L:A32NX_EFIS_L_ND_MODE,·Number)·1·+·4·min·(>L:A32NX_EFIS_L_ND_MODE,·Number)

DEC
(L:A32NX_EFIS_L_ND_MODE,·Number)·1·-·0·max·(>L:A32NX_EFIS_L_ND_MODE,·Number)

Range:
INC
(L:A32NX_EFIS_L_ND_RANGE,·Number)·1·+·5·min·(>L:A32NX_EFIS_L_ND_RANGE,·Number)

DEC
(L:A32NX_EFIS_L_ND_RANGE,·Number)·1·-·0·max·(>L:A32NX_EFIS_L_ND_MODE,·Number)

 

There are ready made scripts, and I think a template for the XT too, on flightsim.to
Like these:
AAO Axis and Ohs Template For X-Touch Mini A32NX [WIP] for Microsoft Flight Simulator | MSFS
XTouch mini AAO template for A320FCU for Microsoft Flight Simulator | MSFS
But look around, I don't keep track of them and don't know how current they are. Just looking around now.

You can also use scripts that are part of another package, like for the StreamDeck. Scripts aren't hardware specific.

And not to forget this very helpful piece of kit:
X-Touch Mini Gauge for use with AAO (Axis and Ohs) for Microsoft Flight Simulator | MSFS

Edited July 22, 20241 yr by Lorby_SI

I tried the axis and the script options for ND_MODE and neither are responding.

I have been going around in circles with this. I have all my other GA aircraft working well with AAO/XTouch.

Its just the A320 I am having issues with. Standard functions like (Barometer aka KOHLSMAN) are working as direct mappings to X-touch dials or as scripts. No issue.

FCU specific stuff is simply not working at all with L: assignments or downloaded scripts (as you suggested - I have tried 3 or 4 different ones).

For example if we look at ND Mode:

As an axis, if I assign:

L:A32NX_EFIS_L_ND_MODE, Number where it says 'Enter Variable' NOTHING HAPPENS.

If instead I directly select this event to the axis:

AIRLINER_ND_MAP_MODE_CPT! 1 (>IE:) 

THE ROTARY WORKS!

I want to use the more comprehensive X-Touch Gauge scripts out there but they all use L: assignments to perform their functions and these are not working for me at present.

Any help appreciated as this is driving me mad! If I can simply get the mode, range, speed and altitude working, I am sure I can do all the rest of the functions using modified scripts if necessary.

I just wanted to double check. That when you import scripts (like the Streamdeck A32NX scripts that support the streamdeck profiles), that, as long as they are visible in the script editor, you should be able to call them without any additional steps.

I have scripts visible that I have imported in their own managed groups and I have attempted to call them with <Group Name>-<Script Name> with a K> Assignment without success for the A320 FCU functions. These include Funatics, Silver Surfer and others.

4 hours ago, PrivatePilotC172 said:

I have attempted to call them with <Group Name>-<Script Name> with a K> Assignment without success for the A320 FCU functions.

Then you are doing something wrong. Can you post a screenshot or the actual code that you were using?

Yes I was doing something wrong. But not AAO at all!

I have checked and double checked all the scripts both on the AAO (RPN) side and on the XTouch Gauge side and all were correct with the functions I was calling in my script library.

The reason the Funatic/Other scripts were not calling was frankly ridiculous. I was in the wrong A320 Neo.

I have been using the A320 Neo V2 mistakenly believing this the the FBW version.

This all relates back to moving my community/official directories (and their content) to a new SSD (F:Drive).

For some reason four folders remained and the recently installed DEV edition of FBW320 was one of them.

Its all working now. I have been able to blend scripts from Funatic and others to extend the XTouch template to 8 pages; when I have this all working well I will share it.

The ONLY issue I have now is with the XTouch Gauge resolution in VR. Its too small. I have seen the workaround (adding a 3X Zoom) to the each X-Touch Gauge screen but this has not worked for me yet.

Thanks for all your help Lorby and thanks for telling me I was doing something wrong. Better to figure this stuff out. I now have 5 GA aircraft, A Hawk T1, A TBM930, and the FBWA320 working as intended with AAO/XTouch. I can now practice IFR procedures with the degree of immersion I need.

Now to figure out how to achieve Reverse Thrust with the Trustmaster Warthog Quadrant Detent. God help me!

I guess this cycle may all start again when I upgrade to MSFS 2024 😉