Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Nicogene authored Nov 29, 2024
1 parent 13666d0 commit 0e585f3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions iCub_manual/ros2/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
:warning: The ROS2 support is in beta :warning:

This directory contains the files related for using `iCubGazeboV3` with ROS2. The contents of this directory are installed inside `iCub`.
This directory contains the files related for using `iCubGazeboV*` with ROS2. The contents of this directory are installed inside `iCub`.
ros2 package. The location of `iCub` ros pacakge is discovered by running `roscd iCub`.
The `launch` directory contains `launch.py` file `robot_state_publisher.launch.py`. The robot model
that will be used depends `YARP_ROBOT_NAME` set in `.bashrc`.
Expand All @@ -13,7 +13,7 @@ Right now are published on ROS2 topics:

The steps to run rviz visualization correctly are:

- Edit `iCubGazeboV3/model.urdf` putting [`icub_ROS2.xml`](https://github.com/robotology/robots-configuration/blob/devel/iCub/conf_icub3/wrappers/icub_ROS2.xml) `robotinterface` xml file used at startup.
- Edit `iCubGazeboV*/model.urdf` putting [`icub_ROS2.xml`](https://github.com/robotology/robots-configuration/blob/devel/iCub/conf_icub3/wrappers/icub_ROS2.xml) `robotinterface` xml file used at startup.
- Ensure that the robot is started correctly with ros configuration files for motor control boards.
- On starting the robot, one should see `/<prefix>/joint_states` ros topic by running `ros2 topic list`.
Also, ensure that the `/<prefix>/joint_states` streams all the robot joint angles by running
Expand Down

0 comments on commit 0e585f3

Please sign in to comment.