You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be very useful to have a log (error?) when the robot hits some joint limits.
Consider for example when the robot is in torque mode.
The firmware does not apply the desired torque when the limit is hit, but because no errors is emitted understanding the cause of the robot misbehaviour can be very difficult (also because usually torque-based controllers are quite complicated..)
why you are interested in this? Actually the same problem applies to position/velocity control, but no signals are emitted, the trajectory is simply clamped.
In torque mode the risk is to generate this signal several tens of times in a second.
An high level controller can easily handle this: just check the encoder position vs the joint limits returned by the iLimit yarp interface (+ additional threshold)
I would like to propose a feature request.
It can be very useful to have a log (error?) when the robot hits some joint limits.
Consider for example when the robot is in torque mode.
The firmware does not apply the desired torque when the limit is hit, but because no errors is emitted understanding the cause of the robot misbehaviour can be very difficult (also because usually torque-based controllers are quite complicated..)
cc @randaz81 @marcoaccame
@DanielePucci @traversaro
The text was updated successfully, but these errors were encountered: