RemoteID User's Manual v1.1

Specifications

Radio module: Espressif ESP-C3 module. Output power Bluetooth and WiFi 2.4GHz (ERP): + 20 dBm (100 mW).

Antenna: 2.33 dBi omni-directional antenna with SMA connector (included).

Firmware: ArduRemoteID (https://github.com/ArduPilot/ArduRemoteID). Supports upgrading firmware via the web interface ("OTA"). Long range: > 500m detection range (Estimated value, ground test of 180 meters).

Connectivity: 1x JST GH 4-pin CAN (DroneCAN) port, 1x JST GH 6-pin TELEM (UART) port.

Power: +5V supplied from TELEM or CAN port.

LED lights: RGB status LED.

Size: 38 x 26.5 x 11.5 mm (not include antenna).

Operating temperature: -40°C to +85°C.

Weight: 27.5g.

Programming: ESP32-C3 through serial port firing programming (when applicable to empty film).

Firmware Upgrade Methods

1. USB-UART Upgrade

Steps:

1. Use the USB-UART board to connect to the REMOTEID UART port with a 6PIN GH wire.
2. Open the flash_download_tool_3.9.3.exe on the computer.
3. Hold down the download button to power on.
4. After selecting firmware and string slogans, click START to start flashing.

Note: This method is applicable for ESP32-C3.

Visual indicators mentioned: "Download Button", "WS2812 Status LED", "CAN", "UART".

2. OTA Firmware Upgrade

The REMOTEID acts as a WiFi Access Point.

Connect to the WiFi network with SSID: RID_xxxxxxxxxxx. The default password is ArduRemotelD.

After connecting, open a web browser and navigate to http://192.168.4.1.

At the bottom of the page, you can upload and flash the new firmware.

Remarks:

• Important: Download the ArduRemoteID-ESP32C3_DEV.bin file from the latest release page: https://github.com/ArduPilot/ArduRemoteID/releases
• Use this file for uploading the new firmware.
• Press the "Update" button to update the firmware.
• If the firmware update fails, it will revert to the factory installed firmware.

System and Location data fields are displayed, including:

• OperatorLocationType: TAKEOFF
• Classification Type: UNDECLARED
• OperatorLatitude: 0.00000000
• OperatorLongitude: 0.00000000
• AreaCount: 1
• AreaRadius: 0
• AreaCeiling: -1000.00
• AreaFloor: -1000.00
• CategoryEU: UNDECLARED
• ClassEU: UNDECLARED
• OperatorAltitudeGeo: -1000.00
• Timestamp: 0
• Status: REMOTE_ID_SYSTEM_FAILURE
• Direction: 361.00
• SpeedHorizontal: 255.00
• SpeedVertical: 63.00
• Latitude: 0.00000000
• Longitude: 0.00000000
• AltitudeBaro: -1000.00
• AltitudeGeo: -1000.00
• HeightType: OVER_TAKEOFF
• Height: -1000.00
• HorizAccuracy: UNKNOWN
• VertAccuracy: UNKNOWN
• BaroAccuracy: UNKNOWN
• SpeedAccuracy: UNKNOWN
• TSAccuracy: UNKNOWN
• TimeStamp: 0.00

Documentation links:

• ArduPilot Project
• ArduRemoteID Project
• ArduPilot RemoteID Documentation
• OpenDroneID Website

2. Using the REMOTEID

The REMOTEID is controlled by the autopilot system. For normal operation, ensure the REMOTEID is powered on (status LED is red) and can communicate with the autopilot system.

Ardupilot Integration

Ardupilot has support for Remote ID in version 4.x and newer. For more information, see: https://ardupilot.org/dev/docs/opendroneid.html#opendroneid

PX4 Integration

Support for PX4 is pending. See this pull request for more information: https://github.com/PX4/PX4-Autopilot/pull/20036/

2.1 Android App

Use the free OpenDroneID OSM Android app to view DroneBeacon Remote ID signals: https://play.google.com/store/apps/details?id=org.opendroneid.android_osm

Note: Only a few Android smartphones support reception of Bluetooth Long Range and/or WLAN NaN signals. A list of supported smartphones is available here: https://github.com/opendroneid/receiver-android/blob/master/supported-smartphones.md

2.2 Open Drone ID Framework

The ArduRemoteID firmware uses the Open Drone ID framework to broadcast Remote ID signals. The framework can be found at: https://www.opendroneid.org/

2.3 Connecting to Flight Controller via Serial Port (MAVLink/TELEM)

Connect the REMOTEID to the flight controller using the MAVLink/TELEM interface.

Use MissionPlanner (version 1.3.77 or higher).

Setup the following parameters in MissionPlanner (Config --> Full Parameter List):

• DID_ENABLE: 1
• DID_OPTIONS: 1
• DID_MAVPORT: X (where X is the serial port attached to the OpenDroneID module)
• DID_CANDRIVER: 0
• AHRS_EKF_TYPE: 3
• GPS_TYPE: 1
• GPS_TYPE2: 0

Configuration: Below the COM port settings, select the interface ending with "-ODID TXRX". In MissionPlanner, go to Config --> Full Parameter List to see the list of Remote ID parameters.

2.4 Connecting to Flight Controller via CAN Port (DroneCAN)

Connect the REMOTEID to the flight controller using the DroneCAN/CAN interface.

Use MissionPlanner (version 1.3.77 or higher).

Setup the following parameters in MissionPlanner (Config --> Full Parameter List):

• DID_ENABLE: 1
• DID_OPTIONS: 1
• DID_MAVPORT: -1
• DID_CANDRIVER: 1 (where 1 is the CAN 1 interface of the flight controller)
• AHRS_EKF_TYPE: 3
• GPS_TYPE: 1
• GPS_TYPE2: 0

Configuration: In MissionPlanner, go to Setup --> Optional Hardware --> DroneCAN/UAVCAN. Click the "MAVLink CAN1" button. If the module is connected to CAN2, click "MAVLink CAN2". After a few seconds, the list of connected CAN devices should be displayed.

2.5 Mobile Phone Search for REMOTEID Hotspot SSID

The default SSID is RID_xxxxxxxx, where xxxxxxxx is the factory WiFi MAC address of the board. The default password is ArduRemotelD.

2.6 Mission Planner Setting

Connect a GPS to MissionPlanner at the ground end to provide the Operation Location.

In MissionPlanner homepage, select "Drone ID" to set:

• (1) UAS ID*
• (2) UAS ID Type
• (3) UA Type

In MissionPlanner, go to "Operation" to set:

• (1) Operator ID
• (2) Oper. ID Type
• (3) Self ID Desc
• (4) Self ID Type

2.8 Status and Operation

After setting the above parameters, wait for the status LED on the REMOTEID to turn green. The REMOTEID will then start sending information about the aircraft and the operator. Both positions can be viewed on the phone APP.

FCC Statement

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

• (1) This device may not cause harmful interference, and
• (2) This device must accept any interference received, including interference that may cause undesired operation.

Warning: Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.

NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

FCC Radiation Exposure Statement

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body.