data-driven-dynamics icon indicating copy to clipboard operation
data-driven-dynamics copied to clipboard

[WIP] Use new CA topics instead of actuator_controls/outputs

Open sfuhrer opened this issue 2 years ago • 2 comments

  • change how flight time calculation is done: use vehicle_land_detected instead of PWM thresholds
  • OR, what we need for the current work about maneuver-based ID: manually selected start/end points for a maneuver
  • use vehicle_torque_setpoint and vehicle_torque_setpoint instead of actuator_outputs for --> this is fine for FW, where every actuator is controlling one axis (not true for roll though with 2 ailerons). Better would be to use actuator_motors, actuator_servos, but I didn't get it working with that. Also, actuator_motors/_servos is logged at a much lower rate, so we may want to add them to the PX4 high rate logging profile and enable that for Sys-ID flights

sfuhrer avatar Nov 24 '22 10:11 sfuhrer

Would you have any ideas where should we put this? Maybe just a hacky manually activated switch for now?

I was thinking the same yes. AUX1 or AUX2 for example. Would be quite straight forward and not even require code changes.

sfuhrer avatar Nov 25 '22 10:11 sfuhrer

@sfuhrer I guess we don't need this anymore?

Jaeyoung-Lim avatar Mar 01 '23 20:03 Jaeyoung-Lim