DragonSync can add nearby crewed aircraft to the same picture as your drone detections. This article covers how to turn it on, how to check that the data is flowing, and what to look at when it is not.
What it does
ADS-B and 978 MHz aircraft reports are optional and off by default. When enabled, DragonSync reads aircraft from a local ADS-B decoder over HTTP and sends them to TAK as CoT, alongside your drone tracks. The records carry position accuracy, squawk code, and aircraft category where the aircraft provides them. When the read-only API is enabled, aircraft also appear in its track list.
This depends on an ADS-B decoder running on the kit and listening at the address you give it. If your kit image does not include one, aircraft reports stay off until one is installed.
Turning it on
Edit /home/dragon/DragonSync/config.ini under [SETTINGS]:
adsb_enabled = true
adsb_json_url = http://127.0.0.1:8080/?all_with_posThen restart the output service:
sudo systemctl restart dragonsyncCheck the decoder first
Before looking at DragonSync, confirm the decoder is returning aircraft:
curl "http://127.0.0.1:8080/?all_with_pos"The response should be JSON containing an aircraft list. If it is empty or the request fails, the decoder is not running or has no aircraft in range, and DragonSync has nothing to forward.
If aircraft do not appear in TAK
- Confirm
adsb_enabledis true and the URL matches the decoder’s address and port. - Check the track list on the API:
curl http://localhost:8088/drones - Check the unit’s log:
journalctl -u dragonsync -f
Related
- WarDragon User Guide, Section 8 — integration with your operational picture
- WarDragon User Guide, Appendix A.2 — file locations
- Reading a detection: tracks, signal alerts, and the API