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
Hello, few months ago, I could run the physical robot without any issue. However, I don't know what happened on the robot side but I obtained the error attached which prevent the robot to move.
The command I'm using is used after employing the ssh protocol to connect to the robot.
I have noticed a similar issue in #37 but it was related to Gazebo not the real world.
[ WARN] [1729261108.864033287]: Could not get transform from locobot/base_footprint to locobot/camera_color_optical_frame after 0.200000 seconds (for stamp=1729261108.588759)! Error="Lookup would require extrapolation 0.064006459s into the future. Requested time 1729261108.588758945 but the latest data is at time 1729261108.524752378, when looking up transform from frame [locobot/camera_color_optical_frame] to frame [locobot/base_footprint]. canTransform returned after 0.201054 timeout was 0.2.".
[ERROR] [1729261108.864143017]: TF of received image 0 at time 1729261108.588759s is not set!
[ERROR] [1729261108.864258575]: Could not convert rgb/depth msgs! Aborting rtabmap update...
Additional Info
No response
The text was updated successfully, but these errors were encountered:
What happened?
Hello, few months ago, I could run the physical robot without any issue. However, I don't know what happened on the robot side but I obtained the error attached which prevent the robot to move.
The command I'm using is used after employing the ssh protocol to connect to the robot.
I have noticed a similar issue in #37 but it was related to Gazebo not the real world.
Robot Model
locobot_wx250s
Operating System
Ubuntu 20.04
ROS Distro
ROS 1 Noetic
Steps To Reproduce
roslaunch interbotix_xslocobot_nav xslocobot_nav.launch robot_model:=locobot_wx250s use_lidar:=true rtabmap_args:=-d
Relevant log output
Additional Info
No response
The text was updated successfully, but these errors were encountered: