@@ -19,7 +19,7 @@

 [red-bug]:    https://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Red_bug.svg/32px-Red_bug.svg.png "blocking bug"

 [warning]:    https://upload.wikimedia.org/wikipedia/commons/thumb/1/12/Achtung-orange.svg/32px-Achtung-orange.svg.png "warning symbol"

-![ZKV1000 in Diamond DA42, in flight from LFLG to LFBD](https://seb.lautre.net/bozon/index.php?f=15eb94e0c0e1d1)running STEC55X autopilot HDG roll mode.

+![ZKV1000 in Diamond DA42, in flight from LFLG to LFBD](https://seb.lautre.net/bozon/index.php?f=15eb94e0c0e1d1)ZKV1000 in Diamond DA42, in flight from LFLG to LFBD, running STEC55X autopilot HDG roll mode.

 [other pictures available here](https://seb.lautre.net/bozon/index.php?f=158cf95340742d)

 # Thanks

@@ -80,6 +80,8 @@ Please report bug at <zkv1000@seb.lautre.net>.

   * simple Traffic Alert Collision Avoidance System (TCAS)

   * 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

 * ![][90%]

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

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

@@ -87,11 +89,11 @@ Please report bug at <zkv1000@seb.lautre.net>.

   * 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

   * AFCS capabilities

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

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

 * ![][80%]

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

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

 * ![][70%]

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

 * ![][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]

@@ -102,8 +104,10 @@ Please report bug at <zkv1000@seb.lautre.net>.

 * ![][20%]

 * ![][10%]

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

+  * power off

   * Aircraft Maintainer's Guide

 * ![][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

@@ -145,6 +149,20 @@ Actually `zkv1000.nas` is where everything begins, please have a look at this co

 ## Set specific values for your aircraft

 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.

+### Adjust size to  the panel of your aircraft

+To increase or decrease the size of all the devices (PFDs and MFDs) you can use a factor property, eg. in the DA42:

+

+        <size-factor type="double">1.19</size-factor>

+

+Defaults to 1 if you don't provide this information. Values lower than 1 decreaase size, and higher than 1 increase the size.

+

+### Make your instrument auto powered on

+Let say you want your PFD and MFD switched on as soon as the electrical system allows it. Set your device with the following

+

+        <auto-power type="bool">1</auto-power>

+

+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

@@ -258,6 +276,13 @@ Actually it checks if the property `/instrumentation/tcas/serviceable` is set to

 Moreover it only shows alerts with an annunciation "TRAFFIC" on PFD, and shows icons on maps (MFD and INSET), no decision is taken, no relation with transponder and no evasion scenari and no evasion scenario.

+## Autopilot

+For now there is only one autopilot system supported: the Octal450's STEC 55X (and at time of writing only HDG mode is available).

+

+To make it available you have to follow the installation rules of the device [on its own page](http://wiki.flightgear.org/S-TEC_55X). The zkv1000 will find it by its own and make it available.

+

+This STEC55X autopilot system would remain shipped in the zkv1000 as it is described in the documentation of Cirrus Perspective SR2x, but the zkv1000 will in near future let you create your own and make its choice depending of the availibilities or property set.

+

 ## Map tiles origin

 By defaults the maps tiles come from `https://maps.wikimedia.org`, type `osm-intl` (please read [https://www.wikimedia.org/wiki/Maps]()), but you can choose your favorite one if you've got one. I've tested `opentopomap.org` and `thunderforest.com` (my favourite).

 You can tell the zkv1000 the tile server, type and eventually apikey by using `--prop:` option while starting FlightGear session: