Troubleshooting ET200S IM151-3 PN Profinet IO with S7-300 CPU 317

Problem Overview

When integrating a Siemens SIMATIC ET 200S distributed I/O station—headed by an IM 151-3 PN interface module—into a Profinet IO network managed by an S7-300 CPU 317, several failure modes can prevent the slave from honoring the master's program. Typical symptoms reported in the field include:

• Online visibility of the IM 151-3 PN and its I/O in STEP 7 / TIA Portal, but real process states do not update.
• Inability to force outputs or read inputs even though the device is online.
• Diagnostic buffer entries referencing channel, slot, or station-level faults.
• A diagnostic event code such as DOC5 appearing in the IM 151-3 PN diagnostic buffer or in the S7 CPU diagnostic buffer when the slave is plugged.

These symptoms are almost always traceable to one of five categories: CPU/PN capability mismatch, Profinet device name and IP configuration, hardware topology, GSDML/STEP 7 hardware catalog mismatch, or termination-module and backplane power issues. This reference walks through each cause, the diagnostic evidence to collect, and the corrective steps to restore deterministic I/O exchange.

Identify the Hardware

Before changing configuration, capture exact order numbers (MLFB) and firmware versions of every component. This determines which GSDML/GSD file and which STEP 7 version is required.

Cross-reference the firmware of the IM 151-3 PN against the catalog in STEP 7. Mismatched GSDML versions are a common reason for I/O that is reachable online but does not reflect process state—the CPU sees the device but the channel mapping is rejected at startup.

Root Cause #1 — Profinet Controller Mismatch

The most common reason an ET 200S station appears online but is non-functional is that the CPU is not actually a Profinet controller.

1. Read the front-panel label of the CPU. Look for a second X1 port labeled PN (Profinet) with its own MAC address sticker.
2. Open STEP 7 → HW Config. Right-click the CPU; if only one PN interface appears under the CPU, the controller is Profinet-capable. If none, the CPU is DP-only.
3. Open Online → Accessible Nodes. If the IM 151-3 PN is visible but is not in the configured Profinet IO system, the controller cannot exchange cyclic data with it.

Resolution:

• Use a CPU 317-2 PN/DP with its onboard X1 PN port as the IO controller, or
• Install a CP 343-1 in the S7-300 rack and assign the IM 151-3 PN to that CP as a Profinet IO device, or
• Convert the project to Profibus DP (if the IM is the IM 151-1 Profibus variant, not PN).

Root Cause #2 — Device Name and IP Address

Profinet IO uses device names (not Profibus station addresses) for identification. An IM 151-3 PN that has not been assigned a name equal to the configured name in HW Config will be discovered by the controller, found "online," but rejected from cyclic data exchange.

Assign the device name from STEP 7:

1. Open PLC → Ethernet → Edit Ethernet Node (or Online → Accessible Nodes).
2. Click Browse to display all reachable Profinet nodes; the IM 151-3 PN appears by MAC address if unconfigured.
3. Select the device, click Assign Name, then type the exact configured name (case-sensitive) and confirm.
4. Optionally assign a static IP if the project uses static addressing rather than DCP.

Root Cause #3 — Hardware Topology Mismatch

STEP 7 HW Config allows "assigned topology" or "non-assigned topology" mode. When topology is assigned, every port must match a neighbor; any deviation prevents the device from going into cyclic data exchange.

1. In HW Config, right-click the PN IO system → Properties → Topology.
2. Verify the port-to-port connections drawn in the editor match the real cabling. Each IM 151-3 PN has Port 1 and Port 2; the controller port is X1 (or X1P1/X1P2 on the CPU 317-2 PN/DP).
3. If topology mode is not required, switch to not assigned via Properties → Profinet IO → Port interconnection.

Also check the SF (system fault) LED on the IM 151-3 PN and the BF (bus fault) LED. A solid red SF plus a flashing BF is the classic signature of a Profinet name/IP mismatch. A solid BF with no SF is usually a physical-layer issue (cable, switch, port).

Root Cause #4 — DOC5 Diagnostic Event

A diagnostic entry labeled DOC5 in the IM 151-3 PN or in the S7-300 CPU diagnostic buffer typically refers to a channel-level diagnostic overflow or slot inconsistency reported by the IM at start-up. Practical interpretations observed on SIMATIC ET 200S:

To read the diagnostic buffer, connect STEP 7 online to the IM 151-3 PN (it is reachable as a Profinet node even if not in cyclic exchange) and open PLC → Diagnostic Buffer. Cross-reference any event ID with the IM 151-3 PN manual's diagnostic event table.

Root Cause #5 — Termination Module and Backplane Power

The ET 200S backplane requires a termination module on the very last slot. Without it, the IM 151-3 PN cannot enumerate the station, and modules inserted in the rack are not visible to the controller.

• Order number for the standard termination module: 6ES7193-4JA00-0AA0.
• Verify the termination cap is fully seated and not mechanically damaged. A cracked cap is one of the most overlooked failure causes.
• Confirm a PM-E power module (e.g., 6ES7138-4CA01-0AA0) is providing 24 V to the electronic submodules. Without a PM-E, digital output modules will not switch even if the CPU reports the slot as OK.

Step-by-Step Diagnostic Procedure

1. Capture device order numbers and firmware. Read the front of the IM 151-3 PN, every electronic module, the CPU, and any CPs. Open the diagnostic buffer of the IM 151-3 PN from STEP 7 (target system accessible without joining cyclic data exchange).
2. Verify the CPU has a Profinet port. Look for a second X1 PN port with a MAC label. If absent, plan a CPU swap to 317-2 PN/DP or add a CP 343-1.
3. Match GSDML to firmware. In HW Config, install the GSDML that matches the IM 151-3 PN firmware. Re-import the device, then drag the IM 151-3 PN from the catalog into the PN IO system.
4. Assign the Profinet device name. Use PLC → Ethernet → Edit Ethernet Node, browse, and assign the exact name from HW Config.
5. Confirm subnet and IP. The controller and device must share the PN subnet. If using DHCP/DCP, verify the controller is the only DCP server on the segment.
6. Inspect LEDs. SF, BF, and MAINT (maintenance) LEDs on the IM 151-3 PN pinpoint whether the fault is configuration, cabling, or module-level.
7. Re-download HW Config to the CPU. A partial download can leave the CPU believing the slave is configured when HW Config has been edited.
8. Test with one module. Strip the station to the IM 151-3 PN and one digital input module with termination. If the controller exchanges data, add modules back one at a time until the fault reappears.

Required Software and GSDML

Always import the GSDML before placing the IM 151-3 PN into HW Config. A device placed from the default catalog with the wrong revision appears online but the I/O data is rejected at the slot level — exactly the symptom of "I see the module but cannot read its real state."

Verification After Repair

1. Open Online → Monitor/Modify on the CPU. The I/O addresses of the ET 200S modules must display the actual process value (or -- if the channel is unconnected, never a frozen stale value).
2. Force a digital output on the ET 200S from the VAT table. The corresponding output module LED must illuminate and the field voltage must rise to 24 V at the terminal.
3. Open the CPU diagnostic buffer. Confirm no Station failure or IO device fault entries are appended during the test.
4. Cycle power to the IM 151-3 PN. The device must rejoin cyclic data exchange within 5–10 s without operator intervention. If the Profinet name must be re-assigned, the name was not committed to non-volatile memory on the IM.

Quick Reference — Diagnostic LED Matrix

Field-Proven Caveats

• Online presence in Accessible Nodes proves only layer-2 reachability, not Profinet IO membership. The controller must also have the device in its configured IO system with a matching name.
• The IM 151-3 PN can show I/O as "available" in HW Config even when the GSDML revision is older than the firmware. The slot accepts the configuration but every read returns the substitute value (often 0) — a common source of "real state not visible."
• A Profinet switch with IGMP snooping enabled can blackhole DCP multicast if not configured for Profinet. Use a managed switch that supports Profinet conformance class A or B.
• For CPU 317-2 PN/DP, the PN port is X1 and the MAC address starts with 00-0E-8C or the vendor prefix on the front sticker. Do not confuse it with the DP port's MAC.
• STEP 7 Accessible Nodes over MPI/DP cannot discover Profinet devices. Always use the Ethernet-attached PG/PC for PN node discovery.

Escalation Path

If the IM 151-3 PN continues to refuse cyclic data exchange after the checks above, gather the following before opening a support case with Siemens Industry Online Support:

1. Screenshots of HW Config including the IM 151-3 PN properties (interface, name, IP).
2. CPU diagnostic buffer (export to .txt via PLC → Diagnostic Buffer → Save).
3. IM 151-3 PN diagnostic buffer.
4. Wiring diagram of the ET 200S rack including PM-E location and termination module part number.
5. Firmware versions of the CPU, CP (if used), and IM 151-3 PN.

FAQ