Releases: pascallanger/DIY-Multiprotocol-TX-Module
Multiprotocol v1.3.0.76
Change Log
- Protocol XK: new protocol supporting X450, X420/X520 (others?), sub-protocols X450 & X420
- Protocol ESky: additional sub-protocol ET4 (transmitter name)
- Protocol V911s: additional sub-protocol E119 (Eachine heli)
- Protocol FrSky R9: supports 915/868MHz 8/16Channels, a SX1276 LoRa chip has to be added to the multi board
- Protocol FrSkyD: fixed a lagging issue with some receivers. All receivers must be rebound
- Protocol Hitec: fixed bind issue with some receivers
- Protocol SLT: use the CC2500 emulation layer if requested/available through the rf freq tuning (0=NRF24L01, other than 0 will use and tune the CC2500 instead)
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.4 nightlies
Multiprotocol v1.3.0.53
Change Log
- Protocol FrSkyX: add bind options CH1-8/CH9-16 & Telem ON/OFF => need an OpenTX nightly build
- Protocol Flyzone: add channel 5
- Protocol Bayang RX: improved RX code and timing
- Protocol FrSky RX: fix bind which could fail if another FrSky TX was transmitting around
- Protocols using the XN297L@250K emulation layer (V911S, KF606, GD00x,...): XN297L@250kbps is emulated by default with the NRF24L01. If option (freq tune) is different from 0, the CC2500 module (if installed) will be used instead with option being the usual frequency tuning.
- New protocol Pelikan: number 60, no sub protocol, 8 channels AETR, extended limit supported => still work in progress
- New protocol Tiger: model Tiger drone 1400782, number 61, no sub protocol, CH5 Flip, CH6 Light
- Fix erskyTX module status
- Direct inputs: only available when using PPM and STM32, possibility to solder 2 or 3 position switches on some of the free pins of the STM32 to add more channels
- XN297Dump: new auto sub protocol, it will automatically:
- find XN297L packet -> bitrate, scrambling, enhanced...
- use address to filter incoming packets
- find all frequencies
- determine channel order (basic)
- help to find out the changes by only displaying packets when there is a change in the packet
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.4 nightlies
Multiprotocol v1.3.0.47
Change Log
- New receiver protocol Bayang: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md#BAYANG-RX---59
- Esky150: add sub protocols for 4 and 7 channels https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md#esky150---35
- Protocol DSM: solved short range issue on some full telemetry receivers
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.3 nightlies
Multiprotocol v1.3.0.45
Change Log
- New protocol FX816: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md#fx816---58
- Protocol V911S: revert to xn297 emulation
- Protocol DSM: tweak timing to hopefully solve the short range issue on some full telemetry receivers
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.3 nightlies
Multiprotocol v1.3.0.44
This version is a pre-release which means that it has been tested now by a few people but might still contain a couple of bugs. So try it with care.
Please report if you see any issues.
Change Log
- Rewritten protocol sequencer
- Rewritten serial interrupt to allow additional data to be sent from the radio
- Graupner HoTT protocol
- Up to 12 channels
- Basic telemetry: RX Batt, RX Temp, RX RSSI, RX LQI, TX RSSI, TX LQI
- Failsafe
- RX config through lua script. Available in OpenTX 2.3.2
- FrSky SPort bidirectionnal communication: SxR and BF configuration scripts working. Available in OpenTX 2.3.2
- Increase RX number from 16 (0..15) to 64 (0..63). Available in OpenTX 2.3.2
- Increase protocol number from 63 to 255. 127 available in OpenTX 2.3.2
- Allow to disable the auto channel mapping from GUI for protocols like DSM, DEVO, Walkera, Flysky... meaning that when activated CH1 will be CH1 on RX and so on. Available in OpenTX 2.3.2
- Allow to disable full telemetry from GUI. Available in OpenTX 2.3.2
- Send default module channel order to be displayed by the radio. Available in OpenTX 2.3.2
- Send the current protocol name, sub-protocol name, number of subprotocols, failsafe support, disable channel mapping support, option type to the radio to be displayed. Available in OpenTX 2.3.2
- Allow the radio to decide the telemetry inversion. Available in OpenTX 2.3.2
- FrSky RX: auto select the protocol D8/D16/LBT at bind time. Multi Trainer available in OpenTX 2.3.2
- DSM max throw can be enabled from the radio GUI. Available in OpenTX 2.3.2
- Scanner in blocking mode for max performance
- Fix AFHDS2A LQI foward on CH
- Fix failsafe behavior for AFHDS2A, FrSkyX and Hisky
Compiled Files
Multiprotocol hex/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 AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
Channel Orders
Starting with v1.2.1.85 there will be builds for three channel orders: AETR, RETA, and TAER. These 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 - 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 ot opentx to match your radio firmware
- Inverted telemetery is the default (inv in the name) - choose that if you're not sure or don't know
- *debug 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
- JumperTX for T16 Compiled FW or GitHub for latest version
Multiprotocol v1.2.1.85
Change Log
- Flysky AFHDS2A RX: turns the multi module into a Flysky AFHDS2A receiver for training or other purpose. It should be available in OpenTX 2.3.2.
- New multi boards for STM32 1.1.7 and Atmega328 1.1.0 which adds signature to bin files and default versions. Compatible with Flash Multi and OpenTX. Signature details are in Binary_Signature.ino
Compiled Files
Multiprotocol hex/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 AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
Channel Orders
Starting with v1.2.1.85 there will be builds for three channel orders: AETR, RETA, and TAER. These 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 - 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 ot opentx to match your radio firmware
- Inverted telemetery is the default (inv in the name) - choose that if you're not sure or don't know
- *debug 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
- JumperTX for T16 Compiled FW or GitHub for latest version
Multiprotocol v1.2.1.84
Change Log
- Failsafe modification
- The following protocols are supporting failsafe: FrSkyX, Devo, WK2x01, SFHSS, HISKY/HK310 and AFHDS2A
- In Serial mode failsafe is configured on the radio itself.
- In PPM mode and only after the module is up and fully operational, press the bind button for at least 5sec to send the current stick positions as failsafe to the RX.
- Low power selection is authorized by default: OpenTX and ErskyTX will warn if model is set to low power.
Compiled Files
Multiprotocol hex/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 AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
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 - 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 ot opentx to match your radio firmware
- Inverted telemetery is the default (inv in the name) - choose that if you're not sure or don't know
- *debug 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
- JumperTX for T16 Compiled FW or GitHub for latest version
Multiprotocol v1.2.1.83
Change Log
- FrskyX RX: added auto tune RF frequency during bind (Thanks Goebish).
- PPM channel remapping: allow to swap or relocate the first 8 channles to any other channels before handing over to the protocol.
- Atmega module: fixed protocols KF606, GD00X and Potensic.
Compiled Files
Multiprotocol hex/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 AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
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 - 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 ot opentx to match your radio firmware
- Inverted telemetery is the default (inv in the name) - choose that if you're not sure or don't know
- *debug 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
- JumperTX for T16 Compiled FW or GitHub for latest version
Multiprotocol v1.2.1.81
Change Log
- FrskyX RX: turn the multi module into a FrskyX RX for training or other purpose
- Flysky AFHDS2A: enhanced telemetry
- Hitec: enhanced telemetry
- New multi boards for STM32 1.1.6 and Atmega328 1.0.9 which ads signature to bin files and default versions.
Compiled Files
Multiprotocol hex/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 AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table.
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 - 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 ot opentx to match your radio firmware
- Inverted telemetery is the default (inv in the name) - choose that if you're not sure or don't know
- *debug 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
- JumperTX for T16 Compiled FW or GitHub for latest version
v1.2.1.80
Fix FrskyX failsafe hold/no pulse inversion