-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generically expose URDF joint dynamics. #56
base: rolling
Are you sure you want to change the base?
Generically expose URDF joint dynamics. #56
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be fine. But as I'm not an expert, I don't see myself in a position to approve the commit.
…alRobots/Universal_Robots_ROS2_Description into dz/expose-joint-dyn-prop-file
…nzimmerman/Universal_Robots_ROS2_Description into dz/expose-joint-dyn-prop-file
This should likely wait and build on top of #59 or equivalent. |
@@ -41,14 +41,15 @@ | |||
<mesh filename="${mesh}"/> | |||
</xacro:macro> | |||
|
|||
<xacro:macro name="read_model_data" params="joint_limits_parameters_file kinematics_parameters_file physical_parameters_file visual_parameters_file force_abs_paths"> | |||
<xacro:macro name="read_model_data" params="joint_limits_parameters_file kinematics_parameters_file physical_parameters_file visual_parameters_file joint_dynamics force_abs_paths"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I would prefer passing the filename down to here as we do with the other parameters, as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I am not sure. It would be nicer to keep it on one level, however this way it is backwards compatible.
This is aimed at simulation use cases like #54 and #55, where simulation needs dictate different non-zero joint dynamics parameters.
In
ur.urdf.xacro
I provide an example loading the joint dynamics properties from a config file, but followed the treatment ofinitial_positions
so that no config file is necessary to use thexacro:ur_robot
macro in other contexts.For the Gazebo Classic use case, I want to compute the dynamics parameters dynamically from other data, setting the joints'
friction
attributes to a multiple of the joints' effort limits like here.(See discussion in #55 and Universal_Robots_ROS2_Gazebo_Simulation/#19 for context.)
In other user code including
ur_macro.xacro
I think this should not require any changes.