Matthias Grob fdc4766da6 Make sure vehicle_thrust_setpoint is always published before vehicle_torque_setpoint ...

After f0b05ea7cf
the control allocator only has a callback on the torque setpoint and even though this should work
I'm paranoid and would like to avoid surprises by always publishing the thrust before torque
then the samples that were published together are also allocated together.

2025-06-05 08:46:30 +02:00

..

CMakeLists.txt

Replace rate controller with RateControlLibrary

2022-08-19 09:40:48 +02:00

Kconfig

Add support for protected build in drivers, systemcmds and modules Kconfig

2022-02-18 07:58:58 +01:00

mc_acro_params.c

mc_acro_params: beginner/tuning friendly defaults

2023-09-20 17:45:07 -04:00

mc_rate_control_params.c

[Multirotor] add yaw torque low pass filter (#24173)

2025-01-15 14:02:28 +01:00

MulticopterRateControl.cpp

Make sure vehicle_thrust_setpoint is always published before vehicle_torque_setpoint

2025-06-05 08:46:30 +02:00

MulticopterRateControl.hpp

Make sure vehicle_thrust_setpoint is always published before vehicle_torque_setpoint

2025-06-05 08:46:30 +02:00