Sending detections to other systems
WarDragon is not tied to any one command-and-control platform. Detections leave the unit in open, documented formats, and several outputs can run at the same time. If a destination fails or goes offline, the other outputs carry on.
Outputs available on every kit
| Output | Suits | Setup |
|---|---|---|
| Cursor on Target by multicast | ATAK, iTAK, WinTAK, and any CoT consumer on the local network. On by default. | Sending detections by multicast |
| Cursor on Target to a TAK Server | Distributed teams and many units feeding one picture | Connecting to a TAK Server |
| MQTT | Dashboards, home-built tools, and message-based middleware | Checking that detections are reaching your MQTT broker |
| Read-only HTTP API on port 8088 | Systems that poll for current status, tracks, and signal alerts | Reading a detection: tracks, signal alerts, and the API |
| WarDragon Analytics | A combined map, history, and dashboards across kits | WarDragon Analytics |
| Lattice | Organizations already running a Lattice environment | Below |
Every detection carries the time the kit processed it, the aircraft’s own timestamp where the broadcast includes one, and an identifier for the kit that saw it, so a downstream system can merge feeds from several units.
For a destination not listed here, ingestion into your own middleware or dashboard is arranged through the contact form.
Lattice
DragonSync includes an output for Anduril Lattice. It is off by default. You need a Lattice environment, an API token for it, and network access from the unit to its endpoint. Edit /home/dragon/DragonSync/config.ini under [SETTINGS]:
lattice_enabled = true
lattice_token = <your-api-token>
lattice_base_url = https://<your-environment>
lattice_source_name = <a-unique-name-for-this-unit>Give each unit its own lattice_source_name when several report to the same environment. Instead of lattice_base_url you can set lattice_endpoint to the host alone. Restart DragonSync after the change:
sudo systemctl restart dragonsyncIf nothing arrives, confirm lattice_enabled is true, that the token and one of the two address settings are filled in, and that the unit can reach the endpoint. Then check the log:
journalctl -u dragonsync | grep -i latticeRelated
- WarDragon User Guide, Section 8 — integration with your operational picture
- WarDragon after purchase: frequently asked questions
WarDragon is manufactured by Millenium Products Inc. Technical support for purchased kits is requested through the support page. Purchasing and quote requests go through the contact form.