Cube ID Operating Quirks

The module seems to require the “Operator ID” DroneCAN message to allow arming, but the Remote ID standard (ASTM F3411 − 22a) lists the Operator ID as optional. Is there a configuration in the CubeID firmware that allows omission of the Operator ID message?

The CubeID module seems to be using a Bluetooth Peer Address Type of “Random Device Address”. This means that on each boot, the CubeID will generate a random MAC address to use for broadcasts. Can this be changed to use the bluetooth chip’s actual MAC address?