# DoodleLabs

{% columns %}
{% column valign="middle" %}

<figure><img src="/files/No0pHPOh2MVcsUpjbear" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Ht94PMvT8hQLX8ImwnL0" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column valign="middle" %}

### 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.
{% endcolumn %}
{% endcolumns %}

### 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

***

### 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.

<table data-full-width="false"><thead><tr><th width="169.8575439453125">DroneCore version</th><th width="154.857177734375">Radio connector</th><th width="189.7144775390625">DroneCore connector</th><th width="186.4281005859375">Cable</th></tr></thead><tbody><tr><td>DCS1</td><td>ETH (RJ45 or JST on radio)</td><td><a href="https://docs.airvolute.com/autopilots/dronecore-2/boards/expansion-boards/dcs2.adapter-default#eth1-eth2">ETH1, ETH2</a> on Jetson carrier</td><td>Ethernet patch or JST-to-RJ45 adapter</td></tr><tr><td>DCS2</td><td>ETH (RJ45 or JST on radio)</td><td><a href="https://docs.airvolute.com/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.2/dronecore.pilot-connector-description-and-pins-assignment-1#ethernet">ETHERNET</a> on adapter board</td><td>Ethernet patch or JST-to-RJ45 adapter</td></tr></tbody></table>

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](https://github.com/airvolute/airvolute-doodle-setup) repository on GitHub contains ready-made configuration scripts for bridging MAVLink over the Mesh Rider network on DCS1.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.airvolute.com/hidden-wip/radios/doodlelabs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.