Replies: 1 comment 3 replies
-
The culprit can probably be found in your output:
This usually happens when a fieldbus (Either Ethernet/IP or Profinet) is enabled. See https://docs.universal-robots.com/Universal_Robots_ROS2_Documentation/doc/ur_robot_driver/ur_robot_driver/doc/usage/toc.html#when-starting-the-driver-it-crashes-with-variable-speed-slider-mask-is-currently-controlled-by-another-rtde-client |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello. I am following the given steps on github and UR documentation (https://docs.universal-robots.com/Universal_Robots_ROS2_Documentation/index.html#). But the driver does not get activated properly. Subnet and default gateways of both remote PC and robot are matched. the Ping command is also a success. I could gather the calibration file also from the robot. but when trying to launch the driver , The teaching pendant of the robot says
Below is the error I get on remote PC when trying to launch the driver using the prompt '''ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur3 robot_ip:=<> launch_rviz:=true
'''.
Error:
There are no other remote PCs connected to the UR3, just this active PC and its teaching pendant. Highly appreciate if you can assist me to find a solution for this error. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions