Supported controllers
Flintloop does not have a driver per brand – it talks to interface families. If your controller speaks one of the protocols below and exposes PV, setpoint and output, it works; the table says what Flintloop reads and what it can write back. No brand names, on purpose: the family is what matters.
Connections
- Modbus TCP
- Modbus RTU
- OPC UA
- Generic ASCII serial
- Historian or CSV import
- none (read via historian)
Families
| Family | Connection | Class | Reads | Writes |
|---|---|---|---|---|
| Single-loop panel controller, 48×96 mm | Modbus RTU | Panel | PV, SP, OUT | Kp, Ti (s), Td (s) |
| Single-loop panel controller, 96×96 mm | Modbus RTU | Panel | PV, SP, OUT, mode | Pb (%), Ti (s), Td (s) |
| Compact PLC with a PID instruction | Modbus TCP | PLC | PV, SP, OUT | Kp, Ki (1/s), Kd (s) |
| Modular PLC, analogue card plus PID block | Modbus TCP | PLC | PV, SP, OUT, auto/man | Kp, Ti (min), Td (min) |
| DCS PID function block | OPC UA | DCS | PV, SP, OUT, mode, limits | GAIN, RESET (min/rep), RATE (min) |
| DCS cascade master/slave pair | OPC UA | DCS | PV, SP, OUT, remote SP | GAIN, RESET (min/rep) |
| Independent trip amplifier | none (read via historian) | Safety | PV (export) | – |
| Panel controller with an ASCII line protocol | Generic ASCII serial | Panel | PV, SP, OUT | Kp, Ti (s), Td (s) |
| Benchtop temperature controller | Modbus RTU | Panel | PV, SP, OUT | Pb (%), Ti (s), Td (s) |
| Flow skid PLC | Modbus TCP | PLC | PV, SP, OUT | Kp, Ki (1/s) |
| Level loop in a tank PLC | Modbus TCP | PLC | PV, SP, OUT | Kp, Ti (min) |
| Pressure loop function block | OPC UA | DCS | PV, SP, OUT, mode | GAIN, RESET (min/rep) |
| pH loop function block | OPC UA | DCS | PV, SP, OUT | GAIN, RESET (min/rep) |
| Ratio station in a PLC | Modbus TCP | PLC | PV, SP, OUT, ratio | Kp, Ti (min) |
| Humidity chamber controller | Generic ASCII serial | Panel | PV, SP, OUT | Pb (%), Ti (s), Td (s) |
| Anything, via historian export | Historian or CSV import | Import | PV (trace), OUT (trace) | – |
A dash under "Writes" means Flintloop can read and analyse that loop but not push gains back – a safety trip, or a historian-only import. In those cases you copy the numbers in by hand, which is often what a change-controlled plant wants anyway.