Skip to content
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

whether the "effort" in "/joint_states" topic stand for the joint torques of UR? #286

Closed
TianXu1991 opened this issue Nov 10, 2020 · 1 comment

Comments

@TianXu1991
Copy link

Summary

Introduction to the issue
Hi, fmauch.
In order to idetify the dynamic parameters of UR, I need to read the joint positions, joint velocities and joint torques of UR. I guess the "position" and "velocity" in the "sensor_msgs/JointState" stand for "joint positions" and "joint velocities" in the "/joint_states" topic, respectively. However, I'm not sure whether the meaning of "effort" stand for joint torques of UR.
Screenshot from 2020-11-10 10-07-42

Versions

  • ROS Driver version: Melodic
  • UR: UR10
  • URCaps Software version(s): 1.0.4

Impact

What is the impact of the issue. Try to describe it well enough, in order for us to prioritise the issues.
Dynamic parameters of robot is necessary for designing the model-based observer, such as collision detection observer. In order to identify these parameters of UR, joint positions, joint velocities and joint torques of UR are needed to read.

Issue details

This part is important in order to clarify the severity of the issue.
I want to read the joint torques of UR, but I'm not sure whether the meaning of "effort" in "/joint_states" topic stand for joint torques of UR?
If the "effort" is not the joint torques, how can I get the joint torque readings from this driver? Maybe this issue can be related to #35.

Expected Behavior

What did you expect and why?
I expect to read the joint positions, joint velocities and joint torques of UR for dynamic parameter identification.

@fmauch
Copy link
Collaborator

fmauch commented Nov 15, 2020

Please see the discussion in #146

@fmauch fmauch closed this as completed Nov 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants