Add HEXADECAROTOR

[muramura]

Add 16 rotor definition for OCTA-X16 COPTER.
18 rotor to be added for VOLOCOPTER.

ArduPilot/ardupilot#21154

HexadecaOcta ( OCTA-X16) Copter

VOLOCOPTER:

[hamishwillee]

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 is that most GCS don't really need anything more than the number of rotors? In PX4 at least you'd get more detailed geometry information from the component information file.

The reason I ask is that the Octa in the image is coaxial, so you might want to/need to identify it using MAV_TYPE_OCTADECA_COAX_ROTOR.
I have no idea what you'd call the MAV_TYPE_HEXADECAROTOR layout in that image!

[muramura]

I have no idea what you'd call the MAV_TYPE_HEXADECAROTOR layout in that image!

Ex HEXADECAROTOR layout

[hamishwillee]

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 not going to make its way into something useful for a GCS to configure itself on, not much point adding at this time.

[rmackay9]

The latest versions of AP do support up to 32 outputs but we don't have support for this vehicle type in AP yet.

[hamishwillee]

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