Determine ArduPilot default hidden flight modes about qgroundcontrol HOT 6 CLOSED

I assigned this one to myself. Actually it's been in my to do list for weeks, but I want to first finish that gimbal PR, as it is taking forever.

Ardupilot implemented a parameter that manages precisely this at the AP level, rejecting the mode change if it is configured to do so using this parameter. So I think it would be great to read that parameter, in the newer firmwares that support it, and update automatically the flight mode list based on it. If we want to make it super neat, we could try to detect discordances between the QGC settings and AP parameter and warn the user and hopefully tidy all up for them.

I Think over the next month I will be able to go through this. In the meantime, If you want to leave by default just some flight modes, maybe I would say they should be for copter:

• STABILIZE
• ALT HOLD
• LOITER
• POS HOLD
• GUIDED
• AUTO
• RTL
• LAND

I think the above are a good starting point. For Plane these would be good:

• FBW A
• LOITER
• GUIDED
• RTL
• TAKEOFF

and for VTOL, we should add these to the ones for plane:

• Q LOITER
• Q RTL
• Q HOVER

About ROVER and SUB I am not really sure, if somebody from Bluerobotics is around they can probably help us figure out the most used modes for these vehicles.

from qgroundcontrol.

Thanks, that is helpful. It also reminds me that ArduPilot flight modes differ quite a bit with respect to vehicle type. I think I'm going to need to change the code to store hidden flight modes by vehicle type before I can make this all work well.

from qgroundcontrol.

I think for Ardupilot we could do something based on that parameter functionality instead, so effectively relying on the vehicle, instead of QGC settings, to show those flight modes. I think we could contain this in APMFirmwarePlugin.

I assigned this to me, I think this month I could take a look at it. I will keep you updated about it, thanks!

from qgroundcontrol.

Now that I think of it, we actually want that QGC settings functionality as well for Ardupilot, because otherwise we don't have a way to know this unless vehicle sends us the parameters, and eventually we could face a situation where we connect to vehicle, so the flight mode menu is available, but we don't have that parameter value yet, so in this situation we would really want to use those stored QGC settings.

from qgroundcontrol.

This feature needs to be changed to be vehicle class specific.

from qgroundcontrol.

@Davidsastresas I've updated to your feedback

from qgroundcontrol.