@@ -52,81 +52,40 @@ Note: this is not because the progress bar show 100% that it means it is 100% bu

 Please report bug at <zkv1000@seb.lautre.net>.

 * ![][100%]

-  * Basic Flight Instrumentation: AI, IAS, ALT, HDG

-  * Wind data widget

-  * trends for altitude and speed (6s prevision)

-  * TAS and Ground Speed display

-  * VSI

-  * 3D knobs rotate

-  * map display on inflight page (with online maps downloading and caching)

-  * display of NavAids on map

-  * XPDR from SoftKeys and knob, with respect of delays from the manual

-  * Selected altitude bug (widget off if IA within 100ft)

-  * baro settings

-  * SoftKeys menus navigation for PFD and MFD: not yet implemented function are logged in console ![][done], softkeys colorized when active ![][done], alerts with white backgroud and black text available ![][done]

-  * CDI

-  * OMI

-  * Slipskid animation

-  * Radio stack, including ID for NAV

-  * windows management: selectable items, modifiable items, scrolling

-  * display of V-speeds in ruler: Vx, Vy, Vr and Vglide (specific for aircraft, see installation instruction)

-  * some aircraft specific data to retrieve from aircraft XML files (VNE, etc)

-  * possibility to add a copilot's PFD, and other displays

-  * EIS: separation for aircraft specifics (selected by the zkv1000 config)

-  * Inset Map (PFD)

-  * single-prop EIS: texts displayed, animations for fuel

-  * ND and map display: synchronized tiles and navaids, range change, map heads up

-  * rotation and zooming of online maps in-flight

-  * Traffic alert and display on map

-  * screen brightness and body lighting settings

-  * checklists management (emergency and normal)

-  * possibility to fit the size of the devices to enter the panel

-  * auto power on if set

-  * AFCS capabilities

-  * integration of [GFC700 from the official Stuart Buchanan's FG1000](http://wiki.flightgear.org/FG1000#GFC700_Autopilot)

+The whole 3D model is animated, with necessary popups (in order to separate nested knobs for example), and adaptable to the size of the panel.

+The basic fligth instrumentation is here (AI, speeds, altitude and vertical speed, etc.), plus many other helpers and information (often displayed in widgets or alerts). Also the radio stack (NAV and COMM) tools are implemented. ADF is available for bearing.

+The official autopilot [GFC700 from the official Stuart Buchanan's FG1000](http://wiki.flightgear.org/FG1000#GFC700_Autopilot) is available and usable.

+Screens are fully animated, with softkeys and menus, on map (PFD inset and MFD) background is configurable with the preferred one, navaids and [route](https://seb.lautre.net/git/seb/zkv1000/issues/6) are displayed. Traffic and topography layers are available for display only on MFD screen (not in PFD inset as the window is too small).

+There is also per-aircraft settings storage for preferred units (speed, distance, etc.).

+Flightplan management is delegated to the more usable FG interface lauched from inside the zkv100, but it is possible to use DirectTo on selected navaid, and OBS mode with GPS.

+Checklists are managed, including separation between emergency and normal checklists (and aircraft agnostic, should be compatible with most systems).

+And many more :) !

 * ![][90%]

-  * TMR/REF Timer ![][done], Vspeeds ![][done], minimums ![][pending] (don't understand the role of this)

   * route displayed on map: legs ![][done], current and next leg ![][done], OBS ![][done], TOC/TOD ![][ongoing]

-  * angle of attack display (not sure about calculation): specific for each airplane (see Installation instructions below)

-  * Bearing needs some checks to be sure it shows the correct information

   * XPDR: emergency code depending of the country (eg.: 1200 for US, 7700 for Europe), should be set in settings

-  * use of [maketimer()](http://wiki.flightgear.org/Nasal_library#maketimer.28.29) instead of [settimer()](http://wiki.flightgear.org/Nasal_library#settimer.28.29) when possible

 * ![][80%]

-  * Setting pages (MFD): pages/sub-pages selection via FMS knob ![][done], pages content implementation ![][ongoing]

   * Flight plans catalog (display on map doesn't work each time...)

-* ![][70%]

 * ![][60%]

   * NOT TESTED: add the posssibility to only use Nasal part of the instrument. This in case of a cockpit which already includes needed objects and animations for screens, knobs and buttons in its config files

-  * Map settings: declutter ![][ongoing], range/zoom ![][done]

 * ![][50%]

   * integration of Octal450's [S-TEC 55X](http://wiki.flightgear.org/S-TEC_55X) autopilot system ![][ongoing]

   * EIS: animations for temperature for YaSim and JSBSim with provided default single-prop EIS

   * make the switch back on working for MFD display and radios ![][ongoing]

-* ![][40%]

-* ![][30%]

-* ![][20%]

 * ![][10%]

   * multikey for every part of the device (actually only power on)

-  * power off

-  * Aircraft Maintainer's Guide

+  * Aircraft Maintainer's Guide ![][ongoing]

+  * User's Guide ![][ongoing]

 * ![][0%] (TODO list, unsorted)

   * make possible to integrate other autopilot systems than the one integrated

   * make booting animation visible

-  * make possible to include in the aircraft directory (instead of Instruments-3d)

-  * separation of code for buttons and knobs scenarii and computing

   * CDI/GPS: scale depending of the flight phase

   * Alerts

-  * TOPO map

   * Weather map

-  * Flight planning (MFD)

-  * PFD settings

   * replace the use of `clip` by a better system in map display (think also about INSET)

   * VS guidance

   * VNAV

   * scrolling lift in menus

   * tutorials

-  * User's Guide

-  * make any Vspeed available (not only Vx, Vy, Vr and Vglide), depending of their presence in aircraft config

   * [touchable screen](http://wiki.flightgear.org/Canvas_Event_Handling) ([other interesting link](http://wiki.flightgear.org/Touch_Animation))

   * many more...

@@ -167,8 +126,8 @@ Let say you want your PFD and MFD switched on as soon as the electrical system a

 Then you need to set the property `/instrumentation/zkv1000/serviceable` by the mean you want, as soon as it property is `true` the zkv1000 will automagically switch on.

 ### Vspeeds

-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, ![][warning] values are not to be used in real life).

-If not set, defaults to 999 knots

+To see the Vspeeds bugs or the IAS background color change (Vne), set the corresponding V-speeds *in knots* by adding them in your `<instrumentation><zkv1000><alerts>` section the following lines (here an example ![][warning] values are not to be used in real life).

+If not set, Vne defaults to 999 knots

         <alerts>

           <Vx>99</Vx>

@@ -178,6 +137,9 @@ If not set, defaults to 999 knots

           <Vne>170</Vne>

         </alerts>

+You can define as many Vspeed you need, with arbitrary names, they only need to be named `Vfoo` (name must begin by a uppercase V) to be recognize as a Vspeed.

+All defined Vspeeds can be adjusted from inside the zkv1000.

+

 ### EIS

 This parameter tells the zkv1000 which kind of engines equips your aircraft, and the associated EIS.  

 The Nasal script should include at least three things: