search
Ctrlk

hashtag
Mesh Rider

DoodleLabs develops the Mesh Rider family of radios - compact, low-SWaP MANET (Mobile Ad-Hoc Network) modules optimised for aerial and robotic platforms. Mesh Rider radios form self-healing, self-forming mesh networks that maintain connectivity even when individual nodes move or drop out, making them ideal for multi-vehicle swarm operations, BVLOS missions, and relay-based range extension.

hashtag
Key capabilities

  • Long-range, high-bandwidth mesh networking across 900 MHz, 2.4 GHz, and 5 GHz bands

  • Ultra-low latency with automatic band and channel switching (Sense interference avoidance)

  • AES-256 encryption and LPI/LPD waveform options for contested environments

  • Multi-hop relay - extend range by chaining UAVs as network nodes

  • Blue UAS Framework certified (Helix variants) for DoD-compliant programs

  • Available in Mini OEM and Nano OEM form factors for tight airframe integrations

hashtag
Connecting to DroneCore

Mesh Rider radios connect via Ethernet. The radio presents itself as a standard network node, so MAVLink telemetry, video, and SSH all route over the same cable.

DroneCore version
Radio connector
DroneCore connector
Cable

DCS1

ETH (RJ45 or JST on radio)

<ETH_PORT_LABEL> on Jetson carrier

Ethernet patch or JST-to-RJ45 adapter

DCS2

ETH (RJ45 or JST on radio)

<ETH_PORT_LABEL> on adapter board

Ethernet patch or JST-to-RJ45 adapter

Power the radio from the <5V_AUX_LABEL> supply rail.

Confirm the radio variant's input voltage - Mini OEM takes 3.3–5 V, Helix OEM takes 3.3–5 V as well

Once connected, the Mesh Rider management UI is reachable in a browser at its default IP.

MAVLink traffic from the Cube flows via the Jetson (/dev/ttyTHS* → MAVProxy or ArduPilot's SERIAL parameter) and is forwarded over UDP through the mesh to the GCS.

The Airvolute airvolute-doodle-setup repository on GitHub contains ready-made configuration scripts for bridging MAVLink over the Mesh Rider network on DCS1.

Last updated