Hamish Willee

Keep alive. It is a good idea. Has been waiting on versioning mechanisms.

@julianoes That true. But if this is true it does no harm to put it here. Or perhaps to put it in "Mission MicroService" docs and link to that. Either...

My plan is to add a Mission Execution section (and possibly mission validation) in the mission microservice doc [about here](https://mavlink.io/en/services/mission.html#mission-file-formats). This update can then refer to that info. @julianoes Can...

Thanks very much! I'll have a think about this. FWIW Another case requiring that you check mission validity before execution is after changing airframe.

Thanks @fisian - it's an issue here, at least initially. This is what I get generated: .hpp ```cpp /** @brief MAV FTP error codes (https://mavlink.io/en/services/ftp.html) */ enum class MAV_FTP_ERR {...

@fisian Ping re comment above ^^^

@julianoes Mean anything to you?

@julianoes @auturgy you know more about motors than me - would you like to add your comments first? I will look at this tomorrow.

@auturgy YOur suggestions aren't showning up. @cmic0 I assume you understand the workflow. We can't merge a PR into common.xml until there is working implementation. At that point the changes...

@cmic0 Please see my note above ^^^ - how are you progressing towards an implementation?