DroneBridge Docs
Search…
Introduction
Comparison
DroneBridge for Raspberry Pi
Release Notes
Getting started
Supported hardware
Standard Modules
Milestones
mwptools
Adjusting TX Power & EIRP
DroneBridge for Android
DroneBridge for Android
DroneBridge for ESP32
Overview & Installation Guide
DroneBridge Desktop
Enabling monitor mode
Video stream playback
Developer Guide
Downloading & Compiling
System Architecture
Startup & Logs
Raw protocol
Communication protocol
Status messages
RC message/packet
USB message
Plugins
Image Build
System Integration Test Specification
DroneBridge lib example usage
Notes About Injection
Powered By GitBook
USB message
The protocol & messages used by DroneBridge USBBridge module to communicate with an android device connected via USB to the ground station.

Introduction

The USBBridge module with the USB protocol allows for an alternative to WiFi based connections between the ground station and the DroneBridge for android app. Compared to USB tethering, the USB protocol allows for a more direct control of the data streams. It is fast & reliable. The user experience is flawless since the app automatically starts up when the phone is connected to the ground station. Most importantly the connection does not require the phone/tablet to have a SIM card. The SIM card is a requirement for android to support USB tethering. In past releases cable based connections were only possible with devices carrying a SIM card. The DroneBridge USB protocol helps to overcome that issue. With it all android based devices can communicate via a wired connection with the ground station.
The DroneBridge USB protocol is used to transfer data between an android device and the ground station. Both devices must be connected via USB. The android open accessory (AOA) protocol is used to establish a connection between the phone and the ground station (USBBridge). On top of the AOA protocol sits the DroneBridge USB protocol. It manages multiple IP streams over a single USB connection.

Message format

Identifier
Port
Payload length
Payload
Sequence of bytes to identify the start of a new message and its protocol version.
Virtual destination port of the data. Same values as for DroneBridge raw protocol
Length of the payload
Payload/User data
0x44, 0x42, 0x01 (DB1)
0x01, 0x02, 0x03, 0x04...
unsigned 16bit little endian
sequence of bytes
3 bytes
1 byte
2 bytes
<=1530 length for DB applications
bit 0-23
bit 24-31
bit 32-47
bit 48+
For payloads bigger than the max size allowed by the USB controller the payload can be split into multiple transmissions. In this case the header is only written once in the first transmission. The following transmissions for the payload must not have a DB-USB-MSG header.
Multiple payloads/headers per USB transmission are not allowed!
Developer Guide - Previous
RC message/packet
Next - Developer Guide
Plugins
Last modified 2yr ago
Copy link
On this page
Introduction
Message format