Closed mcguiremichael closed 1 year ago
Hello, thank you for reporting this. We are trying to reproduce the behavior on an equivalent sensor and find the cause of the error and will come back to you.
Best regards, Manuel
Hello,
we think we found the source of your problem. Currently, the default launch file has the mean filter activated and configured to take the average of 2 measurements. This leads to the sensor delivering measurements at half the scan frequency. You can deactivate it by changing line 93 to <param name="lfp_meanfilter" type="int" value="0" />
.
Note: the name of the "scan frequency" parameter is a bit misleading. With the mean filter deactivated and the output interval set to 1 in Sopas ET, scans will always be sent at 150 Hz. The difference is whether the scans are interlaced or not (see p. 22 and following in the operating instructions https://cdn.sick.com/media/docs/3/43/443/operating_instructions_lms1104c_111031s01_2d_lidar_sensors_en_im0079443.pdf ).
Best regards, Manuel
Thanks for your feedback! Mean and median filter settings are deactivated in default launchfile configuration in branch https://github.com/SICKAG/sick_scan_xd/tree/feature/lms1000_configuration and will be merged in the next release.
Solved due to investigation and documentation update.
We are running the SICK LMS1000 lidar with ros1 melodic. We launch the sensor with the following command.
roslaunch sick_scan sick_lms_1xxx_v2.launch hostname:=169.254.6.195 scan_freq:=150 ang_res:=0.75
No other changes are made to the default launch file used.
This is the output from running the roslaunch command.
After launch we recorded the cloud outputs to a rosbag. However, after running
rosbag info
, we only see 75 messages per second.If it was recording at 150hz as we had asked it to, it would be around 13200 messages in an 88 second rosbag.
What could be causing this? The settings in SOPAS were also set to 150hz.
We tried adjusting the power settings to the sensor and that made no difference.
Thank you.