This post summarizes a build demonstrated by Data Slayer: a low-cost reconnaissance drone that streams live video over a decentralized network stack, without vendor lock-in or cloud dependency. The focus is on the protocol stack, hardware parts, and system behavior.
System Objective
Build an airborne sensor node that streams live video to ATAK (Android TAK protocol), optionally uplinked to the public internet, using commodity parts and open protocols. Total payload cost is approximately $120.
Network Architecture
The system is deliberately mesh-first.
At the ground layer, a mobile ad hoc network is formed using Wi-Fi HaLow and LoRa-based nodes. The core node, previously named “Haven,” acts as the local mainnet. It bridges two domains: long-range low-power links for field nodes and conventional Wi-Fi for operator devices.
An optional backhaul via Starlink is available. When present, it exposes the mesh to the wider internet. When absent, the system continues to operate locally.
This inversion is intentional. Unlike cloud-first drone systems, video flows into the mesh first and only uplinks if a backhaul exists.
Airborne Node (“Scout”)
Scout is a minimal airborne IP camera.
The compute element is a Seeed Studio XIAO board, an ESP32-class microcontroller. It runs custom firmware that hosts a lightweight HTTP server and streams MJPEG video at approximately 2 FPS, tuned for ATAK ingestion.
Video is provided by a bare FPV camera module. There is no onboard encoding beyond what is required to packetize frames.
The radio link is Wi-Fi HaLow (IEEE 802.11ah). HaLow operates in sub-GHz spectrum, trading bandwidth for range and penetration. It transports standard IP packets, which simplifies integration with existing software stacks.
Power is supplied by a single 18650 lithium-ion cell. The payload is electrically independent from the drone.
Drone Platform and Compliance
The carrier platform is a DJI Mini SE. Stock, it sits under the 250 g FAA threshold. With Scout attached, it exceeds that limit.
This triggers U.S. FAA Remote ID requirements. Compliance is achieved using an external broadcast module (Ruko R111S). Remote ID functions as a short-range digital license plate. It is distinct from ADS-B, which is mandatory for manned aircraft and globally receivable.
The build stays within line-of-sight, altitude, and identification rules. Legality is treated as a system constraint, not an afterthought.
Protocol Stack Summary
Video transport: HTTP over IP
Local networking: Wi-Fi HaLow (802.11ah)
Optional messaging/positioning: Meshtastic (tested separately)
Backhaul: Starlink satellite IP
Client software: ATAK on Android
No proprietary SDKs or vendor cloud APIs are required.
Operational Results
The HaLow link remained stable at approximately 60 feet AGL. Live video streamed directly into ATAK. Interference artifacts were observed due to multiple radios in close proximity, and a prop strike damaged an SMA connector mid-flight. The link continued to function.
The key result is architectural, not cosmetic. An airborne node acts as a temporary elevated relay, restoring line-of-sight and stitching ground meshes together. In effect, the drone becomes an ephemeral cell tower.
Cost and Capability
The demonstrated capability—airborne ISR video injected into tactical mapping software—overlaps with systems typically priced around $40,000. The demonstrated payload cost is roughly $120.
The difference is not in the efficiency of the components. It is ownership of the stack. When the radios speak IP, the camera speaks HTTP, and the network is under operator control, integration becomes trivial, and modification becomes routine.
This is not a finished product. It is a proof of control.
No comments:
Post a Comment