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

Added README parts of the default controller topics

Browse Source
This commit is contained in:
Felix Mauch
2019-06-27 15:23:22 +02:00
parent 487b8b55ae
commit e7b1ea5b33
1 changed files with 21 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@@ -26,10 +26,13 @@ Create an issue on the [Issue Board](https://gitlab.com/ur_ros_beta/universal_ro
control from ROS side. Expect this to come in future releases. control from ROS side. Expect this to come in future releases.
* Use the robot's **speed-scaling**. When speed scaling is active due to safety constraints or the * Use the robot's **speed-scaling**. When speed scaling is active due to safety constraints or the
speed slider is used, this gets correctly handled on the ROS side, as well slowing down speed slider is used, this gets correctly handled on the ROS side, as well slowing down
trajectory execution accordingly. **Note**: Due to the speed scaling interface, other controllers trajectory execution accordingly.<br/>
than the scaled controllers provided, currently cannot be used. We plan to change this in **Note**: Other ros-controllers based on a position interface
upcoming releases. can be used with this driver, but may behave wrong if the speed slider isn't set to 100% or if
speed scaling slows down the robot. Also, the pausing function can only be used, if the default
scaled trajectory controller is used.
## Contents
This repository contains the new **ur_rtde_driver** and a couple of helper packages, such as: This repository contains the new **ur_rtde_driver** and a couple of helper packages, such as:
* **controller_stopper**: A small external tool that stops and restarts ros-controllers based on * **controller_stopper**: A small external tool that stops and restarts ros-controllers based on
@@ -191,3 +194,18 @@ Once the robot driver is started, load the previously generated program on the r
execute it. From that moment on the robot is fully functional. You can make use of the pause execute it. From that moment on the robot is fully functional. You can make use of the pause
function or even stop the program. Simply press the play button again and the ROS driver will function or even stop the program. Simply press the play button again and the ROS driver will
reconnect. reconnect.
#### Use the action server
After starting up the robot as described in the last section a scaled position based trajectory
controller is started. It's action-server is located at
```bash
/scaled_pos_traj_controller/follow_joint_trajectory
```
Use this with any client interface such as MoveIt! or simply the joint_trajectory_controller rqt
gui:
```
rosrun rqt_joint_trajectory_controller rqt_joint_trajectory_controller
```