Skip to content

ATR variables and events #49

@gizmo71

Description

@gizmo71

L:MSATR_FGCP_SELALT is presumably a way to read the selected altitude.

The profile I've seen suggests that L:MSATR_FGCP_TGT_DELTA should work the same for speed, though it didn't seem to, at least on the ground. The profile shows A:AUTOPILOT AIRSPEED HOLD VAR with units knot as how to read it; this may correspond to a scaled version of some other LVar.

If the autopilot doesn't respond to standard events (another profile suggests that (>K:AP_MASTER) works), you can toggle it via L:MSATR_FGCP_AP. I think L:MSATR_FGCP_STAT_AP gives its state, though we don't show that anywhere.

You can press the Yaw Damper button by setting L:MSATR_FGCP_YD - presumably it resets after the state changes. The current state is probably L:MSATR_FGCP_STAT_YD.

Similarly, the FD1 state can be ready with L:MSATR_FGCP_STAT_FD1.

They've mapped MSATR_FGCP_STAT_MAN_SPD to the speed dot (i.e. managed speed). Does putting 1 in L:MSATR_FGCP_SPEED_TGT_SEL reliably set managed speed regardless of the current mode?

What is L:MSATR_FGCP_STAT_NAV equivalent to? Managed Nav?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions