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
I just realised that the joint limits in hironx_moveit_config package are not coherent between HiroNX.urdf and joint_limits.yaml.
I'm working with the assumption that the URDF specifies hardware limits, and the MoveIt-specific joint_limits.yaml file can be used to override these values for planning. If that's correct, it makes no sense to plan with velocity limits higher those really supported by the robot hardware.
Is my understanding of how this works incorrect? Are there any real velocity limits that could be introduced in the URDF?
The text was updated successfully, but these errors were encountered:
Quick response/guess is that some information in the URDF in question was made up for certain reason at the time of its creation (just a guess...it might have been more crucial for the manufacturer then, or not available for any reason etc.) so that it's possible that all the info is not necessarily correct.
Related to this, I cannot find which file should be modified to change the velocity limit of joints.
Could you point me which file is actually used with HiroNX ?
I just realised that the joint limits in
hironx_moveit_config
package are not coherent betweenHiroNX.urdf
andjoint_limits.yaml
.I'm working with the assumption that the URDF specifies hardware limits, and the MoveIt-specific
joint_limits.yaml
file can be used to override these values for planning. If that's correct, it makes no sense to plan with velocity limits higher those really supported by the robot hardware.Is my understanding of how this works incorrect? Are there any real velocity limits that could be introduced in the URDF?
The text was updated successfully, but these errors were encountered: