olliw42

ah, many thx for pointing that out. yet, I would think, there must be kind of some process to get the vid recognized by mavlink, I mean, it wouldn't really...

since I originally raised the issue FYI, I've also purchased a USB PID/VID for using it with STorM32, for this message, but I also have to frankly say that I...

yes, I recall that mechanism, and yes, it is very similar if not identical in concept the difference, and maybe a crucial difference, would be that it would be centrally...

this is really fantastic, that this is happening!! TUNNEL: I can confirm that it is implemented in the STorM32 gimbal controller, and is used COMPONENT_INFORMATION: I still find it very...

> The first set of changes merged (see checked items above). FANTASTIC, especially that COMMAND_ACK made it ... really great > gimbal stuff ... I "think" that the ship has...

> Ideally the camera definition file would be deprecated and component definitions used for every component that needs such a thing maybe, maybe not. In principle there is really no...

**EDITED: DISCUSSION MOVED TO** https://github.com/mavlink/mavlink/issues/1686 @olliw42 Very relevant discussion to have, but a bit off topic. I have moved

there are mavlink_msg...._send() functions for all existing messages/packets however, some stuff you don't do via messages but via commands (and I guess this distinction is what confuses you) in order...

well, one can argue that it quite clearly expressed here http://mavlink.io/en/mavgen_c/#decode_command "A MAVLink Command encodes a command defined in a MAV_CMD enum value into a COMMAND_INT or COMMAND_LONG message." what...

I think this may need more thought for the get message(s) ... (1) not every recipient may be able to convert fluently between all the frames, and so it may...