S7-400H IO Limits: 125 ET200M, PROFIBUS Cable, CPU 417-4H Sizing

David Krause16 min read
S7-400SiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview of S7-400H Redundant I/O Architecture

The SIMATIC S7-400H is Siemens' fault-tolerant PLC platform for processes where downtime is not acceptable: power generation, refinery DCS, water treatment, pharmaceutical batch, and continuous chemical lines. The "H" suffix denotes a hot-standby pair of CPUs running in lock-step through fiber-optic sync modules (up to 10 km between the two CPUs using the 6ES7960-1AA04-0XA0 sync module). Both CPUs execute the user program simultaneously; the standby takes over within 100 ms of a primary fault, with bumpless I/O and tag retention.

I/O on an S7-400H is never on the central rack except for a small amount of fast local I/O. Field signals are gathered on PROFIBUS-DP (or PROFINET, with newer CPU 41x-4H firmware) and the dominant slave form factor is the ET200M distributed I/O station, an IP20 modular station built around the IM 153 interface module. In a redundant configuration each ET200M station contains a pair of IM 153-2 modules and accepts up to 12 hot-swappable signal modules per station. With 125 such stations addressable per PROFIBUS master system, the theoretical ceiling is 1,500 signal modules and tens of thousands of channels - more than enough for 4,500 I/O and most process plants short of a full refinery.

Engineering caveat: 125 slaves per master system is the PROFIBUS-DP address space limit (addresses 0-125 minus master = 124 slaves per master; the documented Siemens S7-400H figure of 125 includes the master address bookkeeping). In practical H-system designs with switched I/O, plan for 100-110 redundant pairs per master and use multiple DP master systems for headroom.

Maximum ET200M Bundles, Modules, and Channels

The hard limits of an S7-400H configuration are summarized below. All numbers are taken from the S7-400H Fault-Tolerant Systems manual and the ET200M product manual.

Parameter Maximum Notes
ET200M stations (redundant bundles) per PROFIBUS master system 125 Includes both IM 153-2 pair on each station; address 0 reserved for PG, addresses 1-125 for slaves
IM 153 interface module for redundant ET200M 6ES7 153-2BA02-0XB0 (IM 153-2 HF) or 6ES7153-2BA10-0XB0 (IM 153-2 PN HF) Original 6ES7 153-2BA02-0XA0 is end-of-life; 0XB0 is current
Signal modules per ET200M station 12 (slots 4-15) Slots 0-3 reserved for IM and power supply; max 8 AI/AO or mixed DI/DO/AI/AO up to 12
Total signal modules per master system 125 x 12 = 1,500 Subject to cyclic time and program budget
Channels (32-channel DI/DO assumption) 48,000 45,000+ achievable with 16-channel modules
Channels (8-channel AI assumption) 12,000 Typical analog mix
PROFIBUS master systems per CPU 417-4H 4 (2 DP + 2 optional PN/DP) CPU 414-4H: 2 DP; CPU 412-3H: 1 DP
Maximum PROFIBUS slaves per CPU 417-4H 4 x 124 = 496 redundant pairs Aggregated across all DP masters

For a 4,500-I/O application the math is straightforward. Assuming a realistic mix of 60% digital at 32 channels per module and 40% analog at 8 channels:

  • Digital: 2,700 points / 32 channels = ~85 DI/DO modules
  • Analog: 1,800 points / 8 channels = 225 AI/AO modules
  • Total modules: ~310
  • Bundles required: 310 / 12 = 26 ET200M stations
  • Spare capacity (60%): 47 bundles - well below the 125 ceiling

This is one of the key reasons CPU 417-4H is the recommended platform for 4,500+ I/O: even with 100% analog I/O at 8 channels, the project fits in 47 bundles, leaving headroom for future expansion on the same PROFIBUS trunk.

CPU Selection for High-I/O S7-400H Applications

Siemens publishes the following CPU 41x-4H lineup relevant to redundant applications. Order numbers and memory figures are current as of the SIMATIC S7-400H catalog (2024 edition).

CPU Order Number Work Memory (Code/Data) Bit Memory DP Masters Recommended I/O
CPU 412-3H 6ES7412-3HK14-0AB0 768 KB / 768 KB 8 KB 1 DP + 1 PN < 1,000 I/O
CPU 414-4H 6ES7414-4HM14-0AB0 2 MB / 2 MB 16 KB 2 DP + 2 PN/DP 1,000-2,500 I/O
CPU 416-4H 6ES7416-4FS14-0AB0 5.6 MB / 5.6 MB 32 KB 2 DP + 2 PN/DP 2,500-4,500 I/O
CPU 417-4H 6ES7417-4HT14-0AB0 15 MB / 15 MB 64 KB 2 DP + 2 PN/DP (mixable as 4 DP) 4,500+ I/O, complex batches
CPU 417-4H (PN) 6ES7417-4HT14-0AB0 with FW V6+ 15 MB / 15 MB 64 KB 2 DP + 2 PN PROFINET-converged systems

For a 4,500-I/O process the CPU 417-4H is the right choice. The CPU 416-4H can technically address 4,500 channels but leaves no headroom for the program code, SFC/SFB redundancy handling, and PCS 7 library blocks (APL, I&C) that consume 30-50% of work memory in a typical H-station. The CPU 417-4H also supports the full 4-DP-master configuration natively, which lets you split the field into four independent trunks - a meaningful reduction in single-point-of-failure blast radius and in PROFIBUS cycle time.

Field note: A 4,500-I/O plant built in PCS 7 V9.0 SP2 with APL V9.0 typically compiles to 7-9 MB of code. CPU 416-4H memory fills to 90% within two years of operation. Start with CPU 417-4H for any 4,000+ I/O H-system - the cost delta is under 8% of the H-station price and the memory delta is 2.7x.

PROFIBUS-DP Topology and Cable Length Limits

PROFIBUS-DP cable length is baud-rate dependent. The "1,200 m" figure quoted in field discussions is only valid at the low end of the baud rate table, not at the 1.5 Mbps typical for ET200M. The actual segment limits per IEC 61158 / EN 50170 are:

Baud Rate Max Segment Length (Type A cable) Typical Use
9.6 kbps 1,200 m Slow, legacy devices
19.2 kbps 1,200 m Slow, legacy devices
45.45 kbps 1,200 m Siemens proprietary DP-V1
93.75 kbps 1,200 m Siemens default for H-systems backup trunks
187.5 kbps 1,000 m Diagnostics-heavy, HMI sub-nets
500 kbps 400 m Mid-speed, rarely used in H
1.5 Mbps 200 m Standard ET200M operation
3 Mbps 100 m High-speed motion
6 Mbps 100 m High-speed
12 Mbps 100 m High-speed, rarely used with ET200M

For ET200M bundles on a redundant S7-400H trunk, plan on 1.5 Mbps as the default. That gives you 200 m total trunk length per segment, plus a 2-segment repeater cascade (1 repeater in the middle) for a plant-wide 400 m reach. If the plant is larger than 400 m on one trunk, drop the trunk to 500 kbps (400 m per segment) or 187.5 kbps (1,000 m per segment) and verify the OB1 cycle time budget is still inside the process requirement.

Critical: The 1,200 m figure often cited in informal sources applies only at <= 93.75 kbps. A 1.5 Mbps ET200M trunk cannot span 1,200 m in one segment - that distance requires three repeaters (four segments) and falls outside the PROFIBUS spec for ET200M default operation. Always pull the baud rate from HW Config before specifying cable lengths.

Nodes per Segment, Repeaters, and Segment Limits

Each PROFIBUS segment - meaning the copper cable between two repeaters or between a repeater and the active terminator on the master - is limited to 32 nodes total. The 32 includes both the repeaters themselves and the slaves; do not count only the slaves. The active terminating resistor on the master port and on the last slave consume a stub load each.

Repeater cascade rules:

  • Maximum repeaters in series: 3 (4 segments total, 1 master + 3 repeaters + end-of-line terminator)
  • Maximum total slaves on a single PROFIBUS-DP network: 126 (addresses 0-125)
  • Each repeater counts as a node in the segment in front of it but not the segment behind it
  • Use 6ES7972-0AA02-0XA0 PROFIBUS Repeater (RS485) for cascading; do not use cheap 3rd-party repeaters in H-systems - the redundancy diagnostic time stamps rely on bus timing

For the user's 4,500-I/O application with 26-47 ET200M bundles on a single trunk, plus PG/PC, plus HMI station, plus any remote I/O panel, expect 30-40 nodes per segment. That is feasible, but plan the trunk in 2-3 segments with one 6ES7972-0AA02-0XA0 repeater per plant area.

Switched I/O - the Standard Configuration for S7-400H

PROFIBUS slaves in a redundant CPU system can be wired three ways:

  1. Single-sided I/O: One PROFIBUS trunk, one CPU as DP master, the other CPU gets diagnostic data via backplane. Simplest, lowest cost, but the bus is a single point of failure.
  2. Switched I/O: Two physically separate PROFIBUS trunks. Each CPU is the DP master of its own trunk, and the same ET200M station has two IM 153-2 modules - one on each trunk. Both CPUs poll the I/O; if one CPU or trunk fails, the surviving CPU keeps full I/O update with no process interruption.
  3. Crossed I/O: Two trunks, but the IM 153-2 pair is split: one IM 153-2 on trunk A, the other IM 153-2 on trunk B. Maximum diversity, used only in Ex-2/Ex-3 zones where trunk separation is enforced.

For an S7-400H system, switched I/O is the standard. Each ET200M station is one "bundle" with two IM 153-2 modules. The bundle looks like two slaves to the network (one per IM), at two PROFIBUS addresses (typically consecutive). This is the 125-bundle figure the user is targeting - 125 unique ET200M stations, each contributing two PROFIBUS nodes (so 250 IM 153-2 nodes on the trunk, occupying addresses 4-253 across both DP masters in the redundant pair, but each individual master only sees 125 of them).

Misconception: "125 bundles = 125 slaves on one master" is correct for the master that owns that bundle. But each bundle is two physical slaves, so 125 bundles = 250 slave nodes total on the network, split as 125 per master in the H-pair. The 125 per-master figure is what the field report quotes.

PROFIBUS Cable Type, Connectors, and Shielding

Use only Siemens-approved PROFIBUS cable (6XV1830-0EH10 for the standard violet cable, or 6XV1830-0JH10 for the trailing/robot-rated black cable). Do not use generic RS485 cable - the characteristic impedance (150 ohm +/- 10% at 3-20 MHz) and the 0.64 mm conductor size are not optional. The PROFIBUS connector must be a 6ES7972-0BA12-0XA0 (90 deg, with PG port) or 6ES7972-0BB12-0XA0 (35 deg) for each IM 153-2 and the repeater ports. Always enable the terminating resistor on the connectors at the physical ends of every segment - leave it off on the middle stations.

Shielding is mandatory in industrial environments. Bond the cable shield to functional earth (FE) at both ends using the integrated strain-relief clamp on the PROFIBUS connector. For plants with VFD-driven motors, route PROFIBUS at least 200 mm away from VFD output cables and cross perpendicular at 90 deg, never parallel.

Cyclic Time and OB1 Budget for 4,500 I/O

The PROFIBUS cycle time is a function of slave count, channels per slave, and baud rate. Estimate before sizing the CPU:

Cycle Time Formula (Siemens manual 6GK1970-1BA10-0AA0):

T_cycle = (sum over all slaves of: T_slave_response) + 12 x N_sloves x T_bit + propagation

Where T_bit at 1.5 Mbps is 0.667 us per bit, T_slave_response is the ET200M's processing time (typically 0.5-1.5 ms per station with 12 modules), and 12 bits per byte covers the UART framing overhead (1 start + 8 data + 1 parity + 1 stop).

For 47 ET200M bundles at 1.5 Mbps with a typical 6 ms PROFIBUS update target:

  • Per-slave processing: ~1.0 ms
  • Per-slave message (12 bytes DI + 12 bytes DO + diagnostics): ~32 bytes = 256 bits x 0.667 us = 0.171 ms per station
  • Sum: 47 x (1.0 + 0.171) = 55 ms theoretical, in practice 35-50 ms with 30% bus utilization

With OB1 priority class 1, a 100 ms cycle is achievable on CPU 417-4H for 4,500 I/O. Drop to 50 ms only if the process requires it and budget the CPU work memory accordingly.

Programming in PCS 7 vs STEP 7 for H-Systems

The choice between PCS 7 and STEP 7 fundamentally changes the I/O and program budget:

Aspect STEP 7 (classic) PCS 7 V9.0
Typical I/O block count per I/O signal 1 (user FB) 4-7 (CH_DI, CH_DO, CH_AI, CH_AO, MOT, VLV, MEAS_MON)
Block footprint per signal ~2-4 KB ~10-25 KB (with APL V9.0)
4,500 I/O total code footprint 2-4 MB 7-12 MB
Operator & Alarm integration Manual WinCC tag import Automatic, CFC/SFC + WinCC Explorer
Driver block for ET200M DI/DO/AI/AO User-written or library APL block with faceplate, alarm, and trend built-in
Recommended CPU for 4,500 I/O CPU 416-4H (5.6 MB) CPU 417-4H (15 MB)

For a 4,500-I/O S7-400H system with full operator faceplates, motor blocks (MOT_SPEED, MOT_REV), and valve blocks (VLV_ANL, VLV_DIG), PCS 7 V9.0 SP2 with APL V9.0 is the typical engineering environment. Plan on a CPU 417-4H from the start - do not start with a CPU 416-4H and try to upgrade in a running plant.

Commissioning Procedure for a 47-Bundle S7-400H

  1. Hardware layout planning. Use Siemens COM PROFIBUS or TIA Portal (with S7-400H plugin) to lay out all 47 ET200M stations. Assign consecutive PROFIBUS addresses starting at 4 (1 = master A, 2 = master B, 3 = reserved for PG).
  2. Cable trunk pull. Pull the PROFIBUS cable in a daisy chain, not a star. A star is allowed only when every leg of the star is shorter than 6.7 m; longer drops need a repeater.
  3. Terminator verification. On every segment, verify the bus terminator is ON only on the two physical ends. Disable on all middle stations. Use a PROFIBUS tester (e.g., 6GK1500-0AA10 BC7000) to confirm 1.0-2.0 V differential voltage on each segment.
  4. Baud rate lock. Set the trunk to 1.5 Mbps and stick with it unless the distance forces a lower rate. The auto-baud feature on IM 153-2 should be disabled after initial commissioning - an accidental baud rate drift is a common S7-400H outage cause.
  5. Sync module check. Verify the fiber-optic sync module is installed (6ES7960-1AA04-0XA0) and the LED state is steady green on both CPUs. A flashing sync LED means a fiber or module fault; the CPUs will still run but in single mode without redundancy.
  6. Slave-by-slave rollout. Bring up ET200M station #1 first, verify cyclic I/O, then #2, #3, etc. Do not bring up all 47 stations at once - a single bad address in the middle of the chain will be hard to localize.
  7. Diagnostic buffer test. Force a slave fault (disconnect one IM 153-2 PROFIBUS connector briefly) and confirm the diagnostic event appears in the CPU diagnostic buffer within 100 ms. The standby CPU should take over within 100-300 ms; both should resume I/O updates with no operator action.
  8. Cycle time verification. Read OB1 cycle time from the CPU's "Cycle time" diagnostic. It must be < 80% of the maximum process tolerance.

Troubleshooting Matrix for S7-400H PROFIBUS Issues

Symptom Diagnostic Code (SF / BF) Likely Cause Corrective Action
All slaves drop simultaneously BF (bus fault) flashing on DP master Terminator ON in middle of segment, OR short on trunk, OR baud rate mismatch Power down, walk the chain, verify terminator ON only at end nodes. Set OB86 error mask to enable bus-fault logging. Re-scan baud rate.
One slave drops, others OK SF on that IM 153-2 only Slave address conflict, PROFIBUS connector loose, IM 153-2 firmware mismatch with station Check HW Config address vs physical address. Reseat connector. Verify IM 153-2 FW V6+ matches the rest of the station.
Standby CPU does not take over REDF (redundancy fault) on both CPUs Sync module fiber broken, redundant link not configured in HW Config, both CPUs are in different run states Inspect fiber-optic sync module. Confirm H-Parameters are downloaded (SWR, SZL libraries). Re-run "Assign CPU to H-system" in STEP 7 / TIA Portal.
Cyclic time doubled after adding bundles No SF/BF, but OB1 cycle > 200 ms Bus utilization > 80%, drop-out on retries Reduce baud-rate-dependent retries. Split the network into two DP master systems (1/2 and 3/4). Move diagnostics-heavy stations to a separate low-speed trunk at 187.5 kbps.
Intermittent slave timeouts in Ex zones SF on IM 153-2 with Ex i barrier Ex i barrier signal distortion, common-mode voltage drift Verify barrier is rated PROFIBUS Ex i (e.g., Pepper+Fuchs KFD2-BR-1.PA.1500). Add bus terminator on barrier segment. Check shield bonding at barrier enclosure.

Sizing Checklist for a 4,500-I/O S7-400H

  • CPU: 2 x CPU 417-4H (6ES7417-4HT14-0AB0) with FW V6.0+
  • Sync module: 2 x 6ES7960-1AA04-0XA0 (fiber-optic up to 10 m) or 6ES7960-1AB04-0XA0 (up to 10 km)
  • Power supply: 2 x PS 407 10A (6ES7407-0KA02-0AA0)
  • ET200M bundles: ~47 stations with 2 x IM 153-2 (6ES7153-2BA10-0XB0) each
  • Signal modules: ~310 (mix DI32, DO32, AI8, AO8) - verify against I/O list
  • PROFIBUS trunk: 4 independent DP master systems if 100+ bundles; 1-2 systems if 47
  • Repeaters: 6ES7972-0AA02-0XA0, one per plant area or every 200 m at 1.5 Mbps
  • Cable: 6XV1830-0EH10 (violet, fixed install) or 6XV1830-0JH10 (black, flexible)
  • Connector: 6ES7972-0BA12-0XA0 with PG port at every node
  • Engineering: PCS 7 V9.0 SP2 with APL V9.0 for faceplates, alarms, and trends
  • Memory headroom: 30% free work memory at commissioning closure

Verification - Sizing the Project

Before approving the BOM, run the following numbers and attach them to the design basis document:

  1. Bundles per master: 47 / 1 = 47 (well under 125 ceiling) - PASS
  2. Modules per bundle: 310 / 47 = 6.6 (under 12 ceiling) - PASS
  3. Channels per bundle: 4,500 / 47 = 95 (mix 32-ch DI + 8-ch AI feasible) - PASS
  4. Trunk length at 1.5 Mbps: plant layout, max 200 m per segment, max 400 m with one repeater - VERIFY against site plan
  5. Nodes per segment: 47 bundles x 2 IMs = 94, split across 4 segments = 23-24 per segment - PASS
  6. OB1 cycle at 1.5 Mbps with 47 bundles: ~35-50 ms - PASS for 100 ms process
  7. Code footprint in PCS 7 APL V9.0: ~10 MB - PASS for CPU 417-4H (15 MB)
  8. Sync fiber length: < 10 m (room to room) or < 10 km (separate buildings) - SELECT 6ES7960-1AA04 or 6ES7960-1AB04

FAQ

How many ET200M bundles can an S7-400H CPU 417-4H handle per PROFIBUS master system?

Up to 125 redundant ET200M bundles per DP master, each bundle containing two IM 153-2 interface modules (6ES7153-2BA10-0XB0) and up to 12 signal modules. The CPU 417-4H supports 4 DP master systems, giving a network-wide ceiling of 496 redundant bundles per redundant CPU pair.

What is the maximum PROFIBUS cable length for ET200M on an S7-400H trunk?

200 m per segment at 1.5 Mbps (the typical ET200M baud rate), or up to 1,200 m per segment at 93.75 kbps. With three PROFIBUS repeaters in cascade the network spans 4 segments, so total reach is 800 m at 1.5 Mbps. The 1,200 m figure is only valid at <= 93.75 kbps, not at 1.5 Mbps.

Which CPU should I select for a 4,500-I/O S7-400H application in PCS 7?

CPU 417-4H (6ES7417-4HT14-0AB0) with 15 MB of work memory. CPU 416-4H is technically capable but fills to 90% memory in typical PCS 7 APL V9.0 builds, leaving no headroom for code growth. Always size one CPU step above the calculated footprint for an H-system.

Is switched I/O mandatory on an S7-400H system?

Not mandatory - single-sided I/O is permitted and saves PROFIBUS hardware - but it is the strongly recommended configuration. Switched I/O gives the surviving CPU full I/O update after a primary or trunk failure, with no operator action. The cost delta is two PROFIBUS connectors and one extra IM 153-2 per station, which is small compared to a process trip.

Does the 125-bundle limit apply per CPU or per redundant pair?

Per DP master, which in a switched I/O S7-400H means per CPU. In an H-pair with two DP masters, each master owns 125 bundles, and the redundant pair collectively addresses 250 physical IM 153-2 nodes (125 bundles x 2 IMs) on the network. The 125 figure quoted in the S7-400H manual refers to the per-master limit, not the per-pair limit.

Back to blog