Skip to content

Commit f5e084a

Browse files
author
Felix Exner
committed
Added a documentation section about adapting the robot_description
1 parent 4b34e68 commit f5e084a

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -247,6 +247,22 @@ Use this with any client interface such as [MoveIt!](https://moveit.ros.org/) or
247247
rosrun rqt_joint_trajectory_controller rqt_joint_trajectory_controller
248248
```
249249

250+
### Replacing the robot description
251+
252+
In a real-world scenario you will want to replace the robot description with a description
253+
containing the whole scene where the robot is acting in. For this, all the bringup launchfiles offer
254+
the argument `robot_description_file` that should point to a launchfile loading the robot
255+
description.
256+
257+
While the `load_urXXX.launch` files from the [ur_description](http://wiki.ros.org/ur_description)
258+
package contain a lot of arguments to change the robot model, this driver only forwards the
259+
`kinematics_config` parameter file. For further adaption please create your own `load_urXXX.launch`
260+
file that fits your application and pass this to the `urXXX_bringup.launch` files from this package.
261+
262+
If you prefer decoupling loading the robot description and starting the driver, you can start the
263+
`ur_control.launch` launchfile directly after the `robot_description` has been uploaded to the
264+
parameter server.
265+
250266
## Troubleshooting
251267

252268
This section will cover some previously raised issues.

0 commit comments

Comments
 (0)