Hamish Willee

Should this message include current position information, if relevant to the message? I.e. consider [ORBIT_EXECUTION_STATUS](https://mavlink.io/en/messages/common.html#ORBIT_EXECUTION_STATUS). My gut feeling is that it is _relevant_ to a bunch of commands but I...

The main driver for this message being generic was (for me) to have a way to get around the fact that things like takeoff and orbit are long-running commands that...

General consensus seems to be that something like this is only broadly attractive to stakeholders because it offers the opportunity to add backwards-compatible reporting about progress of commands to the...

FYI on PX4 fixed wing - An idle setpoint will make the vehicle be in idle state - zero throttle, zero roll / pitch. - A Loiter setpoint will make...

@julianoes Thanks. So in next revision of this PR I'll create an extension. Why is knowing the type of setpoint useful?

@julianoes @auturgy OK, updated this to include the position setpoint type in a new enum. Any objections?

@dagar @auturgy Any thoughts on this? Things that spring to mind: 1. Is it also relevant to FW and other types? 2. Why timestamp needed? 3. Ever more than 16...

@bkueng Any further work/planning on events interface? Might be a good candidiate for this. @lthall Your thoughts appreciated. Ideally today so we can move this along.

No idea. What do you see on the console? https://github.com/mavlink/c_uart_interface_example#execution This is pretty low level code. What are you ultimately trying to do? If it is "control a drone" then...

> as far as I understood MAVSDK can not be a choice. That is a question to ask on the PX4 slack channel #mavsdk. It may be that FreeRTOS is...