search

PepperlFuchs / pf_lidar_ros_driver

ROS driver for Pepperl+Fuchs R2000 and R2300 laser scanners
https://www.pepperl-fuchs.com/global/en/23097.htm
Apache License 2.0
39 stars 38 forks source link

Possible connection drop after long runtime #91

Closed abuchegger closed 1 year ago

abuchegger commented 2 years ago

Hi!

We had the issue that after running for several hours (overnight), the driver node suddenly stopped publishing data on the scan topic during one of our tests. The node did not output any log messages, and obviously did not try to reconnect to the scanner. When checking, the scanner was reactive (ping + curl). We restarted the node, and it published scan data again.

Have you encountered this issue? We are using the current main branch with an R2000.

Best regards, Alex

abuchegger commented 2 years ago

Hi!

We had the same issue again; please find attached the (filtered) rosout and stdout of the driver node: lidar-nav_lidar-rosout.log lidar-nav_lidar-stdout.log

The last scan data was received at approx. 1665133948, which is about 26 minutes before the appliance (including PC, Lidar, and Ethernet switch) was manually power-cycled. Interestingly, the driver node does notice the connection loss at the time of power off, as can be seen in the rosout.

Best regards, Alex

hsd-dev commented 2 years ago

which version of the code are you using? In the recent times I have not tested the driver by running it for long duration since that issue had been fixed. I will try it out next week. Not sure if https://github.com/PepperlFuchs/pf_lidar_ros_driver/issues/90 is related.

abuchegger commented 2 years ago

Hi,

we're using the current main branch (commit b07c6170d7112aa5923bb9b1e47c09f865e00e4d). The error occurred approx. 3h48min after the connection to the lidar was established. Configuration of the lidar is 1800 data points at 50Hz.

Best regards, Alex

hsd-dev commented 2 years ago

Thanks for the info. I am currently running on tight schedule, but will try it with the configuration you mentioned next week.

Hr-Senerity commented 2 years ago

Sorry to reply so late,

I also use the current main branch (commit b07c617). But during the long run, I had no data outage. However, when the node is shut down and restarted after running for a long time, the output information of the node is #90 and no data output. The R2000 will return to normal until you restart after power failure.

hsd-dev commented 2 years ago

@abuchegger and @Hr-Senerity very sorry but looks like I will not be able to take a look at this before leaving for ROSCon next week.

@abuchegger did you monitor the CPU usage when no data was received?

abuchegger commented 2 years ago

No, unfortunately we have not been monitoring CPU usage. We are planning to integrate that into our software.

We have tried to reproduce the issue with an R2000 in the office, with no luck so far.

ptruka commented 1 year ago

Thank you for creating this issue. As there has been no feedback for a while, we are closing this issue. please open a new issue if the problem reoccurs.

Kyros8712 commented 5 months ago

Hi, I also encountered the same problem. After using it for a long time, /scan topic will have no data.

Subscribers cannot use callback functions to obtain data.