Ardupilot, mLRS frames are broadcast frames but are beyond the 0x27 broadcast frame space

[Ilidur]

Ardupilot and mLRS have documented their frames. They seem to be using broadcast frames for their communication. The spec in Broadcast Frames mentions that frames under 0x27 are broadcast frames and beyond that there are extended frames.

We can either:

• remove the reference of broadcast frames under 0x27 from the spec, or clarify that it is only for CRSF native frames
• move project specific frames in their own category, but break ascending order.

[olliw42]

The list may not be really complete. To me it looks that

• 0x7A MSP request / 0x7B response
• 0xAA CRSF MAVLink envelope
• possibly also 0xAC CRSF MAVLink system-status sensor (docu isn't clear)

are broadcast too. One can wonder what also the KISS fc frames are going to be.

[kamik2]

i need to have a talk with raphael about that, as well as need to check how etx and ardu handle those messages.
but I can see where the confusion is coming from.

IMHO, it should be sync byte, type, destination, origin ...... for all frame above 0x27 -
but that would not match with the frame description for the 0xAA/ 0xAC frames.

I'll keep you guys updated