Connecting legacy PLCs without replacing them
A controller that has run reliably for twenty years is an asset, not a problem. The goal is to read its data, not to rewrite it.
Start read-only
Begin by only reading values. A read-only connection cannot change the process, which makes it far easier to approve with operations and safety teams.
Common options
- Native protocols. Many older PLCs speak Modbus or a vendor protocol over serial or Ethernet. A gateway can poll them and translate to something modern.
- OPC UA servers. Vendor or third-party servers expose PLC tags in a standard form that other systems can consume.
- Protocol converters. Small industrial gateways bridge serial or fieldbus devices to Ethernet and MQTT.
Design for the edge
Place a gateway close to the machines. It should buffer data when the network is down, add timestamps at the source and publish only what is needed. Keep the control network separate from the office network and cross it in one controlled direction.
Watch the details
Polling too fast can overload an old CPU. Agree register maps and units in writing. Test with the machine in a safe state first.
Done carefully, legacy equipment can feed modern dashboards and quality systems for years to come.
Have a system to build or connect?
Describe your process and constraints. We will reply with questions, options and a realistic plan.