pascallanger/DIY-Multiprotocol-TX-Module 1.3.0.47

Multiprotocol v1.3.0.47

on GitHub

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_STATUS parameter enabled
• OpenTx/JumperTX version (files with opentx in the name) have the MULTI_TELEMETRY parameter enabled
• Files with inv in the name have INVERT_TELEMETRY enabled - this is the default
• Files with noinv in the name have INVERT_TELEMETRY disabled
• Files with ftdidebug in the name have DEBUG_SERIAL enabled 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_SERIAL enabled 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].hex means 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