Troubleshooting PN/PN Coupler Slot 6 Net Configuration Error in Separate TIA Portal Projects

The Siemens PN/PN Coupler is a gateway device that links two physically independent PROFINET networks while logically separating them. It is commonly used when two controllers, two engineering teams, or two plant areas must exchange a bounded, deterministic dataset without sharing a common PROFINET domain. When the two controllers are configured in separate TIA Portal projects, the only contract between the two sides is a GSDML file exported from the producer's PROFINET network and imported into the consumer's project. A frequent failure mode in this scenario is the diagnostic message "Net configuration error - Difference between nets at slot 6" raised by the coupler or by the IO Controller. This reference documents the root cause, the diagnostic workflow, and the verified resolution for that error.

1. Problem Description

The observed symptom set is consistent across multiple field reports:

• Two PROFINET IO Controllers connected to the X1 and X2 ports of a single PN/PN Coupler.
• Each controller is engineered in a separate TIA Portal project. The X2 side (the project that "consumes" the data) is built from a GSDML of the X1 side exported by the other engineer.
• When going online, the device diagnostics show Net configuration error - Difference between nets at slot 6, raised on both the IO Controller and the PN/PN Coupler.
• Removing slot 6 from the transfer mapping clears the error but eliminates the data exchange for that slot.
• Re-importing a different GSDML breaks the coupler connection entirely.

The error message points specifically at slot 6 of the coupler's internal transfer mapping, which is the table that defines which PROFINET slots of the X1 network are exposed to the X2 network as IO data.

2. PN/PN Coupler Architecture Recap

The PN/PN Coupler (catalog number 6ES7158-3AD10-0XA0 for the current hardware revision) is a two-port PROFINET device that operates as an IO Device on both networks simultaneously. Each port is configured independently:

Each transfer slot in the mapping is a logical PROFINET slot exposed by the coupler on the opposite port. Slot 0 is reserved for the coupler's own diagnostics/identification record. The transfer mapping table (configured under Device view > PN/PN Coupler > Transfer mapping) defines for each slot the length and direction of the IO payload.

3. Root Cause: Slot-Level Configuration Mismatch

The diagnostic text "Difference between nets at slot 6" means that the IO Controller on at least one side is reporting that the IO data the coupler advertises for slot 6 does not match the IO data the IO Controller expects for slot 6. The mismatch can be in:

1. Input/output length: The number of input bytes or output bytes configured for slot 6 in the transfer mapping differs from what the imported GSDML describes.
2. Data status bit presence: The "Data status" checkbox appends one status bit to the input payload of the slot. If the GSDML is exported with Data status enabled and the consumer's project builds its slot table without it (or vice versa), every byte from the status bit onward is shifted by 1 bit/byte, cascading into a length mismatch at slot 6.
3. Slot offset overlap: If slot N's configured length pushes the next slot's start address into slot N+1's reserved area, the PROFINET stack interprets the second slot as misaligned and reports it as a configuration difference.
4. Stale or partial GSDML: The producer changed the transfer mapping after the GSDML was exported, but the consumer's project still imports the older GSDML. The slot table embedded in the GSDML no longer matches the live configuration of the coupler.

Slot 6 in particular tends to be the first failure point because it is far enough into the mapping that the user has typically configured several preceding slots by hand, and any small drift in slot length accumulates by the time slot 6 is evaluated.

4. Diagnostic Workflow

Execute the following checks in order. Each step produces a binary pass/fail result; do not proceed until the current step passes.

4.1 Capture both online diagnostics

1. Open the producer's TIA Portal project, connect online to the controller, and read the diagnostics buffer of the PN/PN Coupler device. Record the slot index, channel, and the specific error code.
2. Open the consumer's TIA Portal project, connect online, and repeat the diagnostics read on the same physical device from the opposite network port.
3. Confirm that both sides report the same slot number. If they do not, the consumer's GSDML is for a different revision of the transfer mapping; re-export it.

4.2 Compare transfer mapping to GSDML

1. In the producer project, open Device view > PN/PN Coupler > Transfer mapping. Screenshot every slot (1-16) with the input length, output length, and Data status column visible.
2. In the consumer project, open the GSDML device's slot configuration. Compare slot-by-slot. The input length of slot 6 in the consumer's slot view must match the producer's transfer mapping exactly, and the output length must match exactly.
3. If the consumer's GSDML device shows a different length for any slot, that is the failure source even if the diagnostic text only highlights slot 6.

4.3 Verify Data status state

1. In the producer's project, inspect every transfer mapping slot. Note which slots have Data status enabled.
2. If any slot has Data status enabled, the producer's GSDML export will encode a 1-bit/1-byte status word for that slot. The consumer's GSDML device, when placed into the slot table, must accommodate that extra byte.
3. The safest engineering choice for multi-project configurations is to disable Data status on all transfer mapping slots unless the consumer's controller requires it. See PN/PN Coupler Hardware Manual for the exact slot representation.

4.4 Check byte address contiguity

1. Confirm that input byte addresses are sequential with no gaps and no overlaps across slots 1 through N.
2. Confirm that output byte addresses are sequential with no gaps and no overlaps across slots 1 through N.
3. If the producer hand-typed addresses (e.g., slot 1 = IB4000..IB4011, slot 6 = IB4000..IB4011), the slots will collide. Re-address so that slot 6 starts immediately after slot 5 ends.

5. Resolution Procedure

The verified resolution for the field case in this article is to make the configuration of slot 6 identical in byte geometry to the configuration of slot 1 (or to whichever slot is the first in the table that the coupler accepts). The exact procedure is:

1. In the producer's TIA Portal project, open Device view > PN/PN Coupler > Transfer mapping.
2. Select slot 6. Re-enter the input length and output length to match slot 1 exactly. In the original case, slot 1 was 12 bytes input / 6 bytes output (or vice versa - inspect the slot 1 column to determine which direction is which); slot 6 must use the same pair of lengths.
3. Do not modify slot 1.
4. Compile the hardware (Hardware > Compile).
5. Re-export the GSDML of the X1 PROFINET network (Devices & Networks > right-click the PN/PN Coupler > Export GSDML).
6. Send the new GSDML to the consumer engineer.
7. In the consumer's TIA Portal project, remove the previous GSDML device instance, import the new GSDML, drag a fresh instance into the PROFINET topology, and assign it to the IO Controller.
8. Compile and download the consumer project.
9. Go online and verify that the diagnostic text disappears.

6. Verification

After applying the fix, confirm the following:

1. Online diagnostics for the PN/PN Coupler no longer contain "Net configuration error - Difference between nets".
2. The IO Controller's device view shows the PN/PN Coupler with a green status indicator and no maintenance events.
3. Forcing a slot 6 value in the producer project is visible in the consumer's process image within one PROFINET update cycle.
4. The PN/PN Coupler's web server (if accessible) reports Configuration: OK on both X1 and X2 ports.
5. Disconnecting the producer controller triggers the Data status bit (if enabled) to "invalid" on the consumer side, confirming end-to-end propagation.

7. Multi-Project Configuration Best Practices

Multi-project PN/PN coupling is a common source of support calls because the contract between the two projects is implicit (the GSDML file) rather than enforced by a shared project. The following practices reduce the probability of the slot 6 class of error.

8. GSDML Export and Import Procedure

The following sequence produces a clean GSDML exchange between two TIA Portal projects.

8.1 Producer: Export GSDML

1. Open the TIA Portal project that contains the PN/PN Coupler.
2. Navigate to Devices & Networks.
3. Right-click the PN/PN Coupler in the network view or device view.
4. Choose Export GSDML.
5. Select a versioned filename, for example PNPN_X1_v17.gsdml.
6. Commit the file to the shared version-control repository.

8.2 Consumer: Import and Place GSDML

1. Open the consumer's TIA Portal project.
2. Options > Manage general station description files (GSD) > Source path > select the GSDML directory.
3. Confirm that the new GSDML appears in the device catalog under the correct vendor folder.
4. Drag the device from the catalog into the network view.
5. Connect it to the IO Controller's PROFINET port.
6. Assign the device name and download the device name assignment.
7. Open Device view and inspect every slot. Verify the input/output lengths match the producer's transfer mapping.
8. Compile and download the consumer project.

9. Transfer Mapping Example

The following table illustrates a clean, non-overlapping mapping for a four-slot exchange. Use this as a template and replace the byte counts with application values.

Notice that slot 6 in this template has the same byte geometry as slot 1. This is the pattern that resolved the field case documented in this article.

10. Common Adjacent Errors

11. Frequently Asked Questions