Closed marcoag closed 2 months ago
No issues with documentation, it is clear and can be followed. Except for installation instruction since apt
package does not exist yet.
Error arose from lack of jazzy
support in webots. Also an error in webots_controller
, see image below.
http://packages.ros.org/ros2-testing/ubuntu noble InRelease
: only available packages in jazzy
are ros-jazzy-webots-ros2-importer
, ros-jazzy-webots-ros2-msgs
and ros-jazzy-webots-ros2-tests
. jazzy
support in CMakeLists.txt
, particularly in webots_ros2_driver
. Modifying it to add jazzy
allows python to be found and compiles successfully.Able to launch ros2 launch webots_ros2_universal_robot multirobot_launch.py
Got error in webots_controller
[INFO] [webots_controller_abbirb4600-4]: process started with pid [1021926]
[webots_controller_abbirb4600-4] Error: No link elements found in urdf file
[webots_controller_abbirb4600-4] at line 207 in ./urdf_parser/src/model.cpp
[webots_controller_abbirb4600-4] Failed to parse robot description using: urdf_xml_parser/URDFXMLParser
[webots_controller_abbirb4600-4] terminate called after throwing an instance of 'std::runtime_error'
[webots_controller_abbirb4600-4] what(): URDF cannot be parsed by a `ros2_control` component parser:
[ERROR] [webots_controller_abbirb4600-4]: process has died [pid 1021926, exit code 250, cmd '/home/user/webots_ws/install/webots_ros2_driver/share/webots_ros2_driver/scripts/webots-controller --robot-name=abbirb4600 --protocol=ipc --port=1234 ros2 --ros-args -r __ns:=/abb -p robot_description:=/home/user/webots_ws/install/webots_ros2_universal_robot/share/webots_ros2_universal_robot/resource/webots_abb_description.urdf -p use_sim_time:=True --params-file /home/user/webots_ws/install/webots_ros2_universal_robot/share/webots_ros2_universal_robot/resource/ros2_control_abb_config.yaml'].
Reported the missing packages in the issue above. Thanks for the checks @samuel-ongzx!
Check the documentation for the 'Installation Ubuntu' page
Configuration
Links
Process
Step 1 - I was able to follow the documentation.
Step 2 - The documentation seemed clear to me.
Step 3 - The documentation didn't have any obvious errors.