I bought a mapper module from Slamtec and I'm currently having issues pulling lidar data directly from my S1 RpLidar(without it being connected to the mapper module) when it's connected directly to my computer through USB:
OS
Ubuntu 18.04 / Windows 10
Firmware
1.27 Hardware Revision 17
SDK
1.10 - 1.12
With the proper udev rules set on the /dev/ttyUSB0 if on linux.
When running the ultra_simple example, I'm having an issue where the grabScanDataHq function will call the _waitCapsuledNode function from rplidar_driver.cpp but when it hits the _chanDev->waitfordata() call, it always returns RESULT_OPERATION_TIMEOUT. Would there be any reason the S1 would connect but not be able to receive lidar data when running?
When touching the lidar unit, it also seems like the motors are not spinning. It may relate to the issue at hand. But the startMotors() function is being called from the example code.
I bought a mapper module from Slamtec and I'm currently having issues pulling lidar data directly from my S1 RpLidar(without it being connected to the mapper module) when it's connected directly to my computer through USB:
With the proper udev rules set on the /dev/ttyUSB0 if on linux.
When running the ultra_simple example, I'm having an issue where the grabScanDataHq function will call the _waitCapsuledNode function from rplidar_driver.cpp but when it hits the _chanDev->waitfordata() call, it always returns RESULT_OPERATION_TIMEOUT. Would there be any reason the S1 would connect but not be able to receive lidar data when running?
When touching the lidar unit, it also seems like the motors are not spinning. It may relate to the issue at hand. But the startMotors() function is being called from the example code.