Package Summary

Tags No category tags.
Version 2.1.4
License Apache-2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/UniversalRobots/Universal_Robots_ROS_Driver.git
VCS Type git
VCS Version master
Last Updated 2024-04-17
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The new driver for Universal Robots UR3, UR5 and UR10 robots with CB3 controllers and the e-series.

Additional Links

Maintainers

  • Felix Exner

Authors

  • Thomas Timm Andersen
  • Simon Rasmussen
  • Felix Exner
  • Lea Steffen
  • Tristan Schnell

ur_robot_driver

This package contains the actual driver for UR robots. It is part of the universal_robots_driver repository and requires other packages from that repository. Also, see the main repository's README for information on how to install and startup this driver.

ROS-API

The ROS API is documented in a standalone document. It is auto-generated using catkin_doc.

Technical details

The following image shows a very coarse overview of the driver's architecture.

Architecture overview

Upon connection to the primary interface the robot sends version and calibration information which is consumed by the calibration_check. If the calibration reported by the robot doesn't match the one configured (See calibration guide) an error will be printed to Roslog.

Real-time data from the robot is read through the RTDE interface. This is done automatically as soon as a connection to the robot could be established. Thus joint states and IO data will be immediately available.

To actually control the robot, a program node from the External Control URCap must be running on the robot interpreting commands sent from an external source. When this program is not running, no controllers moving the robot around will be available, which is handled by the controller_stopper. Please see the initial setup guide on how to install and start this on the robot.

The URScript that will be running on the robot is requested by the External Control program node from the remote ROS PC. The robot ur_control.launch file has a parameter called urscript_file to select a different program than the default one that will be sent as a response to a program request.

Custom script snippets can be sent to the robot on a topic basis. By default, they will interrupt other programs (such as the one controlling the robot). For a certain subset of functions, it is however possible to send them as secondary programs. See UR documentation on details.
Note to e-Series users: The robot won't accept script code from a remote source unless the robot is put into remote_control-mode. However, if put into remote_control-mode, the program containing the External Control program node can't be started from the panel. For this purpose, please use the dashboard services to load, start and stop the main program running on the robot. See the ROS-API documentation for details on the dashboard services.

For using the tool communication interface on e-Series robots, a socat script is prepared to forward the robot's tool communication interface to a local device on the ROS PC. See the tool communication setup guide for details.

This driver is using ROS-Control for any control statements. Therefore, it can be used with all position-based controllers available in ROS-Control. However, we recommend using the controllers from the scaled_trajectory_controller package. See its documentation for details. Note: Speed scaling support will only be available using the controllers from scaled_trajectory_controller

A note about modes

The term mode is used in different meanings inside this driver.

Remote control mode

On the e-series the robot itself can operate in different command modes: It can be either in local control mode where the teach pendant is the single point of command or in remote control mode, where motions from the TP, starting & loading programs from the TP activating the freedrive mode are blocked. Note that the remote control mode has to be explicitly enabled in the robot's settings under Settings -> System -> Remote Control. See the robot's manual for details.

The remote control mode is needed for many aspects of this driver such as * headless mode (see below) * sending script code to the robot * many dashboard functionalities such as * restarting the robot after protective / EM-Stop * powering on the robot and do brake release * loading and starting programs * the set_mode action, as it uses the dashboard calls mentioned above

Headless mode

Inside this driver, there's the headless mode, which can be either enabled or not. When the headless mode is activated, required script code for external control will be sent to the robot directly when the driver starts. As soon as other script code is sent to the robot either by sending it directly through this driver or by pressing any motion-related button on the teach pendant, the script will be overwritten by this action and has to be restarted by using the resend_robot_program service. If this is necessary, you will see the output Connection to robot dropped, waiting for new connection. from the driver. Note that pressing "play" on the TP won't start the external control again, but whatever program is currently loaded on the controller. This mode doesn't require the "External Control" URCap being installed on the robot as the program is sent to the robot directly. However, we recommend to use the non-headless mode and leverage the set_mode action to start program execution without the teach pendant. The headless mode might be removed in future releases.

Note for the e-Series: In order to leverage the headless mode on the e-Series the robot must be in remote_control_mode as explained above.

CHANGELOG

2.1.4 (2024-04-08)

  • Added support for UR30 (#688)
  • Added arg to enable/disable launch of ursim (#679)
  • Contributors: Vincenzo Di Pentima, mahp

2.1.3 (2023-12-18)

  • Added support for UR20 (#659)
  • Update documentation (#655)
  • Bump required cmake version to fix the CMake warning about CMP0048
  • Change initializer list ordering to match declaration in header file
  • Implemented spline interpolation in joint space (#543)
  • Use dedicated build for noetic main (#640)
  • fix typo and use ros logging
  • Contributors: Felix Exner, Felix Exner (fexner), Mads Holm Peters, RobertWilbrandt, Simon Schmeisser

2.1.2 (2023-01-23)

2.1.1 (2023-01-23)

  • Move controller_stopper to ur_robot_driver Since a standalone package with that name was declined during the release process, we decided to move the controller_stopper package over to the driver.
  • Update minimal required polyscope version in docs
  • Contributors: Felix Exner

2.1.0 (2022-12-08)

  • delete ros_control.urscript (#593) We\'ve been using the script from the library for a while now
  • Use the RobotMode message inside the SetMode action (#381) This way we can make use of the predefined constants inside the RobotMode message.
  • Make several members of hw_interface atomic, for thread safety (#448) Co-authored-by: Felix Exner (fexner) <exner@fzi.de>
  • Updated transformForceTorque to handle wheter it is a cb3 or an e-Series robot (#566) The force torque is returned at the tool flange on e-series robots and at the tcp for CB3, this is now handled correctly, so that all force/torque measurements will be relative to the active TCP
  • Updated set payload, zero ftsensor and set tool voltage to use the ur... (#567) * Updated set payload, zero ftsensor and set tool voltage to use the urdriver This makes it possible to call the commands when the robot is in local control if the external control script is running on the robot.

    • Update ROS interface docs

    * Fix argument passing in include instruction Co-authored-by: Miguel Prada <miguel.prada@tecnalia.com>

  • Remove URCap installation files from driver and replace references (#580) Link to the respective Github release pages instead.

  • Drop old C++ compiler flags (#577) Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>

  • Fix MoveIt! command in Example (#575)

  • Allow empty stopped_controllers argument. (#572)

  • Dashboard service to query whether the robot is in remote control (#561)

    • new dashboard msg to check remote control
  • test_move: Load controller only if it is not already loaded (#552)

  • Add optional topic rename for speed scaling factor (#544)

    • Add optional topic rename for speed scaling factor
    • Update ROS_INTERFACE.md
  • Wait for controller action server in test_move. (#535)

  • Minor update to display robot_ip parameter without _ (#521)

  • Make hw_interface-node required-argument optional (#450) The UR-robot is only one part of our roslaunch-setup, so I would like to be able to have the rest of the system (non-UR) continue to run even if the ur_hardware_interface-node dies.

  • Fix test move python3 (#492) * make test_move work with python2 and python3 As suggested in http://wiki.ros.org/UsingPython3/SourceCodeChanges#Changing_shebangs

    • Use a version-independent shebang
    • Use catkin_install_python to install the test_move script
  • Update feature list (#490) Some minor formatting and reducing the wrench features to one features to make it more clear.

  • Contributors: Adam Heins, AndyZe, Felix Exner, Felix Exner (fexner), Johnson, Mads Holm Peters, Michael G

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/ur_control.launch
      • debug [default: false] — If set to true, will start the driver inside gdb
      • use_tool_communication — On e-Series robots tool communication can be enabled with this argument
      • controller_config_file — Config file used for defining the ROS-Control controllers.
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • kinematics_config — 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.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller force_torque_sensor_controller robot_status_controller]
      • stopped_controllers [default: joint_group_vel_controller forward_joint_traj_controller forward_cartesian_traj_controller]
      • urscript_file [default: $(find ur_client_library)/resources/external_control.urscript] — Path to URScript that will be sent to the robot and that forms the main control program.
      • rtde_output_recipe_file [default: $(find ur_robot_driver)/resources/rtde_output_recipe.txt] — Recipe file used for the RTDE-outputs. Only change this if you know what you're doing.
      • rtde_input_recipe_file [default: $(find ur_robot_driver)/resources/rtde_input_recipe.txt] — Recipe file used for the RTDE-inputs. Only change this if you know what you're doing.
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • servoj_gain [default: 2000] — Specify gain for servoing to position in joint space. A higher gain can sharpen the trajectory.
      • servoj_lookahead_time [default: 0.03] — Specify lookahead time for servoing to position in joint space. A longer lookahead time can smooth the trajectory.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
      • use_spline_interpolation [default: true] — True if splines should be used as interpolation on the robot controller when forwarding trajectory, if false movej or movel commands are used
  • launch/ur5_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur5_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur5.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur5/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur10_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur10_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur10.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur10/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur30_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur30_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur30.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur30/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur3e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur3e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur3e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur3e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur5e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur5e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur5e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur5e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur3_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur3_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur3.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur3/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur10e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur10e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur10e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur10e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur16e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur16e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur16e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur16e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur_common.launch
      • debug [default: false] — Debug flag that will get passed on to ur_control.launch
      • use_tool_communication — On e-Series robots tool communication can be enabled with this argument
      • controller_config_file — Config file used for defining the ROS-Control controllers.
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • kinematics_config — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller robot_status_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • robot_description_file — Robot description launch file.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
      • use_spline_interpolation [default: true] — True if splines should be used as interpolation on the robot controller when forwarding trajectory, if false movej or movel commands are used
  • launch/ur20_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur20_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur20.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur20/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/example_rviz.launch

Messages

No message files found.

Services

No service files found

Recent questions tagged ur_robot_driver at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 2.1.4
License Apache-2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/UniversalRobots/Universal_Robots_ROS_Driver.git
VCS Type git
VCS Version master
Last Updated 2024-04-17
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The new driver for Universal Robots UR3, UR5 and UR10 robots with CB3 controllers and the e-series.

Additional Links

Maintainers

  • Felix Exner

Authors

  • Thomas Timm Andersen
  • Simon Rasmussen
  • Felix Exner
  • Lea Steffen
  • Tristan Schnell

ur_robot_driver

This package contains the actual driver for UR robots. It is part of the universal_robots_driver repository and requires other packages from that repository. Also, see the main repository's README for information on how to install and startup this driver.

ROS-API

The ROS API is documented in a standalone document. It is auto-generated using catkin_doc.

Technical details

The following image shows a very coarse overview of the driver's architecture.

Architecture overview

Upon connection to the primary interface the robot sends version and calibration information which is consumed by the calibration_check. If the calibration reported by the robot doesn't match the one configured (See calibration guide) an error will be printed to Roslog.

Real-time data from the robot is read through the RTDE interface. This is done automatically as soon as a connection to the robot could be established. Thus joint states and IO data will be immediately available.

To actually control the robot, a program node from the External Control URCap must be running on the robot interpreting commands sent from an external source. When this program is not running, no controllers moving the robot around will be available, which is handled by the controller_stopper. Please see the initial setup guide on how to install and start this on the robot.

The URScript that will be running on the robot is requested by the External Control program node from the remote ROS PC. The robot ur_control.launch file has a parameter called urscript_file to select a different program than the default one that will be sent as a response to a program request.

Custom script snippets can be sent to the robot on a topic basis. By default, they will interrupt other programs (such as the one controlling the robot). For a certain subset of functions, it is however possible to send them as secondary programs. See UR documentation on details.
Note to e-Series users: The robot won't accept script code from a remote source unless the robot is put into remote_control-mode. However, if put into remote_control-mode, the program containing the External Control program node can't be started from the panel. For this purpose, please use the dashboard services to load, start and stop the main program running on the robot. See the ROS-API documentation for details on the dashboard services.

For using the tool communication interface on e-Series robots, a socat script is prepared to forward the robot's tool communication interface to a local device on the ROS PC. See the tool communication setup guide for details.

This driver is using ROS-Control for any control statements. Therefore, it can be used with all position-based controllers available in ROS-Control. However, we recommend using the controllers from the scaled_trajectory_controller package. See its documentation for details. Note: Speed scaling support will only be available using the controllers from scaled_trajectory_controller

A note about modes

The term mode is used in different meanings inside this driver.

Remote control mode

On the e-series the robot itself can operate in different command modes: It can be either in local control mode where the teach pendant is the single point of command or in remote control mode, where motions from the TP, starting & loading programs from the TP activating the freedrive mode are blocked. Note that the remote control mode has to be explicitly enabled in the robot's settings under Settings -> System -> Remote Control. See the robot's manual for details.

The remote control mode is needed for many aspects of this driver such as * headless mode (see below) * sending script code to the robot * many dashboard functionalities such as * restarting the robot after protective / EM-Stop * powering on the robot and do brake release * loading and starting programs * the set_mode action, as it uses the dashboard calls mentioned above

Headless mode

Inside this driver, there's the headless mode, which can be either enabled or not. When the headless mode is activated, required script code for external control will be sent to the robot directly when the driver starts. As soon as other script code is sent to the robot either by sending it directly through this driver or by pressing any motion-related button on the teach pendant, the script will be overwritten by this action and has to be restarted by using the resend_robot_program service. If this is necessary, you will see the output Connection to robot dropped, waiting for new connection. from the driver. Note that pressing "play" on the TP won't start the external control again, but whatever program is currently loaded on the controller. This mode doesn't require the "External Control" URCap being installed on the robot as the program is sent to the robot directly. However, we recommend to use the non-headless mode and leverage the set_mode action to start program execution without the teach pendant. The headless mode might be removed in future releases.

Note for the e-Series: In order to leverage the headless mode on the e-Series the robot must be in remote_control_mode as explained above.

CHANGELOG

2.1.4 (2024-04-08)

  • Added support for UR30 (#688)
  • Added arg to enable/disable launch of ursim (#679)
  • Contributors: Vincenzo Di Pentima, mahp

2.1.3 (2023-12-18)

  • Added support for UR20 (#659)
  • Update documentation (#655)
  • Bump required cmake version to fix the CMake warning about CMP0048
  • Change initializer list ordering to match declaration in header file
  • Implemented spline interpolation in joint space (#543)
  • Use dedicated build for noetic main (#640)
  • fix typo and use ros logging
  • Contributors: Felix Exner, Felix Exner (fexner), Mads Holm Peters, RobertWilbrandt, Simon Schmeisser

2.1.2 (2023-01-23)

2.1.1 (2023-01-23)

  • Move controller_stopper to ur_robot_driver Since a standalone package with that name was declined during the release process, we decided to move the controller_stopper package over to the driver.
  • Update minimal required polyscope version in docs
  • Contributors: Felix Exner

2.1.0 (2022-12-08)

  • delete ros_control.urscript (#593) We\'ve been using the script from the library for a while now
  • Use the RobotMode message inside the SetMode action (#381) This way we can make use of the predefined constants inside the RobotMode message.
  • Make several members of hw_interface atomic, for thread safety (#448) Co-authored-by: Felix Exner (fexner) <exner@fzi.de>
  • Updated transformForceTorque to handle wheter it is a cb3 or an e-Series robot (#566) The force torque is returned at the tool flange on e-series robots and at the tcp for CB3, this is now handled correctly, so that all force/torque measurements will be relative to the active TCP
  • Updated set payload, zero ftsensor and set tool voltage to use the ur... (#567) * Updated set payload, zero ftsensor and set tool voltage to use the urdriver This makes it possible to call the commands when the robot is in local control if the external control script is running on the robot.

    • Update ROS interface docs

    * Fix argument passing in include instruction Co-authored-by: Miguel Prada <miguel.prada@tecnalia.com>

  • Remove URCap installation files from driver and replace references (#580) Link to the respective Github release pages instead.

  • Drop old C++ compiler flags (#577) Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>

  • Fix MoveIt! command in Example (#575)

  • Allow empty stopped_controllers argument. (#572)

  • Dashboard service to query whether the robot is in remote control (#561)

    • new dashboard msg to check remote control
  • test_move: Load controller only if it is not already loaded (#552)

  • Add optional topic rename for speed scaling factor (#544)

    • Add optional topic rename for speed scaling factor
    • Update ROS_INTERFACE.md
  • Wait for controller action server in test_move. (#535)

  • Minor update to display robot_ip parameter without _ (#521)

  • Make hw_interface-node required-argument optional (#450) The UR-robot is only one part of our roslaunch-setup, so I would like to be able to have the rest of the system (non-UR) continue to run even if the ur_hardware_interface-node dies.

  • Fix test move python3 (#492) * make test_move work with python2 and python3 As suggested in http://wiki.ros.org/UsingPython3/SourceCodeChanges#Changing_shebangs

    • Use a version-independent shebang
    • Use catkin_install_python to install the test_move script
  • Update feature list (#490) Some minor formatting and reducing the wrench features to one features to make it more clear.

  • Contributors: Adam Heins, AndyZe, Felix Exner, Felix Exner (fexner), Johnson, Mads Holm Peters, Michael G

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/ur_control.launch
      • debug [default: false] — If set to true, will start the driver inside gdb
      • use_tool_communication — On e-Series robots tool communication can be enabled with this argument
      • controller_config_file — Config file used for defining the ROS-Control controllers.
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • kinematics_config — 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.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller force_torque_sensor_controller robot_status_controller]
      • stopped_controllers [default: joint_group_vel_controller forward_joint_traj_controller forward_cartesian_traj_controller]
      • urscript_file [default: $(find ur_client_library)/resources/external_control.urscript] — Path to URScript that will be sent to the robot and that forms the main control program.
      • rtde_output_recipe_file [default: $(find ur_robot_driver)/resources/rtde_output_recipe.txt] — Recipe file used for the RTDE-outputs. Only change this if you know what you're doing.
      • rtde_input_recipe_file [default: $(find ur_robot_driver)/resources/rtde_input_recipe.txt] — Recipe file used for the RTDE-inputs. Only change this if you know what you're doing.
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • servoj_gain [default: 2000] — Specify gain for servoing to position in joint space. A higher gain can sharpen the trajectory.
      • servoj_lookahead_time [default: 0.03] — Specify lookahead time for servoing to position in joint space. A longer lookahead time can smooth the trajectory.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
      • use_spline_interpolation [default: true] — True if splines should be used as interpolation on the robot controller when forwarding trajectory, if false movej or movel commands are used
  • launch/ur5_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur5_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur5.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur5/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur10_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur10_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur10.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur10/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur30_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur30_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur30.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur30/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur3e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur3e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur3e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur3e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur5e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur5e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur5e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur5e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur3_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur3_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur3.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur3/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur10e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur10e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur10e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur10e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur16e_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur16e_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur16e.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur16e/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/ur_common.launch
      • debug [default: false] — Debug flag that will get passed on to ur_control.launch
      • use_tool_communication — On e-Series robots tool communication can be enabled with this argument
      • controller_config_file — Config file used for defining the ROS-Control controllers.
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • kinematics_config — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller robot_status_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • robot_description_file — Robot description launch file.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
      • use_spline_interpolation [default: true] — True if splines should be used as interpolation on the robot controller when forwarding trajectory, if false movej or movel commands are used
  • launch/ur20_bringup.launch
      • debug [default: false] — Debug flag that will get passed on to ur_common.launch
      • robot_ip — IP address by which the robot can be reached.
      • reverse_ip [default: ] — IP of the driver, if set to empty it will detect it automatically.
      • reverse_port [default: 50001] — Port that will be opened by the driver to allow direct communication between the driver and the robot controller.
      • script_sender_port [default: 50002] — 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.
      • trajectory_port [default: 50003] — Port that will be opened by the driver to allow trajectory forwarding.
      • script_command_port [default: 50004] — Port that will be opened by the driver to allow forwarding script commands to the robot.
      • tf_prefix [default: ] — tf_prefix used for the robot.
      • controllers [default: joint_state_controller scaled_pos_joint_traj_controller speed_scaling_state_controller force_torque_sensor_controller] — Controllers that are activated by default.
      • stopped_controllers [default: pos_joint_traj_controller joint_group_vel_controller] — Controllers that are initally loaded, but not started.
      • controller_config_file [default: $(find ur_robot_driver)/config/ur20_controllers.yaml] — Config file used for defining the ROS-Control controllers.
      • robot_description_file [default: $(find ur_description)/launch/load_ur20.launch] — Robot description launch file.
      • kinematics_config [default: $(find ur_description)/config/ur20/default_kinematics.yaml] — Kinematics config file used for calibration correction. This will be used to verify the robot's calibration is matching the robot_description.
      • use_tool_communication [default: false] — On e-Series robots tool communication can be enabled with this argument
      • tool_voltage [default: 0] — Tool voltage set at the beginning of the UR program. Only used, when `use_tool_communication` is set to true.
      • tool_parity [default: 0] — Parity configuration used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_baud_rate [default: 115200] — Baud rate used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_stop_bits [default: 1] — Number of stop bits used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_rx_idle_chars [default: 1.5] — Number of idle chars in RX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tx_idle_chars [default: 3.5] — Number of idle chars in TX channel used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_device_name [default: /tmp/ttyUR] — Local device name used for tool communication. Only used, when `use_tool_communication` is set to true.
      • tool_tcp_port [default: 54321] — Port on which the robot controller publishes the tool comm interface. Only used, when `use_tool_communication` is set to true.
      • headless_mode [default: false] — 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.
      • ur_hardware_interface_node_required [default: true] — Shut down ros environment if ur_hardware_interface-node dies.
  • launch/example_rviz.launch

Messages

No message files found.

Services

No service files found

Recent questions tagged ur_robot_driver at Robotics Stack Exchange