Adapters
Supported adapter types — in-process, external, and not implemented.
DataHub devices use an adapter type that determines how telemetry is collected. The adapter orchestrator reconciles in-process drivers; external adapters publish to NATS from iot/ or custom services.
Adapter matrix
| Type | Delivery | Status |
|---|---|---|
| SIMULATOR | In-process | Live — demo / lab |
| MQTT | In-process | Live — subscribe per tag topic |
| SIEMENS_S7 | In-process | Live — ISO-on-TCP (nodes7) |
| OPC_UA | In-process | Live — browse/scan supported |
| MODBUS_TCP | In-process | Not implemented — orchestrator reports NOT_IMPLEMENTED |
| MELSEC_A1E | External (iot/) | Publish to NATS via Python template |
| BECKHOFF_ADS | External (iot/) | Publish to NATS via Python template |
Orchestrator status
On the device detail page:
| Status | Meaning |
|---|---|
| RUNNING | In-process driver active |
| STOPPED | Disabled or not started |
| ERROR | Connection or config failure |
| NOT_IMPLEMENTED | No live driver (e.g. Modbus stub) |
Device liveness
CONNECTED (UI) means telemetry arrived within the last 15 seconds — separate from orchestrator RUNNING/ERROR.
Edge vs central
When a device is assigned to an edge gateway, the central orchestrator does not run its driver. Collection, connection test, and tag scan happen on the plant box. See Edge gateway.