Dronetag Scout is a stationary Remote ID receiver, designed to detect compliant drones within its coverage area, providing robust operational awareness. Remote ID technology enables the identification and tracking of drones that meet regulatory standards, enhancing situational awareness and safety in shared airspace.

With Dronetag Scout, users can monitor drone activities, receive real-time data on drone identification, location, heading, speed, height (barometric and GNSS), status, take-off location, and operator location - helping ensure compliance with local airspace regulations. Its stationary design is ideal for fixed installations, offering a reliable solution for consistent, real-time insight into drone operations in the vicinity.

Dronetag Scout supports all Remote ID technologies Wi-Fi Beacon, Wi-Fi NaN, Bluetooth 4 Legacy and Bluetooth 5 Long Range (LE Coded PHY) for Remote ID detection.

• In this photo is Dronetag Scout with One Dual-Band Omnidirectional Antenna, Four Directional Antennas and Holder for Four Directional Antennas.

What Scout Detects​

The Dronetag Scout is drone-agnostic and captures all Broadcast/Direct Remote ID data from drones that comply with Remote ID standards, such as DJI, Autel, and Skydio - up to 10 km in the EU, US, and Japan (with more regions expected to adopt these standards soon). The data can be sent in real-time to the Dronetag App for data visualization and airspace alerts or can be sent raw to third-party platforms without Dronetag apps being involved. It works regardless of whether the drone has built-in Remote ID capabilities or uses an external module.

Please note: the Scout device detects only Remote ID signals - if the drone does not broadcast any Remote ID, the Scout will not detect it.

Here you can find all information about Remote ID.

For a detailed and up-to-date list of Remote ID compatible drones, please contact the official agencies:

• EU: EASA
• US: FAA
• Japan: MLIT

Features​

🧠 Summary​

Dronetag Scout redefines Remote ID detection with:

• Unlimited simultaneous drone tracking
• Zero false positives
• Full-band 2.4 GHz + 5 GHz scanning
• Smart multi-channel tracking logic
• Modular, scalable design
• Real-time cloud connectivity and automatic updates
• Rugged IP67 build ready for 24/7 operation

Simply put - it sees everything, everywhere, with total accuracy.

Optional Upgrades​

You can enhance your Scout with custom upgrades, tailored to your needs:

• 4G Modem with SIM Card and LTE Antenna – Enable online cloud transmission for real-time data monitoring and integration.
• Directional Antennas – Improve performance in high-interference environments or extend coverage with up to 4 antennas for 360° reception.
• Older DJI Drones without Remote ID (planned feature) – Add extra sensors to detect legacy DJI models like Mini 2, Air 2, Mavic 2, Phantom 4 Pro.
• On-Premise Deployment – Operate without cloud dependency for secure, private access.
• ADS-B, ADS-L, FLARM and Other Protocol Support – Add additional aviation tech for full situational awareness.

Range​

The range is defined by the Remote ID transmitter power on the drone and the environment in which the receiver is located. For this User Guide, we divided it into Detection Range and Tracking Range:

Detection Range​

• Ability to sporadically pick up drone activity at greater distances.

Tracking Range​

• Real-time, continuous reception for reliable monitoring.

Tests were based on real internal testing. Drones were flown at different altitudes and distances. A Dronetag Beacon (Bluetooth) and DJI Mavic 3 (Wi-Fi) were used as transmitters, and results comply with EU signal power regulations.

Where to Start with Dronetag Scout​

To explore what your Dronetag Scout can do and how to best deploy it for your use case, start with the overview of supported Operating Modes:

🔍 See all available modes and choose the right one for your mission

We recommend using the Scout in Cloud Mode together with the Dronetag App — it's the easiest way to set up, manage, and monitor your system. It offers full feature access including real-time tracking, data storage, alerts and remote control.

👉 Follow our guide to get started with Cloud Mode and the Dronetag App

For further details or inquiries, contact Dronetag Support.

PoE injector​

The PoE injector is a device that allows you to combine power and network connectivity to your PoE enabled devices using the same Cat5/5e or Cat6 twisted pair cable.

PoE Features:

• Input: 100-240 V AC (50~60 Hz)
• Output: 48.0 V DC 0.5 A
• Overcurrent protection
• Supports 10/100 Mbps Ethernet
• 92.5x47x29.8 mm (±1 mm)

Dronetag s.r.o. carries no responsibility for wrong usage or wrong installation.

Dronetag Scout is available in several configurations tailored to your monitoring needs.
Each setup combines omnidirectional and directional antennas to achieve the ideal coverage pattern for your environment.

Scout Antenna Options​

Dronetag Scout is available in multiple antenna configurations, allowing you to tailor the system to your specific monitoring needs.
Depending on your deployment — whether you need 360° situational awareness or extended range in one or more directions — you can choose from several combinations of omnidirectional and directional antennas for optimal airspace coverage.

Installation Weight of Scout Variants​

Below are approximate total installation weights of different Dronetag Scout antenna configurations, including mounting holders and antennas.

Scout Hardware 3D Models​

To help you better understand the physical setup and mounting options, we provide 3D models of our Scout configurations.

These models can be viewed directly in your browser or downloaded using the links below for your own planning, integration, or installation workflows.

Below are the most common Scout setups:

• Scout Baseline – compact, omnidirectional setup for general coverage
  👉 View 3D model

• Scout (1× Omni + 4× 90° Sector) – extended configuration for maximum coverage and directional detection
  👉 View 3D model

Optional Add-Ons​

Beyond antenna configurations, customers can independently select additional modules and software options according to their operational needs.
Each Scout unit can be customized with connectivity and data-service features tailored to the deployment scenario.

LTE Modem​

Adds integrated LTE connectivity, enabling real-time data transmission without Ethernet connection.
Ideal for remote deployments or temporary installations where wired internet is unavailable.
The LTE module can be added to any Scout configuration, regardless of antenna setup.

Yearly Cloud License​

Required to operate Scout in Cloud Mode, On-Premise Mode, or Sensor+ Mode.

• Includes access to Dronetag Cloud, live visualization, data history, deduplication, and integrations.
• Not required for Sensor Mode, where Scout is used for raw data collection and integration into your own system.
  The license can be activated independently of hardware configuration.

Coming Soon – Expansion Options​

Future versions of Scout will support optional modules such as ADS-B, ADS-L, FLARM and others, further extending detection capabilities beyond Remote ID to provide complete situational awareness across both crewed and uncrewed aviation.

💡 Need help choosing?

• Baseline – ideal for standard airspace awareness.
• Directional setups – increase range and precision for specific sectors.
• LTE + Cloud License – unlock remote, real-time, and multi-sensor features for enterprise or security applications.

Dronetag Scout supports multiple operational modes to suit different deployment scenarios and customer needs — from low-overhead standalone integrations to cloud-connected systems with advanced features and visualization tools.

This page provides a quick overview of the available modes to help you choose the best configuration for your use case.

🛰️ Sensor Mode (Raw Data Receiver)​

Simplest & Most Autonomous Option

Sensor Mode turns the Scout into a dependable, plug-and-play Remote ID receiver. It captures compliant drone broadcasts and outputs decoded data via MQTT or HTTP webhooks — no cloud, no registration, and no subscription required.

🔧 Features:​

• Receives Remote ID signals from surrounding drones.
• Decodes to JSON based on Open Drone ID specification.
• Transmits detection data over Ethernet or LTE.
• No dependencies — no registration, no internet required.
• Ideal for system integrators or sensor network deployments.
• Barebone: No included Dronetag support or cloud features.

📘 Learn how to connect to the Scout: Connecting to Scout
🔧 Configure sensor integrations: Scout Sensor Mode Configuration

Sensor Mode is a standalone mode offering pure hardware functionality with robust output. Perfect for those who just need data — no fluff.

🛰️ Scout Sensor+ Mode (Enhanced Sensor Mode)​

Smarter Detection with Integrated Intelligence

Sensor+ Mode builds on Sensor Mode by adding real-time drone classification and enterprise-grade support. It’s designed for users who need a more intelligent system with simplified integration and enhanced situational awareness.

🔧 Features:​

• All Sensor Mode capabilities, plus:
• Drone model/manufacturer detection onboard via live drone database
• Automatic firmware & database updates
• Remote troubleshooting support from Dronetag
• Basic UI for visual monitoring (Scout Map Interface)
• Advanced integrations into TAK, SAPIENT, and more

📘 Learn how to connect to the Scout: Connecting to Scout
🔧 Configure integrations: Scout Heartbeat Forwarders

Sensor+ is ideal for professional users who want intelligent outputs, real-time classification, and the assurance of active maintenance and support.

☁️ Cloud Mode​

End-to-End Solution with Mobile & Web Access

Cloud Mode enables the full suite of Dronetag capabilities — from setup to data visualization — all managed through the Dronetag App. Designed for easy deployment with mobile and web control, Cloud Mode brings real-time insight anywhere you go.

🔧 Features:​

• Mobile & Web App access
• Live drone tracking & alerts
• Remote device management
• Data deduplication & cloud logging
• Flexible cloud integrations
• Works over LTE or Ethernet

📘 Detailed instructions: Using the Dronetag App with Scout

Cloud Mode is the best choice for users who want everything managed, visualized, and integrated in one seamless platform.

🏢 On-Premise Mode​

Cloud Power, Your Infrastructure

On-Premise mode mirrors the Cloud Mode’s capabilities but runs entirely within your infrastructure. Ideal for sensitive or regulated deployments (e.g. defense, government, critical infrastructure), it offers complete control over data privacy and system access.

🔧 Features:​

• All Cloud Mode features, hosted locally
• Full data privacy, no external dependencies
• Integrates with secure/closed systems
• Available as custom enterprise deployment

📩 For On-Premise deployments, please contact us at support@dronetag.com to discuss your requirements.

For detailed setup instructions for each mode, see the relevant sections in the Getting Started Guide.

At Dronetag, we strive to deliver the most functional and reliable solutions for your Remote ID needs.
Each Scout package is carefully assembled to ensure you have everything required for a smooth and efficient setup.

• Baseline
• 2x Omni and 1x 90° Directional
• 2x Omni and 2x 90° Directional
• 2x Omni and 3x 90° Directional
• 1x Omni and 4x 90° Directional

Scout Baseline​

Once you receive your Scout device with its basic configuration, you should find everything neatly packed in the delivery box. Here’s what to expect when unboxing your new Scout system:

This image illustrates the standard contents included in the Scout baseline package.

3D Model​

• Scout Baseline – compact, omnidirectional setup for general coverage
  👉 View 3D model

PACKAGING SIZE INFO

The Scout package comes in a sturdy box with the following dimensions:

450 mm x 300 mm x 150 mm / 17.7" x 11.8" x 5.9"

This compact size ensures the contents are well-protected during transport while still being easy to handle.

This section describes the requirements for successful deployment of the Scout.

What is required to install and operate the Scout?​

• Appropriate place to mount the Scout
• Pole in the desired place with a diameter of 45 – 110 mm
• Two 10 mm wrenches
• Power outlet or Ethernet available with supported PoE
• Ethernet cable dedicated for outdoor use (CAT5 and higher)
• Ability and equipment to crimp your Ethernet cable
• Safe and dry place for placing the PoE injector
• Local network which will be used to operate the Scout
• Ethernet port configured to 100 Mbit Full Duplex
• Computer to connect to local network to configure Scout

This guide walks you through the full process of deploying your Dronetag Scout device—from unboxing to live drone detection in the field. Each step includes helpful links to relevant documentation, so you can get started quickly and confidently.

1. Unpack Your Scout Device​

Begin by unboxing your Dronetag Scout and verifying that all components are present. Before physical deployment, connect the device to your local network to verify functionality.

2. Connect the PoE Injector to Power​

Use the Power over Ethernet (PoE) injector included with your Scout.

🔌 Connecting to the Scout

4. Access the Management Page​

Open the Scout’s Management Page in your browser (e.g., https://[Scout-IP]).
Here, you can view diagnostics, network info, and configure operational parameters.

📘 Learn how to configure the network correctly

7. Choose an Optimal Installation Location​

Select a location that ensures minimal signal interference and maximum visibility to the sky.

📍 Best practices for site selection

8. Mount the Scout Securely​

Physically install the Scout in your chosen location.
Use the mounting hardware provided or your own reliable outdoor mounting solution.

🔧 Follow the mounting instructions

9. Start Scanning for Drones!​

You're now ready to begin real-time detection of Remote ID signals.

If you use Scout in Cloud Mode, head over to the Dronetag App to monitor live activity from your Scout device.

💡 Need Help?

If you encounter issues at any step, consult our Troubleshooting Guide for solutions to common problems, or contact support for direct assistance.

What is the Right Location​

To get the most out of your Scout, location matters - a lot.

• Choose a suitable and elevated spot for installation.
• The receiver’s performance relies heavily on a clear, unobstructed view of its surroundings.
• A rooftop, ideally the highest one in the area, often proves to be the perfect vantage point for maximum signal coverage.

Factors Influencing Remote ID Signal Reception​

Signal reception isn’t just about hardware - it’s also about the environment. Several key factors can impact how well the Scout picks up Remote ID transmissions.

Ensuring Visual Line of Sight (VLOS)​

• Physical obstacles between the drone and the Scout - like buildings, trees, or terrain - can block or weaken signals.
• When possible, install the Scout in a spot with a clear view in the direction where drone activity is expected.

Signals in the 2.4 GHz and 5 GHz Frequency Bands​

• The Scout operates in frequency bands that are commonly shared with other technologies.
• Devices such as Wi-Fi routers, Bluetooth speakers, or even smart home hubs can cause interference.
• Keep the Scout as far away as possible from these types of devices.

Electromagnetic Noise​

• All electronics generate a certain amount of background noise, which can interfere with sensitive receivers like the Scout.
• Avoid installing the Scout near AC units, inverters, solar power stations, or other large electrical systems.

Transmission Power of the Drone’s Remote ID Signal​

• Not all drones are created equal - the power of the signal they transmit can vary greatly.
• This power level is defined by the drone manufacturer and local regulations, and while you can't control it, it's good to be aware that some drones may simply broadcast farther than others.

Choose the Right Location​

Before installing the Scout receiver, make sure you have the proper location and infrastructure ready. This will save you time and ensure optimal performance from the start.

What You’ll Need for Installation​

To install the Scout, make sure you have the following:

• A tall structure or mast/pole - the higher, the better.
  Ideally on the highest rooftop in the area, with a clear line of sight in all directions.
  The Scout cannot receive signals through buildings or large obstacles.

• A stable power source:

  • Either a standard indoor power outlet near the Ethernet cable entry point, or
  • A PoE (Power over Ethernet) injector if direct power access is not available.
    The Scout has a low power consumption (under 10 W), so both options are easy to accommodate.

• An outdoor-rated Ethernet cable (CAT5 or higher) with the ability to crimp RJ-45 connectors.

• Minimal radio interference: Avoid placing the Scout close to Wi-Fi transmitters or other antennas operating at 2.4 GHz or 5 GHz.

Recommended Conditions​

For best performance:

• Choose a high, unobstructed position — the higher, the larger the detection range.
• Avoid areas with dense urban obstacles, metallic surfaces, or sources of RF noise.
• Ensure the Scout has a clear line of sight toward open space — it will not detect signals behind walls or buildings.
• If you are unsure about the right location, contact our support.
  Send us the address of the intended installation site or photos from the rooftop view, and we’ll help you verify signal conditions using satellite data (e.g., Google Earth) and identify any potential interference sources.

Step-by-Step Guide​

Now that your location is ready, the power and network connection are prepared, and you’ve confirmed optimal conditions, follow these steps to mount and connect the Scout properly.
Carefully go through each step to ensure the best performance and long-term reliability of your installation.

Mount the Device​

• To ensure optimal performance, the receiver should be mounted on an elevated structure like an existing pole, bracket, or mast.
• If no such structure is available, a tripod can be used.

Mount the device to the desired place. Remember that the higher the place is, the better Scout will receive the Remote ID signal coming from the drones. While mounting the Scout, stick with the mounting manual and strictly follow the local regulations for electrical installation and surge and lightning protection.

1. Fix a Cross Bracket to Scout​

Fix the included cross bracket on the bottom of the enclosure with four (4) M6*12 bolts.

2. Mount the Pole Clamp​

Place two (2) pieces of the clamp around the pole and tighten them with the included M6*110 bolts, washers, and nuts.

3. Connect the pole clamp and Scout​

The pole clamp works for 45 – 110 mm diameter of pole and the cross bracket by securing the last piece of the mounting kit in place using M6*30 bolts, washers, and nuts.

caution

The Scout must be fixed so that antennas point perpendicular to the horizontal line.

Connect and Insulate the Cables​

6. Connect the Ethernet cable using the PoE injector​

After the PoE cable is connected, insulate it with the included PVC tape:

Insulate the Ethernet Cable Connector​

• Clean the surface area of the connector that will be wrapped. Wrap a layer of PVC tape with a 50% overlap according to the rotation direction of the connector. Continue wrapping the PVC tape to about 10 mm below the end of the connector.

• Wrap three additional layers with PVC tape with natural uncoiling force and a 50% overlap. Make sure to cover the head and the tail of the connector.

This guide explains how to install the directional antenna mount for Dronetag Scout.
Follow the steps carefully to ensure a secure installation and reliable antenna performance.

Antenna Connector Layout​

• Scout Baseline - 2x Omnidirectional Antennas

---

• Scout with 2x Omnidirectional Antennas + 1x Sector (Directional) Antenna

---

• Scout with 2x Omnidirectional Antennas + 2x Sector (Directional) Antennas

---

• Scout with 2x Omnidirectional Antennas + 3x Sector (Directional) Antennas

---

• Scout with 1x Omnidirectional Antenna + 4x Sector (Directional) Antennas

• Omnidirectional Antennas
• Holder for Four Directional Antennas
• Holder for Two Directional Antennas
• Directional Antennas with No Holder

Omnidirectional Antennas on Scout Baseline​

3D Model​

👉 View 3D model

Mount the 2.4 GHz Antenna​

Screw the antenna marked with the "1" sticker on its box to the connector marked with the same sticker

tip

In case you lost the sticker with the number or forgot what the number of the antenna was: the longer antenna has to be mounted on the left side of the device from the front view.

Mount the Dual-Band Antenna​

Screw the antenna marked with the "4" sticker on its box to the connector marked with the same sticker (the shorter antenna has to be mounted on the right side of the device from the front view)

tip

In case you lost the sticker with the number or forgot what the number of the antenna was: the shorter antenna has to be mounted on the right side of the device from the front view.

Correct Scout Orientation​

The Scout must be mounted perpendicular to the ground.
This ensures the omnidirectional antennas have a clean and even field of view.
If the unit is tilted, one side of the antennas points into the sky and the other into the ground, which reduces performance.

Insulate connectors​

• Cut off about 50 cm of waterproof tape. Stretch it to double the length. Wrap three layers around the connector with a 50% overlap. Hold the tape in place with your hand for a few seconds.

• Wrap three additional layers with PVC tape with natural uncoiling force and a 50% overlap. Make sure to cover the head and the tail of the connector.

To successfully change the SIM card and configure the APN, please follow these steps carefully. Adhere to this guide to ensure the process is completed correctly.

Step-by-Step Guide:​

1. Disconnect the Scout from the Ethernet connection (which also serves as the power source).

2. Unscrew all 12 bolts around the device perimeter.
   Use a screwdriver that fits the bolts correctly to avoid damage.

3. Carefully flip the device over.

4. Remove the cover and disconnect the micro-USB cable inside the device (1).

5. Gently slide the micro-SIM card into the connector (2) — do not press on it or attempt to open the connector.

6. Reconnect the micro-USB cable to the same connector it was disconnected from in step 4.

7. Verify Functionality:

There are two options to verify the SIM card functionality:

• If you use your Scout in Sensor Mode, connect the Scout to your local network and check its LTE status on the network management page.
• If you use your Scout in Cloud Mode, you can view the LTE status in the Dronetag App.

⚙️ LTE Configuration & Setup​

Further configuration of LTE connectivity and APN (if needed) is covered in our Networking Guide:

📘 SIM Card Installation and LTE Setup

✅ Verify LTE Functionality​

To confirm whether the Scout has connected to the mobile network, follow the instructions in the networking section:

🔍 Verify Functionality and LTE

8. Reassemble the Device:

After confirming the device is functioning correctly, reattach the cover, carefully flip the device over, and tighten the 12 bolts (refer back to Step 2).

caution

Pay special attention to assembling the device properly to prevent water ingress and avoid damaging the device.

Take extra care about the correct position of the sealing.

Custom SIM Card Requirements​

Dronetag Scout supports custom LTE SIM cards for independent connectivity. While the hardware is globally compatible, successful operation depends on your carrier’s plan and network policies.

Verified US Carriers​

The following networks have been successfully tested and verified:

• AT&T
• T-Mobile
• Verizon

Critical Connectivity Restrictions​

1. IMEI Whitelisting (Carrier Certification)​

• Some carriers (especially for tablet or hotspot-specific plans) enforce an IMEI lock.
• Dronetag Scout utilizes a Quectel modem that is not certified under specific carrier-proprietary programs (such as Verizon Open Development or AT&T IoT Certification).
• If your plan is restricted to "certified devices only," the carrier will reject the connection based on the Scout's IMEI.

Solution: Use a "Bring Your Own Device" (BYOD) plan or a generic data/IoT plan that does not enforce hardware whitelisting.

2. FirstNet Incompatibility​

• Dronetag Scout is not compatible with FirstNet SIM cards. The hardware does not support the specific bands or protocols required for this network.

3. Phone Plans vs. Data-Only Plans​

• Avoid using SIM cards from standard smartphone plans. Carriers often detect the modem and block data or throttle it under hotspot/tethering limits.

Solution: Use dedicated data-only, mobile broadband, or IoT/M2M plans.

Network & Performance Tips​

• LTE Only: Ensure your SIM supports 4G/LTE. SIM cards provisioned exclusively for 5G Standalone (SA) networks will not function in the Scout.
• Local vs. Roaming SIMs: Global/roaming SIMs (e.g., Hologram, Emnify) work but may introduce higher latency. For time-critical operations, a local carrier SIM is recommended.
• Coverage: Ensure your carrier provides LTE coverage in your area. Note that some carriers (like T-Mobile) use specific bands (e.g., B71) for rural coverage that may differ from standard phone reception.

Pre-Installation Checklist​

• Disable PIN: Use a smartphone to ensure the SIM card has no PIN code lock enabled.
• Verify Data: Confirm the SIM has an active data balance in another device.
• APN Settings: Obtain the correct APN (Access Point Name) from your provider. You will need to enter this in the Dronetag App during configuration.

Quick Troubleshooting​

If the Scout fails to connect despite a valid SIM:

• Contact your carrier to verify the plan isn't locked to a specific IMEI
• Request the carrier to switch your line to a "Generic/BYOD" data profile

The Dronetag Scout features a built-in HTTPS management interface, accessible over your local network on port 443.
This interface allows you to:

• Preview detected data
• Configure network and system settings
• Manage the device securely

To access the interface, you must first determine the Scout’s IP address on your network.

There are two ways to reach the Scout:

1. Through your network (DHCP) — the Scout obtains an address from your network's DHCP server and you discover it using an mDNS/Bonjour browser.
2. Directly with a static IP — no network or DHCP server is required; you connect a computer straight to the Scout and use its fallback address.

🔍 Finding the Scout on Your Network​

By default, the Scout is shipped with DHCP enabled. When powered and connected via Ethernet, the Scout will attempt to obtain an IP address automatically from your network's DHCP server.

If no DHCP server responds within 60 seconds, the Scout falls back to a static IP configuration — see Connecting Directly with a Static IP below. This fallback is temporary: the Scout keeps looking for a DHCP server and returns to a DHCP address automatically once one is available, so its address on your network may change from the fallback back to a DHCP-assigned one.

If you don’t know what IP address the Scout received from your DHCP server, use one of the following methods depending on your platform:

• Android
• iOS
• Windows
• macOS
• Linux

📱 Android – Bonjour Browser​

Download Bonjour Browser on Google Play

1. Install and open the app.
2. Locate Dronetag Scout in the list.
3. The IP address and hostname will be shown.

🖥️ Connecting Directly with a Static IP​

If there is no DHCP server available — for example during first setup on a desk, in an isolated field deployment, or while troubleshooting — you can connect your computer directly to the Scout with an Ethernet cable.

How the fallback address works​

If the Scout does not receive an IP address from a DHCP server within 60 seconds after powering up, it automatically falls back to a static IP configuration:

• IP Address: 192.168.100.100/24
• Default Gateway: 192.168.100.1

This fallback keeps the Scout reachable whenever there is no DHCP server. It is temporary: while on the fallback the Scout keeps checking for a DHCP server in the background and automatically switches back to a DHCP address as soon as one becomes available, so on a network with working DHCP it will not stay on 192.168.100.100. If you need the Scout to hold a fixed address permanently, set a static IP in the management interface instead — see the note at the end of this section.

The Scout is powered over the Ethernet cable (PoE), so a direct connection always goes through the PoE injector included with your unit: connect your computer to the injector's LAN / Data port and the Scout to the PoE / Power+Data port.

To communicate, both devices must be in the same subnet. The Scout's fallback address is fixed, and you configure your computer to match:

Setting a static IP on your computer​

ping 192.168.100.100

ping -c 3 192.168.100.100

# List connection names
nmcli connection show

# Set a static address on your wired connection
sudo nmcli connection modify "Wired connection 1" \
  ipv4.method manual ipv4.addresses 192.168.100.10/24

# Re-activate the connection
sudo nmcli connection up "Wired connection 1"

sudo ip addr add 192.168.100.10/24 dev eth0

ping -c 3 192.168.100.100

Open the management interface​

Once your computer's static IP is configured and the Scout has been powered on for at least 60 seconds, open your browser and navigate to:

https://192.168.100.100

🔐 Accessing the Interface​

Once you have the Scout's IP address:

1. Open a web browser.
2. Navigate to: https://<Scout-IP> (replace <Scout-IP> with the actual IP address, e.g., https://192.168.1.42).
3. Because the Scout uses a self-signed certificate, your browser will likely show a security warning.
   • Proceed by allowing the insecure connection. This may appear as "Advanced > Proceed to IP", depending on your browser.
4. Log in using the default credentials provided by Dronetag Support.

The Scout includes a login-protected management UI. The default username and password are printed on the sticker on the bottom part of each Scout.

🔧 Configuring a Trusted Certificate​

To avoid browser security warnings and enable a trusted HTTPS connection, you can configure the Scout with a certificate trusted by your system.

You can find certificate management options in the Configuration section of the interface.

Here, you can:

• Upload a certificate signed by your internal Certificate Authority (CA), or
• Generate a Certificate Signing Request (CSR) to obtain a signed certificate from your CA.

Once installed, the trusted certificate will replace the default self-signed one, ensuring seamless and secure access from trusted devices.

For a detailed description, please refer to the system configuration page.

🛠️ Troubleshooting Connectivity​

If you're unable to access the Scout’s interface, refer to the detailed network troubleshooting section.

The Dronetag Scout is equipped with a 100 Mbps Ethernet port that supports both DHCP and static IP address configurations. These settings can be modified through the device’s web-based management interface.

For instructions on accessing the interface, refer to the Connect to the Management Interface section.

🔌 Power over Ethernet (PoE)​

The Scout’s Ethernet port is designed to be powered via PoE (Power over Ethernet) using the following standards:

• IEEE 802.3af Type 1 (also known as PoE)
• IEEE 802.3at Type 2 (also known as PoE+)
• Voltage: 48V DC

To power the Scout correctly:

• Use a compatible PoE switch that supports 802.3af Type 1 or 802.3at Type 2, or
• Use the included PoE injector supplied with your unit.
  Refer to What’s in the Box for more details.

📥 DHCP and the Static IP Fallback​

By default the Scout's Ethernet is configured for DHCP, and it is designed to stay reachable even when no DHCP server is available:

1. On start-up the Scout requests an address over DHCP and waits up to 60 seconds for a response.
2. If a DHCP server answers, the Scout uses the address it is given — the normal case on a managed network.
3. If no DHCP server answers within 60 seconds, the Scout falls back to a fixed static IP so it always stays reachable for a direct connection:
   • IP Address: 192.168.100.100/24
   • Default Gateway: 192.168.100.1

Automatic return to DHCP​

The static address is only a fallback, not a permanent setting — its job is to keep the Scout reachable while the network is unavailable. The Scout therefore keeps retrying DHCP in order to re-establish normal connectivity as soon as it returns: while on the fallback it checks in the background, roughly every couple of minutes, whether a DHCP server has become available.

As soon as DHCP works again, the Scout automatically switches back to a DHCP-assigned address — it does not stay on the static fallback once the network recovers. These background checks do not interrupt the fallback address, so the Scout remains reachable at 192.168.100.100 the whole time, right up until it obtains a DHCP lease.

🔧 Configuring a Static IP Address​

To assign a static IP:

1. Navigate to the Networking tab within the web management interface.
2. Enter the desired static IP address using CIDR notation, for example:
   192.168.1.61/24
   • The /24 suffix corresponds to the subnet mask 255.255.255.0.

💡 Not sure what subnet mask to use? Try jodies.de IP Calculator to determine the correct value.

🌍 Setting Gateway and DNS​

If you need the Scout to send data to other networks or access internet services:

• Set the Default Gateway (usually your router's IP address).
• Optionally configure one or more DNS servers to enable domain name resolution instead of using raw IPs.

These settings are especially important if the Scout is connecting to cloud platforms or remote endpoints.

⏰ Time Synchronization (NTP)​

The Scout normally keeps its clock accurate automatically — it takes the time from the LTE network, GNSS, or the internet. You can add your own NTP server (by IP or hostname) in the NTP IP/host field of the Networking tab; it is added to the pool of time sources the Scout uses.

📶 SIM Card Installation and LTE Setup​

For LTE functionality, the Scout must be equipped with an LTE modem, which can be included when purchasing the unit.

You can also use your own SIM card—please refer to the SIM Card Installation Guide for detailed instructions.

If the LTE option does not appear in the Scout’s management UI, this means the device is not equipped with an LTE modem module.

APN (Access Point Name)​

Each SIM card provider supplies an APN, usually listed on their website. Enter it in the Desired APN field so the Scout can establish a mobile data connection.

The APN you set is applied on every start-up. If you change it and the new value fails to connect while the previous one was working, the Scout automatically reverts to the last working APN, so a typo won’t leave the device offline. You can also enter the APN for a new SIM before swapping cards, so the Scout comes up correctly with the new one already configured.

SIM PIN​

If the inserted SIM is protected by a PIN, the Networking tab shows a SIM PIN field. Enter the PIN and select Unlock SIM to bring the modem online. The Scout remembers a PIN that works and re-applies it automatically after a restart, so you only have to enter it once. PIN protection stays enabled on the card — it is only unlocked, never disabled.

Verify Functionality and LTE​

To verify LTE connectivity:

1. Connect to the Scout’s Management Interface
   Follow the instructions in Connect to the Management Interface to access the Scout’s web UI.

2. Open the Networking Tab
   Once logged in, navigate to the Networking section in the management interface.

3. Check the LTE (4G) Switch
   Confirm that the 4G switch is set to ON to enable LTE functionality.

4. Configure the APN
   If your cellular provider requires specific APN settings, enter the APN value into the designated field in the networking tab.

5. Save Changes
   Click the Update 4G connection button to save and apply your changes.

⚖️ Choosing between Ethernet and 4G​

When the Scout has both an Ethernet connection and a working 4G connection, it normally sends its internet traffic — the Dronetag cloud, AWS instances and other remote integration servers — over Ethernet, keeping 4G as a backup. Traffic to devices on your local network always stays on Ethernet and is never sent over 4G.

Two switches in the 4G section of the Networking tab let you change this behaviour.

Prioritize 4G​

Turn Prioritize 4G on to make the Scout prefer the 4G connection for all internet traffic, even while Ethernet is connected. This is useful when the Ethernet network is used only for local access and does not provide reliable internet. Traffic to your local network still goes out over Ethernet as usual. This switch is off by default.

Automatic 4G failover​

Automatic 4G failover lets the Scout switch to 4G on its own, and is on by default. Roughly once a minute the Scout checks whether the remote servers your integrations rely on can still be reached over Ethernet:

• If they can be reached over Ethernet, the Scout keeps using Ethernet.
• If they cannot be reached over Ethernet but are reachable over 4G, the Scout automatically switches its internet traffic to 4G.
• As soon as the Ethernet connection can reach those servers again, the Scout switches back to Ethernet.

A few things to keep in mind:

• The check only runs while 4G is enabled and connected.
• Servers on your local network are ignored — failover reacts only to a loss of internet connectivity, not to local traffic.
• If Prioritize 4G is on, that manual choice always wins and the connection stays on 4G.

In a typical installation you can leave both switches at their defaults: the Scout uses Ethernet whenever it provides working internet access and falls back to 4G only when it doesn’t.

🔒 VPN Access​

The Scout can be configured to use a VPN (Virtual Private Network) to provide access to the device even when you are not directly connected to its Ethernet port. This is useful when the Scout is deployed in a remote network and needs to be reached securely for maintenance, diagnostics, or integration with other services.

Using a VPN also helps securely transfer data by adding another layer of privacy between the Scout and the systems communicating with it.

WireGuard​

Scout currently supports WireGuard configuration from the management interface. A WireGuard configuration can be uploaded to the Scout and then enabled or disabled from the VPN section in the Networking page.

WireGuard can be used to:

• reach the Scout remotely without direct local Ethernet access
• route traffic securely to resources available inside the VPN network
• add an additional privacy layer for communication between the Scout and your remote infrastructure

When preparing a WireGuard configuration for Scout:

• configure the client tunnel address in the [Interface] section
• configure the reachable VPN subnet in [Peer] AllowedIPs
• do not use 0.0.0.0/0 in AllowedIPs; this value is explicitly forbidden by Scout

Current implementation limitations:

• AllowedIPs must be present in the [Peer] section
• only one IPv4 network in AllowedIPs is currently supported, optionally together with the Scout address itself as /32
• the Scout currently expects the [Interface] Address to be inside the AllowedIPs subnet
• 0.0.0.0/0 is explicitly blocked and full-tunnel VPN routing is not supported in the current implementation
• if additional routes are needed beyond the main VPN subnet, they are not yet supported by the current UI flow

Example of a valid Scout WireGuard configuration:

# File must be named wg0.conf
[Interface]
# Private key assigned to this Scout client
PrivateKey = <scout-private-key>
# Tunnel address of this Scout inside the VPN subnet
Address = 192.168.205.85/32
# Optional DNS server reachable through the VPN
DNS = 192.168.205.1

[Peer]
# Public key of the remote WireGuard server or peer
PublicKey = <server-public-key>
# Scout supports one IPv4 VPN subnet here, optionally with the Scout address itself
AllowedIPs = 192.168.205.0/24, 192.168.205.85/32
# Remote server endpoint
Endpoint = 94.230.157.236:51821

In this example:

• the Scout tunnel address 192.168.205.85/32 belongs to the allowed VPN subnet 192.168.205.0/24
• the Scout address itself is also explicitly listed in AllowedIPs, which is allowed
• traffic for the VPN subnet is routed through WireGuard
• default routing for all device traffic is not used

🛠️ Troubleshooting Connectivity​

If you're unable to access the Scout’s interface, try the following steps to identify and resolve common issues:

✅ Double-Check Network Settings​

• Ensure your computer is on the same subnet as the Scout.
• If your network uses DHCP, confirm the DHCP server is running and has available IP addresses.
• If DHCP is not available, verify that your computer is manually configured to access the Scout’s fallback static IP (192.168.100.100/24).
  • Example manual IP for your computer: 192.168.100.10

🔌 Check Ethernet Link LEDs​

Inspect the Ethernet port on your router/switch and if you have the device opened you can check these on the Scout mini computer:

• Green LED: Indicates a successful physical link.
• Amber/Yellow LED: Indicates network activity (blinks when data is being transferred).
• No lights: The cable may be faulty, the port may be disabled, or there may be no physical connection.

⚙️ Configure Ethernet Speed and Duplex​

Some switches or routers may experience auto-negotiation issues with the Scout. To resolve this, manually set the Ethernet port configuration in your switch or router's management interface to:

• Speed: 100 Mbps
• Duplex: Full duplex

This setting can often be found under port settings or advanced configuration in your network equipment's UI.

🔄 Reset the Scout to Factory Defaults​

If you've made changes to the network configuration and can no longer access the device:

• Perform a factory reset to restore default settings.
• After resetting, the Scout will attempt to obtain an IP address via DHCP and fall back to its static IP (192.168.100.100) if no DHCP server is available.

Refer to the Factory Reset Instructions for detailed steps.

Integrations control where and how the Scout sends telemetries. Scout can run multiple Forwarders in parallel. If any instance is not processing the data fast enough, other instances are not affected.

There are two basic forwarders:

• Dronetag forwarders (one for Cloud and one for On-Premise) that can be only enabled/disabled and very basically configured
• JSON forwarders are versatile and intended for user's integration.

See the data format description at the bottom of this page.

Dronetag Forwarders​

Dronetag Cloud is the only (user-visible) permanent forwarder. It cannot be deleted but can be disabled. By disabling the cloud forwarder, you will not be able to see the Scout nor its detections in Dronetag App.

You can add an On-Premise Dronetag integration to have full control of your data with all benefits of our cloud backend.

The Dronetag Forwarder can be used simultaneously with any other forwarders. For further details on how to operate the Scout in Cloud/On-Premise, please refer to this page.

JSON Forwarders​

JSON forwarders are intended for user integration.

All custom forwarders can be secured and support compression and batching.

• MQTT
• HTTP/HTTPS

It is better to specify port into URL, otherwise 1883 is used. For plain MQTT(s) protocol, only host:port is necessary. If you are going to use WebSockets then you can specify path as well, otherwise / will be used.

• MQTT over WebSockets: Connect to MQTT broker using WebSockets instead of native MQTT protocol. Useful when you can only use HTTP/WebSocket connections (e.g., behind restrictive firewalls).
• Drones Topic: MQTT topic for drone detections. Topics are like directories in a filesystem. Template: use {sn} for full serial or {sn4} for last 4 digits. Example: myorg/receivers/scout1/drones
• Aviation Topic: Separate MQTT topic for aviation data. If empty, aviation data is sent to the Drones Topic.
• Status Topic: Separate MQTT topic for Scout status/heartbeat. If empty, status is sent to the Drones Topic.

Here follow common options no matter the basic protocol (HTTP/MQTT).

Basic Settings​

These are the fundamental options required for every forwarder:

• Enabled: Turn this forwarder on or off. When disabled, no data is sent through this forwarder.
• URL: The destination where to send the data. Please, do not try to guess protocol - use clickable options to enable secured connection, mTLS and/or change the protocol to web sockets.
• Sources: Select which types of data to forward: drones (detected drone telemetry), aviation (manned aircraft data from aviation module), status (Scout health and position updates). Please note that drones and aviation are restricted by a global filter on altitude and radius.
• Client Timeout: How long (in seconds) to wait for the server to respond before considering the connection broken. Default is 15 seconds. Increase this if your connection is not reliable or slow.

Batching​

Batching groups multiple messages before sending them. This reduces network traffic and server load but adds slight delay. Here you control those delays and how the data are formatted.

• Enable Batching: Turn message batching on or off. Useful for high-volume scenarios.
• Batch as JSON Array: When enabled, messages are grouped as [msg1, msg2, ...]. When disabled, messages are joined with a separator.
• Items Separator: Character(s) between messages when batching is enabled: nothing (no separator), \r\n (carriage return + newline), or \n (newline).
• Batch Size: Maximum number of messages to group before sending. Leave at 0 to disable, or set to a number like 100.
• Batch Timeout: Maximum seconds to wait before sending a batch, even if it's not full. Example: 0.1 sends batches every 100ms. Disabled if set to 0.

Example: With Batch Size = 100 and Timeout = 0.1 seconds, batches are sent when either 100 messages arrive OR 0.1 seconds pass, whichever happens first.

Compression​

• Compression: Reduce bandwidth usage by compressing data before sending. Beware that for HTTP the data is optionally compressed only when it makes sense. The compression is then noted in Content-Encoding header (with value "gzip"). If selected for MQTT, the data are compressed always because there is no way how to hint on data compression.

Security Settings​

Configure how the Scout securely communicates with your server.

TLS/SSL Server Encryption​

This section relates only to verification of the server certificate. This is the most common part of security and you most likely need to get this right.

• Secured: Enable TLS encryption for the connection. If your server uses HTTPS or MQTTs, enable this.
• Verify Server Cert: Check if the server's certificate is valid and not expired. Disable only for testing with self-signed certificates. Warning: Disabling this makes you vulnerable to man-in-the-middle attacks.
• Verify Server Domain/IP: Check if the certificate's hostname (CN field) matches the server you're connecting to. Enable this to prevent connection to impostor servers.
• Server CA Certificate: Your custom CA certificate in PEM format (.pem or .crt file). This tells the Scout which certificate authority to trust. Typically needed when your organization has its own internal CA. Beware that it has to be the top-level CA in the server's certificate. Not an intermediate one.

Client Certificates​

This section allows you to specify your client certificates for mTLS. Quite usual in the MQTT world but more and more in HTTP also.

• Client Certificate: Upload a certificate to authenticate the Scout to your server. Required if your server checks client certificates (mutual TLS). File format: PEM.
• Client Private Key: The private key corresponding to your client certificate. Only needed if your key isn't embedded in the certificate file.
• Client Key Password: If your private key is encrypted, enter the password here.

Authentication Settings​

For servers that require login credentials:

• Username: Username for HTTP Basic Auth or MQTT authentication. Leave empty if using token-based authentication.
• Password/Token: Password for Basic Auth or API token. Stored securely. For MQTT, this can be your password or token depending on your broker's configuration.

Sensors Range and Altitude Limiting​

You can select thresholds for drones and aviation data:

• ignore thresholds (radius, altitude): object farther OR higher than the limits will be silently dropped
• tracking thresholds (radius, altitude): objects closer AND lower than the limits will be tracked

Tracking means that the messages will not be rate limited. Every message will be forwarded. Rate-limiting means that only one message per (configurable) X seconds per object will be sent. Good limits are especially useful for aviation where average data consumption near a mid-sized airport with no limits is around 150MB/day.

Default limits​

By default, rate limiting and ignore is turned off for drones by setting all values to 0.

Aviation is limited by default because the air traffic visibility is on long distances that are not useful for normal operations. Hence the aviation traffic is ignored if further away than 100km regardless of altitude (ignore threshold). Aviation tracking (not rate-limited) happens by default for any traffic within 10km radius and bellow 1000m of altitude (landing objects).

Formats​

All JSON-based forwarders support two formats: dri and odid. DRI format contains raw OpenDroneID message (as bytes) as it was received by the antenna. ODID message is parsed and transformed OpenDroneID message so it is more pleasant to work with.

Each message is sent separately unless Batching is configured. See above details about batching messages.

{
    "sn": "D11234567812345678",
    "mac": "ab:ab:bc:bc:de:de",
    "counter": 24,
    "rssi": -83,
    "tech": "B4",
    "recv_id": 0,
    "module_id": 0,
    "module_type": 10,
    "msg_type": 1,
    "noise_floor": null,
    "registration": {
        "maker": "Dronetag",
        "model": "Beacon gen.2",
        "type": "rid_module",
        "certain": true
    },
    "odid": {
        "BasicID": [
            {
                "UAType": 15,
                "IDType": 1,
                "UASID": "159112345678"
            }
        ],
        "Location": {
            "Status": 2,
            "Direction": 202.0,
            "SpeedHorizontal": 16.5,
            "SpeedVertical": 0.0,
            "Latitude": 50.0835017,
            "Longitude": 14.4328954,
            "AltitudeBaro": 95.0,
            "AltitudeGeo": 0.0,
            "HeightType": 1,
            "Height": 163.0,
            "HorizAccuracy": 0,
            "VertAccuracy": 0,
            "BaroAccuracy": 0,
            "SpeedAccuracy": 0,
            "TSAccuracy": 0,
            "Timestamp": "2026-06-01T09:49:11",
            "TimestampEstimated": false
        },
        "SelfID": null,
        "System": null,
        "OperatorID": {
            "OperatorIdType": 0,
            "OperatorId": "d6lE0m0Hi2iNx"
        }
    }
}

{
    "odid_payload": {
        "counter": 25,
        "standard": "ODID_STANDARD_ASTM",
        "bluetooth_legacy_info": {
            "mac": "q6u8vN7e",
            "rssi": -116
        },
        "encoded_message": "8hkDAh8xNTkxMTIzNDU2NzgAAAAAAAAAAAAAABImF0IAax3aHVxFmgguC28KsAcAAEyBAABSAEg1dFFzdEdNSFA5WTcAAAAAAAAAAAAA"
    },
    "receiver_data": {
        "timestamp": 1708485109
    },
    "sn": "D11234567812345678"
}

Heartbeat/Status​

If you select status source for your forwarder, you will receive a status message every 60 s These messages contain:

• Basic device information
• GNSS position (when GNSS is enabled)
• LTE network status (when an LTE modem is present)
• Sensors details

Example Heartbeat message:

{
    "sn": "D11234567812345678",
    "timestamp": 1780310741,
    "receivers": 2,
    "last_observation": 1780310741,
    "gnss_available": true,
    "gnss_position": [
        50.073992633,
        14.466609883
    ],
    "gnss_satellites": 6,
    "gnss_altitude": 262.5,
    "gsm": {
        "enabled": true,
        "state": "connected",
        "quality": 100,
        "tech": "lte"
    },
    "sensors": [
        {
            "id": "RW1",
            "uid": 2,
            "source": "wifi/dri_wlp1s0u1u2",
            "state": "ok",
            "timestamp": 1780310741.7995672,
            "tech": "RemoteID",
            "messages": 0,
            "filtered": 0,
            "last_message_at": 0,
            "last_status_at": 0,
            "extras": {
                "module_type": 10,
                "module_type_name": "RW1",
                "module_revision": 0
            }
        },
        {
            "id": "ADS-B",
            "uid": 18873,
            "source": "18873",
            "state": "ok",
            "timestamp": 1780310741.7998254,
            "tech": "ADS-B",
            "messages": 32588,
            "filtered": 32588,
            "last_message_at": 1780310741,
            "last_status_at": 0,
            "extras": {
                "export_running": false,
                "export_size": 0
            }
        }
    ]
}

Downloads​

Scout Sensor Format Specification (v2.5)

JSON+ODID schema (v1.0)

SCOUT datasheet (v2.4, superseded by the Format Specification)

Sensor+ offers advanced integrations with third-party servers.

• TAK
• Sapient
• FlytBase
• SafeSky
• BEAST
• ADSBExchange
• OGN
• DJI O4 Ground Station
• Skydio

TAK (Tactical Awareness Kit)​

TAK offers unsecured and secured communication. Secured communication uses certificates that come in three possible ways to the Scout client

• as separate PEM files (one for CA - the server certificate, one for client certificate, and one for client's private key);
• as P12 bundle - this file contains all three mentioned PEM files bundled together;
• from enrollment process (will be described later)

note

If your Scout runs in Cloud Mode, you don't need this integration to get drone tracks into TAK - the Dronetag cloud can stream them to your TAK server for you over the integration portal. Use that route whenever you don't need the direct data flow from the Scout itself; the Sensor+ integration described here is what you want when the Scout must reach the TAK server on its own, without any cloud in the path. See Using Scout with the Dronetag App for a video walkthrough of the cloud route.

Basic settings​

URL: specify host (e.g. tak.example.com) or IP (e.g. 10.1.1.25). If your server uses standard ports (8088 unsecured, 8089 secured) then you don't need to specify the port. If you want to use unsecured UDP version, use "Force UDP" switch.

SOURCES: you should keep drones and status messages. The only meaningful change is (un)checking aviation if you don't want to see surrounding airplanes in your TAK.

Force UDP: if your server supports only UDP protocol then check this option. UDP cannot be secured nor verified ( connection failure will never be reported).

Security settings​

The suggested setup is to have all security features enabled (security, verify server cert, verify server domain). This will ensure server certificate is enforced and thoroughly checked. If the server certificate doesn't have its domain/IP correctly filled in, then you can disable the domain/IP check to accept even such certificate and keep your comms secured. In this case, either your server needs to use globally recognized CA such as Let's Encrypt or you need to supply your CA's certificate into the first field "Server CA Certificate" in PEM format. There is the option to use p12 bundle with "P12 Trust Bundled RootCA" that will take CA certificate from the last certificate from the bundle.

CERTIFICATE VERIFY FAILED​

The image on the right shows the error when Scout cannot verify server's certificate. Please note that the CA certificate must be server's root CA. It cannot be an intermediate CA. You have a few solutions

1. If you are using p12 bundle and the server's certificate has the same RootCA as the certificate in the bundle then use "P12 Trust Bundled RootCA". This will extract the top-level certificate from the p12 bundle and use it as trusted certificate for verifying the server.
2. If you are using p12 bundle (and have "P12 Trust Bundled RootCA" to "No") or not using the p12 at all - in both cases the "Server CA Certificate" will be used if you have checked "Verify Server Cert". Make sure it is the top-level rootCA.
3. As a temporary fix, you can uncheck "Verify Server Cert" and "Verify Server Domain/IP" in case of problems and the client will simply accept any certificate that the server gives you. This is not secure at all of course.

Client Certificates​

For secured communication from client to server, you must specify "Client Certificate" and "Client Key" either as separate PEM files or in a P12 bundle. If you upload both PEM and P12, only the P12 will be used. Optionally, PEM Key can be password protected. In this case use the "Client Key Password" field. Keys in P12 must not be password protected. Usually the bundle itself is protected hence the field "P12 Bundle Password".

If any of those displayed errors appear, that means your client certificates were rejected by the server or are outright invalid.

• [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error
• [SSL: TLSV13_ALERT_CERTIFICATE_REQUIRED] tlsv13 alert certificate required

ENROLLMENT​

If you don't have certificates but you were given username, password and optionally a passphrase then you should use those in the authentication section together with setting Enroll to "yes". Those credentials are used in standard enrollment process using Marti API on port 8446. We currently do not support custom certificates for secured communication during enrollment but it will be part of the next release. If your enrollment server is running at a different port or even URL, then use the provided Enrollment URL.

TAK Settings​

Friendlies: here you can define friendly drones one-per-line by their serial number or MAC address in standard colon-delimited format. You can optionally add callsign under which they will appear on the map. Separate the callsign by a comma. Example:

1596F319B877381F1BBF, blue1
1596F33DEC76E5C15FD3

TAK Data​

Scout sends the following messages to the server:

Heartbeat​

Scout is sending a heartbeat every 60s as a friendly ground sensor a-f-G-E-S instead of usual t-x-d-d. This will place Scout on the map with callsign "SCOUT-<last-4-digits-of-serial-number>" while the uid of those messages is "<serial-number>-sensor".

Drones​

Scout by default marks drones as Unknown affiliation. If the drone's serial number or MAC address were specified in the friendly settings, then they will be marked as Friend. Scout also distinguishes between fixed-wing and rotary drones. So the possible COT types reaching the server are one of

• a-u-A-C-F-q resp. a-f-A-C-F-q for unknown fixed-wing drone resp. friendly one
• a-u-A-C-H-q resp. a-f-A-C-H-q for unknown rotary drone resp. friendly one

Drone's callsign is [UA]snxxxx where snxxxx is the last 6 digits of the drone's serial number. If the serial number is not available then drone's MAC address is used instead (will have ":" inside).

Drone Operator​

Operator is visually linked to their drone by their callsign [OP]snxxxx that shares the drone's serial number. Operator is also linked to their drone on COT level by the link_to element. Operator's COT type is a simple ground unit a-u-G-U resp. a-f-G-U if the operator's drone is defined as friendly.

Example​

A single Remote ID detection produces up to two CoT events: the UAV track (from the drone's broadcast location) and a separate operator marker (from the drone's broadcast system message). The operator event references the drone via its <link> element, so the two appear connected on the map. Below is a real event pair emitted by a Scout with serial D19D2405DD799BF9B5 for a rotary drone broadcasting UAS ID MJJE3G894BIQV0Z:

<event version="2.0" type="a-u-A-C-H-q" uid="D19D2405DD799BF9B5-UAS-MJJE3G894BIQV0Z" how="m-g" time="2026-07-23T05:10:57.263681Z" start="2026-07-23T05:10:57.263717Z" stale="2026-07-23T05:11:27.263725Z">
  <point lat="-48.8766700" lon="-123.3933300" le="3.0" hae="403.0" ce="10.0"/>
  <detail>
    <_flow-tags_ pytak-scout="2026-07-23T05:10:57.263739Z"/>
    <contact callsign="[UA]BIQV0Z"/>
    <track track="86.0" speed="0.0"/>
  </detail>
</event>

<event version="2.0" type="a-u-G-U" uid="D19D2405DD799BF9B5-OP-MJJE3G894BIQV0Z" how="m-g" time="2026-07-23T05:10:57.264431Z" start="2026-07-23T05:10:57.264448Z" stale="2026-07-23T05:12:57.264454Z">
  <point lat="-48.8766192" lon="-123.3933311" le="10.0" hae="405.5" ce="5.0"/>
  <detail>
    <_flow-tags_ pytak-scout="2026-07-23T05:10:57.264468Z"/>
    <contact callsign="[OP]BIQV0Z"/>
    <link relation="p-p" type="a-u-A-C-H-q" uid="D19D2405DD799BF9B5-UAS-MJJE3G894BIQV0Z"/>
  </detail>
</event>

Aviation​

If your Scout has aviation modules and you enable aviation to be sent to the TAK integration the airplanes will appear as civilian fixed-wings a-u-A-C-F resp. helicopters a-u-A-C-H. In the UI, you should see their reported flight number (e.g. EJU39FN). If the flight number is not available then ICAO ID is used (which is a number).

The Dronetag Scout is equipped with a GNSS receiver that enables:

• Visibility on the map within our application
• Time synchronization using the GNSS signal
• Transmission of position data to the server via the network

Privacy Control​

All Scouts are delivered with GNSS location enabled by default. However, you can disable GNSS location or enter the location coordinates manually. Turning off GNSS will prevent leaking Scout's location over the network. It will not be visible in Heartbeat/Status messages nor in data. Disabling GNSS will not affect Scout's ability to correct its time using the embedded GNSS module.

Setting GNSS Location and Altitude Manually​

To set the GNSS position manually, follow these steps:

1. Connect to the Scout’s Management Interface Follow the instructions in Connect to the Management Interface to access the Scout’s web UI.

2. Navigate to the GNSS Section Go to the System tab and scroll down to the GNSS section. The GNSS position toggle controls sending the positioning information over the network.

3. Enter Coordinates Fill in the desired latitude and longitude coordinates into the GNSS position field. If empty, the receiver is using the internal GNSS Unit to determine its current position.

4. Enter Altitude (optional) Fill in the desired altitude in meters into the GNSS altitude field. If empty, the altitude measured by the internal GNSS Unit is used.

5. Save Your Changes Click the Update GNSS button to save the manual location.

Changing the Username and Password​

To enhance your Scout's security, it is highly recommended to change the default login credentials.

1. Access the Management Interface
   Navigate to the Scout’s management UI and go to the System tab.

2. Authenticate with Current Password
   You will need to enter the current password to authorize changes.

   • The unit itself has a label with the default password on the bottom of the device's body, in case the packaging is lost.
   • If necessary, you can perform the reset to factory defaults, which resets the password as well.

3. Set a New Password
   Enter your new password twice to prevent typographical errors.

4. Save the Changes
   Click the Update Password button to apply the new credentials.

🔧 Configuring a Trusted Certificate​

To avoid browser security warnings and enable a trusted HTTPS connection, you can configure the Scout with a certificate trusted by your system. You can manage certificates directly from the Configuration section of the Scout’s web interface. It provides the following options:

• Add Certificate (CA Upload):
  Upload a Certificate Authority (CA) certificate that will be added to the Scout’s internal trust store.
  This is useful if your organization uses a private CA and you'd like to trust client certificates issued by it.

• Upload HTTPS Certificate and Private Key:
  Use this to replace the default self-signed certificate with a certificate signed by your CA.
  This will allow the Scout’s interface to be accessed via HTTPS without browser warnings, assuming the certificate is trusted by your local system.

🔄 Automatic Fallback to Self-Signed Certificate​

If the uploaded HTTPS certificate becomes invalid or expires, the Scout will automatically regenerate a self-signed certificate.
This ensures that the device remains accessible via HTTPS, even if the trusted certificate can no longer be used.

📡 Status Reporting (Heartbeat)​

The Scout periodically sends a status message (heartbeat) describing its overall health: the number and state of its sensor modules, the time of the last detection, GNSS availability and position, and LTE modem state and signal quality.

The same status message feeds every connected service that subscribes to the status message source:

• Dronetag Cloud — keeps the sensor shown as online in the Drone Scanner app and the Dronetag Cloud.
• Advanced integrations that support status, such as TAK (the marker of the Scout itself), Sapient (sensor status reports), or Skydio (Marker for this Scout). See the Sensor+ configuration page for details on each integration.

⚙️ Configuring the Reporting Rate​

You can adjust the reporting behavior in the System tab under Status Reporting:

• Fast reporting after start (enabled by default): right after start-up (or after a configuration change), status is first sent every 10 seconds and the rate gradually slows down until it reaches the interval below. This makes the Scout appear online promptly after installation or reboot while keeping the steady-state traffic low.
• Send every (default 60 s): the steady-state interval between status messages.

When Fast reporting after start is disabled, the configured interval is used from the very first message.

🛠️ System Maintenance Services​

Both of the following services operate only when the Scout is connected to our servers that handle these functions. They communicate securely via standard HTTPS connections, using asymmetric cryptography to ensure privacy and security. These services are accessible only by our team.

Dronetag Update Service​

This service automatically updates the Scout whenever a new firmware release is available. It helps you to stay up to date with the latest features, improvements, and security patches we develop.

For more details about the automatic updates and how to perform manual firmware updates when the Dronetag Update service is off or no internet connection is available, please refer to the Firmware Update page.

Remote Troubleshooting Service​

This service enables our support team to remotely connect to your Scout to help diagnose and resolve any issues you encounter. If users experience difficulty accessing the Scout's Ethernet port, remote troubleshooting via the 4G network connection can be utilized.

Control and Availability​

Both services can be enabled or disabled according to your preference. We recommend disabling the Remote Troubleshooting Service once the Scout has been installed, since most of the troubleshooting requests come during the Scout installation period.

Statistics​

The Scout can send statistics to Dronetag. These are system statistics and reception-quality metrics — mainly signal sensitivities and background noise — together with the system's internal health indicators. They are indispensable for debugging poor reception performance.

Statistics contain no drone positions and not the sensor's own position, and no passwords or textual settings are transmitted.

Diagnostics​

Send diagnostics to Dronetag is opt-in error tracking. When one of the services experiences an issue or error, the relevant information is sent to Dronetag to help diagnose it. A report includes the error details, partial logs, and this device's serial number.

🔄 System Factory Reset​

To restore your Scout device to its original factory settings, follow the instructions below.

This procedure will erase all local configuration, including network settings, APN, data privacy preferences, the password credentials (if updated), and custom changes.

ℹ️ Cloud registration is not erased — your Scout will remain linked to your Dronetag Cloud account.

🛠️ Reset Instructions​

1. Locate the GPIO pins labeled Factory Reset (GPIO 21) and GND on the Mini Computer board.
   These two pins are directly next to each other.

2. Connect the two pins using a jumper or a small conductive wire.

3. While the pins are connected, power on the Scout using the PoE injector.

4. Keep the pins connected and wait approximately 1 minute.

5. After the reset completes, remove the jumper and reboot the device if necessary.

6. To begin fresh setup after reset, see: 🔗 Scout Connection & Initial Configuration Guide

Dronetag Scout devices require valid licensing to ensure compliance with software usage terms and to unlock specific features. Licensing helps us provide ongoing updates, support, and new functionalities while ensuring proper usage across different deployment modes.

Licensing Requirements​

• Scout EVK: A license is always required to operate the device.
• Scout Sensor Mode: No license is required for basic Sensor Mode.
• Scout Sensor+ Mode: A license is required for Sensor+ mode, which provides additional features.
• Scout Cloud Mode: Requires a software license managed by our servers, not by the Scout device itself. This license is automatically handled and renewed on our side.

Checking Your License Status​

1. Access the Scout’s Management Page.
   For detailed instructions on accessing the Management Interface, please refer to the Connecting to the Scout page.

2. Navigate to the License tab to view license details, including the expiration date.

Purchasing a License​

To obtain a new license:

1. Contact our support team at support@dronetag.com.

2. Provide your Scout’s serial number and specify the desired license validity period to help expedite your request.

Uploading a New License​

Once you have received your license file via email:

1. Download the license file to your computer.

2. Access the Scout’s Management Page.
   For detailed instructions, see the Connecting to the Scout page.

3. Navigate to the License tab.

4. Click Upload New License and select the license file.

5. Confirm to activate the new license.

Licensing Summary​

If you have any questions or need assistance with licensing, please contact support@dronetag.com.

You can monitor the current firmware version of your Scout in the Management UI. For details on accessing the Management Interface, please refer to the Connecting to the Scout page.

Keeping your Scout's firmware up to date is essential to ensure your device runs smoothly and securely. Firmware updates often include important security patches, bug fixes, and new features that enhance performance and functionality.

Checking your firmware version regularly helps you stay informed about your device’s status. In the near future, this page will also include a detailed changelog documenting the latest features and improvements.

🔄 Automatic Firmware Updates​

The firmware update process depends on the mode you are using and your device generation.

Firmware Updates in Sensor+ and Cloud Mode​

When using your Scout in Cloud Mode, firmware updates are handled automatically by the Dronetag Update service.

This service must be enabled for automatic updates to apply. You can manage this in the System Maintenance Services section.

Your device will always run the latest firmware version as soon as it’s released.

Choosing When Updates Happen​

Automatic updates are driven by the Dronetag Update service on the System tab, and you can control when the Scout checks for and applies them:

• Continuous (default) — with the Dronetag Update toggle on, the Scout checks for new firmware regularly and installs updates as soon as they are released.
• Scheduled — turn on Dronetag Update Schedule to restrict update checks to specific days of the week and a time of day. Continuous checking is turned off and the Scout only checks — and installs, if an update is available — at the times you choose. This is useful for keeping updates, and the reboot they trigger, inside a maintenance window.

The Dronetag Update service stays enabled while a schedule is active — the update service must keep running to perform the scheduled checks. Leaving no weekday selected means the check runs every day at the chosen time.

💾 Manual Firmware Updates for Scout​

Manual firmware updates are performed from the Firmware Update page of the Management UI:

1. Access the Management Page for your device.
2. Navigate to the firmware update page at http://<Scout-IP>/update (replace <Scout-IP> with your device’s IP).

The page offers two ways of updating:

• 🗘 Check Online — the Scout checks Dronetag servers for newer firmware and downloads and installs it on request. The Scout needs internet access for this.
• Offline update — you upload a firmware bundle (a .local file provided by us) from your computer. This works even when the Scout itself has no internet access.

After a successful installation, the device reboots automatically.

🔎 Checking for Updates Online​

1. Click the 🗘 Check Online button. The page shows the Installed and the Latest available firmware versions.
2. If a newer firmware is available, an Update available badge appears and the button changes to ⬇ Download Update. Click it to download the update — a progress bar tracks the download.
3. When the download finishes, the button changes to ▶ Apply Update. Click it to install the update. The installation log is streamed to the page.
4. When the installation finishes, the device reboots automatically.

📤 Offline Update (Uploading a Firmware Bundle)​

1. Download the update bundle (.local file) — the packages and the changelog can be found on the Firmware Changelog page.
2. In the Offline update row, click Choose File and select the downloaded .local file. The upload starts immediately after the file is selected.
3. The upload progress and the installation log are streamed to the page.
4. When the installation finishes, the device reboots automatically.

🔁 Automatic Reboot After the Update​

Once the new firmware is installed (via either method), the Scout reboots automatically. The page dims and shows “Rebooting device…” while it waits for the device to come back online. You don’t need to do anything — the page detects the device again by itself.

When the device is back online, the page shows “Update installed — verifying system”. The Scout then verifies the new firmware for several minutes and finalizes the update.

⚠️ Updating Scout EVK (Evaluation Kit)​

For Scout EVK, firmware updates are applied automatically:

1. Connect the Scout EVK to a network with internet access.
2. Keep the device powered on for at least 1 hour.
3. The management software will automatically download and install the latest firmware.

If you have any questions or run into issues during the update process, please contact our support team at support@dronetag.com.

Following is a detailed list of changes to the Dronetag Scout firmware.

Please note that the changelog is very technical and can be hard to understand for non-technical users. You can use this changelog to check if a specific issue you are experiencing has been fixed in a newer firmware version, or to see what new small features are available.

If you find this information confusing, we recommend you check our What's new page instead, where we try to introduce the most important changes and features to all of our products.

This guide walks you through using your Dronetag Scout device with the Dronetag app.

The application requires version v2.126.1 or higher.

The Dronetag App is available on multiple platforms, offering a seamless experience whether you use it on the web or on your mobile or tablet device. While the web version might be the most comfortable for some tasks, all features are fully accessible on mobile and tablets as well.

Registering Your Scout​

Before getting started, make sure you have a Dronetag account. You can sign up for free at dronetag.app.

To view your Scout’s data in the app, you’ll need to register the device to your account. Follow these steps:

1. Navigate to the My Devices page.
2. Click the Register new button in the top-right corner.
3. Enter your Scout’s serial number.

To verify if your device is already registered, head to the My Devices page and check if your Scout appears on the list.

Setting Your Data Privacy​

Before you start using the app, take a moment to review your data visibility settings.

Go to your profile page and click on Cloud Data Visibility. This setting determines whether your drone data is visible to the public or kept private.

Checking the Status of Your Scout​

To check the status of your Scout in real-time:

1. Navigate to the My Devices page.
2. Select the device you want to check.

On this screen, you will be able to see a basic overview of its status, including:

• Online/offline status
• LTE - signal strength (if installed)
• GNSS - number of satellites

Device configuration is not available in the app. To change settings, you need to connect to the Scout web interface. Learn more about Scout configuration here.

Device status: Scanning vs. Standby​

• Scanning — the device is actively scanning and sending detection data to the cloud.
• Standby — the device is not currently sending data to the cloud.

The difference is cloud data transmission, not detection capability.

Viewing Detections in Real-Time​

From the app’s main map screen, you can see all drone traffic accessible to your account — including your own Scout and public drones from other users.

Click on icons in the map to view detailed information such as drone position, altitude, and speed.

Map Icon Legend​

UAV Location — Indicates the current position of a drone.

Operator Location — Shows the position of the drone operator, when available.

Receiver Location — Displays the location of a Remote ID receiver.

Browsing Detection History​

To view past detections:

1. Tap the radar icon at the bottom of the map screen, or
2. Go to your profile page and select My Detections.

This opens a list of all detections available to you.

Use the dropdown menu at the top to select a specific device (if you have more than one). Then choose the desired date — by default, it shows the current day.

Viewing Detection Details​

You can open detailed views for each detection. What happens next depends on the age of the detection:

• Live or recent detections: The map will automatically scroll to the detection's current position.
• Older detections: You’ll be taken to a dedicated detail page showing all the information captured.

Tap the three-dot menu on the right for additional options.

Exporting Detection History​

You can export detection data and view it using mapping tools like Google Earth, QGIS, Mapbox, or OpenStreetMap (OSM).

To export:

1. Open a detection detail screen in the app.
2. Tap Export in the top-right corner and select the KML format.

Here’s how to open it in Google Earth:

1. Visit Google Earth Web.
2. Create a new project.
3. Go to File → Open local KML file and select your exported file.

Streaming Scout Data to a TAK Server (Cloud Mode)​

In Cloud Mode your Scout's detections are not limited to the Dronetag App - the Dronetag cloud can also forward them to your own TAK server as Cursor-on-Target tracks, without any extra hardware or firmware on your side. The setup is done in the integration portal and is described in Setting up TAK Server integration.

A three-minute walkthrough by Tactical Tech Lab showing Dronetag Remote ID data appearing live on a TAK server through this cloud integration.

Using the Dronetag App on Mobile​

The Dronetag App is fully cross-platform — meaning you can access all features from your mobile device just as you would on the web.

Our app is available for both iOS and Android, allowing you to use it on your smartphone or tablet. You can download it from the App Store or Google Play.

All web app features — including device registration, real-time tracking, and detection history — are also available in the mobile app.

The LED on the bottom of the device provides immediate, high-level feedback during installation and maintenance. It is designed to save you trips between the rooftop and your laptop by confirming power, network connectivity, and configuration validity at a glance.

LED Behavior Configuration​

You can customize how the LED behaves in the web UI settings to match your specific deployment needs:

• LED ON: The LED runs continuously in all operating states. Ideal for field tests or tripod use.

• LED OFF: The LED is fully disabled. Best for maximum stealth or security.

• LED Auto-Off (Default): The LED stays active for 10 minutes after power-up to assist with installation, then turns off to prevent light pollution.

Brightness Levels​

Adjust the visibility based on your environment:

• Bright (Default): High visibility for daytime installations.

• Medium: Balanced for general use.

• Dim: Designed for sensitive environments; visible only at night when standing directly next to the unit.

Device States​

Possible states are the following:

This page contains detailed troubleshooting information to help you identify and resolve the most common issues encountered while using the Dronetag Scout. Whether you’re facing connectivity problems, detection range limitations, or firmware concerns, the guidance below is designed to walk you through practical steps toward a solution.

Before contacting our support team, please ensure that your device is running the latest firmware version, as many issues are resolved through regular updates. You can follow our Firmware Update Guide for instructions on how to check and update your Scout.

We also encourage you to review the most common problems first, where we’ve listed known scenarios and their proven solutions. If you're still experiencing trouble after reviewing those, please proceed to the section on how to report a problem to our support team, where you’ll find a checklist of the information we need to assist you efficiently.

If you notice an issue not covered here, don’t hesitate to contact us at support@dronetag.com. Your feedback helps us improve and expand our documentation to serve you better.

How to report a problem to our Support Team​

🛠️ Troubleshooting Connectivity​

If you're unable to access the Scout’s interface, try the following steps to identify and resolve common issues:

Common issues​

Dronetag products are warranted to be defect-free in material and workmanship one year after the purchase. For the duration of the warranty period, Dronetag, at its sole option, will repair or replace any product which fails in normal use. Such repairs or replacement will be made at no charge to the customer for parts or labour, provided that the customer shall be responsible for any transportation cost.

Restrictions​

Warranty does not apply to cosmetic damage, consumable parts, damage caused by accident, abuse, misuse, water, fire or flood, damage caused by unauthorized servicing, or product that has been modified or altered.

Disclaimer​

We kindly advise that our company cannot assume responsibility for the installation of our product by the user or any potential loss incurred as a result. While we strive to provide comprehensive guidance and support, the responsibility for proper installation lies with the user. Should you require any further assistance or clarification, please do not hesitate to contact our customer support team. Your understanding is greatly appreciated.

Warranty Service​

Warranty repair service shall be provided directly by Dronetag. Proof of purchase for the product from Dronetag or an authorized reseller is required to obtain and better expedite warranty service. The customer is responsible for transportation costs involved in getting the unit to the Dronetag facility. It is recommended to use a shipping method with tracking and insurance.

Please email us at support@dronetag.com with a description of the problem you are experiencing. Also, please provide the model, serial number (if applicable), shipping address and a daytime contact number. You will be promptly contacted with further troubleshooting steps or return instructions.

Warranty Conditions​

The foregoing warranty shall apply only if:

1. The Product has not been subjected to misuse, neglect or unusual physical, electrical or electromagnetic stress, or some other type of accident.
2. No modification, alteration or addition has been made to the Product by persons other than Dronetag s.r.o. or Dronetag s.r.o.'s authorized representatives or otherwise approved by Dronetag s.r.o.
3. The Product has been properly installed and used at all times in accordance, and in all material respects, with the applicable Product documentation.
4. The Product's lightning protection, surge protection and ESD has followed local rules and Dronetag's instructions.

Dronetag s.r.o. does not warrant that the operation of the products is error-free or that operation will be uninterrupted. In no event shall Dronetag s.r.o. be responsible for damages or claims of any nature or description relating to system performance, including coverage, buyer’s selection of products for buyer’s application and/or failure of products to meet government or regulatory requirements.

Returns​

In the unlikely event a defect occurs, please work through the dealer or distributor from which this product was purchased.

If the Scout you want to return was bought directly from Dronetag, contact us at support@dronetag.com first and then send the product to the following address:

• Dronetag s.r.o., Benesovska 2270/34, 10100 Prague, Czech Republic

Post-Warranty Service​

Besides warranty service, Dronetag also offers post-warranty repairs. Let us know at support@dronetag.com your problem, and we will try to do our best to find a solution for you.

Manufacturer​

The device is designed and assembled in the Czech Republic. Use the following facility address for any shipment of warranty or repair items.

• Dronetag s.r.o., Benesovska 2270/34, 10100 Prague, Czech Republic

Dronetag Scout and Scout EVK have been created for the most straightforward handling possible. Still, the following safety notes must be followed to reduce the risk of accidents, injuries and device malfunction to a minimum. If misused, it has the potential for causing fire, electrical shock or personal injury. Dronetag is not liable for damages arising from the use or misuse of this product. To help ensure accident-free operation, follow these guidelines:

• This and the Dronetag App manual must be read carefully, and all instructions must be followed. Special attention must be taken to all warnings and precautions.
• Use only attachments/accessories specified by the manufacturer. Dronetag, s.r.o. carries no responsibility for using other than specified attachments/accessories.
• The user is solely responsible for the risk while installing and using this device. Dronetag is not responsible for any injuries or accidents that are a result of installation of the Scout.
• The LTE antenna used for this receiver must be installed to provide a separation distance of at least 20 cm from all human bodies and must not be located or operating in conjunction with any other antenna or transmitter.
• Keep antennas of other devices as far from the Scout as possible, at least 40 cm.
• Do not allow liquid, small particles or other foreign objects to get into the system. Follow the installation manual for proper installation.
• Mounting the Scout or Scout EVK in an improper way may lead to injuring people or damaging property
• Do not expose the system to conditions which exceed the Scout's or Scout EVK's or accessories' IP rating and operating temperature.
• Keep the system and accessories, including cable ties and fasteners, out of the reach of small children.
• If the system is brought directly from a cold location to a warm one, moisture may condense inside the system. If this occurs, the system may not operate properly. In this case, unplug all cables/accessories immediately and leave the device in a dry place for several hours.
• Stop using the system and disconnect it from any connectors immediately if the device functions abnormally, produces unusual sounds or smells, or becomes too hot to touch.
• Use outdoor rated Ethernet cable only.

Electric safety information​

1. Compliance is required with respect to voltage, frequency, and current requirements indicated on the manufacturer’s label. Connection to a different power source than those specified may result in improper operation, damage to the equipment or pose a fire hazard if the limitations are not followed.

2. There are no operator serviceable parts inside the Dronetag Scout and included PoE connector, except for replacing or installing a SIM card. Service should be provided only by a qualified service technician.

3. Included PoE injector is provided with a detachable power cord which has an integral safety ground wire intended for connection to a grounded safety outlet.

   • Do not substitute the power cord with one that is not the provided approved type. Never use an adapter plug to connect to a 2-wire outlet as this will defeat the continuity of the grounding wire.
   • The equipment requires the use of the ground wire as a part of the safety certification, modification or misuse can provide a shock hazard that can result in serious injury or death.
   • Contact a qualified electrician or the manufacturer if there are questions about the installation prior to connecting the equipment.
   • Protective earthing is provided by Listed AC adapter. Building installation shall provide appropriate short-circuit backup protection.
   • Protective bonding must be installed in accordance with local national wiring rules and regulations.

4. Follow all suitable local regulations for installation of electric devices.

5. The maximum input voltage for PoE injector is 240V and should be applied only to included Power Cable.

6. Do not put any DC voltage to any antenna connectors.

Lightning Protection​

Follow the local rules for installation of the lightning surge protection system when deploying the Scout and Scout EVK gateway, both outdoors and indoors. Such a protection system must be taken into consideration to ensure a fully functional gateway without interruptions or damage from lightning.

Outdoor Surge Protection System​

• Antenna Grounding: Dronetag, s.r.o. recommends installing a lightning arrestor on all the antenna N-type terminals. The arrestors must be N-type Female to Male to fit the antenna and enclosure connectors. Ensure you use a 10 AWG or better wire to connect the screw terminals of the arrestors to the grounding rail mounted on the building wall (grounding bar in the case of field deployment).
• Grounding of the Scout: We recommend grounding the device. We do not recommend grounding into the lightning conductor system. Additionally, it is recommended to use another 10 AWG or better grounding wire to connect the screw terminal on the bottom-left side of the gateway casing to the grounding rail (bar).

Indoor Surge Protection​

For protecting the indoor equipment and circuitry connected to the gateway, it is recommended to install an Ethernet surge protector. This device should be positioned along the cabling that connects the gateway to the PoE injector. Make sure you connect its grounding wire terminal to an appropriate building grounding point.

Routine Maintenance​

Regular maintenance of your Scout device helps ensure reliable operation and extends its lifespan. During maintenance checks, please verify the following:

• Antenna Connections: Ensure all antennas are securely screwed in and have not loosened due to vibration or temperature fluctuations.
• Antenna and Ethernet Port Insulation: Check that the insulation tape or protective seals applied to the antennas and the Ethernet port are intact and properly positioned to prevent moisture ingress.
• Grounding Connection: Confirm that the grounding wire is firmly connected and not loose to maintain proper electrical safety and device protection.
• Mounting Stability: Inspect the mounting hardware to make sure the Scout is securely fixed and there is no looseness that could cause mechanical stress or movement.

Perform these checks periodically, especially after harsh weather conditions or extended operation, to keep your Scout functioning optimally.

Limitation of Liability​

EXCEPT TO THE EXTENT PROHIBITED BY LOCAL LAW, IN NO EVENT WILL DRONETAG S.R.O. OR ITS SUBSIDIARIES, AFFILIATES OR SUPPLIERS BE LIABLE FOR DIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR OTHER DAMAGES (INCLUDING LOST PROFIT, LOST DATA, OR DOWNTIME COSTS), ARISING OUT OF THE USE, INABILITY TO USE, OR THE RESULTS OF USE OF THE PRODUCT, WHETHER BASED IN WARRANTY, CONTRACT, TORT OR OTHER LEGAL THEORY, AND WHETHER OR NOT ADVISED OF THE POSSIBILITY OF SUCH DAMAGES

The Dronetag Scout EVK is an earlier evaluation kit model that will continue to receive essential updates and limited support. However, we strongly encourage all users to upgrade their units to the production-ready Dronetag Scout system.

The upgraded Scout offers a more robust system, improved long-term stability, and full access to all available features. Some important capabilities—such as factory reset, secure credential management, and cloud-based provisioning—are not available on the original Scout EVK.

This guide walks you through the upgrade process in detail, including:

• How to request the upgrade
• Flashing and using the required SD card images
• Performing the physical upgrade
• Registering the upgraded Scout with your account

After upgrading, your unit will receive a new serial number, and the old Scout EVK will need to be removed from your Dronetag Cloud account. You will register the new Scout using the provided serial number for continued access and management.

You may choose to flash the SD cards yourself or request pre-flashed cards from us. Instructions for both options are included below.

1. Submit a Scout EVK Upgrade Request​

Please send an email to support@dronetag.com with the following information:

1. Original order number or name of your sales contact.
2. Company name (if applicable).
3. If using the Scout EVK with Dronetag Cloud, include the email address associated with the registered account.
4. Serial number of your Scout EVK unit:
   • Located on the bottom of the unit, or
   • Found in the Dronetag mobile app under your account.

2. Choose Your Flashing Option​

Let us know how you want to handle the SD cards required for the upgrade. There are two SD cards involved:

• Preparation SD Card – used to prepare the device
• Scout System SD Card – contains your custom-provisioned system

Option A: I will flash the SD cards myself​

We will send you both SD card images and you can flash them manually.

• Follow the instructions here to learn how to flash .img files onto SD cards.

Option B: I prefer to receive pre-flashed SD cards​

If you would like to receive ready-to-use SD cards, include the following shipping details in your request email:

1. Shipping address
2. Contact person
3. Email address
4. Phone number

Option C: Full Scout Unit Replacement​

If you're not comfortable performing any technical work, we can offer a full replacement of the Scout unit. The upgrade will be handled at our facility, and you would be responsible for shipping costs.

3. Performing the Upgrade​

Once you have received or prepared the required SD cards, follow the steps below to upgrade your Scout EVK.

There are two SD cards involved in the upgrade process:

If you are flashing the SD cards yourself, you can reuse a single SD card.
In this case, first flash it with the Preparation image, perform the preparation steps, then re-flash the same card with the Scout System image and continue with the remaining steps.

Whether you use one or two physical SD cards, the upgrade steps remain the same.

Step 2: Insert the Preparation SD Card​

1. Insert the Preparation SD Card into the mini computer inside the Scout.
2. Power up the unit using the PoE connector.
3. Wait approximately 1 minute. The mini computer will start blinking with a green ACT LED.
4. Power down the device by unplugging the PoE cable.

Step 3: Insert the Scout System SD Card​

1. Replace the Preparation SD Card with the Scout System SD Card.
2. Power on the unit again.
3. Leave the system running for at least 30 minutes.
   • During this time, the system formats and initializes itself.
   • Do not interrupt power during this process.

4. Post-Upgrade: Access and Configuration​

Once the upgrade is complete:

• The Scout EVK will be accessible on your local network via DHCP using default settings. For more details refer to the configuration page
• You can proceed with further configuration as needed.

Registering the Upgraded Scout​

With the SD cards, you will also receive a new serial number, which replaces the original Scout EVK identity.

1. Remove the old Scout EVK from your Dronetag Cloud account.
2. Register the upgraded Scout using the new serial number provided.

Accessing the Management UI​

The upgraded Scout includes a login-protected management interface.

• The default username and password will be provided by Dronetag Support together with your SD cards or download package.
• Upon first login, please change the credentials immediately to something known only to you.

If you need help accessing the UI or updating credentials, reach out to support@dronetag.com.

💾 SD Card Preparation

This page guides you through flashing new firmware onto a microSD card and upgrading your Scout to a newer generation.

Use a microSD card with at least 8 GB of capacity. This SD card is used during the Scout EVK upgrade process. All former data on the card will be permanently erased.

We recommend using a different SD card than the one currently used in your Scout EVK. This allows you to keep your original setup as a backup.

You can use either Windows or Linux to prepare the SD card.

If you are confident and understand the risks, you may reuse the existing card — but make sure to back up your current setup first.

Scout secured one of the Netherlands’ largest music festivals.​

City of Helsinki Monitored Drone Operations with Scout.​