Giving a range -1.0 will hurt libplayerc as it has an assert range > 0. That could obviously be changed, but I think maybe reporting the maximum distance is better. The ranger units themselves will report the max distances (Usually 8 meters) when they get an error. Or perhaps the driver should be configurable, for either report -1, report max, or interpolate.

On Mon, Oct 20, 2008 at 4:05 PM, Brian Gerkey <> wrote:

On Oct 20, 2008, at 11:58 AM, Alberto Valero wrote:

>> The robot_params work properly for the PatrolBot!!

Great.  I checked them into SVN.

>> The sicklms200 driver doesn't support an "ignore" parameter, but it
>> could be added.  We'd happily accept a patch that adds this
>> capability.
> The only problem is what range should the driver write on the ignored
> rays!, we have added in our client the interpolation between the
> adjacent
> values of the ignored rays, would this fit everybody??

You could give an invalid range, such as 0.0, or even -1.0.

Clients would have to be coded to ignore such readings (which is easy
to do).


This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
Playerstage-users mailing list