PROFIBUS OLM Limits at 45km: S7-400 to ET200 Fiber Solutions

1. Problem Definition

An S7-400 master station must exchange cyclic PROFIBUS DP I/O with one or more ET 200 distributed I/O stations over an existing 45 km underwater fiber optic cable. The cable is presented as a single, spliceless fiber pair (one TX fiber, one RX fiber) with attenuation specified at approximately 0.2 dB/km. The application imposes a hard real-time constraint: critical shedding and interlocking commands must propagate end-to-end in well under 100 ms.

Three architectural decisions must be made before any equipment is ordered:

1. Does the optical budget at 45 km fit the media converter family under consideration?
2. Does PROFIBUS DP remain a real-time, cyclic protocol across that distance, or does the bearer change the cycle model?
3. If the fiber path cannot meet timing or budget, what is the alternate bearer, and does it meet the <100 ms shed time?

2. Optical Budget Analysis for 45 km

Calculate the total optical loss and compare it to the link budget of the chosen media converter. The singlemode 9/125 µm fiber at 1310 nm is the typical assumption for subsea telecom-grade cable with a 0.2 dB/km loss figure.

The 13 dB figure is a hard floor. Any media converter selected for this link must publish a minimum optical power budget of 15 dB to leave a comfortable design margin.

3. Siemens OLM Family and Distance Limits

The Optical Link Module (OLM) family converts PROFIBUS RS-485 segments to fiber optic segments. Several variants exist, but all are designed for campus-scale PROFIBUS networks rather than long-haul industrial backbones. The current product range is documented in the SIMATIC NET catalog.

The 15 km ceiling of the OLM/G11-1300 reflects three independent constraints, not just cable attenuation:

1. Optical power budget: ~13 dB at 1310 nm; consumes 9 dB on 45 km of 0.2 dB/km fiber alone, before connectors and margin.
2. Chromatic dispersion: Long singlemode spans at 1310 nm accumulate pulse spreading, reducing signal integrity at the OLM's clock and data recovery circuit. The OLM is optimized for ≤ 15 km; beyond this, the eye diagram closes.
3. PROFIBUS bit-error behavior: Once the link is electrically marginal, the DP cycle is corrupted and the master reports station failure rather than gracefully degrading latency. The shed signal is therefore lost entirely rather than delivered late.

4. Long-Haul PROFIBUS Fiber Modems

When the path length exceeds the OLM family envelope, industrial PROFIBUS-to-fiber modems fill the gap. These devices are designed for line topologies up to 80 km on singlemode and present themselves to the master as a transparent RS-485 extension. The PROFIBUS DP master does not see them as a bridge or a router — it sees the ET 200 directly on the segment.

4.1 Key Selection Criteria

• Optical power budget ≥ 15 dB to cover 45 km of 0.2 dB/km fiber plus connector and aging margin.
• Wavelength 1310 nm or 1550 nm; avoid 850 nm for this distance.
• Bit-transparent RS-485 extension (no PROFIBUS DP store-and-forward); PROFIBUS DP is timing-sensitive and a buffered bridge would break the cycle.
• Galvanic isolation between RS-485 side and fiber side (≥ 1.5 kV).
• DIP switch selectable PROFIBUS termination (ON / OFF) for the segment end.
• Repeater function in the RS-485 port, so the modem counts as a PROFIBUS segment and not as a station (no DP address consumed).
• Diagnostic LEDs for receive optical power and PROFIBUS activity.

4.2 Optical Interface Specification

5. PROFIBUS DP Cycle Time and Latency Budget

The 100 ms switching time budget must accommodate three delay contributions. None of them is dominated by the 45 km fiber.

1. PROFIBUS DP cycle (master polling all configured slaves, plus the master's own request frame).
2. Propagation delay through the fiber and the modem pair (≈ 5 µs/km × 45 km × 2 = 450 µs round-trip).
3. Buffer and clock recovery latency of the modems themselves (typically 1–3 bit times per direction).

5.1 Cycle Time at Common Baud Rates (Single ET 200 Slave, 16 Bytes I/O)

Fiber propagation is negligible compared with the PROFIBUS DP cycle at any baud rate above 93.75 kbit/s. A bit-transparent fiber pair therefore does not extend the cycle time by more than a few hundred microseconds and leaves ample headroom under the 100 ms requirement.

5.2 Multiple-Slave Case

Add additional ET 200 stations linearly. At 1.5 Mbit/s, each 16-byte slave adds roughly 4 ms to the cycle. Twenty slaves consume the full 100 ms budget; 32 slaves exceed it. If the project includes more than ten ET 200 stations on the remote side, distribute them over multiple PROFIBUS DP segments via a repeater or move the architecture to PROFINET over fiber.

6. SINAUT Wireless and Other Non-Fiber Alternatives

When the fiber route is genuinely unavailable, the Siemens SINAUT ST7 / TIM telecontrol modules remain a documented option. SINAUT was designed for utility telecontrol across WAN bearers (leased line, GSM, dedicated radio).

SINAUT is, however, a telecontrol protocol: data is acknowledged and buffered at each TIM, and store-and-forward is part of the design. Switch-over from primary to standby route, plus end-to-end acknowledgement, is documented in the 400–700 ms range for typical WAN bearers. Internal Siemens engineering feedback on SINAUT radio paths puts switch-over above 400 ms in conservative cases. That figure makes SINAUT unsuitable for the <100 ms shed requirement that this project specifies.

6.1 GSM / Cellular Public Network

Public cellular networks (GPRS, LTE-M, NB-IoT) inherit the same store-and-forward buffering at the TIM, plus additional cellular attach and PDP-context activation delays. Total round-trip including bearer setup regularly exceeds 1 second. Not suitable for hard real-time interlocking.

6.2 Dedicated Industrial Radio

Licensed-band point-to-point digital radio (e.g., 400 MHz or 2.4 GHz / 5 GHz industrial spread-spectrum links) achieves 10–50 ms over 45 km line-of-sight. Wireless security concerns raised in early project reviews are addressed by AES-128/256 link encryption and proprietary frequency registration. The radio path itself meets the <100 ms requirement; the question becomes whether S7-400 to radio to ET 200 is architecturally cleaner than S7-400 to fiber modem to ET 200 when the fiber cable already exists in the ground.

7. ET 200 Configuration as DP Slave

The remote station is typically an ET 200S or ET 200pro with an IM 151-1 DP interface module, configured as a standard PROFIBUS DP slave. The fiber modems terminate the bus segment on both ends; the ET 200 appears on the master's bus as if it were directly attached.

STEP 7 / TIA Portal procedure for configuring the DP slave (illustrated for ET 200S, applies equally to ET 200pro and ET 200MP):

1. Insert the IM 151-1 DP interface module in the device configuration.
2. Assign a unique PROFIBUS address (1–125, default 3).
3. Insert the I/O modules in the slot table consistent with the physical rack.
4. Open the master's PROFIBUS subnet properties and set baud rate, bus profile (DP), and highest station address (HSA).
5. Wire the master to the segment, segment to the fiber modem, fiber modem to the patch panel, patch panel to the 45 km fiber.

For applications where the ET 200 carries an additional CPU and exchanges data with the S7-400 master via PROFIBUS DP as an I-slave, refer to the official TIA Portal configuration example for an ET 200 CPU as an I-slave at TIA Portal V20 — Configuring an ET 200 CPU as an I-Slave.

8. Recommended Architecture

1. Verify the existing fiber with OTDR at both 1310 nm and 1550 nm to confirm attenuation, splice count, and end-to-end length before any equipment is ordered. Confirm the fiber is genuinely singlemode 9/125 µm and not a low-loss multimode.
2. Specify a PROFIBUS-to-fiber modem pair whose optical budget ≥ 15 dB at 1310 nm on singlemode 9/125 µm; both modems configured for line topology (no store-and-forward) and PROFIBUS transparent mode.
3. At the S7-400 end, terminate the DP segment on the modem; do not place an OLM in the path. At the ET 200 end, terminate on the modem and into the ET 200 IM 151-1 DP slave interface.
4. Configure the master for 1.5 Mbit/s as a conservative starting point, then evaluate higher baud rates if cycle time permits.
5. Implement a diagnostic watchdog in the S7-400 program that triggers a controlled trip if the DP slave fails to respond within 200 ms (twice the design cycle), satisfying functional safety requirements for the shed command.
6. Document the optical link budget calculation, the OTDR trace, and the modem datasheets in the project quality dossier.

9. Commissioning and Verification Procedure

1. With the ET 200 powered off, measure receive optical power at the S7-400-side modem. Expect -14 to -18 dBm for a healthy link. Record the value in the commissioning log.
2. Power the ET 200 station and verify PROFIBUS LED activity on both modems.
3. Run a single PROFIBUS diagnostic frame from STEP 7 / TIA Portal; verify that the ET 200 station reports without diagnostics.
4. Trigger a force of a critical output from the master and timestamp the corresponding input echo at the ET 200; confirm round-trip latency under 10 ms at 1.5 Mbit/s.
5. Force a fiber disturbance (introduce 3 dB of additional attenuation with a calibrated attenuator) and confirm the master reports station failure within one DP cycle rather than propagating stale data.
6. Re-verify after 24 h of continuous operation to confirm no drift caused by temperature or aging.

9.1 Required Test Equipment

10. Functional Safety and Shed Command Design

A shed command propagating over a 45 km PROFIBUS fiber link must be designed for the failure mode where the link is unavailable, not just the steady-state latency. Apply the following principles:

• Treat the shed command as a hardwired backup signal in parallel with the PROFIBUS DP command. The PROFIBUS path is the primary; the hardwire is the failsafe.
• Implement a timeout in the S7-400 that escalates to a local trip if the PROFIBUS DP slave diagnostic word is not refreshed within 200 ms.
• Configure the ET 200's output modules to fall to a safe state (de-energize) on PROFIBUS failure or on loss of the cyclic data exchange.
• Log every DP station failure with timestamp in the S7-400 diagnostic buffer to allow post-event analysis of the fiber plant.

11. Troubleshooting Matrix

12. Frequently Asked Questions