📄
SPAD.neXt
  • SPAD.neXt Manual
  • About SPAD.neXt
  • Getting Started
    • System Requirements
    • Supported hardware
      • Check Hardware
    • Installation
      • Simulation Specifc Steps
        • SimConnect Configuration
        • MSFS: Enable PMDG data access
        • X-Plane Configuration
    • First Start
      • Configuration Wizard
    • Common Tasks and Issues
      • SPAD
        • Online Services
        • Fresh reinstall
        • Move SPAD.neXt to new Computer
        • License Issues
      • MSFS Specific Topics
      • X-Plane specific Topics
      • Saitek/Logitech MP/RP blinking
      • USB Powermanagement
  • Guides and Videos
    • New User Series
    • MSFS SimConnect
    • L:Vars / H:Events and B:Events
    • Features & Functions
    • Device Specific
      • Arduino / SPAD Serial
      • Authentikit
      • Cockpit Simulator CDU
      • Honeycomb
      • Joystick (Generic HID)
      • miniCockpit
      • RealSimGear
      • Saitek/Logitech
      • Script Panel
      • Stream Deck
      • Thrustmaster TCA
      • vFIP
      • Virtual Avionics
      • vJoy
      • VRinsight
      • X-Touch MC Mode
      • X-Touch Midi Mode
    • Simulation Specific
      • ATR 600 (MSFS)
      • AS CRJ 550/700/900/1000 (MSFS)
      • FBW A32NX (MSFS)
      • FFX/MG HJet (MSFS)
      • FFX Vision Jet (MSFS)
      • FSW C414AW (MSFS)
      • PMDG 737 (MSFS)
      • PMDG 777 (MSFS)
      • SWS Kodiak (MSFS)
      • WT CJ4 (MSFS)
      • WT G1000 NXi (MSFS)
      • PMDG 777 (P3D)
  • User Interface
    • UI Familiarization
      • Home Page
      • Profiles Page
  • Features
    • Expressions
      • Values
      • Referencing Simulation Data
      • Operators
      • Functions
      • Examples
    • Tuner Acceleration
    • Event Execution Order
  • Simulations
    • MSFS 2024
    • MSFS 2020
    • X-Plane
      • Pre-Requisites
      • Dataref Tool
      • Helping Spad Help You
      • Dataref vs. Command: Know Your Copilots
      • Basic Flight Controls – Axis Setup
    • P3d and FSX
    • Other
  • Hardware specific
    • USB HUB Requirements
    • CPFlight Devices
    • Saitek FIP (Flight Instrument Panel)
      • Saitek FIP: Driver & Function Check
    • Loupedeck Image Devices
    • Midi Devices
      • X-Touch Mini
    • Serial (COM) Devices
    • Skalarki
    • VRInsight Overhead
  • Extending and API's
    • Gauges and Extensions
      • SPAD Gauges: GaugeSettings
    • C# Scripting Interface
      • C# Scripting: ScriptStub
      • C# Scripting: Provide Values
      • C# Scripting: PreCompile
    • Device Interface
      • Device Communication Flow
        • Device INIT-Phase
        • Device CONFIG-Phase
          • Device options
          • Device COLORSET configuration
          • Device PROFILE configuration
          • Device OUTPUT Configuration
          • Device INPUT configuration
            • Device input AXIS
            • Device input ENCODER
            • Device input PUSHBUTTON
            • Device input ROTARY
            • Device input SWITCH
            • Device input SWITCH3
            • Device LABEL
          • Device config: Advanced topics
        • Device STATESCAN-Phase
      • Device General Commands
      • Device commands
        • Page-Control
      • Device SPAD.neXt Events (2)
      • Device Simulation Events (Channel 4)
      • Device Data (Channel 5)
      • Device LED Update (Channel 6)
      • Device Display Update (Channel 7)
      • Device Input Updates (Channel 8)
      • Device Virtual Power
      • Device Custom UI
      • Device HTML UI
      • Device preconfigured definition
      • Serial V2
        • Command 1,RAISE
        • Command: 0,AUTH
    • X-Plane Datarefs & Commands
    • FSUIPC: Custom Offsets
    • RestAPI
    • HTML Rendering API
    • Other API's
  • FAQ
    • General FAQ
    • MSFS: Lost profile aircraft assigments
  • Changes
    • 0.9.21
    • 0.9.14.0
    • 0.9.13.39
  • Glossar
  • Old-Docs
    • Old-Getting-Started-Guide
Powered by GitBook
On this page
  • Extensions for (RPN) Expressions
  • GaugeSettings

Was this helpful?

  1. Extending and API's

Gauges and Extensions

SPAD.neXt generally supports ESP compatible gauges

PreviousVRInsight OverheadNextSPAD Gauges: GaugeSettings

Last updated 3 months ago

Was this helpful?

Gauges loaded into SPAD.neXt have to match this schema:

RPN Expressions have to be ESP RPN conform!

SPAD.neXt is generally Saitek/Logitech compatible, but it has NOT implemented Saitek Bugs:

Saitek gauges require a Non-Space-Character before a closing brace "}" e.g. in if{ statements: if{ someexpression %} els{ someotherexpression %}

SPAD.neXt does not support this. You will need to alter the gauge accordingly and remove the %

Extensions for (RPN) Expressions

To access any other Data than Simconnect (FSX / P3D / MSFS) use the Dataref-Tag as it is used by SPAD.neXt. Those Datarefs have always the format

RPN Expressions: (PROVIDER:DATREFNAME) or (PROVIDER:DATREFNAME,unit) SPAD Expressions: [PROVIDER:DATREFNAME] or [PROVIDER:DATREFNAME,unit]

If the requested unit does not match the datarefs default unit, SPAD.neXt will automatically convert it to the requested unit, if such a conversion is known

To access LVAR use the prefix LVAR: (FSX/P3D/MSFS only) (LVAR:AB_MCP_AP_ON, Number)

To access FSUIPC Offsets use the Prefix FSUIPC: (FSUIPC:0000:0AB2, Number)

You can copy a dataref from the data browser to you cilpboard, by selecting it and pressing CTRL-C or the OK Button.

Other examples:

PMDG (P3D): (PMDG737:1000:010E) = Glareshield.Mode Control Panel.Altitude

ETS2 (SCS:scs/truck/fuel) X-Plane: (XPLANE:sim/cockpit2/annunciators/afterburner)

Local Variables access

LOCAL:VARNAME Local var , will not be saved, will be initialized to 0 if it does not exist already

DEVICE:VARNAME Local var, Value will be DEVICE-specific, and will be initialized to the saved value again when the gauge is loaded onto that device. (Same varibale has diffrent value son different FIP devices)

PROFILE:VARNAME Local var , Value will be saved to the PROFILE , and will be initialized to the saved value again when the profile is loaded

Additional Time-Variables

(LOCAL:LOCAL TIME,Hours)

Dynamic Images

The Image-Tag supports the following extensions for dynamically changing images:

  • Attribute "Dynamic"

  • Sub-tag "Value"

Example:

<Element id="RevBar">
        <Position X="164" Y="144" />
        <Image Name="null1.png" Dynamic="rpm_{VALUE}.png" ImageSizes="472,135,472,135">
           <Value Minimum="1" Maximum="32">(A:RPM) ABS 250 / %</Value>
       </Image>
</Element>

Dynamic Labels

In order to show numbers on the gauge, SPAD.neXt support an additional sub element: <Label>

See: Dynamic Labels

Extended Button Configuration

To assign a function to a FIP button other than a SimConnect Control Event, you can deliver an extended button configuration together with your gauge. Just configure the button as desired within SPAD.neXt, and then export the button configuration (copy to clipboard and save to a file) to a file BUTTONNAME.bml in the gauge main directory. The following buttons are supported: FIP_BUTTON_S1 - FIP_BUTTON_S6 , FIP_RIGHTDIAL, FIP_LEFTDIAL, FIP_BUTTON_PAGEUP, FIP_BUTTON_PAGEDOWN

GaugeSettings

SPAD.neXt also defines an additional tag for providing settings in a gauge:

<Gauge>
..
..
..
  <GaugeSettings .....>
  </GaugeSettings>
</Gauge>
  • SPAD.neXt GaugeSettings Sample

All time variables as shown can also be used with the "LOCAL:"-Prefix to retrieve the local computer time as UTC/Local. To get the local computer hour you would use

Gauge.xsd
here