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

Publishing Joint Temperature and information #81

Closed
atomoclast opened this issue Nov 22, 2016 · 7 comments
Closed

Publishing Joint Temperature and information #81

atomoclast opened this issue Nov 22, 2016 · 7 comments

Comments

@atomoclast
Copy link

Hello all,

I'm in the process of developing a system with several UR robots and we are using the ur_modern_driver package to allow for us to move the robots with ros_control.

One of the things that has come up recently for our application was monitoring the health of the robots, and we were interested in logging the temperature of the joints of each robot with respect to time. On the UR pendant, on the "Log" tab, we see the temperature being displayed. Is there any way to use the ur_modern_driver package for us to be able to get that information published via ros? Or is there a way to get that data and log it?

Thanks in advance!

@miguelprada
Copy link
Contributor

There should be a way, since that information is sent by the controller through the RT interface and unpacked by RobotStateRT (see the unpacking and the getter).

It should be a matter of reading these values in rosControlLoop and publishing them as desired (I suggest using a realtime_tools::RealtimePublisher, such as this one).

@ThomasTimm
Copy link
Collaborator

ThomasTimm commented Nov 28, 2016

Does any of you have any suggestions as to what message type we should use for this? - preferably something that is already in ROS

@gavanderhoorn
Copy link
Member

sensor_msgs contains a Temperature msg: sensor_msgs/Temperature.

I would suggest to use that.

Perhaps a single publisher would suffice, if we set the frame_id to suitable values.

@ThomasTimm
Copy link
Collaborator

So should we set up 1 (or six) publishers that just publishes joint temperatures, or a more elaborate system state message overview?

@gavanderhoorn
Copy link
Member

A single publisher should be possible:

frame_id is the location of the temperature reading

if the TF frames for the joints are acceptable as 'locations' of the motors.

@gavanderhoorn
Copy link
Member

Probably covered by #120.

@gavanderhoorn
Copy link
Member

This was added in #120: motor temperatures for all joints are published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants