The new driver for Universal Robots UR3, UR5 and UR10 robots with CB3 controllers and the e-series.
Standalone launchfile to startup a ur3e. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Parameter to set the id of the wrench frame, required if using multiple robots
Set the topic on which this robot publishes its speed scaling factor.
Baud rate used for tool communication. Only used, when use_tool_communication is set to true.
Local device name used for tool communication. Only used, when use_tool_communication is set to true.
Parity configuration used for tool communication. Only used, when use_tool_communication is set to true.
Number of idle chars in RX channel used for tool communication. Only used, when use_tool_communication is set to true.
Number of stop bits used for tool communication. Only used, when use_tool_communication is set to true.
Port on which the robot controller publishes the tool comm interface. Only used, when use_tool_communication is set to true.
Number of idle chars in TX channel used for tool communication. Only used, when use_tool_communication is set to true.
Tool voltage set at the beginning of the UR program. Only used, when use_tool_communication is set to true.
On e-Series robots tool communication can be enabled with this argument
Standalone launchfile to startup a ur10 robot. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Robot bringup launchfile without the robot description. Include this, if you want to include robot control into a larger launchfile structure.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller vel_based_pos_joint_traj_controller force_torque_sensor_controller")
Controllers that are activated by default.
If set to true, will start the driver inside gdb
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description. Pass the same config file that is passed to the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Please add description. See file "launch/ur_control.launch".
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
IP address by which the robot can be reached.
Recipe file used for the RTDE-inputs. Only change this if you know what you're doing.
Recipe file used for the RTDE-outputs. Only change this if you know what you're doing.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Baud rate used for tool communication. Only used, when use_tool_communication is set to true.
Local device name used for tool communication. Only used, when use_tool_communication is set to true.
Parity configuration used for tool communication. Only used, when use_tool_communication is set to true.
Number of idle chars in RX channel used for tool communication. Only used, when use_tool_communication is set to true.
Number of stop bits used for tool communication. Only used, when use_tool_communication is set to true.
Port on which the robot controller publishes the tool comm interface. Only used, when use_tool_communication is set to true.
Number of idle chars in TX channel used for tool communication. Only used, when use_tool_communication is set to true.
Tool voltage set at the beginning of the UR program. Only used, when use_tool_communication is set to true.
Path to URScript that will be sent to the robot and that forms the main control program.
On e-Series robots tool communication can be enabled with this argument
Launchfile that starts a robot description with robot_state publisher and the driver for a given robot. It is recommended to use the individual launch files instead such as ur10_bringup.launch. Additionally, this launchfile can be used as a template to include this driver into a larger launch file structure.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_control.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Baud rate used for tool communication. Only used, when use_tool_communication is set to true.
Local device name used for tool communication. Only used, when use_tool_communication is set to true.
Parity configuration used for tool communication. Only used, when use_tool_communication is set to true.
Number of idle chars in RX channel used for tool communication. Only used, when use_tool_communication is set to true.
Number of stop bits used for tool communication. Only used, when use_tool_communication is set to true.
Port on which the robot controller publishes the tool comm interface. Only used, when use_tool_communication is set to true.
Number of idle chars in TX channel used for tool communication. Only used, when use_tool_communication is set to true.
Tool voltage set at the beginning of the UR program. Only used, when use_tool_communication is set to true.
On e-Series robots tool communication can be enabled with this argument
Standalone launchfile to startup a ur5 robot. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Standalone launchfile to startup a ur5e robot. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Baud rate used for tool communication. Only used, when use_tool_communication is set to true.
Local device name used for tool communication. Only used, when use_tool_communication is set to true.
Parity configuration used for tool communication. Only used, when use_tool_communication is set to true.
Number of idle chars in RX channel used for tool communication. Only used, when use_tool_communication is set to true.
Number of stop bits used for tool communication. Only used, when use_tool_communication is set to true.
Port on which the robot controller publishes the tool comm interface. Only used, when use_tool_communication is set to true.
Number of idle chars in TX channel used for tool communication. Only used, when use_tool_communication is set to true.
Tool voltage set at the beginning of the UR program. Only used, when use_tool_communication is set to true.
On e-Series robots tool communication can be enabled with this argument
Standalone launchfile to startup a ur3 robot. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Standalone launchfile to startup a ur10e robot. This requires a robot reachable via a network connection.
Config file used for defining the ROS-Control controllers.
controllers (default: "joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller")
Controllers that are activated by default.
Debug flag that will get passed on to ur_common.launch
Automatically send URScript to robot to execute. On e-Series this does require the robot to be in 'remote-control' mode. With this, the URCap is not needed on the robot.
Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
Note: The default_kinematics.yaml file will not reflect the kinematic parameters of your
robot. Make sure to generate your own config file.
Use the description in limited mode (Every axis rotates from -PI to PI)
Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
Robot description launch file.
IP address by which the robot can be reached.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port. If the robot cannot connect to this port, External Control will stop immediately.
Controllers that are initally loaded, but not started.
tf_prefix used for the robot.
Baud rate used for tool communication. Only used, when use_tool_communication is set to true.
Local device name used for tool communication. Only used, when use_tool_communication is set to true.
Parity configuration used for tool communication. Only used, when use_tool_communication is set to true.
Number of idle chars in RX channel used for tool communication. Only used, when use_tool_communication is set to true.
Number of stop bits used for tool communication. Only used, when use_tool_communication is set to true.
Port on which the robot controller publishes the tool comm interface. Only used, when use_tool_communication is set to true.
Number of idle chars in TX channel used for tool communication. Only used, when use_tool_communication is set to true.
Tool voltage set at the beginning of the UR program. Only used, when use_tool_communication is set to true.
On e-Series robots tool communication can be enabled with this argument
This is the actual driver node containing the ROS-Control stack. Interfaces documented here refer to the robot's hardware interface. Controller-specific API elements might be present for the individual controllers outside of this package.
dashboard/add_to_log (ur_dashboard_msgs/AddToLog)
Service to add a message to the robot's log
dashboard/brake_release (std_srvs/Trigger)
Service to release the brakes. If the robot is currently powered off, it will get powered on on the fly.
dashboard/clear_operational_mode (std_srvs/Trigger)
If this service is called the operational mode can again be changed from PolyScope, and the user password is enabled.
dashboard/close_popup (std_srvs/Trigger)
Close a (non-safety) popup on the teach pendant.
dashboard/close_safety_popup (std_srvs/Trigger)
Close a safety popup on the teach pendant.
dashboard/connect (std_srvs/Trigger)
Service to reconnect to the dashboard server
dashboard/get_loaded_program (ur_dashboard_msgs/GetLoadedProgram)
Load a robot installation from a file
dashboard/get_robot_mode (ur_dashboard_msgs/GetRobotMode)
Service to query the current robot mode
dashboard/get_safety_mode (ur_dashboard_msgs/GetSafetyMode)
Service to query the current safety mode
dashboard/load_installation (ur_dashboard_msgs/Load)
Load a robot installation from a file
dashboard/load_program (ur_dashboard_msgs/Load)
Load a robot program from a file
dashboard/pause (std_srvs/Trigger)
Pause a running program.
dashboard/play (std_srvs/Trigger)
Start execution of a previously loaded program
dashboard/popup (ur_dashboard_msgs/Popup)
Service to show a popup on the UR Teach pendant.
dashboard/power_off (std_srvs/Trigger)
Power off the robot motors
dashboard/power_on (std_srvs/Trigger)
Power on the robot motors. To fully start the robot, call 'brake_release' afterwards.
dashboard/program_running (ur_dashboard_msgs/IsProgramRunning)
Query whether there is currently a program running
dashboard/program_saved (ur_dashboard_msgs/IsProgramSaved)
Query whether the current program is saved
dashboard/is_in_remote_control (ur_dashboard_msgs/IsInRemoteControl)
Query whether the robot is currently in remote control mode. This is only available on e-Series models.
dashboard/program_state (ur_dashboard_msgs/GetProgramState)
Service to query the current program state
dashboard/quit (ur_dashboard_msgs/GetLoadedProgram)
Disconnect from the dashboard service.
dashboard/raw_request (ur_dashboard_msgs/RawRequest)
General purpose service to send arbitrary messages to the dashboard server
dashboard/restart_safety (std_srvs/Trigger)
Used when robot gets a safety fault or violation to restart the safety. After safety has been rebooted the robot will be in Power Off. NOTE: You should always ensure it is okay to restart the system. It is highly recommended to check the error log before using this command (either via PolyScope or e.g. ssh connection).
dashboard/shutdown (std_srvs/Trigger)
Shutdown the robot controller
dashboard/stop (std_srvs/Trigger)
Stop program execution on the robot
dashboard/unlock_protective_stop (std_srvs/Trigger)
Dismiss a protective stop to continue robot movements. NOTE: It is the responsibility of the user to ensure the cause of the protective stop is resolved before calling this service.
hand_back_control (std_srvs/Trigger)
Calling this service will make the "External Control" program node on the UR-Program return.
resend_robot_program (std_srvs/Trigger)
When in headless mode, this sends the URScript program to the robot for execution. Use this after the program has been interrupted, e.g. by a protective- or EM-stop.
Service to set any of the robot's IOs
Set the speed slider fraction used by the robot's execution. Values should be between 0 and 1. Only set this smaller than 1 if you are using the scaled controllers (as by default) or you know what you're doing. Using this with other controllers might lead to unexpected behaviors.
Setup the mounted payload through a ROS service
zero_ftsensor (std_srvs/Trigger)
Calling this service will zero the robot's ftsensor. Note: On e-Series robots this will only work when the robot is in remote-control mode.
Timeout after which a call to the dashboard server will be considered failure if no answer has been received.
Names of the joints. Usually, this is given in the controller config file.
Start robot in headless mode. This does not require the 'External Control' URCap to be running on the robot, but this will send the URScript to the robot directly. On e-Series robots this requires the robot to run in 'remote-control' mode.
Path to the file containing the recipe used for requesting RTDE inputs.
Hash of the calibration reported by the robot. This is used for validating the robot description is using the correct calibration. If the robot's calibration doesn't match this hash, an error will be printed. You can use the robot as usual, however Cartesian poses of the endeffector might be inaccurate. See the "ur_calibration" package on help how to generate your own hash matching your actual robot.
Enables non_blocking_read mode. Should only be used with combined_robot_hw. Disables error generated when read returns without any data, sets the read timeout to zero, and synchronises read/write operations. Enabling this when not used with combined_robot_hw can suppress important errors and affect real-time performance.
Path to the file containing the recipe used for requesting RTDE outputs.
Port that will be opened to communicate between the driver and the robot controller.
The robot's IP address.
Path to the urscript code that will be sent to the robot.
Port that will be opened to forward script commands to the robot when in local control mode.
The driver will offer an interface to receive the program's URScript on this port.
Specify gain for servoing to position in joint space. A higher gain can sharpen the trajectory.
Specify lookahead time for servoing to position in joint space. A longer lookahead time can smooth the trajectory.
When the robot's URDF is being loaded with a prefix, we need to know it here, as well, in order to publish correct frame names for frames reported by the robot directly.
Baud rate used for tool communication. Will be set as soon as the UR-Program on the robot is started. See UR documentation for valid baud rates. Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Parity used for tool communication. Will be set as soon as the UR-Program on the robot is started. Can be 0 (None), 1 (odd) and 2 (even). Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Number of idle chars for the RX unit used for tool communication. Will be set as soon as the UR-Program on the robot is started. Valid values: min=1.0, max=40.0 Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Number of stop bits used for tool communication. Will be set as soon as the UR-Program on the robot is started. Can be 1 or 2. Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Number of idle chars for the TX unit used for tool communication. Will be set as soon as the UR-Program on the robot is started. Valid values: min=0.0, max=40.0 Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Tool voltage that will be set as soon as the UR-Program on the robot is started. Note: This parameter is only evaluated, when the parameter "use_tool_communication" is set to TRUE. Then, this parameter is required.
Should the tool's RS485 interface be forwarded to the ROS machine? This is only available on e-Series models. Setting this parameter to TRUE requires multiple other parameters to be set,as well.
robot_program_running (std_msgs/Bool)
Whenever the runtime state of the "External Control" program node in the UR-program changes, a message gets published here. So this is equivalent to the information whether the robot accepts commands from ROS side.
script_command (std_msgs/String)
Send arbitrary script commands to this topic. Note: On e-Series the robot has to be in remote-control mode. Sending scripts to this will stop program execution unless wrapped in a secondary program: sec myProgram(): set_digital_out(0, True) end
add_to_log (ur_dashboard_msgs/AddToLog)
Service to add a message to the robot's log
brake_release (std_srvs/Trigger)
Service to release the brakes. If the robot is currently powered off, it will get powered on on the fly.
clear_operational_mode (std_srvs/Trigger)
If this service is called the operational mode can again be changed from PolyScope, and the user password is enabled.
close_popup (std_srvs/Trigger)
Close a (non-safety) popup on the teach pendant.
close_safety_popup (std_srvs/Trigger)
Close a safety popup on the teach pendant.
connect (std_srvs/Trigger)
Service to reconnect to the dashboard server
get_loaded_program (ur_dashboard_msgs/GetLoadedProgram)
Load a robot installation from a file
get_robot_mode (ur_dashboard_msgs/GetRobotMode)
Service to query the current robot mode
get_safety_mode (ur_dashboard_msgs/GetSafetyMode)
Service to query the current safety mode
load_installation (ur_dashboard_msgs/Load)
Load a robot installation from a file
load_program (ur_dashboard_msgs/Load)
Load a robot program from a file
pause (std_srvs/Trigger)
Pause a running program.
play (std_srvs/Trigger)
Start execution of a previously loaded program
popup (ur_dashboard_msgs/Popup)
Service to show a popup on the UR Teach pendant.
power_off (std_srvs/Trigger)
Power off the robot motors
power_on (std_srvs/Trigger)
Power on the robot motors. To fully start the robot, call 'brake_release' afterwards.
program_running (ur_dashboard_msgs/IsProgramRunning)
Query whether there is currently a program running
program_saved (ur_dashboard_msgs/IsProgramSaved)
Query whether the current program is saved
program_state (ur_dashboard_msgs/GetProgramState)
Service to query the current program state
Disconnect from the dashboard service.
raw_request (ur_dashboard_msgs/RawRequest)
General purpose service to send arbitrary messages to the dashboard server
restart_safety (std_srvs/Trigger)
Used when robot gets a safety fault or violation to restart the safety. After safety has been rebooted the robot will be in Power Off. NOTE: You should always ensure it is okay to restart the system. It is highly recommended to check the error log before using this command (either via PolyScope or e.g. ssh connection).
shutdown (std_srvs/Trigger)
Shutdown the robot controller
stop (std_srvs/Trigger)
Stop program execution on the robot
unlock_protective_stop (std_srvs/Trigger)
Dismiss a protective stop to continue robot movements. NOTE: It is the responsibility of the user to ensure the cause of the protective stop is resolved before calling this service.
Timeout after which a call to the dashboard server will be considered failure if no answer has been received.
The IP address under which the robot is reachable.
This node prints the robot- and safety mode to ROS logging and offers an action to set the robot to a specific mode (e.g. for initial startup or recovery after a protective stop or EM-Stop). It should best be started inside the hardware interface's namespace
dashboard/brake_release (std_srvs/Trigger)
Service to release the robot's brakes
dashboard/play (std_srvs/Trigger)
Service to start UR program execution on the robot
dashboard/power_off (std_srvs/Trigger)
Service to power off the robot
dashboard/power_on (std_srvs/Trigger)
Service to power on the robot
dashboard/restart_safety (std_srvs/Trigger)
Service to restart safety
dashboard/stop (std_srvs/Trigger)
Service to stop UR program execution on the robot
dashboard/unlock_protective_stop (std_srvs/Trigger)
Service to unlock protective stop
robot_mode (ur_dashboard_msgs/RobotMode)
Topic on which the robot_mode is published by the driver
safety_mode (ur_dashboard_msgs/SafetyMode)
Topic on which the safety is published by the driver
This node is used to start the RS485 tunneling interface on the ROS machine. This requires that the RS485 daemon is running on the robot controller and tool communication is enabled on the robot.
By default, socat will create a pty in /dev/pts/N with n being an increasing number. Additionally, a symlink at the given location will be created. Use an absolute path here.
IP address of the robot