Troubleshooting ET200SP PNIO AR Code 15 on S7-1500F TIA Portal

Problem Summary

A SIMATIC S7-1516F-3 PN/DP controller is connected through PROFINET to an ET 200SP distributed I/O station built around an IM 155-6PN ST interface module that also carries F-I/O modules. After downloading the STEP 7 / TIA Portal hardware configuration, the IM 155-6PN enters a hard fault state: the SF (group error) and BF (bus fault) LEDs illuminate, the channel diagnostics on the inserted I/O modules flash, and the CPU's diagnostic buffer records the following entry:

IO device failure — PNIO configuration error (connection parameter) — internal AR code: 15

The PROFINET connection itself is physically intact. Both the S7-1516F-3 PN/DP and the IM 155-6PN respond to ping and appear in the "Accessible nodes" list with their configured IP addresses. The Application Relationship (AR) between the PROFINET IO controller and the PROFINET IO device is rejected during connection parameter negotiation, before any cyclic data exchange starts. This is a configuration-side failure, not a cable or layer-1 issue. The error text uses the word "connection", which frequently steers engineers toward network topology, but the actual root cause is in the device/station configuration record.

Affected Hardware and Required Firmware

Confirm the exact catalog numbers and firmware versions in the field before opening the project in TIA Portal. AR code 15 is version-sensitive, so use the SIMATIC Automation Tool, the device's web server, or the online & diagnostics view in TIA Portal to read the live firmware of every PROFINET device involved.

Root Cause Analysis: What AR Code 15 Actually Means

PROFINET uses the term "AR" (Application Relationship) for the cyclic data channel between an IO controller and an IO device. Before the controller can exchange process data, it must establish the AR by exchanging the expected configuration record (the AR Set with slot, subslot, module, sub-module, and expected identification data) with the device. The device then compares the offer against what it has physically plugged in and configured internally.

When the device's comparison fails, the controller receives an AR abort with a vendor-specific error code. On Siemens IM 155-6PN stations, the most common abort codes encountered in the field are:

AR code 15 covers any "configuration record error" detected at AR establishment. In practice on ET 200SP this almost always traces back to one of three root causes:

1. Wrong firmware in the offline project: the IM 155-6PN has, for example, firmware V4.5 installed, but the TIA Portal device configuration pins the IM to V4.2 because the engineer dragged an old HSP version into the project, or because the TIA Portal installation does not yet contain the newer HSP.
2. Wrong module order or empty slots in a station: the configuration includes a module ID that the actual IM does not support on the given firmware, or a slot is reserved without a corresponding module.
3. Mixed F- and standard I/O mis-wired in slot: an F-capable module (e.g., 6ES7136-6BA00-0CA0) is placed in a slot whose BaseUnit is not a Type F BaseUnit, so the module ID is correct but the channel does not start.

Preliminary Diagnostics Before Opening TIA Portal

1. Open the SIMATIC project and switch to Online > Accessible nodes. Verify that the S7-1516F-3 PN/DP and the IM 155-6PN both appear with their configured IP addresses.
2. Ping both devices from a workstation on the same subnet. PROFINET uses ICMP echo, so a successful ping pass means TCP/IP, ARP, and the switch path are working.
3. Open the IM 155-6PN web server by typing its IP into a browser (default port 80; user "admin", password configurable in TIA Portal under Properties > Web server > Security). Navigate to "Module information" and record the Article number (for example 6ES7155-6AU02-0BN0) and Firmware version (for example V4.5.0).
4. Use the "Online & Diagnostics" view in TIA Portal: select the IM, go to Online & Diagnostics > Module information > Firmware version. This is the authoritative view and is identical to the web server output.
5. Open "Topology view" in TIA Portal and switch to Online > Compare offline/online. Resolve every reported difference using the "Synchronize" action. Pay particular attention to neighbour port assignments and cable delay measurements; topology mismatches do not normally cause AR code 15 on their own, but they can mask the real cause by confusing the diagnostic buffer.

Detailed Diagnostic Buffer Interpretation

Read the detailed diagnostic buffer of both the CPU and the IM 155-6PN. The buffer text alone ("PNIO configuration error") is too generic to isolate the cause. Click on the entry to open the detail pane and copy the following fields:

Hex code 0x000F = decimal 15 = "Configuration record: module/subslot identification data rejected". Hex code 0x0018 = decimal 24 = "PROFIsafe parameter or address error". The two are easily confused; if the add-value pair matches the expected PROFIsafe address, then AR code 24 is the actual cause and the path below will not help.

Repairing the Station Configuration in TIA Portal

Update the device description in TIA Portal

1. In the TIA Portal device configuration of the IM 155-6PN, right-click the device and choose Change device.
2. Replace the IM 155-6PN with the correct article number and firmware from the hardware catalog. If the correct article number is not in the catalog, install the matching HSP from the Siemens Industry Online Support portal: search for "HSP 0330 ET200SP" or the specific article number, then run Options > Support Packages > Install Support Packages.
3. After the HSP installation, restart TIA Portal to refresh the hardware catalog.

Re-assign the PROFINET device name

1. Select the IM 155-6PN in the project tree, then Online > Assign PROFINET device name.
2. Choose the MAC address of the IM, the configured name (must match the device configuration 1:1, case-sensitive, no trailing spaces), and the configured IP address.
3. Click Assign name — the IM is identified by the PROFINET DCP protocol on the network and the name is written to non-volatile memory.
4. Repeat the assignment after a power cycle to confirm that the name persists. A PROFINET name that does not persist indicates a server module issue or a defective IM.

Re-compile and download the hardware configuration

1. Right-click the device or the entire S7-1516F-3 station and choose Compile > Hardware (rebuild complete).
2. Mark the CPU and choose Download to device > Hardware configuration.
3. Confirm the prompt "Stop CPU and download" — the AR is rebuilt during the download and the CPU is restarted with the new configuration.
4. Watch the IM 155-6PN: the SF LED should extinguish within 5–10 seconds of the AR re-establishment, and the BF LED should also extinguish once the cyclic frames are exchanged.

Verification Steps

1. Switch to Online > Accessible nodes and confirm the IM 155-6PN now shows a green status icon.
2. Open "Online & Diagnostics" of the IM — the "Status" tab should show "Module OK" and the SF and BF LEDs should be off.
3. Check the I/O modules' status LEDs: a solid green RUN LED per module means the module is exchanging cyclic data.
4. Read the diagnostic buffer of both the CPU and the IM. There should be no new "IO device failure" entry after the download. A clean buffer is the strongest evidence that AR code 15 is resolved.
5. Use a watch table in TIA Portal to read one input byte of the ET 200SP and toggle a corresponding input on the field wiring — the value should change online within one PROFINET update time.
6. For F-I/O: open the safety program in TIA Portal, go to Safety > Compile and check, then F-Runtime group > Passivate / Reintegrate the F-I/O. Reintegration must succeed with no PROFIsafe CRC error.

F-I/O Specific Considerations on the S7-1516F-3

The "F" suffix on the S7-1516F-3 PN/DP enables PROFIsafe over PROFINET for fail-safe I/O. The IM 155-6PN must be the F-capable variant (article 6ES7155-6BA00-0CN0 or newer) and the F-modules must sit on Type F BaseUnits (BU15-P16+A0+2B or BU20-P6+A0+2B-T with the -T suffix for the dark-coloured coding element on the backplane). Misplacing an F-module on a non-F BaseUnit can also raise AR code 15 on the failing slot, even though the controller still receives an "AR abort" for the entire station.

Use the Configuration Control with S7-1500 and ET 200SP application document if you intend to enable or disable I/O modules by the PLC program (option handling). Configuration Control adds an additional layer of AR parameter records and can surface as AR code 15 if the control record is not aligned with the slot list.

Troubleshooting Matrix

Preventive Measures and Best Practices

1. Centralise firmware management. Use the SIMATIC Automation Tool to read every device's firmware, compare it to the TIA project, and raise a deviation report. This is the single most effective countermeasure for AR code 15.
2. Use the latest HSP that matches the project version. When starting a new project, install the most recent HSP for the IM 155-6PN family before you instantiate the device. Older TIA installations default to older firmware entries, and the next engineer on the project may add a newer IM without updating the HSP.
3. Document PROFINET names and IPs in a separate file. A name with a typo (extra space, wrong case, leading/trailing space) is reported as a configuration record error by some IM revisions and is time-consuming to debug from the buffer alone.
4. Use PRONETA (free) for field commissioning. PRONETA's "Network analysis" and "IO test" features quickly identify name/IP duplicates, missing device names, and wrong module placements before the first CPU download.
5. Enable the "Report PROFINET IO device state" option in the S7-1500 CPU under Properties > PROFINET interface > Diagnostics addresses. This gives you a status bit in the process image that tells you when a device is in AR error state and can be linked to the HMI diagnostic screen.
6. Set the diagnostic interrupt OB82 and the device-fault OB83 in the S7 program. Without these OBs the CPU will simply enter the AR abort without a visible reaction; with them, you can log the exact slot, subslot, and event ID to a ring buffer on the CPU.
7. Keep the IM 155-6PN firmware and the TIA Portal HSP version aligned across the project life cycle. When you upgrade the IM firmware in the field, update the TIA project at the same time, otherwise the next project restore from the TIA backup will overwrite the IM's expectations and re-introduce AR code 15.

TIA Portal Configuration Reference for the S7-1516F-3 PN/DP

Per the official TIA Portal V17 documentation for the CPU 1516F-3 PN/DP, the configuration sequence is:

1. Create a new project in the TIA Portal portal view.
2. Add the F-CPU and select the matching article number (6ES7516-3FN02-0AB0 for the F variant).
3. Configure PROFINET interface X1: set IP address, subnet mask, and router (if used). The PROFINET device name on the X1 interface is what the IM will see in the AR offer.
4. Enable the F-capability under Properties > F-Configuration. This sets the PROFIsafe CRC length and enables the F-runtime group support.
5. Add the IM 155-6PN as IO device, configure the slot list, and download. The full procedure is documented in the SIMATIC S7-1500 / ET 200MP Manual Collection — Step 1 Configuring the CPU 1516F-3 PN/DP chapter.

PROFINET Update Time and Performance Considerations

AR code 15 is raised at connection establishment, but a related class of faults surfaces only after the station has been running for a while. Set the PROFINET update time explicitly in the device properties of the IM 155-6PN rather than leaving it on "automatic":

An update time that is too short relative to the number of modules or the switch latency will not cause AR code 15, but it will raise AR code 27 (PROFINET watchdog timeout). If the diagnostic buffer alternates between code 15 and code 27, set the update time to the next value in the table above and re-test.

Firmware Update Procedure for the IM 155-6PN in the Field

1. Download the firmware file (for example "IM1556PN_V45.zip") from the Siemens Industry Online Support portal entry for the IM article number.
2. Extract the file to a known location on the TIA Portal workstation.
3. In the TIA Portal project, open the IM 155-6PN device configuration and select Properties > General > Firmware update.
4. Browse to the extracted .upd file and confirm the target version.
5. Connect online, place the IM in STOP by switching the IM to "Update in RUN" mode only if your station supports it; otherwise plan a CPU stop.
6. Click Execute update. The IM reboots after the update. The PROFINET name and IP address are preserved.
7. After the reboot, re-read the firmware in the IM web server to confirm the new version.
8. Update the offline TIA project to the same firmware version, recompile, and download to the CPU so that the controller's AR offer matches the IM.

Frequently Asked Questions