Integration Overview
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 A‑class and Specific Category by Retrofit
Using the Dronetag DRI to satisfy the requirements of A‑class drones in the Open category and drones in the Specific category as defined by EASA. An A‑class drone is classified according to its CE marking and technical specifications; see the How do I determine which subcategory I can fly under? to determine your category. 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
🇺🇸 USA – Retrofit Drone with Remote ID Module
Dronetag DRI module as an add‑on for non‑compliant drones operated by hobbyists.
You only need to connect the Dronetag DRI to your flight controller and set up the Dronetag DRI device via our Dronetag App.
This option will make you compliant by means of a Remote ID Broadcast Module in the US 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
🇺🇸 USA – Standard Remote ID for Manufacturers
Full integration of the Dronetag DRI as part of a certified drone system.
It requires the ability to transfer the GNSS position of the ground station or pilot to the aircraft. The flight controller requires firmware with support for OpenDroneID and complex configuration.
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.