GNS Other Behavior Options

The GNS 430/530 package also provides additional behaviour options to be set to customize behavior for differing plane configurations. These can be customized by adding new tags to the <Instrument> configuration in your panel.xml file. These options are primarily used to allow for interactions between the GNS and other instruments

Please note the standard, default behavior of the GNS:

By default, the instrument will use an empty string '' for the flight planner ID. To specify which ID to use, use the <FlightPlannerId> tag. If two GNS units share the same flight planner ID, then their flight plans will be synced with each other, simulating automatic crossfill between the units.

By default, the instrument will consider its FMS to be primary if it is the primary instrument. To specify whether it is the primary FMS, use the <IsFMSPrimary> tag. There must be exactly one primary FMS instance per flight planner ID. Therefore, if two GNS units share the same flight planner ID, then one unit should be configured for a primary FMS and the other should be configured for a non-primary FMS. If two GNS units have separate flight planner IDs, then both units should be configured for a primary FMS.

By default, LNAV will use index 0. To specify which LNAV index to use, use the <LNavIndex> tag. Two GNS units can have the same LNAV index if and only if they have the same flight planner ID.

By default, VNAV will use index 0. To specify which VNAV index to use, use the <VNavIndex> tag. Two GNS units can have the same VNAV index if and only if they have the same flight planner ID.

The following is a sample instrument config block that changes all these settings from the default using the tags described above:

<Instrument>
  <Name>AS530</Name>
  <FlightPlannerId>GNS</FlightPlannerId>
  <IsFMSPrimary>True</IsFMSPrimary>
  <LNavIndex>2</LNavIndex>
  <VNavIndex>2</VNavIndex>
</Instrument>

Any or all of these can be used as appropriate.