Merge branch 'master' of https://github.com/pascallanger/DIY-Multiprotocol-TX-Module

docs/Transmitters.md

@@ -37,7 +37,8 @@ This serial protocol does not require any hardware modifications, but **will** r
 
 Transmitter|Firmware Options|Telemetry Enabled
 :----------|:---------------|:----------------
-[FrSky Taranis/Plus/9XE](Tx-Taranis.md)| erSky9x, OpenTx 2.1.9 Multi|Yes - native
+[FrSky Taranis X9D/X9D+/9XE](Tx-Taranis.md)| erSky9x, OpenTx 2.1.9 Multi, OpenTX 2.2 (multimodule option)|Yes - native
+[Frsky Taranis Q X7/Horus](Tx-Taranis.md)| OpenTX 2.2 (multimodule option)| Yes - native
 [Turnigy 9X/9xR](Tx-FlyskyTH9X.md)|er9x|[Mod required](#Telemetry_Mod)
 [Turnigy 9XR-Pro](Tx-erSky9X.md)|erSky9x|Yes - native
 [FlySky TH9x](Tx-FlyskyTH9X.md)|er9x|[Mod required](#Telemetry_Mod)

docs/Tx-Taranis.md

@@ -1,15 +1,17 @@
 # FrSky Taranis/Horus Setup
-This page contains setup instructions for the FrSky family of transmitters. These include the Trananis X9D, Taranis X9D Plus, Taranis X9E and Horus X12S.  It may also be relevant to the following transmitters: Turnigy 9XR Pro, Sky board-based, AR9X board-based, 9Xtreme board-based and AR9X Uni board-based.  
+This page contains setup instructions for the FrSky family of transmitters. These include the Trananis X9D, Taranis X9D Plus, Taranis X9E and Horus X12S.  It may also be relevant to the following transmitters: Turnigy 9XR Pro, Sky board-based, AR9X board-based, 9Xtreme board-based and AR9X Uni board-based, for these the OpenTX is implemented but currently untested.  
 
 <img src="http://www.frsky-rc.com/product/images/pic/1456723548.jpg" width="300" height="200" />
 <img src="http://www.frsky-rc.com/product/images/pic/1456723588.jpg" width="300" height="200" />
 <img src="http://www.frsky-rc.com/product/images/pic/1471248674.jpg" width="300" height="200" />
+<img src="http://www.frsky-rc.com/product/images/pic/1483518722.jpg" width="300" height="200" />
 
 The instructions below are relevant to the following firmwares:
  1. Taranis with erSky9X available [here](http://www.er9x.com)
- 1. Taranis with OpenTx available [here](http://plaisthos.de/opentx/)
  1. Taranis/Horus with OpenTX 2.2 and multimodule option enabled [here](http://www.open-tx.org/)
+ 1. Taranis with OpenTx available [here](http://plaisthos.de/opentx/), outdated use OpenTX 2.2
 
+If you use OpenTX Version 2.2 RC9 or later is strongly recommended as earlier version had a bug that scaled -100;100% output to -125%;125% output.
 
 The MULTI-module can be used with all transmitters and firmwares in PPM mode.  Taranis transmitters running erSky9X or OpenTX (Version 2.1.9 Multi or Version 2.2) fully support Serial mode. 
 ## PPM Mode
@@ -19,7 +21,7 @@ Please refer to the [PPM Setup](PPM_Setup.md) page.
 ###Enabling Serial Mode
 To operate in serial mode, you need one of these firmwares:
  1. erSky9x
- 1. OpenTx supporting the MULTI-Module (Version 2.18 Multi or later)
+ 1. OpenTx supporting the MULTI-Module (Version 2.1.8 Multi or later)
 
 Check and upload a supported firmware.  The latest available version at time of writing are:
  - erSky9x Revision 218 or later - the hex files are available [here](http://www.er9x.com) (Mike's latests test versions are available [here](http://openrcforums.com/forum/viewtopic.php?f=7&t=4676)).  
@@ -46,6 +48,22 @@ To select the protocol, scroll through the available options under the Model Set
 
 The following picture shows DSM – DSMX – Option 6 (6 channels and 11ms frame rate). Check out the [Protocol Details](Protocol_Details.md) page for detailed information and suggestions regarding the sub-protocols and options.
 
+###Protcol Status in Serial mode (OpenTX)
+If you see ```NO MULTI_TELEMETRY``` or no ```NO TELEMETRY``` in the setup screen of the external module, like this:
+
+<img width="594" height="213" src="images/X7-no-telemetry.png" />
+
+you are missing the ```MULTI_TELEMETRY``` and/or ```INVERT_TELEMTRY``` option in your ```_Config.h``` and/or [you need to hardware modifications to enable telemetry](Hardware.md). OpenTX also shows the ```NO TELEMETRY``` message if no module status has been received in the last 2s which can indicate a non working module if the telemetry status worked before.  With the option enabled, the right telemetry type is automatically detected and you will see the status of the module:
+
+<img width="580" height="210" src="images/X7-protocol-invalid.png">
+
+(Selected protocol is not available, most probably mssing from ```_Config.h```)
+
+<img width="576" height="209" src="images/X7-bind.png">
+
+(Module is currently binding and code on the module is running V1.1.6.10)
+
+
 ###Binding in Serial mode
 1. Switch on the model or put the receiver into bind mode
 1. On the transmitter go to the Model Settings menu and scroll down to the [Bind] menu option and press Enter.