diff --git a/docs/Bind_Timing.md b/docs/Bind_Timing.md index 64cb257..87fcfc1 100644 --- a/docs/Bind_Timing.md +++ b/docs/Bind_Timing.md @@ -1,4 +1,4 @@ -#Getting your Bind timing right. +# Getting your Bind timing right. On many consumer models it it important for the Tx to send a bind signal in a narrow window once the model has powered up. If the bind signal is not recieved during this window, the bind sequence times out. Try this: diff --git a/docs/Compiling.md b/docs/Compiling.md index aeb40c6..29a5085 100644 --- a/docs/Compiling.md +++ b/docs/Compiling.md @@ -70,7 +70,7 @@ If there is another error carefully read it, go to the line number indicated and 1. If you have a 4in1 Multiprotocol module you can skip this step. If you've just finished to build your DIY Multiprotocol module (like v2.3d), the first step is to flash the fuses of the microcontroller. This needs to be done only once. For this purpose, click on **Tools -> Burn Bootloader** 1. You are now ready to flash the firmware. In the Arduino IDE click **Sketch -> Upload Using Programmer**. -If the output indicates that the firmware has been uploaded successfully - give yourself a pat on the back. Well done, you have successfully programmed your DIY Multiprotocol module. You can already go to the final step [Setting up your Transmitter](TransmitterSetup.md) and begin to fly!!!! But don't forget to visit the next topic [Advanced settings](#AdvancedSettings) which has some extra steps needed to use your module at his full potential. +If the output indicates that the firmware has been uploaded successfully - give yourself a pat on the back. Well done, you have successfully programmed your DIY Multiprotocol module. You can already go to the final step [Setting up your Transmitter](Transmitters.md#compatible-transmitters) and begin to fly!!!! But don't forget to visit the next topic [Advanced settings](#AdvancedSettings) which has some extra steps needed to use your module at his full potential. **Troubleshooting** diff --git a/docs/Documentation_To_Do_List.md b/docs/Documentation_To_Do_List.md index 827c1fd..c3db0ec 100644 --- a/docs/Documentation_To_Do_List.md +++ b/docs/Documentation_To_Do_List.md @@ -1,14 +1,13 @@ -#Documentation ToDos -1. Documentation on all the FlySky boards: (MikeB?) +# Documentation ToDos +- [ ] Documentation on all the FlySky boards: (MikeB?) - SKY board erSky9x - AR9X board erSky9x - 9Xtreme board erSky9x - AR9X UNI board -1. Add to the troubleshooting page -1. Add how to do custom protocol setup on er9x and OpenTx -1. Document the OrangeRx Transmitter module (Mikeb?) -1. enabling Serial on the DIY PCB page -1. lots of pictures mentioned between the {} markers -1. Someone to add the Build the board from scratch if it is still relevant - -1. Move to atmega specific and add ftdi to stm32 AVR ISP programmer like the popular USBASP programming dongle that is 3.3V safe - available from many sellers on ebay. There are reports that some of the cheap programmers are not safe to use with 3.3V units (like this unit). Look for USBAsp programmers with the “LC Technologies” label. {Pascal to confirm these reports are true} Also, you will need a 10-pin to 6-pin connector to connect the USBASP to the board. +- [ ] Add to the troubleshooting page +- [ ] Add how to do custom protocol setup on er9x and OpenTx +- [ ] Document the OrangeRx Transmitter module (Mikeb?) +- [ ] enabling Serial on the DIY PCB page +- [ ] lots of pictures mentioned between the {} markers +- [ ] Someone to add the Build the board from scratch if it is still relevant +- [ ] Move to atmega specific and add ftdi to stm32 AVR ISP programmer like the popular USBASP programming dongle that is 3.3V safe - available from many sellers on ebay. There are reports that some of the cheap programmers are not safe to use with 3.3V units (like this unit). Look for USBAsp programmers with the “LC Technologies” label. {Pascal to confirm these reports are true} Also, you will need a 10-pin to 6-pin connector to connect the USBASP to the board. diff --git a/docs/Protocol_Details_old.md b/docs/Protocol_Details_old.md index 1fedb2e..7ce127d 100644 --- a/docs/Protocol_Details_old.md +++ b/docs/Protocol_Details_old.md @@ -1,4 +1,4 @@ -#MULTI-Module Protocol Details +# MULTI-Module Protocol Details **You'll find below a detailed description of every supported protocols sorted by RF modules.** Legend: @@ -8,9 +8,9 @@ Legend: The AETR mentionned here for all protocols depends on the TX settings compilation option set in _Config.h. *** -#A7105 RF Module +# A7105 RF Module -##FLYSKY +## FLYSKY Extended limits supported CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 @@ -19,22 +19,22 @@ A|E|T|R|CH5|CH6|CH7|CH8 Note that the RX ouput will be AETR. -###Sub_protocol V9X9 +### Sub_protocol V9X9 CH5|CH6|CH7|CH8 ---|---|---|--- FLIP|LIGHT|PICTURE|VIDEO -###Sub_protocol V6X6 +### Sub_protocol V6X6 CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12 ---|---|---|---|---|---|---|--- FLIP|LIGHT|PICTURE|VIDEO|HEADLESS|RTH|XCAL|YCAL -###Sub_protocol V912 +### Sub_protocol V912 CH5|CH6 ---|--- BTMBTN|TOPBTN -##HUBSAN +## HUBSAN Models: Hubsan H102D, H107/L/C/D and Hubsan H107P/C+/D+ Autobind protocol @@ -47,10 +47,9 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|LIGHT|PICTURE|VIDEO|HEADLESS -*** -#CC2500 RF Module +# CC2500 RF Module -##FRSKYV = FrSky 1 way +## FRSKYV = FrSky 1 way Models: FrSky receivers V8R4, V8R7 and V8FR. Extended limits supported @@ -61,7 +60,7 @@ CH1|CH2|CH3|CH4 ---|---|---|--- CH1|CH2|CH3|CH4 -##FRSKYD +## FRSKYD Models: FrSky receivers D4R and D8R. DIY RX-F801 and RX-F802 receivers. Extended limits supported @@ -74,7 +73,7 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 -##FRSKYX +## FRSKYX Models: FrSky receivers X4R, X6R and X8R. Extended limits supported @@ -83,17 +82,17 @@ Telemetry enabled for A1 (RxBatt), A2, RSSI, TSSI and Hub Option=fine frequency tuning. This value is different for each board. To determine the option value, find the two limits where the RX loses connection then set the option value to half way between them. If you have a 4in1 V2 board the value is around 40. -###Sub_protocol CH_16 +### Sub_protocol CH_16 CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12|CH13|CH14|CH15|CH16 ---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|---- CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12|CH13|CH14|CH15|CH16 -###Sub_protocol CH_8 +### Sub_protocol CH_8 CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 -##SFHSS +## SFHSS Models: Futaba RXs and XK models. Option=fine frequency tuning. This value is different for each board. To determine the option value, find the two limits where the RX loses connection then set the option value to half way between them. If you have a 4in1 V2 board the value is around 40. @@ -102,10 +101,9 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- A|E|T|R|CH5|CH6|CH7|CH8 -*** -#CYRF6936 RF Module +# CYRF6936 RF Module -##DEVO +## DEVO Extended limits supported CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 @@ -135,7 +133,7 @@ Bind procedure using PPM: - To verify that the TX is in fixed mode: power cycle the TX, the module LED should be solid ON (no blink). - Note: Autobind/fixed ID mode is linked to the dial number. Which means that you can have multiple dial numbers set to the same protocol DEVO with different RX_Num and have different bind modes at the same time. It enables PPM users to get model match under DEVO. -##DSM +## DSM Extended limits supported Telemetry enabled for TSSI and plugins @@ -150,31 +148,34 @@ Notes: - model/type/number of channels indicated on the RX can be different from what the RX is in fact wanting to see. So don't hesitate to test different combinations until you have something working. Using Auto is the best way to find these settings. - RX ouput will always be TAER independently of the input AETR, RETA... -###Sub_protocol DSM2_22 +### Sub_protocol DSM2_22 DSM2, Resolution 1024, refresh rate 22ms -###Sub_protocol DSM2_11 + +### Sub_protocol DSM2_11 DSM2, Resolution 2048, refresh rate 11ms -###Sub_protocol DSMX_22 + +### Sub_protocol DSMX_22 DSMX, Resolution 2048, refresh rate 22ms -###Sub_protocol DSMX_11 + +### Sub_protocol DSMX_11 DSMX, Resolution 2048, refresh rate 11ms -###Sub_protocol AUTO + +### Sub_protocol AUTO The "AUTO" feature enables the TX to automatically choose what are the best settings for your DSM RX and update your model protocol settings accordingly. The current radio firmware which are able to use the "AUTO" feature are ersky9x (9XR Pro, 9Xtreme, Taranis, ...) and er9x for M128 (9XR) and M2561. For these firmwares, you must have a telemetry enabled TX and you have to make sure you set the Telemetry "Usr proto" to "DSMx". Also on er9x you will need to be sure to match the polarity of the telemetry serial (normal or inverted by bitbashing), while on ersky9x you can set "Invert COM1" accordinlgy. -##J6Pro +## J6Pro CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12 ---|---|---|---|---|---|---|---|---|----|----|---- A|E|T|R|CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12 -*** -#NRF24L01 RF Module +# NRF24L01 RF Module -##ASSAN +## ASSAN Extended limits supported CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10 @@ -183,7 +184,7 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10 The transmitter must be close to the receiver while binding. -##BAYANG +## BAYANG Models: EAchine H8(C) mini, BayangToys X6/X7/X9, JJRC JJ850, Floureon H101 ... Autobind protocol @@ -192,7 +193,7 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10 ---|---|---|---|---|---|---|---|---|---- A|E|T|R|FLIP|RTH|PICTURE|VIDEO|HEADLESS|INVERTED -##CG023 +## CG023 Models: EAchine CG023/CG031/3D X4 Autobind protocol @@ -201,14 +202,14 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|LIGHT|PICTURE|VIDEO|HEADLESS -###Sub_protocol YD829 +### Sub_protocol YD829 Models: Attop YD-822/YD-829/YD-829C ... CH5|CH6|CH7|CH8|CH9 ---|---|---|---|--- FLIP||PICTURE|VIDEO|HEADLESS -###Sub_protocol H8_3D +### Sub_protocol H8_3D Models: EAchine H8 mini 3D, JJRC H20/H22 CH5|CH6|CH7|CH8|CH9 @@ -223,7 +224,7 @@ H8 3D: OPT1=RTH then press a direction to enter headless mode (like stock TX), O CAL: calibrate accelerometers -##CX10 +## CX10 Extended limits supported Autobind protocol @@ -234,12 +235,12 @@ A|E|T|R|FLIP|RATE Rate: -100%=rate 1, 0%=rate 2, +100%=rate 3 -###Sub_protocol GREEN +### Sub_protocol GREEN Models: Cheerson CX-10 green pcb Same channels assignement as above. -###Sub_protocol BLUE +### Sub_protocol BLUE Models: Cheerson CX-10 blue pcb & some newer red pcb, CX-10A, CX-10C, CX11, CX12, Floureon FX10, JJRC DHD D1 CH5|CH6|CH7|CH8 @@ -248,13 +249,13 @@ FLIP|RATE|PICTURE|VIDEO Rate: -100%=rate 1, 0%=rate 2, +100%=rate 3 or headless for CX-10A -###Sub_protocol DM007 +### Sub_protocol DM007 CH5|CH6|CH7|CH8|CH9 ---|---|---|---|--- FLIP|MODE|PICTURE|VIDEO|HEADLESS -###Sub_protocol Q282 and Q242 +### Sub_protocol Q282 and Q242 CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12 ---|---|---|---|---|---|---|--- @@ -262,120 +263,129 @@ FLIP|LED|PICTURE|VIDEO|HEADLESS|RTH|XCAL|YCAL Model: JXD 509 is using Q282 with CH12=Start/Stop motors -###Sub_protocol JC3015_1 +### Sub_protocol JC3015_1 CH5|CH6|CH7|CH8 ---|---|---|--- FLIP|MODE|PICTURE|VIDEO -###Sub_protocol JC3015_2 +### Sub_protocol JC3015_2 CH5|CH6|CH7|CH8 ---|---|---|--- FLIP|MODE|LED|DFLIP -###Sub_protocol MK33041 +### Sub_protocol MK33041 CH5|CH6|CH7|CH8|CH9|CH10 ---|---|---|---|---|--- FLIP|MODE|PICTURE|VIDEO|HEADLESS|RTH -##ESKY +## ESKY CH1|CH2|CH3|CH4|CH5|CH6 ---|---|---|---|---|--- A|E|T|R|GYRO|PITCH -##FY326 +## FY326 CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|RTH|HEADLESS|EXPERT|CALIBRATE -##FQ777 +## FQ777 Model: FQ777-124 CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- A|E|T|R|FLIP|RTH|HEADLESS|EXPERT -##HISKY +## HISKY CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- A|E|T|R|GEAR|PITCH|GYRO|CH8 GYRO: -100%=6G, +100%=3G -###HK310 +### HK310 Models: RX HK-3000, HK3100 and XY3000 (TX are HK-300, HK-310 and TL-3C) CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8 ---|---|---|---|---|---|---|--- |||T|R|AUX|T_FSAFE|R_FSAFE|AUX_FSAFE -##KN +## KN CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11 ---|---|---|---|---|---|---|---|---|----|---- A|E|T|R|DR|THOLD|IDLEUP|GYRO|Ttrim|Atrim|Etrim Dual Rate: +100%=full range, Throttle Hold: +100%=hold, Idle Up: +100%=3D, GYRO: -100%=6G, +100%=3G -###Sub_protocol WLTOYS -###Sub_protocol FEILUN +### Sub_protocol WLTOYS + +### Sub_protocol FEILUN Same channels assignement as above. -##HONTAI +## HONTAI Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11 ---|---|---|---|---|---|---|---|---|----|---- A|E|T|R|FLIP|LED|PICTURE|VIDEO|HEADLESS|RTH|CAL -###Sub_protocol HONTAI -###Sub_protocol JJRCX1 +### Sub_protocol HONTAI + +### Sub_protocol JJRCX1 CH6| ---| ARM| -###Sub_protocol X5C1 clone +### Sub_protocol X5C1 clone -##MJXQ +## MJXQ Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11|CH12|CH13 ---|---|---|---|---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|LED|PICTURE|VIDEO|HEADLESS|RTH|AUTOFLIP|PAN|TILT -###Sub_protocol WLH08 -###Sub_protocol X600 -Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them -###Sub_protocol X800 -Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them -###Sub_protocol H26D -###Sub_protocol E010 +### Sub_protocol WLH08 -##MT99XX +### Sub_protocol X600 +Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them + +### Sub_protocol X800 +Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them + +### Sub_protocol H26D + +### Sub_protocol E010 + +## MT99XX Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|LED|PICTURE|VIDEO|HEADLESS -###Sub_protocol MT +### Sub_protocol MT Models: MT99xx -###Sub_protocol H7 + +### Sub_protocol H7 Models: Eachine H7, Cheerson CX023 -###Sub_protocol YZ + +### Sub_protocol YZ Model: Yi Zhan i6S Only one model can be flown at the same time since the ID is hardcoded. -###Sub_protocol LS + +### Sub_protocol LS Models: LS114, 124, 215 CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|INVERT|PICTURE|VIDEO|HEADLESS -##Shenqi +## Shenqi Autobind protocol Model: Shenqiwei 1/20 Mini Motorcycle @@ -386,27 +396,27 @@ CH1|CH2|CH3|CH4 Throttle +100%=full forward,0%=stop,-100%=full backward. -##SLT +## SLT Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6 ---|---|---|---|---|--- A|E|T|R|GEAR|PITCH -##Symax +## Symax Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP||PICTURE|VIDEO|HEADLESS -###Sub_protocol SYMAX +### Sub_protocol SYMAX Models: Syma X5C-1/X11/X11C/X12 -###Sub_protocol SYMAX5C +### Sub_protocol SYMAX5C Model: Syma X5C (original) and X2 -##V2X2 +## V2X2 Models: WLToys V202/252/272, JXD 385/388, JJRC H6C, Yizhan Tarantula X6 ... CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9|CH10|CH11 @@ -417,17 +427,21 @@ PICTURE: also automatic Missile Launcher and Hoist in one direction VIDEO: also Sprayer, Bubbler, Missile Launcher(1), and Hoist in the other dir -##YD717 +## YD717 Autobind protocol CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9 ---|---|---|---|---|---|---|---|--- A|E|T|R|FLIP|LIGHT|PICTURE|VIDEO|HEADLESS -###Sub_protocol YD717 -###Sub_protocol SKYWLKR -###Sub_protocol SYMAX4 -###Sub_protocol XINXUN -###Sub_protocol NIHUI +### Sub_protocol YD717 + +### Sub_protocol SKYWLKR + +### Sub_protocol SYMAX4 + +### Sub_protocol XINXUN + +### Sub_protocol NIHUI Same channels assignement as above. diff --git a/docs/Tx-FlyskyTH9X.md b/docs/Tx-FlyskyTH9X.md index 8147d9f..986e3e0 100644 --- a/docs/Tx-FlyskyTH9X.md +++ b/docs/Tx-FlyskyTH9X.md @@ -1,4 +1,4 @@ -#Flysky TH9X family of transmitters +# Flysky TH9X family of transmitters This page is relevant to the following transmitters: * FlySky TH9X * Turnigy 9X, Turnigy 9XR @@ -19,21 +19,21 @@ Serial mode is only supported by the er9X firmware. Loading this firmware is be er9X is very well documented, see [here](http://openrcforums.com/forum/viewtopic.php?f=5&t=6473#p90349) -###Enabling Serial Mode +### Enabling Serial Mode 1. Confirm that the MULTI-Module has the required physical connections between the pins on the back of the Tx and the ATMega328 microprocessor. This may require some soldering and depends on which version of the MULTI-Module you have. Check out your module’s hardware page under the section **Enabling your MULTI-Module for Serial** for details. Click here for the [hardware](Hardware.md) pages. 1. Plug in your DIY Multiprotocol module into the transmitter module bay. If you have a rotary protocol selection switch, turn the switch to position 0 to put the unit into Serial mode. 1. Ensure throttle is down and all switches are in the start position and power up the Tx. The red LED on the DIY Multiprotocol module should be flashing with a period of about 1 second indicating that it has not established a valid serial link with the Tx. This is expected as we have not set up the Tx yet. -1. Create a new model and confirm that the channel order is set to AETR (**This is really important - this is for all protocols - even for DSM as the MULTI-module firware will change the transmitted channel order according to the protocol.** +1. Create a new model and confirm that the channel order is set to AETR (**This is really important - this is for all protocols - even for DSM as the MULTI-module firware will change the transmitted channel order according to the protocol.** 1. In the Model Settings menu scroll down to change the RF settings to MULTI {mikeb - can you write this line } 1. The red LED on the MULTI-Module should briefly flash and then go off. This confirms that the MULTI-Module has established serial communication with the Tx. If the red LED on the module continues to flash at a period of about 1 seconds then it signals that serial communication has not been established. Check your settings under the model menu as described above and check that the protocol selection switch on the module is at 0 (enable Serial mode). If there is still no communication, power down and power up the Tx. Finally check that you have correctly enabled your module for serial as described on the hardware page for your module under the heading "Enabling your module for Serial". Click here to access the [hardware](Hardware.md) and then click on the picture of your module. -###Protocol Selection in Serial mode +### Protocol Selection in Serial mode To select the protocol: 1. In the Model Setting menu, scroll through the available options under the MULTI option {mikeb to confirm}. - 1. Depending on which protocol you have selected you may be required to select a sup-protocol and options. For example, the FrSky protocol has three sub-protocols FrSky_V, FrSky_D and FrSky_X. In some cases the sub-protocols have options that could specify the number of channels, packet frame rate or fine frequency tuning. Check out the [Protocol Details](Protocol_Details.md) page for detailed information and suggestions regarding the sub-protocols and options. The picture below shows the settings in the erSky Model Setup menu for FrSkyX subprotocol with {mike to insert} options: + 1. Depending on which protocol you have selected you may be required to select a sup-protocol and options. For example, the FrSky protocol has three sub-protocols FrSky_V, FrSky_D and FrSky_X. In some cases the sub-protocols have options that could specify the number of channels, packet frame rate or fine frequency tuning. Check out the [Protocol Details](../Protocols_Details.md) page for detailed information and suggestions regarding the sub-protocols and options. The picture below shows the settings in the erSky Model Setup menu for FrSkyX subprotocol with {mike to insert} options: {mikeb to send simple picture} -###Binding in Serial mode +### 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. 1. Press Enter again to exit Bind mode diff --git a/docs/Tx-Taranis.md b/docs/Tx-Taranis.md index 567bc9d..17c01ef 100644 --- a/docs/Tx-Taranis.md +++ b/docs/Tx-Taranis.md @@ -20,16 +20,10 @@ Please refer to the [PPM Setup](PPM_Setup.md) page. ## Serial mode ### Enabling Serial Mode To operate in serial mode, you need one of these firmwares: - 1. erSky9x - 1. OpenTx supporting the MULTI-Module (Version 2.1.8 Multi or later, 2.2 recommended) - -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)). - - OpenTx 2.2RC10 or later [www.open-tx.org](http://www.open-tx.org/) - - Please make sure that the "multimodule" option in OpenTX Companion is checked: -   -   +1. 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)). +1. OpenTx supporting the MULTI-Module (Version 2.1.8 Multi or later, 2.2 recommended). Check and upload a supported firmware. The latest available version at time of writing are: + - OpenTx 2.2RC16 or later [www.open-tx.org](http://www.open-tx.org/) + - Please make sure that the "multimodule" option in OpenTX Companion is checked:

Tutorials for uploading new firmware using the SD Card are available [here](http://www.dronetrest.com/t/how-to-upgrade-firmware-for-frsky-taranis-x9d/959) or the CompanionTx or eepe software (recommended) are available [here](http://open-txu.org/home/undergraduate-courses/fund-of-opentx/part-2-flashing-opentx/). @@ -37,15 +31,11 @@ Tutorials for uploading new firmware using the SD Card are available [here](http First, confirm that the MULTI-Module has the required physical connections between the pins on the back of the Tx and the ATMega328 microprocessor. This may require some soldering and depends on which version of the DIY Multiprotocol module you have. Check out the specific pages for your module hardware (under the section "Enabling Serial") linked [here](Hardware.md) for details. - 1. Plug in your MULTI-Module into the transmitter's module bay. - 2. If you have a rotary protocol selection switch, turn the switch to position 0 to put the unit into Serial mode. - 2. Ensure throttle is down and all switches are in the start position and power up the Transmitter. The red LED on the MULTI-Module should be flashing with a period of about 1s indicating that it has not established a valid serial link with the Tx. This is expected as we have not set up the Tx yet. - 3. Create a new model (make sure channel order is AETR - **This is really important - this is for all protocols - even for DSM as the MULTI-module firware will change the transmitted channel order according to the protocol.**) and on the first Model Settings page scroll down to disable the internal RF and enable the external RF by selecting MULTI as the external RF. Your Transmitter settings should look like this: - - or - - The Red LED on the MULTI-Module should briefly flash and then stay on. This confirms that the MULTI-Module module has established serial communication with the Tx. - 4. If the red LED on the module continues to flash at a period of about 1s then it signals that serial communication has not been established. Check your settings under the model menu as described above and check that the protocol selection switch on the module is at 0 (zero). If there is still no communication, power down and power up the Tx. Finally check that you have correctly enabled your module for serial as described in specific pages for your module hardware (under the section "Enabling Serial") linked [here](Hardware.md) +1. Plug in your MULTI-Module into the transmitter's module bay. +1. If you have a rotary protocol selection switch, turn the switch to position 0 to put the unit into Serial mode. +1. Ensure throttle is down and all switches are in the start position and power up the Transmitter. The red LED on the MULTI-Module should be flashing with a period of about 1s indicating that it has not established a valid serial link with the Tx. This is expected as we have not set up the Tx yet. +1. Create a new model (make sure channel order is AETR - **This is really important - this is for all protocols - even for DSM as the MULTI-module firware will change the transmitted channel order according to the protocol.**) and on the first Model Settings page scroll down to disable the internal RF and enable the external RF by selecting MULTI as the external RF. Your Transmitter settings should look like this:

or

The Red LED on the MULTI-Module should briefly flash and then stay on. This confirms that the MULTI-Module module has established serial communication with the Tx. +1. If the red LED on the module continues to flash at a period of about 1s then it signals that serial communication has not been established. Check your settings under the model menu as described above and check that the protocol selection switch on the module is at 0 (zero). If there is still no communication, power down and power up the Tx. Finally check that you have correctly enabled your module for serial as described in specific pages for your module hardware (under the section "Enabling Serial") linked [here](Hardware.md) ### Protocol Selection in Serial mode To select the protocol, scroll through the available options under the Model Settings menu. Depending on which protocol you have selected you may be required to select a sup-protocol and options. For example, the FrSky protocol has three sub-protocols FrSkyV, FrSkyD and FrSkyX. Each of the sub-protocols may have options that specify the number of channels and the packet frame rate, etc. @@ -53,19 +43,7 @@ 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: - - - -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: - - - -(Selected protocol is not available, most probably mssing from ```_Config.h```) - - - -(Module is currently binding and code on the module is running V1.1.6.10) +If you see ```NO MULTI_TELEMETRY``` or no ```NO TELEMETRY``` in the setup screen of the external module, like this:

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:

(Selected protocol is not available, most probably mssing from ```_Config.h```)

(Module is currently binding and code on the module is running V1.1.6.10) ### Binding in Serial mode diff --git a/docs/Tx-erSky9X.md b/docs/Tx-erSky9X.md index 61cd011..cd52dbe 100644 --- a/docs/Tx-erSky9X.md +++ b/docs/Tx-erSky9X.md @@ -1,4 +1,4 @@ -#erSky9X family of transmitters +# erSky9X family of transmitters This page is relevant to the following transmitters: - Taranis running erSky9X (for the Taranis running OpenTx see [here](Tx-Taranis.md)) - Turnigy 9XR Pro (for Turnigy 9X see [here](Tx-FlyskyTH9X.md)) @@ -21,7 +21,7 @@ Serial mode is only supported by the erSky9X firmware. Loading this firmware is erSky9X is well documented, the slightly outdated erSky9X documentation is [here](http://openrcforums.com/forum/viewtopic.php?f=5&t=6473#p90349). You may find the new Er9x manual very helpful in understanding Ersky9x as the two firmwares are very closely related. It provides more detailed explanations and numerous relevant programming examples and is available [here](http://openrcforums.com/forum/viewtopic.php?f=5&t=6473#p90349). -###Enabling Serial Mode +### Enabling Serial Mode 1. Confirm that the MULTI-Module has the required physical connections between the pins on the back of the Tx and the ATMega328 microprocessor. This may require some soldering and depends on which version of the MULTI-Module you have. Check out your module’s hardware page under the section **Enabling your module for Serial** for details. Click on the image that corresponds to your MULTI-Module on the [hardware](Hardware.md) page. 1. Plug in your MULTI-Module into the transmitter module bay. If you have a rotary protocol selection switch, turn the switch to position 0 to put the unit into Serial mode. 1. Ensure throttle is down and all switches are in the start position and power up the Tx. The red LED on the MULTI-Module should be flashing with a period of about 1 second indicating that it has not established a valid serial link with the Tx. This is expected as we have not set up the Tx yet. @@ -29,13 +29,13 @@ erSky9X is well documented, the slightly outdated erSky9X documentation is [here 1. In the Model Setup menu scroll down to the **Protocol** submenu and change the RF settings to MULTI. This should reveal a set of additional options (like Protocol and Options) 1. The red LED on the MULTI-Module should briefly flash and then remain solid. This confirms that the MULTI-Module has established serial communication with the Tx. If the red LED on the module continues to flash at a period of about 1 seconds then it signals that serial communication has not been established. Check your settings under the model menu as described above and check that the protocol selection switch on the module is at 0 (enable Serial mode). If there is still no communication, power down and power up the Tx. Finally check that you have correctly enabled your module for serial as described on the hardware page for your module under the heading "Enabling your module for Serial". Click here to access the [hardware](Hardware.md) and then click on the picture of your module. -###Protocol Selection in Serial mode +### Protocol Selection in Serial mode To select the protocol: 1. In the Model Setting menu, scroll through the available options under the MULTI protocol - 1. Depending on which protocol you have selected you may be required to select a sup-protocol and options. For example, there are three protocols that correspond to FrSky recievers: FrSky_V, FrSky_D and FrSky_X. In some cases the sub-protocols have options that could specify the number of channels, packet frame rate or fine frequency tuning. Check out the [Protocol Details](Protocol_Details.md) page for detailed information and suggestions regarding the sub-protocols and options. The picture below shows the settings in the erSky Model Setup menu for FrSkyX subprotocol with {mike to insert} options: + 1. Depending on which protocol you have selected you may be required to select a sup-protocol and options. For example, there are three protocols that correspond to FrSky recievers: FrSky_V, FrSky_D and FrSky_X. In some cases the sub-protocols have options that could specify the number of channels, packet frame rate or fine frequency tuning. Check out the [Protocol Details](../Protocols_Details.md) page for detailed information and suggestions regarding the sub-protocols and options. The picture below shows the settings in the erSky Model Setup menu for FrSkyX subprotocol with {mike to insert} options: {mikeb to send simple picture} -###Binding in Serial mode +### 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. 1. Press Enter again to exit Bind mode