ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

It's been three months so I figured I'd give an update on where I got to with this.

Based on gvdhoorn's et al suggestions, I ended up creating a mux node which allows switching between various inputs via a service that the user can control. The reason I created my own node for this is because it also allows the user to tune some domain specific settings such as the frame and magnitude of the twist. It works well for my needs. A publishing node has no idea if it is the currently selected input but the mux node knows when a non-selected input starts publishing and can throw up a warning.

I also discovered the bond package which looks like it could be used for resource acquisition, similar to remote_mutex except the bond package looks well supported.

From the docs:

Bonds can be used to track resource ownership. The creation of a bond indicates a lease on the resource, and breaking a bond indicates that the lease is broken.