pascallanger/DIY-Multiprotocol-TX-Module v1.2.1.85

Multiprotocol v1.2.1.85

on GitHub

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_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
• 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 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].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
• JumperTX for T16 Compiled FW or GitHub for latest version