Closed bodkal closed 3 months ago
Did you start the external control program on the teach pendant after starting the driver (e.g. after ros2 launch ur_robot_driver ur_control.launch.py [...]
)? When this is started you should see the lines
[ur_ros2_control_node-1] [INFO] [1712574636.743142775] [UR_Client_Library:]: Robot requested program
[ur_ros2_control_node-1] [INFO] [1712574636.743210885] [UR_Client_Library:]: Sent program to robot
[ur_ros2_control_node-1] [INFO] [1712574636.789046949] [UR_Client_Library:]: Robot connected to reverse interface. Ready to receive control commands.
in your controller log. Alternatively you can use headless mode.
update: i find how to eanable the external control and now it is working. can i anable the external control by default? or from code?
tanks for the replay. I'm using the script from the ur_client_library, so the external control should be enabled from the beginning.
And it looks like the external control is enabled.
i dont see the log you provided in my terminal. any idea?
URsim has the urcap installed, but no program using it and also doesn't start it directly (which wouldn't work, because you have to start the driver on the PC first). Please look at the already linked headless mode if you want to start the program automatically on driver startup.
@bodkal Since the above comment seems to be an adequate solution, I will go ahead and close this issue. If the issue still persists and/or you would like to comment something more, feel free to do so and/or reopen this issue.
Affected ROS2 Driver version(s)
humble
Used ROS distribution.
Humble
Which combination of platform is the ROS driver running on.
Ubuntu Linux with standard kernel
How is the UR ROS2 Driver installed.
From binary packets
Which robot platform is the driver connected to.
URSim in docker
Robot SW / URSim version(s)
ros2 run ur_client_library start_ursim.sh -m ur10e
How is the ROS driver used.
Headless without using the teach pendant
Issue details
Summary
whan i trray to execute path using moveit with real hardwer i get: MoveGroupInterface::execute() failed or timeout reached.
Issue details
i can move the arm useng the topic /urscript_interface/script_command. in addisen if i move the arm in the docker i can see it moveing in rviz. on fake harwer it working as expected.
logs for ur_robot_driver:
logs for moveit:
controllers logs:
Steps to Reproduce
i run in 3 terminals:
ros2 launch ur_robot_driver ur_control.launch.py ur_type:=ur10e robot_ip:=192.168.56.101 launch_rviz:=false use_fake_hardware:=false
ros2 run ur_client_library start_ursim.sh -m ur10e
ros2 launch ur_moveit_config ur_moveit.launch.py ur_type:=ur10e launch_rviz:=true
then try to move the arm useing the rviz plagin (move from code dosent work as well)
Expected Behavior
arm move to goal.
Actual Behavior
arm dosent move.
Relevant log output
No response
Accept Public visibility