Troubleshooting S7-300 SF LED with Wago 753-323 Profibus Overload

Problem Description

An Siemens S7-300 CPU enters a system-fault condition immediately after its backplane connector is inserted, while the connected Wago 753-323 PROFIBUS DP fieldbus coupler lights its red overload LED and refuses to start cyclic I/O exchange. Field experience shows this signature appears after a 24 VDC brown-out, a brief supply interruption, or an unplanned cabinet power-down. Removing every field wire from the Wago terminals does not clear the overload LED; only a power-down of the field supply with the backplane connector removed lets the indicator extinguish. Reconnecting the rear Profibus (backplane / bus connector to the CPU) immediately re-triggers the red overload on the coupler and the SF on the CPU.

This behavior is documented in the Wago 753 series coupler manual: the overload LED latches under four discrete electrical conditions, each of which raises a periphery fault signal to the PROFIBUS controller board. The PLC in turn posts a system fault, which is why the SF LED on the S7-300 is illuminated concurrently with the overload indicator on the Wago module. The fault is cleared automatically once the offending condition is removed and after a 1-second settling delay on the coupler.

Affected Hardware and Module Identification

Confirm the exact Wago part by the printed label on the side of the module. The label format typically reads 753-323 / xxx-xxx with a date code and a firmware version. Cross-check the firmware on the label against the GSD file revision installed in STEP 7 or TIA Portal because a mismatch can also produce station-failure entries.

Root Cause Analysis: Why the Overload LED Latches

The Wago 753-323 coupler latches its overload LED and posts a diagnostic alarm to the PROFIBUS master when one or more of the following physical conditions are detected on the output channels (and, for feedback conditions, on the input side):

1. Short circuit of one or more outputs – sustained over-current on a DO channel due to a wiring fault, miswired supply, or a failed field load.
2. Missing supply voltage to the output drivers – the field 24 V that powers the DO driver stages is absent, sagging, or wired with reverse polarity. This is the most common post-power-interruption failure mode because some power supplies briefly hiccup their output regulation and others latch in protection.
3. Fault of an output driver – internal high-side or low-side switch failure in the 753-323 output stage, typically detected by a current watchdog inside the module.
4. Feedback (cross-talk) condition – an input channel reads a level that is inconsistent with the corresponding output command, indicating wiring error or external back-feeding of voltage into the input.

When any of these four states is true, the electronic module transmits a periphery fault signal to the PROFIBUS coupler head. The PLC interprets this as a slave diagnostic interrupt and raises an SF. The channel- or group-fault LED on the affected module also goes red. Per Wago documentation, the coupler drops the overload LED only after the offending condition has been corrected and a 1-second debounce window has elapsed without re-triggering; until then the diagnostic message to the master remains active and the SF LED stays lit.

Reading the S7-300 Diagnostic Buffer

STEP 7 (classic) and TIA Portal both expose the CPU diagnostic buffer with the exact event IDs you need to pin the fault. Open the buffer as follows:

1. Go online to the CPU (STEP 7 V5.x: PLC > Module Information; TIA Portal: Online & Diagnostics > Diagnostic buffer).
2. Locate the most recent Periphery fault (event ID 0x0301 / decimal 769) or Station failure (event ID 0x031C / decimal 796) entries.
3. Drill into the entry: the supplementary information block names the PROFIBUS diagnostic address (for example, 1023 dec / 0x3FF) and the slave's logical slot. This is the Wago head station.
4. Walk the chronological list from bottom up. After a brown-out you typically see: Power-on → Module reconfiguration → Station failure → Periphery fault. The exact ordering tells you whether the master re-detected the slave first and then saw a diagnostic interrupt, or whether the diagnostic interrupt arrived during power-up.

For diagnostic LED philosophy on Siemens F-modules (same SF LED behavior pattern), see Siemens TIA Portal: Error Diagnostics for F-Modules. The same channel-LED / SF-LED interlock applies to non-F PROFIBUS couplers: while any channel is in fault, the channel LED and the SF LED are red, and they go out together once all faults are eliminated.

Step-by-Step Isolation Procedure

The objective is to isolate the four overload conditions (short, missing field supply, output driver fault, feedback) one at a time, while keeping the PLC powered so the diagnostic buffer keeps recording events. Use the order below to converge quickly on the failing branch.

1. Capture state. Open the diagnostic buffer and record the last event ID and the PROFIBUS diagnostic address before touching the cabinet.
2. Confirm Profibus wiring. With CPU in STOP, check the purple Profibus cable shield is bonded to PE at both ends, that the line terminators (typically on the CPU's DP port and on the last coupler) are ON, and that no intermediate node is also terminated. A terminator ON in the middle of the segment plus a missing terminator at the end produces cyclic retries that the CPU will report as station-failure, masking the underlying overload.
3. Verify CPU-isolated swap. Disconnect the bus connector to the S7-300 CPU and apply CPU power only. The Wago overload LED should go out because the fieldbus controller on the head station is no longer being interrogated. If the overload LED stays red with no CPU attached, the fault is local to the Wago module and almost certainly one of the four overload conditions.
4. Remove field wiring. With CPU still disconnected, switch off the 24 VDC field supply, wait 30 seconds, and re-apply it. With all field wiring off the Wago terminals the overload LED must extinguish. If it still latches, move to step 5 (field supply verification). If it clears, proceed to step 6 (channel-by-channel re-energizing).
5. Field supply verification. Measure terminal +24 V to terminal 0 V at the Wago power input with a true-RMS multimeter while the line is loaded (put a 50 Ω / 50 W resistor on the bench supply to simulate worst-case load). The voltage must stay within 20.4 V to 28.8 V. A sag below 20.4 V or a peak above 30 V will trip the Wago's supply watchdog and latch the overload LED. Replace any supply showing more than 2 % droop at full load.
6. Channel-by-channel re-energize. With the CPU still disconnected, restore field wiring one channel pair at a time. After each pair, cycle the field supply and observe the overload LED. The moment the LED latches, the last inserted channel is suspect.
7. Reattach CPU and warm-start. Once the field side is clean, plug the bus connector into the CPU, perform a CPU STOP → RUN, and confirm: SF out, BUSF out, overload LED on Wago out, and the diagnostic buffer records Module OK (0x035E / 862).
8. Functional test. Force one DO through STEP 7 and verify the corresponding input mirror reads back within the configured debounce window.

Power Supply and Field Wiring Verification

After a power interruption, supply wiring is statistically the highest-probability cause of the Wago overload latch. Check the following with the field supply powered up and the Wago module running:

• Voltage at the Wago + / − terminals. 24 VDC nominal; tolerance ±20 % (20.4 to 28.8 V). Reversed polarity will be detected as a missing-supply condition because the input protection reverse-biases the module's internal rail.
• Field wiring routing. 24 VDC field wires must be run separately from PROFIBUS and from any AC drive cables. Induced voltages from a VFD output dV/dt faster than 10 kV/µs can couple into the DC rail, holding the Wago in a feedback fault indefinitely.
• PE bonding. Shield to PE at the cabinet entry only (one-sided shielding is acceptable for DC field wiring; for Profibus use the PROFIBUS grounding concept with shield bonded to PE at both ends and a potential equalization conductor).
• Supply current headroom. Sum all DO channel currents plus coupler electronics. For a 753-323 with 16 outputs at 0.5 A each, worst-case field draw is 8 A. Size the supply at 1.3 × worst-case, i.e., 10 A minimum. An undersized supply will brown-out on the inrush of multiple output loads.

Output Driver and Short-Circuit Detection

If field wiring and supply check out, the fault is inside the Wago electronics. The coupler's diagnostic interrupt payload includes a channel-level fault bitmap. To extract it, use STEP 7 or TIA Portal as follows:

1. Go online to the CPU, open Online & Diagnostics > Diagnostics for DP Slave.
2. Select the diagnostic interrupt entry; the channel-level status will list the slot and channel number in fault (for example, slot 1 / channel 7 of the head station).
3. Cross-check with the physical module: the channel LED for the offending channel should be steady red while healthy channels are unlit.

Verify suspected output driver faults as follows. With the field supply isolated from the load side:

• Set the suspect DO off in the PLC program.
• Power up the field supply. If overload LED still latches without loads attached, the driver inside the Wago module is shorted internally → replace the module.
• Set the suspect DO on with no load → if overload LED now goes red and the corresponding LED goes green, the driver stage is good, the fault is on the load side.

Fieldbus Communication Verification

Once the electrical side is clean, validate PROFIBUS health with the S7-300 in RUN. Use the indicator pattern below as a quick visual triage before deeper checks:

Module Replacement, GSD File, and Firmware Notes

If all four overload conditions are ruled out, the Wago head station itself is suspect. Replace the module as a unit and observe the same procedure:

1. Record the PROFIBUS address set on the rotary/address switches of the old head (e.g., 4).
2. Set the replacement head to the same address. The address must match the GSD configuration in STEP 7 or TIA Portal exactly, including any address offset for downstream I/O modules on the 753 backplane.
3. Do not move termination resistors: the last physical node on the bus must stay terminated regardless of node address.
4. Verify the GSD file revision in STEP 7 matches the firmware revision printed on the replacement module's side label. If the Wago module is newer firmware than what STEP 7 is configured for, either import the matching GSD file from the Wago product page or downgrade the module to a matching revision. Mixing firmware and GSD can drive the head into configuration mismatch, which the CPU logs as an I/O fault rather than the channel-overload event you are debugging.
5. Use a narrow screwdriver to torque the cage-clamp terminals to the Wago-specified 0.5 Nm; under-torqued power terminals will introduce series resistance that the Wago interprets as supply sag.

The diagnostic interrupt logic in the new module is identical to the old one and the periphery-fault event IDs do not change.

Commissioning Verification Checklist

After isolating the fault, run through this check before returning the line to production:

• CPU in RUN, no SF, no BUSF.
• Wago overload LED off; all channel LEDs off in idle state.
• Diagnostic buffer records Module OK (event 0x035E / 862) at module startup.
• Force each output for 200 ms; verify the corresponding input reads back the expected feedback value (if feedback is wired) and that no overload LED blip occurs.
• Cycle the field 24 V supply five times in succession to confirm the module is not borderline-latching on power-up.
• Capture the buffer, export the log as a CSV from TIA Portal, and archive the file for trend analysis if the issue recurs.

Preventive Maintenance Recommendations

The four overload conditions are almost always triggered by an upstream event. To prevent recurrence, address the underlying causes:

• Add a UPS or DC buffer on the 24 V field supply sized for at least 5 seconds of hold-up. The Wago overload latch fires on field supply dips of more than 50 ms because its internal supervisor interprets the dip as a partial brown-out.
• Install surge protection on the 24 V field rail to clip transients above 36 V.
• Separate 24 V and PROFIBUS routes; keep at least 200 mm from VFD motor cables.
• Run OB82 (diagnostic interrupt OB) and OB86 (rack/station failure OB) in the PLC program so the CPU logs every diagnostic event into the buffer instead of swallowing them.
• Record field supply voltage with a data-logging multimeter or the PLC's analog input once a shift. Anything below 22 V during inrush is a leading indicator of an under-sized supply that will fail under load.
• Schedule annual inspection of the Wago cage-clamp torques, PROFIBUS terminator settings, and the shield bond at each cabinet entry.

Frequently Asked Questions