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

Update README.md

Browse Source 
Added instructions on where to find packages needed when using ros_control
This commit is contained in:
HurchelYoung
2016-11-17 07:27:03 -08:00
committed by GitHub
parent 814364dd1f
commit a410f99400
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -52,6 +52,10 @@ If you want to test it in your current setup, just use the modified launch files
--- ---
If you would like to use the ros\_control-based approach, use the launch files urXX\_ros\_control.launch, where XX is '5' or '10' depending on your robot. If you would like to use the ros\_control-based approach, use the launch files urXX\_ros\_control.launch, where XX is '5' or '10' depending on your robot.
**Note** If you are using the ros\_control-based approach you will need 2 packages that can be found in the ur\_driver package. Simply copy these packages into your workspace /src folder.
* urXX_movit_config
* ur_description
The driver currently supports two position trajectory controllers; a position based and a velocity based. They are both loaded via the launch file, but only one of them can be running at the same time. By default the velocity based controller is started. You can switch controller by calling the appropriate service: The driver currently supports two position trajectory controllers; a position based and a velocity based. They are both loaded via the launch file, but only one of them can be running at the same time. By default the velocity based controller is started. You can switch controller by calling the appropriate service:
``` ```
rosservice call /universal_robot/controller_manager/switch_controller "start_controllers: rosservice call /universal_robot/controller_manager/switch_controller "start_controllers: