Interesting, I haven't updated a scanner to 2.5 up to now. Can you try it over USB? Can you try to sniff what's going on using wireshark? I won't have much time next week, so it could take some time for me to replicate this over here.

This is not an issue with the package but, rather, a limitation of the most recent TiM3xx firmware. Please contact me at aaron.rothmeyer@sick.com to talk about the application and a possible fix.

Thanks for taking care of this, @SICK-NorthAmerica ! If there is any information about that we should add to the README, let us know!

The TiM351 is a detection-only device meaning that it should only output GPIO-style digital outputs based on the presence or absence of an object in a preconfigured zone. A firmware bug present on versions prior to V2.50 allowed ranging data output over TCP and USB when that functionality should be limited to the TiM5xx series. To prevent future confusion, I'd recommend modifying the wiki to either remove the "TiM351-2134001" from the list or note "firmware revisions prior to V2.50". If a user of the sick_tim package is using BOTH ranging and detection modes of the TiM351 in a single application, they should contact me at aaron.rothmeyer@sick.com to let me know.

I've added a note to the ROS wiki, thanks for the explanation @SICK-NorthAmerica.

Hi,
Laser scanner mode: TiM571

is this problem related to this same issue?

I have attached a pic of what is happening.
the second picture, is the above error, which happens after some time.
If not, is there is an answer why it is happening like this?
(didnt want to start a new issue, since the problem seemed the same)

Don't know, you should find your version number in the Sick software..

I found the version number using SOPAS ET:
Laser scanner model: TiM571
Firmware version: V2.54-22.06.16

How it worked again:
we have 5 robots and all of them had the same problem starting yesterday.
I connected the scanner using USB, open SOPAS ET.
rebooted the system.
works fine.

Probably until next time.

TiM571 is not covered in this issue.
Also there where no changes in the driver (to my knowledge), so probably something else on your side.

its all working very well after some changes on my Tim351 with firmware V2.61

Sopas Command "LMDscandata" is not working on >V2.5 (maybe deactivated by sick to buy a more expensive scanner)

so just look how Sopas connect to the scanner and rebuild it.

here are the important changes:

stop streaming command:
old command: "\x02sEN LMDscandata 0\x03\0"
new command: "\x02sEI 5B 0\x03\0"

start streaming:
old command: "\x02sEN LMDscandata 1\x03\0"
new command: "\x02sEI 5B 1\x03\0" direct followed by "\x02sRI E7\x03\0"

all can be found in sick_tim_common.cpp (line 78, 245)
make sure to change/skip the isCompatibleDevice (Line 270)

greetings

yes sure, but time-limited only in a few days

After the product that was operating in tim351 v2.31 was changed to V2.51 by product replacement, sopas checked the operation, but it does not work due to a communication error in the actual connected system.
Can you advise me
Can you send me v2.31 firmware?

@lee6225 : We don't have any firmware to send you, and I'm not sure whether the firmware supports downgrading. We are also not affiliated with SICK. Please contact SICK directly.

After the product that was operating in tim351 v2.31 was changed to V2.51 by product replacement, sopas checked the operation, but it does not work due to a communication error in the actual connected system. Can you advise me Can you send me v2.31 firmware?

@lee6225 Please reach out to me directly at aaron.rothmeyer@sick.com. I'm the product manager for the TiM line at SICK and I should be able to assist if you are still seeing this issue. Thank you!