How do you connect a 15-year-old PLC to a modern MES?
A 15-year-old PLC can be connected to a modern MES without replacing it. The standard approach is an edge gateway running a protocol driver that polls the PLC over its native interface (Modbus RTU, Profibus, DeviceNet or Allen-Bradley DF1) and publishes tags to an MQTT broker or OPC UA server. The MES subscribes to the broker and receives real-time data. This adds live visibility at one-tenth the cost of PLC replacement and takes 2 to 4 weeks per machine type.
Talk to an engineer about thisThe four protocol layers that cover 95 percent of old PLCs
Most PLCs made between 1995 and 2015 communicate over one of four protocols. Siemens S7 (S7-300, S7-400) uses the S7 protocol accessible over Ethernet or MPI bus. Allen-Bradley PLCs (SLC 500, MicroLogix, ControlLogix) use DF1 over serial, Ethernet/IP or DH+ over a 1784 card. Modbus RTU over RS-485 is the universal fallback: nearly every PLC from this era supports it. Mitsubishi MELSEC uses MC protocol over Ethernet.
Edge gateway software such as Kepware, Ignition OPC-UA module, or open-source tools like node-opcua and pymodbus can translate any of these into OPC-UA or MQTT without touching the PLC firmware.
What an edge gateway actually does
An edge gateway is a small industrial PC (Advantech, Moxa, Raspberry Pi CM4 for light loads) installed in the panel room or network cabinet. It runs a protocol driver that reads register addresses from the PLC at 100 ms to 1 second intervals, then publishes the values as structured MQTT messages or OPC-UA nodes.
The MES subscribes to these topics and timestamps each reading. From the MES perspective, the PLC is just another data source. From the PLC perspective, nothing has changed: it still runs its ladder logic at full speed. The gateway is read-only by default, which means there is no risk of the MES accidentally sending a write command to the machine.
Cost and timeline for a typical brownfield connection
Hardware: an industrial edge gateway with 4G failover costs INR 25,000 to 60,000 per unit depending on IO capacity. Software: Kepware licence costs USD 500 to 1,500 depending on drivers; open-source alternatives are free. Integration engineering per machine type (writing the tag map, testing and deploying) takes 3 to 5 days. For a plant with 20 machines across 5 different PLC types, expect 4 to 6 weeks total, and INR 4 lakh to 12 lakh all-in.
The result: real-time OEE data on every machine without a single PLC firmware change.
Related questions
Ajinkya Technologies has connected over 500 machines ranging from 1995-era Siemens S7-300 PLCs to 2020 Allen-Bradley ControlLogix systems, across steel, aluminium, automotive and paints plants in India. Contact hello@ajinkyatechnologies.in for a brownfield connectivity assessment.
References and scope
External references explain the underlying technology or regulatory context. Ajinkya pricing, schedules and project results are company provided estimates or examples, not independently audited industry benchmarks. Confirm scope and current requirements before making a purchasing decision.
What would this look like at your plant?
Share your production process, current systems and the problem you want to solve. An engineer, not a salesperson, replies.
Step 1
An engineer reads it
Not a sales bot. Our team replies within 24 hours with questions or times for a call.
Step 2
30 minute call
Your process, machines, systems and the number you want to move. We tell you honestly if we are a fit.
Step 3
A written scope for one line
What we would connect, what you would see, how long it takes. You decide; nothing starts without your approval.
Free scoping call. We start with one line, never change your machine logic, and you own the code and the data.
Reviewed by Amey Kadle, Founder, Ajinkya Technologies. Last reviewed: .