How to add nearby crewed aircraft to a WarDragon picture, check that the decoder is feeding data, and troubleshoot missing aircraft.
Why an aircraft can appear in ATAK with the wrong icon, where the icon comes from, and what to check.
How to add a kit to WarDragon Analytics from the web interface, a configuration file, or MQTT push, and what to check if it does not appear.
What WarDragon Analytics does, why it runs on a separate server, and the two ways kits connect to it.
How to create alert zones in the WarDragon ATAK plugin, choose what triggers them, and read the threat direction indicator.
How to confirm MQTT publishing from a WarDragon kit and where to look when messages do not arrive.
A TAK Server carries detections to users who are not on the unit’s local network segment and lets many units feed one picture. Configuration is a short edit to the DragonSync config file plus the server’s certificates. Before you start Edit the configuration Open /home/dragon/DragonSync/config.ini and set these under [SETTINGS], substituting your values. Use one…
Multicast is the default output and needs no change on the unit. Detections and unit health arrive as Cursor on Target on any TAK client that shares a network segment with the unit. On the TAK device Client Setting ATAK Settings → Network Preferences → SA Multicast: set both Input and Output to 239.2.3.1:6969 iTAK…
The plugin adds unit health, enhanced tracks, and pilot locations inside ATAK. Detections continue to arrive over multicast or TAK Server whether or not the plugin is installed. Before you start Install If the plugin shows no data The plugin reads the unit’s HTTP API. Confirm the API answers from the device’s network before troubleshooting…
The Console is a local web interface for unit health, live detections, and a curated set of configuration. Not every kit ships with it installed. Check whether the Console is already installed From a browser running on the unit itself, open: If the Console loads, it is installed and you can stop here. If the…