ATAK over Meshtastic Configuration Guide

Overview

This guide covers complete configuration of ATAK (Android Team Awareness Kit) integration with Meshtastic mesh networks. You'll learn firmware version requirements, optimal Meshtastic settings for ShortTurbo, complete ATAK plugin configuration, and mesh architecture strategies for scaling your network.

Prerequisites: This is an advanced configuration guide. You should already have Meshtastic devices, understand basic Meshtastic operation, and have ATAK-CIV installed. If you're new to Meshtastic, start with the Meshtastic Devices guide first. There is also a guide for getting started with ATAK.

Why Version Numbers Matter

Meshtastic uses Protocol Buffers (protobufs) for data serialization. In recent versions of the Meshtastic firmware, the protobuf definitions changed significantly. If your firmware versions and app versions don't align, you'll end up in a non-functioning mesh quagmire where devices can't properly communicate.

Current Recommended Versions (January 2026):

Meshtastic Firmware: 2.7.15 (from flasher.meshtastic.org)
Meshtastic Android App: 2.7.10 (from the Play Store or GitHub)
ATAK Meshtastic Plugin: 1.1.33 (from GitHub)

Check your firmware version before starting. Upgrade if needed. The compatibility matters more for ATAK integration than for basic Meshtastic operation.

Meshtastic Configuration

Most default settings are fine, but here's what needs tuning for optimal ATAK performance over ShortTurbo. All settings are configured through the Meshtastic Android app.

LoRa Settings

Settings → Radio configuration → LoRa

Setting	Value	Why
Preset	Short Range - Turbo	LongFast lacks bandwidth for ATAK. ShortTurbo provides the throughput needed for PLI, chat, and data packages.
Ignore MQTT	On	We don't care about internet traffic on a private RF-only mesh. Reduces noise.
Frequency Slot	49	"0" should theoretically auto-negotiate, but explicit is better. Prevents frequency conflicts.

Device will reboot when you save these changes.

Channel Settings

Settings → Radio configuration → Channels

Delete the default "LongFast" or "ShortFast" channel (channel 0)
Replace with a private primary channel
Set a PSK for AES 256-bit encryption
Enable precise location
Hit "Send" after changes (device will NOT reboot for channel changes)

Quick QR Code Setup: On the "Conversations" tab in the Meshtastic app, there's a QR code icon in the bottom right. Use this to easily copy your private encrypted channels to other devices, or generate a link to share channels if configuring multiple devices with the same Android device.

Device Settings

Settings → Device configuration → Device

Setting	Value	Use Case
Device Role	TAK	For devices paired with an ATAK EUD via Bluetooth
Device Role	TAK_TRACKER	For standalone devices with no ATAK EUD attached
Rebroadcast Mode	LOCAL_ONLY	Only care about traffic on our private channel(s), not public mesh

Timezone (optional): "Use phone time zone" works fine. For standalone devices, set a POSIX timezone string.
For example, US Eastern/New York would be:
EST5EDT,M3.2.0/2:00:00,M11.1.0/2:00:00
-or-
EST5EDT,M3.2.0/2,M11.1.0/2
if you shorten each instance of "2:00:00" to "2".

Device will reboot when you save these changes.

Position Settings

Settings → Device configuration → Position

Setting	Value	Why
Smart Position	On	Only broadcasts position when it changes/when you're moving. Reduces mesh chatter, also saves battery.

Note: You can turn Smart Position off for stationary testing to see more frequent updates, but leave it on for operational use.

Device will reboot when you save these changes.

Display Settings

Settings → Device configuration → Display

Setting	Options
Display Units	Switch between metric and imperial as needed

Device will reboot when you save these changes.

ATAK Plugin Installation

If you haven't already, download the correct plugin version and install it: ATAK Plugin Releases

In ATAK, enable the Meshtastic plugin via Settings → Plugins

ATAK Plugin Configuration

Navigate to: Settings → Tool Preferences → Specific Tool Preferences → Meshtastic Preferences

Mesh Settings

Setting	Value	Explanation
Meshtastic Channel Index	0	Use your private primary encrypted channel. Set to different value if using a different channel for ATAK.
Filter by Channel Index	On	Ignore traffic on other channels if you have multiple channels configured.
Hop Limit	3	Good starting point. Controls how many mesh hops a message can make. Adjust based on network size.
Request ACK	Off	Don't need acknowledgments, just extra mesh traffic. Turn off for scalability.

PLI & Reporting

Setting	Value	Why
Limit PLI Reporting Rate	On	Keeps the mesh clean by throttling position updates.
PLI Reporting Interval	1 minute	Balance between situational awareness and bandwidth conservation.
Only Send PLI and Chat	Off	We want to send data packages, GRGs, etc., not just position and chat.
Send Read/Delivery Receipts	Off	Extra traffic we don't need. Save bandwidth.

Display Settings

Setting	Value	Effect
Show Meshtastic Devices	On	See standalone TAK_TRACKER devices and ATAK EUDs on the map.
Hide Devices Without GPS	Off	Personal preference. Some prefer to see every device in geochat even without position.
Hide Local Node	On	Shows your usual Blue Arrow in ATAK without a duplicate Meshtastic icon. Cleaner display.

Server Relay

Setting	Default Value	Gateway ATAK EUD
Relay to Server	Off	On (for gateway only)
Relay from Server	Off	On (for gateway only)

Critical: Only enable these on one EUD. That EUD becomes your "gateway" between your ATAK server and mesh network. It must have internet access. All other EUDs should have these turned off to avoid a traffic relay nightmare.

File Transfer

Setting	Value	Notes
Enable File Transfer	On	ShortTurbo has some bandwidth. Use it.

Audio & Voice

Text to Speech	Off	Enable if you want ATAK to read messages aloud. Personal preference.
PTT KeyCode	Off	Push-to-talk feature, off unless you're using it.

GPS Settings

Use Meshtastic GPS

Use the Meshtastic device's GPS for position data.

Encryption

Enable Extra Encryption	Off	Only enable if you need to encrypt already-encrypted packets. Usually unnecessary.
Encryption PSK	Unset	Leave blank unless double-encrypting.

Mesh Architecture & Scaling

Once your nodes can see each other, optimize your mesh architecture for performance and scalability.

Favorites System

Add nodes to each other's "Favorites" via the node list in the Meshtastic Android app. Favorited nodes get priority treatment in mesh routing.

Strategy: Create a core group of reliable, well-positioned nodes that favor each other. This creates a backbone mesh that newer nodes can connect to.

CLIENT_BASE Role for Fixed Nodes

If you have a well-positioned, stationary high node (rooftop, tower, hilltop), set its Role to CLIENT_BASE.

Behavior: Acts as a ROUTER for nodes it has favorited, acts as a CLIENT for any others. This is a good baseline strategy for scaling your mesh. Your priority nodes get routing, but the node still plays nice with strangers.

Best practices:

Use CLIENT_BASE for solar-powered rooftop nodes
Use CLIENT_BASE for any node that has excellent coverage and reliable power
Favor your mobile nodes from these fixed nodes
This creates mesh "infrastructure" separate from portable/mobile nodes

Scaling Your Network

As you add more nodes, think in layers:

Core infrastructure: Fixed CLIENT_BASE nodes with solar power, optimal positioning
Mobile operators: TAK role devices paired with ATAK EUDs
Trackers: TAK_TRACKER devices for personnel or asset tracking
Edge nodes: Extending coverage at the periphery

Each layer serves a purpose. Infrastructure provides reliability. Mobile operators provide flexibility. Trackers provide visibility. Edge nodes extend reach.

Troubleshooting

Common Issues:

Nodes see each other but ATAK doesn't show them: Check channel index settings. Make sure ATAK plugin is using the same channel as your encrypted Meshtastic channel.
Messages not getting through: Check hop limit. Start at 3, adjust if needed. Verify encryption is configured the same on all nodes.
Poor performance: Confirm you're using ShortTurbo, not LongFast. LongFast lacks bandwidth for ATAK traffic.
Firmware version conflicts: Verify all devices are on compatible firmware (2.7.x series). Check app version matches firmware series.
Gateway not bridging to server: Only one Meshtastic-enabled ATAK EUD should have "Relay to/from Server" enabled. Verify that EUD has internet connectivity.

Performance Notes

ShortTurbo provides significantly better throughput than default LongFast, but at the cost of range. Typical ranges:

Urban environment: 0.5 miles depending on obstacles
Suburban environment: 1 mile with line of sight
Elevated node in rural/open terrain: 3 miles with good line of sight
High elevation nodes: Can easily extend to 10+ miles in good conditions

The trade-off is worth it for ATAK integration. The extra bandwidth enables file transfer, faster PLI updates, and more reliable data package transmission.

Additional Resources

For more information on ATAK and Meshtastic:

Meshtastic ATAK Plugin GitHub
Official Meshtastic Documentation
Chaos Koalas FAQ - Common questions about mesh networking
Contact Us - Get help with your setup

Next Steps

You now have a complete ATAK-integrated mesh network. Test it. Practice with it. Break it and fix it. Understanding how it behaves under different conditions makes you a better operator when it matters.

Consider running regular neighborhood nets, testing file transfers, experimenting with different node roles and positions. The more familiar you are with the system, the more effective you'll be in an actual emergency.

Deploy strategically. Practice regularly. Stay ready.