Runtime & Extension Points
The injectable transport, platform, and logging interfaces Gripper is built on — implement these to add a custom transport, port to an RTOS, or capture logs in tests. Most users do not need to implement these interfaces.
Split by what you're implementing, plus what a failure in any of them looks like to the caller:
- Transport — the byte-level link to the hardware (Serial).
- Platform — the OS services the threaded runtime needs (locks, threads, sleeps).
- Logging — where diagnostic lines go.
- Exceptions — the driver- and transport-level failures thrown up through these interfaces.
- Modbus Client — the no-thread layer below Gripper, for the rare integration that cannot run Gripper at all.
Members
| Topics | |
| Exceptions | |
|
Failures thrown by the transport or driver. More... | |
| Logging | |
|
Where diagnostic log lines go. More... | |
| Modbus Client | |
|
The no-thread layer below Gripper: one Modbus transaction per call, for superloop targets and diagnostic tooling only. More... | |
| Platform | |
|
The OS services (locks, threads, sleeps) behind the threaded runtime. More... | |
| Transport | |
|
The byte-level transport extension point (Serial). More... | |
Generated via doxygen2docusaurus 2.2.2 by Doxygen 1.9.8.