Update atak-plugin.mdx

This commit is contained in:
Ben Meadors 2024-02-19 12:46:37 -06:00 committed by GitHub
parent ba6c0a525f
commit f53cbe16f4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -21,7 +21,7 @@ The ATAK plugin does not permit any Meshtastic configuration. The plugin does th
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.
2. Set the device's role to `TAK` in the configuration settings
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.
@ -33,8 +33,6 @@ For devices with GPS available, configuring the device's role to `TAK_TRACKER` w
A couple of important notes regarding this setup:
1. The intervals and behavior of TAK PLI broadcast will honor the settings configured for the standard [/configuration/radio/position/](Position config) in Meshtastic.
1. The intervals and behavior of TAK PLI broadcast will honor the settings configured for the standard (Position configuration)[/docs/configuration/radio/position/] in Meshtastic.
2. The callsign sent with the PLI will appear in ATAK with the `long_name` configured for the Meshtastic device.
2. The callsign sent with the PLI will appear in ATAK with the User [Long Name](/docs/configuration/radio/user/#long-name) configured for the Meshtastic device.