zeroconf_implementations: zeroconf_avahi | zeroconf_avahi_demos | zeroconf_comms | zeroconf_jmdns | zeroconf_jmdns_demos
Stack Summary
Convenient wrappers around platform-dependant implementations whose purpose are both to expose a fairly standard sort of api as well as a ros api (topics and services) where practical. The only implementation it doesn't include is the android (will eventually merge back in here if ubuntu starts officially including adk packages).
- Author: Maintained by Daniel Stonier
- License: BSD
- Repository: yujin-ros-pkg
- Source: git https://github.com/stonier/zeroconf_implementations.git
Overview
What is Zeroconf? - a few notes about zero-configuration in general.
This stack provides native language implementations with a fairly standard api (e.g. libs) as well as ros nodes that can be conveniently accessed with your typical ros api (topics and services).
Beyond that, it doesn't try to do anything specific (like advertise your ros master). What you wish to advertise or listen for on your network is up to your program. Think of it as a set of building blocks.
Implementations
Linux : zeroconf_avahi, python-avahi
Apple/Windows : bonjour
Java : zeroconf_jmdns
Android : zeroconf_android (uses zeroconf_jmdns)
Embedded Linux : avahi-core/custom
Installation
If you want to just use the linux avahi implementation, you can install the .deb:
> sudo apt-get install ros-electric-zeroconf-implementations
otherwise via rosinstall refer to zeroconf.rosinstall/zeroconf_overlay.rosinstall as a reference.
# For a self-contained working source tree: > rosinstall ~/zeroconf https://raw.github.com/stonier/zeroconf_implementations/master/zeroconf.rosinstall # OR overlaying on an apt-get installed electric: > sudo apt-get install ros-electric-ros-base > rosinstall ~/zeroconf https://raw.github.com/stonier/zeroconf_implementations/master/zeroconf_overlay.rosinstall
Errata
Ros master zeroconf: initial efforts on zeroconf were built with the thought of advertising a ros master in mind, but that is simply a special case of what you may wish to do with it. You can use it to advertise a remote configuration server (perhaps an xml-rpc server) whilst leaving your ros master hidden in your embedded robot, or you could use it to listen for the apple air tv device so that your robot can satisfy the urge to flake out in front of the telly for a while. There are no boundaries!
Contact Points
<d DOT stonier AT gmail DOT com>






