What is remote I/O? Remote I/O connects input and output signals from different parts of a machine or plant to a central PLC or industrial computer through a communications network. It is also commonly called distributed I/O. Instead of running every field signal cable back to the main cabinet, the I/O modules are installed closer to the devices they serve.

“Remote” does not necessarily mean access over the internet. The controller may be in the main cabinet while an I/O station sits at the other end of the same machine or elsewhere in the plant. Communication can take place entirely on a local industrial network; an internet connection is not required.

How does it work? Sensors convert physical conditions into electrical signals. The remote input module reads those signals and sends their values to the controller. The PLC program makes the control decision and sends output commands back over the network. The output module then provides the appropriate electrical signal to the field device. An HMI or SCADA system can display operating conditions, but normally does not replace the field I/O module.

A pump station example: A pressure transmitter, level switch and valve coil located 30 metres from the main cabinet can connect to an I/O station beside the pump. Pressure and level data travel to the PLC. According to its program, the PLC opens the valve or sends a run command and speed reference to a variable frequency drive. A standard I/O module does not directly control the motor's power current; the drive or a suitable motor starter operates the motor.

Digital input (DI): A DI channel reads an on/off signal from a pushbutton, switch or compatible proximity sensor. Typical states include “product present”, “tank full” and “end position reached”. Input voltage and PNP/NPN compatibility must match the sensor type and the module's specifications.

Digital output (DO): A DO channel switches a signal lamp, relay coil or solenoid valve within the module's voltage and current ratings. Check whether the output uses a transistor or relay, the current limits per channel and per group, inductive load suppression and any external power requirements.

Analog input (AI): An appropriate AI module reads a changing value, such as pressure, level or flow, through a 4–20 mA or 0–10 V signal. For a transmitter that linearly maps 0–10 bar to 4–20 mA, 16 mA represents 7.5 bar. The transmitter range, module input range and scaling in the PLC must agree for the displayed value to be correct.

Analog output (AO): An AO channel sends a variable command, such as a speed reference to a compatible drive or a position reference to a proportional valve. An analog channel is not automatically both an input and an output: AI measures; AO issues a command. Current and voltage outputs are not directly interchangeable either.

Specialised channels: Encoder counting, fast pulse capture, thermocouple, RTD and load cell measurements may require dedicated modules. A temperature sensor can connect directly to a compatible RTD or thermocouple module, or through an appropriate temperature transmitter that converts its signal to a standard analog range. Not every sensor can connect to an ordinary DI or AI channel.

Signal types and network protocols describe different things. DI, DO, AI and AO identify the field signals a station can handle. The industrial communications protocol defines how the station exchanges data with its controller. One remote I/O station can contain both digital and analog channels.

Ethernet-based connections: Remote I/O systems may use PROFINET, EtherNet/IP, Modbus TCP or EtherCAT. An Ethernet port alone does not establish compatibility. The controller and station must support the same protocol, the required controller/device roles and an appropriate configuration.

Other fieldbus options: Remote I/O stations are also available for PROFIBUS DP and Modbus RTU. The RS-485 interface commonly used for Modbus RTU defines electrical communication characteristics; it is not the same thing as the Modbus protocol. Device addresses, baud rate, parity and line termination must suit the network in use.

Response time depends on more than the protocol name. EtherCAT's fast, synchronised data exchange can benefit suitable applications. Actual response time also depends on input filtering, module conversion time, network updates, the PLC task cycle and output delays. Any required synchronisation feature must be supported by the individual devices.

Why use remote I/O? It can shorten field signal cables, reduce the number of cables and terminals at the main cabinet, and simplify expansion and fault diagnosis. It also introduces station power supplies, network infrastructure, addressing and communication fault handling. Local I/O may be more economical for a small machine contained within one cabinet.

Inside a cabinet or mounted on the machine? IP20 modules are generally installed inside a suitable enclosure. Machine-mounted stations may use a rating such as IP67. An IP rating alone does not guarantee chemical resistance, suitability for every washdown process or unlimited underwater operation. Connector selection and installation conditions matter too.

What should you check when selecting a station? Start with channel types and quantities, then check protocol compatibility, signal ranges, output loads, power requirements, isolation, diagnostics and environmental conditions. Cable and connector choices also affect installation and maintenance. Many systems use 24 V DC, but the station, sensors and loads may have separate supplies. Follow the manufacturer's wiring diagram for the actual connections.

What happens if communication is lost? Depending on the module and configuration, outputs may switch off, move to a configured substitute value or retain their last value. Remote I/O stations do not all behave the same way. Watchdog settings, data validity checks and restart conditions after communication returns must suit the application.

Standard I/O and safety I/O are different. Emergency stop and guard interlock functions require appropriately rated hardware, a suitable safety control architecture and validation. Connecting an emergency stop button to an ordinary input module does not make the system safety-rated. Networked safety functions also require a suitable safety protocol and compatible devices.