fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Aircraft/Instruments/dme.xml

578 lines
14 KiB
XML
Raw Normal View History

I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<?xml version="1.01"?>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<!--
Default DME instrument.
Started summer 2000 by David Megginson, david@megginson.com.
This is an instrument configuration file for the open-source flight
simulator FlightGear (www.flightgear.org). The file is an XML-encoded
FlightGear property list defining the instrument's layers and actions.
Each instrument is composed of layers stacked on top of each other.
A layer may be a texture (with transparent parts to show the layers
underneath), text, or a special layer that switches between two
others (say, to turn an indicator light on or off). Each layer can
move independently in proportion to a property value, and text
can be generated from property values as well: all of the layer's
movements are defined as transformations.
Actions are hotspots on the instrument that will respond to a mouse
click. Actions always modify the values of properties, either by
adjusting them, toggling them, or swaping them with other
properties' values.
-->
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<!--
Dave Perry added a check for dme voltage greater than 8.0 volts so
that the dme text does not light up if there is no power supplied.
This allows more realistic implementation of master switches or
avionics master switches as is done in pa24-electrical.nas. This
change has no affect on the c172p since this voltage is 28 volts
all the time in that electrical system.
-->
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<PropertyList>
<name>DME</name>
<w-base>128</w-base>
<h-base>64</h-base>
<layers>
<layer>
<name>background</name>
<texture>
<path>Aircraft/Instruments/Textures/navcom-radios.rgb</path>
<x1>0.0</x1>
<x2>0.49609375</x2>
<y1>0.0</y1>
<y2>0.23828125</y2>
</texture>
</layer>
<layer>
<name>distance to station</name>
<type>switch</type>
<w>128</w>
<h>64</h>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<layer>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">0</value>
</equals>
</condition>
<type>group</type>
</layer>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
<not>
<property>/instrumentation/dme/in-range</property>
</not>
</and>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
</condition>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<name>display</name>
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>literal</type>
<text>---.--</text>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<name>display</name>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
<greater-than>
<property>/instrumentation/dme/indicated-distance-nm</property>
<value type="double">999.99</value>
</greater-than>
</and>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</condition>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>literal</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<text>999.99</text>
</chunk>
</chunks>
</layer>
<layer>
<name>display</name>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<condition>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
</condition>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
<property>/instrumentation/dme/indicated-distance-nm</property>
<format>%5.1f</format>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
<transformations>
<transformation>
<type>x-shift</type>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<offset>-50</offset>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</transformation>
<transformation>
<type>y-shift</type>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<offset>11</offset>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</transformation>
</transformations>
</layer>
<layer>
<name>ground speed towards station</name>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<condition>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
</condition>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<type>switch</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<layer>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">0</value>
</equals>
</condition>
<type>group</type>
</layer>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
<not>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<property>/instrumentation/dme/in-range</property>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
</not>
</and>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
</condition>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<name>display</name>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>literal</type>
<text>---</text>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<greater-than>
<property>/instrumentation/dme/indicated-ground-speed-kt</property>
<value type="double">999</value>
</greater-than>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
</and>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</condition>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<name>display</name>
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>literal</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<text>999</text>
</chunk>
</chunks>
</layer>
<layer>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<condition>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
</condition>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
<property>/instrumentation/dme/indicated-ground-speed-kt</property>
<format>%3.0f</format>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<transformations>
<transformation>
<type>y-shift</type>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<offset>11</offset>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</transformation>
</transformations>
</layer>
<layer>
<name>time to station</name>
<type>switch</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<layer>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">0</value>
</equals>
</condition>
<type>group</type>
</layer>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<not>
<property>/instrumentation/dme/in-range</property>
</not>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
</and>
Modified to work with changed "switch" layer.
2003-03-09 03:41:48 +00:00
</condition>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<name>display</name>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>literal</type>
<text>--</text>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<condition>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<and>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<greater-than>
<property>/instrumentation/dme/indicated-time-min</property>
<value type="double">99</value>
</greater-than>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
</and>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</condition>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<name>display</name>
<type>text</type>
This one should use the LED font as well.
2002-02-20 04:07:56 +00:00
<font>led</font>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<point-size>6</point-size>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>literal</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<text>99</text>
</chunk>
</chunks>
</layer>
<layer>
I made a minor change to one file in the c172p that accommodates a feature I added to the navcom-kx155.xml and the dme.xml in the Instruments folder. I wanted to leave the frequencies, etc. on these dark until there was voltage applied to /systems/electrical/outputs/nav. This was accomplished by adding a param and property alias pointing to the appropriate value. Since the c172p "always" applies 28 volts, this made no change in the c172p, but allowed me to model the avionics master and battery master realisticly in pa24-electrical.nas. I put in comments explaining this at the change points. There is a useful "help > aircraft help" that walks you through the start procedure and lists the key bindings as well as the key to "light up" the hot spots.
2006-02-12 17:31:21 +00:00
<condition>
<greater-than>
<property>/systems/electrical/outputs/dme</property>
<value>8.0</value>
</greater-than>
</condition>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>1.0</red>
<green>0.5</green>
<blue>0.0</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
<property>/instrumentation/dme/indicated-time-min</property>
<format>%02.0f</format>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</chunk>
</chunks>
</layer>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<transformations>
<transformation>
<type>y-shift</type>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<offset>11</offset>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</transformation>
<transformation>
<type>x-shift</type>
The new led font is now antialiased (`a la Andy) and has twice the design size (character height) of the old one. Advantages: - displays . and : correctly with less space around, and digits with more space around (using Andy's improvements to plib) - small text becomes much more legible (-> clock, AP-altitude) - the font contains pretty much every character that can be displayed on a seven segment display, so it might be more useful for future instruments.
2002-11-02 00:23:46 +00:00
<offset>33</offset>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</transformation>
</transformations>
</layer>
<layer>
<name>knob</name>
<texture>
<path>Aircraft/Instruments/Textures/navcom-radios.rgb</path>
<x1>0.53125</x1>
<x2>0.59765625</x2>
<y1>0.05859375</y1>
<y2>0.1484375</y2>
</texture>
<w>16</w>
<h>20</h>
<transformations>
<transformation>
<type>y-shift</type>
<offset>-24</offset>
</transformation>
<transformation>
<type>rotation</type>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<property>/instrumentation/dme/switch-position</property>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<min>0</min>
<max>3</max>
<scale>45</scale>
<offset>-90</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>-4.0</offset>
</transformation>
</transformations>
</layer>
</layers>
<actions>
before the big instrumentation rewrite dme.cxx cared for the initial mode according to the switch position. Now dme.cxx is more generic and can't make these settings any more -- and doesn't. So the dme didn't display anything even if the knob was on. The initialization has now to be done in the dme.xml file. (Button-less actions are fired at init time and then thrown away.)
2006-02-02 00:07:11 +00:00
<action>
<name>Setup</name>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">1</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
<value>/instrumentation/nav[0]/frequencies/selected-mhz</value>
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
<value>/instrumentation/dme/frequencies/selected-mhz</value>
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/selected-mhz</property>
<property>/instrumentation/nav[0]/frequencies/selected-mhz</property>
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">3</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
<value>/instrumentation/nav[1]/frequencies/selected-mhz</value>
</binding>
</action>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<action>
<name>Rotate knob left</name>
<button>0</button>
<x>-32</x>
<y>-32</y>
<w>32</w>
<h>32</h>
<binding>
<command>property-adjust</command>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<property>/instrumentation/dme/switch-position</property>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<step>-1</step>
<min>0</min>
<max>3</max>
<wrap>0</wrap>
</binding>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">1</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
Roy Vegard Ovesen: I've finished the emigration of the radiostack, and I've also removed it completely. It turned out that the comm radio is completely implemented in the ATC subsystem. I've changed the affected ATC files to point to /instrumentation/com, but I guess that the maintainer of the ATC code should decide wether to make it configureable, and how. I also had to change some files in Network and Main. The changes in network should be obvious, but the changes in Main were a bit suspect. The files included radiostack.hxx, but they weren't directly depending on radiostack-hxx. They were depending on other files that were included by radiostack.hxx. I got it to compile, but I'm not sure if I included the correct directly depending file. For the data directory I changed every occurrence of /radios/ with /instrumentation/ with this simple one-liner that I found on the net: find -name '*.xml' -type f | xargs perl -pi -e 's/\/radios\//\/instrumentation\//g' Instead of me sending all the files that got changed by this I suggest that you execute the one-liner yourself. Of course I can not guarantee that this will work perfectly, but I considered hand editing to be not an option (I'm lazy). I don't want to test every aircraft to see if everything still works, I think it's better to wait and see if anyone complaints about broken nav radios/instruments.
2004-12-03 21:25:48 +00:00
<value>/instrumentation/nav[0]/frequencies/selected-mhz</value>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
<value>/instrumentation/dme/frequencies/selected-mhz</value>
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/selected-mhz</property>
Roy Vegard Ovesen: I've finished the emigration of the radiostack, and I've also removed it completely. It turned out that the comm radio is completely implemented in the ATC subsystem. I've changed the affected ATC files to point to /instrumentation/com, but I guess that the maintainer of the ATC code should decide wether to make it configureable, and how. I also had to change some files in Network and Main. The changes in network should be obvious, but the changes in Main were a bit suspect. The files included radiostack.hxx, but they weren't directly depending on radiostack-hxx. They were depending on other files that were included by radiostack.hxx. I got it to compile, but I'm not sure if I included the correct directly depending file. For the data directory I changed every occurrence of /radios/ with /instrumentation/ with this simple one-liner that I found on the net: find -name '*.xml' -type f | xargs perl -pi -e 's/\/radios\//\/instrumentation\//g' Instead of me sending all the files that got changed by this I suggest that you execute the one-liner yourself. Of course I can not guarantee that this will work perfectly, but I considered hand editing to be not an option (I'm lazy). I don't want to test every aircraft to see if everything still works, I think it's better to wait and see if anyone complaints about broken nav radios/instruments.
2004-12-03 21:25:48 +00:00
<property>/instrumentation/nav[1]/frequencies/selected-mhz</property>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</binding>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</action>
<action>
<name>Rotate knob right</name>
<button>0</button>
<x>0</x>
<y>-32</y>
<w>32</w>
<h>32</h>
<binding>
<command>property-adjust</command>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<property>/instrumentation/dme/switch-position</property>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
<step>1</step>
<min>0</min>
<max>3</max>
<wrap>0</wrap>
</binding>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">1</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
Roy Vegard Ovesen: I've finished the emigration of the radiostack, and I've also removed it completely. It turned out that the comm radio is completely implemented in the ATC subsystem. I've changed the affected ATC files to point to /instrumentation/com, but I guess that the maintainer of the ATC code should decide wether to make it configureable, and how. I also had to change some files in Network and Main. The changes in network should be obvious, but the changes in Main were a bit suspect. The files included radiostack.hxx, but they weren't directly depending on radiostack-hxx. They were depending on other files that were included by radiostack.hxx. I got it to compile, but I'm not sure if I included the correct directly depending file. For the data directory I changed every occurrence of /radios/ with /instrumentation/ with this simple one-liner that I found on the net: find -name '*.xml' -type f | xargs perl -pi -e 's/\/radios\//\/instrumentation\//g' Instead of me sending all the files that got changed by this I suggest that you execute the one-liner yourself. Of course I can not guarantee that this will work perfectly, but I considered hand editing to be not an option (I'm lazy). I don't want to test every aircraft to see if everything still works, I think it's better to wait and see if anyone complaints about broken nav radios/instruments.
2004-12-03 21:25:48 +00:00
<value>/instrumentation/nav[0]/frequencies/selected-mhz</value>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
<value>/instrumentation/dme/frequencies/selected-mhz</value>
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">2</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/selected-mhz</property>
Roy Vegard Ovesen: I've finished the emigration of the radiostack, and I've also removed it completely. It turned out that the comm radio is completely implemented in the ATC subsystem. I've changed the affected ATC files to point to /instrumentation/com, but I guess that the maintainer of the ATC code should decide wether to make it configureable, and how. I also had to change some files in Network and Main. The changes in network should be obvious, but the changes in Main were a bit suspect. The files included radiostack.hxx, but they weren't directly depending on radiostack-hxx. They were depending on other files that were included by radiostack.hxx. I got it to compile, but I'm not sure if I included the correct directly depending file. For the data directory I changed every occurrence of /radios/ with /instrumentation/ with this simple one-liner that I found on the net: find -name '*.xml' -type f | xargs perl -pi -e 's/\/radios\//\/instrumentation\//g' Instead of me sending all the files that got changed by this I suggest that you execute the one-liner yourself. Of course I can not guarantee that this will work perfectly, but I considered hand editing to be not an option (I'm lazy). I don't want to test every aircraft to see if everything still works, I think it's better to wait and see if anyone complaints about broken nav radios/instruments.
2004-12-03 21:25:48 +00:00
<property>/instrumentation/nav[0]/frequencies/selected-mhz</property>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</binding>
<binding>
<condition>
<equals>
<property>/instrumentation/dme/switch-position</property>
<value type="int">3</value>
</equals>
</condition>
<command>property-assign</command>
<property>/instrumentation/dme/frequencies/source</property>
Roy Vegard Ovesen: I've finished the emigration of the radiostack, and I've also removed it completely. It turned out that the comm radio is completely implemented in the ATC subsystem. I've changed the affected ATC files to point to /instrumentation/com, but I guess that the maintainer of the ATC code should decide wether to make it configureable, and how. I also had to change some files in Network and Main. The changes in network should be obvious, but the changes in Main were a bit suspect. The files included radiostack.hxx, but they weren't directly depending on radiostack-hxx. They were depending on other files that were included by radiostack.hxx. I got it to compile, but I'm not sure if I included the correct directly depending file. For the data directory I changed every occurrence of /radios/ with /instrumentation/ with this simple one-liner that I found on the net: find -name '*.xml' -type f | xargs perl -pi -e 's/\/radios\//\/instrumentation\//g' Instead of me sending all the files that got changed by this I suggest that you execute the one-liner yourself. Of course I can not guarantee that this will work perfectly, but I considered hand editing to be not an option (I'm lazy). I don't want to test every aircraft to see if everything still works, I think it's better to wait and see if anyone complaints about broken nav radios/instruments.
2004-12-03 21:25:48 +00:00
<value>/instrumentation/nav[1]/frequencies/selected-mhz</value>
Use the new DME support under /instrumentation/ instead of the old support under /radios/. The display now goes dark when the switch is turned off. The switch position is now handled entirely within the XML -- the C++ code is generic, so that other DME receiver types can also be modelled.
2003-03-09 04:13:18 +00:00
</binding>
Instruments are now consolidated in a single directory. Textures are now more organized and usefully named.
2001-12-12 14:20:38 +00:00
</action>
</actions>
</PropertyList>
Copy permalink