C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Troubleshooting Foundation Fieldbus Redundancy Failures with IM 655-FF in S7-410H Systems

Troubleshooting Foundation Fieldbus Redundancy Failures with IM 655-FF in S7-410H Systems

In redundant SIMATIC S7-410H systems utilizing Compact FF Link (IM 655-FF) modules on a Foundation Fieldbus (FF) ring, field devices failing and PDM communication dropping whenever the system switches CPU masters is caused by unsynchronized hardware parameters or a compromised fiber-optic synchronization link between the CPUs. If one CPU has a damaged optical transceiver or desynchronized bus parameters, the standby CPU cannot maintain active master token arbitration on the redundant PROFIBUS-DP / PROFINET lines connected to the IM 655 coupler. To resolve this: 1) Replace damaged fiber-optic sync transceivers to restore full redundant lockstep; 2) Ensure both CPUs have identical HW Config parameters and transmission rates compiled; and 3) Verify that the IM 655-FF active bus modules and coupler firmware match on both racks.

Table of Contents

Executive Summary

High-availability process automation architectures frequently bridge Foundation Fieldbus (FF-H1) instrumentation into redundant SIMATIC S7-400H or CPU 410-5H controllers using the SIMATIC Compact FF Link (IM 655-FF). A rare but critical failure mode occurs when FF field devices function flawlessly while CPU 0 is Master, but immediately transition to fault status on WinCC OS and lose SIMATIC PDM communication the moment the system switches to CPU 1. This symptom points to a failure in redundant fieldbus line handover. This technical guide explains the redundant arbitration mechanics of IM 655-FF couplers, analyzes the impact of degraded optical synchronization links, and provides the systematic diagnostic procedure to restore bumpless failover.

Architecture and Fundamental Mechanics

Redundant S7-410H to Foundation Fieldbus Architecture

+-----------------------+                         +-----------------------+
| CPU 410-5H (Rack 0)   |   Fiber-Optic Sync      | CPU 410-5H (Rack 1)   |
| Active Master         |<=======================>| Standby Partner       |
| [DP/PN Subnet 1]      |   [TRANSDUCER FAULT!]   | [DP/PN Subnet 2]      |
+-----------|-----------+                         +-----------|-----------+
            |                                                 |
            +-----------------------+-------------------------+
                                    |
                                    v Redundant Fieldbus Lines
+-------------------------------------------------------------------------+
|                 Compact FF Link Assembly (IM 655-FF)                    |
|                 (6ES7655-5FF00-0AB0 on Active Bus Module)               |
|                                                                         |
|   - Coupler evaluates Line A vs Line B heartbeat & master tokens        |
|   - If Sync Link is Degraded / Asymmetric:                              |
|     * Standby CPU fails to maintain synchronized token handover         |
|     * Upon failover to Rack 1 -> FF coupler detects bus timeout         |
|     * FF-H1 Segment Enters FAULT! (All field transmitters drop offline) |
+-----------------------------------|-------------------------------------+
                                    |
                                    v Foundation Fieldbus H1 Ring
+-------------------------------------------------------------------------+
|                 FF-H1 Segment Field Devices (31.25 kbps)                 |
|                 (Pressure, Temperature, Flow Transmitters)              |
+-------------------------------------------------------------------------+

Why One-Sided Redundancy Fails

  1. The Role of the Optical Synchronization Link: Redundant S7-400H / CPU 410-5H CPUs operate in cycle-by-cycle lockstep via dual fiber-optic synchronization submodules. If one optical transceiver is damaged (operating in degraded single-cable mode or dropping packets), the operating system cannot perform seamless bumpless state updates for peripheral I/O tokens.
  2. IM 655-FF Master Handover: The Compact FF Link sits as a slave on both redundant subnets. When Rack 0 is Master, Line A provides the cyclic PZD token. Upon switchover, Line B must immediately pick up the token without exceeding the bus watchdog time (Ttr). If Rack 1's bus parameters differ or synchronization lag occurs, the IM 655 trips into line fault.
  3. HW Config Compilation Imbalance: Downloading hardware changes in RUN (H-CiR) while the sync link is degraded can result in the modified configuration being stored in only one CPU's memory, causing the other CPU to hold an obsolete bus configuration.

Step-by-Step Implementation Procedure

Step 1: Inspect Optical Synchronization Transceivers and Diagnostic Buffer

  1. Connect the Engineering Station to the S7-410H controller.
  2. In SIMATIC Manager, select both CPUs and press Ctrl+D to open Module Information.
  3. Open the Diagnostic Buffer tab on both Rack 0 and Rack 1 CPUs.
  4. Look for Event IDs relating to synchronization:
    - Event 16#43E2: Redundancy lost / Synchronization link error.
    - Event 16#4567: Defective sync module or fiber-optic cable.
  5. Inspect the physical sync transceivers on the CPU front panels; replace any optical submodules (6ES7960-1AA04-0XA0 or 6ES7960-1AB04-0XA0) showing yellow or red FAULT LEDs.

Step 2: Verify IM 655-FF Redundant Bus Wiring and Active Bus Modules

  1. Inspect the physical installation of the Compact FF Link:
    - Ensure both IM 655-FF modules are mounted on the certified Active Bus Module BM IM/IM (6ES7655-5DX00-0XE0).
    - Verify that redundant bus cables from Rack 0 and Rack 1 are connected to Line A and Line B respectively.
    - Verify shield grounding and termination on the FF-H1 segment.

Step 3: Verify Identical Bus Parameters in HW Config

  1. In SIMATIC Manager, open HW Config for the redundant station.
  2. Open properties for the PROFIBUS-DP or PROFINET subnet connecting Rack 0 to IM 655.
  3. Note the transmission rate (e.g., 1.5 Mbps) and bus profile (e.g., DP or Standard).
  4. Open properties for the subnet connecting Rack 1 to IM 655.
  5. Verify that transmission rates, bus profiles, and retry limits match identically on both subnets.
  6. In HW Config, select Station > Save and Compile.

Step 4: Perform Complete Synchronized Download

  1. Once physical fiber transceivers are replaced and healthy lockstep is restored (RUN/RUN redundant LED status on both CPUs):
  2. Execute an online hardware download:
    - In redundant operation, use PLC > Download to CPU with modified configuration (H-CiR).
    - Alternatively, during a plant maintenance window, download HW Config with the controller in STOP to ensure total database congruence across both CPU memory cards.

Verification

  1. Redundancy Health Check: Verify that both CPU 410-5H modules show steady green RUN LEDs with zero flashing REDF or IFM fault LEDs.
  2. Manual Master Switchover Test: In SIMATIC Manager Module Information, trigger a controlled master-standby switchover (Operating Mode > Switch to CPU with modified configuration / Switchover).
  3. FF Segment Continuity: Confirm that when Rack 1 becomes Master, all Foundation Fieldbus devices remain active and green in WinCC OS graphics, with zero communication dropouts in SIMATIC PDM.

Limitations and Operational Precautions

  1. Damaged Transceiver Operating Risk: Never operate an S7-400H / CPU 410-5H system in production with a known damaged fiber-optic synchronization transceiver; redundant failover cannot be guaranteed.
  2. FF Coupler Firmware: Ensure both redundant IM 655-FF modules possess identical firmware revisions (e.g., V1.1.x) to prevent failover arbitration mismatches.

Engineer FAQ

Why do FF devices fail when switching the master CPU?

The standby CPU's fieldbus line cannot establish master token communication with the IM 655 coupler, caused by broken sync links or mismatched bus parameters.

Can S7-410H run redundantly with one damaged sync port?

It can run in degraded single-channel sync mode temporarily, but seamless bumpless failover and online H-CiR downloads become unreliable.

What is IM 655-FF?

The Compact FF Link module used in PCS 7 to integrate Foundation Fieldbus H1 field segments into PROFIBUS or PROFINET controller networks.

Where can I replace S7-400H optical transceivers?

Optical submodules are hot-swappable hardware components ordered through an authorized Siemens distributor or the Siemens Industry Mall.

Does SIMATIC PDM communicate through the standby CPU?

PDM routes communication through the active master CPU; if the active CPU loses communication to the FF link, PDM cannot reach the devices.

What bus module is required for redundant IM 655 couplers?

The Active Bus Module BM IM/IM (6ES7655-5DX00-0XE0) is required for redundant coupler configurations.

How do I verify fiber-optic cable health?

Check the CPU diagnostic buffer for sync link events (16#43E2) and inspect optical power levels using a fiber optic power meter.

What is the baud rate of Foundation Fieldbus H1?

Standard FF-H1 operates at 31.25 kbps with bus power delivery to field transmitters.

Does changing bus parameters require an AS stop in H-systems?

Redundant H-systems allow downloading modified bus parameters in RUN via H-CiR if synchronization is fully intact.

Can IM 655-FF operate in a ring topology?

Yes, Foundation Fieldbus H1 segments can be configured as a spur or redundant ring topology using active field distributors (AFDiSD).

Technical References

Related Articles

Related Tags

  • Foundation Fieldbus
  • IM 655-FF
  • S7-410H
  • Redundancy Failover
  • Sync Transceiver
  • SIMATIC PDM
  • Compact FF Link
20 respuestas