You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I cannot reveive laser scans nor datagram from a brand new Tim310, maybe i am missing an obvious confuguration step
I ran:roslaunch sick_tim310.launch and get the following console output:
Nothing is published on the topics /scan and /datagram (I have set publish_datagram to true).
The usb connection seems okay though, as i can somehow see the Serial Number of my device in the diagnotic topic, here is some echo of /diagnostics:
header:
seq: 17
stamp:
secs: 1459415111
nsecs: 247821658
frame_id: ''
status:
-
level: 2
name: sick_tim310: /scan topic status
message: LIBUSB - Read Error: LIBUSB_ERROR_TIMEOUT.
hardware_id: ''
values: []
---
header:
seq: 18
stamp:
secs: 1459415111
nsecs: 247946211
frame_id: ''
status:
-
level: 2
name: sick_tim310: /scan topic status
message: No events recorded.; No data since last update.
hardware_id: sRA 0 6 TiM31x E V2.51-21.08.15 sRA SerialNumber 8 16100082
values:
-
key: Events in window
value: 0
-
key: Events since startup
value: 0
-
key: Duration of window (s)
value: 9.011856
-
key: Actual frequency (Hz)
value: 0.000000
-
key: Target frequency (Hz)
value: 15.000000
-
key: Minimum acceptable frequency (Hz)
value: 13.500000
-
key: Maximum acceptable frequency (Hz)
value: 16.500000
-
key: Earliest timestamp delay:
value: 0.000000
-
key: Latest timestamp delay:
value: 0.000000
-
key: Earliest acceptable timestamp delay:
value: -1.000000
-
key: Latest acceptable timestamp delay:
value: 0.086667
-
key: Late diagnostic update count:
value: 0
-
key: Early diagnostic update count:
value: 0
-
key: Zero seen diagnostic update count:
value: 0
---
header:
seq: 19
stamp:
secs: 1459415112
nsecs: 248420411
frame_id: ''
status:
-
level: 2
name: sick_tim310: /scan topic status
message: LIBUSB - Read Error: LIBUSB_ERROR_TIMEOUT.
hardware_id: ''
values: []
---
header:
seq: 20
stamp:
secs: 1459415112
nsecs: 248683595
frame_id: ''
status:
-
level: 2
name: sick_tim310: /scan topic status
message: No events recorded.; No data since last update.
hardware_id: sRA 0 6 TiM31x E V2.51-21.08.15 sRA SerialNumber 8 16100082
values:
-
key: Events in window
value: 0
-
key: Events since startup
value: 0
-
key: Duration of window (s)
value: 10.012495
-
key: Actual frequency (Hz)
value: 0.000000
-
key: Target frequency (Hz)
value: 15.000000
-
key: Minimum acceptable frequency (Hz)
value: 13.500000
-
key: Maximum acceptable frequency (Hz)
value: 16.500000
-
key: Earliest timestamp delay:
value: 0.000000
-
key: Latest timestamp delay:
value: 0.000000
-
key: Earliest acceptable timestamp delay:
value: -1.000000
-
key: Latest acceptable timestamp delay:
value: 0.086667
-
key: Late diagnostic update count:
value: 0
-
key: Early diagnostic update count:
value: 0
-
key: Zero seen diagnostic update count:
value: 0
The text was updated successfully, but these errors were encountered:
The reason is probably that the firmware version you have is too new: V2.51-21.08.15. As explained by @SICK-NorthAmerica 's comment in #33 , the SICK TiM3xx devices were never meant to be used for ranging, only for detection. Unfortunately, there is nothing we can do in the sick_tim driver. You could try contacting @SICK-NorthAmerica directly (his email is in #33 ) and see if there is anything he can do.
Thank you very much for your prompt answer. There was an issue with the order, we received a 310 instead of 310s01, we are going to proceed to an exchange.
Hello,
I cannot reveive laser scans nor datagram from a brand new Tim310, maybe i am missing an obvious confuguration step
I ran:
roslaunch sick_tim310.launch
and get the following console output:Nothing is published on the topics /scan and /datagram (I have set publish_datagram to true).
The usb connection seems okay though, as i can somehow see the Serial Number of my device in the diagnotic topic, here is some echo of /diagnostics:
The text was updated successfully, but these errors were encountered: