Drone ↔ drone
Exchange status and mission messages across the intended mesh.
COMMUNICATIONS / PURPOSEFUL CONNECTIONS
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 integrationExchange status and mission messages across the intended mesh.
Direct ground links, with peer relay proposed where configured.
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
Each aircraft carries its own communication module and stick antennas. The intended network supports peer messages and a ground-control link.
Peer-to-peer mesh links
Ground controlDirect or via a configured peer relay
Exchange aircraft status and mission messages. Mesh routing would select a peer path when direct communication is unavailable.
Use a direct link when available, with a configured drone relay as a proposed alternative. Ground command authority remains explicit.
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
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
Proposed for compact status, telemetry, and bounded command traffic. Messages need priorities, freshness limits, and an explicit response to link loss.
02 / WI-FI HALOW
Proposed for larger data transfers. Actual throughput depends on the radio, host interface, drivers, RF conditions, and the selected operating profile.
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
Placement, power, data, and radio coexistence are one system-level problem.
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.
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.
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.
LoRa and HaLow can operate in overlapping bands. Measure simultaneous transmission, receiver desensitisation, and GNSS behaviour with propulsion electronics running.
SEPARATE POSITIONING / GNSS
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.
The carrier reference uses UART navigation data, with optional timing and compass connections.
Preserve sky visibility and review nearby carbon structures, current-carrying wiring, and radio emissions.
Test positioning and timing while both radios transmit and the aircraft power system is active.
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
Tell us about the data, operating region, ground station, and aircraft constraints.