mirror of
https://github.com/meshtastic/meshtastic.git
synced 2025-01-29 23:00:46 -08:00
docs: make atak plugin install more explicit
This commit is contained in:
parent
dcd5e84bea
commit
674681aa89
|
@ -23,7 +23,9 @@ The ATAK plugin does not permit any Meshtastic configuration. The plugin does th
|
|||
|
||||
2. Set the device's role to `TAK` in the [device configuration settings](/docs/configuration/radio/device/).
|
||||
|
||||
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.
|
||||
3. Install the release of the Meshtastic ATAK-Plugin that matches your version of ATAK on all parties' devices from the [project's GitHub Releases](https://github.com/meshtastic/ATAK-Plugin/releases).
|
||||
|
||||
4. 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. If you do not see a Meshtastic icon, make sure that you have installed the Meshtastic ATAK-Plugin correctly.
|
||||
|
||||
## Standalone TAK Tracker usage
|
||||
|
||||
|
|
Loading…
Reference in a new issue