47
edits
m (→Generic transponder: Update volts tag) |
(→Generic transponder: updated with Mode-S related documentation) |
||
Line 62: | Line 62: | ||
<encoder-path type="string">/instrumentation/altimeter</encoder-path> | <encoder-path type="string">/instrumentation/altimeter</encoder-path> | ||
<kt70-compatibility type="bool">0</kt70-compatibility> | <kt70-compatibility type="bool">0</kt70-compatibility> | ||
<auto-ground>...</auto-ground> <!-- input for Mode-S automatic GND bit --> | |||
<airspeed-path>...</airspeed-path> | |||
<mach-path>...</mach-path> | |||
</transponder> | </transponder> | ||
</syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead. | </syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead. | ||
The following is a copy of a comment in instrument source, explaining the use of Mode-S related properties | |||
<code> | |||
// Mode-S transponders (configured with mode = 2) can transmit a ground bit to | |||
// indicate ground operation. If auto-ground is not defined, the ground bit is | |||
// switched manually by setting the transponder knob to GND. If auto-ground is | |||
// defined, the transponder simulates automatic switching of the ground bit | |||
// using the value of the property defined in auto-ground. | |||
// | |||
// For a squat switch, use "/gear/gear/wow". For automatic switching based on | |||
// airspeed, use a property rule to make a new boolean property that indicates, | |||
// for example, airspeed < 80, and reference your new property in auto-ground. | |||
// | |||
// Note that Mode-A and Mode-C transponders do not transmit a ground bit, even | |||
// if the transponder knob is set to the GND position. | |||
// | |||
// Mode-S transponders also transmit indicated airspeed and Mach number. The | |||
// default sources are "/instrumentation/airspeed-indicator/indicated-speed-kt" | |||
// and ".../indicated-mach", but this can be changed by setting "airspeed-path" | |||
// and "mach-path" properties respectively as shown above. | |||
</code> | |||
=== | ==Related content== | ||
* [ | ===Wiki articles=== | ||
* [ | *[[Howto:Develop an aircraft transponder in Nasal]] – Most probably obsolete | ||
* [ | *[[FLARM]] | ||
*[[Multiplayer protocol]] – The IDs 1501-1503 are earmarked for transmitting transponder properties | |||
*[[OpenRadar: Transponder]] | |||
*[[Traffic alert and collision avoidance system]] | |||
=== | ===Forum topics=== | ||
* [https:// | *[https://forum.flightgear.org/viewtopic.php?f=4&t=31492 Transponder properties over MP] (January-June 2017) | ||
* [https:// | *[https://forum.flightgear.org/viewtopic.php?f=75&t=19826 Transponder over network] (April-December 2018) | ||
*[https://forum.flightgear.org/viewtopic.php?f=4&t=6395 Transponder] (November 2009-December 2010) | |||
=== Source code === | ===Developer mailing list=== | ||
* {{flightgear source|src/Instrumentation/transponder.hxx}} | *[https://sourceforge.net/p/flightgear/mailman/message/30785263/ <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Improve tranponder instrument] (Apr 2009) | ||
* {{flightgear source|src/Instrumentation/transponder.cxx}} | *[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1388915221.2195.15.camel%40duter.localdomain/#msg31810053 <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Transponder Ident not transmitted via MP Protocol?] (Jan-Feb 2014) | ||
===Source code=== | |||
*{{flightgear source|src/Instrumentation/transponder.hxx}} | |||
*{{flightgear source|src/Instrumentation/transponder.cxx}} | |||
[[Category:Aircraft enhancement]] | [[Category:Aircraft enhancement]] | ||
[[Category:Aircraft instruments]] | [[Category:Aircraft instruments]] |
edits