After an actuator faults, cmd_velocity on the motor controller remains last commanded velocity and does not get resetted from Reset() command. Therefore, any consequent profiled command would generate a profile starting from residual commanded velocity, causing an actuator to move in undesired way
Suggested solution
Generate a profile with initial velocity of "actual velocity"
cmd_velocity
on the motor controller remains last commanded velocity and does not get resetted from Reset() command. Therefore, any consequent profiled command would generate a profile starting from residual commanded velocity, causing an actuator to move in undesired way