Showing 3 changed files with 7 additions and 3 deletions
+2 -1
Nasal/display.nas
... ...
@@ -28,6 +28,8 @@ var displayClass = {
28 28
             m.MFDMapNavDisplay = MapNavDisplay.new(m.display);
29 29
         }
30 30
 
31
+        m._ias_vne = getprop('/instrumentation/zkv1000/alerts/Vne');
32
+
31 33
         return m;
32 34
     },
33 35
 #}}}
... ...
@@ -556,7 +558,6 @@ var displayClass = {
556 558
     },
557 559
     _last_ias_kt : 0,
558 560
     _last_ias_s : systime(),
559
-    _ias_vne : 999,
560 561
     _ias_already_exceeded : 0,
561 562
 #}}}
562 563
 
+3 -2
README.md
... ...
@@ -72,6 +72,7 @@ Please report bug at <seb.marque@free.fr>.
72 72
   * Radio stack, including ID for NAV
73 73
   * windows management: selectable items ![][done], modifiable items ![][done], scrolling ![][done]
74 74
   * display of V-speeds in ruler: Vx, Vy, Vr and Vglide (specific for aircraft, see installation instruction)
75
+  * some aircraft specific data to retrieve from aircraft XML files (VNE, etc)
75 76
 * ![][90%]
76 77
   * Bearing needs some checks to be sure it shows the correct information
77 78
   * XPDR: emergency code depending of the country (eg.: 1200 for US, 7700 for Europe), should be set in settings
... ...
@@ -91,7 +92,6 @@ Please report bug at <seb.marque@free.fr>.
91 92
   * multikey for every part of the device (actually only power on)
92 93
 * ![][0%] (TODO list, unsorted)
93 94
   * CDI/GPS: scale depending of the flight phase
94
-  * some aircraft specific data to retrieve from aircraft XML files (VNE, etc)
95 95
   * angle of attack display
96 96
   * Alerts
97 97
   * Flight planning (MFD)
... ...
@@ -121,7 +121,7 @@ Actually this is where everything begins, please have a look at this code, it wo
121 121
 Specifics values for aircraft can be set via the aircraft configuration, in the `<instrumentation>` section, just add a section `<zkv1000>` and set here the needed values.
122 122
 
123 123
 ### Vspeeds
124
-To see the Vspeeds bugs, set the corresponding V-speeds in knots by adding in your `<instrumentation><zkv1000>` section the following lines (here are the numbers for the Lancair-235, ![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/12/Achtung-orange.svg/32px-Achtung-orange.svg.png) values are not to be used in real life).
124
+To see the Vspeeds bugs or the IAS background color change (Vne), set the corresponding V-speeds in knots by adding in your `<instrumentation><zkv1000>` section the following lines (here are the numbers for the Lancair-235, ![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/12/Achtung-orange.svg/32px-Achtung-orange.svg.png) values are not to be used in real life).
125 125
 If not set, defaults to 999 knots
126 126
 
127 127
         <alerts>
... ...
@@ -129,6 +129,7 @@ If not set, defaults to 999 knots
129 129
           <Vy>110</Vy>
130 130
           <Vr>65</Vr>
131 131
           <Vglide>80</Vglide>
132
+          <Vne>170</Vne>
132 133
         </alerts>
133 134
 
134 135
 ## 3D models
+2
zkv1000.nas
... ...
@@ -66,6 +66,8 @@ var init_props = func {
66 66
     alerts.getNode('Vr', 1).setIntValue(v != nil ? v : 999);
67 67
     v = getprop('/instrumentation/zkv1000/alerts/Vglide');
68 68
     alerts.getNode('Vglide', 1).setIntValue(v != nil ? v : 999);
69
+    v = getprop('/instrumentation/zkv1000/alerts/Vne');
70
+    alerts.getNode('Vne', 1).setIntValue(v != nil ? v : 999);
69 71
 
70 72
     afcs = zkv.getNode('afcs',1);
71 73
     afcs.getNode('fd-bars-visible',1).setBoolValue(0);