Has anyone succeeded in getting standard remote id working reliably with Cube ID and CubePilot? If so, is there any documentation of the steps?
@dleroi CubeID provides a mechanism to transmit RemoteID information. The details are stored in Cube, refer Cube ID | CubePilot . You will need to go through the registeration and approval process at FAA or relevant authorities to get the information you need to transmit like Basic ID, Operator ID etc.
Thank you.
Aside from FAA approval, is there any evidence of someone getting it to work reliably?
According to the FAA’s Declaration of Compliance website, 4 companies have used the CubeID CAN and 3 companies have used the CubeID (serial). It’s worth noting that while you are supposed to submit your data, the DoC process is primarily self-attestation that the product is compliant with the requirements.
I have spent close to 100 hours trying to get the CubeID to work without success. The hardware seems entirely capable of emitting the necessary messages at the necessary rate to be compliant with the requirements – however, the firmware running on the CubeID (1.8.59A73E5 as of this writing) has a bug where it skips messages and therefore doesn’t emit each required message at the necessary 1Hz.
In the below graph, you can see that there is an advertisement every ~200ms. This is the exact rate required to emit all 5 messages within 1 second, though it actually seems to be a little slower than 200ms by ~75us. Not sure if that timing discrepancy is on the TX or RX side.
It looks like the issue is that the module isn’t consistently cycling through the different message types. So, for instance, let’s say that the expected order is:
Operator ID → Basic ID → Self ID → System → Location
You may get that for one cycle, but the next cycle you get:
Basic ID → System → Operator ID → Location → Self ID
So you’ve blown the deadline for the Operator ID and Self ID messages and you’ve sent the rest of the messages at a higher frequency than required.
The hardware seems to be doing the right thing. It is getting an advertisement out every 200ms, but the firmware is just putting the wrong data in the advertisement. This could easily be fixed with a firmware update. I’ve asked repeatedly over the past year and a half, and in particular over the past month, for support with this issue. I have also asked for the data that they collected when developing the product to prove that it was capable of compliance. I haven’t received support or the data.