Closed eliasdc closed 3 years ago
Hi, I will try to debug this. Thanks for bringing this to my attention
Alright i can reproduce the issue. However with a microScan3 it is behaving as expected. Just the nanoScan3 does not behave like it is supposed to. Furthermore, I fixed a small typo in the default launch file.
Should be fixed now. the setup of the sensor settings should always be invoked now.
Furthermore defaulted to use custom angles as default.
Please reopen if the latest commits didn't fix the problem
I completely missed that typo, fixed in initial post too for future searches. I was however using the correct parameter when testing from my own launch file.
Just tested your fix and it does work as expected. Thanks.
When using a NanoScan3 we're unable get messages from the
/scan
topic when trying to configureangle_start
andangle_end
. These settings are only pushed to the lidar ifuse_persistent_config:=false
but from that moment we don't receive messages on the topic. Withuse_persistent_config:=true
everything works except for the changed angles of course. Changing this angle in the sick safety designer does not work. In the data output option the angles selection boxes are greyed out.It does work with our custom
sick_safetyscanners
port (https://github.com/Tractonomy/sick_safetyscanners) to ros2 with the same settings, just altering the node and package in the launch file.*edit: fixed typo