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
{{ message }}
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
There are some parameters I can not find how to set them via ros e.g. the echo filter or the particle filter, the mean filter, the fog filter and the multiecho handling. There are also others. Does ros only expose a subset of the options of the sensor? And if I change them in sopas will the change be reflected when running the sensor using the ros drivers or will the drivers overwrite these parameters with some defaults? I checked the sick_generic_caller.cpp file and didn't find all parameters, so I assume the driver won't overwrite the set config on the sensor?
The text was updated successfully, but these errors were encountered:
You are right in your assumption.
Yes the driver uses only a subset of the Lidar configurations, especially settings like particle or fog filters are not modified by the driver. If these parameters are set in SOPAS ET and then stored in the EEPROM, this driver does not overwrite the parameters and the lidar works with these settings.
There are some parameters I can not find how to set them via ros e.g. the echo filter or the particle filter, the mean filter, the fog filter and the multiecho handling. There are also others. Does ros only expose a subset of the options of the sensor? And if I change them in sopas will the change be reflected when running the sensor using the ros drivers or will the drivers overwrite these parameters with some defaults? I checked the sick_generic_caller.cpp file and didn't find all parameters, so I assume the driver won't overwrite the set config on the sensor?
The text was updated successfully, but these errors were encountered: