Servers by jDrones

How to avoid built in velocity control for thrust in guided mode

For an onboard MPC application I would like to control my quadcopter as in stabilize or acro mode (attitude and thrust inputs). I am working with mavros on a companion computer (Nvidia Jetson TX2).
The issue I am facing is that this only works in guided mode, and in this mode a thrust input (published to /mavros/setpoint_attitude/thrust, which corresponds to the SET_ATTITUDE_TARGET message) is interpreted as some vertical velocity setpoint, rather than an actual thrust setpoint. How can I work around this built-in vertical velocity controller and send an actual thrust input in guided mode?


I’m afraid we don’t support directly controlling thrust in Guided mode. We’ve got an item on the to-do list here to support it. It’s not a very difficult task to change the commands to the position controller so that thrust is sent instead of a climb rate target but there are just so many other items on the to-do list to tackle that I can’t personally make any promises on when this will be done.

Thank you for your reply and for pointing out where to start. I might try to fix it myself, but I also look forward to a ‘proper’ fix.

Servers by jDrones