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: gpio_controllers/doc/userdoc.rst
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,3 +57,26 @@ The controller expects at least one GPIO interface and the corresponding command
57
57
- ana.2
58
58
59
59
With the above-defined controller configuration, the controller will accept commands for all gpios' interfaces and will only publish the state of Gpio2.
60
+
61
+
62
+
63
+
### gpio_tool_controller
64
+
65
+
The controller enables control of tools connected to the robot or components of a robot via general-purpose inputs and outputs (GPIO), digital or analog.
66
+
Concretely the controller is made for controlling the custom-made industrial grippers or tools, or components like lifts or breaks.
67
+
The IOs might even be virtual, like controlling the state machine of a robot that is implemented on a PLC.
68
+
69
+
The controller provides high-level interface for engaging or disengaging a tool or a component, as well as for reconfiguring it.
70
+
The reconfiguration is possible only in *disengaged* state.
71
+
In the example of gripper this would be *open* state.
72
+
73
+
74
+
75
+
The controller implements state machine for the transition between states and
0 commit comments