Inconsistent time_increment, scan_time and angle_increment about sick_scan HOT 3 CLOSED

@ZSeymour1
Unfortunately, We could not reproduce this behavior with a TIM 561. Which scanner do you use exactly?
What is the update rate of your scanner ?
you can read it with this command:

rostopic hz /cloud

Can you also post your entire launchfile so we can figure out the reason better ?

from sick_scan.

Hi,

We're using the SICK TIM 571 (P/N: 1075091) with the 25m range (outdoor version). The update rate (using rostopic hz /cloud) is approximately 15Hz (see below for copy-pasted data).

I've also attached the launch file (but as a .txt not .launch), which is the default one provided in the package, with the default hostname IP changed to "190.168.1.71".

average rate: 15.007
min: 0.063s max: 0.070s std dev: 0.00130s window: 15
average rate: 15.007
min: 0.063s max: 0.070s std dev: 0.00095s window: 30
average rate: 15.001
min: 0.063s max: 0.070s std dev: 0.00082s window: 45
average rate: 15.002
min: 0.063s max: 0.070s std dev: 0.00075s window: 60
average rate: 15.000
min: 0.063s max: 0.070s std dev: 0.00070s window: 75
average rate: 15.001
min: 0.063s max: 0.070s std dev: 0.00067s window: 90
average rate: 15.000
min: 0.063s max: 0.070s std dev: 0.00066s window: 92

sick_tim_5xx.txt

from sick_scan.

We have tested with the TiM571, using both sick_scan and sick_scan_xd on ROS-1 Noetic. Unfortunately, the error is not reproducable in our system. There are no error messages and the frequencies are as expected (expected and reported time increment at 6.172e-05). As long as TiM571 and driver run as expected and provide the scanner data, it's save to ignore the warning.

from sick_scan.