You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* - use `tool communication forwarder <https://github.com/UniversalRobots/Universal_Robots_ToolComm_Forwarder_URCap>`_ on e-series
40
-
- yes
38
+
- yes (:ref:`setup-tool-communication`)
41
39
* - use the driver without a teach pendant necessary
42
40
- yes
43
41
* - support of CB1 and CB2 robots
@@ -47,10 +45,18 @@ Feature list and roadmap
47
45
* - use ROS as drop-in for TP-programs
48
46
- yes
49
47
* - headless mode
50
-
- yes
48
+
- yes (:ref:`headless_mode`)
51
49
* - extract calibration from robot
52
-
- yes
50
+
- yes (:ref:`ur_calibration`)
53
51
* - send custom script commands to robot
54
-
- yes
52
+
- yes (:ref:`io_and_status_controller`)
55
53
* - Reconnect on a disconnected robot
56
54
- yes
55
+
* - Freedrive Mode
56
+
- yes (:ref:`freedrive_mode_controller`)
57
+
* - Tool Contact mode
58
+
- yes (:ref:`tool_contact_controller`)
59
+
* - Force Mode
60
+
- yes (:ref:`force_mode_controller`)
61
+
62
+
:raw-html-m2r:`<sup>1</sup>` Velocity-based joint control is implemented in the driver, the velocity-based joint trajectory controller would need tweaking of the gain parameters for each model.
0 commit comments