# Panel XML Properties<no value>
The `panel.xml` file is a configuration file for the virtual cockpit gauges and glasscockpits that are loaded as part of the instrumentation of an aircraft, and it may also be used to configure certain properties of [Electronic Flightbag](../../../../programming-apis/efb/electronic-flight-bag-api/) apps. In general, most of the elements used in this file are *custom* elements that you define and then retrieved in your gauge [JavaScript](../../../../programming-apis/javascript/javascript/) code, and you can also use some of the elements that the SDK has defined in the JS files included for the Microsoft Flight Simulator 2024 aircraft.

{{< callout context="note" title="NOTE" icon="outline/bulb" >}}

This file is only used by JavaScript instruments, and is **not** used by [WebAssembly](../../../../programming-apis/wasm/webassembly/) instruments.

{{< /callout >}}

 

This file is well suited to making variations of your glass-cockpit depending on the aircraft that will be using it, although it should be noted that it is absolutely *optional* and many aircraft never have any need for this XML file. It is worth noting that there is only ever **one** `panel.xml` file for any single aircraft, and it can - and usually does - contain data and logic for multiple instruments.

 

When creating the `panel.xml` file, it should have the following structure:

``` xml
<PlaneHTMLConfig>
    
    <Instrument>
        </Instrument>
    
    <Annunciations>
        </Annunciations>
    
    <VoicesAlerts>
        </VoicesAlerts>
    
    <EngineDisplay>
        </EngineDisplay>
    
    <EFB>
        </EFB>
    
    <FlightPerformance>
        <FlightPerformance>
</PlaneHTMLConfig>
```

 

All `panel.xml` files must have the `<PlaneHTMLConfig>` element at the top level, but the other internal elements to that are all *optional* and will be included or not depending on the requirements for the instruments being defined.

{{< callout context="note" title="NOTE" icon="outline/bulb" >}}

You can find a full example of a JavaScript instrument that includes use of the `panel.xml` file here - [Simple JavaScript Instrument Example](../../../../programming-apis/javascript/javascript/#example)

{{< /callout >}}

 

It should be noted that in many places you can supply [Simulation Variables](../../../../programming-apis/simvars/simulation-variables/) to be used in the different XML elements and element attributes. These may require "indices" to target a specific aircraft component, and for all Microsoft Flight Simulator 2024 this is supplied using a *name* string, as shown in the accompanying element code examples (for more information please see here: [Using Indexed Parameter Names](../../../../programming-apis/simvars/simulation-variables/#h1)).

 

Finally, there are additional XML elements and attributes that are common to all SimObject XML files which can be used in the panel XML. These are all related to the modular SimObject [Merge Process](../../modular-simobject-merging/), and can be ignored if the SimObject is not modular. You can find these elements and attributes here:

-   [Modular SimObject XML Properties](../../modular-simobject-xml-properties/)

 

 

### &lt;PlaneHTMLConfig&gt;

This is the top-level container for all the different `panel.xml` sections. All `panel.xml` files *must* have this at the top and everything else goes within the open/close `<PlaneHTMLConfig>` tags.

 

 

### &lt;[CUSTOM]&gt;

A "custom" element is a special element that can be named as you require - for example, the following would all be valid custom element definitions: `<ScreenMode>`, `<RadarAltitude>` or `<Opacity>`. The value you then place within the element can be read **as a string** by the JavaScript for the gauge (this includes the values `True` and `False`) using the `parseXMLConfig()` method. Note that you may use the `<Simvar />` element or [Panel XML Logic Elements](panel-xml-logic-elements/) to define the value of the custom element instead of assigning it a fixed value or string. This SimVar can be read on the JavaScript side with a `CompositeLogicXMLElement`, which allows you to use a `getValueAsNumber()` method instead of a string.

 

Below is an example of an instrument that uses a few custom elements for parsing in the gauge JS file:

``` xml
<PlaneHTMLConfig>
    <Instrument>
        <Name>ASVigilus</Name>
        <RightFuelName>Aux</RightFuelName>
        <RightFuelQuantity>
            <Simvar name="FUEL TANK CENTER2 QUANTITY" unit="gallon"/>
        </RightFuelQuantity>
        <RightFuelCapacity>
            <Simvar name="FUEL TANK CENTER2 CAPACITY" unit="gallon"/>
        </RightFuelCapacity>
    </Instrument>
</PlaneHTMLConfig>
```

In this example, three custom elements are defined and two of them use the `<Simvar />` sub element to create their value.

 

 

### &lt;Instrument&gt;

The instrument element is used to define the values and electric component logic for a virtual cockpit instrument. It has no attributes and can contain the following sub-elements:

1.  `<Name>`
2.  `<Electric>`
3.  `<AlwaysUpdate>`
4.  `<SkipValidationAfterInit>`
5.  `<HighlightBackgroundOpacity>`
6.  `<[CUSTOM]>`

Note you can have as many instrument element definitions as you have virtual cockpit gauges in the aircraft.

 

 

#### &lt;Name&gt;

The name element is where you give the `templateID` as defined in your glass-cockpit main class.

 

 

#### &lt;Electric&gt;

Inside this element you can define your the logic of the electrical system associated with the virtual cockpit instrument being defined. Usually the electrical behavior of your glass-cockpit is defined by several combinations of switches (**Battery**, **Avionics** and **Breakers**, for example) so you can define a set of SimVars here (using the `<Simvar />` sub-element) that link the instrument to these switches.

 

This element has no attributes and is a sub-element of `<Instrument>`. Below is an example of an instrument with the electrical system setup:

``` xml
<PlaneHTMLConfig>
    <Instrument>
        <Name>AS1000_PFD</Name>
        <SyntheticVision>True</SyntheticVision>
        <RadarAltitude>True</RadarAltitude>
        <Electric>
            <Or>
                <Simvar name="CIRCUIT ON:'Main'_n" unit="Boolean"/>
                <Simvar name="CIRCUIT ON:'Backup'_n" unit="Boolean"/>
            </Or>
        </Electric>
    </Instrument>
</PlaneHTMLConfig>
```

In this example, if either Circuit 28 *or* Circuit 29 is **ON**, then the electrical system for the gauge will be turned on.

 

It is important to note that you may use many of the [Panel XML Logic Elements](panel-xml-logic-elements/) - like `<And>`, `<GreaterEqual>`, `<Subtract>`, etc... - along with the `<Simvar />` sub element within the `<Electric>` element to define the conditions under which the electrical system will operate.

 

 

#### &lt;AlwaysUpdate&gt;

Within the simulation menu settings there is an option to set the refresh rate of glass-cockpit displays. When this element is included and set to *true*, the instrument will use the full refresh rate, regardless of the setting.

``` xml
 <Instrument>
     <Name>A320_Neo_CDU</Name>
     <Electric>
         <Simvar name="CIRCUIT ON:'Main'_n" unit="Boolean"/>
     </Electric>
     <AlwaysUpdate>True</AlwaysUpdate>
 </Instrument>
```

 

 

#### &lt;SkipValidationAfterInit&gt;

Glass-cockpit displays can have five "states", which are (in order): Off, Init, WaitingValidation, On, and Reversionary. Now, some glasscockpits will need user input - for example, a button press - to go from the *Init* stage to the *On* stage, and will be in the intermediate *WaitingValidation* stage until that happens. However, this may not always be the case, and so you can specify this element and set it to *true* to skip directly from *Init* to *On*.

``` xml
<Instrument>
    <Name>AS1000_MFD</Name>
    <SkipValidationAfterInit>True</SkipValidationAfterInit>
    <Electric>
        <Simvar name="CIRCUIT ON:'Main'_n" unit="Boolean"/>
    </Electric>
</Instrument>
```

 

 

#### &lt;HighlightBackgroundOpacity&gt;

For checklist purposes, parts of the glass-cockpit can be highlighted by reducing the opacity of the rest of the screen around it. For that to happen, you need to include this element and set the opacity level of the background from 0.0 to 1.0.

``` xml
 <Instrument>
     <Name>AS_EPM</Name>
     <Electric>
         <Simvar name="CIRCUIT GENERAL PANEL ON" unit="Boolean"/>
     </Electric>
     <HighlightBackgroundOpacity>0.3</HighlightBackgroundOpacity>
 </Instrument>
```

 

 

### &lt;Annunciations&gt;

This element is used to define the list of all messages that can displayed in the warning area of compatible instruments (eg the G1000, an airliners EICAS screen, etc...). This element has no attributes and is a container for one or more `<Annunciation>` elements. The following example creates an annunciation "warning" event for when the main bus voltage is equal to or less than 25.5:

``` xml
<PlaneHTMLConfig>
    <Annunciation>
        <Type>Warning</Type>
        <Text>LOW VOLTS</Text>
        <Condition>
            <LowerEqual>
                <Simvar name="ELECTRICAL MAIN BUS VOLTAGE:'Main_Bus'_n" unit="volts"/>
                <Constant>25.5</Constant>
            </LowerEqual>
        </Condition>
    </Annunciation>
</PlaneHTMLConfig>
```

 

 

#### &lt;Annunciation&gt;

This is a container element for the logic and text related to a single annunciation. It is a sub-element of `<Annunciations>`, has no attributes, and can contain the following sub-elements:

1.  `<Type>`
2.  `<Text>`
3.  `<Condition>`

You may have multiple `<Annunciation>` elements in a file.

 

 

#### &lt;Type&gt;

This specifies the type of annunciation that is being defined, which can be one of the following:

-   **Warning** - This is a serious issue that needs resolving
-   **Caution** - This is a minor issue that you should be aware of and try to resolve
-   **Advisory** - This is a recommendation that something may be wrong and should be checked

The element has no attributes and is a sub-element of `<Annunciations>`.

 

 

#### &lt;Text&gt;

This specifies the text that should be displayed when the annunciation conditions have been met. The element has no attributes and is a sub-element of `<Annunciations>`.

 

 

### &lt;VoicesAlerts&gt;

This is a container element for the logic related to alerts for those aircraft instruments that support the voice alerting system (for example, the G1000, airliner EICAS screens, etc...). This element has no attributes and is a container for one or more `<Alert>` elements. The following example creates a voice alert event for when the `STALL WARNING` SimVar is "True":

``` xml
<VoicesAlerts>        
    <Alert>
        <Type>Warning</Type>
        <ShortText>PULL UP</ShortText>
        <LongText>PULL UP</LongText>
        <SoundEvent>aural_pull_up</SoundEvent>
        <Condition>
            <And>
                <LinearMultiPoint>
                    <Table>
                        <ReferencePoints>1160,2320,4930,12000</ReferencePoints>
                        <Maximums>0,1070,2380,4285</Maximums>
                    </Table>
                    <Param>
                        <Multiply>
                            <Simvar name="VERTICAL SPEED" unit="feet per minute"/>
                            <Constant>-1</Constant>
                        </Multiply>
                    </Param>
                    <Param>
                        <Simvar name="PLANE ALT ABOVE GROUND" unit="feet"/>
                    </Param>
                </LinearMultiPoint>
                <Not>
                    <Simvar name="SIM ON GROUND" unit="bool"/>
                </Not>
            </And>
        </Condition>
    </Alert>
</VoicesAlerts>
```

 

 

#### &lt;Alert&gt;

This is a sub-element of `<VoicesAlerts>`, has no attributes, and can contain the following sub-elements:

1.  `<Type>`
2.  `<ShortText>`
3.  `<LongText>`
4.  `<SoundEvent>`
5.  `<Condition>`

You may have multiple `<Alert>` elements in a file.

 

 

#### &lt;Type&gt;

This is a sub-element of `<Alert>`, and has no attributes. It is used to define the type of alert that is being triggered, and can be one of the following:

-   **Warning**: This is a serious warning that something is wrong. This type usually requires a `<ShortText>` element and a `<LongText>` element as well.
-   **Caution**: This is a caution that something may be wrong. This type usually requires a `<ShortText>` element and a `<LongText>` element as well.
-   **SoundOnly**: This is an alert that is sound only and doesn't use the `<ShortText>` element nor the `<LongText>` element.
-   **Test**: This is a test alert, and is usually accompanied by a `<ShortText>` element.

 

 

#### &lt;ShortText&gt;

The warning message as a short-form string.

 

 

#### &lt;LongText&gt;

The warning message as a long-form (more explicit) string.

 

 

#### &lt;SoundEvent&gt;

This element is used to specify the Wwise Event that should be associated with the alert being created. The event name used here should match the WwiseEvent attribute that has been set in the `<Sound>` element of the `<AvionicSounds>` container in the [sound.xml](../../../sounds/sound-xml/) file. See the [Avionic Sounds Example](../../../sounds/sound-xml-examples/#h8) for an example of use.

 

 

#### &lt;Once&gt;

This is a sub-element of `<Alert>`, and has no attributes. When set to "True" it tells the panel logic that this alert should only be played once, for example:

``` xml
<Alert>
    <Type>SoundOnly</Type>
    <SoundEvent>aural_taws_system_test_ok</SoundEvent>
    <Condition>
        <And>
            <Greater>
                <TimeSinceStart/>
                <Constant>30000</Constant>
            </Greater>
        <InstrumentWasOff/>
        </And>
    </Condition>
    <Once>True</Once>
</Alert>
```

 

 

### &lt;EngineDisplay&gt;

The `<EngineDisplay>` element is a container element that can hold one or more `<Gauge>` and/or `<Text>` elements, as well as define `<Function>` elements for later use. This container has no attributes and it is used to help with the styling of the instruments that are linked to the operation of the engine, linking the styles to specific values derived from conditions, values or SimVars. This element is mostly used in the G1000, G3000, G3X and G3X Touch displays, but can be applied to most glasscockpits.

``` xml
<EngineDisplay>
    <Gauge>
        <Type>Horizontal</Type>
        <ID>FuelPress_Gauge</ID>
        <Title>FUEL</Title>
        <Unit>PSI</Unit>
        <Minimum>0</Minimum>
        <Maximum>10</Maximum>
        <Style>
            <ValuePos>End</ValuePos>
        </Style>
        <Value>
            <Simvar name="GENERAL ENG FUEL PRESSURE:1" unit="psi"/>
        </Value>
        <BeginText></BeginText>
        <EndText></EndText>
   </Gauge>
   <Text>
       <Left>CHT °F</Left>
       <Right id="CHT">
           <ToFixed precision="0">
               <Simvar name="ENG CYLINDER HEAD TEMPERATURE:1" unit="farenheit"/>
            </ToFixed>
        </Right>
    </Text>
</EngineDisplay>
```

 

 

### &lt;Gauge&gt;

This is an element that belongs in the `<EngineDisplay>` or `<Column>` container element, and you can have multiple of these in the `panel.xml` file. This element has no attributes and can contain the following sub-elements:

1.  `<Type>`
2.  `<ID>`
3.  `<Title>`
4.  `<Unit>`
5.  `<Minimum>`
6.  `<Maximum>`
7.  `<Style>`
8.  `<Value>`
9.  `<Value2>`
10. `<ColorZone>`
11. `<ColorLine>`
12. `<ReferenceBug>`
13. `<RedBlink>`
14. `<GraduationLength>`
15. `<GraduationTextLength>`
16. `<BeginText>`
17. `<EndText>`
18. `<CursorText>`
19. `<CursorText2>`

 

The `<Gauge>` element is used to customise some of the default glass-cockpit gauges available to developers for inclusion in their own displays. Customisation is done by first selecting the `<Type>` of gauge to be created, then defining the `<Style>` of the gauge, and then finally refining the way the gauge will be displayed using text and other elements. The current value that the gauge will be using for the display is defined using the `<Value>` element (and sometimes the `<Value2>` element too, depending on instrument `<Type>`), which can use many of the [Panel XML Logic Elements](panel-xml-logic-elements/) - like `<And>`, `<Or>`, `<Lower>`, `<GreaterEqual>`, etc... - along with the `<Simvar />` element or [Unique Logic Elements](panel-xml-logic-elements/#unique) to extract the required information from the simulation for the gauge.

 

The example below shows a full and complex implementation of this element:

``` xml
<Gauge>
    <Type>DoubleVertical</Type>
    <Style>
        <Height>70</Height>
        <TextIncrement>1</TextIncrement>
    </Style>
    <ID>Piston_LoadGauge</ID>
    <Title>LOAD</Title>
    <Unit></Unit>
    <Minimum>0</Minimum>
    <Maximum>100</Maximum>
    <Value>
        <Max>
            <Min>
                <Multiply>
                    
                        <Multiply>
                            <Simvar name="ENG TORQUE:1" unit="Foot pounds"/>
                            
                                <Simvar name="GENERAL ENG RPM:1" unit="rpm"/>
                                <Constant>5252</Constant>
                            
                            <Constant>550</Constant>
                        </Multiply>
                        
                            <Gamevar name="AIRCRAFT MAX RATED HP" unit="ft lb per second"/>
                            <Simvar name="NUMBER OF ENGINES" unit="number"/>
                        
                    
                    <Constant>100</Constant>
                </Multiply>
                <Constant>100</Constant>
            </Min>
            <Constant>0</Constant>
        </Max>
    </Value>
    <Value2>
        <Max>
            <Min>
                <Multiply>
                    
                        <Multiply>
                            <Simvar name="ENG TORQUE:2" unit="Foot pounds"/>
                            
                                <Simvar name="GENERAL ENG RPM:2" unit="rpm"/>
                                <Constant>5252</Constant>
                            
                            <Constant>550</Constant>
                        </Multiply>
                        
                            <Gamevar name="AIRCRAFT MAX RATED HP" unit="ft lb per second"/>
                            <Simvar name="NUMBER OF ENGINES" unit="number"/>
                        
                    
                    <Constant>100</Constant>
                </Multiply>
                <Constant>100</Constant>
            </Min>
            <Constant>0</Constant>
        </Max>
    </Value2>
    <ColorZone>
        <Color>yellow</Color>
        <Begin>95</Begin>
        <End>100</End>
    </ColorZone>
    <ColorZone>
        <Color>green</Color>
        <Begin>0</Begin>
        <End>95</End>
    </ColorZone>
    <GraduationLength text="True">20</GraduationLength>
    <BeginText>%</BeginText>
</Gauge>
```

 

 

#### &lt;Type&gt;

This element specifies the type of gauge data being generated and is a sub-element of `<Gauge>`. It has no attributes, and can only contain one of the following defining strings:

 

<table><thead><tr class="header"><th>String</th><th>Description</th><th>Example</th></tr></thead><tbody><tr class="odd"><td>Circular</td><td><p>Defines a circular instrument with a cursor showing a single value.. The value the instrument cursor will be set to is defined using the logic contained in the the <code>&lt;Value&gt;</code> element. This type can also use the following main elements:</p><ol><li><code>&lt;Title&gt;</code></li><li><code>&lt;Unit&gt;</code></li><li><code>&lt;Minimum&gt;</code></li><li><code>&lt;Maximum&gt;</code></li><li><code>&lt;ColorZone&gt;</code></li><li><code>&lt;ColorLine&gt;</code></li><li><code>&lt;ReferenceBug&gt;</code></li><li><code>&lt;RedBlink&gt;</code></li><li><code>&lt;GraduationLength&gt;</code></li><li><code>&lt;GraduationTextLength&gt;</code></li><li><code>&lt;BeginText&gt;</code></li><li><code>&lt;EndText&gt;</code></li></ol><p>It can also use the following <code>&lt;Style&gt;</code> sub-elements:</p><ol><li><code>&lt;ValuePos&gt;</code></li><li><code>&lt;BeginAngle&gt;</code></li><li><code>&lt;EndAngle&gt;</code></li><li><code>&lt;CursorType&gt;</code></li><li><code>&lt;TextIncrement&gt;</code></li><li><code>&lt;ForceTextColor&gt;</code></li><li><code>&lt;FontSize&gt;</code></li></ol></td><td><img src="images/5_Content_Config/Instruments/panel_xml_2_circle.png" title="Example Of A Circular Instrument" alt="Example Of A Circular Instrument" /></td></tr><tr class="even"><td>Horizontal</td><td><p>Defines a single horizontal "bar" instrument with a cursor showing a single value. This type can also use the following main elements:</p><ol><li><code>&lt;Title&gt;</code></li><li><code>&lt;Unit&gt;</code></li><li><code>&lt;Minimum&gt;</code></li><li><code>&lt;Maximum&gt;</code></li><li><code>&lt;ColorZone&gt;</code></li><li><code>&lt;ColorLine&gt;</code></li><li><code>&lt;RedBlink&gt;</code></li><li><code>&lt;GraduationLength&gt;</code></li><li><code>&lt;GraduationTextLength&gt;</code></li><li><code>&lt;BeginText&gt;</code></li><li><code>&lt;EndText&gt;</code></li><li><code>&lt;CursorText&gt;</code></li></ol><p>It can also use the following <code>&lt;Style&gt;</code> sub-elements:</p><ol><li><code>&lt;ValuePos&gt;</code></li><li><code>&lt;TextIncrement&gt;</code></li><li><code>&lt;CursorColor&gt;</code></li><li><code>&lt;CursorStyle&gt;</code></li><li><code>&lt;Width&gt;</code></li><li><code>&lt;ValuePrecision&gt;</code></li><li><code>&lt;ReverseY&gt;</code></li><li><code>&lt;StrokeWidth&gt;</code></li><li><code>&lt;FontSize&gt;</code></li></ol><p>The value the instrument will display is defined using the logic contained in the the <code>&lt;Value&gt;</code> element.</p></td><td><img src="images/5_Content_Config/Instruments/panel_xml_3_horz.png" title="Example Of A Horizontal Instrument" alt="Example Of A Horizontal Instrument" /></td></tr><tr class="odd"><td>DoubleHorizontal</td><td><p>Defines an instrument with a single horizontal "bars" and a double cursor, each of which can show a different value. The values the instrument will display are defined using the logic contained in the the <code>&lt;Value&gt;</code> element (for the top bar) and the <code>&lt;Value2&gt;</code> element (for the bottom bar). This type can also use the following main elements:</p><ol><li><code>&lt;Title&gt;</code></li><li><code>&lt;Unit&gt;</code></li><li><code>&lt;Minimum&gt;</code></li><li><code>&lt;Maximum&gt;</code></li><li><code>&lt;ColorZone&gt;</code></li><li><code>&lt;ColorLine&gt;</code></li><li><code>&lt;RedBlink&gt;</code></li><li><code>&lt;GraduationLength&gt;</code></li><li><code>&lt;GraduationTextLength&gt;</code></li><li><code>&lt;BeginText&gt;</code></li><li><code>&lt;EndText&gt;</code></li><li><code>&lt;CursorText&gt;</code></li><li><code>&lt;CursorText2&gt;</code></li></ol><p>It can also use the following <code>&lt;Style&gt;</code> sub-elements:</p><ol><li><code>&lt;ValuePos&gt;</code></li><li><code>&lt;TextIncrement&gt;</code></li><li><code>&lt;ValuePrecision&gt;</code></li></ol></td><td><img src="images/5_Content_Config/Instruments/panel_xml_4_dhorz.png" title="Example Of A Double Horizontal Instrument" alt="Example Of A Double Horizontal Instrument" /></td></tr><tr class="even"><td>Vertical</td><td><p>Defines a single vertical "bar" instrument with a cursor showing a single value. The value the instrument will display is defined using the logic contained in the the <code>&lt;Value&gt;</code> element. This type can also use the following main elements:</p><ol><li><code>&lt;Title&gt;</code></li><li><code>&lt;Unit&gt;</code></li><li><code>&lt;Minimum&gt;</code></li><li><code>&lt;Maximum&gt;</code></li><li><code>&lt;ColorZone&gt;</code></li><li><code>&lt;ColorLine&gt;</code></li><li><code>&lt;RedBlink&gt;</code></li><li><code>&lt;GraduationLength&gt;</code></li><li><code>&lt;GraduationTextLength&gt;</code></li><li><code>&lt;BeginText&gt;</code></li><li><code>&lt;EndText&gt;</code></li></ol><p>It can also use the following <code>&lt;Style&gt;</code> sub-elements:</p><ol><li><code>&lt;ValuePos&gt;</code></li><li><code>&lt;CursorColor&gt;</code></li><li><code>&lt;TextIncrement&gt;</code></li></ol></td><td><img src="images/5_Content_Config/Instruments/panel_xml_5_vert.png" title="Example Of A Vertical Instrument" alt="Example Of A Vertical Instrument" /></td></tr><tr class="odd"><td>DoubleVertical</td><td><p>Defines an instrument with two vertical "bars" and a double cursor, each of which can show a different value. The values the instrument will display are defined using the logic contained in the the <code>&lt;Value&gt;</code> element (for the left bar) and the <code>&lt;Value2&gt;</code> element (for the right bar). This type can also use the following main elements:</p><ol><li><code>&lt;Title&gt;</code></li><li><code>&lt;Unit&gt;</code></li><li><code>&lt;Minimum&gt;</code></li><li><code>&lt;Maximum&gt;</code></li><li><code>&lt;ColorZone&gt;</code></li><li><code>&lt;ColorLine&gt;</code></li><li><code>&lt;RedBlink&gt;</code></li><li><code>&lt;GraduationLength&gt;</code></li><li><code>&lt;GraduationTextLength&gt;</code></li><li><code>&lt;BeginText&gt;</code></li><li><code>&lt;EndText&gt;</code></li></ol><p>It can also use the following <code>&lt;Style&gt;</code> sub-elements:</p><ol><li><code>&lt;TextIncrement&gt;</code></li><li><code>&lt;Height&gt;</code></li><li><code>&lt;ValuePrecision&gt;</code></li></ol></td><td><img src="images/5_Content_Config/Instruments/panel_xml_6_dvert.png" title="Example Of A Double Vertical Instrument" alt="Example Of A Double Vertical Instrument" /></td></tr><tr class="even"><td>Flaps</td><td>Defines an instrument that displays the flaps position. This instrument requires a <code>&lt;Value&gt;</code> and you can optionally use the <code>&lt;TakeOff&gt;</code> element to give the position of the T/O indicator, and also give it a <code>&lt;Title&gt;</code> and <code>&lt;ID&gt;</code>.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_10_flaps.png" title="Example Of The Flaps Instrument" alt="Example Of The Flaps Instrument" /></td></tr><tr class="odd"><td>FlapsSpeedbrakes</td><td>Defines an instrument that displays the speed brake status. This instrument requires a <code>&lt;Value&gt;</code> and you can optionally give it an <code>&lt;ID&gt;</code>.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_11_flapsspeedbrakes.png" title="Example Of The Flaps Speed Brake Instrument" alt="Example Of The Flaps Speed Brake Instrument" /></td></tr><tr class="even"><td>LongitudeFuel</td><td>Defines a gauge that is specific to the <strong>Longitude</strong> family of aircraft, and displayes the left and right fuel tank quantity as well as the total fuel quantity.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_12_longfuel.png" title="Example Of The Longitude Fuel Instrument" alt="Example Of The Longitude Fuel Instrument" /></td></tr></tbody></table>

 

 

#### &lt;ID&gt;

This element specifies the ID of the gauge being generated and is a sub-element of `<Gauge>`. If you are using two of the same gauge type, then the ID values should be different so you can differentiate between them. This element has no attributes.

 

 

#### &lt;Title&gt;

This element is a sub-element of `<Gauge>` and is the title of the instrument, and it will be included as part of the display (when appropriate to the `<Type>`). It has no attributes.

 

 

#### &lt;Unit&gt;

This element is a sub-element of `<Gauge>` and sets the unit that the instrument will use. When supplied (and when appropriate to the `<Type>`), this will be displayed along with the instrument. It has no attributes and can be omitted for the following instrument types:

1.  [Flaps](#Flaps)
2.  [FlapsSpeedbrakes](#FlapsSpeedbrakes)
3.  [LongitudeFuel](#LongitudeFuel)

 

 

#### &lt;Minimum&gt;

This element is a sub-element of `<Gauge>` and sets the minimum value for the instrument display (when appropriate to the `<Type>`). It has no attributes and can be omitted for the following instrument types:

1.  [Flaps](#Flaps)
2.  [FlapsSpeedbrakes](#FlapsSpeedbrakes)
3.  [LongitudeFuel](#LongitudeFuel)

 

 

#### &lt;Maximum&gt;

This element is a sub-element of `<Gauge>` and sets the maximum value for the instrument display (when appropriate to the `<Type>`). It has no attributes and can be omitted for the following instrument types:

1.  [Flaps](#Flaps)
2.  [FlapsSpeedbrakes](#FlapsSpeedbrakes)
3.  [LongitudeFuel](#LongitudeFuel)

 

 

#### &lt;TakeOff&gt;

This element is optional and is used to set the position of the take-off indicator for the "flaps" instrument. It takes a value, in degrees, that shows where the T/O indicator should be positioned, with 0° being to the *right* and increasing values going clockwise. If omitted, the default value will be 10°.

Only required when the `<Type>` is set to "Flaps".

 

 

#### &lt;Style&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is a container for the following style elements that will be used to set certain aspects of the instrument that is being defined:

1.  `<SizePercent>`
2.  `<ValuePos>`
3.  `<BeginAngle>`
4.  `<EndAngle>`
5.  `<CursorType>`
6.  `<CursorColor>`
7.  `<CursorStyle>`
8.  `<TextIncrement>`
9.  `<Width>`
10. `<Height>`
11. `<ValuePrecision>`
12. `<ForceTextColor>`
13. `<ReverseY>`
14. `<StrokeWidth>`
15. `<FontSize>`

 

Note that this element is not obligatory and can be omitted regardless of the type of instrument being defined, however it should *always* be omitted for the following instruments:

1.  [Flaps](panel-xml/#Flaps)
2.  [FlapsSpeedbrakes](panel-xml/#FlapsSpeedbrakes)
3.  [LongitudeFuel](panel-xml/#LongitudeFuel)

 

 

##### &lt;SizePercent&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used to scale the size of the instrument being defined relative to it's base size (which is considered as 100%).

All instrument types can use this element.

 

 

##### &lt;ValuePos&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used by the different instrument types to change the default positioning of the value text within the instrument context. The actual string that this uses to define the position will change depending on the instrument, as shown in the following table (note that only those instrument types listed use this element):

<table><thead><tr class="header"><th>Instrument</th><th>Strings</th><th>Description</th><th>Example</th></tr></thead><tbody><tr class="odd"><td><a href="#Circular">Circular</a></td><td>"End"</td><td><p>By default this instrument will show the current value as text in the center, under any <code>&lt;Title&gt;</code> text. When you include this element with the string "End", the value will instead be displayed at the <code>&lt;EndAngle&gt;</code> position.</p></td><td><img src="images/5_Content_Config/Instruments/panel_xml_15_circlepos.png" title="Example &lt;ValuePos&gt; for a Circular Instrument" alt="Example &lt;ValuePos&gt; for a Circular Instrument" /></td></tr><tr class="even"><td><a href="#Horizontal">Horizontal</a></td><td><p>"End"</p><p>"Right"</p></td><td>By default this instrument will not show the current value as text, however you can supply either "End" or "Right" to display the text at one of two positions. Note that when you use the "Right" option, the <code>&lt;Title&gt;</code> text will not be drawn.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_16_horzpos.png" title="Example &lt;ValuePos&gt; for a Horizontal Instrument" alt="Example &lt;ValuePos&gt; for a Horizontal Instrument" /></td></tr><tr class="odd"><td><a href="#DoubleHorizontal">DoubleHorizontal</a></td><td>"Right"</td><td>By default this instrument will not show the current value as text, however you can supply "Right" to display the text for both values on the far right end. Note that when you use this option, the <code>&lt;Title&gt;</code> text will not be drawn.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_17_dhorzpos.png" title="Example &lt;ValuePos&gt; for a Double Horizontal Instrument" alt="Example &lt;ValuePos&gt; for a Double Horizontal Instrument" /></td></tr><tr class="even"><td><a href="#Vertical">Vertical</a></td><td>"None"</td><td>By default this instrument will show the current value as text under the instrument, however you can supply "None" to remove this display.</td><td><img src="images/5_Content_Config/Instruments/panel_xml_18_vertpos.png" title="Example &lt;ValuePos&gt; for a Vertical Instrument" alt="Example &lt;ValuePos&gt; for a Vertical Instrument" /></td></tr></tbody></table>

 

 

##### &lt;BeginAngle&gt;

This element is a sub-element of `<Style>` and has no attributes. This sets the starting angle from which the circular instrument will be drawn. For this instrument, 0° is to the *left*, and positive values will be clockwise (so 90° is up, 180° is right and 270° is down). Note that you can use a negative value here too if required to start the gauge from the lower quadrant (eg: -45° is valid).

Used by the [Circular](#Circular) instrument type.

 

 

##### &lt;EndAngle&gt;

This element is a sub-element of `<Style>` and has no attributes. This sets the ending angle at which the circular instrument will be drawn. For this instrument, 0° is to the *left*, and positive values will be clockwise (so 90° is up, 180° is right and 270° is down).

Used by the [Circular](#Circular) instrument type.

 

 

##### &lt;CursorType&gt;

This element is a sub-element of `<Style>` and has no attributes. This element can be used to set the shape of the cursor that indicates the current value(s). You may include this element and use the string "Triangle" to set the cursor indicator to a triangle, or you may use any other string (or omit the element) to get the default arrow-type indicator, as shown in the image below:  

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_9_cursor.png"
    alt="Example Of How CursorType Affects The Circular Instrument" >}}

Used by the [Circular](#Circular) instrument type.

 

 

##### &lt;CursorColor&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used to set the colour of the cursor to something other than the default white. Colours should be [CSS compliant](https://www.w3.org/wiki/CSS/Properties/color/keywords "W3 CSS Colour Compliancy Details") (both hexadecimal values and colour keywords), but note that generally only the following are used: red, yellow, green, white, blue, magenta.

Used by the [Horizontal](#Horizontal) and [Vertical](#Vertical) instrument types.

 

 

##### &lt;CursorStyle&gt;

This element is a sub-element of `<Style>` and has no attributes. The element can be used to set the style of cursor that the instrument uses, either "Cursor" or "Fill", as shown in the image below. If omitted it will default to "Cursor".

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_13_cursorstyle.png"
    alt="Example Of How CursorStyle Affects The Horizontal Instrument" >}}

Used by the [Horizontal](#Horizontal) instrument type.

 

 

##### &lt;TextIncrement&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used to set the incremental amount by which values will be shown. For example, a value here of 0.1 will show 5.1, 5.2, 5.3, etc... while a value of 5 will show something like 235, 240, 245, 250, etc...

Used by the [Circular](#Circular), [Horizontal](#Horizontal), [DoubleHorizontal](panel-xml/#DoubleHorizontal), [Vertical](panel-xml/#Vertical) and [DoubleVertical](panel-xml/#DoubleVertical) instrument types.

 

 

##### &lt;Width&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used to scale the width of the instrument (as a percentage, where 100% is the default). Note that if you include this element, then the instrument may be scaled down or up to fit the available space, and not overlap other instruments.

Used by the [Horizontal](#Horizontal) instrument type.

 

 

##### &lt;Height&gt;

This element is a sub-element of `<Style>` and has no attributes. It is used to scale the height of the instrument (as a percentage, where 100% is the default). Note that if you include this element, then the instrument may be scaled down or up to fit the available space, and not overlap other instruments.

Used by the [DoubleVertical](#DoubleVertical) instrument type.

 

 

##### &lt;ValuePrecision&gt;

This element is a sub-element of `<Style>` and has no attributes. With this element you can set the number of decimal places to be displayed by the current value(s) for the instrument.

Used by the [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal) and [DoubleVertical](#DoubleVertical) instrument types.

 

 

##### &lt;ForceTextColor&gt;

This element is a sub-element of `<Style>` and has no attributes. It can be used to force the colour of some of the text elements of the instrument. Colours should be [CSS compliant](https://www.w3.org/wiki/CSS/Properties/color/keywords "W3 CSS Colour Compliancy Details"), but note that generally only the following are used: red, yellow, green, white, blue, magenta.

Used by the [Circular](#Circular) instrument type.

 

 

##### &lt;ReverseY&gt;

This element is a sub-element of `<Style>` and has no attributes. When set to "True" (or any value other than an empty - or omitted - element), the instrument will be drawn reversed on the Y axis (see the image, below, for an example).

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_7_reversey.png"
    alt="Example Of An Instrument With And Without Reversed Y" >}}

Used by the [Horizontal](#Horizontal) instrument type.

 

 

##### &lt;StrokeWidth&gt;

This element is a sub-element of `<Style>` and has no attributes. When included, the value given will change the width of the base lines used to draw the instrument (it will *not* affect additional lines drawn using the element), as shown in the example below:

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_8_strokewidth.png"
    alt="Example Of An Instrument With And Without A Specific Stroke Width" >}}

Used by the [Horizontal](#Horizontal) instrument type.

 

 

##### &lt;FontSize&gt;

This element is a sub-element of `<Style>` and has no attributes. This element sets the font size for the text elements within the instrument. If this element is not used then the default font size will be 10.

Used by the [Circular](#Circular), and [Horizontal](#Horizontal) instrument types.

 

 

#### &lt;Value&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is where you would place the XML that calculates the current value that the instrument is displaying, or the primary value for instruments showing two values (in which case `<Value2>` should also be defined). The value can be calculated using `<Simvar />`, [Panel XML Logic Elements](panel-xml-logic-elements/), or [Unique Logic Elements](panel-xml-logic-elements/#unique) elements. This element is required by all instrument types.

``` xml
<Value>
    <Simvar name="GENERAL ENG OIL TEMPERATURE:1" unit="farenheit"/>
</Value>
```

 

 

#### &lt;Value2&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is where you would place the XML that calculates the current *secondary* value that the instrument is displaying. The value can be calculated using `<Simvar />`, [Panel XML Logic Elements](panel-xml-logic-elements/), or [Unique Logic Elements](panel-xml-logic-elements/#unique) elements. Note that this element is only required for the [DoubleHorizontal](#DoubleHorizontal) and [DoubleVertical](#DoubleVertical) instrument types, and will require that you also define `<Value>`.

``` xml
<Value>
    <Simvar name="GENERAL ENG OIL TEMPERATURE:1" unit="celsius"/>
</Value>
<Value2>
    <Simvar name="GENERAL ENG OIL TEMPERATURE:2" unit="celsius"/>
</Value2>
```

 

 

#### &lt;ColorZone&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is a container for the following elements:

1.  `<Color>`
2.  `<Begin>`
3.  `<End>`
4.  `<SmoothFactor>`

The element is used to define one or more zones between the minimum and maximum values of the instrument, and then colour them using the specified colour. Note that this element can be omitted for the following instrument types:

1.  [Flaps](#Flaps)
2.  [FlapsSpeedbrakes](#FlapsSpeedbrakes)
3.  [LongitudeFuel](#LongitudeFuel)

 

Below is an example of a gauge definition using various colour zones:

``` xml
<Gauge>
    <Type>Circular</Type>
    <ID>Piston_RPMGauge</ID>
    <Title></Title>
    <Unit>RPM</Unit>
    <Minimum>0</Minimum>
    <Maximum>2800</Maximum>
    <Value>
        <Simvar name="PROP RPM:1" unit="rpm"/>
    </Value>
    <ColorZone>
        <Color>white</Color>
        <Begin>0</Begin>
        <End>2800</End>
    </ColorZone>
    <ColorZone>
        <Color>green</Color>
        <Begin>0</Begin>
        <End>2100</End>
    </ColorZone>
    <ColorZone>
        <Color>yellow</Color>
        <Begin>2100</Begin>
        <End>2300</End>
    </ColorZone>
    <ColorZone>
        <Color>red</Color>
        <Begin>2300</Begin>
        <End>2800</End>
    </ColorZone>
</Gauge>
```

 

 

##### &lt;Color&gt;

This is a sub element of both the `<ColorZone>` and `<ColorLine>` elements, as well as the `<Style>` sub-element (for reference bugs). It has no attributes and is simply used to define the colour that will be used for the zone, line, or bug being defined. Colours should be [CSS compliant](https://www.w3.org/wiki/CSS/Properties/color/keywords "W3 CSS Colour Compliancy Details"), but note that generally only the following are used: red, yellow, green, white, blue, magenta.

 

 

##### &lt;Begin&gt;

This is a sub element of the `<ColorZone>` element, and has no attributes. It sets the start point for the zone being defined, which should fall between the values set by the `<Minimum>` and `<Maximum>` elements.

 

 

##### &lt;End&gt;

This is a sub element of the `<ColorZone>` element, and has no attributes. It sets the end point for the zone being defined, which should fall between the values set by the `<Minimum>` and `<Maximum>` elements.

 

 

##### &lt;SmoothFactor&gt;

This is a sub element of the `<ColorZone>`, `<ColorLine>`, and `<ReferenceBug>` elements. It has no attributes and is simply used to set how "smooth" the movement of a gauge is as the indicator moves around. Essentially, the higher the value here, the more interpolated the instrument indicator will be, meaning that it will move to a new value at a smoother rate rather than instantly or very quickly.

 

 

#### &lt;ColorLine&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is a container for the following elements: `<Color>`, `<Position>`, `<SmoothFactor>`. The element is used to define one or more lines positioned between the minimum and maximum values of the instrument, coloured using the specified colour. Note that this element can be omitted for the following instrument types:

1.  [Flaps](#Flaps)
2.  [FlapsSpeedbrakes](#FlapsSpeedbrakes)
3.  [LongitudeFuel](#LongitudeFuel)

 

Below is an example of a gauge definition using various colour lines:

``` xml
<Gauge>
    <Type>Circular</Type>
    <ID>RPM_Gauge</ID>
    <Unit>RPM</Unit>
    <Minimum>0</Minimum>
    <Maximum>2750</Maximum>
    <Style>
        <BeginAngle>-45</BeginAngle>
        <EndAngle>180</EndAngle>
        <ValuePos>End</ValuePos>
        <CursorType>Triangle</CursorType>
    </Style>
    <Value>
        <Simvar name="PROP RPM:1" unit="rpm"/>
    </Value>
    <ColorZone>
        <Color>green</Color>
        <Begin>500</Begin>
        <End>2700</End>
    </ColorZone>
    <ColorLine>
        <Color>yellow</Color>
        <Position>2501</Position>
    </ColorLine>
    <ColorLine>
        <Color>red</Color>
        <Position>2701</Position>
    </ColorLine>
</Gauge>
```

 

 

##### &lt;Position&gt;

This is a sub element of the `<ColorLine>` element, and has no attributes. It sets the position for the line being defined, which should fall between the values set by the `<Minimum>` and `<Maximum>` elements.

 

 

#### &lt;ReferenceBug&gt;

This element is a sub-element of `<Gauge>`, and is used to show some kind of reference bug (marker) within the instrument being displayed. The element has no atrributes, and can take the following sub-elements: `<Style>`, `<Position>`, `<DisplayLogic>`, `<SmoothFactor>`. Note that this element is only useful for [Circular](panel-xml/#Circular) instrument types and is not implemented for any of the others. Also note that you can define multiple reference bugs for a single gauge. The image below shows an instrument with two active reference bugs (in yellow):

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_20_refbug.png"
    alt="Example Instrument With Two Defined Reference Bugs" >}}

Below is an example of how a reference bug would typically be formatted:

``` xml
<ReferenceBug>
    <Style>
        <Color>#00ccff</Color>
    </Style>
    <DisplayLogic>
        <And>
            <GreaterEqual>
                <Simvar name="PROP RPM:1" unit="rpm"/>
                <Constant>1600</Constant>
            </GreaterEqual>
            <LowerEqual>
                <Simvar name="PROP RPM:1" unit="rpm"/>
                <Constant>1900</Constant>
            </LowerEqual>
        </And>
    </DisplayLogic>
    <Position>
        <Function Name="MaximumCruiseTorqueBug"/>
    </Position>
</ReferenceBug>
```

 

 

##### &lt;Style&gt;

This is a sub-element of `<ReferenceBug>` and is used to set the style properties for the element. It takes no value itself, but must have the following sub-element:

1.  `<Color>`

 

 

##### &lt;Position&gt;

This sub-element of `<ReferenceBug>` is used to set the position of the reference bug graphic (within the `<Minimum>` and `<Maximum>` values) for the instrument. You can supply a fixed value here, or instead use the [Panel XML Logic Elements](panel-xml-logic-elements/) to determine the position dynamically based on the simulation.

 

 

##### &lt;DisplayLogic&gt;

This sub-element of `<ReferenceBug>` is used to display or hide the reference bug being defined for the instrument. This would normally be done using [Panel XML Logic Elements](panel-xml-logic-elements/) to create an expression that will evaluate to 1 (*true*: the bug is displayed) or 0 (*false*: the bug is hidden).

 

 

#### &lt;RedBlink&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and defines the parameters which will cause certain parts of the instrument to "blick" or "flash" red/white, indicating a serious issue. The element can use any of the [Panel XML Logic Elements](panel-xml-logic-elements/) to create an expression that resolves to 1 (*true*) or 0 (*false*), and when 1 (or greater than 1), the instrument will blink, as shown in the image below:

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_19_blink.gif"
    alt="Example Of A Gauge With The &lt;RedBlink&gt; Element" >}}

 

Used by the [Circular](#Circular), [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal), [Vertical](#Vertical) and [DoubleVertical](#DoubleVertical) instrument types.

 

 

#### &lt;GraduationLength&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and defines the distance between graduations on the instrument. The value should be proportional to the `<Minimum>` and `<Maximum>`: for example, if the minimum is 0 and the maximum is 100, a graduation length of 20 will show a graduation mark at 20, 40, 60 and 80. Note that if this element is omitted, then no graduation marks will be shown on the instrument.

Used by the [Circular](#Circular), [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal), [Vertical](#Vertical) and [DoubleVertical](#DoubleVertical) instrument types.

 

 

#### &lt;GraduationTextLength&gt; 

This element may be present in some legacy aircraft but is not actually parsed by the simulation.

 

 

#### &lt;BeginText&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and defines some text that will be shown aligned with the beginning of the instrument graduation, as illustrated in the image below for various instrument types (for clarity, we have used the text "Hello" as the begin text, and "World" as the end text):

![An Example Showing Various Instruments With Begin And End Text](images/5_Content_Config/Instruments/panel_xml_21_beginend.png)Used by the [Circular](#Circular), [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal), [Vertical](#Vertical) and [DoubleVertical](#DoubleVertical) instrument types.

 

 

#### &lt;EndText&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and defines some text that will be shown aligned with the ending of the instrument graduation, as illustrated in the image shown for the `<BeginText>` element.  
Used by the [Circular](#Circular), [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal), [Vertical](#Vertical) and [DoubleVertical](#DoubleVertical) instrument types.

 

 

#### &lt;CursorText&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is used to define a string that will be drawn over the cursor. There is no limit to the length of this string, but due to the size of the cursor being fixed, we recommend that you only use a single character - for example "L" or "R" - since additional characters will cause the text to overspill the cursor and be unreadable. The image below shows an example:

<img src="images/5_Content_Config/Instruments/panel_xml_14_cursortext.png" class="center" />

Used by the [Horizontal](#Horizontal), [DoubleHorizontal](#DoubleHorizontal) (defines the top cursor text), and [DoubleVertical](#DoubleVertical) (defines the left cursor text) instrument types.

 

 

#### &lt;CursorText2&gt;

This element is a sub-element of `<Gauge>`, has no attributes, and is used to define a string that will be drawn over the cursor. There is no limit to the length of this string, but due to the size of the cursor being fixed, we recommend that you only use a single character - for example "L" or "R" - since additional characters will cause the text to overspill the cursor and be unreadable. See `<CursorText>` for an example image.

Used by the [DoubleHorizontal](#DoubleHorizontal) (defines the right cursor text) and [DoubleVertical](#DoubleVertical) (defines the bottom cursor text) instrument types.

 

 

### &lt;Text&gt;

This element can be used within `<Gauge>` to define text-only instrument that is to be displayed. The text itself is defined using one of the position sub-elements:

1.  `<Left>`
2.  `<Center>`
3.  `<Right>`

The element has the following optional attributes:

 

{{< table-wrapper >}}

| Attribute  | Description                                           | Type       | Required |
|------------|-------------------------------------------------------|------------|----------|
| `id`       | The unique ID of the text element.                    | String/Int | No       |
| `fontsize` | The size of the font to be used for the text element. | Float      | No       |

{{< /table-wrapper >}}


 

Below is a basic example of a text-only instrument definition:

``` xml
<Text>
    <Center>FUEL FLOW</Center>
</Text>
<Text>
    <Left>
        <ToFixed precision="1">
            <Simvar name="ENG FUEL FLOW GPH:1" unit="gallons per hour"/>
        </ToFixed>
    </Left>
    <Center>
        <Content>GPH</Content>
        <Color>green</Color>
    </Center>
    <Right>
        <ToFixed precision="1">
            <Simvar name="ENG FUEL FLOW GPH:2" unit="gallons per hour"/>
        </ToFixed>
    </Right>
</Text>
```

The above would look like this in the glass-cockpit display:

{{< image-center
    src="images/5_Content_Config/Instruments/panel_xml_1_text.png"
    alt="Example Of A Text-Only Instrument Display" >}}

 

 

#### &lt;Left&gt;

This is a sub-element of `<Text>` and has no attributes. Text will be displayed on the far left of the area where the parent element is being positioned. In general, the text to be displayed goes within these tags, however if you wish to colour it, you will need to use the sub-element `<Content>` for the text and `<Color>` for the colour.

 

 

##### &lt;Content&gt;

This is a sub-element of `<Left>`, `<Center>`, or `<Right>` and is only required when you are also including the `<Color>` sub-element. Its sole purpose is to hold the text to be displayed (see the above example for `<Text>`).

 

 

##### &lt;Color&gt;

This is a sub-element of `<Left>`, `<Center>`, or `<Right>` and using it will also require you to use the `<Content>` sub-element. The element takes a colour string which will be used to colour the text being displayed (see the above example for `<Text>`). Colours should be [CSS compliant](https://www.w3.org/wiki/CSS/Properties/color/keywords "W3 CSS Colour Compliancy Details"), but note that generally only the following are used: red, yellow, green, white, blue, magenta.

 

 

#### &lt;Center&gt;

This is a sub-element of `<Text>` and has no attributes. Text will be displayed in the center of the area where the parent element is being positioned. In general, the text to be displayed goes within these tags, however if you wish to colour it, you will need to use the sub-element `<Content>` for the text and `<Color>` for the colour.

 

 

#### &lt;Right&gt;

This is a sub-element of `<Text>` and has no attributes. Text will be displayed on the far right of the area where the parent element is being positioned. In general, the text to be displayed goes within these tags, however if you wish to colour it, you will need to use the sub-element `<Content>` for the text and `<Color>` for the colour.

 

 

### &lt;ColumnsGroup&gt;

This is a container element for the `<Column>` sub-element, of which there should always be two. It is used to tell the simulation to display two gauges side by side. Note that this element can be nested within a `<Column>` sub-element to create rows of gauges, for example:

``` xml
<EngineDisplay>
    <ColumnsGroup>
        <Column width="43">
            <ColumnsGroup>
                <Column>
                    <Gauge>
                        
                    </Gauge>
                </Column>
                <Column>
                    <Gauge>
                        
                    </Gauge>
                </Column>
            </ColumnsGroup>
        </Column>
        <Column>
            <Gauge>
                
            </Gauge>
            <Gauge>
                
            </Gauge>
        </Column>
        <Column>
            <Gauge>
                 
            </Gauge>
            <Gauge>
                 
            </Gauge>
        </Column>
    </ColumnsGroup
</EngineDisplay>
```

 

 

#### &lt;Column&gt;

This is a sub-element of the `<ColumnsGroup>` container, and is used to specify a gauge that should be displayed beside another one, using the `<Gauge>` element. You must have two of these elements within each `<ColumnsGroup>` and the first defines the left gauge, and the second the right. The element can have the following (optional) attribute:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>width</code></td><td><p>This is the width of the column expressed as a percentage, where 100% is considered the total width of the <code>&lt;ColumnGroup&gt;</code> the element is within. Note that <em>only</em> the value is given, with no need for the % symbol, eg:</p><pre class="language-xml"><code>&lt;Column width=&quot;50&quot;&gt;</code></pre></td><td>String</td><td>No</td></tr></tbody></table>

 

 

### &lt;Condition&gt;

This element defines the condition(s) under which an annunciation or voice alert should be triggered. It is primarily a sub-element of `<Annunciations>`, `<Alert>`, and `<State>` , although it can be used in many other situations (for example, as part of an `<If>`). It has the following optional attribute:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>Suffix</code></td><td><p>This adds a specific suffix onto the <code>&lt;Text&gt;</code> element string. The suffix itself can only be:</p><ol><li>"<strong>L</strong>"</li><li>"<strong>R</strong>"</li><li>"<strong>L-R</strong>"</li></ol><p>See <a href="panel_xml/#Suffix">Using The Suffix Attribute</a>, below, for more information.</p></td><td>String</td><td>No</td></tr></tbody></table>

 

It is important to note that you may use many of the [Panel XML Logic Elements](panel-xml-logic-elements/) - like `<And>`, `<Or>`, `<Lower>`, `<GreaterEqual>`, etc... - along with the `<Simvar />` element or [Unique Logic Elements](panel-xml-logic-elements/#unique) within the `<Condition>` element to define the true/false state which will trigger the condition (or not).

 

#### Using The Suffix Attribute

The `Suffix` attribute can be used in a condition that is being created for an `<Annunciation>` element. The way it works is as follows:

-   Your JS code inherits from the `NavSystem` subclass.
-   Your XML has conditions for one, two or three of the possible suffix strings.
-   If one of the conditions is true, then the suffix string is appended onto the `<Text>` element string.

The following example shows how the XML should be structured when using this attribute:

``` xml
<Annunciation>
    <Type>Caution</Type>
    <Text>PITOT HT ON </Text>
    <Condition Suffix="L-R">
        <And>
            <Lower>
                <Simvar name="PROP RPM:1" unit="rpm"/>
                <Constant>1</Constant>
            </Lower>
            <And>
                <Simvar name="L:XMLVAR_Pitot_1" unit="Bool"/>
                <Simvar name="L:XMLVAR_Pitot_2" unit="Bool"/>
            </And>
        </And>
    </Condition>
    <Condition Suffix="L">
        <And>
            <Lower>
                <Simvar name="PROP RPM:1" unit="rpm"/>
                <Constant>1</Constant>
            </Lower>
        <Simvar name="L:XMLVAR_Pitot_1" unit="Bool"/>
        </And>
    </Condition>
    <Condition Suffix="R">
        <And>
            <Lower>
                <Simvar name="PROP RPM:1" unit="rpm"/>
                <Constant>1</Constant>
            </Lower>
        <Simvar name="L:XMLVAR_Pitot_2" unit="Bool"/>
        </And>
    </Condition>
</Annunciation>
```

 

 

### &lt;Simvar /&gt;

This self-closing element is a sub-element of multiple other elements and is used to define a SimVar that should be used by the associated variable or element. It is used by: `<[CUSTOM]>`, `<Electric>`, and as part of the `<Condition>` element, and can be nested within other [Panel XML Logic Elements](panel-xml-logic-elements/) to create a complex expression.

 

This element has the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>name</code></td><td><p>The name of the SimVar that is being referenced along with any parameters, separated by a colon. You can find a complete list of available SimVars here: <a href="../../../../6_Programming_APIs/SimVars/Simulation_Variables.htm">Simulation Variables</a></p><p>Below you can find an example of how the attribute is formatted:</p><pre class="codeblock"><code>name=&quot;GENERAL ENG OIL PRESSURE:1&quot;</code></pre></td><td>String</td><td>Yes</td></tr><tr class="even"><td><code>unit</code></td><td><p>The unit that the SimVar should be using, which should be one of the accepted strings listed here: <a href="../../../../6_Programming_APIs/SimVars/Simulation_Variable_Units.htm">Simulation Variable Units</a></p><p>For example:</p><pre class="codeblock"><code>unit=&quot;psi&quot;</code></pre></td><td>String</td><td>Yes</td></tr></tbody></table>

 

 

### &lt;Gamevar /&gt; 

This self-closing element is a sub-element of multiple other elements and is used to define a Game Variable that should be used by the associated variable or element. It is used by: `<[CUSTOM]>`, `<Electric>`, and as part of the `<Condition>` element, and can be nested within other [Panel XML Logic Elements](panel-xml-logic-elements/) to create a complex expression.

{{< callout context="caution" title="IMPORTANT!" icon="outline/alert-triangle" >}}

This is an obsolete tag and **should not be used**. You should be using the `<Simvar />` element instead.

{{< /callout >}}

 

This element has the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>name</code></td><td><p>The name of the Game Variable that is being referenced along with any parameters, separated by a colon.</p><p>Below you can find an example of how the attribute is formatted:</p><pre class="codeblock"><code>name=&quot;GENERAL ENG OIL PRESSURE:1&quot;</code></pre></td><td>String</td><td>Yes</td></tr><tr class="even"><td><code>unit</code></td><td><p>The unit that the Game Variable should be using, which should be one of the accepted strings listed here: <a href="../../../../6_Programming_APIs/SimVars/Simulation_Variable_Units.htm">Simulation Variable Units</a></p><p>For example:</p><pre class="codeblock"><code>unit=&quot;psi&quot;</code></pre></td><td>String</td><td>Yes</td></tr></tbody></table>

 

 

### &lt;Constant&gt;

This element is used to hold a single constant value and is used as part of the expression being evaluated within the following elements:

1.  `<[CUSTOM]>`
2.  `<Electric>`
3.  `<Condition>`

 

It can also be nested within other [Panel XML Logic Elements](panel-xml-logic-elements/) to create a complex expression.

 

 

### &lt;EFB&gt;

This top level element is used to setup certain properties of the aircraft within the {{< glossterm >}}efb{{< /glossterm >}}. Currently this section is used exclusively for customising the layout of the aircraft within the Mass And Balance menu of the aircraft app. Future updates may add more possibilities and sections.

 

A typical {{< glossterm >}}efb{{< /glossterm >}} definition in the panel XML looks something like this:

``` xml
<EFB>
  <MassAndBalance>
    <Electrical>
      <Battery name="LowBattery1" full-title="Low voltage battery 1" short-title="LVB1" section="CENTER"/>
      <Battery name="LowBattery2" full-title="@asobo-aircraft-es30,TT:EFB.ELECTRICAL.LOW_VOLTAGE_BATTERY_2" short-title="@asobo-aircraft-es30,TT:EFB.ELECTRICAL.LOW_VOLTAGE_BATTERY_2_SHORT" section="CENTER"/>
    </Electrical>
    <Fuel>
      <Tank name="LeftTank" full-title="@fs-base,TT:MENU.FUEL.LEFT_TANK" short-title="@fs-base,TT:MENU.FUEL.LEFT_TANK_SHORT" section="LEFT" />
      <Tank name="RightTank" full-title="Right Tank" short-title="RT" section="RIGHT" />
    </Fuel>
  </MassAndBalance>
</EFB>
```

 

This element can have the following container sub-element:

1.  `<MassAndBalance>`
2.  `<FlightPerformance>`

 

 

#### &lt;MassAndBalance&gt;

This is a sub-element of `<EFB>` and is a container for the other element that will affect the mass and balance of the aircraft. Currently you can only have *one* of these containers defined for the EFB. Note that this is not a required element, and if omitted the aircraft size will be deduced from the aircraft *wingspan*.

 

The element has the following required attribute:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>aircraft-size</code></td><td><p>This is used to define the "size" of the aircraft, which can be either "Small", "Medium", or "Large". It is used to set the zoom level of the aircraft outline displayed in the Mass and Balance menu in the EFB. The smaller the aircraft is, the more the shape will be zoomed in:</p><p><img src="images/6_Programming/EFB/efb_4_mass.png" title="The Different Aircraft Sizes In The EFB Display" class="center" alt="The Different Aircraft Sizes In The EFB Display" /></p><p>For informationon how to create the aircraft outline used in the Mass and Balance section of the EFB, please see here: <a href="../../../../2_DevMode/Menus/tools_info/The_Aircraft_Capture_Tool.htm">The Aircraft Capture Tool</a></p></td><td>String</td><td>Yes</td></tr></tbody></table>

 

This element can have the following sub-elements:

1.  `<Electrical>`
2.  `<Fuel>`
3.  `<Liquid>`

 

 

#### &lt;Electrical&gt;

This is a sub-element of `<MassAndBalance>` and is a container element for the different electrical components that will be displayed as part of the electrical system for the aircraft. It has no attributes and can have the following sub-elements:

1.  `<Battery>`

 

 

##### &lt;Battery&gt;

This is a sub-element of `<Electrical>` and is used to define a single battery that is part of the electrical system of the aircraft. It should be noted that - by default - **no** batteries belonging to the electrical system will be displayed in the aircraft app Mass and Balance menu. If you wish *any* to be displayed, then they need to be explicitly listed in this file.

 

The element has the following required attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>name</code></td><td>This is the <em>name</em> of the <a href="../../../cfg-files/systems_cfg/#batteryn">battery</a> to be shown in the <a href="#" class="glossterm">EFB</a>.</td><td>String</td><td>No  

(Yes, if no <code>id</code> is specified)</td></tr><tr class="even"><td><code>full-title</code></td><td><p>This attribute corresponds to the name that will be displayed in the popup when clicking on the battery in the aircraft app Mass and Balance menu. This text can be localised.</p><p><strong>NOTE</strong>: If this is not included, then the title will be generated automatically based on internal calculations. If you wish to force an empty title, then you can use this attribute with an empty string "".</p></td><td>String</td><td>No</td></tr><tr class="odd"><td><code>short-title</code></td><td><p>This attribute corresponds to the characters that will be displayed within the battery in the aircraft app Mass and Balance menu.</p><p><strong>NOTE</strong>: If this is not included, then the short title will be generated automatically based on internal calculations. We <strong>strongly</strong> recommend that you supply a value for this attribute to prevent text overflow. If you wish to force an empty short-title, then you can use this attribute with an empty string "".</p></td><td>String</td><td>No</td></tr><tr class="even"><td><code>section</code></td><td><p>This attribute is used to show visually the battery position within the aircraft. There are three available strings that can be used:</p><ol><li>left</li><li>center</li><li>right</li></ol><p>If this attribute is not included, then it will be considered as "center".</p></td><td>String</td><td>No</td></tr></tbody></table>

 

 

 

#### &lt;Fuel&gt;

This is a sub-element of `<MassAndBalance>` and is a container element for the different tanks that will be displayed as part of the fuel system for the aircraft. It has no attributes and can have the following sub-elements:

1.  `<Tank>`

 

 

##### &lt;Tank&gt;

This is a sub-element of `<Fuel>` and `<Liquid>` and is used to define a single tank that is part of the main fuel or liquid dripping system of the aircraft. It should be noted that - by default - **all** tanks belonging to the fuel and liquid dropping systems will be displayed in the aircraft app Mass and Balance menu. However, if at least one tank is listed in the `<Fuel>` or the `<Liquid>` elements, all other tanks that are present in the corresponding system but which are *not* referrenced as an element in the XML, *will not be displayed in the aircraft*. This makes it a useful way to hide specific tanks that should not be directly filled by the user (for example, a reservoir fuel tank).

 

The element has the following required attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>name</code></td><td>This is the <em>name</em> of the <a href="../../../cfg-files/flight_model_cfg/#Tank.N">fuel tank</a> or the <a href="../../../cfg-files/systems_cfg/#Tank.N%20%5BLiquid%20Dropping%20System%5D">liquid dropping tank</a> in the <a href="#" class="glossterm">EFB</a>. If this is included then there is no need for the <code>id</code> attribute. If this is not included, then the <code>title</code> from the <code>Tank.N</code> definition will be used instead.</td><td>String</td><td>No  

(Yes, if no <code>id</code> is specified)</td></tr><tr class="even"><td><code>id</code></td><td><p>This is the <em>index</em> of the <a href="../../../cfg-files/flight_model_cfg/#Tank.N">fuel tank</a> or the <a href="../../../cfg-files/systems_cfg/#Tank.N%20%5BLiquid%20Dropping%20System%5D">liquid dropping tank</a>. If this is included then there is no need for the <code>name</code> attribute.</p><p><strong>NOTE</strong>: It is preferrable to always use the <code>name</code> attribute, due to the fact that modular aircraft may change the indexing as part of the <a href="../../modular-simobject-merging/">merge process</a>.</p></td><td>Integer</td><td>No  

(Yes if no <code>name</code> is specified)</td></tr><tr class="odd"><td><code>full-title</code></td><td><p>This attribute corresponds to the name that will be displayed in the popup when clicking on the tank in the aircraft app Mass and Balance menu. This text can be localised.</p><p><strong>NOTE</strong>: If this is not included, then the EFB will use the <a href="../../../cfg-files/flight-model/modular-fuel-system-information/#tank">tank</a>title defined in the CFG file. If you wish to force an empty title, then you can use this attribute with an empty string "".</p></td><td>String</td><td>No</td></tr><tr class="even"><td><code>short-title</code></td><td><p>This attribute corresponds to the characters that will be displayed within the tank in the aircraft app Mass and Balance menu.</p><p><strong>NOTE</strong>: If this is not included, then the short title will be generated automatically based on internal calculations. We <strong>strongly</strong> recommend that you supply a value for this attribute to prevent text overflow. If you wish to force an empty short-title, then you can use this attribute with an empty string "".</p></td><td>String</td><td>No</td></tr><tr class="odd"><td><code>section</code></td><td><p>This attribute is used to show visually the tank position within the aircraft. There are three available strings that can be used:</p><ol><li>left</li><li>center</li><li>right</li></ol><p>If this attribute is not included, then it will be calculated automatically based on the position of the named/indexed tank in the CFG files.</p></td><td>String</td><td>No</td></tr></tbody></table>

 

 

#### &lt;Liquid&gt;

This is a sub-element of `<MassAndBalance>` and is a container element for the different tanks that will be displayed as part of the liquid dropping system for the aircraft. It has no attributes and can have the following sub-elements:

1.  `<Tank>`

 

 

### &lt;FlightPerformance&gt;

This sub-element of `<EFB>` allows you to customise some aspects of the **environment** menu in the default aircraft app in the {{< glossterm >}}efb{{< /glossterm >}}. Currently, the only available configuration options are for the aircraft **flaps** which also requires that you have added relevant flaps data to the [flight\_performance.cfg](../../../cfg-files/flight_performance.cfg/) and included the file as part of the aircraft configuration files. Configurations are separated for takeoff and landing, and note that if no configuration is specified, the default flaps lists will be displayed (from 0 to the maximum defined flap index). It is also possible to create a list with custom names for the various flap indices using the flap configurations.

{{< image-center
    src="images/6_Programming/EFB/efb_5_environment.png"
    alt="The Environment Section Of The Aircraft App In the EFB" >}}

 

The following example shows how the XML should be structured when using this element:

``` xml
<FlightPerformance>
     <TakeOff>
         <FlapsConfiguration>
             <Flap title="Flaps 5°" flapIndex="3" />
             <Flap title="Flaps 10°" flapIndex="4" />
             <Flap title="Flaps 15°" flapIndex="5" />
             <Flap title="Flaps 25°" flapIndex="6" />
         </FlapsConfiguration>
     </TakeOff>
     <Landing>
         <FlapsConfiguration>
             <Flap title="Flaps 25°" flapIndex="6" />
             <Flap title="Flaps 30°" flapIndex="7" />
             <Flap title="Flaps 40°" flapIndex="8" />
         </FlapsConfiguration>
     </Landing>
 </FlightPerformance>
```

 

This element has no attributes and can have the following sub-elements:

1.  `<TakeOff>`
2.  `<Landing>`

 

 

#### &lt;TakeOff&gt;

This is a sub-element of `<FlightPerformance>` and acts as a container element for environment data related to the aircraft takeoff procedures. It has no attributes and uses the following sub-element:

1.  `<FlapsConfiguration>`

 

 

#### &lt;Landing&gt;

This is a sub-element of `<FlightPerformance>` and acts as a container element for environment data related to the aircraft landing procedures. It has no attributes and uses the following sub-element:

1.  `<FlapsConfiguration>`

 

 

#### &lt;FlapsConfiguration&gt;

This is a sub-element of the `<TakeOff>` and `<Landing>` and holds one or more of the following sub-elements used to define the different flap indices to display the performance data for:

1.  `<Flap>`

 

 

#### &lt;Flap /&gt;

This sub-element of `<FlapsConfiguration>` is used to define a specific flap index to show in the EFB environment section, and if there is corresponding information from the [flight\_performance.cfg](../../../cfg-files/flight_performance.cfg/) for the flap, this will also be shown as well. You can have multiple &lt;Flap&gt; elements, and it is self-closing, requiring the following attributes:

 

{{< table-wrapper >}}

| Attribute   | Description | Type    | Required |
|-------------|-------------|---------|:--------:|
| `title`     |             | String  |    No    |
| `flapIndex` |             | Integer |    Yes   |

{{< /table-wrapper >}}