Resolving Connection Point Not Supported Error KTP Mobile TIA V17

Problem Overview

A SIMATIC Connection Point (article number 6AV2 125-2AE13-0AX0) running firmware V5.2 is configured as the PROFINET access point for a KTP700 Mobile / KTP700F Mobile Panel. When the project is loaded into an S7-1517F-3PN controller under TIA Portal V17, the diagnostic buffer of the CPU reports "Connection point - not supported" (German equivalent: Anschaltpunkt wird nicht unterstützt). The wireless link between the Mobile Panel and the Connection Point comes up, standard HMI tags operate, but the safety-related emergency-stop circuit on the Mobile Panel does not engage the F-program in the CPU.

This failure mode is a classic PROFIsafe address-mismatch / PROFINET IO activation problem on the Wireless HMI subsystem. It is fully recoverable in the field and does not normally indicate a hardware fault on the Connection Point, the Mobile Panel, or the S7-1500F CPU. The resolution requires three coordinated actions: enabling PROFINET IO on the HMI station, restarting the Mobile Panel so it re-reads its PROFINET identity, and aligning the PROFIsafe F-destination address between the Connection Point and the TIA Portal device configuration.

Affected Components and Versions

Root Cause Analysis

The error string "Connection point - not supported" is produced by the PROFINET IO controller inside the S7-1500F when it cannot bind a configured AR (Application Relationship) to the physical device. The most frequent root causes in this topology are listed in order of probability:

1. PROFINET IO mode is disabled on the Mobile Panel / Connection Point station. The Connection Point can be operated in two roles: pure PROFINET access point for HMI traffic, or PROFINET IO device exposing the wireless safety slot. If the IO role is not activated, the controller never sees the slot, and the safety communication path stays down even though standard HMI pages still work over the same wireless link.
2. F-destination address mismatch. The PROFIsafe F-destination address on the Connection Point (assigned by the user at first commissioning) does not match the F-destination address configured under Devices & Networks > Properties > PROFIsafe for the F-CPU. The CPU logs a communication error (SF) on the F-module and refuses the safety frames.
3. Device description / HSP missing. A Connection Point on V5.2 firmware has new GSDML revision that may not be present in the TIA V17 base install. The catalog shows the device as a placeholder; the controller treats the slot as "not supported".
4. Topology or NTP interruption during semi-offline commissioning. When the project is loaded without the complete physical topology (e.g. ET200SP or Festo CPX missing from the rack), the diagnostic buffer fills with subordinate faults and the real connection-point error becomes hard to identify.

Reading the Diagnostic Buffer Correctly

Before any change is made, capture the CPU diagnostic buffer. This is the single source of truth and must be captured in English so the message IDs can be matched against the Siemens manual.

1. Open the project, select the S7-1517F-3 PN, right-click Online & Diagnostics > Diagnostics > Diagnostic Buffer.
2. Click Save as Text and store the file in UTF-8.
3. If the project language is French, change it first: Project > Languages > Editor language > English. Reload, then re-export.
4. Filter the buffer for entries whose Event ID is in the range 0x08E0 … 0x08FF (PROFINET IO connection events) and 0x0E0A … 0x0E15 (PROFIsafe events).

A clean buffer should contain exactly one PROFINET connection-establish entry for the Connection Point slot, followed by a PROFIsafe address-OK entry. Anything else (IO not accessible, station failure, AR-removed) is a symptom, not the root cause, and must be eliminated first.

Reducing Diagnostic Noise Before Re-Test

When the panel is loaded in a semi-offline environment (e.g. the ET200SP and the Festo CPX are physically missing), the diagnostic buffer can be flooded with IO-not-accessible events that push the real PROFIsafe error out of the historical log. Apply this five-step noise-reduction procedure before reloading:

1. Use File > Save As > Save as copy on the live project. Work on the copy.
2. Open Devices & Networks > Topology view and temporarily delete all port-to-port interconnections. Recompute and reload.
3. Either remove the NTP server configuration in the CPU properties, or stage a real NTP server on the same subnet (a router or a Windows time service) so the CPU does not log a clock-failure every cycle.
4. Ensure only one controller owns each HMI connection. If a secondary S7-1500 is in the project and also has a WinCC connection to the KTP700, the controller will log a connection-station-down entry on every cycle.
5. Create an OB82 (IO fault) and an OB83 (module plug/remove) in the S7-1500F program. Without these OBs the CPU goes to STOP on the first missing device, which prevents the safety program from reaching the F-runtime OB.

Resolution Procedure

Step 1 – Enable PROFINET IO on the Mobile Panel / Connection Point

1. In the TIA Portal project tree, select the Mobile Panel device (or the Connection Point device if the IO slot is owned by the CP).
2. Open Properties > PROFINET interface > Operating mode.
3. Tick the option "Operate as PROFINET IO device" (or Activate PROFINET IO mode, depending on the GSDML revision).
4. Confirm that the slot assigned to the safety sub-module is selected (typically slot 1 sub-slot 1 for the F-source address of the Mobile Panel).
5. Recompile the project. The CPU device configuration must show the Connection Point as a partner on PROFINET IO, not only as an HMI station.

Step 2 – Restart the KTP700 Mobile

Once the PROFINET IO role is enabled and downloaded, the Mobile Panel must perform a clean re-init so it re-reads its station name, IP address, and PROFINET identity. Power-cycle the panel from the Connection Point:

1. Hold the operator panel power key for three seconds until the display goes dark.
2. Wait ten seconds.
3. Re-insert the panel into the Connection Point cradle. The panel pulls a fresh identity from the CP and starts a PROFINET AR with the F-CPU.

A soft restart via the Control Panel Reboot command is not sufficient when the F-source address has changed; a hard power-cycle is required.

Step 3 – Align the PROFIsafe F-Destination Address

The F-destination address is a 1-based integer in the range 1…65534 and is stored both in the project and in the Connection Point. Both values must match exactly, otherwise the F-CPU discards the safety telegram.

1. In the project, navigate to the F-CPU's PROFINET IO submodule representing the Mobile Panel. Open Properties > PROFIsafe.
2. Read the F-destination address field. Note the value (e.g. 3).
3. On the Connection Point's web-based management (WBM) or via the KTP Control Panel, navigate to Safety > PROFIsafe > F-destination address.
4. Set the same value (e.g. 3) and apply. The CP prompts for confirmation to overwrite the current address; confirm.
5. Power-cycle the Mobile Panel once more so the new F-address is loaded into the F-CPU AR.

The address assignment follows the rule: one unique F-destination address per PROFIsafe slot on a single PROFINET network segment. The F-source address is the device's own, while the F-destination address is the controller-side logical identifier of the slave.

Step 4 – Re-Download and Verify the F-Program

1. Compile the safety program (F-blocks). TIA Portal performs a signature check on every F-block.
2. Download the F-program to the S7-1517F-3 PN with the standard F-download procedure (password-protected).
3. Check the CPU operator panel: SF / BF / MAINT LEDs must be off.
4. Inspect the diagnostic buffer: only the F-address-OK entry should remain as the latest PROFIsafe event.

Safety Function Verification

The emergency-stop circuit on the KTP700F Mobile is wired to the F-inputs of the F-CPU through PROFIsafe. After the resolution steps the path is live, but the safety function must be formally proven before the machine is released for production.

1. Open TIA Portal Online & Diagnostics > Safety > Status for the F-module. The status must read RUN with no passivation indicator.
2. Press the physical E-Stop on the Mobile Panel. The status should toggle to passivated within one PROFIsafe watchdog cycle (default 50 ms × monitoring number 3 = 150 ms max).
3. Release the E-Stop with the standard acknowledge sequence. The slot should return to RUN only after the F-runtime OB in the CPU confirms the safe state.
4. Document the test result with the operator-panel screenshot and the diagnostic-buffer export. This is mandatory for the CE technical file and for the safety acceptance test record.

Pre-Commissioning Checklist

Parameter Reference

Common Variations and Edge Cases

Two Mobile Panels on one Connection Point. The CP can host two Mobile Panels (primary + secondary). When only one is online, the second slot raises a station-failure event that may obscure the connection-point error. Disable the secondary slot in the project during commissioning, then re-enable for production.

Mixing generations. Connecting a first-generation Mobile Panel (6AV2 125-1Ax) to a V5.2 Connection Point is supported, but the F-source address negotiation behaves differently. Always check the WBM after a panel swap.

Cross-project copy. If the F-destination address is copied from a reference project, TIA Portal may silently remap the address if the slot number changes. Re-validate the address table after every "Copy & Paste" between controllers.

Firmware downgrade. A downgraded CP firmware (e.g. V4.x to V5.2) retains the previously assigned F-destination address. If the previous project was on a different slot numbering, the new project will show a mismatch.

FAQ