Resolving KTP600 HMI Not Detected as Accessible Device on S7-1200

Problem Statement

A Siemens SIMATIC KTP600 Basic mono PN panel, networked to a SIMATIC S7-1215 DC/DC/DC CPU on PROFINET port 2, fails to appear in the Accessible devices view of TIA Portal. The programming device (PG/PC) is connected to the same network, the CPU (192.168.0.1) responds, but the HMI (192.168.0.2) cannot be reached. The panel attempts to start a host connection at boot and, if cancelled, the Control Panel is reachable but menu items cannot be opened. This is one of the most common commissioning issues when integrating Comfort/Basic panels with S7-1200 controllers in TIA Portal V15 through V20.

Affected Hardware and Firmware

Root Cause Analysis

When the HMI does not appear in Accessible devices on TIA Portal, the failure path runs from the physical cable up through the IP and PROFINET name stack. The likely causes, in order of probability based on field data, are:

1. Defective or unterminated PROFINET cable between the CPU Port 2 and the HMI. This is the dominant cause. The HMI powers up, attempts DCP (Discovery and Configuration Protocol) identification, sees no link partner on its RJ45, and silently fails.
2. Wrong PG/PC interface selected in TIA Portal (a Wi-Fi adapter or VPN tunnel is selected instead of the wired Ethernet connected to the CPU).
3. IP address mismatch between the TIA project and the actual HMI runtime configuration. The HMI Control Panel shows the effective address; the project shows the configured one.
4. PROFINET device name not assigned. The CPU can only route to a device that has a valid PROFINET name matching the configured HMI in the project.
5. Subnet mask mismatch (e.g., project says /24 but the HMI was previously commissioned on /16).
6. Windows firewall blocking UDP port 34964 (PNIO DCP) and TCP port 102 (S7 communication).
7. Out-of-order download: The HMI configuration was downloaded but the HMI was reset to factory defaults, removing the project IP.

Step 1 - Verify the Physical Layer First

Before any TIA Portal interaction, confirm the link status on every RJ45 socket in the path: PG/PC, CPU Port 1, CPU Port 2, and the HMI.

1. Inspect the link LED on the HMI RJ45. On the KTP600 Basic mono PN, the green Link LED must be solid when a 100 Mbit partner is connected. A dark LED means no Physical Layer signal - the cable is the prime suspect.
2. Inspect the Link LEDs on CPU X1 P1 and X1 P2. The S7-1215 has two PROFINET ports that act as an internal switch. The LED next to each port lights green when a link is established.
3. Swap the suspect patch cable with a known-good Cat 5e or Cat 6 PROFINET cable (max 100 m per segment, per PROFINET cabling guidelines).
4. Try a different port on the CPU. Port 1 (X1 P1) is the upper network; Port 2 (X1 P2) is the lower network. Either port can host the HMI, but the configuration in TIA must reference the same port the cable is plugged into.
5. Verify the cable pinning. PROFINET uses standard 8P8C (RJ45) T-568B for both ends. Crossover is not required on modern S7-1200 ports (they are Auto-MDI/MDIX).

Step 2 - Confirm the HMI's Live IP Address

Even when the project lists 192.168.0.2 for the HMI, the runtime device may have a different address (e.g., from a previous project). Use the HMI's own operating system to verify.

1. Power-cycle the HMI.
2. During the boot sequence, if the HMI prompts Connect to host?, tap Cancel (the Cancel button is on the touch screen, not the Control Panel menu).
3. When the Control Panel appears, the right-hand "Open" icon launches the loader menu. The Control Panel on WinCC RT Advanced is reached via the loader, not via a Windows-style Start menu on Basic panels.
4. Open Network and Dial-up Connections > PN/IE (or PROFINET on newer images). The currently effective IP address, subnet mask, and PROFINET device name are displayed.
5. Compare these three values against the values in the TIA Portal project (Project tree > Devices & Networks > select HMI > Properties > PROFINET interface > Ethernet addresses).

If the values disagree, the panel is not in the state the project assumes. Reset the HMI to factory defaults from the Control Panel and re-download the project, or manually correct the IP and PROFINET name on the panel and re-download.

Step 3 - Validate the TIA Portal Project Configuration

Open the project and verify each of the following parameters. Mismatches here are the second most common cause.

Confirm the subnet is the same on both nodes. The S7-1200 CPU does not perform routing between its two ports; it acts as a 2-port switch. A device on Port 1 cannot be reached from a device on Port 2 if the IP subnets differ unless the PG is on the same subnet as the HMI.

Step 4 - Use "Find Accessible Nodes" the Correct Way

Per the official Siemens TIA Portal documentation on displaying accessible devices, the procedure is:

1. Switch the TIA Portal project tree to the Project view (not Portal view).
2. Expand Online access in the project tree.
3. Locate the Ethernet adapter that is physically connected to the CPU (not the Wi-Fi adapter, not the VPN tunnel, not a Hyper-V virtual switch). Right-click it.
4. Select Update accessible devices (or Find accessible nodes in older builds).
5. TIA Portal sends a DCP multicast (UDP 34964) on the selected adapter and lists every PROFINET device that responds. The CPU will appear as PN/IE_1 and the HMI as its PROFINET name.

If the CPU appears but the HMI does not, the problem is on the segment between the CPU and the HMI (cable, port, or the HMI's own configuration). If neither appears, the PG/PC adapter is wrong or no link exists between the PG and the CPU.

Step 5 - Assign the PROFINET Device Name

A PROFINET IO device has no usable network identity until it is assigned a PROFINET device name via DCP. The HMI may be physically present on the wire (link LED on) but invisible to "Find accessible nodes" if it has never been named, or if it was named for a different controller.

1. In the project tree, right-click the HMI device > PROFINET device name > Assign PROFINET device name.
2. In the dialog, the accessible devices list shows all unnamed DCP devices on the wire. Select the entry whose MAC address matches the HMI's MAC (printed on the rear label of the KTP600).
3. Confirm the PROFINET name from the project is written to the device. The HMI will restart its PROFINET stack and, if the configuration matches, come online green.

Verify the assignment with Update accessible devices again. The HMI should now appear with its project name.

Step 6 - PG/PC Interface Assignment

Wrong PG/PC interface assignment is a top-three cause of "device not found."

1. Open the Windows Control Panel > Set PG/PC Interface (the 32-bit applet, not the modern Settings app).
2. Under Access point of the application, select S7ONLINE (STEP 7).
3. Set the Interface parameter assignment used to the wired Ethernet adapter that connects to the S7-1200. For TCP/IP direct, choose TCP/IP > Network card > [your NIC].
4. Click OK. Restart TIA Portal if the change was made while it was running.

Step 7 - Subnet and Routing Considerations

The S7-1200 CPU (firmware V4.x) does not route IP traffic between its two PROFINET ports. It is a Layer-2 switch, not a router. Therefore:

• All devices on CPU Port 1 and CPU Port 2 must be in the same IP subnet, OR the PG must be physically on the same subnet as the device it is trying to reach.
• If the PG is on 192.168.0.x and the HMI is on 192.168.1.x, the HMI will not respond to ARPs sent from the PG - even though the cable is good.

Recommended subnet for a small HMI/PLC cell:

Verification Procedure

Run the following checks in order. Stop at the first check that fails.

1. Link LEDs green on PG, CPU P1, CPU P2 (if used), and the HMI.
2. ICMP ping from the PG: ping 192.168.0.1 (CPU) and ping 192.168.0.2 (HMI). If ping fails, the IP stack is not reachable - check firewall, subnet, and cable again.
3. ARP cache contains the MAC of the HMI: arp -a | findstr 192.168.0.2 in cmd.exe.
4. In TIA Portal, Online > Accessible devices on the correct NIC shows both the CPU and the HMI with their PROFINET names.
5. Right-click the CPU > Go online; TIA Portal reports an online connection to the PLC.
6. Right-click the HMI > Go online; the HMI loader must respond with firmware, project name, and runtime version.
7. From the online HMI, open Diagnostics > Connection and confirm the HMI_Connection_1 status is Established.
8. Download the HMI project again: right-click HMI > Download to device > Software (all) to force a clean transfer of the configuration, including PROFINET name, IP, and connection tables.

Preventive Measures and Field-Proven Caveats

• Use PROFINET-certified patch cables (green RJ45, Siemens 6XV1870-3-series or equivalent) for any cable that lives in a cabinet or is subject to flexing. Standard Cat 5e is electrically fine for 100 Mbit but may fail in industrial environments.
• Disable Windows Firewall on the PG during commissioning, or explicitly allow UDP 34964, UDP 49152-65535, and TCP 102 inbound on the wired adapter.
• Always use a managed switch (e.g., SCALANCE XC-100) when the cell grows beyond 3-4 PROFINET devices. The CPU's 2-port switch is intended for small topologies only.
• Document the PROFINET name and IP of every HMI in a commissioning sheet. A factory reset of the panel erases both and silently breaks the connection.
• Reserve IP addresses outside the DHCP range of any management switch to prevent the DHCP server from handing out the CPU or HMI's IP to a stray laptop.
• Keep the KTP600 firmware aligned with the TIA Portal version used to compile the project. A panel with V13 firmware cannot load a project compiled with TIA V17 without an OS update, and the loader will hang on the connection dialog.

Troubleshooting Matrix

Related Diagnostics Functions in TIA Portal

Beyond Update accessible devices, TIA Portal V17-V20 offers a number of integrated diagnostics tools that surface the same problem from a different angle:

• Online & Diagnostics on the CPU > PROFINET diagnostics lists all PROFINET stations it sees on each of its ports, with link status, speed, and duplex.
• Online & Diagnostics on the HMI (once reachable) > PROFINET diagnostics shows the HMI's view of the connection, including the partner's IP and MAC.
• Trace function for capturing DCP frames in real time on a SCALANCE switch with port mirroring enabled.