Skip to main content

Integration Overview

info

It is important to note that integration and compliance when using the Dronetag DRI module will depend on the market you are in and the market where you plan to use the drone.

There are different regulations governing drone usage around the world. In the European Union (EU) market, there are slightly different regulations and compliance mechanisms in place for drones than in the United States of America (USA).
For details, see the EASA drone regulations for the EU and the FAA Remote ID rules for the USA.
Before using the DRI, it is important to familiarize yourself with these regulations and ensure that you comply with them.

Integration Paths​

EU – Compliance with Open Category (A1–A3) and Specific Category by Retrofit​

Using the Dronetag DRI to satisfy the requirements for drones operated in the Open category (A1–A3) and for drones in the Specific category as defined by EASA. Drones in the Open category are flown under subcategories A1, A2, or A3, depending on the operational limitations. The actual class of the drone (C0–C6) is determined by its CE marking and technical specifications; see the How do I determine which subcategory I can fly under? for details. To achieve compliance, you only need to connect the Dronetag DRI module to your flight controller and set up the Dronetag DRI module via our Dronetag App.

This step‑by‑step guide covers:

  • Hardware installation of the DRI module and how to choose the antenna
  • Software configuration of your flight controller and DRI module for EU regulations

Open EU Retrofit Step‑by‑Step Guide

EU – Compliance with Open Category C‑class for Manufacturers​

Using the Dronetag DRI to satisfy the requirements of C‑class drones in the Open category as defined by EASA.
As a manufacturer, you need to classify your drone into one of the C classes, flash the flight controller with OpenDroneID‑compatible firmware, and configure the DRI module via our Dronetag Toolbox App. Users can configure their Operator ID using their preferred flight controller configuration tool.

This step‑by‑step guide covers:

  • Introduction to compliance for C‑class drones in the Open category
  • Hardware installation of the DRI module and how to choose the antenna
  • Software flashing and configuration of the flight controller and DRI module for EU regulations

Open EU Manufacturer Step‑by‑Step Guide

USA – Retrofit Drone with Remote ID Module​

The Dronetag DRI module can be used as a Remote ID Broadcast Module for drones that do not have built‑in Standard Remote ID. This option is primarily intended for existing or hobbyist drones that would otherwise be non‑compliant with FAA Remote ID rules.

To use it, simply connect the Dronetag DRI to your flight controller and configure the device via the Dronetag App. When properly installed and configured, the DRI broadcasts the required identification and flight information as defined by the FAA.

This step‑by‑step guide covers:

  • Hardware installation of the DRI module and how to choose the antenna
  • Software configuration of your flight controller and DRI module for USA regulations

Open USA Retrofit Step‑by‑Step Guide

Note about USA Retrofit

A Broadcast Module enables compliance for many operations, but it has limitations.

  • It does not convert the drone into a Standard Remote ID aircraft.
  • The drone must be flown within visual line of sight.
  • Operations in FRIA (FAA‑Recognized Identification Areas) do not require Remote ID at all.

USA – Standard Remote ID for Manufacturers​

Using the Dronetag DRI as part of an FAA‑approved Standard Remote ID unmanned aircraft. This requires full integration of the module into the drone’s system, including the ability to transmit the GNSS position of the control station (pilot) to the aircraft for broadcast. The flight controller must run firmware with OpenDroneID support and be configured to ensure continuous Remote ID functionality. Manufacturers are also required to implement a fail‑safe mechanism so that the aircraft cannot take off if the Remote ID system is not operational. Configuration of the DRI module is done via the Dronetag Toolbox App, while users can set their Operator ID through their preferred flight controller configuration tool.

This step‑by‑step guide covers:

  • Hardware installation of the DRI module and how to choose the antenna
  • Software flashing and configuration of the flight controller and DRI module for USA regulations

Open USA Manufacturer Step‑by‑Step Guide

Forwarding​

The DRI module has a Forwarding port, which can forward MAVLink messages (MAVLink 2 only). This allows for connecting the DRI module on drones lacking an additional TELEM port.

The baud rate of this Forwarding port can be configured inside the Dronetag App. Any valid MAVLink message from the Forwarding port will be sent to the Controller port and vice versa. Note that this feature should theoretically work with any MAVLink peripheral; however, problems may occur when using untested peripherals. Prior to using this feature, we highly recommend conducting thorough testing. Additionally, for non‑flight‑critical component modules that may drop MAVLink messages when forwarding large amounts of data, we suggest forwarding them separately. In most cases, the Forwarding port functions smoothly as a lossy connection. We recommend treating it as such, while acknowledging that occasional dropped MAVLink messages may occur.

The DRI module changes the rates of some messages on the flight controller, which might interfere with peripheral functionality. When a peripheral requires some of the messages at a rate different from the module’s, see the MAVLink integration section. In future updates, the module may operate with different rates than its own.