Skip to content

ExpressLRS V3.2.1
Compare
Choose a tag to compare
@wvarty wvarty released this 03 Apr 02:02
· 300 commits to 3.x.x-maintenance since this release
3.2.1
8dbbdbe
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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 bugfix release (bug-fixes only, no new targets or features) and is compatible with V3.X.

Who should update from V3.2.0?

  • There are minor fixes that benefit all users, so ideally everyone should update, however some fixes will be more important for:
    • Users with Skystars SS24D receivers
    • Users with Emax 900Mhz transmitter modules
    • Users with Radiomaster Zorro, TX12 or TX16S handsets, with internal ELRS modules
    • Users within the EU_LBT region

Maintenance

  • Hide the 'Reset Runtime Options' button in webui if runtime options are not customized #2053
  • Tweak output power values for Emax 900Mhz targets #2126

Fixes

  • Fix Skystars SS24D target layout #2078
  • Fix "random hangs" when using the EU_LBT region, and a "channel in use" is detected #2055
  • Fix issue where some MSP commands would be mistakenly processed by the RX as RX commands #2062
  • Fix race condition in Telemetry #2103
  • Display the correct UID (the one that is currently being used) in the webui #2112
  • Fix the displayed telemetry bandwidth in LUA when using F1000 TLM 1:2 #2118
  • Fix "AST node column out of range", python 3.11 support (#2116) #2138
  • Fixed an issue that caused RF power to increase past the set limit on TX modules that use the SKY85321 #2142

Known Issues

  • Changing the packet rate via the screen + 5way while a link is active between TX and RX may sometimes result in a failure to re-link after the rate change. Reverting back to the previous packet rate will recover the link. The current workaround for this issue is to use the LUA to change packet rates, which is not affected by this problem.
Assets 3