Change Log since v1.3.0.81
- Protocol FrSkyX and FrSkyX2: improve TX to RX SPort code
- Protocol FrSkyL: New
- Compatible model: L9R RX
- Protocol: FrSkyL (66)
- Sub protocols: LR12 36ms and LR12_6CH 18ms
- Extended limits supported
- Telemetry: no
- Protocol FrSky_RX: RX addition of D16v2.1 FCC/LBT
- Auto detection of the protocol used by a TX transmitting FrSkyD/D8, FrSkyX/D16 v1.xxx FCC/LBT or FrSkyX/D16 v2.1.0 FCC/LBT at bind time..
- For FrSkyX/D16, RX num must match on the master and slave. This enables a multi student configuration for example.
- Protocol FrSky_RX: new subprotocol CloneTX
- This subprotocol makes a clone of a TX identifier transmitting FrSkyD/D8, FrSkyX/D16 v1.xxx FCC/LBT and FrSkyX/D16 v2.1.0 FCC/LBT.
- There are 3 slots available, 1 slot for D8 cloning, 1 slot for FrSkyX (D16v1) cloning and 1 slot for FrSkyX2 (D16v2.1.0) cloning.
- The same TX or different TXs can be used for each slot but a maximum of 1 per slot.
- If you launch the FrSky_RX/CloneTX protocol and do a bind with a TX transmitting with the D8 protocol, it will be saved in the slot D8. Same for D16v1 and D16v2.1 .
- Then the system will alow you to enable cloning as you wish for each model using the FrSkyD/X/X2 "Cloned" subprotocol. This way you can have models working with the original MPM indentifier and models which are shared by both the cloned TX and MPM.
- Notes:
- OpenTX 2.3.8 N184 (nightly) or later is needed to have access to the new FrSky "D8Cloned" and "D16Cloned" subprotocols, D16v2.1 "Cloned" is available under FrSkyX2/Cloned.
- For FrSkyX and FrSkyX2, RX number has to be adjusted on each model to match the original TX model
- For FrSkyD, only the RX number used during bind is cloned -> you can't use RX num anymore