expresslrs ExpressLRS V3.3.0-RC2

[WaF Bot]

Changes since RC1

• Don't copy the extra binaries for ESP32 #2245
• Fix compile error with DEBUG_RCVR_LINKSTATS #2244
• Removing WiFi upload methods from STM targets #2253
• Fix no backpack overwriting channels #2255
• Fix Airport running at F1000 without a handset #2257
• ADC attenuation for ESP32 targets #2252 #2268
• Respect when someone declines to flash the wrong target #2267
• Change airport packet type #2258
• Fix LBT TLM reception bug #2271
• More fixes for the flasher #2273
• Speed bootup of ESP32 RXes without a vario #2274
• RadioMaster targets ER4, ER6, ER6-G, ER6-GV, ER8, ER8-G, ER8-GV #2247
• BETAFPV Super-P 2.4GHz and 900MHz #2251
• GEPRC True Diversity 2.4GHz #2265
• iFlight 2.4 & 900 V2 TX modules #2281

WARNING - RC2 contains a breaking change for Airport users. Anyone using Airport must update both TX and RX.

Getting Started 3.0 Documentation

The important stuff

• Arming must be on AUX1 for safety and feature reasons, having this fixed allows us to maintain small packet sizes and deliver better aux channel options
• Be sure to flash both the TX and RX.
• Lua script MUST be updated to elrsV3.lua and is backwards compatible with 2.x. Get it here: Lua

Compatibility

This is a minor version release (new features, targets and bug-fixes only) and is compatible with V3.X.

Who should update from V3.2?

• Anyone who likes the sounds of the hit list of features below!
• Anyone using a radio with a color LCD should update the Lua script for speed improvements
• Owners of the new hardware listed below

New Features

Cloud Builds

“ELRS is great, but the first-time setup was a PITA!”
This is one of the main complaints we see across the groups about ExpressLRS.

We understand the challenges faced during the initial setup process of ExpressLRS, with many users expressing their frustration. In version 3.3, we are doing something to improve this, starting with the introduction of pre-compiled builds.

While our "just-in-time" firmware compilation approach has served us well in the past, it has also caused inconvenience and frustration. Various factors, some of which were completely out of our control (e.g. updates to the platformio framework), have resulted in failed configurator builds, leading to user dissatisfaction.

To overcome these challenges, we have made a significant change in v3.3. Instead of relying on local compilation for release versions, the configurator will now seamlessly retrieve pre-built firmware from the cloud and flash it onto your device. This shift not only drastically reduces firmware update times from minutes to seconds but also eliminates many annoying build issues, where users are faced with the dreaded red "failed build" error message in the Configurator.

Make sure you have updated to version 1.6.0-rc1 of the Configurator to take advantage of this awesome new feature: https://github.com/ExpressLRS/ExpressLRS-Configurator/releases

AirPort

#1904
In the hobby and commercial UAV industry, securing a dependable telemetry downlink alongside RC control often presents challenges in terms of cost, availability, and reliability. While Dragonlink has been the go-to option for a reliable long-range RC + telemetry link, it can be difficult to find in stock and tends to be expensive. Other alternatives, such as the RFD900 modems, are typically limited to 900MHz and also suffer from availability and cost issues.

This is where AirPort comes to the rescue.

AirPort offers a firmware option that transforms a standard ExpressLRS transmitter and receiver pair into a bidirectional transparent serial data link over the air. This enables seamless serial data communication between the connected devices, supporting any protocol of your choice, including MAVLINK (Ardupilot), MSP (Betaflight and INAV), or any other telemetry protocol that can be transmitted serially. This feature may also be useful for interfacing wirelessly with other ground devices, such as antenna trackers or similar.

Thanks to the increasing availability of ExpressLRS hardware, AirPort makes it effortless and cost-effective to incorporate an inexpensive telemetry uplink/downlink into your UAV models.

New Receiver Protocols

In previous versions, the only receiver protocol available for connecting ELRS to your FC was CRSF. While CRSF performs admirably in most scenarios and remains the preferred option if your hardware is compatible, what if your hardware doesn't support it? Typically, this would require the use of an additional protocol converter, such as the CRSF to SBUS converter.

In this release, we are delighted to introduce not just one, but THREE new receiver protocols, along with inverted options tailored for specific hardware requirements. This expanded protocol support ensures greater flexibility and compatibility, empowering you to seamlessly integrate ELRS with a wider range of hardware options.

SBUS

#2094
That’s right, you read that correctly… after all that bitching and whining from us in the past, ELRS finally added SBUS as a receiver protocol! This is particularly useful for those closed-source FCs & flight stabilizers that only allow SBUS as an input. We’ve also added an inverted version of SBUS (which is normally inverted, so technically it’s un-inverting it - insert Xzibit meme) for hardware that doesn’t have the inverter on the UART.

PWM receivers can also be configured to output serial on some pins and select serial protocol, so now you can have CRSF/SBUS etc and PWM simultaneously!

SUMD

#2137
Graupner HoTT SUMD joins SBUS as another user selectable receiver protocol, which can be found in many open source flight control firmwares (BF, INAV, ARDU) as well as a variety of flybarless controllers (helis).

DJI Ronin RS Pro

#2140
The DJI RS Pro series, including the RS2 Pro and RS3 Pro gimbals, are renowned professional camera stabilizers often utilized on cinelifters for active stabilization of high-end cinema-grade cameras. While these gimbals can be controlled via an SBUS interface, DJI’s janky implementation of the protocol demands precise channel endpoints to trigger various functions, such as recentering.

To spare you the frustration of manually adjusting mixer settings as you attempt to discover the exact (and poorly documented) values expected by DJI for channel outputs, the ELRS team has introduced a dedicated version of SBUS, specifically tailored to these gimbals. This special version is preconfigured to seamlessly integrate with your RS2 Pro or RS3 Pro. For more detailed information regarding installation, please refer to the associated pull request: #2140 or check out a quick demo here: https://youtube.com/shorts/OPZykP-bP4k

Gemini and Diversity for 900MHz

#1993
Dry those eyes #Team900, ELRS now has True Diversity 900MHz receivers. A much sought after piece of gear that was frequently requested is now a reality. Check the new targets list for BETAFPVs Super-D, and I'm sure there will be more to follow!

But that's not all… with diversity also comes Gemini! Need a 900 Gemini Tx? Be sure to go and pester your favorite FPV manufacturer.

DVDA for 900MHz

#2089
Exciting news! #Team900 is now part of the DVDA family! With the latest release, we introduce the new D50 packet mode, leveraging the 200Hz OTA modulation parameters to transmit 4 repeat packets across 3 frequencies. This approach is identical to the functionality of D250 for the 2.4GHz frequency range.

The primary goal of the D50 packet mode is to significantly enhance Link Quality (LQ) in RF-congested environments, particularly when flying alongside other pilots operating on the same frequency domain. By providing 4 transmission attempts for each packet, distributed across multiple frequency hops, you can enjoy improved reliability and stability during flights.

Wireless head tracking

#2060
Support has been added into VRx & TX backpack as well as the main firmware to allow head tracking information to be sent wirelessly from the goggles to the TX module and then mixed into the channel output. At present, this functionality is exclusively supported by HDZero goggles, however we are optimistic that other goggle manufacturers will follow suit and incorporate compatibility with this exciting feature.

16 channel PWM Receivers

Target support has been added for 16 channel PWM receivers in both 2.4G and 900M flavors. Not only that, they are true diversity!

Any PWM channel can be set to a combination of the available PWM modes e.g. 400Hz, 10kHz PWM, On/Off switch. A single PWM channel can also be reassigned to a serial protocol (CRSF, Sbus etc). You want a FC connected plus native PWM output, you got it.

Option to disable TX backpack

#2054
We understand that not everyone requires or utilizes the TX backpack feature in their transmitter setup. While enjoying a few cold ones at the ELRS headquarters, we asked ourselves: “If you’re not using the backpack, why have it sitting there chewing power?”, so we’ve introduced a convenient option to disable the TX backpack functionality. This can save a little juice (~0.3W) on the transmitter. Zorro users rejoice!

MSP VTX support for combined RX/VTX

#2007
Proprietary VTX control protocols SUCK! That's right Smartaudio and Tramp… you guys suck. These protocols are owned by commercial manufacturers who never seem to do a good job at properly documenting the protocol specs, and have low motivation to extend their protocols for features that don’t directly interest them and their bottom lines.

MSP control for VTXs is a breath of fresh air that alleviates many of these pains, and now it’s supported in ELRS for hardware where the VTX is controlled by the same MCU as the receiver.

Gemini Antenna mode selection

#2002
Allows you to run a Gemini TX in different antenna configurations:

• Gemini
• Ant1
• Ant2
• Switch - alternating single antenna output

Auto detect CRSF VBAT sensor

#1968
If you have a receiver with analog VBAT and use a CRSF based VBAT sensor, then the receiver will favor the CRSF based sensor automatically.

New Targets

Receivers

• Foxeer 900MHz receiver
• Happymodel EP5W and EP6W PWM receivers
• NewBeeDrone 2.4GHz antenna diversity receiver
• Generic 900MHz true diversity 16 PWM target
• Generic 900MHz true diversity target
• AnyLeaf targets, Diversity, true diversity and H7 FC Integrated
• RadioMaster ER4, ER6, ER6-G, ER6-GV, ER8, ER8-G, ER8-GV PWM receivers
• BETAFPV Super-D 900MHz true diversity receiver
• BETAFPV Super-P 2.4GHz and 900MHz true diversity PWM receivers
• GEPRC 2.4GHz true diversity receiver
• iFlight 2.4 & 900 V2 TX modules
• And more…

Maintenance

• True diversity RSSI update on both radios, provides faster update to RSSI for second radio #2143
• Updates true diversity dynamic power to behave more like antenna diversity receivers #2143
• Updates to BLE Joystick for better compatibility #2050
• Display backpack version in Lua, also indicates that the backpack is working #2041
• Power reduction (~0.04W) by idling second core when possible on ESP32 devices #2021

Fixes

• Faster loading of Lua script on color LCD radios #2183
  • On all radios really, but color LCD radios such as the TX16S on EdgeTX 2.8.0+ now load nearly twice as fast. Requires elrsV3.lua update.
• Fix receivers which do not have a minimum power level of 10mW #2177
• Drop max packet rate to <= 200Hz for 115k baud connections, this fixes the “Loading…” issue for older radios #2170
• Fix power creep on TTGO V2 as TX. #2167
• General Web-UI Fixes
  • Fix error reporting in wifi update where it reports “target mismatch” instead of the underlying error #2174
  • Fix error accessing button 2 if the TX has only one button #2166
  • Only show “Reset Runtime Options” button if things have been changed
  • Clearly display the source of the binding ID with new chrome
• Always use flashed options after a new flash, fixes the problem where new flashed bind-phrase did not take effect #2149
  • Previously the Web-UI always overrode any flashed value, now flashing the device clears any overridden values from the first tab and will use the flashed configuration.
• VBAT measurement fixes for ESP32-based receivers #2144
  • If it was reporting a value far too low, or would start reading 0V if the actual voltage got too low.
• Reduced RAM usage of Unified hardware definitions, can make wifi AP mode slightly more usable. #2080

Known Issues

• On performing WiFi updates to some TX modules you may get a “Bad Size Given” error. If you get this error, it can be remedied by either flashing via UART, or flashing the repartitioner from https://github.com/ExpressLRS/repartitioner/releases/download/1.0/repartitioner.bin then reflashing via wifi after it has completed. For more information about the problem see https://github.com/ExpressLRS/repartitioner/

Acknowledgements

• We would like to acknowledge the contributions of Vitroid, Senk0, King David, and FlyingBaguette, whose diligent testing played a part in shaping this RC release. Your assistance has been truly appreciated.

Lire la source