Closed ismet55555 closed 4 years ago
Never mind.
Although this does happen, the most simple solution is to just use the following endpoint method:
[result, modelID, hardwareVersion, firmwareMajor, firmwareMinor, serialNumber] = GetInfoRequestRPLIDAR(pRPLIDAR)
Here are some clarifications :
Indeed, the behavior you describe about GetInfoRequestRPLIDAR()
was expected.
Note however that in the current state, without RPLIDAR SDK support GetAllSupportedScanModesRPLIDAR()
and GetTypicalScanModeRPLIDAR()
should return an error code (EXIT_NOT_IMPLEMENTED=17
) in result
since they do not do anything (they seem more complicated to implement). Also StartOtherScanRequestRPLIDAR()
should print a message which is unfortunately not visible in Windows terminal to warn that it will only start in Standard
scan mode, and GetOtherScanDataResponseRPLIDAR()
should then silently give Standard
scan data (they might also require some time to be implemented correctly). From what you said some time ago, I wonder if for the RPLIDAR S1, in reality the Standard
and DenseBoost
scan modes give the same data in practice...
Thanks for the clarification!
Yeah in the test script I posted, GetAllSupportedScanModesRPLIDAR()
and GetTypicalScanModeRPLIDAR()
do come back with an error code 17
. I probably should have mentioned that. Just using that script to test some things.
When compiling the interface library without the RPLIDAR SDK support (
ENABLE_RPLIDAR_SDK_SUPPORT
commented out) on a S1 RPLIDAR. LIDAR hardware information returns zeros.However the RPLIDAR still works and acquires in DenseBoost mode and no errors are shown during connection, usage, and disconnection.
The hardware information, however does show when using the following in
RPLIDAR0.txt
:Here is the output to
pRPLIDAR.value
:The script that was used:
The
RPLIDAR0.txt
file contents: