SICKAG / sick_safetyscanners

ROS driver for SICK safety laser scanners
https://www.sick.com/de/en/opto-electronic-protective-devices/safety-laser-scanners/c/g187225
Apache License 2.0
61 stars 59 forks source link

diagnostic warn "Frequency too high" #96

Closed FlyHan closed 2 years ago

FlyHan commented 2 years ago

I have the question, diagnostic topic get warn "Frequency too high" I searched all the code and can't find where is the print

FlyHan commented 2 years ago

The message is as follows,

header:
seq: 602
stamp:
secs: 1649428650
nsecs: 662985874
frame_id: ''
status:
-
level: 1
name: "sick_safetyscanners/sick_safetyscanners: /scan topic status"
message: "Frequency too high."
hardware_id: "192.168.23.70"
values:
  -
    key: "Events in window"
    value: "175"
  -
    key: "Events since startup"
    value: "21003"
  -
    key: "Duration of window (s)"
    value: "5.139810"
  -
    key: "Actual frequency (Hz)"
    value: "34.047954"
  -
    key: "Target frequency (Hz)"
    value: "20.000000"
  -
    key: "Minimum acceptable frequency (Hz)"
    value: "18.000000"
  -
    key: "Maximum acceptable frequency (Hz)"
    value: "22.000000"
  -
    key: "Earliest timestamp delay:"
    value: "0.000109"
  -
    key: "Latest timestamp delay:"
    value: "0.000230"
  -
    key: "Earliest acceptable timestamp delay:"
    value: "-1.000000"
  -
    key: "Latest acceptable timestamp delay:"
    value: "1.000000"
  -
    key: "Late diagnostic update count:"
    value: "0"
  -
    key: "Early diagnostic update count:"
    value: "0"
  -
    key: "Zero seen diagnostic update count:"
    value: "0"

level: 0
name: "sick_safetyscanners/sick_safetyscanners: State"
message: "OK"
hardware_id: "192.168.23.70"
values:
  -
    key: "Version version"
    value: "R"
  -
    key: "Version major version"
    value: "2"
  -
    key: "Version minor version"
    value: "0"
  -
    key: "Version release"
    value: "0"
  -
    key: "Serial number of device"
    value: "22020357"
  -
    key: "Serial number of channel plug"
    value: "22030268"
  -
    key: "Channel number"
    value: "0"
  -
    key: "Sequence number"
    value: "23978"
  -
    key: "Scan number"
    value: "23960"
  -
    key: "Timestamp date"
    value: "0"
  -
    key: "Timestamp time"
    value: "705848"
  -
    key: "Run mode active"
    value: "true"
  -
    key: "Standby mode active"
    value: "false"
  -
    key: "Contamination warning"
    value: "false"
  -
    key: "Contamination error"
    value: "false"
  -
    key: "Reference contour status"
    value: "false"
  -
    key: "Manipulation status"
    value: "false"
  -
    key: "Current monitoring case no table 1"
    value: "1"
  -
    key: "Current monitoring case no table 2"
    value: "0"
  -
    key: "Current monitoring case no table 3"
    value: "0"
  -
    key: "Current monitoring case no table 4"
    value: "0"
  -
    key: "Application error"
    value: "false"
  -
    key: "Device error"
    value: "false"
FlyHan commented 2 years ago

I found the problem, the configuration expected_frequency is different from the device