Skip to content
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

incorrect command in tutorial #3761

Open
cccccmake opened this issue Jun 27, 2023 · 3 comments · May be fixed by #4928
Open

incorrect command in tutorial #3761

cccccmake opened this issue Jun 27, 2023 · 3 comments · May be fixed by #4928
Labels
help wanted Extra attention is needed

Comments

@cccccmake
Copy link

In the tutorial for ROS2 humble, section Gazebo, the command for visualizing lidar data in riv2 is:

ros2 run ros_gz_bridge parameter_bridge /lidar2@sensor_msgs/msg/LaserScan[ignition.msgs.LaserScan --ros-args -r /lidar2:=/laser_scan

This command is considered as a "bad pattern". However, the following command works:

ros2 run ros_gz_bridge parameter_bridge /lidar2@sensor_msgs/msg/[email protected] --ros-args -r /lidar2:=/laser_scan

@ahcorde
Copy link
Contributor

ahcorde commented Jun 27, 2023

can you open a PR fixing this issue?

@clalancette clalancette added the help wanted Extra attention is needed label Jul 6, 2023
@mjforan
Copy link
Contributor

mjforan commented Aug 21, 2023

The first command works for me. I don't know why you would need a bidirectional bridge for a lidar topic, since data should only be flowing from Gazebo.

@edgar-mycrobez
Copy link

Hello, I also followed the instruction given here and I do get the "bad pattern" error when using the unidirectional command [ . For me it also makes sense to implement a unidirectional communication channel for this example, but it only works for me with the @ option. I am using Ubuntu 22.04, ROS Humble and Gazebo Fortress. Recommendation for using Gazebo Fortress from here. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants