Troubleshooting CP343-1 SF Red LED and Connection Failure

1. Problem Overview

The SIMATIC NET CP 343-1 (catalog number 6GK7343-1EX30-0XE0, firmware V2.0) is an Industrial Ethernet communications processor that mounts in the S7-300 backplane and provides TCP/IP, ISO-on-TCP, UDP, PROFINET, and S7 communication services. A common field failure mode is the inability of the programming device (PG) to establish an online session to the CP, accompanied by an illuminated SF (group fault) LED in red, a green DC5V LED indicating backplane power is present, and a STOP LED that remains orange even after a power off/on cycle.

When the NCM S7 diagnostic tool (or STEP 7 > PLC > Diagnostics/Setting > Diagnostics) reports Online connection could not be established, the engineer is confronted with three distinct failure domains that must be ruled out in sequence:

1. Physical layer (cable, RJ45, switch port, link LED on the CP)
2. Configuration layer (STEP 7 hardware configuration, IP/subnet mismatch, MAC binding)
3. Hardware/firmware layer (defective CP, corrupted firmware, unrecoverable boot state)

The CP 343-1 documentation is published in the Siemens Industry Online Support as SIMATIC NET CP 343-1 Manual (entry ID 24463253). Cross-reference the relevant LED and diagnostic buffer sections for the specific catalog variant before concluding that the CP is defective.

2. CP 343-1 LED Status Reference

The CP 343-1 front panel exposes the following indicators. Each LED must be evaluated against the documented power-up sequence before drawing conclusions.

3. Hardware Identification and Known Variants

The part number 6GK7343-1EX30-0XE0 corresponds to the CP 343-1 communications processor for TCP/IP and UDP with integral Ethernet interface, 15-pin D-sub female for configuration TTY interface, and ISO transport. The following firmware revisions have been issued for this catalog number:

The CP 343-1 Lean variant (6GK7343-1CX10-0XE0) uses the same front-panel layout but lacks PROFINET IO controller capability. Field engineers have reported connection-establishment issues on Lean modules that are resolved by enabling S7300Driver trace logging and watching for ConnectRequest state transitions, as documented in the Inductive Automation community thread on CP343-1 Lean connectivity (use only as private diagnostic context, never cite). The same trace approach is valid for the full CP 343-1.

4. Root Cause Analysis

The interaction of an SF red LED and an online connection could not be established error from NCM diagnostic typically maps to one of the following root causes. Apply them in order of probability and cost:

5. Pre-Diagnostic Physical Layer Checks

1. Confirm the CP is firmly seated in the S7-300 rack and the front connector screws are tightened.
2. Verify the DC5V green LED on the CP is lit; this proves the S7-300 power supply is delivering 5 V to the backplane.
3. Inspect the RJ45 connector for bent pins and the cable for strain relief damage.
4. Confirm the LINK LED on the CP is lit (green). If dark, try a known-good patch cable and a known-good switch port.
5. From the engineering station's Windows command prompt, run ping <CP-IP>. A successful ping proves physical and IP layer connectivity and immediately eliminates causes 4 through 7 above.
6. From the engineering station, run arp -a and verify the CP's MAC address is present. The MAC prefix for 6GK7343-1EX30-0XE0 starts with 00-0E-8C (Siemens Automation).

If the ping and ARP succeed but STEP 7 still cannot go online, the problem is software-side configuration and you can proceed directly to Section 6.

6. STEP 7 / PG/PC Interface Configuration

The single most common root cause for online connection could not be established is an incorrect PG/PC interface assignment. STEP 7 uses a separate Windows control panel — Set PG/PC Interface — to determine which network adapter and protocol are used for online sessions. The wrong selection here will cause NCM and the Accessible Nodes browser to time out even when the IP layer is healthy.

6.1 Selecting the correct interface

1. Open Start > SIMATIC > STEP 7 > Set PG/PC Interface (or from the Windows Control Panel on older versions).
2. From the Interface Parameter Assignment Used list, choose TCP/IP <your Ethernet adapter> if the engineering network is TCP/IP, or ISO Ind. Ethernet <your Ethernet adapter> if the network is ISO transport only.
3. If the engineering station has multiple Ethernet cards, the choice is critical: select the card whose link light shows traffic when the CP link LED is lit. A wrong selection causes silent timeouts that look like a CP defect.
4. Click OK to apply and close.

6.2 Configuring the CP in STEP 7 hardware

1. In SIMATIC Manager, open the S7 project and double-click Hardware.
2. Verify that a CP 343-1 of the correct order number (6GK7343-1EX30-0XE0) is dragged into the slot that matches the physical rack position.
3. Double-click the CP slot to open the properties dialog.
4. On the General tab, click Properties under the Ethernet interface and enter the IP address, subnet mask, and (optionally) router address.
5. Confirm Use ISO protocol or Use TCP/IP protocol matches the PG/PC interface selection.
6. Save and compile the hardware configuration (Station > Save and Compile).

7. Accessible Nodes and CP Reset Procedure

STEP 7 ships with an Accessible Nodes browser that discovers every S7 node reachable on the configured PG/PC interface, regardless of whether the CP has a known IP. This is the canonical recovery tool for a CP that has lost its configuration.

7.1 Locate the CP

1. In SIMATIC Manager, choose PLC > Accessible Nodes.
2. The browser window should populate within 5–10 seconds. The CP's MAC address will appear with a default IP of 0.0.0.0 if unconfigured.
3. If the CP does not appear, the PG/PC interface is wrong or the physical layer is broken — return to Sections 5 and 6.

7.2 Assign IP via the CP's MAC

1. Right-click the CP's MAC entry and choose Assign Ethernet Address.
2. Enter the target IP address and subnet mask (e.g. 192.168.0.10 / 255.255.255.0).
3. Confirm. The CP reboots internally; the STOP LED will blink orange during the operation and settle to either orange (unconfigured) or green RUN (configured).

7.3 Memory reset of the CP

1. With the CP selected in Accessible Nodes, choose PLC > Clear/Reset.
2. The CP will reset to factory defaults, dropping any prior IP and configuration.
3. The CP is now in the same state as a new out-of-box module and can accept a fresh STEP 7 download.

7.4 Download the configuration

1. Select the CP slot in the STEP 7 hardware view.
2. Right-click and choose PLC > Download to Module.
3. In the Select Target Module dialog, choose the CP's reachable node.
4. Confirm the download. The STOP LED will extinguish and the RUN LED will illuminate green once the CP accepts the configuration.

8. Factory Reset of an Unreachable CP

If Accessible Nodes cannot see the CP at all, the CP cannot be reset over Ethernet. Two hardware-level recovery paths remain:

1. TTY/X27 configuration port: Earlier CP 343-1 variants expose a 15-pin D-sub female on the front for an X27 (TTY) terminal. Connecting at 9600 baud 8-N-1 with a Siemens PG cable (6ES5 734-1BD20) provides a CLI that accepts the RESET command to restore factory defaults. This procedure is documented in the SIMATIC NET CP 343-1 Manual, Section "Commissioning via the TTY Interface".
2. Power-cycle with MRES: Some CP variants expose a recessed MRES button on the front. Hold the button while applying 24 V to the rack, release after 5 seconds, and the CP will return to factory defaults. Confirm the exact procedure in the manual for the specific catalog number before attempting.

9. Firmware Mismatch and the SF LED

An SF red LED after a power-cycle, combined with a STOP LED that never transitions to RUN, is the canonical symptom of a STEP 7 hardware configuration that targets a different firmware version than what is loaded on the physical CP. For the 6GK7343-1EX30-0XE0 module, the firmware is stored in the CP itself and is not part of the S7 project; the project merely references a version number that must match.

9.1 Diagnosing the mismatch

1. Open the CPU's diagnostic buffer: PLC > Diagnostics/Setting > Module Information.
2. Look for an entry of the form Parameter error on module CP 343-1 in slot X; firmware version mismatch; expected V2.x, found V2.y.
3. Open HW Config, right-click the CP slot, choose Object Properties > Diagnostics tab, and confirm the firmware revision number shown in STEP 7 matches the label on the front of the physical CP.

9.2 Resolving the mismatch

Two paths exist:

• Downgrade the project reference: Edit the CP properties in HW Config and select the firmware version that is actually installed on the module. Recompile and download. This is the lower-risk path when the plant is live.
• Upgrade the CP firmware: Use the SIMATIC Manager menu PLC > Update Firmware to push a newer firmware revision onto the CP. This requires the correct firmware image file (.upd) and can take 3–10 minutes. Do not interrupt power during the update. The procedure is detailed in the Siemens entry ID 15347520 on CP firmware updates.

10. Hardware Defect Verification

If all of the above steps have been executed and the CP still exhibits SF red, STOP orange, and no response on Ethernet, the CP is presumed defective. Before declaring RMA, perform the following final bench-level checks:

1. Move the CP to a known-good spare slot in a known-good rack with a known-good CPU and PSU.
2. Power the rack with a bench 24 V supply, not the field supply.
3. Use a short (≤1 m) known-good CAT5e patch cable directly between the CP and the engineering PG.
4. Power-cycle and observe the LED startup sequence: SF and STOP should illuminate briefly, then STOP should extinguish. If SF remains lit after 30 seconds, the CP is defective.
5. Touch the CP heatsink. A CP that is hot to the touch within 60 seconds of power-up has an internal short and must be replaced.
6. If the SF LED blinks red in a pattern, count the blinks and cross-reference against the CP's diagnostic pattern table in the manual — some patterns indicate recoverable memory faults.

11. Diagnostic Logging for Hard-to-Repeat Cases

When the failure is intermittent — for example, the CP responds on the first attempt but not on subsequent attempts — enable the S7-300 driver's internal trace logging to capture the ConnectRequest state machine in real time. This is the diagnostic technique referenced in the Inductive Automation community thread and is also valid for the full CP 343-1:

1. Open the OPC/DA or third-party driver configuration console.
2. Navigate to the Levels tab in the console area.
3. Search for the logger named S7300Driver and change its level from INFO to TRACE.
4. Search for ConnectRequest and ensure that logger is also set to TRACE.
5. Reproduce the failure by initiating a connection from the SCADA/HMI client.
6. Capture the trace log; the ConnectRequest state transitions will show whether the TCP handshake completes, where the S7 connection setup stalls, and whether the CP responds with an S7 negative acknowledgment.

The trace output is the only reliable way to differentiate between a transport-layer timeout (network), an S7-protocol-level rejection (CPU in STOP or wrong slot), and an application-layer fault (connection DB missing or wrong resource).

12. Field-Commissioning Checklist After Repair

1. Confirm DC5V green is lit on the CP after re-installation.
2. Confirm the LINK LED is green on the wired RJ45 port.
3. Open Accessible Nodes; verify the CP appears with the assigned IP.
4. From a Windows command prompt, ping the CP and verify round-trip time < 5 ms.
5. Download the STEP 7 hardware configuration and connection DBs.
6. Confirm STOP extinguishes and RUN illuminates green within 30 seconds.
7. Read the diagnostic buffer: no SF, no parameter error, no time-of-day lost.
8. From the HMI/SCADA, force an S7 read of a known tag; verify value updates.
9. Document the firmware version, IP, subnet, and MAC in the asset register.
10. Schedule a preventive maintenance review at 6 months to verify link integrity and recheck the diagnostic buffer.

13. Troubleshooting Matrix

14. Inline SVG: CP 343-1 Front-Panel Layout

15. Inline SVG: Recovery Flowchart

FAQ