Remote ID configuration

Configuration options for drone manufacturers

Support for Remote ID has been added starting from AuterionOS 2.5.5. While the core functionalities of the Remote ID agent are mostly untouched, the next AuterionOS releases can have minor modifications to the configuration options and broadcast interface.

Enabling or Disabling Remote ID in AuterionOS

Starting with AuterionOS 2.7, this feature is by default disabled and can be enabled through the following mechanisms:

  • The Auterion Developer Tools, by injecting the following environment variable: REMOTEID_ENABLED=1 This setting is overriden by:

  • The "Enable Remote ID" toggle on the vehicle's web interface:

This is a one-time toggle, which works only in the Disabled -> Enabled direction. It is designed to allow operators to delay their adoption of Remote ID, in accordance with local law. Once enabled through this mechanism, Remote ID transmission can no longer be disabled, except by an OEM, via the third override:

  • The override.env file located in /data. A value of either 0 or 1 for REMOTEID_ENABLED will disable/enable Remote ID transmission, respectively. Modifications to this file require ssh access and are therefore not available to the end customer/operator.

Enabling or Disabling Remote ID in APX4


Starting with AuterionOS 2.7, AuterionOS exposes the following variables that allow Manufacturers to configure their own specific settings required to to comply with the Means of Compliance document (MOC).

Configuring custom Remote ID WiFi Beacon channel and manufacturer ID

Starting with AuterionOS v2.7, it is possible for OEMs to customize the Remote ID service using two environment variables, injected through the Auterion Developer Tools into the custom OEM image. These are:

  • REMOTEID_MANUFACTURER_CODE : The Manufacturer (MFR) Code is a 4-character code that consists of digits and may include a combination of digits and uppercase letters, except the letters O and I. Any strings that exceed the limit will be truncated. The International Civil Aviation Organization (ICAO) is responsible for assigning a unique MFR Code to UAS manufacturers around the world. To obtain an MFR Code, visit .

  • REMOTEID_EXTRA_ID: specifies a custom ID that will be transmitted as an extra BasicID message inside the Remote ID Message Pack. The maximum length of this ID is 20 characters. Any strings that exceed the limit will be truncated.

  • REMOTEID_BEACON_CHAN: specifies a custom channel to use for the WiFi Beacon transmission.

  • REMOTEID_ENABLED: by default AuterionOS 2.7.X ships with Remote ID functionality disabled. In case your customer base falls in a country that requires Remote ID by default, set this variable to 1 to have all your production vehicles Remote ID ready.

Basic ID Message: UAS Serial number definition

As described in Section of the MOC, AuterionOS' Remote ID agent automatically generates and fills the Basic ID message with the UAS Serial Number in the format of ANSI/CTA-2063-A.

  • The Manufacturer Code is obtained by reading the REMOTEID_MANUFACTURER_CODEvariable. If not specified, the Auterion Manifacturer code will be used instead.

  • The Vehicle Serial Number is assigned to the vehicle via the Auterion Suite when the vehicle is created for the first time by the Manufacturer.

In order to make sure your vehicles are streaming the correct Vehicle Serial number defined in the Vehicle Identity in the Auterion Suite, follow the steps below.

Bring up Steps

1. When creating a new vehicle add the Vehicle Serial Number

2. Navigate to the Vehicle Dashboard and Activate the vehicle.

3. Powercycle the vehicle to conclude the operation.

After power cycling the vehicle, its Vehicle Serial Number will happear to the Dashboard and the Remote ID agent will use it.

At this point, the vehicle is ready to be claimed by a customer. When claimed in a new company, the vehicle serial number will still persists, but the end-customer will need to re-activate the vehicle in order to use the Suite features.


The APX4 parameter COM_PREARM_ODID needs to be enabled in order for the Remote ID preflight check to be enabled. In production builds of APX4 this parameter will be enabled by default and cannot be changed by the pilot. The parameter primarily exists to give developers more control over their vehicles during their development process.

  • COM_PREARM_ODID=0: Remote ID preflight check is disabled and the pilot could arm even when Remote ID is not running correctly.

  • COM_PREARM_ODID=1: Remote ID preflight check is enabled. If Remote ID is not running and healthy, APX4 will deny arming.

Ground Station

The Ground Station needs to have access to an accurate 3D GPS position, as this information needs to be broadcast fas part of Remote ID.

Stationary ground stations are however exempt from this rule. They are allowed to broadcast a static position. Auterion Mission Control 1.14.6 does not currently provide a setting to manually specify the GCS position. This feature will be added in the next release.

GCS with Built-in GPS

If the GCS device has a built-in GPS module, no additional steps should be necessary, except for validation.

GCS using External GPS

If the ground station is retrofitted with an external GPS module, for example via USB, please adhere the following procedure when testing:

  1. Close AMC

  2. Connect the GPS device

  3. Open AMC, then go to the "Settings" menu and the "General" tab. Then scroll down to the section "AutoConnect to the following devices". There make sure that RTK GPS is disabled, select the serial device and configure the baudrate. For the Freefly RTK GPS for example this would be a rate of 57600.

    1. On Windows, select the corresponding COM port and baudrate.

    2. On Ubuntu, select the corresponding /dev/tty device and configure the baudrate.

The screenshot below shows an example configuration on Ubuntu:


Antenna Placement

The vehicle needs an exposed WiFi Antenna such that the Remote ID information can be broadcasted with sufficient signal strength. The WiFi radiation pattern has certain requirements, as described in the Means of Compliance document (MOC) in Appendix X2.

The WiFi radiation needs to match specific criteria, such as omnidirectionality and minimum signal strength at a given distance. We summarized a possible test setup for omnidirectionality, adapted from the MOC.

In order to meet the requirements described above, antennas shall be placed in such a way that a certain signal strength at a specific distance is reached. Refer to the tests Single Point Accuracy Measurement and Omnidirectionality of the broadcast module for more details.

WiFi Configuration

In AuterionOS 2.5.5 the WiFi functionality must be disabled in order for the RemoteID agent to be fully operational. Starting with AuterionOS 2.7 and AMC 1.17.3, users will automatically get a notification via the RemoteID indicator in AMC if the WiFi is enabled.

Last updated