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

C271A1 Low level real-time thread issue on dual arm setup #1116

Open
1 task done
kfryhilderbrand opened this issue Oct 1, 2024 · 0 comments
Open
1 task done

C271A1 Low level real-time thread issue on dual arm setup #1116

kfryhilderbrand opened this issue Oct 1, 2024 · 0 comments

Comments

@kfryhilderbrand
Copy link

Affected ROS2 Driver version(s)

Humble

Used ROS distribution.

Humble

Which combination of platform is the ROS driver running on.

Ubuntu Linux with realtime patch

How is the UR ROS2 Driver installed.

From binary packets

Which robot platform is the driver connected to.

UR E-series robot

Robot SW / URSim version(s)

Polyscope 5.15

How is the ROS driver used.

Headless without using the teach pendant, Through the robot teach pendant using External Control URCap

Issue details

Summary

Dual arm setup being controlled from 1 controller manager, trajectory being sent to one robot that fails to execute the trajectory due to a real-time thread error.

Issue details

Running a setup with two UR robots (UR5e and UR10e). The UR10e is running an admittance controller while the UR5e is running a joint trajectory controller (1 controller manager). We are sending a trajectory to the UR5e, but it throws a "Low level real-time thread" error and does not execute the trajectory. We tried jogging the robot to a consistent starting pose (that the trajectory also starts from), but that did not solve the issue.

Expected Behavior

Admittance controller running on UR10e, robot will not move if COM calculations correct. Joint trajectory controller running on UR5e, trajectory being sent and executed on robot.

Actual Behavior

Admittance controller on UR10e ran without issue, trajectory did not run on the UR5e

Workaround Suggestion

Suggested including a Wait or a sync(), but including these within our trajectory executor did not solve the issue.

Relevant log output

No response

Accept Public visibility

  • I agree to make this context public
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

1 participant