Resolving Siemens PN/PN Coupler V2 BF Errors in TIA Portal

1. Problem Summary

A Siemens PN/PN Coupler V2 (catalog number 6ES7158-3AD01-0AX0, X2 P1 variant) presents a flashing BF (Bus Fault) LED when integrated into a TIA Portal V12 project, despite the same topology having previously worked under STEP 7 Classic. The PLC assembly comprises a CPU 319-3 PN/DP, an SM 321 digital input module, and a CP 343-1 Lean communications processor running firmware V2.6. The coupler is reachable on the PROFINET network — the engineering station sees it and accepts the assigned IP and device name — yet no cyclic IO data exchange is established with the controller.

This symptom is not a defective coupler. It is a known combination of three issues that all manifest the same way: a bus-fault-only condition, with no application-layer errors and no obvious topology mismatch. The most common cause, in this firmware combination, is a controller-side mismatch between the IO controller's PROFINET stack revision and the device's GSDML version, often hidden behind a missing firmware variant in the TIA Portal hardware catalog.

2. Affected Hardware and Software Inventory

The following components are referenced throughout this document. Use the catalog numbers to verify what is physically installed before pursuing firmware or configuration changes.

The complete mechanical, electrical, and PROFINET specification of the coupler is contained in the official Siemens manual: PN/PN Coupler Hardware Manual (6ES7158-3AD01).

3. Root Cause Analysis: Why the Coupler Fails in TIA Portal

The flashing BF LED on a PN/PN coupler can be produced by any of the following conditions. Each is examined in turn with the evidence that distinguishes it from the others. Walk through the list in order; most field cases resolve at items 3.5 or 3.6.

3.1 Physical layer fault

The X2 P1 port on the coupler must be patched to a switch port or directly to the CPU PN port with a Cat 5e or better cable, max 100 m. Verify the link LED on the switch port and on X2 P1. If the link LED is off, the BF is reporting a physical-layer fault, not a configuration fault. Replace the patch cable and re-test before touching the project. The PN/PN Coupler V2 supports 100 Mbps full duplex with autonegotiation; manual speed/duplex settings are not exposed in the device view.

3.2 Duplicate IP address

If two devices on the subnet share the IP address assigned to the coupler, both report BF. Remove the coupler from the network, ping the assigned IP from the engineering station, and confirm a single response. If there is no response, the assignment has not been written to the device (see Section 3.5). If there are two responses, scan the subnet with PRONETA to identify the conflicting device and reassign.

3.3 Duplicate device name

PROFINET IO uses the device name as the primary identity token. If two devices on the subnet share the coupler name, the controller cannot establish an AR (Application Relationship) with either. Rename the coupler to a unique string and reassign via PROFINET DCP. Siemens recommends a hierarchical, location-based naming convention, for example pn-pn-coupler-line3-cell2. The name is limited to 240 characters, must match the DNS label grammar (letters, digits, hyphens), and is case-insensitive.

3.4 IO controller not commissioned

The coupler must be assigned to a controller in the TIA project. If the coupler appears in the project but is unassigned, or assigned to a controller that is in STOP, the BF LED flashes at 2 Hz with the standard PROFINET alarm pattern. Place the controller in RUN, recompile, and redownload to the controller. Also confirm that the IO controller's PROFINET interface is enabled (not disabled by configuration).

3.5 Assignment not transferred to the device

IP address and device name are not written by the topology editor or the device configuration download. They must be assigned to the physical device using one of:

• "Assign PROFINET device name" from the Online menu of the device or accessible nodes.
• PRONETA tool (Siemens, free of charge) — Network analysis → Assign name tab.
• Web server of the coupler (port 80, default IP 0.0.0.0 until first assignment).

If the assignment is only present in the offline project, the controller cannot find the device, and the BF LED on the coupler indicates the failed AR. This is the single most common cause of a flashing BF on a coupler that is otherwise reachable.

3.6 GSDML or firmware mismatch with the IO controller stack

This is the failure mode most often seen with CP 343-1 Lean V2.6 in TIA Portal V12. The IO controller firmware predates the release of certain PROFINET conformance class features that the PN/PN Coupler V2 requires for AR establishment. The diagnostic buffer of the controller then contains a parameter assignment error, the BF LED on the coupler stays on, and there is no cyclic IO traffic. The same hardware, paired with an integrated PN interface on a CPU 315-2 PN/DP running an up-to-date PROFINET stack, comes up cleanly. Verify the PROFINET conformance class of the controller in the device properties — the PN/PN Coupler V2 supports conformance class B and C.

4. The PN/PN Coupler Configuration Principle

A common misdiagnosis in TIA Portal projects is to treat the PN/PN coupler as an IO device with slot-level configuration. The coupler is in fact a transparent gateway with no slot 0 input or output data, no substitute modules, and no record-data configuration. The only data the controller must provide to the coupler is:

1. An IP address.
2. A PROFINET device name.

All user data passes through unchanged to the partner subnet on the far side. There is no I&M data to fill in, no port statistics to enable, and no module to add in the device view of the coupler. Configuring a 16-bit DI module on the coupler in the device view of the controller is a configuration error — the slot does not exist, and the AR is rejected with "wrong parameter."

Reference: PN/PN Coupler Hardware Manual, Section 6.1.4 — "Configuring the PN/PN Coupler with STEP 7 in the TIA Portal."

5. TIA Portal V12 Catalog Gaps and the CP 343-1 Lean V2.6 Issue

TIA Portal V12 (released 2013) ships with a fixed set of HSP (Hardware Support Packages) and GSDML files. The following firmware variants of the CP 343-1 Lean are commonly present in the catalog:

When the catalog does not list V2.6, the IO device on the PROFINET side of the coupler is also unselectable, and the controller will not generate any IO assignment. In this case, the controller is technically present on the network, but the project has no coupler configuration to download — so the BF LED is expected.

Resolution paths, in order of preference:

1. Install the latest HSP for TIA Portal V12 from the Siemens Industry Online Support portal. The HSP is delivered as a single .xml bundle and must be installed under the project's support tree, not as a system HSP if the TIA installation is read-only.
2. Upgrade TIA Portal to V13 SP1 or later — full firmware coverage of the CP 343-1 family is included in the V13 SP1 catalog.
3. Replace the CP 343-1 Lean with a controller that ships with TIA V12 — for example, the integrated PROFINET interface of a CPU 315-2 PN/DP (6ES7315-2EH14-0AB0) or a CPU 319-3 PN/DP with firmware V3.2 or later.

6. Extended PROFINET Diagnostics and "Wrong Parameter" Errors

Two distinct diagnostic outputs are reported when the coupler fails to come up in TIA V12. Both indicate a controller-stack mismatch and both are resolved by switching to a controller that is native to TIA V12.

6.1 Extended PROFINET diagnostics with CP 343-1 Advanced

When the CP 343-1 Advanced is used in place of the Lean as the PROFINET controller, the project compiles but the AR establishment at download time fails with the following diagnostic message:

"The selected IO device requires the support of the extended PROFINET diagnostics, by the IO controller. This controller is not supported by the configured IO controller."

The CP 343-1 Advanced family supports extended PROFINET diagnostics, but the AR parameter set emitted by the V2.x firmware of the CP 343-1 Advanced when acting as PN IO controller is not always accepted by the PN/PN Coupler V2 when both ends are configured through TIA V12. The coupler reports this as "wrong parameter" in its own diagnostic buffer, and the controller reports it as a station parameterization error.

6.2 "New I/O access error during processing update" with S7-1200

If the S7-1212C is used as the IO controller instead, the project compiles and downloads cleanly, but the diagnostic buffer of the S7-1200 reports:

"New I/O access error during processing update."

The cause is a leftover module configuration in the device view of the coupler — most often a slot 1 DI or DO module carried over from a STEP 7 Classic project. The PN/PN Coupler V2 has no slot 1; remove the module from the offline project, recompile, and redownload. The AR will then establish.

6.3 Decision: switch the controller

When the original CP 343-1 Lean V2.6 cannot be made visible in the TIA V12 catalog and the CP 343-1 Advanced reports the extended-diagnostics error, the path of least resistance is to migrate the PROFINET controller role to the integrated PN interface of a CPU 31x-2 PN/DP that is native to TIA V12. The SM 321 DI module remains on the central backplane; the PROFINET cable from the CPU PN port lands on the X2 P1 port of the coupler.

7. Step-by-Step TIA Portal Configuration Procedure

The following procedure produces a working PN/PN coupler configuration in TIA Portal V12 (and later) without any device-level application configuration on the coupler itself.

7.1 Prerequisites

• TIA Portal V12 SP1 or later. V13 SP1 recommended for full firmware coverage.
• Coupler firmware V2.0 or later. The latest firmware at the time of writing is V2.2.x; verify with PRONETA.
• Engineering station with a routable Ethernet connection to the coupler subnet.
• PRONETA V2.x (Siemens, free of charge) installed for network analysis and name assignment.
• SIMATIC Automation Tool V3.x or later installed for batch firmware updates (optional).

7.2 Install the GSDML for the coupler

The PN/PN Coupler V2 (6ES7158-3AD01-0AX0) is shipped with a GSDML file on the Siemens support portal. Install it via Options → Manage general station description files (GSD) in TIA Portal. The GSDML is identified by the namespace GSDML-Vx.y-Siemens-PNPNCoupler-.... Restart TIA Portal after installation so the device catalog is refreshed.

7.3 Insert the coupler in the project

1. Open the Devices & Networks editor in the TIA project.
2. Drag the PN/PN Coupler from the hardware catalog (under PROFINET IO → Gateway → Siemens AG → PN/PN Coupler) into the network view.
3. Connect the coupler's X2 P1 port to the PROFINET interface of the IO controller (CPU or CP).

7.4 Assign the IP address and the device name

1. Right-click the coupler → Properties → PROFINET interface → Ethernet addresses.
2. Set the IPv4 address. For a 192.168.0.x subnet, 192.168.0.10 is conventional for the coupler.
3. Set the PROFINET device name. The name must be unique on the subnet and follow DNS naming rules (no underscores, no leading digits).

The values typed in the Properties dialog are stored in the offline project only. They must be transferred to the physical device before they take effect.

7.5 Transfer the assignment to the physical coupler

1. In the project tree, right-click the coupler → Assign device name.
2. In the Assign PROFINET device name dialog, select the coupler from the list of accessible nodes (matched by MAC address).
3. Confirm the name and IP. Click Assign name.
4. Repeat for the IP address if it is set independently of the name. TIA V12 allows IP assignment via Online & Diagnostics → Functions → Assign IP address.

7.6 Compile and download the controller

1. Select the controller in the project tree.
2. Compile (Hardware and Software, full rebuild).
3. Download to the target device. If warnings appear, read the warning text — "The IO device requires firmware X but the controller supports Y" is a critical warning and must be resolved before the coupler will come up.

7.7 Verify the BF LED

After the controller reaches RUN, the BF LED on the coupler must be off. The SF LED may briefly illuminate during the parameterization phase, then extinguish. The link LEDs on both X1 P1 and X2 P1 must be solid on. If BF is on or flashing, proceed to Section 8.

7.8 Reference topology

8. Diagnostic Buffer Error Code Reference

The following diagnostic buffer entries are observed on the controller when the PN/PN coupler fails to come up. Match the entry to the resolution path in Section 10.

The "New I/O access error during processing update" (0x0021) is particularly common on the S7-1200 side when a slot 1 DI or DO module has been left in the device view from a previous STEP 7 Classic project. The coupler has no slot 1; remove the module from the project, recompile, redownload.

9. Verification and Commissioning Tests

Once the BF LED is off, run the following checks to confirm end-to-end PROFINET communication across the coupler.

9.1 PROFINET diagnostics on the controller

Open Online & Diagnostics of the controller → PROFINET diagnostics tab. The coupler should appear with status "OK" and the AR state "Established." If the AR state is "Not established" or "Establishing," check the diagnostic buffer (Section 8) for the parameter assignment error code.

9.2 Web server of the coupler

The PN/PN Coupler V2 exposes a web server on port 80. Browse to the assigned IP. The home page shows the device name, IP, firmware, port state for both X1 and X2 (Link up/down, speed, duplex, autonegotiation result), and the partner IO controller IP. Confirm:

• Firmware matches what is in the project (V2.0 or later).
• Partner IO controller IP is the CPU or CP that should be the master.
• Port X2 P1 is "Link up" and the negotiated speed is 100 Mbps full duplex (the default for the V2 coupler).
• Port X1 P1 is "Link up" if the partner subnet is connected; "Link down" if the partner subnet is not yet wired up.

9.3 Application-level ping

Use an S7 PUT/GET or a direct PROFINET IO read of a known input module on the far side of the coupler. If the read returns a value that changes when the physical input is toggled, the gateway is fully operational. A common test input is a single DI on an ET 200S or ET 200SP on the partner subnet.

9.4 Cycle time and send clock

Record the actual IO update time of the coupler in the controller's online PROFINET diagnostics. The PN/PN Coupler V2 has a worst-case update time of 1 ms at send clock 1 ms; an update time greater than 10 ms indicates a watchdog or send-clock mismatch in the controller configuration. The send clock is set in the PROFINET interface properties of the controller under Real-time settings → Send clock. The coupler accepts 1 ms, 0.5 ms (reduced), and 0.25 ms (highly reduced) send clocks.

9.5 PRONETA network scan

Run a full network scan in PRONETA. The coupler should appear with the assigned name and IP, no name conflicts, and a green "reachable" status. PRONETA also reports the firmware version and the MAC address, which are useful for matching the physical device to the project entry. The Topology view in PRONETA shows the LLDP neighbors reported by the coupler — both X1 P1 and X2 P1 — which is the fastest way to confirm the physical cabling matches the project.

10. Workarounds and Migration Paths

There are three field-proven workarounds for projects in which the original CPU/CP combination cannot be made to communicate with the PN/PN Coupler V2 in TIA Portal V12.

10.1 Replace the controller with a CPU 315-2 PN/DP

The integrated PROFINET interface of the CPU 315-2 PN/DP (6ES7315-2EH14-0AB0) is fully supported in TIA V12 with a clean AR to the coupler. No additional hardware is required. The SM 321 DI module is wired to the backplane bus of the CPU; the coupler is patched to the PN port. This is the configuration most commonly seen to work on the bench on the first try. Confirm the CPU firmware is V3.2 or later for full PROFINET conformance class C support.

10.2 Migrate to TIA Portal V13 SP1 or later

TIA V13 SP1 includes HSPs for the CP 343-1 Lean V2.6 and the CP 343-1 Advanced variants that were missing from V12. The migration is a project upgrade (Migrate project in the Project menu) and preserves the topology, the symbol table, and the program blocks. Plan a regression test on the program blocks after the upgrade, especially for SCL sources using 64-bit data types, indirect addressing, and any user-defined data types (UDTs) added in V12.

10.3 Firmware update on the coupler

Update the coupler firmware using the SIMATIC Automation Tool, PRONETA, or the TIA Portal online Update firmware function. The latest firmware at the time of writing is V2.2.x. After the update, the coupler is reset to factory defaults; re-assign the IP and device name. The firmware update is performed over Ethernet and does not require a memory card on the host CPU.

10.4 Decision matrix for the workarounds

11. Safety-Related Communication

The PN/PN coupler supports safety-related communication between two F-CPUs acting as IO controllers on either side, provided the coupler is configured as a safety-related gateway. The configuration is described in the SIMATIC Safety programming manual: Configure safety-related IO controller–IO controller communication. This is an advanced use case; the failure modes discussed in Sections 5 and 6 do not apply to F-configuration when the F-HSP is installed, but the firmware requirements of the coupler are stricter — V2.1 or later is required for F-CPU coupling.

For safety-related coupling, the GSDML is installed separately as part of the F-HSP, and the device view of the coupler in TIA Portal shows a "PROFIsafe" slot in addition to the standard PN slot. The slot configuration of the safety slot is fixed by the F-CPU firmware and cannot be edited by the user. The PROFIsafe address on the coupler must match the F-destination address configured in the safety program; a mismatch produces a PROFIsafe address error and the F-CPU goes to STOP with a safety diagnostics event.

12. Frequently Asked Questions