-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multicopter hover thrust estimator use vehicle_thrust_setpoint (work in stabilized/manual mode) #19633
base: main
Are you sure you want to change the base?
Conversation
src/modules/mc_hover_thrust_estimator/MulticopterHoverThrustEstimator.cpp
Show resolved
Hide resolved
Should we go even lower level and use the allocated_thrust from control_allocator_status? |
Il would improve the estimate on setups that are often saturating, yes. For the other ones, it shouldn't change anything. |
1 similar comment
Il would improve the estimate on setups that are often saturating, yes. For the other ones, it shouldn't change anything. |
Let's pick this up again. I've not seen the hover thrust estimator fail 👀
That's done 😃 |
0a90621
to
4d00981
Compare
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 728 byte (0.04 %)]
px4_fmu-v6x [Total VM Diff: 728 byte (0.04 %)]
Updated: 2025-01-08T12:47:45 |
src/modules/mc_hover_thrust_estimator/MulticopterHoverThrustEstimator.cpp
Outdated
Show resolved
Hide resolved
src/modules/mc_hover_thrust_estimator/MulticopterHoverThrustEstimator.cpp
Outdated
Show resolved
Hide resolved
17550b1
to
94dd880
Compare
94dd880
to
e21605a
Compare
Update the hover thrust estimator to use vehicle_thrust_setpoint (body frame) rather than vehicle_local_position_setpoint thrust (NED). This allows it to work in stabilized mode.
https://logs.px4.io/plot_app?log=6df3713e-f511-4e2e-854d-8fc7ab98ec65
TODO: