User Tools

Site Tools


aircraft:tmd:inputs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
aircraft:tmd:inputs [2019/07/20 17:07] jhaircraft:tmd:inputs [2019/07/20 17:09] jh
Line 724: Line 724:
 </code> </code>
  
-===== Digital States =====+===== Other Inputs =====
  
 ==== input_binary ==== ==== input_binary ====
Line 772: Line 772:
 The input_discrete has an output to the tmd only (''Output''). The input_discrete has an output to the tmd only (''Output'').
  
-==== input_event ====+==== input_discrete_cyclic ====
  
-Receives messages and then fires events with the received message value.+The input_discrete_cyclic works exactly like the ''input_discrete'' but with the addition that is loops back around to the beginning of the range when the value is stepped beyond the range limitsE.g. it cycles through the list of display pages
  
-  * ''Input'' is the message name +<code>            <[input_discrete_cyclic][ECAMPageManuallyTuned][] 
-  * ''InputValue'' filters the messages for a specific value, leave the line of code away to not filter for any values +                <[string8][Input][ECAM.Page]> 
-  * All events in the ''Events'' list are triggered once a message is received +                <[string8][InputEnable][ClockOn.Output]> 
- +                <[string8][Range][ 0.0 11.0 ]> 
-The use of the ''input_event'' class is described further in the [[aircraft:tmd:events|TMD Events]] topic. +                <[float64][Value][0.0]> 
- +                <[bool][Toggle][true]>
-<code>            <[input_event][Button_Pressed][] +
-                <[string8][Input][Controls.Button]> +
-                <[string8][Events][ DEV0.Trigger ]> +
-            > +
-            <[input_event][Button_Pressed][] +
-                <[string8][Input][Controls.Button]> +
-                <[float64][InputValue][1.0]> +
-                <[string8][Events][ DEV0.Trigger ]>+
             >             >
 </code> </code>
  
-==== input_active ====+==== input_discrete_momentary ====
  
-Outputs 1.to the tmd as long as lever is grabbed or a button is depressed.+Again very similar to the ''input_discrete'' the input_discrete_momentary does pretty much the same with the difference being that the last value in the range cannot stay selectedIt returns to the second to last value after short time when the input is no longer active.
  
-<code>            <[input_active][ButtonDepressed][] +> Used for the magneto switch and starter or a hold-to-test switch. 
-                <[string8][Input][Controls.Button]> + 
-                <[float64][InputValue][1.0]>+<code>            <[input_discrete_momentary][MagnetosSwitch][] 
 +                <[string8][Input][Controls.Magnetos]> 
 +                <[tmvector2d][Range][ 0.0 4.0 ]> 
 +                <[float64][Value][3.0]> 
 +                <[string8][EventsUp][ MagnetoSwitchSound.Trigger ]> 
 +                <[string8][EventsDown][ MagnetoSwitchSound.Trigger ]>
             >             >
 </code> </code>
  
- 
-===== Other Inputs ===== 
  
 ==== input_cyclic ==== ==== input_cyclic ====
Line 864: Line 859:
 </code> </code>
  
-==== input_discrete_cyclic ====+==== input_event ====
  
-The input_discrete_cyclic works exactly like the ''input_discrete'' but with the addition that is loops back around to the beginning of the range when the value is stepped beyond the range limits. E.g. it cycles through the list of display pages+Receives messages and then fires events with the received message value. 
 + 
 +  * ''Input'' is the message name 
 +  * ''InputValue'' filters the messages for a specific value, leave the line of code away to not filter for any values 
 +  * All events in the ''Events'' list are triggered once a message is received 
 + 
 +The use of the ''input_event'' class is described further in the [[aircraft:tmd:events|TMD Events]] topic.
  
-<code>            <[input_discrete_cyclic][ECAMPageManuallyTuned][] +<code>            <[input_event][Button_Pressed][] 
-                <[string8][Input][ECAM.Page]> +                <[string8][Input][Controls.Button]> 
-                <[string8][InputEnable][ClockOn.Output]> +                <[string8][Events][ DEV0.Trigger ]> 
-                <[string8][Range][ 0.0 11.0 ]> +            > 
-                <[float64][Value][0.0]> +            <[input_event][Button_Pressed][] 
-                <[bool][Toggle][true]>+                <[string8][Input][Controls.Button]> 
 +                <[float64][InputValue][1.0]> 
 +                <[string8][Events][ DEV0.Trigger ]>
             >             >
 </code> </code>
  
-==== input_discrete_momentary ====+==== input_active ====
  
-Again very similar to the ''input_discrete'' the input_discrete_momentary does pretty much the same with the difference being that the last value in the range cannot stay selectedIt returns to the second to last value after short time when the input is no longer active.+Outputs 1.to the tmd as long as lever is grabbed or a button is depressed.
  
-> Used for the magneto switch and starter or a hold-to-test switch. +<code>            <[input_active][ButtonDepressed][] 
- +                <[string8][Input][Controls.Button]> 
-<code>            <[input_discrete_momentary][MagnetosSwitch][] +                <[float64][InputValue][1.0]>
-                <[string8][Input][Controls.Magnetos]> +
-                <[tmvector2d][Range][ 0.0 4.0 ]> +
-                <[float64][Value][3.0]> +
-                <[string8][EventsUp][ MagnetoSwitchSound.Trigger ]> +
-                <[string8][EventsDown][ MagnetoSwitchSound.Trigger ]>+
             >             >
 </code> </code>
- 
  
aircraft/tmd/inputs.txt · Last modified: 2022/07/19 21:02 by jh