This is part of the Robotics in Concert project. |
Only released in EOL distros:
Package Summary
This doesn't do everything you need for multimaster, however it does provide the building blocks common to most or all multimaster systems. In particular, it provides the gateway model, which is an upgrade on old foreign_relay and master_sync concepts.
- Author: Daniel Stonier, Jihoon Lee, Piyush Khandelwal
- License: BSD
- Source: git https://github.com/robotics-in-concert/rocon_multimaster.git (branch: fuerte)
Package Summary
This doesn't do everything you need for multimaster, however it does provide the building blocks common to most or all multimaster systems. In particular, it provides the gateway model, which is an upgrade on old foreign_relay and master_sync concepts.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- Author: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_multimaster/issues
- Source: git https://github.com/robotics-in-concert/rocon_multimaster.git (branch: groovy-devel)
Package Summary
This doesn't do everything you need for multimaster, however it does provide the building blocks common to most or all multimaster systems. In particular, it provides the gateway model, which is an upgrade on old foreign_relay and master_sync concepts.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- Author: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_multimaster/issues
- Source: git https://github.com/robotics-in-concert/rocon_multimaster.git (branch: hydro)
Package Summary
This doesn't do everything you need for multimaster, however it does provide the building blocks common to most or all multimaster systems. In particular, it provides the gateway model, which is an upgrade on old foreign_relay and master_sync concepts.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- Author: Daniel Stonier, Jihoon Lee, Piyush Khandelwal
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_multimaster/issues
- Source: git https://github.com/robotics-in-concert/rocon_multimaster.git (branch: release/0.7-indigo)
Package Summary
This doesn't do everything you need for multimaster, however it does provide the building blocks common to most or all multimaster systems. In particular, it provides the gateway model, which is an upgrade on old foreign_relay and master_sync concepts.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>, Piyush Khandelwal <piyushk AT gmail DOT com>
- Author: Daniel Stonier, Jihoon Lee, Piyush Khandelwal
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_multimaster/issues
- Source: git https://github.com/robotics-in-concert/rocon_multimaster.git (branch: release/0.8-kinetic)
About
Design Goals - bulleted goals and implementation decisions for multimaster.
Hub - redis key-value stores (~forums) for shared use by multimaster gateways.
Gateway Model - advertise/pull/flip connections over a multimaster system.
Use Cases - various ways you might use these components for more complete solutions on top.
![/!\](./rostheme/img/alert.png "/!\"){kind=small}
We are not working on robust transports for wireless communications between ros systems yet. We hope to delay this and provide useful input into the next gen design of ros comms and thereby save some effort in the long run. This might become a priority though if next gen comms is significantly far away. If you have an interest in bumping this priority, let us know.
Usage
Refer to the Tutorials