The latest QGroundControl (QGC) version (I’m currently running v4.2.3) has a fixed wing landing “sequence” or “syntax” that is not recognized by the MAVSDK parsing routine (I believe MAVSDK is not up to date on the latest QGC landing “syntax”). This is evidenced by the fact that an unedited working QGC mission exported to “.plan” format will not re-import using the MAVSDK “mission_import.py” script in the MAVSDK examples due to a parsing error. I can, however, get around this by manually creating MAV_CMD_DO_LAND_START & MAV_CMD_NAV_LAND mission items (essentially defining a landing as per older versions of QGC).
The latest QGroundControl (QGC) version (I’m currently running v4.2.3) has a fixed wing landing “sequence” or “syntax” that is not recognized by the MAVSDK parsing routine (I believe MAVSDK is not up to date on the latest QGC landing “syntax”). This is evidenced by the fact that an unedited working QGC mission exported to “.plan” format will not re-import using the MAVSDK “mission_import.py” script in the MAVSDK examples due to a parsing error. I can, however, get around this by manually creating MAV_CMD_DO_LAND_START & MAV_CMD_NAV_LAND mission items (essentially defining a landing as per older versions of QGC).