Hamish Willee

Howdy! 1. Thanks for cross posting this to https://github.com/ArduPilot/pymavlink/pull/569 - that's where the tools are maintained. 2. I think you might be correct about the problem though. The `rxmsg->len` that...

@peterbarker Would appreciate your comment on this. At the moment you can infer some of the states of the mission from the mode (particularly in ArduPilot where pause is a...

Mission states are a little complex and we may need to rethink this to make sure that we're sending the right information. What that information depends on who/how this is...

@julianoes @tridge I updated so all fields are 0 for the default "not supported" case. In addition, have modified the reporting of state in line with the [notes above](https://github.com/mavlink/mavlink/pull/1869#issuecomment-1212621078). It...

As discussed in dev call, this has been reviewed by ArduPilot and PX4 and can be merged. Note that this: - adds extension fields to the previous mission in a...

FYI @TSC21

The simple way of looking at this is that "Body" implies that velocity is relative to vehicle heading, while "Local_Offset" implies "Position" is relative to vehicle current position. If those...

Some of this could be captured in the MAVLink docs -e.g. https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_OFFSET_NED Won't do anything for now though - lets see what other's say. E.g. might be a more clear...

OK, you're right that BODY_OFFSET_NED is different from LOCAL_OFFSET_NED with respect to positions. Both have origin set on the vehicle, but for the later the axis is NED while for...

@korigod @okalachev That is a really comprehensive and well worded RFC. Going to take me some time to digest. I *believe* the plan is for people to comment here, with...