33ROS 2 integration paths
44=======================
55
6- There are different paths to use a Universal Robots arm with ROS 2:
6+ There are different paths to use a Universal Robots arm with ROS 2.
7+
8+ ROS 2 on the robot
9+ ------------------
710
8111. Starting with PolyScope X v10.7.0 the robots have builtin ROS 2 support that allows some amount
912 of interaction with the robot without the need of any ROS 2 driver. In particular, the robot
@@ -12,19 +15,41 @@ There are different paths to use a Universal Robots arm with ROS 2:
1215 <https://docs.universal-robots.com/polyscopex-ros2/v10.7/Appendix/Appendix%202.html> `_ for more
1316 information.
1417
15- .. note ::
16-
17- The builtin ROS 2 support will only be compatible with the ROS distribution running on the
18- robot. For example, PolyScope 10.7.0 is running ROS 2 Humble. It should not be used with
19- any other distribution.
2018
21192. Starting with PolyScope X v10.7.0 there is basic URScript support for ROS 2. This allows
2220 publishing to and subscribing from ROS 2 topics directly in URScript as well as calling ROS 2
2321 services and actions from URScript. See `Basic Usage in URScript
2422 <https://docs.universal-robots.com/polyscopex-ros2/v10.7/Basic%20Usage%20in%20URScript.html> `_
2523 for details on that.
26- 3. Using the :ref: `ur_robot_driver ` which is a ROS 2 driver that offers full `ros2_control
27- <https://control.ros.org> `_ compatibility. This allows visualizing the robot's state in RViz and
28- control its motions through ROS 2. It works with CB3, e-Series (PolyScope 5) and PolyScope X robots.
2924
30- The ROS 2 driver uses the :ref: `ur_client_library ` to communicate with the robot.
25+ .. note ::
26+
27+ The builtin ROS 2 support will only be compatible with the ROS distribution running on the
28+ robot. For example, PolyScope 10.7.0 is running ROS 2 Humble. It should not be used with
29+ any other distribution.
30+
31+ Control the robot from an external ROS 2 application
32+ ----------------------------------------------------
33+
34+ Using the :ref: `ur_robot_driver ` which is a ROS 2 driver that offers full `ros2_control
35+ <https://control.ros.org> `_ compatibility. This allows visualizing the robot's state in RViz and
36+ control its motions through ROS 2. It works with CB3, e-Series (PolyScope 5) and PolyScope X robots.
37+
38+ Use the ROS 2 driver to build your own application on the ROS framework leveraging available
39+ drivers for other hardware components, sensor integration and ready-to-use software functionalities
40+ such as collision-aware path-planning.
41+
42+ The ROS 2 driver uses the :ref: `ur_client_library ` to communicate with the robot.
43+
44+ Build your own external application using the C++ library
45+ ---------------------------------------------------------
46+
47+ With the standalone C++ library ":ref: `ur_client_library `" you can control a UR robot from a remote
48+ application. It offers a lot of the functionality that traditionally the robot's teach pendant
49+ would be used for. This includes
50+
51+ - Controlling the robot's power state
52+ - Controlling the robot's motion
53+ - Controlling the robot's I/O ports
54+ - Access to low-level interfaces such as the Primary Interface, Dashboard Interface and the
55+ Realtime Data Exchange (RTDE).
0 commit comments