Skip to content

Multiprotocol v1.3.0.53
Compare
Choose a tag to compare
@pascallanger pascallanger released this 12 Jan 15:22
1.3.0.53
6a9b6ed

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_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:

Assets 26
Loading