Přeskočit na hlavní obsah

Setting up TAK Server Integration

All of our cloud-connected Dronetag products can be integrated with TAK Server by using our integration portal and stream their Drone Remote ID data in the Cursor on Target (CoT) format directly to your TAK server in real-time.

Network Remote ID (NRI) devices (such as Dronetag Mini), can stream their UA positions. Direct Remote ID (DRI) receivers (such as Dronetag RIDER or Dronetag Scout) can additionally stream the operator location, and the location of the receiver itself.

info

This article is about setting up TAK Server integration from our cloud environment over public internet. We're working on enabling Dronetag Scout in Sensor+ Mode to integrate with TAK directly. Please contact us if you're interested in direct TAK integration and would like to inquire about the current state of the integration.

Prerequisites​

Before you begin, ensure you have:

  • Dronetag account (create at https://dronetag.app/signup)
  • Supported Dronetag product(s) registered on your account
    • Supported are Dronetag Mini, Dronetag Mini 4G, Dronetag RIDER, or Dronetag Scout
  • Active Pro or Enterprise subscription plan (required for integration portal access)
  • TAK Server instance
    • With publicly accessible TAK Server endpoint (IP address or domain name)

How to Set-up​

  1. Configure your TAK Server​

    Before setting up the integration, ensure your TAK Server is ready:

    1. Open the required port on your firewall
    2. Configure TAK Server to accept data feeds on this port
    3. Note your connection details:
      • Server IP or domain (e.g., tak.yourcompany.com or 203.0.100.200)
      • Port number (e.g., 8087)

    If unfamiliar with TAK Server configuration, refer to the official TAK Server documentation.

  2. Access the Integration Portal​

    Visit https://integrations.dronetag.app and sign in using your account credentials

  3. Create New Distribution​

    Create a new distribution using the following configuration:

    Required Settings​

    • Connection type — TCP or UDP Socket
    • Target URI — Your TAK Server address (e.g., tak.yourcompany.com or 203.0.100.200)
    • Target port — Your TAK Server port (e.g., 8087)
    • Output format — Cursor on Target XML

    Leave the other options to default values, or customize to your preferences. Please note that not all options are relevant to TCP+XML integration.

    Data Source Selection​

    Take note of the selected data source. The default, "My account", streams data from all devices registered to your account. Other options include "Device Groups" (a static list of devices) and "Partnered Integration" (allows any Dronetag user to share data to your TAK server). Contact us for details.

    Optional mTLS Authentication​

    If your TAK Server requires mutual TLS authentication, enable the mTLS option and upload the necessary client certificate and private key files in PEM format. This option is available only for TCP connections.

  4. Verify the Connection​

    • Allow 2-3 minutes for the integration to initialize and establish connection
    • Turn on your Dronetag device and ensure it's actively transmitting
    • Open your TAK client (ATAK, WinTAK, or iTAK), look for the drone icon appearing on your map at the device's location
    • Verify position updates are occurring in real-time

Troubleshooting​

If you're experiencing issues, try these steps in order:

  1. Verify TAK Server connectivity — Ensure your TAK Server IP/domain is correct and publicly accessible. Check that firewall rules allow incoming connections on the specified port.

  2. Check device status — Confirm your Dronetag device is powered on, has GNSS lock, shows as "Online" and is visible on the map in your account at https://dronetag.app.

  3. Review integration portal logs — Check the "Server logs" section in the integration portal and refresh the view several times (logs are not real-time). Look for connection errors or status messages.

  4. Allow time for initialization — The integration needs 2-3 minutes to establish connection. If issues persist beyond this, restart the distribution in the integration portal by disabling and re-enabling the distribution.

If problems persist, contact support with your server logs and configuration details.

Relevant Resources​