Open leander2189 opened 9 months ago
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
This issue was closed because it has been stalled for 45 days with no activity.
As a follow up of this issue, robot_model_loader must be created with (node, "robot_description") parameters, otherwise the node will not find the kinematic settings, nor joint_limits, nor acceleration limits
Description
Usual way of creating a RobotModelLoader instance is by setting the
Options
field withrobot_description = "robot_description"
. This works ok, and the application will expect the kinematic parameters to be underrobot_description_kinematics
key, just like when launching move_group node.On the other hand when
Options
is build by passing directly both the URDF and SRDF (why wait for a topic when I have access to the files),robot_description
field is never set, and then the application will complain about kinematics not being defined, as it looks for_kinematics
key.This happens even if you manually set
robot_description
field manually inOptions
, as it builds RDFLoader through this line where the attributerobot_description
is never set.Your environment
Steps to reproduce
Init your RobotModelLoader with urdf and srdf instead of robot_description field:
This warning will appear in the log
Expected behaviour
Default behavior (loader expecting kinematics data under
robot_description_kinematics
) should not change depending on which constructor is called, and a method to manually change that key should be exposed, maybe by passing throughrobot_description
field to RDFLoader in every case.