Open ben-greenberg opened 8 months ago
I see that #35 mentions that it is now "Able to produce global plan given a goal pose"
Is this expected to solve my issue?
I don't see what changes would have this impact, but I'm not very familiar with the nav2 stack and BT interface
I can confirm that building the code in that #35 did solve this problem.
What happened?
When given a
/goal_pose
the robot is motionless, we expected it to move to the specified position.After some digging around, it seems that the path planning process is hanging without return a path to be executed. We enabled debug messages and see that the
planner_server
node seems to be stuck.Full log attached, the goal is sent around line 13951 LOG.txt
Questions:
Robot Model
locobot-wx250s
Operating System
Ubuntu 22.04
ROS Distro
ROS 2 Humble
Steps To Reproduce
Following the instructions here we are able to successfully build a map by running slam with the following command and moving the create3 base around with using
teleop_twist_keyboard
However, when we run the localization command:
the robot does not move to the specified goal when a
/goal_pose
message is sent using the 2D Goal Pose interface in rviz (or published from the command line).Relevant log output
Additional Info
Our create3 base is still on galactic. I don't think this is the issue, since we've been able to send and receive messages from it, but figure it's worth mentioning