From 674681aa89866b078e5473d7ce2dbf1641f790a1 Mon Sep 17 00:00:00 2001 From: Sean Kilgore Date: Sun, 25 Feb 2024 14:29:43 -0800 Subject: [PATCH 1/2] docs: make atak plugin install more explicit --- docs/software/integrations/atak-plugin.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/software/integrations/atak-plugin.mdx b/docs/software/integrations/atak-plugin.mdx index d2732ecc..858f8abb 100644 --- a/docs/software/integrations/atak-plugin.mdx +++ b/docs/software/integrations/atak-plugin.mdx @@ -23,11 +23,13 @@ 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 -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 to a Meshtastic device 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 to a Meshtastic device and configured with the Meshtastic ATAK plugin (provided they are configured on the same Meshtastic channels). A couple of important notes regarding this setup: From 67946af5d7faef443da7be6d7548db8a61c55997 Mon Sep 17 00:00:00 2001 From: Sean Kilgore Date: Sun, 25 Feb 2024 14:40:26 -0800 Subject: [PATCH 2/2] docs: atak; remove 'your' reference --- docs/software/integrations/atak-plugin.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/software/integrations/atak-plugin.mdx b/docs/software/integrations/atak-plugin.mdx index 858f8abb..609e836b 100644 --- a/docs/software/integrations/atak-plugin.mdx +++ b/docs/software/integrations/atak-plugin.mdx @@ -23,7 +23,7 @@ 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. 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). +3. Install the version of the Meshtastic ATAK-Plugin that matches the ATAK version on all participants' 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.