You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have followed the "First-Time Robot Setup Guide¶", and my robot is just drifiting in different directions. After trying to move the Sam robot in this repo, I get the same behavior, even worse.
There are also some misconfiguration:
Because of Gazebo's diff driver plugin's namespace, no cmd_vel commands are received
bt_navigator & controller_server are registered to /odom, while gazebo is publishing to /demo/odom
There is an issue with the time on the tf frames because not all nodes are using the sim time parameter.
For the misconfigurations I have created a PR: #57
For the reason the robot is flying away, I have been batteling it, being able to only mitigate it, but not solve it.
The text was updated successfully, but these errors were encountered:
[bt_navigator-5] [ERROR] [1706987053.543650228] [bt_navigator]: Exception when loading BT: Error at line 14: -> Node not recognized: WouldAPlannerRecoveryHelp
[bt_navigator-5] [ERROR] [1706987053.543975397] [bt_navigator]: Error loading XML file: /opt/ros/iron/share/nav2_bt_navigator/behavior_trees/navigate_to_pose_w_replanning_and_recovery.xml
[lifecycle_manager-8] [ERROR] [1706987053.545413334] [lifecycle_manager_navigation]: Failed to change state for node: bt_navigator
[lifecycle_manager-8] [ERROR] [1706987053.545639442] [lifecycle_manager_navigation]: Failed to bring up all requested nodes. Aborting bringup.
Hi,
I have followed the "First-Time Robot Setup Guide¶", and my robot is just drifiting in different directions. After trying to move the Sam robot in this repo, I get the same behavior, even worse.
There are also some misconfiguration:
For the misconfigurations I have created a PR:
#57
For the reason the robot is flying away, I have been batteling it, being able to only mitigate it, but not solve it.
The text was updated successfully, but these errors were encountered: