-
The latest version 1.0.8 driver occasionally has abnormal radar data publishing problems during operation, which can be restored to normal after restarting the node, seriously affecting the operation.…
-
sick_safetyscanners ros package version: 1.0.8
When `field_data` service is called while communication with LiDAR sensor is established, we observed the case that the ros node caused segfault.
H…
-
Hi!
We are using nanoScan3 and encounter the situations where the node "sick_safetyscanners" would stop after couple of days of correct work. The moment it happens is hard to capture, so I currentl…
-
Hi,
My hardware configure:
MS3 : IP: 192.168.1.12
Subnet: 255.255.255.0
Data Output: IP Addrress: 192.168.1.255
UDP PORT: 6060
MS3 : IP: 192.168.1.13
Subnet: 255.255.255.0
Data Output: IP …
-
When disconnecting the power to the scanners and reconnecting it, the ROS node is getting stuck. I would expect it to recover or fail when the scanner loses power.
Steps to reproduce for a MicroSca…
-
I am able to do tcpdump and see the UDP packets in the container but I cannot access topic with this package.
Host IP 192.168.0.5
sensor IP 192.168.0.3
container IP 172.20.0.5
Any solution?
-
I have the question, diagnostic topic get warn "Frequency too high"
I searched all the code and can't find where is the print
-
Would you be so kind as to make a Python wrapper for this ?
Thanks!
-
Hi,
We are seeing a discrepancy between the `angle_start`/`angle_end` parameters that we define in our launch files and the `angle_min`/`angle_max` values that are published to the `/sick_safetysca…
-
Driver crash:
```
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 0)
```