DragonScope decodes encrypted DJI OcuSync 4 identification. It is the one WarDragon capability that needs an internet connection, and this article explains what that means in practice.
What needs a connection and what does not
| Capability | Internet required |
|---|---|
| Remote ID detection, Wi-Fi and Bluetooth | No |
| DJI OcuSync 2 and 3 detection with telemetry | No |
| DJI OcuSync 4 detection — per-flight identifier and distance estimate | No |
| FPV video and 900 MHz link awareness (Elite) | No |
| Output to ATAK, TAK Server, and other endpoints | No — only your network path to them |
| DragonScope — OcuSync 4 decoding with full telemetry and serial number | Yes, active connection while decoding |
How it works
Decoding OcuSync 4 is not done on the unit. When DragonScope is active and an OcuSync 4 aircraft is detected, the unit sends the information needed for decoding to the DragonScope service, and the decoded result — aircraft position, velocity, pilot position, home point, serial number, and signal data — comes back to the unit and is published like any other detection. The exchange runs while the aircraft is in range; it is not a batch process.
Because of that, DragonScope needs a working outbound internet connection from the unit at the time of detection. Ethernet, Wi-Fi client mode, or a cellular connection all work; the unit’s own hotspot does not provide internet unless the unit also has an upstream path.
What happens without a connection
Nothing else changes. Every capability in the table above marked No continues exactly as before. An OcuSync 4 aircraft is still detected and still produces a per-flight identifier and a distance estimate; what it does not produce is decoded telemetry or a serial number until connectivity returns. There is no offline decoding and no stored backlog that decodes later.
Note A unit with DragonScope active and no internet connection behaves the same as a unit without DragonScope. That is the expected behavior, not a fault.
Checking the connection from the unit
nmcli device status
ping -c 3 1.1.1.1If the external interface shows connected but the ping fails, the problem is usually upstream — a firewall or a captive portal on the site network. If your network restricts outbound traffic, open a support request and ask which destinations the unit needs to reach.
Data handling
The terms that govern the service, including how data sent for decoding is handled, are in the DragonScope Service Agreement and the privacy policy on the legal page. Where this article and those documents differ, the documents govern.
Getting DragonScope
DragonScope is an annual per-sensor service available on every kit. Availability and pricing are through the contact form. Support for active subscriptions is through the support page.
Related
- WarDragon User Guide, Section 1.5 — DragonScope
- WarDragon User Guide, Section 5 — network configuration