Plane 4.1.0 beta

[tridge]

@David82

Why is it that when THROTTLE_NUDGE = 0 and no airspeed sensor is used, throttle still moves around, as if it is trying to maintain a specific air or ground speed? Is the only possibility that it is trying to stay above ARSPD_FBW_MIN?

you haven’t said what flight mode the Q is about. If this is AUTO then the throttle moves to maintain height.

@David82

When ardupilot firmware first boots up, does the plane have to be level? Is there some kind of IMU leveling that happens on boot?

no, but it does need to be not moving. It doesn’t matter what the orientation is as long as it is still until gyro cal is finished

@David82

Several of the digital OSD (e.g. DJI Air unit) indicators don’t work/show up. Bearing and airspeed are some examples. I’m not using a compass or airspeed sensor, but (1.) I think ardupilot is estimating airspeed, so that should be shown, even if no airspeed sensor is present, (2.) even if no compass is present, GPS units still output a bearing, so that should be shown. Azimuth indicators don’t work as well, if I remember correctly. Are there plans to fix any of this?

you’re better off asking here:

MSP protocol support

I’ve been working at adding MSP (multiwii serial protocol) support to Ardupilot, right now the code is on a test branch on my github and is very likely to change a lot in the future This thread will serve as the base to create proper documentation and as a central point to collect feedback on the implementation. The protocol decoder is ported from betaflight/inav and supports both MSPV1 and MSPV2. It also supports iNav MSPV2 sensor messages for lidar and optical flow. It shoul…

but make sure you include your parameters, as without those we’re just guessing. Best to provide a log as that has parameters and firmware version.