You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was facing the same issue (LaserScanRangeFilter was not working). But I managed to fix this issue (problem was in the naming of the node). I will describe my scenario and a solution here. Maybe it could help you as well.
Expected behavior:
Ranges of scan data are filtered as requested in YAML file.
Current behavior:
Ranges of scan data are not filtered.
More specifically, I slightly modified only launch file range_filter_example.launch.py as follows (the only change is adding name of node compare to example):
Comparing my and example versions:
MY modified version of example is NOT working. More specifically, update and configure methods are not called in LaserScanRangeFilter class (tested by logging). So the ranges of scan data are not filtered.
EXAMPLE version is working. Ranges of scan data are filtered as requested in yaml file.
Solution:
The only difference is that I added the name of the node to the launch file (name parameter).
After removing the name of node. It is working.
My launch file is:
My rplidar_range_filter_config.yaml is :
scan_filter_chain:
type: laser_filters/LaserScanRangeFilter
params:
use_message_range_limits: false
lower_threshold: 0.5
upper_threshold: 1.0
lower_replacement_value: -.inf
upper_replacement_value: .inf
The text was updated successfully, but these errors were encountered: