Appearance
Safety and commissioning #
Use purchasable gateway and interface hardware first. Pi 5 or CM5 industrial carriers are candidate hosts; a final BOM requires measured I/O capacity, electrical envelopes, enclosure/PSU suitability and physical deployment evidence. The initial software package does not freeze or certify a hardware BOM.
Machine interfaces must be galvanically isolated and protected as appropriate. Never wire unprotected Linux GPIO directly to commercial-machine signalling. Qualified installers must use the exact verified controller instructions before connecting a live machine. No supported machine wiring page is currently included.
Software commissioning #
Start with the explicit simulators and recorded profile fixtures. Check capability discovery, supported actions, unknown/stale state, immutable correlation IDs and raw observations. Confirm one gateway can handle multiple machine simulators and instrumentation together. A missing serial adapter must produce disconnected readings while other equipment remains usable.
Issue a test service, duplicate its invocation, then submit the same service ID through a different invocation. Verify the physical adapter is called only once. Interrupt dispatch and restart the workload; its outcome must remain unknown and require reconciliation. Disconnect the agent or network after dispatch and verify that recovery reports the result without another vend.
Perform a lab OS update and RAUC rollback with state on dpdata. Verify the command journal and profile evidence survive. These host tests must be recorded on the actual Pi 5/CM5 image before declaring it a qualified reference.
Troubleshooting and removal #
| Symptom | Inspect |
|---|---|
| Kiosk payments unavailable | Terminal/provider readiness and Site impact; gateway events alone do not prove payment readiness |
| Machine outcome unknown | Order/vend/Process/Operation and invocation evidence; reconcile before any new physical action |
| Instrument disconnected | Approved device mapping, host permissions, isolated interface and power |
| Instrument timeout or CRC error | Address, common serial settings, bus wiring and termination using the verified device instructions |
| Stale reading | Observation timestamp, poll interval and equipment connectivity |
| Journal full | Capacity and evidence retention; stop new physical commands and archive safely |
Stop the workload through Software management. Revoke approved resource grants and remove device/configuration bindings. Preserve the journal and evidence for reconciliation and audit. Machine electrical removal follows the verified controller's rollback procedure; a simulator cleanup is not a machine wiring instruction.