COMMUNICATIONS / PURPOSEFUL CONNECTIONS

Connect the fleet.
Stay in touch
with the ground.

A proposed communication module with external stick antennas connects aircraft to nearby drones and ground control. Peer routing and ground access are designed together; flight stabilisation stays onboard.

Explore the integration
PROPOSED NETWORK ROLESX8
PEERS

Drone ↔ drone

Exchange status and mission messages across the intended mesh.

GROUND

Drone ↔ control

Direct ground links, with peer relay proposed where configured.

GNSS

Position & timing

A separate receiver pod with a sky-facing antenna.

Mesh routing, relay performance, range, and throughput remain to be implemented and qualified.

COMMUNICATION MESH / PROPOSED

Between aircraft.
Connected to the ground.

Each aircraft carries its own communication module and stick antennas. The intended network supports peer messages and a ground-control link.

Proposed drone mesh and ground-control networkDrone A, B, and C are connected by bidirectional peer links. Drone B connects to ground control. Other aircraft may reach ground control directly or through a configured peer relay. Links show design intent, not a live network.DRONE ARadio + stick antennasDRONE CRadio + stick antennasDRONE BRadio + stick antennasPEER ↔ PEERGROUND ↔ AIRGROUND CONTROLMission oversight & telemetry
Illustrative topology. Lines represent intended two-way links. Direct ground access and peer relaying depend on coverage, configuration, and the selected network implementation.

Share with nearby drones

Exchange aircraft status and mission messages. Mesh routing would select a peer path when direct communication is unavailable.

Reach ground control

Use a direct link when available, with a configured drone relay as a proposed alternative. Ground command authority remains explicit.

Keep control onboard

Attitude control stays local. Loss of peers or ground connectivity must invoke defined onboard behaviour.

Network concept only. Radio selection, routing, security, latency, and moving-aircraft tests are pending; no range or self-healing performance is claimed.

RADIO OPTIONS / NETWORK DESIGN

Two radios.
Two distinct jobs.

LoRa and Wi-Fi HaLow are development radio references. Neither is presented here as a working mesh implementation; routing software, host support, and the final radio choice remain to be established.

01 / LORA

Small messages.
Useful awareness.

Proposed for compact status, telemetry, and bounded command traffic. Messages need priorities, freshness limits, and an explicit response to link loss.

Hardware reference
Core2021-HF / LR2021
Host connection
SPI + control signals
Integration
Dedicated RF path & regulation

02 / WI-FI HALOW

A path for
richer mission data.

Proposed for larger data transfers. Actual throughput depends on the radio, host interface, drivers, RF conditions, and the selected operating profile.

Hardware reference
FGH100M-H
Host connection
SPI + host driver
Integration
Dedicated RF path & regulation

Development references, not a final regional product configuration. Current pod references target 902–928 MHz; suitability for another region must be established separately.

COMMUNICATIONS ON THE X8

Good links start
with good integration.

Placement, power, data, and radio coexistence are one system-level problem.

01 / ANTENNAS

Give each radio its own space.

The revised concept uses a lower radio enclosure and two external stick antennas. Keep them clear of propellers, landing gear, and sensor views. Antenna count, frequency, spacing, and orientation follow the selected radio architecture and measured coverage.

02 / POWER

Protect each branch.

The carrier proposes switched, protected 5 V branches and local pod regulation. Harness drop, startup current, and transmit bursts must be measured with the assembled aircraft.

03 / HOST INTERFACE

Keep data traffic predictable.

The reference pods use SPI/control wiring with 3.3 V logic. Driver integration and bus scheduling must protect IMU sampling and the flight-control timing budget.

04 / COEXISTENCE

Test the radios together.

LoRa and HaLow can operate in overlapping bands. Measure simultaneous transmission, receiver desensitisation, and GNSS behaviour with propulsion electronics running.

View the aircraft placement guide

SEPARATE POSITIONING / GNSS

A clear view
of the sky.

GNSS supplies position and timing through its own receiver path. The top-mounted receiver stays separate from the transmitting communication module and its mesh links.

01

Separate signal path

The carrier reference uses UART navigation data, with optional timing and compass connections.

02

Deliberate placement

Preserve sky visibility and review nearby carbon structures, current-carrying wiring, and radio emissions.

03

System-level verification

Test positioning and timing while both radios transmit and the aircraft power system is active.

Connectivity supports the mission. It must not become a dependency of attitude stabilisation.

Mesh membership, authenticated commands, routing, stale-message handling, and ground-link loss require explicit design and validation. Peer relaying and automatic path recovery are intended behaviours, not demonstrated capabilities.

WHAT COMES NEXT

Define the connection your mission needs.

Tell us about the data, operating region, ground station, and aircraft constraints.

Prepare a communications brief