Obbart/universal_robots_ros_driver
1
0
Fork 0
mirror of https://gitlab.com/obbart/universal_robots_ros_driver.git synced 2026-04-09 17:40:47 +02:00
Code Releases Activity

updated feature list to current development

Browse Source
This commit is contained in:
Felix Mauch
2019-08-08 17:06:59 +02:00
parent 423c6833c3
commit a1a6ec1680
1 changed files with 6 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
ur_rtde_driver/doc/features.md
View File

@@ -11,26 +11,23 @@
| continue trajectories after EM-Stop resume | - | yes | | continue trajectories after EM-Stop resume | - | yes |
| continue trajectories after protective stop | - | yes | | continue trajectories after protective stop | - | yes |
| panel interaction in between possible | no<sup>1</sup> | yes | | panel interaction in between possible | no<sup>1</sup> | yes |
| get and set IO states | yes | planned | | get and set IO states | yes | yes |
| use tool communication on e-series | - | yes | | use tool communication on e-series | - | yes |
| use the driver without a teach pendant necessary | - | planned | | use the driver without a teach pendant necessary | - | planned |
| support of CB2 robots | yes | - | | support of CB2 robots | yes | - |
| trajectory extrapolation on robot on missing packages | no<sup>2</sup> | yes | | trajectory extrapolation on robot on missing packages | no<sup>2</sup> | yes |
| use ROS as drop-in for TP-programs | - | planned<sup>3</sup> | | use ROS as drop-in for TP-programs | - | yes |
| extract calibration from robot | - | yes | | extract calibration from robot | - | yes |
| send custom script commands to robot | yes | planned | | send custom script commands to robot | yes | yes |
| ROS 2 support | ? | (planned)<sup>4</sup> | | ROS 2 support | ? | (planned)<sup>3</sup> |
| Reconnect on a disconnected robot | yes | in progress | | Reconnect on a disconnected robot | yes | yes |
<sup>1</sup> Depending on the mode the driver is running the panel won't react or using the panel <sup>1</sup> Depending on the mode the driver is running the panel won't react or using the panel
will stop the program without notifying the ROS user. will stop the program without notifying the ROS user.
<sup>2</sup> In velocity mode this is implicitly given. <sup>2</sup> In velocity mode this is implicitly given.
<sup>3</sup> Currently, you can use ROS as the last element in a program, but handing back control <sup>3</sup> There is no specific plan to do this inside of the first driver development. However,
to the TP is not yet implemented.
<sup>4</sup> There is no specific plan to do this inside of the first driver development. However,
it is structured in a way so that a ROS2 driver should be developed as easy as possible by keeping it is structured in a way so that a ROS2 driver should be developed as easy as possible by keeping
as much as possible in a ros-independent library. as much as possible in a ros-independent library.