Skip to content

Commit f6a7328

Browse files
committed
Added a documentation section about adapting the robot_description
1 parent c4cfef3 commit f6a7328

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
@@ -200,6 +200,22 @@ Use this with any client interface such as [MoveIt!](https://moveit.ros.org/) or
200200
rosrun rqt_joint_trajectory_controller rqt_joint_trajectory_controller
201201
```
202202

203+
### Replacing the robot description
204+
205+
In a real-world scenario you will want to replace the robot description with a description
206+
containing the whole scene where the robot is acting in. For this, all the bringup launchfiles offer
207+
the argument `robot_description_file` that should point to a launchfile loading the robot
208+
description.
209+
210+
While the `load_urXXX.launch` files from the [ur_description](http://wiki.ros.org/ur_description)
211+
package contain a lot of arguments to change the robot model, this driver only forwards the
212+
`kinematics_config` parameter file. For further adaption please create your own `load_urXXX.launch`
213+
file that fits your application and pass this to the `urXXX_bringup.launch` files from this package.
214+
215+
If you prefer decoupling loading the robot description and starting the driver, you can start the
216+
`ur_control.launch` launchfile directly after the `robot_description` has been uploaded to the
217+
parameter server.
218+
203219
## Troubleshooting
204220

205221
This section will cover some previously raised issues.

0 commit comments

Comments
 (0)