-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
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
RPLiDAR Node Crashes with std::bad_array_new_length
#136
Comments
grwells
changed the title
No Scan Data Published by rplidar_composition Node
RPLiDAR Node Crashes with Oct 3, 2023
std::bad_array_new_length
Notes after further research and discussion in #138:
Conclusion: fixing this bug is not a priority/doesn't have maintainer attention yet, so path of least resistance is to shell out for a new lidar. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I am working through the iRobot Create3 LiDAR SLAM tutorial and have run into the issue that when the rplidar composition node is running, no data is published to the
/scan
topic (partly because waiting for subscriber). Then, as soon as the topic is subscribed to, the rplidar node crashes with:Comments
ros2 launch create3_lidar_slam sensors_launch.py
RPLiDAR health status: OK
ros2 topic echo /scan
I am running Pop!_OS, ROS2 Humble, RPLiDAR ROS2 flavor of
rplidar_ros
repo, and have replicated these results on several different machines including my desktop and the RPi 4 I am using on the Create3.As far as I can tell, this is an error internal to the
rplidar_ros
package, in the source code, but debug information is insufficient for someone unfamiliar with the project to trace. Some research indicates this is an array related error, but documentation in the code is scarce enough I would welcome any input before swimming through the code.The text was updated successfully, but these errors were encountered: