diamondback:Only showing information from the released package extracted on Unknown. No API documentation available. Please see this page for information on how to submit your repository to our index.
electric:Documentation generated on March 01, 2013 at 02:15 PM
fuerte:Documentation generated on August 15, 2013 at 10:10 AM
groovy:Documentation generated on October 05, 2014 at 10:32 PM
hydro:Documentation generated on August 28, 2015 at 10:10 AM (doc job).
indigo:Documentation generated on June 07, 2019 at 04:29 AM (doc job).
jade:Documentation generated on August 17, 2017 at 10:58 AM (doc job).
kinetic:Documentation generated on September 02, 2020 at 03:38 AM (doc job).
lunar:Documentation generated on March 20, 2019 at 03:47 PM (doc job).
melodic:Documentation generated on March 01, 2022 at 05:54 AM (doc job).
noetic:Documentation generated on March 02, 2022 at 07:51 AM (doc job).
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer: Esteve Fernandez <esteve AT osrfoundation DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Esteve Fernandez <esteve AT osrfoundation DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Michael Carroll <michael AT openrobotics DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Mikael Arguedas <mikael AT osrfoundation DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Michael Carroll <michael AT openrobotics DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Michael Carroll <michael AT openrobotics DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Michael Carroll <michael AT openrobotics DOT org>
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Maintainer status: maintained
Maintainer: Michael Carroll <michael AT openrobotics DOT org>
Bond exists to ensure that two processes can monitor each other's termination. This is useful in several situations.
Spawning nodelets/controllers/robots in gazebo
When spawning a nodelet (or anything else), two processes, the spawner and the container, communicate to bring the nodelet up, however, the current system does not cleanly deal with all termination possibilities (<<Ticket(ros-pkg 4221)>>). Creating a bond between the spawner and the container allows each to know when the other crashes and to implement appropriate recovery behaviors.
This applies to controllers (re-loading when the realtime_loop goes down) and to gazebo (re-creating the robot if gazebo crashes).
Resource ownership
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.
You could, for example, request that the laser scan at a particular frequency. By passing a bond id along with the request, the laser scanner controller will form a bond based on the request. When it receives a new request, it breaks the bond. Whether the laser controller receives a new request or the controller crashes, you will be informed that the laser is no longer scanning as you desired.
