FlyByWire A320 in AAO: All A:A32NX_AUTOPILOT_ACTIVE Zero

[Lawnsen 0]

Hey,

I am right now working on lighting up my LEDs on the xTouch Mini with the fbw a320 - and therefore reading A:Simvars like (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, Bool) or (a:A32NX_AUTOPILOT_ACTIVE, Bool) and many others.

So, for e.g. the Baro reference I get values but the aforementioned variables ALWAYS deliver 0. (The LS, LOC etc, too)

I am able to send commands to the simulator as well as read some specific values, yet, the fcu-stuff does not change nor deliver any value > 0.

Is there any precondition I am missing? Anything that has to be done to make these values work?

TY in advance!

[Lorby_SI 2,108]

2 hours ago, Lawnsen said:

a:A32NX_AUTOPILOT_ACTIVE

This is wrong.

A: (aircraft) variables are those from the MSFS SDK - excusively. There is nothing aircraft specific among them - ever.

All the A32NX stuff are most likely LVars. Which you can read from the Sim in the Scripting menu.

Try:

(L:A32NX_AUTOPILOT_ACTIVE, Number)

All variable names are case sensitive and spaces must be set correctly too.

Make sure to read up on variables in MSFS, there are many different types.

Edited September 16, 2023 by Lorby_SI

[Lawnsen 0]

Ah thank you, that solved most of the problems, yet, the flight director status is still not readable though I tried K: and L: ...

But thx anyways!

[Lorby_SI 2,108]

5 hours ago, Lawnsen said:

yet, the flight director status is still not readable though I tried K: and L: ...

K: are events, not variables. You cannot read anything from them.

"trying" IMHO is a complete waste of time. You need to do research first, for example in the MSFS SDK documentation. Or ask the aircraft developer what variable name and type is required for a certain component. They can do pretty much whatever they want, they just invent their own variables (the LVArs)

Simulation Variables (flightsimulator.com)

Edited September 17, 2023 by Lorby_SI

[Lorby_SI 2,108]

I just checked, FBW was using the default variable in the past. Maybe it is still the same:

(A:AUTOPILOT FLIGHT DIRECTOR ACTIVE:1, Bool)

This is an indexed variable, as there is more than one FD status. Unfortunately Asobo doesn't say that in the SDK doc 😞

Edited September 17, 2023 by Lorby_SI

[Lawnsen 0]

Ah that was the final hint - PLUS, I just saw it in this neato introduction for the xTouch Mini:

https://www.flusi.info/index.php?attachment/45878-xtouchgauge-documentation-pdf/

Thank you for your support!