Hamish Willee

Thanks. See #1143.

This looks pretty cool. So: - MAV_TYPE_HEXADECAROTOR = 16 rotor - MAV_TYPE_OCTADECAROTOR - 18 rotor @rmackay9 @MaEtUgR @meee1 @DonLakeFlyer I am inclined to accept this - any objections? My assumption...

Discussed in the dev call. How can this work when neither ArduPilot or PX4 currently support more than 16 outputs? We're not opposed to the names, but if this is...

Thanks @rmackay9 I guess it is chicken and egg - you'll need this before it goes in. Any particular ETA?

@julianoes Do you happen to know how [MPC_YAW_MODE](http://docs.px4.io/master/en/advanced_config/parameter_reference.html#MPC_YAW_MODE) option `4: towards waypoint (yaw first)` differs from option 0?

@auturgy The ones I'd need to include from ArduPilot are these, right? : https://ardupilot.org/copter/docs/parameters-Copter-stable-V3.6.9.html?#wp-yaw-behavior-yaw-behaviour-during-missions

@bresch @julianoes That sounds like a distinction that a MAVLink user should never need to know about - ie the vehicle should know if it is VTOL or has avoidance...

@auturgy Further to https://github.com/mavlink/mavlink/pull/1297#issuecomment-579559161 ... I propose the following mapping for ardupilot yaw modes: * 0 - Never change yaw - add mode ``` Vehicle yaw does not change. ```...

@auturgy @julianoes can you please sanity check this? James, please see my comment https://github.com/mavlink/mavlink/pull/1297#issuecomment-580508523. I believe that this captures the ardupilot modes, except possibly 2. Should we make this WIP...

@amilcarlucas I attempted to be compatible with ArduPilot - see https://github.com/mavlink/mavlink/pull/1297#issuecomment-580508523 There was an open question on the mode "2" in that post (ie the ArduPilot definition is ambiguous). I...