Which SBC(Single Board Computer) is working on TurtleBot3?
[ ] Intel Joule 570x
[ ] Raspberry Pi 3B+
[x] Raspberry Pi 4
[ ] etc (Please specify your SBC here)
Which OS you installed on SBC?
[ ] Raspbian distributed by ROBOTIS
[x] Ubuntu MATE (16.04/18.04/20.04)
[ ] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)
Which OS you installed on Remote PC?
[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[x] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)
Specify the software and firmware version(Can be found from Bringup messages)
Software version: Noetic
Firmware version: turtlebot3_msgs/VersionInfo
Copy and Paste the error messages on terminal.
Extrapolation Error: Lookup would require extrapolation 0.003984088s into the future. Requested time 1703667865.989929199 but the latest data is at time 1703667865.985944986, when looking up transform from frame [odom] to frame [map]
[ERROR] [1703667865.990101947]: Global Frame: odom Plan Frame size 22: map
[ WARN] [1703667865.990149510]: Could not transform the global plan to the frame of the controller
[ERROR] [1703667865.990196793]: Could not get local plan
got new plan
got new plan
got new plan
Extrapolation Error: Lookup would require extrapolation 0.003984088s into the future. Requested time 1703667865.989929199 but the latest data is at time 1703667865.985944986, when looking up transform from frame [odom] to frame [map]
[ERROR] [1703667865.990101947]: Global Frame: odom Plan Frame size 22: map
[ WARN] [1703667865.990149510]: Could not transform the global plan to the frame of the controller
[ERROR] [1703667865.990196793]: Could not get local plan
got new plan
got new plan
goal reached
Please describe the issue in detail.
I'm currently facing an error in my robot navigation system, particularly related to the exploration error as mentioned earlier Interestingly, this error occurs more frequently for the robot equipped with the LDS 01 sensor compared to the one with the LDS 02 sensor. In my troubleshooting efforts, I'm exploring the possibility of using Cartographer localization instead of AMCL.
During this investigation, I've noticed differences in the configuration files between the two sensors. I've successfully located the configuration files for LDS 02 in a GitHub repository, but unfortunately, I'm unable to find the configuration files for LDS 01.
To address this issue more effectively, I'm looking for assistance in obtaining the configuration files for LDS 01. It would be helpful to compare the configurations of both sensors to gain insights and potentially resolve the discrepancies causing the exploration error.
The location of the LDS 02 config file is as follows: turtlebot3_slam/config/turtlebot3_lds_2d.lua
ISSUE TEMPLATE ver. 0.4.0
Which TurtleBot3 platform do you use?
Which ROS is working with TurtleBot3?
Which SBC(Single Board Computer) is working on TurtleBot3?
Which OS you installed on SBC?
Which OS you installed on Remote PC?
Specify the software and firmware version(Can be found from Bringup messages)
Copy and Paste the error messages on terminal. Extrapolation Error: Lookup would require extrapolation 0.003984088s into the future. Requested time 1703667865.989929199 but the latest data is at time 1703667865.985944986, when looking up transform from frame [odom] to frame [map]
[ERROR] [1703667865.990101947]: Global Frame: odom Plan Frame size 22: map
[ WARN] [1703667865.990149510]: Could not transform the global plan to the frame of the controller [ERROR] [1703667865.990196793]: Could not get local plan got new plan got new plan got new plan Extrapolation Error: Lookup would require extrapolation 0.003984088s into the future. Requested time 1703667865.989929199 but the latest data is at time 1703667865.985944986, when looking up transform from frame [odom] to frame [map]
[ERROR] [1703667865.990101947]: Global Frame: odom Plan Frame size 22: map
[ WARN] [1703667865.990149510]: Could not transform the global plan to the frame of the controller [ERROR] [1703667865.990196793]: Could not get local plan got new plan got new plan goal reached
I'm currently facing an error in my robot navigation system, particularly related to the exploration error as mentioned earlier Interestingly, this error occurs more frequently for the robot equipped with the LDS 01 sensor compared to the one with the LDS 02 sensor. In my troubleshooting efforts, I'm exploring the possibility of using Cartographer localization instead of AMCL.
During this investigation, I've noticed differences in the configuration files between the two sensors. I've successfully located the configuration files for LDS 02 in a GitHub repository, but unfortunately, I'm unable to find the configuration files for LDS 01.
To address this issue more effectively, I'm looking for assistance in obtaining the configuration files for LDS 01. It would be helpful to compare the configurations of both sensors to gain insights and potentially resolve the discrepancies causing the exploration error.
The location of the LDS 02 config file is as follows: turtlebot3_slam/config/turtlebot3_lds_2d.lua