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

Access RTDE variables #315

Open
RisMmi opened this issue Jan 26, 2021 · 1 comment
Open

Access RTDE variables #315

RisMmi opened this issue Jan 26, 2021 · 1 comment
Labels
PR pending A PR exists for this issue

Comments

@RisMmi
Copy link

RisMmi commented Jan 26, 2021

I am new in ROS and currently involved in a project with an UR3e.
I need to access to the RTDE data. I have couple of questions I would be super grateful if you´d help me clarify:

It seems that the variables that I need to access are stated in the following txt:

/ur_robot_driver/resources/rtde_output_recipe.txt

However, I am not sure how would it be possible for me to access to them either from the terminal or from a script.

This subject is also related to issue #35. It seems that what they tried to do here is to publish this data into different topics. Therefore, I would like to know, if the only way of accessing to these variables is through the topics, meaning that I need to install this branch of the driver? If so, after installing this branch of the package, How do the RTDE variables can be seen/printed and what are the specific names of the topics to which these variables are being saved to?

Thanks so much in advance for your time and help!

@fmauch
Copy link
Collaborator

fmauch commented Mar 8, 2021

Yes, #35 would be the way to access arbitrary RTDE data. I'm sorry, this isn't high enough in our priority list currently.

Did this comment not answer your second question, though?

@stefanscherzinger stefanscherzinger added the PR pending A PR exists for this issue label Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR pending A PR exists for this issue
Projects
None yet
Development

No branches or pull requests

3 participants