Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish bumpers data (if available) #25

Open
reed-adept opened this issue Feb 13, 2017 · 4 comments
Open

Publish bumpers data (if available) #25

reed-adept opened this issue Feb 13, 2017 · 4 comments

Comments

@reed-adept
Copy link

Copy and paste from rosaria is fine, unless someone is inspired to do some more heavy duty refactoring (if so please discuss on user list)

@RobertBlakeAnderson
Copy link
Contributor

We were just discussing adding this to our fork the other day. I'd like to do it a little differently than rosaria. Rosaria publishes the bumper state on every call to the publish() function. To save bandwidth, I'd like to only publish when an event occurs. The Kobuki API provides an example of this: http://docs.ros.org/hydro/api/kobuki_msgs/html/msg/BumperEvent.html

@reed-adept
Copy link
Author

Sounds good. I guess you can just save the bitmask and publish it (and save) if it changes, there's no event driven trigger or callback for that in ARIA. (It just provides the bumpers state every cycle (100ms) as a bitmask) [Aria also has the ArRangeDevice point cloud interface for it as well, creating a point whenever a triggered bumper is seen, not sure if anyone would find that useful?]

@RobertBlakeAnderson
Copy link
Contributor

Added bumper publishing to PR #19 .

@reed-adept
Copy link
Author

Merge request #19 includes battery information. It has now been merged into master. Anyone interested can take a look and let us know if this will be ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants