fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Protocol/acms.xml

103 lines
2.2 KiB
XML
Raw Permalink Normal View History

Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
<?xml version="1.0"?>
<PropertyList>
<generic>
<input>
<line_separator>newline</line_separator>
<var_separator>tab</var_separator>
<chunk>
<name>time GMT (hhmmss)</name>
<type>string</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/sim/time</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>pressure altitude (feet)</name>
<type>int</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/position/altitude-ft</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>indicated speed (kt)</name>
<type>int</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/velocities/airspeed-kt</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>climb rate (ft/mn)</name>
<type>int</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<factor>0.01666667</factor>
<node>/fdm/acms/velocities/vertical-speed-fps</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>pitch att (deg)</name>
<type>float</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<factor>-0.0174533</factor>
<node>/fdm/acms/orientation/pitch-rad</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>roll att (deg)</name>
<type>float</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<factor>0.0174533</factor>
<node>/fdm/acms/orientation/roll-rad</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>magnetic heading (deg)</name>
<type>float</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<factor>0.0174533</factor>
<node>/fdm/acms/orientation/heading-rad</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>latteral acceleration (G's)</name>
<type>float</type>
<factor>32.2</factor>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/accelerations/ned/east-accel-fps_sec</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>longitudinal acceleration (G's)</name>
<type>float</type>
<factor>32.2</factor>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/accelerations/ned/north-accel-fps_sec</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>vertical acceleration (G's)</name>
<type>float</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<factor>32.2</factor>
<offset>-32.2</offset>
<node>/fdm/acms/accelerations/ned/down-accel-fps_sec</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>outside air temperarure (degC)</name>
<type>int</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/environment/temperature-degc</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>Weight on Wheels ("GND"/"AIR")</name>
boolean has officially become bool as a type (but boolean will internally still be supported)
2009-06-30 07:40:44 +00:00
<type>bool</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/gear/wow</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
<chunk>
<name>date (yy/mm/dd)</name>
<type>string</type>
Directly updating the right properties doesn't work when not uing --fdm=null, create a separate branch instead.
2004-10-20 09:20:35 +00:00
<node>/fdm/acms/sim/date</node>
Add a protocol for the ACMS protocol which seems to be used as an output format for black-box data flight data. This configuration does not work directly since there is no FDM available that reads the accelerations from the property tree and translates them into actual lat/lon positions.
2004-10-16 11:32:56 +00:00
</chunk>
</input>
</generic>
</PropertyList>
Copy permalink