Replies: 2 comments 1 reply
-
Controller manager comes from the external dependency
step. You are correct that without the controller manager, the robot won't run correctly. |
Beta Was this translation helpful? Give feedback.
-
Can you attach the full text of the application startup from when you initiate the command? I wonder if something is dying earlier in the startup process, sometimes it can be hidden because gazebo is starting up so many things simultaneously. I just tested a fresh checkout of galactic on my computer and it started up without issues. |
Beta Was this translation helpful? Give feedback.
-
How are you connecting to your Create 3?
Wi-Fi (ROS 2)
Computer(s) Model(s) and Operating System(s)
Ubuntu 22.04
Which version of ROS 2 is installed on your computer?
Humble
Which firmware version is installed on your robot?
H.1.2
Which RMW is your robot running?
CycloneDDS
Does your robot have an assigned namespace? If so, please share.
No response
Is the robot connected to a network? If so, what is the network type?
yes
Are there multiple Create 3 robots connected to your network?
No
Is multicast enabled?
No
What is the Adapter Board's USB/BLE Toggle currently switched to?
USB
Describe your question.
Hello everyone,
I'm currently attempting to launch the Gazebo simulation of Create 3 by using the following command: ros2 launch irobot_create_gazebo_bringup create3_gazebo_aws_small.launch.py. Gazebo and rviz2 start up successfully, but I'm encountering some errors in the command terminal:
I suspect that these errors are causing the robot to not respond to the \dock and \undock actions. When I try to execute these actions, the system responds with: "Undock Goal Aborted."
I would greatly appreciate it if someone could provide assistance in resolving this issue.
Thank you very much.
Best regards,
Beta Was this translation helpful? Give feedback.
All reactions