Skip to content

Commit d1f8f39

Browse files
committed
Added note of ur16 support status to README
1 parent 535d3e9 commit d1f8f39

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,15 @@ To make sure that robot control isn't affected by system latencies, it is highly
9191
a real-time kernel with the system. See the [real-time setup guide](ur_robot_driver/doc/real_time.md)
9292
on information how to set this up.
9393

94+
## Preliminary UR16e support
95+
This driver supports all UR variants including the UR16e. However, upstream support for the UR16e is
96+
not finished, yet. When using the UR16e there is currently no support for gazebo or MoveIt!.
97+
98+
See [#97](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/pull/97) for details on
99+
using the latest upstream develop branch of
100+
[ros_industrial/universal_robot](https://github.com/ros-industrial/universal_robot) which includes
101+
gazebo support for the ur16e, but no working MoveIt! support at the time of writing.
102+
94103
## Building
95104

96105
```bash
@@ -166,7 +175,7 @@ To actually start the robot driver use one of the existing launch files
166175

167176
$ roslaunch ur_robot_driver <robot_type>_bringup.launch robot_ip:=192.168.56.101
168177

169-
where **<robot_type>** is one of *ur3, ur5, ur10, ur3e, ur5e, ur10e*. Note that in this example we
178+
where **<robot_type>** is one of *ur3, ur5, ur10, ur3e, ur5e, ur10e, ur16e*. Note that in this example we
170179
load the calibration parameters for the robot "ur10_example".
171180

172181
If you calibrated your robot before, pass that calibration to the launch file:

0 commit comments

Comments
 (0)