Release 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.bin

More config options

• Configure SSID
• Configure WiFi channel

UDP broadcast to all connected stations

• MSP & LTM UDP forwarding fix
• Auto broadcasting of messages to UDP:14550 to all connected stations. No config required for QGroundControl

UDP support. Performance improvements

• Fixed performance issues
• Added support for up to 5 UDP client connections. Clients must register to ESP by sending a packet to UDP port 14550

Use TCP connections. In sync with DroneBridge v0.6 Beta release

• Based on latest ESP-IDF
• Uses TCP instead of UDP (multiple simultaneous connections)
• Improved communication module
• Tested with MAVLink, DroneBridge for android v1.3 & QGroundControl
• Removed unnecessary settings
• Needs testing with LTM/MSP
• Synced to DB v0.6 Beta release
• Improved & tested installation guide

DroneBridge for ESP32

Support for MAVLink, MSP or LTM via a single serial port