Siemens Remote I/O Architecture: Logo 8, S7-1200, and ET 200

Remote I/O Architecture Overview

A remote I/O station is a physically distributed module that exchanges process signals with a master controller over a fieldbus rather than a parallel backplane. In a Siemens Profinet environment the CPU acts as the IO Controller, the field device acts as an IO Device, and a third class, the IO Supervisor (engineering station or HMI), handles diagnostics and parameter assignment. The choice of remote I/O tier - Logo! 8 slave, S7-1200 in IO Device mode, or dedicated ET 200 station - drives cabinet footprint, bus load, redundancy posture, and lifecycle cost of the installation.

When a remote I/O station is selected for a building-services or light-industrial application, three constraints dominate the engineering decision:

1. The station must remain galvanically isolated from the bus on both the input side and the output side, so a field-side short or transient surge does not propagate into the network trunk.
2. The local actuator logic (lighting relays, shutter drives, dimmer stages) must survive a loss of the bus or master controller and continue to fail-safe in the field.
3. The selected module family must integrate with the controller's programming tool using standard libraries so the I/O image is exposed as ordinary process variables rather than vendor-specific handles.

The remote I/O portfolios from Phoenix Contact, the ADAM families from Advantech, the ICP DAS M-7000 / ET-7000 / WISE modules, and the Siemens ET 200 line all satisfy the isolation requirement, but they differ sharply in tooling, certification depth, and integration complexity. Reference documentation for the two main third-party families is published at the Phoenix Contact remote I/O systems product page and the Advantech ADAM remote I/O catalog.

Communication Protocol Selection

Profinet is the native deterministic Ethernet protocol for the S7-1500, S7-1200, ET 200, and Logo! 8 (12/24 RCE variant with Ethernet) families. Profinet supports three device classes:

• Profinet IO - real-time, cyclic, typical update of 1 ms.
• Profinet IO with IRT - isochronous real-time, deterministic below 1 ms with reserved time slots.
• Profinet CBA - component-based automation for modular machine-to-machine data exchange.

For distributed I/O in a non-motion building or process application, Profinet IO without IRT is the default, and an external managed switch is unnecessary because the devices handle the line topology internally through their integrated switch ports.

For mixed-vendor installations, Profinet sits alongside EtherNet/IP (ODVA) and Modbus TCP. The S7-1500 exposes Profinet and Modbus TCP natively; EtherNet/IP on the S7-1500 is provided through the CP 1543-1 communications processor or via an external gateway. When the master is an S7-1500 and the remote I/O is ICP DAS, the M-7000 / ET-7000 / WISE series speak Modbus TCP on a fixed register map and integrate through the MB_CLIENT block on the S7-1500.

Bus topology choice directly affects failure-mode analysis. Profinet permits line, star, and ring topologies. The ring topology with MRP (Media Redundancy Protocol) reconfiguration in 200 ms or less is the standard recommendation for any installation where a single cable break must not drop an entire segment. For higher availability, MRPD (Media Redundancy with Duplicate frame paths) provides bumpless failover when used with the appropriate interface modules and the IRT scheduler.

Siemens Controller Family Comparison

The Logo! 8 family (for example the 6ED1052-1MD08-0BA1 logic module with display) is a logic module with integrated digital and analog I/O. As a slave on Profinet it does not act as a strict IO Device; it acts as a Profinet-compatible slave that exchanges a fixed bit/byte image with the master using the S7 connection protocol via the LOGO! CMR router or by acting as a Modbus TCP server. The footprint is small (72 mm wide for the basic unit), the price floor is the lowest of the three families (approximately €60-70 for the bare logic module in the Italian distribution market), and the programming tool is Logo! Soft Comfort.

The S7-1200 (CPU 1211C, 1212C, 1214C, 1215C, 1217C) is a compact PLC with Profinet IO Controller and IO Device capability. As an IO Device the S7-1200 exposes its local I/O and any attached signal board or SM module as process data to a higher-level controller. The local program continues to run independently of the Profinet link status, which is the property that makes it useful as a distributed I/O station that retains local autonomy. The price floor for an S7-1200 CPU with Ethernet is approximately €150 in the Italian distribution market.

The ET 200 family (ET 200SP, ET 200MP, ET 200S, ET 200AL, ET 200eco) is the dedicated distributed I/O line. The interface module handles the bus interface and the I/O modules snap into the backplane. ET 200SP is the workhorse with a 35 mm or 40 mm module width per channel group and a Profinet interface module that supports MRP, MRPD, and PROFIenergy. ET 200MP carries the same I/O modules as the S7-1500 and is used when high-channel-count and hot-swap capability are required. ET 200AL is the IP65 / IP67 variant for cabinet-free field mounting; ET 200eco is the block I/O variant for distributed sensors. The base price for an ET 200SP Profinet interface module is in the order of €250, with I/O modules priced separately.

ET 200 Distributed I/O Family

ET 200SP is the modern Profinet distributed I/O platform. The interface module (IM 155-6 PN BA, ST, or HF) connects to the bus and the BaseUnit provides the backplane power and the terminal connections. Each slot accepts one I/O module (DI, DO, AI, AO, F-DI, F-DO, technology module, communications module). The HF variant of the interface module supports MRP, MRPD, and shared device operation where multiple controllers read the same I/O. Channel-level diagnostics are surfaced as standard diagnostic alarms in TIA Portal.

For applications where the same I/O modules as the S7-1500 must be used without re-wiring the cabinet, ET 200MP is selected. The interface module (IM 155-5 PN) accepts the full range of S7-1500 I/O modules and supports hot-swap under power with the appropriate BaseUnit configuration. This is the preferred choice for high-channel-count panels where the I/O count exceeds what an ET 200SP station can reasonably carry.

ET 200AL is the IP65/67 variant. It uses M12 or M8 connectors and the I/O modules are field-mountable without a cabinet. Typical applications are conveyor segments, machine skids, and packaging lines where the field termination is taken directly to the sensor/actuator without an intermediary marshalling cabinet. The interface module (IM 157-1 PN) connects the segment back to the Profinet trunk through a single Profinet cable.

ET 200S is the legacy platform retained for spare-part compatibility on existing installations. New designs should select ET 200SP unless the existing cabinet has been built around ET 200S mechanics and the cost of re-engineering the layout exceeds the lifecycle benefit.

S7-1200 as Distributed I/O Station

Configuring the S7-1200 as a Profinet IO Device is done in TIA Portal under Devices & Networks > [CPU] > Operating Mode > IO Device. The S7-1200 exposes its local I/O and SM modules to the higher-level IO Controller (typically an S7-1500 or another S7-1200) through the standard transfer areas. Up to three IO Controllers can read or write the same transfer areas when the S7-1200 is configured as a shared device, which is the basis of a multimaster distributed logic architecture.

The local program on the S7-1200 continues to run when the Profinet link is lost, because the user program executes on the CPU cycle and does not depend on the IO Controller's presence. This property is exploited in the architecture where each S7-1200 retains control of its local zone (lighting, shutters, HVAC) and only exposes supervisory data to the master. The GET and PUT instructions on the S7-1200 are used for S7 communication between controllers; for higher performance and consistency, the BSEND / BRCV pair is used for variable-length data exchange.

A common failure pattern to avoid is configuring the S7-1200 only as an IO Device and not providing a local fallback program. When the Profinet link is lost, the outputs of the S7-1200 behave according to the configured substitute value behavior (keep last value, substitute 0, substitute 1). The local fallback program must therefore be the one driving the outputs in normal operation; the IO Controller's commands are processed as overlaid setpoints rather than as the primary write source.

Logo! 8 as Profinet Slave

The Logo! 8 logic module exposes its digital and analog I/O to a higher-level controller through two integration paths:

1. S7 connection via LOGO! CMR - the LOGO! 8 connects through the LOGO! CMR 2020 (4G router with Logo! support) to an S7 master and exchanges a fixed 32-byte input / 32-byte output image using the S7 protocol.
2. Modbus TCP server - the Logo! 8 12/24 RCE and the Logo! 8.3 variants expose a Modbus TCP server on port 502. The master reads coil and register addresses that map to the Logo! 8 program variables.

The Logo! 8 cannot be configured as a strict Profinet IO Device in the sense of GSD-based IO Device configuration. It is a logic module with Ethernet, not a distributed I/O station in the Profinet sense. For installations where the requirement is to read a small number of digital inputs (limit switches, pushbuttons) and command a small number of relay outputs (lighting, contactor) at a low cost, the Logo! 8 is appropriate. For installations where 32+ channels of I/O must be integrated per station, the S7-1200 or ET 200 is the right choice.

The Logo! Soft Comfort program must be compiled with the network variable block configured to expose the desired inputs and outputs to the Ethernet interface. The block VM 0 through VM 850 is the network variable area; the master reads these as holding registers or input bits over Modbus TCP. Refer to the Logo! 8 system manual for the exact register-to-VM mapping for the firmware version installed.

Third-Party Remote I/O Options

ICP DAS provides three remote I/O families that are widely used in the Italian and European market:

• M-7000 series - RS-485 Modbus RTU I/O modules for distributed sensor integration where Profinet is not required.
• ET-7000 series - Modbus TCP I/O modules with an Ethernet interface and integrated web configuration.
• WISE series - Modbus TCP / MQTT I/O modules with logic engine for rule-based local automation.

The ET-7000 and WISE modules provide galvanic isolation between the field side and the Ethernet side (typically 2500 Vrms). They are configured as Modbus TCP slaves and addressed from the S7-1500 through MB_CLIENT or from the S7-1200 through MB_CLIENT. The integration cost is lower than the ET 200 family, but the diagnostic depth is shallower (no standard Profinet alarms, no MRP, no GSD-based device description).

Advantech ADAM modules provide five families per the Advantech ADAM remote I/O catalog:

• ADAM-6000 - Modbus TCP / OPC UA Ethernet I/O.
• ADAM-6100 - EtherNet/IP Ethernet I/O.
• ADAM-6200 - Modular I/O system with daisy-chain Ethernet.
• ADAM-4000 - RS-485 Modbus RTU I/O.
• ADAM-5000 - Serial / USB converters and repeaters.

Phoenix Contact remote I/O is documented at the Phoenix Contact remote I/O systems page. The Axioline F (IP20) and Axioline E (IP65/67) families integrate Profinet, EtherNet/IP, Modbus TCP, and PROFIBUS DP through a common I/O module library. The Inline family is the PROFIBUS-oriented alternative. Phoenix Contact modules are commonly selected when the application requires ship-classification certifications (DNV, ABS, LR, BV) or ATEX/IECEx zone 2 approval that the Siemens equivalent does not carry.

Electrical Isolation Requirements

Industrial remote I/O modules are specified with at least three independent isolation barriers:

1. Bus-to-logic isolation - the Profinet / Modbus interface is galvanically isolated from the internal logic supply, typically rated 1500 Vrms or 2500 Vrms for 60 seconds.
2. Logic-to-field isolation - the internal logic is isolated from the field-side terminals, again typically rated 2500 Vrms.
3. Channel-to-channel isolation - on higher-end modules, individual channels are isolated from each other to prevent a single short from affecting adjacent channels.

Verify the isolation rating in the module's data sheet before installation. Modules with only functional isolation (typically 500 Vrms or no specified isolation) must not be used in installations where the field wiring is routed alongside power cables or where transients from contactor coils can couple back into the bus. The Logo! 8 logic module's onboard I/O has limited isolation and must not be used as the direct termination for field wiring that carries transients above its rating.

The cabinet design must also respect creepage and clearance distances between field-side terminals and the bus trunk. The ET 200SP BaseUnits provide keyed slots that enforce the segregation; mixing digital and analog BaseUnits into adjacent slots without the appropriate separator base unit breaks the segregation and is a common installation error.

Bus Reliability and Failure-Mode Analysis

A Profinet line is robust against cable breaks only when the topology is a ring with MRP enabled. In a line topology, a single break isolates everything downstream of the break. In a star topology, the loss of the central switch isolates everything connected through that switch. The mitigation depends on the application criticality:

• Non-critical building services (lighting, shutters) - line topology is acceptable, provided each station has local fallback logic that holds the last commanded state.
• Process-critical applications (HVAC plant rooms, water treatment) - ring topology with MRP, with each IO Device connected to two switches.
• Safety-relevant applications - Profisafe over Profinet with ET 200SP F-modules and a F-CPU; the safety layer handles its own channel redundancy independent of the standard bus redundancy.

The failure probability of a Profinet segment in a properly installed building-services environment is low (typical observed MTBF for the bus segment is in the order of 200,000 hours), but the consequences of a single failure can be high if the local fallback logic is not implemented. The architectural rule of thumb is to distribute the control logic so that the loss of one segment does not disable a critical service.

Multimaster Distributed Logic

In a multimaster architecture, multiple CPUs act as IO Controllers and exchange data through the shared device mechanism of Profinet or through S7 connection PUT / GET blocks. A typical building-services layout assigns one S7-1200 per floor or per zone, and one S7-1500 as the supervisory controller that aggregates the data and exposes it to the HMI and the web server.

Each S7-1200 owns its local I/O and runs its local program. The supervisory S7-1500 reads the status of each zone and writes setpoints (lighting scenes, temperature setpoints, occupancy schedules). The HMI connects to the S7-1500 as an IO Supervisor and displays the aggregated view.

The multimaster configuration is configured in TIA Portal under Devices & Networks > [CPU] > Operating Mode > Shared Device. Each shared device can be assigned to up to four IO Controllers, with each IO Controller granted a subset of the submodules. The I/O modules are statically partitioned; they cannot be written by two IO Controllers simultaneously without an arbitration layer in the program.

For installations where the S7-1500 is already on the shelf but the application is light (single residential or small commercial building), an alternative architecture is to use the S7-1500 as the sole IO Controller and use ET 200SP stations as distributed I/O, with the S7-1500 itself running the local logic for each zone. This simplifies the engineering at the cost of a single point of failure. The choice between multimaster and single-master is driven by the consequence of losing the master: if losing the S7-1500 disables critical services, distribute the logic.

Web-Based HMI Integration

The S7-1500 and S7-1200 both expose an integrated web server that serves standard web pages (diagnostic overview, tag tables, data records) and user-defined web pages. User-defined web pages are authored in TIA Portal using the Web Editor and can include HTML, CSS, JavaScript, and SVG graphics. The S7-1500 supports S7-1500 Web API access to tag values from external clients; the S7-1200 supports a subset of the same API on firmware 4.4 and later.

The ESA HMI panels referenced in the field report are industrial-grade HMI panels with built-in web server functionality. The panel connects to the S7-1500 over Profinet, and the operator can access the panel's web interface from any browser on the plant network. This is the standard mechanism for remote monitoring of a building-services installation.

For installations where remote access from outside the local network is required, a VPN router or a cellular router (such as the LOGO! CMR 2020 or the SCALANCE M876-3) is placed between the plant network and the public internet. Direct exposure of the S7-1500 web server to the public internet is not supported and creates a security exposure; the published Siemens security guidance prohibits this configuration.

Selection Criteria and Cost Analysis

The selection between Logo! 8, S7-1200, and ET 200 as the remote I/O tier is driven by five criteria. Use the matrix below to score each candidate against the project requirements before committing to a design.

The general decision rule is:

• Select Logo! 8 when the station has 8 or fewer digital I/O points and no requirement for analog I/O, and the local program logic is fixed and simple.
• Select S7-1200 when the station has more than 8 I/O points, requires analog I/O, and must retain local autonomy when the Profinet link is lost.
• Select ET 200SP when the station is pure I/O (no local control logic) and the engineering toolchain is unified with the master controller.
• Select ET 200AL or ET 200eco when the installation is field-mount (no cabinet) and the I/O must terminate directly at the sensor / actuator.

The total installed cost includes the I/O module cost, the cabinet cost (for IP20 variants), the wiring cost, the engineering cost (TIA Portal license cost for ET 200SP and S7-1200; Logo! Soft Comfort for Logo! 8), and the lifecycle maintenance cost. Lifecycle maintenance is lowest for the ET 200SP because the spare-part catalog is unified with the master controller; the Logo! 8 has a separate spare-part catalog and firmware lifecycle.

Implementation Checklist

Use the following checklist during the engineering and commissioning phase of a Siemens remote I/O installation.

1. Topology decision - line, star, or ring. Select MRP ring for critical applications.
2. IO Controller assignment - assign one CPU as the IO Controller per Profinet segment. For multimaster, configure the shared device mapping in TIA Portal.
3. GSD file import - import the GSDML file for each ET 200 station and each third-party IO Device. Verify the GSDML version matches the device firmware.
4. Device naming and IP assignment - assign a unique device name and IP address to each IO Device. Use the topology editor in TIA Portal to verify the port-to-port connections match the physical wiring.
5. Submodule configuration - assign the I/O channels to the IO Controller. Configure substitute value behavior for each output channel (keep last value, substitute 0, substitute 1).
6. Diagnostic configuration - enable channel-level diagnostics for each I/O module. Configure the diagnostic alarm routing to the HMI.
7. Local fallback program - for each S7-1200 station, implement the local fallback program that drives the outputs when the Profinet link is lost. Test the fallback behavior by physically disconnecting the Profinet cable and verifying the local outputs respond correctly.
8. Web server configuration - enable the user-defined web pages on the S7-1500 / S7-1200. Configure the user rights and the access control list.
9. Ring test - if MRP is enabled, physically break the ring at one point and verify the reconfiguration time is within 200 ms. Restore the ring and verify normal operation resumes.
10. Documentation handover - export the TIA Portal project, the device list, the network topology diagram, and the spare-part list. Archive the project under version control.

Verification and Commissioning

The verification of a remote I/O installation is performed in three stages.

Stage 1 - wiring and power-up. Verify the bus cable is Profinet-certified (typically Cat 5e or higher, shielded, with the shield grounded at both ends through the M12 or RJ45 connector). Power up the IO Controller first, then the switches, then the IO Devices in sequence. Verify the link LEDs on each device indicate link-up at 100 Mbps full duplex.

Stage 2 - device discovery and parameter assignment. Open TIA Portal Online > Accessible Nodes and verify each IO Device is reachable. Assign the configured device name to each IO Device and download the configuration. Verify the IO Device transitions to the AR (Application Relationship) established state and the diagnostic buffer reports no errors.

Stage 3 - functional verification. Force each input and read the corresponding process variable in the IO Controller's watch table. Write each output from the IO Controller and verify the field device responds. For each station with local fallback logic, disconnect the Profinet cable and verify the local outputs respond correctly to the local inputs.

Troubleshooting Matrix

Field-Proven Caveats

Three caveats are commonly observed in the field on European building-services installations.

Caveat 1 - mixed firmware on Profinet segments. When an S7-1500 with firmware 2.9 is connected to an S7-1200 with firmware 4.2 and an ET 200SP with interface module firmware 4.4, the GSD-based configuration is accepted but some diagnostic features are only available on a subset of the devices. Plan a firmware upgrade campaign before commissioning to bring all devices to the same firmware generation.

Caveat 2 - substitute value behavior on ET 200SP outputs. The ET 200SP output module substitute value behavior is configured per channel, not per module. The default is "keep last value" but many field installations set this to "substitute 0" without realizing that the local actuator will de-energize on Profinet loss. Review the substitute value configuration for each channel and align it with the desired fail-safe behavior.

Caveat 3 - Profinet cable routing in existing buildings. Existing residential and commercial buildings often lack cable trays that support the 200 mm segregation distance between Profinet cables and power cables required by the standard. Field routing through existing conduit may force Profinet cables to run parallel to power cables for several meters. The EMC immunity of Profinet is sufficient for short parallel runs, but long parallel runs (more than 10 m) require either shielded Profinet cable with the shield grounded at both ends, or a separate cable tray. Verify the cable route during the site survey.

FAQ