-
Notifications
You must be signed in to change notification settings - Fork 86
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
Launch file for "full scan" (multiScan) #437
Comments
Thanks for your feedback. I assume the customer is using the sick_scan_xd API without ROS. There is no need to adjust the launch file to get the full frame point clouds with all layers. The callback registered with "SickScanApiRegisterCartesianPointCloudMsg" is called for the segments and for the full frame point clouds. The segment_idx of the message is -1 for fullframe point clouds (or the segment index otherwise). To process only the fullframe point clouds, just use Note that custom point clouds are only supported with ROS. The API only provides the cartesian point clouds with fields (x,y,z,intensity) and the polar point clouds with fields (range,azimuth,elvation,intensity). Each scan (full frame or segmented) contains the scan points of different layers. The layer of a scan point can be derived from the elevation angle if necessary. If the callback is not called (or is called only once), the error is probably different. A common error is a wrong or empty It is recommended to use SOPAS Air to check the settings, i.e. open the lidar IP address in a browser. If the point cloud is visible in SOPAS Air, the IP addresses are valid. Use the arguments |
I am using the sick_scan_xd API for Windows without ROS. |
Thanks for your log file. The full scan with an index -1 is only sent if all segments could be collected successfully. You can see this in your dump here, for example: msg->segment_idx: 0 From this point onwards, individual segments are always missing in the output so that all segments from 0 to 11 can never be gathered again. For this reason, no further full scan with index -1 is sent. |
How do I have to adjust the launch file so that the sensor gives me a "full scan" or "fullframe" with all 16 layers?
I also want to query which layer the current scan is from.I tried setting "custom_pointclouds" to "cloud_all_fields_fullframe":
Unfortunately, this did not work in with "SickScanApiRegisterCartesianPointCloudMsg", or rather, the callback is never called.
With the setting , the callback of "SickScanApiRegisterCartesianPointCloudMsg" is only called once.
Only the setting works well, but I don't want to split the scans into segments, but into layers.
The text was updated successfully, but these errors were encountered: