Not getting any data from any of the scan topics about pf_lidar_ros_driver

[bk-mtg]

@ipa-hsd I work with @milano-technical-intern, and I just finished testing that this appears to be working now for us. We even verified that we are able to change the IP/subnet on the device (as expected) and the driver works on the new subnet (assuming appropriate host IP config obviously).

I assume this was addressed in c176058? Thanks for the help with this!

[ptruka]

Hello,

a quick question to start: Which hardware version are you using?

Best Regards

[milano-technical-intern]

This is what it says on the label that is on the R2300:

HW: 0.608
FW: 0.70

Best,

[hsd-dev]

@milano-technical-intern could you please pull the latest master and try again?

[milano-technical-intern]

@ipa-hsd I did, and I'm still having the same issue: no data from any of the scan topics. Have you updated the master @ipa-hsd? In the repository, it reads "Latest commit adff7b9 13 days ago"

Best,

[hsd-dev]

@milano-technical-intern yes I have updated the master branch. Have you made sure the device is in working condition? Probably just pinging it may not be enough. @ptruka is there any Windows software where he can test the device?

[milano-technical-intern]

@ipa-hsd I just tested it out in the Windows 10 program. It works. I can see all four layers. The problem persists on the ROS driver. I'm not getting any data. Do you know what indicates each LED in the R2300? It seems that in the ROS program is not establishing connection with the R2300. As you can see in this picture, the orange LED keeps blinking when using the ROS driver. On the other hand, when using the Windows program is not blinking but on all the time.

Best,

[milano-technical-intern]

Nevermind. I just got the manual where it describes the indicators.

The PC where I'm testing the R2300 doesn't have WiFi. Therefore, when I connect to the R2300 is by Ethernet only. I've tried with a network switch and directly connecting the R2300 to the computer but none of them worked.

[hsd-dev]

I have connected the device directly to my computer with Ethernet. Could you try that without using the network switch?

[milano-technical-intern]

I'm getting the same result with or without the network switch. I even tried with another computer and it's the same.

Best,

[milano-technical-intern]

@ipa-hsd by the way, I cannot reopen the issue because I'm not a collaborator since you closed it.

https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github

[hsd-dev]

I will try to implement SSDP within the driver, that might solve the issue.

[milano-technical-intern]

@ipa-hsd Have you tried to use the driver in a freshly installed Ubuntu 18.04 and ROS melodic? Maybe you can replicate the issue I'm having by doing that.

Best,

[YangAndI]

I have the same problem.
Infinite loop
data_notifier.wait_for(lock, std::chrono::seconds(1));
because the scans is empty
best

[YangAndI]

And the led is only three,the first is green and the last is green,and the second to last is flashing yellow light.
Best,

[hsd-dev]

@YangAndI and @milano-technical-intern is the scanner's IP 10.0.10.76 and your host PC's IP 10.0.10.1?

[milano-technical-intern]

@ipa-hsd Actually, It worked by changing the host PC's IP to 10.0.10.1

That makes me wonder, is it possible to change the IP to be another one under the subnet 255.0.0.0? For example, I tried with 10.0.10.75, and it didn't work. The reason is that address is normally reserved for the default gateway.

Thanks!

Best,

[YangAndI]

@ipa-hsd Thanks,it is worked by changing the IP to 10.0.10.1.
May i change the sensor ip or host ip?

[milano-technical-intern]

@ipa-hsd Any particular reason why it doesn't work for any other address in the subnet but 10.0.10.1? If I send HTTP commands like this one:
http://10.0.10.76/cmd/set_parameter?pilot_laser=on
it works for any address in the subnet.

Best,

[hsd-dev]

Sorry for the delay. Can you test with the latest master?

[milano-technical-intern]

Sorry for the delay. Can you test with the latest master?

Still not working with other ip address other than 10.0.10.1

[hsd-dev]

Make sure your IP is has a subnet of 10.0.10.*
I cannot reproduce this error from my side anymore.

[hsd-dev]

Good to know it works!