High-level idea: use COTS Meshtastic LoRa radios as a long-range pipe, then get position / text into ATAK via a local TAK server or a data-package style import. This is an architecture outline — not a full plugin build guide.
Materials
2+ Meshtastic-capable LoRa boards (COTS) with antennas and charged batteries
Phone/tablet with Meshtastic app + ATAK-CIV installed
Optional: small Linux box or phone hotspot host for a local TAK server / bridge process
USB-C cable / Bluetooth for radio pairing
Steps (outline)
Flash & pair Meshtastic. Flash current Meshtastic firmware to each board. Pair one radio to the Meshtastic app over BLE/USB. Set region/frequency legally for your country.
Mesh sanity check. With two nodes in range, confirm position and text hop across the mesh in the Meshtastic app alone — before involving ATAK.
Decide the bridge pattern. Common high-level patterns:
Local TAK server: a small process on a laptop/Pi listens to Meshtastic (serial/BLE/MQTT) and emits CoT events to a local TAK server that ATAK joins on Wi‑Fi/USB tether.
Data package idea: periodically export mesh positions into an ATAK-friendly package / marker set and import on the device (batch, not live).
Stand up a local pipe (concept). On the bridge host: read mesh position packets → map node IDs to callsigns → format as CoT (see the CoT heartbeat instructable) → send to localhost TAK / multicast as your environment supports.
Point ATAK at the local server. In ATAK network settings, add the local TAK server (or use whatever discovery your stack provides). Confirm self + bridged nodes appear as markers.
Range test. Walk one radio out of Wi‑Fi range but still on LoRa. Confirm updates still refresh in ATAK via the bridge host — that is the point of the pipe.
Document callsign map. Keep a simple table: Meshtastic node ID ↔ ATAK callsign. Ambiguous names cause blue-on-blue confusion in exercises.
Notes / gotchas
LoRa is not magic: antennas, height, and legal power matter more than fancy software.
Do not bridge into production or untrusted TAK networks without a clear security review.
Battery: mesh radios + phone GPS + ATAK = three drain sources. Plan power.
This outline intentionally skips plugin APK names and unofficial forks — prefer maintained open projects and official ATAK network docs.
Video tips
Related watch — Marshall Pix4D/DTED2, TAK Syndicate, Meshtastic. Spelling lock: ATAK.