Troubleshooting CP343-1 Lean TCP/IP Connection on S7-300 Systems

David Krause11 min read
S7-300SiemensTroubleshooting
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

Troubleshooting CP343-1 Lean TCP/IP Connection Failures on S7-300 with SCALANCE X208

The CP 343-1 Lean (Siemens order number 6GK7 343-1EX21-0XE0) is one of the most widely deployed Ethernet communication processors for the SIMATIC S7-300 family. When the module refuses TCP/IP traffic and the WinCC engineering station cannot reach it across a SCALANCE X208 switch, the symptom set is consistent: RUN LED on, SF LED red, BF PN LED blinking, no ping reply, and diagnostic buffers reporting "send/recv communication: not configured". This reference walks through every verified diagnostic and remediation step drawn from Siemens field practice, and it consolidates the configuration data the engineer actually needs on the bench.

1. Problem Statement

A SIMATIC S7-300 station is equipped with a CP 343-1 Lean communication processor and connected through a SCALANCE X208 managed switch to a WinCC PC station. Initial commissioning fails with the following observable symptoms:

  • CP 343-1 Lean module is in RUN (green RUN LED).
  • SF (Group Error) LED is solid red.
  • BF PN (Bus Fault PROFINET) LED is blinking.
  • Engineering PC cannot ping the CP at its configured IP address.
  • NCM S7 diagnostics report:
    • Send/Recv communication: in stop — not configured
    • System connection: in stop — the task has not started
  • STEP 7 Edit Ethernet Node / Primary Setup Tool (PST) cannot discover the CP MAC address.
A red SF LED combined with a blinking BF PN LED on a CP 343-1 Lean almost always points to one of three root causes: missing / corrupted IP configuration, PROFINET IO controller expecting a different topology, or a Layer-1 physical link failure (cable type, port, or wiring pair mismatch).

2. Affected Hardware and Firmware Versions

The following Siemens part numbers are in scope for this article. Confirm the exact MLFB before applying any configuration change, as PROFINET capabilities differ between variants.

Component Order Number (MLFB) Firmware / HW Version Notes
CP 343-1 Lean 6GK7 343-1EX21-0XE0 Firmware V1.x (HW V1.1 / diagnostics V1.2.3 reported) PROFINET IO Device capable, single-port 10/100 Mbit/s RJ45
SCALANCE X208 6GK5 208-0BA10-2AA3 Firmware V4.x or higher typical 8-port managed switch, Web-based management
S7-300 CPU e.g. CPU 315-2 PN/DP (6ES7 315-2EH14-...) Firmware V3.x Slot for CP typically in slot 4
STEP 7 (SIMATIC Manager) V5.5 + SPx NCM S7 included Used for HW Config and Edit Ethernet Node

The reported discrepancy between HW catalog version V1.1 and diagnostics version V1.2.3 is normal. V1.1 is the HSP (Hardware Support Package) catalog entry; V1.2.x is the field-loaded firmware revision. Both are functionally compatible for PROFINET IO Device operation. Do not attempt to downgrade firmware to match the catalog entry.

3. LED Diagnostic State Analysis

Every LED on the CP 343-1 Lean front panel maps to a specific fault domain. Read the LEDs before opening any diagnostic tool.

LED Color State Meaning Action
RUN Green On CP firmware running, no CPU stop None — module is alive
SF Red On solid Group error: configuration, IP, or diagnostic buffer entry Open NCM Diagnostics and read buffer
BF PN Red Blinking 2 Hz No PROFINET IO controller connection / link error Check cabling, controller IP, IO device name
BF PN Red On solid PROFINET configuration mismatch Compare controller / device name
LINK / ACT Green On or flickering Ethernet link present, traffic activity If dark: physical layer fault

With RUN=on, SF=on, BF PN=blink, LINK=off, the dominant root cause is almost always Layer 1 — either the wrong cable type (straight-through where crossover is required, or vice versa) or a dead link partner port.

4. Root Cause Identification

Two failure layers must be ruled out sequentially:

  1. Layer 1 — Physical: cable type, port health, link LEDs at both ends.
  2. Layer 3 — Configuration: IP address assignment, subnet mask, gateway, PROFINET IO Device role.

For the SCALANCE X208 + CP 343-1 Lean + WinCC PC topology the typical IP plan is:

Node IPv4 Address Subnet Mask Role
Engineering / WinCC PC 10.0.0.20 255.255.255.0 HMI client
SCALANCE X208 10.0.0.10 255.255.255.0 Management IP (switch fabric)
CP 343-1 Lean 10.0.0.41 255.255.255.0 PLC Ethernet interface

All three addresses must reside in the same /24 subnet. If a single node uses a different mask, ARP resolution will fail and the CP will remain invisible to ping and arping.

4.1 Cable Topology Decision

The CP 343-1 Lean ships with a single RJ45 port and does not support Auto-MDI/MDIX on every firmware revision. SCALANCE X208 ports do support Auto-MDI/MDIX. Therefore:

  • PC → SCALANCE X208: use a straight-through (patch) cable.
  • PC → CP 343-1 Lean (direct, no switch): use a crossover cable if the CP does not negotiate MDIX on the given firmware. Carry one crossover cable in the commissioning kit.
  • CP 343-1 Lean → SCALANCE X208: a straight-through cable is normally sufficient because the switch handles MDIX.
Empirically, the most common single point of failure when commissioning the CP 343-1 Lean is the cable type between the engineering PC and the CP. Verify the cable with a continuity tester or substitute a known-good patch lead before chasing IP parameters.

5. Step-by-Step Recovery Procedure

5.1 Prerequisites

  • STEP 7 V5.5 with NCM S7 installed (part of the SIMATIC Manager DVD).
  • Primary Setup Tool (PST) installed from the SIMATIC NET DVD or downloaded from Siemens Industry Online Support.
  • PG/PC interface set to S7ONLINE → TCP/IP → (fixed Ethernet adapter). Do not use TCP/IP (Auto) when first provisioning — Auto-Negotiation issues are a documented source of discovery failures on CP 343-1 Lean.
  • One crossover cable and one straight-through cable verified with a tester.

5.2 Procedure — Sequenced Actions

  1. Power down the S7-300 station. Connect the CP 343-1 Lean directly to the engineering PC using a crossover cable. Confirm the CP LINK LED lights.
  2. Set the PG/PC interface to S7ONLINE → TCP/IP → (your NIC, fixed). Disable any Wi-Fi NIC or virtual adapters.
  3. Open SIMATIC Manager and choose PLC → Edit Ethernet Node. Click Browse. The MAC address of the CP should appear.
  4. If Browse succeeds, assign IP 10.0.0.41, subnet 255.255.255.0, and confirm. The CP will store the IP in its non-volatile memory (or in the optional C-PLUG if fitted).
  5. If Browse fails, repeat the procedure with the Primary Setup Tool. PST and STEP 7 cannot probe the network simultaneously on the same PC — close one before opening the other.
  6. From a Windows command prompt on the engineering PC, execute ping 10.0.0.41 -t and confirm echo replies.
  7. Power down again. Connect the CP 343-1 Lean to a free port on the SCALANCE X208 with a straight-through cable. Connect the engineering PC to another SCALANCE port, also straight-through. Restore power.
  8. Open STEP 7 HW Config, add the SCALANCE X208 only if PROFINET IO functionality is required (see Section 7). Otherwise the switch may remain out of the project.
  9. Compile and download the HW Config to the CPU. STEP 7 will write the system data blocks (SDB) for the CP.
  10. Re-open NCM Diagnostics for the CP. Confirm:
    • SF LED → off
    • BF PN LED → off (unless a PROFINET IO controller is expected)
    • Send/Recv connection → configured
    • System connection → running

6. IP Assignment via STEP 7 "Edit Ethernet Node"

The Edit Ethernet Node function is the only out-of-the-box method to assign the first IP address to a CP 343-1 Lean without an existing project. It operates at Layer 2 by sending a Siemens-specific DCP (Discovery and Configuration Protocol) multicast.

6.1 Command Sequence

  1. SIMATIC Manager → PLCEdit Ethernet Node.
  2. Click Browse. The tool will populate any reachable CP / SCALANCE / PN device in the broadcast domain.
  3. Select the MAC of the CP 343-1 Lean. Click Assign IP Address.
  4. Enter 10.0.0.41 and subnet mask 255.255.255.0. Leave the router field blank for a single-subnet plant.
  5. Optionally tick Assign PROFINET device name if the CP is also configured as a PROFINET IO Device.
  6. Confirm with Assign. The CP will reboot its communication stack and apply the new IP.
If Browse returns no devices, the Layer 1 link is most likely broken. Confirm both LINK LEDs are lit, try the crossover cable direct to the PC, and verify the firewall is not blocking UDP port 49152 (DCP discovery) on the engineering PC.

7. SCALANCE X208 Integration in HW Config

A common misunderstanding is that the SCALANCE X208 must appear in HW Config for every TCP-based application. In fact:

Use Case SCALANCE X208 in HW Config? Reason
Plain TCP/IP transport for WinCC No Switch operates as a transparent Layer 2 device
SCALANCE diagnostics via Web or SNMP No Use SCALANCE Web UI directly
PROFINET IO via the switch (topology, port diagnostics) Yes Required for PROFINET topology editor and port-level diagnostics
CP 343-1 Lean configured as PROFINET IO Device Optional but recommended Topology editor validates cabling paths

To insert the switch for PROFINET: in HW Catalog → PROFINET IO → Network Components → SCALANCE X-200. Drag the X208 onto the PROFINET IO System line and assign an IP (here 10.0.0.10) plus a PROFINET device name.

8. SDB Container, C-PLUG, and Persistent IP Storage

After an initial misconfiguration, the CP can retain stale parameters in two locations:

  • SDB container on the CPU (system data blocks generated by HW Config).
  • C-PLUG (removable configuration memory) inserted in the CP 343-1 Lean.

If a previous configuration existed and the current download produces persistent faults, the standard recovery sequence is:

  1. Open SIMATIC Manager → PLC → Delete SDB Container (or use the Accessible Nodes → right-click → Delete SDBs).
  2. Power cycle the station.
  3. Open HW Config, recompile, and download again.
  4. If a C-PLUG is fitted, remove it, power-cycle, reinsert, and re-download to force a fresh initialization.
Removing the C-PLUG while powered may corrupt its contents. Always power down the station before extracting or inserting the C-PLUG.

9. PROFINET IO Device Mode Considerations

The CP 343-1 Lean (6GK7 343-1EX21-0XE0) supports PROFINET IO Device mode. If the property "Obtain IP address from PROFINET IO Controller" is enabled in HW Config and no PROFINET IO Controller is reachable, the CP will not acquire its IP and the BF PN LED will blink. Two remediation paths:

  1. Disable "Obtain IP address from PROFINET IO Controller" and assign the IP via STEP 7 Edit Ethernet Node.
  2. Connect the CP to an active PROFINET IO Controller that will assign the IP via DCP at startup.

For pure WinCC TCP/IP communication without a PROFINET controller, option 1 is the recommended approach.

10. Verification Checklist

# Check Expected Result Tool
1 CP LINK LED Solid green Eyes
2 SCALANCE port LED Solid green + activity flicker Eyes
3 Ping from PC Reply from 10.0.0.41 in <1 ms ping 10.0.0.41 -t
4 STEP 7 Browse MAC of CP 343-1 listed Edit Ethernet Node
5 NCM Diagnostics SF off, connections "configured" / "running" NCM S7
6 PG functions on S7 Online view opens, blocks readable SIMATIC Manager
7 WinCC connection test Channel diagnosis green WinCC Explorer

11. Troubleshooting Matrix

Symptom Likely Cause First Action
LINK LED dark on CP Cable fault or wrong type Substitute crossover cable direct to PC
SF red, BF PN blinking, no ping IP not assigned Use Edit Ethernet Node with fixed TCP/IP adapter
SF red, BF PN solid PROFINET IO name mismatch Compare IO Device name in HW Config
Browse finds no MAC PST and STEP7 both open, or MDIX issue Close one tool, force crossover cable
Connections drop after restart Stale SDB or C-PLUG Delete SDB, re-download HW Config
PG/PC interface auto-mode fails NIC Auto-negotiation mismatch Set fixed 100 Mbit/s Full Duplex
SCALANCE X208 unreachable Management VLAN, port security Reset switch via SET button, reassign 10.0.0.10

12. Field-Proven Tips

  • Always carry one crossover cable in the commissioning kit. CP 343-1 Lean firmware V1.x does not always negotiate MDIX reliably with consumer NICs.
  • Use a static IP for the engineering PC — avoid DHCP on commissioning day.
  • Set the SCALANCE X208 management IP before connecting the CP. This eliminates the switch as a fault candidate.
  • When the BF PN LED keeps blinking after the link is up, check whether PROFINET IO Device mode was enabled by accident in HW Config. If only TCP/IP is required, leave the PROFINET checkbox off.
  • After replacing the C-PLUG, power-cycle twice — the first boot re-initializes the C-PLUG, the second reads the freshly downloaded configuration.

FAQ

Why is the BF PN LED blinking on my CP 343-1 Lean even though my TCP/IP application is the only thing running?

The BF PN LED reflects PROFINET IO status, not classic TCP/IP. If PROFINET IO Device mode is enabled in HW Config but no PROFINET controller is online, the LED will blink at 2 Hz. Disable PROFINET IO Device mode in the CP properties if you only need TCP/IP for WinCC.

What is the default IP address of a factory-fresh CP 343-1 Lean (6GK7 343-1EX21-0XE0)?

Siemens ships the CP with no IP address assigned. You must provision it using STEP 7 Edit Ethernet Node or the Primary Setup Tool before any TCP-based client (WinCC, TIA, OPC UA) can connect.

Can I use a straight-through cable to connect my PC directly to the CP 343-1 Lean?

Only if both devices support Auto-MDIX. On CP 343-1 Lean firmware V1.x the safest approach is a crossover cable. Carry one in the commissioning kit to rule out MDIX negotiation failures when the LINK LED stays dark.

Do I need to add the SCALANCE X208 to my STEP 7 HW Config?

Only if you use PROFINET IO topology features, port-level diagnostics, or PROFINET device replacement. For pure TCP/IP transport (WinCC over Industrial Ethernet) the switch can remain outside HW Config and still forward frames transparently.

After a configuration change the CP still holds the old IP. What clears it?

Delete the SDB container on the CPU (PLC → Delete SDB Container), recompile HW Config, download again, and power-cycle. If a C-PLUG is installed in the CP, remove it before the next power-up so the configuration is re-initialized from the CPU.

Back to blog