Releases: pascallanger/DIY-Multiprotocol-TX-Module
Multiprotocol v1.2.1.76
Change Log
- New scanner protocol: 2.4GHz spectrum analyzer available in the upcoming 2.3 OpenTX version
- XN297Dump: added enhanced mode
- GW008: fixed
- CHECK_FOR_BOOTLOADER now set by default
- New multi boards for STM32 1.1.5 and Atmega328 1.0.8 which simplify the compilation/upload and default versions.
- New pre-compiled binary file names / types, including debugging builds
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.71
Change Log
- New Flyzone protocol
- New ZSX protocol
Compiled Files
Multiprotocol hex/bin files attached can be used to flash the multi module.
While they are fully working it's really easy to compile them with you own settings by modifying the file _Config.h and following the compile and upload documentation.
They have been compiled with the source files from this release using the default settings AETR, telemetry enabled, serial mode enabled with inversion and ppm mode enabled using default table.
STM32 Builds (file names beginning with 'MULTI-STM_')
Use Flash-Multi to upload the firmware.
- All radio modules and protocols are included in all builds
- Files with TXFLASH in the name are built with a bootloader and USB support for flashing from a transmitter or via the module's USB port
- Files with FTDI in the name are built without a bootloader or USB support for flashing using an FTDI adapter
- OpenTx/JumperTX version (files with OPENTX in the name) have the
MULTI_TELEMETRYparameter enabled
Atmega328 Builds (file names beginning with 'MULTI-AVR_')
- Only 1 RF module and associated protocols have been included in each hex to fit in the Atmega328. For example Multiprotocol_Vxxxx_A7105.hex means that only protocols depending on A7105 protocols 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
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.69
Change Log
- New Traxxas protocol
- Global frequency tunning for all protocols using the CYRF6936 by adjusting channel 15 when enabled
- Fixed DSM telemetry with some RXs (R720X)
- Changed default DSM_THROTTLE_KILL_CH to use channel 14
Compiled Files
Multiprotocol hex/bin files attached can be used to flash the multi module.
While they are fully working it's really easy to compile them with you own settings by modifying the file _Config.h and following the compile and upload documentation.
They have been compiled with the source files from this release using the default settings AETR, telemetry enabled, serial mode enabled with inversion and ppm mode enabled using default table.
STM32 Builds (file names beginning with 'MULTI-STM_')
Use Flash-Multi to upload the firmware.
- All radio modules and protocols are included in all builds
- Files with TXFLASH in the name are built with a bootloader and USB support for flashing from a transmitter or via the module's USB port
- Files with FTDI in the name are built without a bootloader or USB support for flashing using an FTDI adapter
- OpenTx/JumperTX version (files with OPENTX in the name) have the
MULTI_TELEMETRYparameter enabled
Atmega328 Builds (file names beginning with 'MULTI-AVR_')
- Only 1 RF module and associated protocols have been included in each hex to fit in the Atmega328. For example Multiprotocol_Vxxxx_A7105.hex means that only protocols depending on A7105 protocols 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
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.67
Change Log
- Mandatory upgrade of the Multi AVR (1.0.7) and STM32 (1.1.4) boards fixing the source path space issue
- New Redpine protocol
- New POTENSIC protocol
- V761 protocol: additional IDs
- GD00X: add low/high rates
- Common deadband code applied to: GD00X aileron, KF606 aileron, POTENSIC throttle
- XN297Dump: improved packet timer
- BUGS and BUGSMINI protocols: EEPROM modification, need to rebind models
- Devo protocol: selectable number of channels using sub_protocol
Compiled Files
Multiprotocol hex/bin files attached can be used to flash the multi module.
While they are fully working it's really easy to compile them with you own settings by modifying the file _Config.h and following the compile and upload documentation.
They have been compiled with the source files from this release using the default settings AETR, telemetry enabled, serial mode enabled with inversion and ppm mode enabled using default table.
STM32 Builds (file names beginning with 'MULTI-STM_')
Use Flash-Multi to upload the firmware.
- All radio modules and protocols are included in all builds
- Files with TXFLASH in the name are built with a bootloader and USB support for flashing from a transmitter or via the module's USB port
- Files with FTDI in the name are built without a bootloader or USB support for flashing using an FTDI adapter
- OpenTx/JumperTX version (files with OPENTX in the name) have the
MULTI_TELEMETRYparameter enabled
Atmega328 Builds (file names beginning with 'MULTI-AVR_')
- Only 1 RF module and associated protocols have been included in each hex to fit in the Atmega328. For example Multiprotocol_Vxxxx_A7105.hex means that only protocols depending on A7105 protocols 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
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.59
Change Log
- V761 new protocol
- KF606 new protocol
- XN297 Dump new protocol
- Bayang/DHD_D4 new subprotocol
- BUGSMINI/3H new subprotocol
- AFHDS2A stop bind process when requested to fix some RX binding issues
- WFly frequency tunning
- XN297L emulation layer using CC2500 plus frequency tunning, protocols updated: GD00X, KF606, V911S and MJXQ/E010
Compiled Files
Multiprotocol hex/bin files attached are only for reference/test purposes.
While they are fully working it's really easy to compile them with you own settings by modifying the file _Config.h and following the compile and upload documentation.
They have been compiled with the source files from this release date using the default settings AETR, telemetry enabled, serial mode enabled with inversion and ppm mode enabled using default table.
Atmega328 Builds (file names beginning with 'MULTI-AVR_')
- Only 1 RF module and associated protocols have been included in each hex to fit in the Atmega328. For example Multiprotocol_Vxxxx_A7105.hex means that only protocols depending on A7105 protocols 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
STM32 Builds (file names beginning with 'MULTI-STM_')
- All radio modules and protocols are included in all builds
- Files with TXFLASH in the name are built with a bootloader and USB support for flashing from a transmitter or via the module's USB port
- Files with FTDI in the name are built without a bootloader or USB support for flashing using an FTDI adapter
- OpenTx version (files with OPENTX in the name) have the
MULTI_TELEMETRYparameter enabled
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
- ersky9x test builds along with the Multi.txt file to be placed at the root of the SD card.
- OpenTX for Taranis
- JumperTX for T16
Multiprotocol v1.2.1.39
Change Log
- Too many things
Compiled Files
Multiprotocol hex/bin files attached are only for reference/test purposes.
While they are fully working it's really easy to compile them with you own settings by modifying the file _Config.h and following the compile and upload documentation.
They have been compiled with the source files from this release date using the default settings AETR, telemetry enabled, serial mode enabled with inversion and ppm mode enabled using default table.
Atmega328 Builds (file names beginning with 'MULTI-AVR_')
- Only 1 RF module and associated protocols have been included in each hex to fit in the Atmega328. For example Multiprotocol_Vxxxx_A7105.hex means that only protocols depending on A7105 protocols 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
STM32 Builds (file names beginning with 'MULTI-STM_')
- All radio modules and protocols are included in all builds
- Files with TXFLASH in the name are built with a bootloader and USB support for flashing from a transmitter or via the module's USB port
- Files with FTDI in the name are built without a bootloader or USB support for flashing using an FTDI adapter
- OpenTx version (files with OPENTX in the name) have the
MULTI_TELEMETRYparameter enabled
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
- ersky9x test builds along with the Multi.txt file.
- OpenTX for Taranis
Multiprotocol v1.2.0
ChangeLog:
- Many fixes and optimizations
- Documentation updates
- New Multi 4in1 boards to ease the compilation of Atmega & OrangeRX TX (v1.0.2) and STM32 (v1.0.3). Make sure to use them!!!
- Flash from TX option if you are using ersky9x for all 3 platforms Atmega, STM32 and OrangeRX TX
- Failsafe settings for S-FHSS, Hisky/HK310, FrSkyX, Walkera, Devo and AFHDS2A
- SFHSS improvements
- DM002 improvements
- New CABELL protocol
- New Esky150 protocol
- New Bayang/IRDRONE sub-protocol
- New H8_3D protocol with sub_protocols H8_3D, H20H, H20Mini and H30Mini
- New HUBSAN sub_protocols H107, H301 and H501
To access new protocols and features from er9x/ersky9x/OpenTX, you'll need to upgrade to the latest version available here:
- er9x test builds
- ersky9x test builds along with the Multi.txt file.
- OpenTX for Taranis
Multiprotocol v1.1.6
Multiprotocol hex/bin files attached have been compiled with the source files dated of 19/12/2016 using the default settings AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table. INV versions have inverted telemetry set which is a must for OpenTX while the others are compatibe with er9x/ersky9x.
For Atmega328 boards, some RF modules (and associated protocols) have been included in each hex to fit in the Atmega328. For example Multiprotocol_V1.1.5_A7105-CC2500-CYRF6936.hex means that protocols depending on NRF24L01 protocols are excluded.
For STM32 boards, all protocols are included.
For OrangeTX, all CYRF6936 based protocols are included.
If you require a more specific configuration, you can build your own version by modifying the _Config.h file as explained in the documentation.
ChangeLog:
- Many fixes and optimizations
- New blink pattern if no PPM signal is present
- After 70ms of input signal (serial or PPM) absence the current protocol is paused. The protocol is resumed as soon as the input signal reappears.
- New protocol Flysky AFHDS2A with telemetry sent either using FrSky Hub or forwarded untoouched to the TX (ersky9x/OpenTX)
- New Q2X2 protocol with sub_protocols Q222/Q242/Q282
- New Flysky sub_protocol CX20
- New Bayang sub_protocol H8S3D
- New Bayang telemetry using FrSky Hub for Silverxxx firmwares
- New MT99xx sub_protocol FY805
- New V2X2 sub_protocol JXD506
- New FY326 sub_protocol FY319
- New Hontai sub_protocol FQ777_951
- New MJXQ sub_protocol H26HW
- MJXQ sub_protocol E010: 16 TX IDs + associated frequencies
To access new protocols and features from er9x/ersky9x/OpenTX, you'll need to upgrade to the latest version available here:
Multiprotocol v1.1.5
Multiprotocol hex/bin files attached have been compiled with the source files dated of 17/10/2016 using the default settings AETR, telemetry enabled, serial mode enabled and ppm mode enabled using default table. INV versions have inverted telemetry set which is a must for OpenTX while the others are compatibe with er9x/ersky9x.
For Atmega328 boards, some RF modules (and associated protocols) have been included in each hex to fit in the Atmega328. For example Multiprotocol_V1.1.5_A7105-CC2500-CYRF6936.hex means that protocols depending on NRF24L01 protocols are excluded.
For STM32 boards, all protocols are included.
For OrangeTX, all CYRF6936 based protocols are included.
If you require a more specific configuration, you can build your own version by modifying the _Config.h file as explained in the documentation.
ChangeLog:
- Many fixes and optimizations
- DSM fully rewritten with support for DSM2/22ms/1024, DSM2/11ms/2048, DSMX/22ms/2048 and DSMX/11ms/2048. An AUTO mode is also available in serial mode to select automatically the best settings for a given RX.
- STM32 boards support added
- Validation of _Config.h file configuration: error message is displayed during compilation in case of conflicts
- Added Hontai/X5C1 protocol
- Added E010 transmitter IDs
- PPM telemetry is using the original protocol serial speed (8n1): 9600 for FrSkyD (includes Hubsan), 57600 for FrSkyX and 125000 for DSM
- Updated Documentation: big thanks to Gerrye!
To access new protocols and features from er9x/ersky9x/OpenTX, you'll need to upgrade to the latest version available here:
Multiprotocol v1.1.4
Multiprotocol hex files attached have been compiled with the source files dated of 04/09/2016.
As you can see only some RF modules (and associated protocols) have been included in each hex to fit in the Atmega328. For example Multiprotocol_V1.1.4_A7105-CC2500-CYRF6936.hex means that protocols depending on NRF24L01 protocols are not included.
If you require a more specific set of protocols, you can build your own version by modifying the _Config.h file and compile under the Arduino IDE.
ChangeLog:
- Many fixes and optimizations
- FrSkyV: new protocol added
- MJX: fixed
- MJXQ/E010: new protocol added
- Updated Documentation
To access new protocols from er9x/ersky9x/OpenTX, you'll need to upgrade to the latest version when available here: