INSTRUMENT ATTACHMENTS

IMPORTANT! This page is currently WIP and will be improved with future updates.

The attachments listed here are all cockpit instruments that can be used in your own aircraft. Most of them can be used in most aircraft, regardless of the career path.

 

 

Behavior Parameters

In all of the following instruments, unless otherwise stated, when a model behavior parameter is listed, this is a dynamic parameter that has been created in the SimAttachment model behaviors. For example, the Asobo_Monitoring_FCU has the following in it's Model XML file (FCU.xml):

<DynamicParameters>
    <CIRCUIT_ID>1</CIRCUIT_ID>
</DynamicParameters>

 

These dynamic parameters will also need to be listed in the attached_objects.cfg using the behavior_parameter.N parameter. Again, using the previously mentioned FCU attachment, we have this in the attached_objects.cfg:

[SIM_ATTACHMENT.11]
attachment="SimAttachments\Instruments\Asobo_Monitoring_FCU\model\FCU.xml"
attach_to_model="interior"
attach_to_model_minsize=0 
attach_to_node="ATTACH_POINT_FCU_01"
attach_offset=0,0,0
attach_pbh=0,0,0
attach_scale=1.0
always_execute_associate_js=1
always_execute_model_behavior=1
vcockpit_parameter.0="VCockpit01_htmlgauge00_params,?Index=1"
alias="FRONT"
behavior_parameter.0="CIRCUIT_ID,'FCU_FES'_n" ;

 

Here we are defining two parameters, the first is the one the FCU adds in the model behavior, while the second is the name of the circuit that we'll be supplying to the dynamic parameter. Both of these can now be used in your own model behavior files to control the FCU power.

 

 

VCockpit Parameters

In all of the following instruments, unless otherwise stated, when a VCockpit parameter is listed, this is something that can be used in the the attached_objects.cfg using the vcockpit_parameter.N parameter. For example, if we look at the Asobo_MPA_ASD57 there are two additional VCockpit parameters, and these would be listed in the attached_objects.cfg like this:

[SIM_ATTACHMENT.3]
attachment="SimAttachments\Instruments\Asobo_MPA_ASD57\model\ASD57.xml"
attach_to_model="interior"
attach_to_model_minsize=0 
attach_to_node="ATTACH_POINT_MFD_AA57_02"
attach_offset=0,0,0
attach_pbh=0,0,0
attach_scale=1.0
always_execute_associate_js=1
always_execute_model_behavior=1
behavior_parameter.0="CIRCUIT_ID,13"
behavior_parameter.1="RADIO_INDEX,2"
behavior_parameter.2="XPDR_INDEX,2"
vcockpit_parameter.0="VCockpit01_htmlgauge00_params,?xpdrIndex=2&radioIndex=2"

 

It should be noted that almost all instrument attachments have two pre-defined VCockpit parameters created in their panel.cfg file. These are:

[DynamicParameters]
param.0 = "VCockpit01_htmlgauge00_file,[HTML FILE HERE]"
param.1 = "VCockpit01_htmlgauge00_params,"
  • VCockpit01_htmlgauge00_file: This is meant to contain the path to the [instrument].html file. This can potentially be used to look at a different HTML file, but in most cases that should not be necessary and this will not need edited or changed.
  • VCockpit01_htmlgauge00_params: This is meant to contain any additional parameters for the URL. By default this has no additional parameters.

 

 

Asobo_Accelerometer_01

 

 

 

Asobo_ADF_AS87

 

 

 

Asobo_ADF_BearingIndicator_01

 

 

 

Asobo_Altimeter_01

 

 

 

Asobo_Altimeter_4FGH10

 

 

 

Asobo_Attitude_Indicator_01

 

 

 

Asobo_Attitude_Indicator_02

 

 

 

Asobo_Attitude_Indicator_AS2610

 

 

 

Asobo_Attitude_Indicator_AS321

 

 

 

Asobo_AudioPanel_AS28

 

 

 

Asobo_AUDIOPANEL_AS340

 

 

 

Asobo_AudioPanel_G350

 

 

 

Asobo_AUTOPILOT_AS50

 

 

 

Asobo_Autopilot_AS140

 

 

 

Asobo_Autopilot_G305

 

 

 

Asobo_Autopilot_G307_NoYawDamper

 

 

 

Asobo_Autopilot_G307_YawDamper

 

 

 

Asobo_Autopilot_G700

 

 

 

Asobo_CDI_With_Glide_01

 

 

 

Asobo_CDI_Without_Glide_01

 

 

 

Asobo_Clock_Analogic_01

 

 

 

Asobo_Clock_AS803

 

 

 

Asobo_Compass_01

 

 

 

Asobo_Compass_AS2300

 

 

 

Asobo_ELT_01

 

 

 

Asobo_Floaters_Landing_Gear_Panel_Generic_01

 

 

 

Asobo_Fuel_Gauge_Double_01

 

 

 

Asobo_FuelFlow_EGT_01

 

 

 

Asobo_Garmin_Common

 

 

 

Asobo_GPS_G196

 

 

 

Asobo_Heading_Indicator_01

 

 

 

Asobo_Heading_Indicator_Two_Knobs

 

 

 

Asobo_Hourmeter_01

 

 

 

Asobo_HSI_01

 

 

 

Asobo_HSI_AS525

 

 

 

Asobo_Lever_BannerRelease

 

 

 

Asobo_Lever_LandingGearFloats_Box

 

 

 

Asobo_Lever_LandingGearSafetyPump

 

 

 

Asobo_Lever_LandingGearSkis_Box

 

 

 

Asobo_Lever_WaterRudder

 

 

 

Asobo_Monitoring_AS_50T

Asobo_Monitoring_AS_50T

This is a main display panel that can be used in any aircraft. For an example, it is currently used by the AT 802 in the simulation.

 

Expected behavior parameter and its default value:

<CIRCUIT_ID>1</CIRCUIT_ID>
<BOUNCE_POTENTIOMETER>1</BOUNCE_POTENTIOMETER>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. BOUNCE_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Monitoring/MVP50/mvp50.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Monitoring_ASMiniVigilus

Asobo_Monitoring_ASMiniVigilus

This is a "mini" version of the Vigilus monitoring screen that can be used in any aircraft. Currently it is unused by any of the default aircraft in the simulation, and only has a model, but no code. As such, we do not recommend using this attachment except as a visual asset.

 

 

Asobo_Monitoring_ASVigilus

Asobo_Monitoring_ASVigilus

This is a Vigilus monitoring screen that can be used in any aircraft. Currently it is unused by any of the default aircraft in the simulation.

 

Expected behavior parameter and its default value:

 <CIRCUIT_ID>39</CIRCUIT_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Monitoring/ASVigilus/ASVigilus.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Monitoring_FCU

Asobo_Monitoring_FCU

This is a generic Flight Control Unit that can be used in any aircraft. For an example, it is currently used by the DG 1001 in the simulation.

 

Expected behavior parameter and its default value:

<CIRCUIT_ID>1</CIRCUIT_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Monitoring/FES-FCU/FES-FCU.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Monitoring_OilTemp_Press_01

 

 

 

Asobo_Monitoring_Vaccum_Amp_01

 

 

 

Asobo_MPA_AS_XL

Asobo_MPA_AS_XL

This is small information display for use in hot air balloons. For an example, it is currently used by the FlyDoo in the simulation.

 

This attachment neither defines nor requires any additional behavior parameters.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, HotAirBalloon/Syride/Syride.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_MPA_ASD57

Asobo_MPA_ASD57

This is the ASD57 radio/transponder that can be used in any aircraft. For an example, it is currently used by the DG 1001 in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<RADIO_INDEX>1</RADIO_INDEX>
<XPDR_INDEX>1</XPDR_INDEX>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. RADIO_INDEX: Contains the index of the radio. It is used to identify which radio index should be used when using functions related to COM frequencies. It has to match the VCockpit parameter, explained below.
  3. XPDR_INDEX: Contains the index of the transponder. It is used to identify which transponder index should be used when using functions related to transponder frequencies. It has to match the VCockpit parameter, explained below.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Radios/ASD57/ASD57.html
  2. VCockpit01_htmlgauge00_params: This is empty by default but will require the following parameter definitions in the attached_objects.cfg (see VCockpit Parameters, above, for more information).
    1. radioIndex - This allows you to specify the radio index, which can be necessary if you want multiple instances of this panel running with separate radios.
    2. xpdrIndex - This allows you to specify the transponder index, which can be necessary if you want multiple instances of this panel running with separate transponders.

 

 

Asobo_MPA_ASX9000

Asobo_MPA_ASX9070

This is a a main display panel that can be used in any aircraft. Curently this asset is visual only and contains no behaviors or panel setup. However the model is fully finished and you can use tools like the VS Code Extension to find the node names used and create your own behaviours and panel XML if you wish.

 

 

Asobo_MPA_ASX9070

Asobo_MPA_ASX9070

This is a a main display panel that can be used in any aircraft. For an example, it is currently used by the DG 1001 in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<BOUNCE_POTENTIOMETER>1</BOUNCE_POTENTIOMETER>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. BOUNCE_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Radios/ASD57/ASD57.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_MPA_G1000_AudioPanel

Asobo_MPA_G1000_AudioPanel

This is an audio panel that is meant to be used in conjunction with one of the Garmin G1000 displays. For an example, it is currently used by the Cessna 172 Skyhawk and other default aircraft in the simulation.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_MPA_G1000_Autopilot_NoYawDamper

Asobo_MPA_G1000_Autopilot_NoYawDamper

This is a version of the Garmin G1000 display - with an autopilot panel and no yaw damper button - that can be used in any aircraft. For an example, it is currently used by the Cessna 172 Skyhawk in the simulation.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<AMBIENT_POTENTIOMETER>1</AMBIENT_POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
<ALTITUDE_ID>0</ALTITUDE_ID>
<ADDITIONAL_EMISSIVE_FACTOR>1</ADDITIONAL_EMISSIVE_FACTOR>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. AMBIENT_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. ALTITUDE_ID: Contains the index of the panel altimeter, allowing you to have multiple G1000 (or other altimeters) with their separate settings.
  5. ADDITIONAL_EMISSIVE_FACTOR: Can contain some custom calculation that will affect both the screen and the emissive decal brightness. The default value of 1 means it doesn't change the calculated value.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G1000_Autopilot_YawDamper

Asobo_MPA_G1000_Autopilot_YawDamper

This is a version of the Garmin G1000 display - with an autopilot panel and a yaw damper button - that can be used in any aircraft. For an example, it is currently used by the DA62 in the simulation.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<AMBIENT_POTENTIOMETER>1</AMBIENT_POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
<ALTITUDE_ID>0</ALTITUDE_ID>
<ADDITIONAL_EMISSIVE_FACTOR>1</ADDITIONAL_EMISSIVE_FACTOR>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. AMBIENT_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. ALTITUDE_ID: Contains the index of the panel altimeter, allowing you to have multiple G1000 (or other altimeters) with their separate settings.
  5. ADDITIONAL_EMISSIVE_FACTOR: Can contain some custom calculation that will affect both the screen and the emissive decal brightness. The default value of 1 means it doesn't change the calculated value.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default. 

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G1000_NoAutopilot

Asobo_MPA_G1000_NoAutopilot

This is a version of the Garmin G1000 display - with no autopilot panel - that can be used in any aircraft. This panel is currently not used by any default aircraft in the simulation.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<AMBIENT_POTENTIOMETER>1</AMBIENT_POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
<ADDITIONAL_EMISSIVE_FACTOR>1</ADDITIONAL_EMISSIVE_FACTOR>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. AMBIENT_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. ADDITIONAL_EMISSIVE_FACTOR: Can contain some custom calculation that will affect both the screen and the emissive decal brightness. The default value of 1 means it doesn't change the calculated value.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G1000_NoAutopilot_Alt_Hdg_Knobs

Asobo_MPA_G1000_NoAutopilot_Alt_Hdg_Knobs

This is a version of the Garmin G1000 display - without an autopilot panel but with altitude and heading knobs - that can be used in any aircraft. For an example, it is currently used by the Cessna 172 Skyhawk in the simulation.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<AMBIENT_POTENTIOMETER>1</AMBIENT_POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
<ALTITUDE_ID>0</ALTITUDE_ID>
<ADDITIONAL_EMISSIVE_FACTOR>1</ADDITIONAL_EMISSIVE_FACTOR>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. AMBIENT_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. ALTITUDE_ID: Contains the index of the panel altimeter, allowing you to have multiple G1000 (or other altimeters) with their separate settings.
  5. ADDITIONAL_EMISSIVE_FACTOR: Can contain some custom calculation that will affect both the screen and the emissive decal brightness. The default value of 1 means it doesn't change the calculated value.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G1000_NoAutopilot_NoHDG

Asobo_MPA_G1000_NoAutopilot_NoHDG

This is a version of the Garmin G1000 display - without an autopilot panel - that can be used in any aircraft. None of the default aircraft in the simulation currently use this panel.

 

Expected behavior parameters and their default values:

<POTENTIOMETER>1</POTENTIOMETER>
<AMBIENT_POTENTIOMETER>1</AMBIENT_POTENTIOMETER>
<CIRCUIT_ID>1</CIRCUIT_ID>
<ADDITIONAL_EMISSIVE_FACTOR>1</ADDITIONAL_EMISSIVE_FACTOR>
  1. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  2. AMBIENT_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. ADDITIONAL_EMISSIVE_FACTOR: Can contain some custom calculation that will affect both the screen and the emissive decal brightness. The default value of 1 means it doesn't change the calculated value.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTG1000v2/PFD/WTG1000_PFD.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G3X_Mini

Asobo_MPA_G3X_Mini

This is a "mini" version of the Garmin G3X display that can be used in any aircraft. For an example, it is currently used by the Extra 330LT in the simulation.

 

Expected behavior parameters and their default values:

CIRCUIT_ID>1</CIRCUIT_ID>
<POTENTIOMETER>1</POTENTIOMETER>
<BOUNCE_POTENTIOMETER>1</BOUNCE_POTENTIOMETER>
<HTML_EVENT_ID>1</HTML_EVENT_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  3. BOUNCE_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  4. HTML_EVENT_ID: Contains the index of this instance of the G3X mini. It can be used when there are multiples instances of the G3X to to ensure that interacting with one doesn't interact with the other. It must match with the Index in the VCockpit parameters.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/G3XTouchv2/G3XTouch.html
  2. VCockpit01_htmlgauge00_params: This is empty by default but will require the following parameter definition in the attached_objects.cfg (see VCockpit Parameters, above, for more information).
    1. Index - This allows you to specify a unique index for the display, allowing you to differentiate between multiple instances of the G3X mini (if there are more than 1), which can be use to separate their brightness levels. Must match the value given in the <HTML_EVENT_ID> behavior parameter.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_G3X_Touch

Asobo_MPA_G3X_Touch

This is a Garmin G3X Touch display that can be used in any aircraft. For an example, it is currently used by the CubCrafters X Cub in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<BOUNCE_POTENTIOMETER>1</BOUNCE_POTENTIOMETER>
<BACKLIGHT_ID>1</BACKLIGHT_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. BOUNCE_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen (the brightness will be written within the potentiometer which can then be used within the lights definition).
  3. BACKLIGHT_ID: Contains the index of this instance of the G3X. It can be used when there are multiples instances of the G3X to control their backlighting separately. It must match with the Index in the VCockpit parameters.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/G3XTouchv2/G3XTouch.html
  2. VCockpit01_htmlgauge00_params: This is empty by default but will require the following parameter definition in the attached_objects.cfg (see VCockpit Parameters, above, for more information).
    1. Index - This allows you to specify a unique index for the display, allowing you to differentiate between multiple instances of the G3X (if there are more than 1), which can be use to separate their brightness levels. Must match the value given in the <BACKLIGHT_ID> behavior parameter.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_GNS430

Asobo_MPA_GNS430

This is a GPS radio with NAV / COM that can be used in any aircraft. For an example, it is currently used by the Skyship 600 and other aircraft in the simulation.

 

Expected behavior parameters and their default values:

<COM_INDEX>1</COM_INDEX>
<NAV_INDEX>1</NAV_INDEX>
<CIRCUIT_ID>1</CIRCUIT_ID>
<AVIONICS_CIRCUIT_ID>'avionics'_n</AVIONICS_CIRCUIT_ID>
<POTENTIOMETER>1</POTENTIOMETER>
<SCREEN_EMISSIVE_CODE>(L:AS430_ManualBrightness_Value, Percent over 100) (A:AMBIENT LIGHT SENSOR, Number) 0 4000 0.001 1 (F:MapRange) (L:AS430_ManualBrightness_Enabled, Bool) ?</SCREEN_EMISSIVE_CODE>
  1. COM_INDEX: Contains the index of the COM channel (between 1 and 3).
  2. NAV_INDEX: Contains the index of the NAV channel (between 1 and 3).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. AVIONICS_CIRCUIT_ID: Contains the index of the avionics circuit to use. For reasons related to backwards compatibility, you have to link the state of the CIRCUIT_ID to the avionics + the volume of the COM, which is why this parameter is used.
  5. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  6. SCREEN_EMISSIVE_CODE: This can be used to override the default logic of the emissive of the screen. If not set, the default logic will automatically tune the brightness based on the current light conditions.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTGNSv2/WT430/WT430.html
  2. VCockpit01_htmlgauge00_params: This is empty by default but will require the following parameter definition in the attached_objects.cfg (see VCockpit Parameters, above, for more information).
    1. NavIndex - Sets the NAV channel for the JavaScript side of the panel.
    2. ComIndex - Sets the COM channel for the JavaScript side of the panel.
  3. NOTE: There are many other additional parameters which can be used with this panel, and these are described here: Working Title GNS 430 and 530 Overview

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_GNS530

Asobo_MPA_GNS530

This is a GPS radio with NAV / COM that can be used in any aircraft. For an example, it is currently used by the Cessna 172 Classic in the simulation.

 

Expected behavior parameters and their default values:

<COM_INDEX>1</COM_INDEX>
<NAV_INDEX>1</NAV_INDEX>
<CIRCUIT_ID>1</CIRCUIT_ID>
<POTENTIOMETER>1</POTENTIOMETER>
<SCREEN_EMISSIVE_CODE>(L:AS530_ManualBrightness_Value, Percent over 100) (A:AMBIENT LIGHT SENSOR, Number) 1 4000 0.001 1 (F:MapRange) (L:AS530_ManualBrightness_Enabled, Bool) ?</SCREEN_EMISSIVE_CODE>
  1. COM_INDEX: Contains the index of the COM channel (between 1 and 3).
  2. NAV_INDEX: Contains the index of the NAV channel (between 1 and 3).
  3. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  4. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.
  5. SCREEN_EMISSIVE_CODE: This can be used to override the default logic of the emissive of the screen. If not set, the default logic will automatically tune the brightness based on the current light conditions.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTGNSv2/WT530/WT530.html
  2. VCockpit01_htmlgauge00_params: This is empty by default but will require the following parameter definition in the attached_objects.cfg (see VCockpit Parameters, above, for more information).
    1. NavIndex - Sets the NAV channel for the JavaScript side of the panel.
    2. ComIndex - Sets the COM channel for the JavaScript side of the panel.
  3. NOTE: There are many other additional parameters which can be used with this panel, and these are described here: Working Title GNS 430 and 530 Overview.

 

For more information and additional setup details please see the following page on the MSFS Avionics Framework website:

 

 

Asobo_MPA_GTN650

Asobo_MPA_GNS530

This is a transponder that can be used in any aircraft. For an example, it is currently used by the Cabri and other aircraft in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<COM_ID>1</COM_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. COM_ID: Contains the index of the COM channel (between 1 and 3).

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, NavSystems/WTGNSv2/WT530/WT530.html
  2. VCockpit01_htmlgauge00_params

 

 

Asobo_Radar_Altimeter_AS416

 

 

 

Asobo_Radio_Com_AS196

Asobo_Radio_Com_AS196

This is a simple radio that can be used in any aircraft. For an example, it is currently used by the Skyship 600 in the simulation.

 

Expected behavior parameters and their default values:

<COM_ID>1</COM_ID>
<CIRCUIT_ID>1</CIRCUIT_ID>
  1. COM_ID: Contains the index of the COM channel (between 1 and 3).
  2. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Helicopters/AS650/dist/AS650.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Radio_Com_G225

Asobo_Radio_Com_G225

This is a Garmin G225 radio that can be used in any aircraft. For an example, it is currently used by the AT802 in the simulation.

 

Expected behavior parameters and their default values:

<COM_ID>1</COM_ID>
<CIRCUIT_ID>1</CIRCUIT_ID>
  1. COM_ID: Contains the index of the com channel (between 1 and 3).
  2. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Radios/AS225/AS225.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Slip_Indicator_01

 

 

 

Asobo_Tablet_Generic_10_9

Asobo_Tablet_Generic_10_9

This is a generic large EFB tablet. This SimAttachment is "plug and play" and does not require any additional setup. Simply add it to the interior of your aircraft and you should have a fully functional basic EFB.

 

 

Asobo_Tablet_Generic_8_3

Asobo_Tablet_Generic_8_3

This is a generic small EFB tablet. This SimAttachment is "plug and play" and does not require any additional setup. Simply add it to the interior of your aircraft and you should have a fully functional basic EFB.

 

 

Asobo_Tachometer_01

 

 

 

Asobo_Transponder_AS21

Asobo_Transponder_AS21

This is a small transponder that can be used in any aircraft. For an example, it is currently used by the Cabri in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Transponders/AS21/AS21.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Transponder_AS76C

Asobo_Transponder_AS76C

This is a simple transponder that can be used in any aircraft. For an example, it is currently used by the Skyship 600 in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<POTENTIOMETER>1</POTENTIOMETER>
<DECAL_POTENTIOMETER>7</DECAL_POTENTIOMETER>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the screen.
  3. DECAL_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Transponders/KT76C/KT76C.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Transponder_G330

Asobo_Transponder_G330

This is a simple transponder that can be used in any aircraft. For an example, it is currently used by the AT 802 in the simulation.

 

Expected behavior parameters and their default values:

<CIRCUIT_ID>1</CIRCUIT_ID>
<DECAL_POTENTIOMETER>7</DECAL_POTENTIOMETER>
  1. CIRCUIT_ID: Contains the index of the circuit to use to verify that the panel is powered. The name of the circuit can be used if using the 'Name'_n syntax.
  2. DECAL_POTENTIOMETER: Contains the index of the potentiometer to use for the brightness of the emissive component of the decals.

 

The supported VCockpit parameters are the standard ones:

  1. VCockpit01_htmlgauge00_file, Generic/Transponders/AS330/AS330.html
  2. VCockpit01_htmlgauge00_params: This is empty by default.

 

 

Asobo_Turn_Coordinator_01

 

 

 

Asobo_Turn_Coordinator_02

 

 

 

Asobo_VSI_01

 

 

 

Asobo_VSI_02

 

 

 

Asobo_VSI_03

 

 

 

Asobo_VSI_AS8

 

 

 

 

 

Related Topics

  1. Modular SimObjects
  2. Modular Aircraft SimObjects
  3. Models And Textures
  4. CFG Files General Information