Adding I/O to an existing PLC without changing the program

A machine that has run for years often needs a few more signals: motor temperatures for maintenance, a cycle counter for OEE, or a sensor for a new process step. Changing the PLC program needs the original project, someone who knows the code, a production stop and sometimes a new acceptance test. This article explains how to add I/O to an existing PLC system, when the program can stay as it is, and when a change cannot be avoided.

Start with who uses the signal

The deciding question is who needs the value. If only people and IT systems use it, for dashboards, logs or maintenance alarms, the PLC does not have to see it, and the new I/O can be read by SCADA or an edge device.

If the value must affect the machine, as an interlock, a start permissive or a setpoint, the PLC logic has to use it, and the aim is to keep that change small. Safety functions belong in the machine's safety circuit and are outside the scope of this article.

Four ways to add I/O to an existing PLC

1. Parallel Ethernet I/O read by SCADA or an edge device

An Ethernet I/O module is wired to the new sensors and connected to the plant network rather than to the PLC. SCADA reads it over Modbus TCP. The ET-2200 series can also publish values over MQTT, and OPC UA I/O modules such as the U-7560M have OPC UA, MQTT and a RESTful API built in. The PLC program and hardware configuration stay untouched.

If the data has to reach an MES or a cloud platform, a UA-5231M communication server reads Modbus TCP and RTU devices and converts the values to OPC UA, MQTT or SNMP. For simple local logic, a WISE-5231M edge controller runs IF-THEN-ELSE rules set up in a web browser and connects to up to 16 Modbus TCP modules and up to 32 DCON or Modbus RTU modules.

2. Fieldbus slave I/O on the PLC's own network

If the PLC needs the signal, the direct route is an I/O module on the PLC's fieldbus. ICP DAS has slave I/O for PROFINET (PFN-2000, with a GSDML file), PROFIBUS DP (PROFI-5000, with a GSD file), EtherNet/IP (EIP-2000, with two ports for daisy-chaining) and CANopen (CAN-2000C, with an EDS file). The module is added to the PLC's hardware configuration with its device file.

That is a configuration change, and on most PLCs it means a download. The logic only changes if the new values are used in it.

3. A gateway to Modbus I/O

When Modbus I/O is already installed, or suits the signals or distances better, a gateway maps Modbus data into the PLC's fieldbus. The GW-7662 lets a PROFINET controller access Modbus RTU/ASCII devices such as M-7000 modules, and the GW-7663 does the same for Modbus TCP devices such as ET-7000 modules. The GW-7553 gives a PROFIBUS master access to Modbus TCP devices, the GW-7472 links an EtherNet/IP scanner to Modbus RTU and TCP devices, and the I-7232D connects up to 10 Modbus RTU I/O modules to a CANopen master.

To the PLC the gateway is one fieldbus device, so the same rule applies.

4. Modbus TCP I/O polled by the PLC

Many PLCs can act as a Modbus TCP client and read any Modbus TCP module directly. The polling has to be set up in the PLC, so this route always involves the PLC project.

When the PLC program must change

Worked example: two requirements, two routes

A filling machine is controlled by a PROFINET PLC. Maintenance wants eight bearing and motor temperatures with trends, and production wants the machine to stay stopped until a newly installed chiller reports ready.

• The temperatures are for people, not for the control logic. An ET-2215H with eight RTD inputs, 3-wire lead resistance compensation and open-wire detection is connected to the plant network. SCADA polls it over Modbus TCP, and the PLC is not touched.
• The chiller signal is a start permissive, so the PLC must see it. A PFN-2051 with 16 isolated digital inputs is added to the PROFINET network with its GSDML file, and one condition is added to the start logic.

The result is one small program change with a clear test.

Practical checks before installation

• Keep parallel Ethernet I/O on the plant or SCADA network, away from the PLC's real-time fieldbus traffic where possible.
• Plan IP addresses and restrict access. The ET-2200 series supports a password and an IP filter.
• Define power-on and safe values for outputs so they go to a known state if communication is lost. The ET-2242, for example, supports both, plus a dual watchdog.
• Check isolation between field wiring and network. The ET-2200 modules mentioned here have 3000 VDC I/O isolation.
• Fuse the module supply separately and update the wiring diagrams.

Which ICP DAS product groups fit

• Ethernet I/O modules (ET-2200, ET-7200, OPC UA I/O) for parallel monitoring without PLC changes.
• Fieldbus I/O modules (PFN-2000, PROFI-5000, EIP-2000, CAN-2000C) when the PLC must read the signal.
• Fieldbus gateways (GW-7662, GW-7663, GW-7553, GW-7472, I-7232D) to bring Modbus I/O into the PLC's network.
• IIoT communication servers and edge controllers (UA-5231M, WISE-5231M) to pass data to MES or cloud platforms.

Send technical sales the PLC type, its fieldbus and your signal list, and we will suggest the route and modules that fit.