Meshtastic
+ ATAK

Why Meshtastic
+ ATAK

You already know what Meshtastic can do. You've seen the packets hop across a city, watched nodes appear on the map, sent a message to someone a mile away through two relay nodes on a thirty-dollar radio. It works. It's remarkable. But there's a ceiling.

The Meshtastic app is a messaging tool with a basic map. It tells you where your nodes are. It does not tell you where your people are, relative to terrain features, mission objectives, roads, buildings, or each other in real time. It has no awareness of teams, no ability to drop tactical markers, no cursor-on-target. When the situation gets complex — search and rescue, emergency comms, field ops of any kind — you need a map platform, not a chat app.

ATAK is that platform. The Android Team Awareness Kit was originally developed by the Air Force Research Laboratory and has since become the standard for distributed situational awareness in both military and civilian public safety contexts. It runs on Android, shows live positions of every team member on a detailed map, supports tactical markers and shapes, relays messages between operators, and integrates with everything from drones to satellite feeds. ATAK doesn't care about your radio. It speaks a protocol called Cursor on Target (CoT) and accepts connections from whatever feeds it that data.

The Meshtastic ATAK plugin bridges these two worlds. It runs on the same Android device as ATAK, connects to your Meshtastic node via USB or Bluetooth, and translates LoRa mesh traffic into CoT events that appear live on your ATAK map. Your GPS position flows out over LoRa to every other team member. Their positions flow back. All of this happens with no cell towers, no internet, and no cloud services — just radio.

This guide walks through the complete build: selecting and flashing hardware, configuring the Meshtastic node, installing ATAK, wiring up the plugin, and deploying the whole stack in realistic field conditions. It covers the failure modes that send people to forums at 2am, and the advanced configurations that most guides skip.

By the end you'll have a working system. Not a demo. Not a lab test. A system you can hand to a team member who has never touched Meshtastic and watch their position appear on your map inside five minutes of them powering on.

Understanding
the Stack

The TAK Ecosystem

TAK (Team Awareness Kit) is a family of applications, not a single app. The core product is ATAK — the Android version. WinTAK runs on Windows desktops and laptops. iTAK runs on iOS. FreeTAK is an open-source TAK server implementation. They all speak the same underlying protocol: Cursor on Target (CoT), an XML-based format for representing tactical events.

CoT events describe things that happen in time and space. A position update is a CoT event. A chat message is a CoT event. A marker dropped on the map is a CoT event. Everything in the TAK world is expressed as CoT XML, wrapped in either UDP multicast packets or TCP streams, and consumed by whatever TAK client is listening.

<event version="2.0" uid="MESHTASTIC-abc123" type="a-f-G-U-C" how="m-g"
       time="2026-03-23T18:00:00Z" start="2026-03-23T18:00:00Z"
       stale="2026-03-23T18:05:00Z">
  <point lat="33.7701" lon="-118.1937" hae="15.0"
         ce="9999999" le="9999999"/>
  <detail>
    <contact callsign="ALPHA-1" endpoint="*:-1:stcp"/>
    <__group name="Cyan" role="Team Member"/>
  </detail>
</event>
COT XML

The type field encodes what kind of object this is. a-f-G-U-C means: Atoms → Friendly → Ground → Unit → Combat. The TAK type hierarchy is the language of the TAK map — it determines the icon, the color, and the behavior of every object shown.

Where Meshtastic Fits

Meshtastic is the radio transport layer. Your Meshtastic node does three things in this stack: it broadcasts your GPS position over LoRa to every other node in range (or in range of relay nodes), it receives position updates from other nodes and passes them to the ATAK plugin, and it carries GeoChat messages in both directions.

The Meshtastic ATAK plugin runs on your Android device alongside ATAK. It connects to your Meshtastic node — via USB serial or Bluetooth — and acts as a translator between the Meshtastic packet format and the CoT XML that ATAK consumes. The plugin registers itself as a TAK data connection, so ATAK sees it as just another network source and renders everything it receives natively.

Key Concepts

Protocol Versions — Which ATAK?

Hardware
Selection

Every Meshtastic-compatible board will work with the ATAK plugin, but not all hardware is equal in a field context. The key differentiators for ATAK integration are: GPS capability (for automatic PLI without relying on the phone), battery life, form factor, and connection interface (USB vs Bluetooth). The following boards represent the best choices for this specific use case.

What You'll Need Per Operator

• One Meshtastic-compatible LoRa node (T-Beam or T-Deck recommended)
• Android device running Android 9.0 or higher
• USB OTG cable (USB-A to USB-C or USB-C to USB-C) for wired connection, OR
• Alternatively: Bluetooth connection (no cable needed, lower reliability)
• LoRa antenna — DO NOT run without an antenna attached
• Power source: LiPo battery, 18650 cell, or USB power bank
• ATAK-CIV installed from Google Play
• Meshtastic ATAK plugin APK (sideloaded)

Antenna Selection

The stock antennas that ship with most LoRa dev boards are adequate for initial testing but underperform in the field. For ATAK deployments, the antenna is the single cheapest upgrade with the biggest range impact.

Flashing
Meshtastic Firmware

Meshtastic firmware is flashed directly to your LoRa board. The easiest method for most users is the web flasher at flasher.meshtastic.org — a browser-based tool that handles everything over WebUSB. No Python, no drivers, no terminal required. It supports Chrome and Edge only (no Firefox or Safari).

Method 1 — Web Flasher (Recommended)

Method 2 — CLI Flasher

For users who prefer the terminal or need to flash multiple boards rapidly:

# Install the Meshtastic CLI and esptool
$ pip3 install meshtastic esptool --break-system-packages

# Download firmware for your board from GitHub releases
# Example: T-Beam v1.1
$ wget https://github.com/meshtastic/firmware/releases/latest/download/firmware-tbeam-2.x.x.x.bin

# Put ESP32 boards into flash mode (hold BOOT button while pressing RESET)
# nRF52 boards (RAK, SenseCAP) may require DFU mode instead

# Flash via esptool (ESP32 boards)
$ esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 921600 write_flash 0x10000 firmware-tbeam-2.x.x.x.bin

# For nRF52-based boards (RAK, SenseCAP), use the UF2 drag-and-drop method:
# Double-tap RESET to enter bootloader, device mounts as USB drive
# Drag .uf2 firmware file onto the mounted drive
BASH

Firmware Variant Guide

Configuring Your
Meshtastic Node

After flashing, configure the node through the Meshtastic app (Android or iOS), the web interface (accessible via WiFi on WiFi-capable boards), or the Python CLI. For ATAK integration, you need to configure several specific settings beyond the defaults.

Initial Setup via Meshtastic App

# Configure via Python CLI — useful for batch configuration
$ pip3 install meshtastic --break-system-packages

# Show current configuration
$ meshtastic --info

# Set owner/callsign
$ meshtastic --set-owner "ALPHA-1" --set-owner-short "A1"

# Set region (must be set before radio will transmit)
$ meshtastic --set lora.region US

# Configure position broadcast interval (seconds)
$ meshtastic --set position.position_broadcast_secs 30

# Set modem preset
$ meshtastic --set lora.modem_preset LONG_FAST

# Enable node as a router (for relay nodes)
$ meshtastic --set device.role ROUTER

# Verify settings
$ meshtastic --info
BASH

Node Role Configuration

Meshtastic nodes have roles that determine how they behave on the mesh. For ATAK deployments, assign roles deliberately:

Installing
ATAK

Install ATAK-CIV from Google Play

ATAK-CIV (the civilian version) is available on the Google Play Store. Search for "ATAK" — the publisher is TAK Government. Install it like any other app. No account or registration is required to install and run the base application.

The Meshtastic
ATAK Plugin

The Meshtastic ATAK plugin is an ATAK plugin (ATAK uses a plugin architecture for extensions) that bridges your Meshtastic node with ATAK. It intercepts position data, translates it to CoT XML, and injects it into ATAK as if it came from a network connection. Simultaneously, it captures your ATAK position and PLI and transmits it through the Meshtastic node over LoRa.

Obtaining the Plugin

The official Meshtastic ATAK plugin is hosted on GitHub: github.com/meshtastic/ATAK-Plugin. Download the latest release APK from the releases page. This is a sideloaded application — it does not come from the Play Store. You'll need to enable "Install from unknown sources" for your browser or file manager in Android Settings.

Installing the Plugin

Plugin Interface Overview

PLI —
Sharing Your Position

Position Location Information is the core of what makes this integration powerful. Once configured, every team member with a connected Meshtastic node appears as a live icon on every other team member's ATAK map. Icons move in real time as people move. When a node goes silent (out of range, battery dead, turned off), its icon fades after the stale timer expires.

How PLI Flows

When the Meshtastic ATAK plugin is running and connected to a node, the flow works like this: your Android device's GPS (or the node's onboard GPS) generates a position fix. The plugin packages this as a CoT PLI event, then passes it to the Meshtastic app's IMeshService, which transmits the CoT payload over LoRa. Remote nodes receive the packet, decode the CoT payload, and pass it up to any ATAK plugins connected on those devices. Those plugins inject the position into their local ATAK instance and the icon appears on the map.

PLI Configuration Settings

In the Meshtastic ATAK plugin, the PLI configuration panel controls the following:

CoT Type Codes Reference

The CoT type code determines what icon appears on the ATAK map. The format is hierarchical: Affiliation → Battle Dimension → Function. For typical tactical deployments:

GeoChat
& Team Messaging

GeoChat is the ATAK messaging system. It's more than just text — every message carries sender location, team affiliation, and can be targeted to individuals, teams, or broadcast to all. The Meshtastic plugin bridges these messages bidirectionally: messages sent from ATAK GeoChat appear in the Meshtastic app's message list, and messages sent from the Meshtastic app appear in ATAK's GeoChat panel.

Sending Messages from ATAK

In ATAK, open the Chat panel (speech bubble icon in the toolbar). Messages sent here flow through the Meshtastic plugin and are broadcast over LoRa. The message appears in the chat panel of every team member's ATAK running the same channel configuration.

Team-specific messages (sent to a specific team color rather than All Chat) are sent on the corresponding Meshtastic channel. This lets you segment comms by team at the LoRa layer — Blue Team messages go on one channel, Red Team on another. Operators with the wrong channel configuration simply won't receive those messages.

Channel-to-Team Mapping

The Meshtastic plugin maps ATAK team colors to Meshtastic channels. Configure this mapping in the plugin's Channel Config panel. A common deployment uses the default (primary) Meshtastic channel as the equivalent of ATAK's "All Chat" broadcast channel, with secondary Meshtastic channels mapped to specific team colors.

Marker and CoT Object Sharing

The Meshtastic ATAK plugin can also relay CoT objects beyond PLI and chat — specifically, point markers dropped on the ATAK map. When an operator drops a tactical marker (enemy contact, vehicle, point of interest), the plugin encodes this as a CoT event and broadcasts it over LoRa. Remote operators see the marker appear on their maps.

This is one of the most tactically significant features of the integration. Sharing a grid coordinate verbally over a voice radio is slow and error-prone. Dropping a pin on the map and having it appear on everyone's map instantly eliminates that problem — even without voice comms.

Note on bandwidth: Map object sharing consumes significantly more bandwidth than PLI updates. On congested meshes, limit marker sharing to critical events only. Configure the plugin's CoT filter to transmit specific event types and suppress low-priority map objects.

Channels, Groups
& Encryption

Every Meshtastic channel has an independent AES-256 encryption key. Nodes that don't have the key for a channel cannot decode its traffic. This is the primary access control mechanism: you control who can communicate on each channel by controlling who has the keys.

Channel Configuration

Meshtastic supports up to 8 channels per node (0–7). Channel 0 is the primary channel — all nodes must have at least this configured the same way to communicate. Secondary channels (1–7) are optional and can carry different traffic types with different encryption keys.

# Set up channels via Python CLI

# Set primary channel name and key (all team members must match exactly)
$ meshtastic --ch-set name "TACTICAL" --ch-set psk "base64:YOUR_KEY_HERE==" --ch-index 0

# Add secondary channel for Blue Team
$ meshtastic --ch-add --ch-set name "BLUE" --ch-set psk "base64:BLUE_TEAM_KEY==" --ch-index 1

# Add Command net (restricted to leadership)
$ meshtastic --ch-add --ch-set name "CMD" --ch-set psk "base64:CMD_ONLY_KEY==" --ch-index 2

# Generate a random secure key (use this to create deployment keys)
$ python3 -c "import os, base64; print('base64:' + base64.b64encode(os.urandom(32)).decode())"

# Export channel QR code for easy distribution to team members
# In the Meshtastic app: Settings → QR Code → Share
# Team members scan this to configure their nodes identically
BASH

Key Distribution

Meshtastic generates a QR code for each channel configuration. Scanning this QR code with another Meshtastic node configures it with the correct channel name, settings, and encryption key in a single step. This is the fastest way to onboard new nodes to a deployment.

Operational security note: Channel QR codes contain the encryption key in encoded form. Treat them like a physical key — don't share them on untrusted networks, don't screenshot them and upload to cloud services, and revoke and re-key if a device is lost or compromised. Re-keying means generating new keys, reconfiguring all nodes, and redistributing new QR codes to the team.

ATAK Data Package Key Distribution

For teams running full ATAK deployments, encryption keys and channel configurations can be bundled in a TAK Data Package. This package is distributed to all operators before an operation — it configures both the ATAK side (team colors, callsigns, server connections) and provides the Meshtastic channel QR data. The Data Package approach is the most robust way to synchronize a large team's configuration before going into the field.

# ATAK Data Package structure for Meshtastic integration
DEPLOYMENT_NAME.zip
├── MANIFEST/
│   └── manifest.xml          # Package metadata
├── certs/
│   └── team_cert.p12         # Optional: TAK server TLS cert
├── configs/
│   └── network.xml           # TAK connection settings
├── preferences/
│   └── atak_preferences.pref # ATAK startup configuration
└── meshtastic/
    ├── channel_primary.qr    # Channel 0 QR data for node config
    ├── channel_blue.qr       # Channel 1 QR data
    └── README.txt            # Node setup instructions for operators
STRUCTURE

TAK Server
Bridging

The Meshtastic ATAK integration is fully self-contained — it requires no server. But in hybrid deployments where some operators have internet connectivity (even intermittent) and others are on pure LoRa mesh, a TAK Server acts as a hub that bridges the two worlds. Operators on the internet see the full operational picture including LoRa-mesh nodes. LoRa-mesh operators relay position and chat to the server when connectivity is available, extending their reach beyond the mesh.

FreeTAK Server (Open Source)

FreeTAK Server is the open-source implementation of a TAK server. It runs on any Linux machine, Raspberry Pi, or cloud VPS. It accepts CoT connections from ATAK clients and relays events between them. For our purposes, it serves as a bridge between the LoRa mesh network and any broader IP network.

# Install FreeTAK Server on a Linux machine or Raspberry Pi
$ pip3 install FreeTAKServer --break-system-packages

# Or via the automated installer script
$ wget -qO - https://raw.githubusercontent.com/FreeTAKTeam/FreeTAKServer-User-Docs/main/docs/deployment/automated/install.sh | bash

# Start the server
$ python3 -m FreeTAKServer.controllers.services.FTS -CoTServicePort 8087 \
         -DataPackageServicePort 8080 \
         -FTS_SECRET_KEY "your-secret-key"

# Default ports:
# 8087 — CoT TCP (ATAK client connections)
# 8080 — Data Package Service (HTTP)
# 19023 — SSL (if enabled)
BASH

Connecting ATAK to a TAK Server

In ATAK, go to Settings → Network Settings → TAK Servers → Add Server. Enter the server IP/hostname and port (default: 8087 for TCP). ATAK connects and begins relaying all CoT events — including the PLI data coming from your Meshtastic node via the plugin — to the server, which distributes them to all connected clients.

Meshtastic MQTT Bridge (Alternative)

Meshtastic also includes an optional MQTT bridge that can forward mesh traffic to an MQTT broker over WiFi or cellular. This is a separate integration path from the ATAK plugin. If you have a Raspberry Pi at base camp with WiFi reach to the mesh, it can bridge Meshtastic traffic to an MQTT broker, which a custom gateway can then forward as CoT to a TAK server. This is a more complex setup but enables full mesh visibility at the command center without operators needing direct ATAK connections.

WinTAK &
Desktop Integration

WinTAK is the Windows version of ATAK — same protocol, same CoT events, larger screen. It's commonly used at base camp, Emergency Operations Centers, and command posts where a laptop or desktop is present. WinTAK cannot directly connect to a Meshtastic node (the plugin only runs on Android), but it participates fully in the operational picture via TAK Server.

Setting Up WinTAK

# WinTAK multicast connection (ATAK default broadcast address)
# In WinTAK: Preferences → Network Preferences → Network Connections → Add
# Type: UDP Multicast
# Address: 239.2.3.1
# Port: 6969
# This is the default ATAK LAN SA (Situational Awareness) multicast group

# ATAK also broadcasts on this address by default
# Both apps on the same WiFi network = automatic shared picture
# No configuration required on the ATAK side
WINTAK

Tactical Deployment
Scenarios

The Meshtastic + ATAK stack is not a single product with a fixed use case — it's a configurable platform. The following deployment scenarios illustrate how to tailor the configuration for specific operational contexts.

Node Deployment Best Practices

Regardless of scenario, these practices improve mesh performance and reliability:

Failures
& Fixes

Debug Workflow

When things break, follow this sequence before diving deep into settings:

Appendix
& Reference

Regional Frequency Reference

Meshtastic Modem Presets

Meshtastic CLI Quick Reference

ATAK + Plugin + Firmware Compatibility Matrix

Always verify against current releases: github.com/meshtastic/ATAK-Plugin/releases · github.com/meshtastic/firmware/releases

Hardware Comparison Summary

Key Resources