@@ -82,14 +82,14 @@ Please report bug at <zkv1000@seb.lautre.net>.

   * 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)

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

   * 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

-  * AFCS capabilities

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

@@ -98,7 +98,9 @@ Please report bug at <zkv1000@seb.lautre.net>.

   * 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%]

-  * EIS: animations for temperature for YaSim and JSBSim

+  * 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%]

@@ -277,8 +279,16 @@ 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).

+There are two systems supported: the GFC700 shipped with the official Stuart Buchanan's FG1000 and the Octal450's STEC 55X (and at time of writing only HDG and buggy NAV/GPS modes are available).

+

+### GFC700

+To make the magic operate, you just need to insert these lines into the `sim/systems` section. Be aware that this autopilot [has been tuned for the Cessna 182, so may not be correct for light jets](http://wiki.flightgear.org/FG1000#Include_the_GFC700_autopilot_.28optional.29).

+

+        <autopilot>

+          <path>Aircraft/Instruments-3d/FG1000/GFC700.xml</path>

+        </autopilot>

+### S-TEC 55X

 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.

@@ -307,7 +317,20 @@ An option is also available to tell the format of the tile image which can be us

         --prop:/sim/online-tiles-format=jpeg

 ## Switch it up

-You can use the multikey (souvenirs, thanks to Melchior having that much expended this feature years ago :)) service by typing:

+### Autopower on/off

+You can set an electrical system to make the property `/instrumentation/zkv1000/serviceable` reflect the alimentation of the ZKV1000 (boolean or volts > 12). Then configure the zkv1000 to auto power on as soon as it is known as serviceable withe the following

+

+        <instrumentation>

+          <zkv1000>

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

+          <zkv1000>

+        </instrumentation>

+

+Note that will also switch off the zkv1000 if it becomes non-serviceable.

+

+The re-switching on is buggy (the MFD doesn't re-display the contents and the NAV/COMM utils aren't available anymore... working on it)

+### Manually

+If you haven't set a electrical system to make the property `/instrumentation/zkv1000/serviceable` to reflect the availibity of the ZKV1000, and you haven't set the auto-power, then you can use the multikey (souvenirs, thanks to Melchior having that much expended this feature years ago :)) service by typing:

 `:zo`

 The `:z` will be the multikey entry for all multikeys of the zkv1000.