forked from dhled/universal_robot
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add arg prefix #7
Closed
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,130 +1,17 @@ | ||
# Universal Robot | ||
# universal_robot | ||
Forked from [universal_robot](https://github.com/fmauch/universal_robot) | ||
For more information, refer to it. | ||
|
||
[![Build Status](http://build.ros.org/job/Kdev__universal_robot__ubuntu_xenial_amd64/badge/icon)](http://build.ros.org/job/Kdev__universal_robot__ubuntu_xenial_amd64) | ||
[![license - apache 2.0](https://img.shields.io/:license-Apache%202.0-yellowgreen.svg)](https://opensource.org/licenses/Apache-2.0) | ||
[![License](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause) | ||
## Getting Started | ||
Package needed by Universal_Robots_ROS_Driver, not to be used directly. | ||
Modification has been done to simplify Aldo's integration | ||
|
||
[![support level: community](https://img.shields.io/badge/support%20level-community-lightgray.png)](http://rosindustrial.org/news/2016/10/7/better-supporting-a-growing-ros-industrial-software-platform) | ||
|
||
[ROS-Industrial](http://wiki.ros.org/Industrial) Universal Robot meta-package. See the [ROS wiki](http://wiki.ros.org/universal_robot) page for compatibility information and other more information. | ||
|
||
|
||
__Installation__ | ||
|
||
There are two different ways to install the packages in this repository. The following sections detail installing the packages using the binary distribution and building them from source in a Catkin workspace. | ||
|
||
|
||
___Using apt (Ubuntu, Debian)___ | ||
|
||
On supported Linux distributions (Ubuntu, up to 16.04 (Xenial), `i386` and `amd64`) and ROS versions: | ||
|
||
``` | ||
sudo apt-get install ros-$ROS_DISTRO-universal-robot | ||
``` | ||
|
||
replace `$ROS_DISTRO` with `hydro`, `indigo` or `kinetic`, depending on which ROS version you have installed. | ||
|
||
|
||
___Building from Source___ | ||
|
||
There are releases available for ROS Hydro, Indigo and Kinetic. However, for the latest features and developments you might want to build the packages from source. | ||
|
||
**NOTE**: please prefer using the binary release (see previous section) over building from source where possible. Source installs will not be automatically updated by new package releases and require more work to setup. | ||
|
||
The following instructions assume that a [Catkin workspace](http://wiki.ros.org/catkin/Tutorials/create_a_workspace) has been created at `$HOME/catkin_ws` and that the source space is at `$HOME/catkin_ws/src`. Update paths appropriately if they are different on the build machine. | ||
|
||
In all other cases the packages will have to be build from sources in a Catkin workspace: | ||
|
||
``` | ||
cd $HOME/catkin_ws/src | ||
|
||
# retrieve the sources (replace '$ROS_DISTRO' with the ROS version you are using) | ||
git clone -b $ROS_DISTRO-devel https://github.com/ros-industrial/universal_robot.git | ||
|
||
cd $HOME/catkin_ws | ||
|
||
# checking dependencies (again: replace '$ROS_DISTRO' with the ROS version you are using) | ||
rosdep update | ||
rosdep install --rosdistro $ROS_DISTRO --ignore-src --from-paths src | ||
|
||
# building | ||
catkin_make | ||
|
||
# activate this workspace | ||
source $HOME/catkin_ws/devel/setup.bash | ||
``` | ||
|
||
|
||
__Usage__ | ||
|
||
___With real Hardware___ | ||
There are launch files available to bringup a real robot - either UR5 or UR10. | ||
In the following the commands for the UR5 are given. For the UR10, simply replace the prefix accordingly. | ||
|
||
Don't forget to source the correct setup shell files and use a new terminal for each command! | ||
|
||
To bring up the real robot, run: | ||
|
||
```roslaunch ur_bringup ur5_bringup.launch robot_ip:=IP_OF_THE_ROBOT [reverse_port:=REVERSE_PORT]``` | ||
|
||
|
||
CAUTION: | ||
Remember that you should always have your hands on the big red button in case there is something in the way or anything unexpected happens. | ||
|
||
|
||
___MoveIt! with real Hardware___ | ||
Additionally, you can use MoveIt! to control the robot. | ||
There exist MoveIt! configuration packages for both robots. | ||
|
||
For setting up the MoveIt! nodes to allow motion planning run: | ||
|
||
```roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch``` | ||
|
||
For starting up RViz with a configuration including the MoveIt! Motion Planning plugin run: | ||
|
||
```roslaunch ur5_moveit_config moveit_rviz.launch config:=true``` | ||
|
||
|
||
NOTE: | ||
As MoveIt! seems to have difficulties with finding plans for the UR with full joint limits [-2pi, 2pi], there is a joint_limited version using joint limits restricted to [-pi,pi]. In order to use this joint limited version, simply use the launch file arguments 'limited', i.e.: | ||
|
||
```roslaunch ur_bringup ur5_bringup.launch limited:=true robot_ip:=IP_OF_THE_ROBOT [reverse_port:=REVERSE_PORT]``` | ||
|
||
```roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch limited:=true``` | ||
|
||
```roslaunch ur5_moveit_config moveit_rviz.launch config:=true``` | ||
|
||
|
||
___Usage with Gazebo Simulation___ | ||
There are launch files available to bringup a simulated robot - either UR5 or UR10. | ||
In the following the commands for the UR5 are given. For the UR10, simply replace the prefix accordingly. | ||
|
||
Don't forget to source the correct setup shell files and use a new terminal for each command! | ||
|
||
To bring up the simulated robot in Gazebo, run: | ||
|
||
```roslaunch ur_gazebo ur5.launch``` | ||
|
||
|
||
___MoveIt! with a simulated robot___ | ||
Again, you can use MoveIt! to control the simulated robot. | ||
|
||
For setting up the MoveIt! nodes to allow motion planning run: | ||
|
||
```roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch sim:=true``` | ||
|
||
For starting up RViz with a configuration including the MoveIt! Motion Planning plugin run: | ||
|
||
```roslaunch ur5_moveit_config moveit_rviz.launch config:=true``` | ||
|
||
|
||
NOTE: | ||
As MoveIt! seems to have difficulties with finding plans for the UR with full joint limits [-2pi, 2pi], there is a joint_limited version using joint limits restricted to [-pi,pi]. In order to use this joint limited version, simply use the launch file arguments 'limited', i.e.: | ||
|
||
```roslaunch ur_gazebo ur5.launch limited:=true``` | ||
|
||
```roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch sim:=true limited:=true``` | ||
|
||
```roslaunch ur5_moveit_config moveit_rviz.launch config:=true``` | ||
## Authors | ||
* **Dufay Gaëtan** - *Initial work* - [steliaRT](https://github.com/steliaRT) | ||
|
||
## License | ||
This project is licensed under Stelia Aerospace License | ||
|
||
## See also | ||
* [universal_robot](https://github.com/fmauch/universal_robot) | ||
* [Universal_Robots_ROS_Driver](https://github.com/steliaRT/Universal_Robots_ROS_Driver) | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not completely replace the README file.