search

mavlink / MAVSDK-docs

MAVSDK Guide Docs - Source Code
https://mavsdk.mavlink.io
Other
24 stars 37 forks source link

api_changes: add note about QGC plan import change #237

Closed julianoes closed 3 years ago

julianoes commented 3 years ago

To import QGC missions, you now need to use MissionRaw instead of Mission.

Thanks @mcsauder!

hamishwillee commented 3 years ago

@julianoes This is good, and I have merged it.

Note though that I might expect some more background within the MissionRaw docs - for example, I know that previously the idea was that you'd import a consistent mission into SDK objects, that could then be manipulated in Mission and then reuploaded. Further, if the object in mission not supported by MAVSDK you might reject the import. It isn't clear to me how this now works from this information provided - my assumption is that now you can download anything and just save it as a buffer to file - but we know nothing about the format of the data or how it is used -(I'm not familiar with MissionRaw, perhaps this is obvious).

julianoes commented 3 years ago

I know that previously the idea was that you'd import a consistent mission into SDK objects, that could then be manipulated in Mission and then reuploaded.

Yes you could. Initially it would reject a mission during import if it contained mission items that were not supported (had no mapping to MAVSDK mission items). Then this was extended to just warn on unsupported items. This can make for a frustrating experience if you upload your mission were some of the actions are ignored but you don't check/see the emitted warning. The drone would then e.g. not trigger the camera, move the servo, whatever it actually should be doing.

Now, with mission raw it's just a one to one mapping.

hamishwillee commented 3 years ago

@julianoes Thanks for the explanation. I looked at the MissionRaw, and yes, it makes complete sense.