We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was trying to run my X4 with slam_toolbox, but when I launched slam_toolbox I kept receiving an error message stating:
LaserRangeScan contains 719 range readings, expected 720
Here is the header of the /scan topic:
header: seq: 4289 stamp: secs: 1631644371 nsecs: 564544000 frame_id: "base_scan" angle_min: -3.14159274101 angle_max: 3.14159274101 angle_increment: 0.00869043637067 time_increment: 0.000199999994948 scan_time: 0.130799993873 range_min: 0.10000000149 range_max: 12.0
I tried with the older package from YDLIDAR/ydlidar_ros and it worked just fine... I realize that angle_increment was a little different:
header: seq: 128 stamp: secs: 1631645675 nsecs: 389754000 frame_id: "laser_frame" angle_min: -3.14159274101 angle_max: 3.14159274101 angle_increment: 0.00873878411949 time_increment: 0.000200000009499 scan_time: 0.130600005388 range_min: 0.10000000149 range_max: 12.0
Do you have any clue why there is this difference?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was trying to run my X4 with slam_toolbox, but when I launched slam_toolbox I kept receiving an error message stating:
LaserRangeScan contains 719 range readings, expected 720
Here is the header of the /scan topic:
I tried with the older package from YDLIDAR/ydlidar_ros and it worked just fine... I realize that angle_increment was a little different:
Do you have any clue why there is this difference?
The text was updated successfully, but these errors were encountered: