mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-03-05 21:00:08 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update atak-plugin.mdx

Browse source
This commit is contained in:
Ben Meadors 2024-02-19 13:03:58 -06:00 committed by GitHub
parent 54866c100c
commit 0ad2496a6e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/software/integrations/atak-plugin.mdx
View file

@ -14,22 +14,20 @@ Meshtastic can integrate with ATAK on Android using the [Official ATAK Plugin.](
The ATAK plugin does not permit any Meshtastic configuration. The plugin does three things:
1. Binds to the IMeshService provided by the Meshtastic Android App in order to send.
2. Intercepts all outgoing ATAK CoT via the ATAK "PreSendProcessor" Interface and send them to the IMeshService.
2. Intercepts all outgoing ATAK CoT via the ATAK "PreSendProcessor" Interface and sends them to the IMeshService.
3. Listens for broadcasts from the Meshtastic Android App on the ATAK_PLUGIN portnum packets.
### Instructions
1. Use the Meshtastic Android App on all party's devices, and ensure they can talk to their local LoRa radio. Confirm they are able to achieve basic text messaging using the App.
1. Use the Meshtastic Android App on all parties' devices, and ensure they can talk to their local LoRa radio. Confirm they are able to achieve basic text messaging using the App.
2. Set the device's role to `TAK` in the (device configuration settings)[/docs/configuration/radio/device/].
2. With the Meshtastic Android App running in the background (to ensure the IMeshService is alive), launch ATAK (with the Meshtastic ATAK-Plugin installed or install it once ATAK is running) and you should observe a green Meshtastic icon in the bottom right. If the icon is red, then the plugin was not able to bind to the IMeshService provided by the Meshtastic Android App. If this is the case, check to ensure the Meshtastic Android App is functioning. The plugin will reconnect after a failed bind without restarting ATAK.
3. Sending larger CoT such as freestyle map drawings or GeoChats will fragment and take longer to send. Don't try to send a bunch without waiting for the previous one to complete.
3. With the Meshtastic Android App running in the background (to ensure the IMeshService is alive), launch ATAK (with the Meshtastic ATAK-Plugin installed or install it once ATAK is running) and you should observe a green Meshtastic icon in the bottom right. If the icon is red, then the plugin was not able to bind to the IMeshService provided by the Meshtastic Android App. If this is the case, check to ensure the Meshtastic Android App is functioning. The plugin will reconnect after a failed bind without restarting ATAK.
## Standalone TAK Tracker usage
For devices with GPS available, configuring the device's role to `TAK_TRACKER` will allow the Meshtastic to transmit TAK PLI data independently of ATAK. This data can be received and displayed within ATAK EUDs connected and configured with the Meshtastic ATAK plugin (provided they are configured on the same Meshtastic channels).
For devices with GPS available, configuring the device's role to `TAK_TRACKER` will allow the Meshtastic to transmit TAK PLI (Position Location Information) independently of ATAK. This data can be received and displayed within ATAK EUDs connected and configured with the Meshtastic ATAK plugin (provided they are configured on the same Meshtastic channels).
A couple of important notes regarding this setup: