If certain inputs were passed to trajectory planner, an expression inside the trajectory planner which is an argument to sqrtf() could become negative due to finite floating point accuracy.
This led to Vr_ == NaN and then Tf_ == 0, causing the trajectory to jump to the final setpoint instantaneously. To the user, this manifested as a sudden increase in velocity (limited by controller.config.vel_limit) and/or an overcurrent fault.
This bug was likely to show up when constantly sending trajectory setpoints while moving in the negative direction.
See also: https://discourse.odriverobotics.com/t/move-to-pos-not-works-well/4626
Unknown
Oskar Weigl
Samuel Sadok