▲ 7 r/meshtastic
Context: Meshtastic integrated with ATAK can deliver GPS via the plugin, but ATAK will default to the phone’s GNSS unless explicitly redirected.
Observed behavior
- Meshtastic node has valid GPS fix.
- Plugin connection is functional.
- ATAK self marker still follows phone location.
Resolution procedure
- Meshtastic channel configuration
- Ensure the channel carrying position data (with precise location enabled) is set to index 0.
- The plugin may allow selecting a channel index for general data, but self-location (arrow marker) is sourced strictly from index 0.
- Enable Meshtastic GPS in plugin
- Open the Meshtastic plugin settings inside ATAK.
- Enable “Use Meshtastic GPS”.
- Without this flag, the plugin will not forward GPS data as a location source.
- Disable internal GPS in ATAK
- Open Overlay Manager (three stacked planes icon).
- Go to Location Input Manager.
- Uncheck Internal GNSS/GPS Receiver.
- This prevents ATAK from prioritizing the phone’s onboard GPS.
- Verify NMEA streaming
- In the same Location Input Manager, ensure Streaming NMEA is enabled.
- Status should be active (green).
- Confirm that location data appears with a current timestamp.
Result
- The ATAK self marker (arrow) is now driven by the Meshtastic node’s GPS feed instead of the phone GNSS.
Key constraints
- Channel index 0 is mandatory for self-location ingestion.
- “Use Meshtastic GPS” must be enabled; otherwise GPS data is ignored even if received.
- ATAK always prioritizes internal GNSS unless explicitly disabled.
u/ArgumentLive3678 — 17 days ago