Releases: pascallanger/DIY-Multiprotocol-TX-Module
Releases · pascallanger/DIY-Multiprotocol-TX-Module
Multiprotocol v1.3.1.49
Change Log since v1.3.1.36
- FrSky R9
- FCC sub protocol added
- V2X2
- Fixed issue from last update...
- Kyosho
- New protocol
- Surface protocol called FHSS introduced in 2017. Transmitters: KT-531P, KT-431PT, Flysky Noble NB4 (fw>2.0.67)...
- Flysky AFHDS2A
- New sub-protocol supporting up to 16 channels with LQI on channel 17
- FrSkyX/X2
- New "Cloned_8CH" subprotocols for 8 channels transmission (instead of only 16 previously)
- RadioLink
- New protocol
- Surface sub protocol, TXs: RC4GS,RC6GS. Compatible RXs:R7FG(Std),R6FG,R6F,R8EF,R8FM,R8F,R4FGM,R4F and more
- Air sub protocol, TXs: TXs: T8FB,T8S. Compatible RXs:R8EF,R8FM,R8SM,R4FG,R4F and more
- Telemetry enabled
- Only 64 IDs, cycle through then using RX number
- Height
- Previously called Flyzone but renamed using the real manufacturer name
- New sub protocol 5ch: the one available so far
- New sub protocol 8ch: upgraded version of the protocol to 8 channels
- OpenTX Multi Lua scripts
- MultiChannelsUpdater.lua and MultiChan.txt updated with all the latest protocols and sub protocols
Multiprotocol v1.3.1.36
Change Log since v1.3.1.24
- FrSky R9 Flex 868/915
- fixed 868 bind and control
- added additional ID byte: all RXs must be rebound
- added bind options: CH1-8/CH9-16 and Telem ON/OFF. Need OpenTX 2.3.10 not released yet.
- added full telemetry RX to TX (tested)
- added telemetry TX to RX (untested)
- TQly is now the percentage of number of packets received 100%=perfect..0%=signal lost
- FrSkyX / X2
- improved telemetry for AVR
- TQly is now the percentage of number of packets received 100%=perfect..0%=signal lost
- FrSky_RX
- additonal ID byte saved/checked in D8 RX or Clone mode
- FrSkyD
- fix Cloned sub protocol
- New STM32 board v1.1.8
- upgrade using Arduino's Boards Manager
- need to update the driver to libusbK. Flash Multi v0.4.0 offers an easy way to do it.
Multiprotocol v1.3.1.24
Change Log since v1.3.1.9
- T18 5-in-1 initial support
- DSM
- servo refresh rate is by default 22ms and can't be changed until the OpenTX code is modified to give the option to switch to 11ms. The current display on OpenTX of DSM 2/X 11/22ms is the frame rate which is not the servo refresh rate.
- SAFE channel association documentation
- DSM RX
- changed Aileron and Rudder direction to match original radio convention
- bind can be ended on GUI
- increased retries during bind
- HoTT
- Telemetry fix, the telemetry link was lost under certain situations
- Q90C
- full protocol options support
- V2x2
- new sub protocol MR101
- full code rewrite
- V761
- only 5 IDs selected by RX number
- sub protocols 3CH and 4CH
- additonal channels for Calibration, Flip, Return activation and Return on/off
- OpenTX Multi Lua scripts
- new folder with all the OpenTX lua scripts related to Multi
- MultiChannelsUpdater.lua and MultiChan.txt updated with all the latest protocols and sub protocols
Multiprotocol v1.3.1.9
Change Log since v1.3.1.1
- New sub protocol for Pelikan: Lite
- New sub protocol for Bayang: QX100
- New protocol Q90C: this protocol has limited features. If you have a TX then contact me on GitHub or RCGroups.
- Protocol DSM RX: changed Aileron and Rudder direction to match original radio convention.
- Protocol HoTT:
- LBT implemented.
- Full telemetry support including auto sensors discovery.
- Full sensors text config.
- Available in OpenTX 2.3.8N226
- New sub protocols Sync and No_Sync:
- Sync offers better telemetry performance but the RXs/sensors must use the latest firmware.
- No_Sync is for compatibility mode with old receiver firmwares but you should upgrade...
Multiprotocol v1.3.1.1
Change Log since v1.3.0.95
- New protocol DSM RX: To be used as a source for Multi/trainer available in OpenTX. Auto detect DSM2/X 11/22ms and 1024/2048 formats at bind time
- New protocol JJRC345
- HoTT: Full telemetry support including auto sensors discovery. Full sensors text config. It should be available in OpenTX 2.3.8N226
- Devo: add basic telemetry TX RSSI, A1 and A2
Multiprotocol v1.3.0.95
Change Log since v1.3.0.91
- New protocol eSky 150 v2
- FrSky D16 LBT v1.x & 2.1: adjust LBT detection threshold and LBT power to match ETSI requirements
Multiprotocol v1.3.0.91
Change Log since v1.3.0.87
- Protocols appearing in alphabetic order, only available in the latest OpenTX 2.3.8 nightlies (not published yet)
- Video in action: https://youtu.be/eiExuVHtWDw
- Only show protocols which are installed in the Multi module
- the only exception is FrSky D8 and V8 which will still appear if disabled but will show up as invalid
- RX protocols have now a disable LNA feature and less unuseful settings
- New protocol Skyartec
Multiprotocol v1.3.0.87
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
Multiprotocol v1.3.0.81
This is a pre-release to test the new FrSky X v1.x / v2.1.0 code (ACCST D16 FCC/LBT) and PROPEL.
Fly with caution and report success/failures: https://www.rcgroups.com/forums/showthread.php?t=2165676&goto=newpost
Change Log since v1.3.0.79
- Protocol PROPEL: New
- Compatible model: PROPEL 74-Z Speeder Bike
- Protocol: PROPEL (66)
- Sub protocol: none
- Autobind protocol
- Extended limits not supported
- Telemetry supported: LQI, life, model status (flying, taking off, landing, landed/crashed,...)
- 14 channels in use due to many features
Multiprotocol v1.3.0.79
This is a pre-release to test the new FrSky X v1.x and v2.1.0 code (ACCST D16 FCC/LBT).
Fly with caution and report success/failures: https://www.rcgroups.com/forums/showthread.php?t=2165676&goto=newpost
Change Log
- Protocol FrSkyX:Rewrite of the full FrSkyX code to support both v1 and v2.1.0 with FCC and LBT.
- FrSky v1 accessible as usual.
- FrSky v2.1.0 accessible through the protocol 64=FrSkyX2 with the same sub-protocols as v1.
- The LBT feature is now fully implemented on the TX and turned on for both v1 LBT and v2.1.0 LBT.
- For v2.1.0, to access the bind functions Telem=on/off, CH1-8/9-16 and bidirectional SPort (SxR setup for example), you need to update OpenTX to the latest 2.3.8 nightly 170
- Protocol FrSkyRX: chanskip test to improve the RX reliability against bad frames
Compiled Files
Multiprotocol bin files attached can be used to flash the multi module.
While these files are fully working, it's easy to compile the firmware with your own settings by modifying the configuration file, _Config.h, and following the compile and upload documentation.
The attached files have been compiled with the source from this release using the default settings, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
Channel Orders
3 channel orders: AETR, RETA, and TAER are denoted in the firmware file names.
- Each build expects to receive channel data from the radio in the order given in the name
- You must match the channel order of your models to the order which your Multi-module expects
E.g. If you configure your models as TAER, flash your Multi-module with firmware with -taer- in the name.
STM32 Builds (file names beginning with 'multi-stm-')
- All files contain all protocols
- erSkyTx version (files with erskytx in the name) have the
MULTI_STATUSparameter enabled - OpenTx/JumperTX version (files with opentx in the name) have the
MULTI_TELEMETRYparameter enabled - Files with inv in the name have
INVERT_TELEMETRYenabled - this is the default - Files with noinv in the name have
INVERT_TELEMETRYdisabled - Files with ftdidebug in the name have
DEBUG_SERIALenabled and are built for debugging with a USB-to-serial adapter (built-in for Jumper 4in1 modules) - Files with usbdebug in the name have
DEBUG_SERIALenabled and are built for debugging via the native USB port - All files except the ftdidebug files have support for the native USB port and the bootloader
Choosing the right firmware file:
- Choose erskytx or opentx or ppm to match your radio
- Inverted telemetery (inv in the name) for external modules
- None inverted telemetery (noinv in the name) for internal modules
- debug or xn297dump files are for testing purposes or dumping data from unknown models, not for regular use
For example, for a Jumper JP4IN1, iRangeX IRX4, etc., and a radio running OpenTX or JumperTX you probably want the file named multi-stm-opentx-inv-[version].bin.
Use Flash-Multi to upload the firmware.
Atmega328 Builds (file names beginning with 'multi-avr-')
- Only one RF module and associated protocols have been included in each hex file in order to fit in the Atmega328. For example
multi-avr-txflash-A7105-inv-[version].hexmeans that only protocols using the A7105 RF module are included. - There are no files for the NRF24L01 as there are too many protocols to fit in a single build
- Files with txflash in the name are built with the OptiBoot bootloader for flashing from a transmitter
- Files with usbasp in the name are built without a bootloader for flashing using a USBasp programmer
Use AVRDUDESS to upload the firmware.
OrangeRX Builds (file names beginning with 'multi-OrangeRX-')
- All CYRF6936 based protocols are included
Radio Firmware
To access new protocols and features from er9x/ersky9x/OpenTX, you'll need to upgrade to the latest version available here:
- er9x test builds
- erskyTX test builds along with the Multi.txt file to be placed at the root of the SD card.
- OpenTX for Taranis and T16 -> to access the latest features use the 2.3.8 nightlies