Cube ID

Overview

Cube ID is small size (25mm * 13.75mm * 3.5mm ) Remote ID which broadcasting information about UAVs in flight through a Bluetooth 5.2 dual-mode unit, supports both CAN and serial protocols.

Users can write different codes with one Cube ID only, to adapt to multiple UAVs based on their needs.

CubeID is FCC and CE certified.

Hardware Specification

Cube ID Specification

Type	Parameter
Bluetooth chip	Nordic NRF52840 (Bluetooth 5.2 )
Frequency	2402MHz ~ 2480MHz
Operation Temperature	-40°C ~ 85°C
Dimension	25mm * 13.75mm * 3.5mm
Weight	10g (with cable and antenna)
Protocol	Serial

Cube ID_CAN Specification

Type	Parameter
Bluetooth chip	Nordic NRF52840 (Bluetooth 5.2 )
Frequency	2402MHz ~ 2480MHz
Operation Temperature	-40°C ~ 85°C
Dimension	25mm * 13.75mm * 3.5mm
Weight	10g (with cable and antenna)
Protocol	CAN & Serial

Pinout

CAN

Pin	Definition	Cable color
1	VCC_5V	red
2	CAN_H	red
3	CAN_L	black
4	GND	black

Serial

Pin	Definition	Cable color
1	VCC_5V	red
2	TX	black
3	RX	black
4	GND	black

Installation

Connect the CAN or Serial port on module and flight controller with the suitable cable(we provide 4 Pin CAN cable,6 Pin and 8 pin Serial cable) . Stick the module to UAV by regular sticker or soft sticker (with slightly vibration isolation).

*Keep the antenna away from the propeller.

Settings

For OEM use, you must create your OEM OpenDroneID Ardupilot firmware ，please check

https://ardupilot.org/dev/docs/opendroneid.html#opendroneid)

https://www.youtube.com/watch?v=Az8v4Kx4hS0

For normal user please load latest Ardupilot firmware. Do ensure that the build you are using has OpenDroneID feature enabled. Easiest way to tell is that DID_* parameters should appear.

1. Connect the flight controller to computer via USB cable. Open Mission Planner（latest version）. Install the OpenDroneID firmware firmware by "Load custom firmware".

1. Go to "Full Parameter List" and find "DID_ENABLE". Change it to "1" to enable ODID.

For CAN

1.Go to "Full Parameter List" and find "CAN_P1_DRIVER". Change it to "1" to enable CAN.

1. Modify the following parameters:

   DID_CANDRIVER : 1 (enable relative CAN port)

For Serial

1.Find Serialx_PROTOCAL and change it to mavlink）

2.Modify the following parameters:

DID_CANDRIVER : 0 (disable relative CAN port)

DID_MAVPORT : (Serial port number to send OpenDroneID MAVLink messages to. Can be -1 if using DroneCAN)

Go to MissionPlanner homepage select Drone ID to set (1)UAS ID* (2)UAD ID Type and (3)UA Type

to set (1)UAS ID (2)UAD ID Type and (3)UA Type

Go to Operation to set (1)Operator ID , (2)Oper ID Type , (3)Self ID DESC and (4)Self ID Type

Testing

---

Download DroneScanner for IOS， OpenDroneID or DroneScanner for Android to detect and monitor nearby UAVs.

Operator are able to check UAV's location, ID , operator ID, distance from operator , ect by using these APP.

Note

For more information about Remote ID, you may check in Wiki:

https://ardupilot.org/copter/docs/common-remoteid.html

Persistent UAS ID

• To meet FAA requirements for manufacturers, a persistent ID needs to be recorded in Flight system.

• To achieve this with CubeID + Ardupilot setup. Ardupilot's persistent storage feature is used.

• The Manufacturer needs to integrate following changes depending on which release they are on:

  • Ardupilot 4.3 Releases (https://github.com/ArduPilot/ardupilot/pull/24367)
  • Ardupilot 4.4 Releases (https://github.com/ArduPilot/ardupilot/pull/24370)
• The changes are merged into latest master at the time of writing this doc, and are expected to be added to stable release 4.4.2.

• Once the firmware with said changes is loaded, parameter DID_OPTIONS need to be set to 4

• This can also be done as part of default.parms at custom build stage, to ease the setup process.

• After the setting, the first reception of Basic ID containing Drone ID and other details (from Mission Planner or any other GCS) will be persistently recorded. Please note that once set the persistent parameters can't be rolled back.

• The ID will be persistently linked with the Flight Controller.

Updating

CubeID CAN module Update

• Inside Mission Planner Go to Setup > Optional Hardware > DroneCAN/UAVCAN and establish mavcan connection depending on which CAN port you are connected.

• CubeID should appear as com.cubepilot.cubeid in the list, click Menu > Update to start the update process, Mission Planner will fetch the latest firmware binary automatically and start the process

Note: If you want to use different tool to update CubeID CAN module, you can get the latest firmware from https://firmware.cubepilot.org/UAVCAN/com.cubepilot.cubeid/1.0/firmware.bin

CubeID Serial module update

If you are not seeing CubeID Update tab in Mission Planner please update your mission planner to latest beta https://ardupilot.org/planner/docs/mission-planner-overview.html?highlight=beta#support

• Start Mission Planner with CubeID connected to one of the Telem ports of Cube and the cube connected via USB. Ensure that you start connection with Baud rate as 57600.

• Select Serial Port number where CubeID is connected (Telem1 is Serial 1 and Telem2 is Serial 2).

• Select ODID TX RX device from the Top left corner list.

• Finally click Update Firmware. The firmware update can take few minutes.

Warning

Caution: The user is cautioned that changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.

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.

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.

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

Last modify: 14th March 2023