forked from gazebosim/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Rename Ignition to Gazebo in ci.md Signed-off-by: Nate Koenig <[email protected]> * Rename Ignition to Gazebo in contributing.md Signed-off-by: Nate Koenig <[email protected]> * Rename Ignition to Gazebo in release_features.md Signed-off-by: Nate Koenig <[email protected]> * Rename ignition to gazebo in release.md Signed-off-by: Nate Koenig <[email protected]> * Rename ignition in readme, and yaml files Signed-off-by: Nate Koenig <[email protected]> * Update releases.md Signed-off-by: Nate Koenig <[email protected]> * Rename ign in acropolis Signed-off-by: Nate Koenig <[email protected]> Co-authored-by: Nate Koenig <[email protected]>
- Loading branch information
Showing
5 changed files
with
53 additions
and
53 deletions.
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
File renamed without changes
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,20 +4,20 @@ Please refer to the latest supported version.** | |
|
||
# ROS Integration | ||
|
||
Most of the Ignition libraries use [Ignition Transport](https://github.com/gazebosim/gz-transport) | ||
Most of the Gazebo libraries use [Gazebo Transport](https://github.com/gazebosim/gz-transport) | ||
to exchange data between different software components. This tutorial details | ||
how to interface with [ROS](http://www.ros.org/), enabling the ability to use | ||
tools such as [Rviz](http://wiki.ros.org/rviz) for robot or sensor | ||
visualization. | ||
|
||
# ros1_ign_bridge to the rescue | ||
# ros1_gz_bridge to the rescue | ||
|
||
ros1_ign_bridge provides a network bridge which enables the exchange of messages | ||
between ROS 1 and Ignition Transport. Its support is limited to only certain | ||
ros1_gz_bridge provides a network bridge which enables the exchange of messages | ||
between ROS 1 and Gazebo Transport. Its support is limited to only certain | ||
message types. Please, read this [README](https://github.com/osrf/ros1_ign_bridge) | ||
to verify if your message type is supported by the bridge. | ||
|
||
# How to install ros1_ign_bridge | ||
# How to install ros1_gz_bridge | ||
|
||
## Binary install | ||
|
||
|
@@ -37,7 +37,7 @@ sudo apt install ros-melodic-desktop ros-melodic-rqt-image-view libignition-comm | |
|
||
# Run the bridge and exchange images | ||
|
||
In this example, we're going to generate Ignition Transport images using Gazebo, that will be converted into ROS 1 images, and visualized with rqt_viewer. | ||
In this example, we're going to generate Gazebo Transport images using Gazebo, that will be converted into ROS 1 images, and visualized with rqt_viewer. | ||
|
||
First we start a ROS 1 `roscore`: | ||
|
||
|
@@ -51,15 +51,15 @@ Then we start Gazebo. | |
|
||
```bash | ||
# Shell B: | ||
ign-gazebo -r -f camera_sensor.sdf | ||
gz sim -r -f camera_sensor.sdf | ||
``` | ||
|
||
Gazebo should be running and publishing images over the `/camera` topic. | ||
Let's verify it: | ||
|
||
```bash | ||
# Shell C: | ||
ign topic -l | grep "^/camera" | ||
gz topic -l | grep "^/camera" | ||
/camera | ||
``` | ||
|
||
|
@@ -68,7 +68,7 @@ Then we start the parameter bridge with the previous topic. | |
```bash | ||
# Shell D: | ||
. ~/bridge_ws/install/setup.bash | ||
rosrun ros1_ign_bridge parameter_bridge /camera@sensor_msgs/[email protected] | ||
rosrun ros1_gz_bridge parameter_bridge /camera@sensor_msgs/[email protected] | ||
``` | ||
|
||
Now we start the ROS 1 GUI: | ||
|
@@ -80,10 +80,10 @@ rqt_image_view /camera | |
``` | ||
|
||
You should see the current images in `rqt_image_view` which are coming from | ||
Gazebo (published as Ignition Msgs over Ignition Transport). | ||
Gazebo (published as Gazebo Msgs over Gazebo Transport). | ||
|
||
The screenshot shows all the shell windows and their expected content | ||
(it was taken using ROS Melodic): | ||
|
||
|
||
![Ignition Transport images and ROS 1 rqt](images/bridge_image_exchange_ign-gazebo.png) | ||
![Gazebo Transport images and ROS 1 rqt](images/bridge_image_exchange_gz-sim.png) |