Remote I/O Modules

Remote I/O modules are input/output devices installed outside the controller’s own rack or cabinet, often in the field near the instruments they serve. They connect field instruments to a central controller over a digital network instead of through individual hardwired connections. That shortens cable runs and frees up marshalling cabinet space, so remote I/O can suit sites with spread-out equipment or tight cabinet space.

This guide comes from Vista Projects, a multi-disciplinary engineering and system integration firm headquartered in Calgary, Alberta.

What Are Remote I/O Modules?

A programmable logic controller (PLC) or distributed control system (DCS) hears from the field and answers back through I/O (input/output) modules or other interfaces. Inputs bring signals in, like a level switch closing. Outputs send commands out, like starting a motor.

The difference between local and remote I/O is where the modules live. Local I/O sits in the same rack or cabinet as the controller’s processor, and in a conventional hardwired setup, every field signal is wired back to it. Remote I/O sits outside that rack or cabinet and talks to the controller over a network. It’s often near the equipment it serves, but it can also go in another cabinet or on a machine.

Most remote I/O modules handle a set number of channels for one signal type, commonly 4, 8, 16, or 32, though some are configurable. Mount several modules together with a power supply and a network interface, and you have a remote I/O station. Some vendors call it a drop or a node, and others call it a rack.

How Do Remote I/O Modules Work?

Remote I/O modules work by moving the point where field wiring ends from a central cabinet to a station closer to the field. Input modules at the station convert each signal to a digital value, and a communication interface sends the data to the controller over an industrial network. Commands come back the same way, and output modules turn them into signals that drive valves and motors or sound alarms. One network link, or a redundant pair, can replace many long point-to-point cables.

How Does Remote I/O Work, Step by Step?

Here’s the round trip a single signal makes.

  1. The field device sends a signal. A level transmitter can send a 4-20 mA current, or a limit switch opens a contact.
  2. The input module reads it. Many analogue modules condition the signal and convert it to a number, and, when configured, they also detect a broken wire.
  3. The network adapter sends it. The data goes to the controller over a protocol like EtherNet/IP or PROFINET.
  4. The controller decides. It uses remote values much like local ones, allowing for network update time.
  5. The output module acts. It switches a solenoid or starts a pump, or sets a valve position.

HART-capable analogue modules also let technicians check transmitter settings from the control room, where the module supports it.

What Happens During a Remote I/O Communication Loss?

When a remote I/O station loses contact with its controller, outputs with a configured communication-fault response move to their documented fault state. Common options are holding the last value or applying a set value, like off or closed. The choices and timing depend on the product, and picking the right fault state for each output is a process safety decision, not a factory default to accept.

Don’t assume the shipped setting. If an output holds its last run command, a pump that should stop can keep running. Test communication loss under control during commissioning.

A redundant ring network keeps traffic moving after a single cable break, if every device supports it. PROFINET’s Media Redundancy Protocol, defined in IEC 62439-2, recovers in under 200 milliseconds on a ring of up to 50 devices using its 200 ms profile.

Remote I/O vs Hardwired I/O

Remote I/O modules exist to cut the wiring that a centralized design piles up. In a typical centralized design, each instrument is wired to a local junction box, and local junction boxes feed larger central ones. From there, multicore home-run cables carry every pair to a marshalling cabinet for cross-wiring. On large projects, that’s a lot of terminations.

Conventional hardwired I/O runs each field signal back to central I/O on its own conductors. Remote I/O collects field wiring at a station near the field devices and sends the signals over an industrial network. That can mean less copper, fewer terminations, less marshalling, and less cabinet space, in exchange for a reliance on the network and field power.

AttributeConventional hardwired I/ORemote I/O
Where field wiring endsCentral marshalling cabinetsA station near the equipment
Cable back to the cabinetMulticore home-run cablesCopper or fibre network links
MarshallingOften neededReduced or removed
Central cabinet spaceLargerCan be smaller
Late design changesNew cross-wiringOften handled in software
New dependenciesNo network to manageNetwork health, field power

What Remote I/O Savings Look Like on a Real Project

In a 2019 study reported by Control Global, Bechtel redesigned a just-completed project with 2,253 I/O signals across four buildings using configurable remote I/O modules. The redesign reduced 80 field junction boxes to 39 smart I/O enclosures and 195 home-run cables to 16. Bechtel eliminated 21,000 home-run cable terminations and almost two million linear feet (about 610 kilometres) of cable, along with all 23 marshalling cabinets. DCS cabinets went from eight to five, and the cabinet footprint shrank from 864 to 234 square feet (about 80 to 22 square metres). These are design comparisons, not audited construction results.

The redesign did add some costs, because it needed redundant power and redundant network links, plus longer fan-out cable. Canadian facilities should check these figures against local labour, material, climate, and code conditions. For a few points near the control room, direct wiring can still cost less.

Weighing remote I/O against conventional wiring for an upcoming facility or expansion? Talk to Our Experts

Main Parts of a Remote I/O Station

A remote I/O station usually has five main parts: a network adapter, a power supply, input and output modules, terminal bases, and an enclosure. The exact build varies by platform, and surge protection or ring switches are added where the design calls for them.

  • Network adapter (also called a communication coupler or head-end). Links the station to the controller network.
  • Power supply. 24 V DC is common, with a redundant pair where availability calls for it. In Canada, classify each field circuit under CSA C22.1, where Section 16 covers Class 1 and Class 2 circuits.
  • Remote I/O modules. A module or channel for each signal (see the table below). Some can be hot-swapped where the manual allows.
  • Terminal bases. On platforms that have them, field wiring stays put when a module is changed.
  • Enclosure. Rated for the environment and the hazardous-location classification.
  • Network media. Standard copper Ethernet is limited to about 100 metres per link. Fibre suits long or electrically noisy runs, including links between buildings.
Module typeWhat it handlesExample field device
Digital input (DI)On/off contact statesLimit or pressure switch
Digital output (DO)On/off commandsSolenoid valve, motor starter
Analogue input (AI)Current or voltage, often 4-20 mALevel, pressure, and flow transmitters
Analogue output (AO)Current or voltage commandsValve positioner, drive speed reference
Temperature inputRTD or thermocouple signalsProcess temperature sensors
Pulse or counter inputFrequency or pulse signalsTurbine flow meters, encoders

Types of Remote I/O, Including Universal I/O and Electronic Marshalling

Remote I/O comes in three physical formats, plus features that apply across them.

  • Chassis or rack-based remote I/O. Backplane I/O in a remote cabinet, linked by a remote adapter.
  • Modular DIN-rail I/O. Narrow plug-in modules on a rail inside a field enclosure, sized to the signals in each area.
  • On-machine block I/O. Sealed, IP-rated blocks mounted straight on conveyors and other machinery.
  • Hazardous-area remote I/O. Certified for classified locations, some with approved intrinsically safe circuits.
  • Configurable (universal) I/O. Signals land on any channel and get set up in software, which eases late changes. Some vendors call related approaches electronic marshalling.
  • Wireless I/O. WirelessHART or ISA100 field instruments on a wireless network, best for monitoring hard-to-cable points. Control loops need engineering and validation first.

Remote I/O Hazardous Area Installation

Some petroleum and chemical facilities contain classified locations, where an explosive gas atmosphere may be present. Putting I/O near the instruments can avoid long multicore runs, and some intrinsically safe remote I/O systems remove separate barrier cabinets.

Remote I/O products are available with Zone 2 and Class I, Division 2 approvals. Some offer approved intrinsically safe circuits for Zone 0 and Zone 1 or Division 1 field devices. In Canada, the rules come from the facility’s hazardous area classification and Section 18 of CSA C22.1, the Canadian Electrical Code. CSA states that new installations use the Zone system, while existing Division installations may continue under Annex J. For comparison, the U.S. equivalent is NFPA 70 (the National Electrical Code), but Canadian requirements take precedence on Canadian sites.

Where Remote I/O Modules Are Used

Remote I/O modules are often considered when field signals sit far from the controller, or cabinet space is tight. Documented applications include tank farms, process units, compressor and pump stations, multi-well pads, pipeline stations, and modular SAGD facilities. In brownfield work, full cable trays or marshalling cabinets can make remote I/O worth evaluating.

If remote I/O carries monitoring signals, like tank level switches, a network failure should raise a communication alarm, not show a held value as current.

A remote I/O enclosure can hold live circuits from several sources, and switching an output off over the network does not isolate energy. Before maintenance, isolate every source with lockout/tagout and verify. In Alberta, Part 15 of the Occupational Health and Safety Code governs this, with CSA Z460 as the Canadian lockout standard. For work near energized equipment, CSA Z462:24 applies where adopted or required. Other provinces set their own rules.

Remote I/O vs Distributed I/O vs RTU vs Fieldbus

Remote I/O and distributed I/O both place I/O away from the controller on a network, and many vendors use the terms interchangeably. The difference is that remote I/O relies on a central controller, while some distributed I/O adds local logic. A remote terminal unit (RTU) runs its own program and reports to a SCADA system over long distances. With a fieldbus like FOUNDATION Fieldbus H1, instruments talk digitally to the host, which can remove the I/O module layer.

AttributeRemote I/ODistributed I/ORTUFieldbus devices
Where the logic runsCentral controllerMostly centralIn the RTUHost or devices
If the network failsOutputs go to their fault stateSome keep limited functionsDepends on its programDepends on the design
Typical locationWithin a facilityMachines and plantsRemote sites, often kilometres awayWithin a facility
Example networksEtherNet/IP, PROFINET, Modbus TCPSimilar to remote I/ODNP3 over radio, cellular, or satelliteFOUNDATION Fieldbus, PROFIBUS PA
Illustrative exampleTank farm field enclosureI/O blocks on a conveyorWell head or block valveTransmitters on a process unit

Because vendors use these labels loosely, skip the label and ask two questions: where does the logic run, and what happens when the network drops? For RTUs in wide-area systems, see Vista’s glossary entry on SCADA architecture.

Remote I/O on Capital Projects: What Project Teams Should Know

The choice to use remote I/O modules belongs in early design, because it can change cable tray, cabinet space, field power, and civil works across disciplines, and changing course late gets expensive.

On a capital project, remote I/O work usually moves through five stages. Design sets the I/O and network architecture and assigns each signal in the I/O list. Procurement specifies the platform and its ratings, along with spare capacity. The factory acceptance test (FAT) checks the stations with the control system before shipping. Crews then install the stations, and the site acceptance test (SAT) and commissioning prove each loop and test the failover and fault states.

Ask these before anyone freezes the I/O architecture.

  • Which areas justify remote I/O, and which are cheaper to hardwire?
  • Who owns the I/O list, and how are tag-to-channel changes controlled?
  • How much spare capacity will each station carry?
  • Where will field enclosures get power, and is it redundant for critical stations?
  • What does each output do on communication loss, and who approved it?
  • Will failover and fault states be tested at the FAT and again at the SAT?

Remote I/O cuts terminations but adds mapping work. Each signal passes through several layers of mapping, from the tag to the station and module, then to the channel and network address. When an instrument moves on the P&ID, every one of those records has to change, or they drift apart and create rework risk. A single source of truth, where each value is stored once and every drawing links to it, keeps disciplines aligned. Vista’s instrumentation and controls engineering team works this way. Engineering work in Alberta is regulated by APEGA, and work elsewhere by the equivalent provincial regulator.

Keep Your I/O Data Aligned From Design to Handover

Vista Projects was founded in 1985, and its in-house I&C engineering covers PLC and DCS scopes, plus safety instrumented systems, including remote I/O architecture. Vendor packages are integrated into one plant-wide control system, and project data sits in an Owner-Controlled Digital Execution Environment, so I/O lists stay in step with the design. On one plant-wide control network, Vista revised a preliminary design to use remote I/O with centralized controllers. The star network kept two independent routing paths, and routing the home runs to pre-planned fibre panels saved many kilometres of fibre optic cable. Settling choices like these before the I/O architecture freezes helps reduce avoidable rework and protect total installation cost (TIC).

Consult a Team Expert

Related Topics Worth Knowing

Planning and Installing a Remote I/O System

Vista’s complete guide to planning and installing remote I/O systems covers each step, from the business case to selecting remote I/O modules and commissioning.

Safety-Rated Remote I/O

Safety-critical signals need certified I/O. For a process safety system, apply IEC 61511 (CAN/CSA-C22.2 No. 61511-1 in Canada) to the whole function, using I/O suitable under IEC 61508. Safety-certified remote I/O is available from several vendors. Check the certificate for the SIL rating before specifying it. See safety instrumented systems.

Ethernet-APL

Ethernet-APL (Advanced Physical Layer) runs Ethernet straight to field instruments. On a powered segment, one twisted pair carries power and data at 10 Mbit/s, with trunk runs up to 1,000 metres and intrinsically safe options for hazardous areas, as set out in IEC TS 63444 and IEC TS 60079-47. Expect it to coexist with remote I/O for years.

Cybersecurity for Networked I/O

Networked I/O can open attack paths an isolated copper circuit doesn’t have. The ISA/IEC 62443 series is a major framework for securing control systems, with network segmentation a key layer of defence. Vista’s guide to remote SCADA monitoring covers secure network design for spread-out sites.

Frequently Asked Questions About Remote I/O Modules

What is remote I/O?

Remote I/O is input/output hardware outside the controller’s own rack or cabinet, often near the field instruments, connected to the controller over a network. In a conventional design, the central controller still runs the control program.

Local I/O vs remote I/O: what is the difference?

Local I/O sits in the controller’s own rack or cabinet, so field signals are wired back to it. Remote I/O modules sit elsewhere, often in the field, and link over a network. That cuts wiring and marshalling but adds a network to maintain.

What is the difference between remote I/O and distributed I/O?

There’s no industry-wide definition, and many vendors use the terms interchangeably. Where they differ, remote I/O relies on a central controller, while some distributed I/O products add local logic. Check the documentation, not the label.

Remote I/O vs RTU: are they the same?

No. A conventional remote I/O station depends on a controller elsewhere. An RTU runs its own program and may keep working when its SCADA link drops, depending on its design. RTUs suit remote sites, and remote I/O suits facilities.

What happens to remote I/O outputs if communication is lost?

Outputs with a configured fault response move to their set fault state, usually holding the last value or going to a value like off or closed. Choose each state for the process and test it at commissioning.

Which remote I/O protocols are most common?

Remote I/O products commonly support EtherNet/IP and PROFINET, as well as Modbus TCP, while PROFIBUS DP and Modbus RTU remain in older plants. Pick a network protocol your controller supports.

Can remote I/O be installed in a hazardous area?

Yes. Remote I/O products are available with Zone 2 and Class I, Division 2 approvals, some with intrinsically safe circuits for more hazardous areas. The installation must match the area’s hazardous area classification and, in Canada, CSA C22.1.

Remote I/O marshalling: are marshalling cabinets eliminated?

They can be cut sharply and sometimes removed, because field wires land at the remote station. Bechtel’s comparative redesign of a 2,253-signal project eliminated all 23 marshalling cabinets. Any hardwired signals left may still need some marshalling.

How far can remote I/O be from the controller?

The network sets most of the limit. Standard copper Ethernet reaches about 100 metres per link, while switches and fibre-optic cable extend links to several kilometres. For distant well pads, an RTU or SCADA architecture often fits better.

Plan Remote I/O With Vista’s Engineering Team

Remote I/O moves the point where field wiring ends closer to the field. That can cut home-run cable and marshalling, but it makes the network and its fault states part of the design, so prove the savings with a project-specific cost analysis before committing. Vista Projects, headquartered in Calgary, Alberta, provides instrumentation and controls engineering for energy and industrial facilities, and remote I/O designs for Canadian sites must meet the applicable CSA and provincial requirements. Talk to Vista’s engineering team about the control system scope on your next project.

This article reflects Canadian standards and Alberta regulations, and licensing and code requirements differ in other provinces and jurisdictions. Confirm them with the authority having jurisdiction before you apply them to a project

Related Terminology

Data-centric Execution

Datacentric PDF DL