Releases: DroneBridge/ESP32
v2.0RC4
Pre-Release RC4 for DroneBridge for ESP32 v2.0
Use this version to test the latest features.
Changelog from v2.0RC3
- DB for ESP32 v2.0RC4 by @seeul8er in #88
- Fixed MSP errors over ESP-NOW
- Improved Skybrush support by adding a configurable read/send timeout to transparent and MAVLink mode. Packets are no longer getting stuck with non-continuous streams. Packet is filled with complete MAVLink messages till max. packet size is reached or the timeout is reached.
- Changed default max. packet size to 128 bytes
- Added serial speed indication in web-interface
Changelog from v2.0RC2
- When manually adding a UDP client the user can now choose to save the added UDP client so it is there after reboot. Only one UDP client can be stored. Otherwise, the current one will be overwritten
- Added support for receiving UDP broadcast packets on port 14555 (Skybrush support)
- Cleanup of UI
- Added add & clear button for UDP targets
- Push to esp-idf 5.3
- Added ESP32-C6 support (untested)
- ESP32 now also reports noise level as part of RADIO_STATUS MavLink message
- Added per peer packet loss based on GND station observation to MAV RADIO Status
Changelog from v2.0RC1
- Fixed bugs related to startup, mavlink parsing and parameter protocol - In MAVLink mode the ESP32 will register as telemetry component to the GCS and drone.
- Removed WiFi client mode failsafe
- Fixed bugs related to client mode freeze when TCP is connected
- Boot button will reset configuration to prevent lockout: Short press (<0,8s) will reset mode to access point mode with default SSID and password. Long Press (>1,5s) will reset all settings and trigger a reboot of the device.
- Added experimental support for serial over USB (no UART connection required - serial data over USB - no debugging console via USB) Ideal for ground station esp32
- Hide settings in the web interface that are of no interest in the current mode
- Push to esp-idf v5.2.2
- Refactoring
Changelog from v1.5
- ESP-NOW LR Mode support with AES256-GCM encryption for more robust & secure long-range connections (swarm support)
- ESP32 LR (long range) support using WiFi mode (swarm support)
- Support for MAVLink semi-transparent parsing to reduce packet loss
- Injection of Radio-Status messages in MAVLink mode to pass RSSI information to GCS when in LR mode (introduction of ESP32 to ESP32 telemetry)
- Support for receiving UDP Broadcast messages
- Support for manually adding UDP targets via web interface
- Support for static IP
- Boot button to reset configuration (long press & short press)
- Documentation updates
- Fixed MSP parsing bugs
- No more need to erase the flash when updating the firmware from this version onwards
- Make the v2.0 API RESTful by @mmalecki in #76
- Add automated frontend build to v2.0dev by @mmalecki in #77
- Merge of V2.0dev to master for upcoming release v2.0 by @seeul8er in #78
Full Changelog: v2.0RC3...v2.0RC4
Full Changelog: v2.0RC2...v2.0RC3
Full Changelog: v2.0RC1...v2.0RC2
Full Changelog: v1.5...v2.0RC1
Install Instructions
When upgrading from v1.5 erase the flash first to be sure! Otherwise, it may not boot!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
For detailed instructions please visit the wiki
Known "Bugs"
- Restart of esp32 in access point mode will not de-register clients. Clients will think they are still connected but they aren't. Restart/reset of clients necessary or the access point must be taken offline for at least 3 seconds to trigger a WiFi search on the clients.
- When MAVLink parsing is activated, packet loss is ~0.5 packets/second. This may be due to unanswered messages from the GCS to the ESP32. General performance is not affected.
Contributors
Assets 3
v2.0RC3
Pre-Release RC3 for DroneBridge for ESP32 v2.0
Use this version to test the latest features.
Changelog from v2.0RC2
- When manually adding UDP client the user can now choose to save the added UDP client so it is there after reboot. Only one UDP client can be stored. Otherwise the current one will be overwritten
- Added support for receiving UDP broadcast packets on port 14555 (Skybrush support)
- Cleanup of UI
- Added add & clear button for UDP targets
- Push to esp-idf 5.3
- Added ESP32-C6 support (untested)
- ESP32 now also reports noise level as part of RADIO_STATUS MavLink message
- Added per peer packet loss based on GND station observation to MAV RADIO Status
Changelog from v2.0RC1
- Fixed bugs related to startup, mavlink parsing and parameter protocol - In MAVLink mode the ESP32 will register as telemetry component to the GCS and drone.
- Removed WiFi client mode failsafe
- Fixed bugs related to client mode freeze when TCP is connected
- Boot button will reset configuration to prevent lockout: Short press (<0,8s) will reset mode to access point mode with default SSID and password. Long Press (>1,5s) will reset all settings and trigger a reboot of the device.
- Added experimental support for serial over USB (no UART connection required - serial data over USB - no debugging console via USB) Ideal for ground station esp32
- Hide settings in the web interface that are of no interest in the current mode
- Push to esp-idf v5.2.2
- Refactoring
Changelog from v1.5
- ESP-NOW LR Mode support with AES256-GCM encryption for more robust & secure long-range connections (swarm support)
- ESP32 LR (long range) support using WiFi mode (swarm support)
- Support for MAVLink semi-transparent parsing to reduce packet loss
- Injection of Radio-Status messages in MAVLink mode to pass RSSI information to GCS when in LR mode (introduction of ESP32 to ESP32 telemetry)
- Support for receiving UDP Broadcast messages
- Support for manually adding UDP targets via web interface
- Support for static IP
- Boot button to reset configuration (long press & short press)
- Documentation updates
- Fixed MSP parsing bugs
- No more need to erase the flash when updating the firmware from this version onwards
- Make the v2.0 API RESTful by @mmalecki in #76
- Add automated frontend build to v2.0dev by @mmalecki in #77
- Merge of V2.0dev to master for upcoming release v2.0 by @seeul8er in #78
Full Changelog: v2.0RC2...v2.0RC3
Full Changelog: v2.0RC1...v2.0RC2
Full Changelog: v1.5...v2.0RC1
Install Instructions
When upgrading from v1.5 erase the flash first to be sure! Otherwise, it may not boot!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
For detailed instructions please visit the wiki
Known Bugs
- Restart of esp32 in access point mode will not de-register clients. Clients will think they are still connected but they aren't. Restart/reset of clients necessary or the access point must be taken offline for at least 3 seconds to trigger a WiFi search on the clients.
- When MAVLink parsing is activated there is a packet loss ~0.5 packets/second. This may be due to unanswered messages from the GCS to the ESP32. General performance is not affected.
Contributors
Assets 3
v2.0RC2
Pre-Release RC2 for DroneBridge for ESP32 v2.0
Use this version to test the latest features.
Changelog from v2.0RC1
- Fixed bugs related to startup, mavlink parsing and parameter protocol - In MAVLink mode the ESP32 will register as telemetry component to the GCS and drone.
- Removed WiFi client mode failsafe
- Fixed bugs related to client mode freeze when TCP is connected
- Boot button will reset configuration to prevent lockout: Short press (<0,8s) will reset mode to access point mode with default SSID and password. Long Press (>1,5s) will reset all settings and trigger a reboot of the device.
- Added experimental support for serial over USB (no UART connection required - serial data over USB - no debugging console via USB) Ideal for ground station esp32
- Hide settings in the web interface that are of no interest in the current mode
- Push to esp-idf v5.2.2
- Refactoring
Changelog from v1.5
- ESP-NOW LR Mode support with AES256-GCM encryption for more robust & secure long-range connections (swarm support)
- ESP32 LR (long range) support using WiFi mode (swarm support)
- Support for MAVLink semi-transparent parsing to reduce packet loss
- Injection of Radio-Status messages in MAVLink mode to pass RSSI information to GCS when in LR mode (introduction of ESP32 to ESP32 telemetry)
- Support for receiving UDP Broadcast messages
- Support for manually adding UDP targets via web interface
- Support for static IP
- Boot button to reset configuration (long press & short press)
- Documentation updates
- Fixed MSP parsing bugs
- No more need to erase the flash when updating the firmware from this version onwards
- Make the v2.0 API RESTful by @mmalecki in #76
- Add automated frontend build to v2.0dev by @mmalecki in #77
- Merge of V2.0dev to master for upcoming release v2.0 by @seeul8er in #78
Full Changelog: v2.0RC1...v2.0RC2
Full Changelog: v1.5...v2.0RC1
Install Instructions
When upgrading from v1.5 erase the flash first to be sure! Otherwise, it may not boot!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
For detailed instructions please visit the wiki
New Contributors
Known Bugs
- Restart of esp32 in access point mode will not de-register clients. Clients will think they are still connected but they aren't. Restart/reset of clients necessary or access point must be taken offline for at least 3 seconds to trigger a WiFi search on the clients.
- When MAVLink parsing is activated there is a packet loss ~0.5 packets/second. This may be due to unanswered messages from the GCS to the ESP32. General performance is not affected.
Contributors
Assets 3
v2.0 RC1
Pre-Release RC1 for DroneBridge for ESP32 v2.0
Use this version to test the latest features.
Changelog
- ESP-NOW LR Mode support with AES256-GCM encryption for more robust & secure long-range connections (swarm support)
- ESP32 LR (long range) support using WiFi mode (swarm support)
- Support for MAVLink semi-transparent parsing to reduce packet loss
- Injection of Radio-Status messages in MAVLink mode to pass RSSI information to GCS when in LR mode (introduction of ESP32 to ESP32 telemetry)
- Support for receiving UDP Broadcast messages
- Support for manually adding UDP targets via web interface
- Support for static IP
- Boot button to reset configuration (long press & short press)
- Documentation updates
- Fixed MSP parsing bugs
- No more need to erase the flash when updating the firmware from this version onwards
- Make the v2.0 API RESTful by @mmalecki in #76
- Add automated frontend build to v2.0dev by @mmalecki in #77
- Merge of V2.0dev to master for upcoming release v2.0 by @seeul8er in #78
Full Changelog: v1.5...v2.0RC1
Install Instructions
You want to erase the flash of the ESP32 first! Otherwise, it will not boot!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
For detailed instructions please visit the wiki
New Contributors
Contributors
Assets 3
v1.5
Changelog:
- Fixed crashes of the esp32c3
- Fixed MSP/LTM parsing bug
- Improved throughput performance
- Added support for UART flow control
- RSSI is reported when in client mode via the web interface
Full Changelog: v1.4...v1.5
You want to erase the flash of the ESP32 first! Otherwise, it will not boot!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
For detailed instructions please visit the wiki
Release v1.4
Changelog:
- Added compiled binaries for esp32, esp32c3, esp32s2 & esp32s3
- Fixed UDP broadcast bug, when multiple clients are connected to the esp32 access point
- ESP32 in client mode can now connect to WEP enabled WiFi networks
- Fixed packet loss bug when two esp32s were talking to each other (one in client mode, the other one in ap mode)
Full Changelog: v1.3...v1.4
You might want to erase the flash of the ESP32 first!
To flash/install see the included flashing_instructions.txt.
The attached zip file includes all pre-compiled binaries that are ready to flash.
Release v1.3
Changelog:
- Pushed to esp-idf v5.1.2
- Added support for ESP32C3
- Fixed bug with number only SSID or Wifi password
- Fixed load times and failed loads of the website by minifying and including the CSS and JS code
- No pre-defined pins for the UART. If both pins are set to the same number (like initially) then the UART will not be opened. User has to define the TX & RX pins initially. That way there is only one image for all boards necessary.
Known Issues:
- Load errors may occur on the ESP32C3 when in AP-Mode and accessed via PC/Desktop browser. Android mobile browsers performed well.
Erase the flash of the ESP32 first!
To flash see the Github Readme or run:
esptool.py -p (PORT) -b 460800 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_size detect --flash_freq 40m 0x1000 bootloader.bin 0x8000 partition-table.bin 0x10000 db_esp32.bin 0x110000 www.binRelease v1.2
If the DroneBridgeESP32_v1_2 build does not work (no startup etc.) please choose the DroneBridgeESP32_v1_2_alt_UART_conf. Some boards have the flash chip connected to pins 16/17. In that case the alt. UART conf. version has pins 32/33 configured.
If you are using a Pico board, like the TinyPico or M5Stack Atom Lite please use the alternative build. The other one will not work.
Changelog:
- Added WiFi client mode support - ESP32 can now connect to existing WiFi instead of creating an access point on its own
- Enhancements for the web interface: Support for new modes, hide unnecessary config options depending on the current config
- re-base onto esp-idf 4.4.6
- Fixed bugs related to country code settings
Erase the flash of the ESP32 first!
To flash see the Github Readme or run:
esptool.py -p (PORT) -b 460800 --before default_reset --after hard_reset --chip esp32 write_flash --flash_mode dio --flash_size detect --flash_freq 40m 0x1000 bootloader.bin 0x8000 partition-table.bin 0x10000 db_esp32.bin 0x110000 www.binRelease v1.0
If the DroneBridgeESP32_v1_1 build does not work (no startup etc.) please choose the DroneBridgeESP32_v1_1_alt_UART_conf. Some boards have the flash chip connected to pins 16/17. In that case the alt. UART conf. version has pins 32/33 configured.
If you are using a Pico board, like the TinyPico or M5Stack Atom Lite please use the alternative build. The other one will not work.
Changelog:
- re-write of the web interface
- re-base onto esp-idf 4.3
- fixed UDP bugs
- added REST:API for settings and status updates
Erase the flash of the ESP32 first!
To flash see the Github Readme or run:
esptool.py -p (PORT) -b 460800 --before default_reset --after hard_reset --chip esp32 write_flash --flash_mode dio --flash_size detect --flash_freq 40m 0x1000 bootloader.bin 0x8000 partition-table.bin 0x10000 db_esp32.bin 0x110000 www.binMore config options
- Configure SSID
- Configure WiFi channel