Release 22.09

This release include major protocol changes and incompatible with previous releases.

Changes:

1. Added WFB-ng standard draft. We announce standard draft for long-range data transmission via raw wifi radio.
2. WFB-ng now supports multiple links out of box. You can use one GS for multiple drones control (channel bandwidth will be shared between all of them)
3. Added missing libsodium init. You will be warned if not enough entropy is available.
4. WFB-ng wifi cards now will be automatically set to unmanaged state in NetworkManager during service startup. No need to add them manually to NetworkManager.conf anymore.
5. LDPC now enabled by default due to most of the setups use rtl8812au cards. If you use Ralink or Atheros cards you need to disable it in config file.
6. Added project logo.

Raspberry PI 3B ready to use image:

• This image was tested on RPI3b + Alfa AWUS036ACH + PI Camera. Use native ("thick") USB3 cable from this card. If you have issues with different HW setup then try to test this setup first before issuing bugreport.
• OSD will not work on RPI4 due to dropped OpenVG support.
• If you use high-power cards like "taobao card" then you must use external high-current power supply and low-esr capacitor on the card. Don't power them from USB!

Release 22.05

Changes:

1. Fixed bug with mavlink rx error report
2. CLI refactoring - now works even for very small terminal sizes
3. Removed python2 support - minimal python version now is 3.6
4. Log messages for lost packets now aggregated - no more log flooding.
5. Location of /etc/wifibroadcast.cfg can be customized via WIFIBROADCAST_CFG environment variable
6. mavlink_sys_id/comp_id for injected RADIO_STATUS packets can be customized via config file.

Due to (6) you need to use osd >= 22.05

If you have Raspberry PI 3/3B/3B+ then you can try to use preconfigured image.

Just flash it into the SD-card (8Gb or larger), ssh to the board and follow instructions on the screen.

Release 21.08

This release is NOT compatible with previous releases due to packet header change. You need to upgrade both drone and GS sides.

Changes:

1. Fix bug with FEC if first packet of block was not lost
2. Add TX FEC timeout option: emit empty packets if block is open but no input.
   This can reduce video latency and allow to use K/N FEC for telemetry where K > 1
   This option is disabled by default, use it on your own risk.
3. Add serial endpoint support. You can use peer = 'serial:ttyX:1500000 to connect directly to autopilot without mavlink-router
4. Add ARM/DISARM handler. You can use call_on_arm = '/some/binary' and/or call_on_disarm = '/other/binary' in telemetry sections of drone and GS. For example this can be used for trigger video recording.
5. Add telemetry mirroring on GS. You can use it to mirror all incoming mavlink traffic to some UDP port (for example to OSD app) without mavlink-router
6. Python3 is now default. Python2 support will be dropped in the next release

Release 21.03.2

This is a bugfix release:

• Fixed bug with broken FEC introduced in 20.12

Release 21.03.1

This is a bugfix release:

• Fixed memory leak in FEC code
• Fixed python3 compatibility

Binary builds are for Ubuntu 18.04 (amd64) and Raspbian (armhf)

Release 21.02

Changes:

• Fixed long living bug with settings sync freeze in QGroundControl
• Fixed radiotap parsing on high-endian machines (some OpenWRT routers)

Supported platforms: Linux kernels 4.x and 5.x
Supported hardware: rtl8812au, rt28xx
Prebuild packages: Ubuntu-18.04 (amd64), Raspbian (arm32)

Release 20.12

• Decrease latency in pcap
• Improve FEC behavior: don't discard packets from incomplete blocks

Release 20.08

• Allow to disable MAVLink aggregation by setting agg_timeout=None or agg_size=None
• Fix compilation with GCC 10
• Added Raspberry Pi deb package

Release 19.06

• Add support for python 3.x
• Add FEC params to config file
• Add controller for Storm32 gimbals
• Fix TX antenna selection
• Add txpower settings (disabled by default due to incompatibility with Atheros chipsets)

Release 19.03.1

Fix non-ascii symbol in master config file (triggers error on some systems)