Hamish Willee

My fault - this should not be merged until in master. At that point the parameters if present should get picked up. I vote we look at this again once...

Any progress on this? I ask because of the associated docs PR :-)

@TSC21 Is this something you can help with?

@friissoren Just to make sure I do understand the problem: - The information you are interested in the GCS knowing about is in [OPEN_DRONE_ID_BASIC_ID](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_BASIC_ID). - The currently implemented and well...

So to paraphrase: - the autopilot will not stream [OPEN_DRONE_ID_BASIC_ID](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_BASIC_ID) (because it does not have the information) - The remoteID transmitter has to send the OPEN_DRONE_ID_BASIC_ID to the GCS with...

I wouldn't recommend the extended parameter protocol. It is only supported by PX4, and I "think" only for camera protocol. Generally parameters are for component specific things, and should be...

> is wrong (@hamishwillee ). Those units are only valid if the command is sent via COMMAND_INT, but AFAIK sending this via COMMAND_LONG is perfectly valid. Yes you can send...

> tridge pointed out that being able to transport 7 floats can be useful for non-COMMAND_LONG messages. So he's right in theory, but perhaps not so much in practice. If...

Fair enough. I've proposed some wording that might make this more clear in linked items.

Thanks very much for posting. Let's hope Wireshark fix that issue soon.