Break beam sensor does not take name into account when making the topic
Issue #13
resolved
See: https://discourse.ros.org/t/break-beam-sensor-not-publishing-on-named-topic/1057
This effectively prevents you from using more than one break beam sensor at a time since they would all publish to the same topic.
I suppose that may have been intentional, but as the user pointed out, it is documented to publish to a named topic:
https://bitbucket.org/osrf/ariac/wiki/competition_interface_documentation
Comments (4)
-
-
- marked as critical
-
- changed status to resolved
-
I'll give an update on the discourse thread once debians have been rebuilt
- Log in to comment
update: this is also affects the proximity sensor, because both use the ROSProximityRayPlugin.
As that's a sensor plugin not a model plugin, the parent's name that is accessed in the plugin is the name of the sensor which is not unique.