DataTS ingest contract
DataTS does not expose REST. It has no listen port and no /live, /ready, or /health. Supervision can see whether the Windows service is running.
The time-series page, settle, and evaluate read the time-series store. They do not connect to a DataTS process.
Kinds on the current network
| Id | Typical source | How it is chosen |
|---|---|---|
opc | Subscribe to field OPC | The process file has Driver.time_interval_ms |
dcct | Streaming points through ZeroMQ or a similar source | The process file has Driver.time_interval_us (this key also selects the kind) |
An unregistered kind must not start. During integration, VirtualPlant writes the store itself. Do not run another DataTS against the same paths.
Point rows
Each row is one point. Identity and address keys are group, system, device, tag, address, and datatype. scripts is optional.
These switches decide where the point is written:
| Key | Meaning |
|---|---|
iotdb | Write to IoTDB |
stream | Write to the data stream |
cache | Cache recent values |
subscription | Subscribe to changes |
Process keys
Both kinds need Driver.server (the field address from that site’s point table) and the time-skew threshold Driver.max_allowed_timedelta.
OPC uses Driver.time_interval_ms as the poll interval. DCCT uses Driver.time_interval_us as the sample interval.
The IoTDB block needs whether writing is on, the batch interval, whether only changes are stored, and whether a write still happens after a quiet interval. The Redis block must still exist when it is off. Turning it off does not block closed-loop reads of the main store.