You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: controller_manager/doc/userdoc.rst
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -225,6 +225,10 @@ Note that not all controllers have to be restarted, e.g., broadcasters.
225
225
Restarting hardware
226
226
^^^^^^^^^^^^^^^^^^^^^
227
227
228
-
If hardware gets restarted then you should go through its lifecycle again.
229
-
This can be simply achieved by returning ``ERROR`` from ``write`` and ``read`` methods of interface implementation.
230
-
**NOT IMPLEMENTED YET - PLEASE STOP/RESTART ALL CONTROLLERS MANUALLY FOR NOW** The controller manager detects that and stops all the controllers that are commanding that hardware and restarts broadcasters that are listening to its states.
228
+
If hardware gets restarted then you should go through its lifecycle again in order to reconfigure and export the interfaces
229
+
230
+
Hardware and Controller Errors
231
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
232
+
233
+
If the hardware during it's ``read`` or ``write`` method returns ``return_type::ERROR``, the controller manager will stop all controllers that are using the hardware's command and state interfaces.
234
+
Likewise, if a controller returns ``return_type::ERROR`` from its ``update`` method, the controller manager will deactivate the respective controller. In future, the controller manager will try to start any fallback controllers if available.
0 commit comments