IMDTouchKnowledge BaseShop main store

Troubleshooting

Fix WinCC Professional runtime not connecting to the S7-1500

HMI and touchscreens Published 6 min read

Short answer

WinCC Professional Runtime can start, load screens and raise no error while the HMI connection leaves through the wrong PC network adapter, because the access point selects the interface automatically. Disable that automatic option, assign the access point to the PLC-facing adapter in Set PG/PC interface, re-download the runtime and restart.

On this page
  1. Why Runtime starts cleanly with no live values
  2. The two places an access point is chosen
  3. Checks that isolate the wrong binding
  4. Example: subnet arithmetic that proves the binding
  5. Fix: disable the automatic selection and pin the adapter
  6. Accept the fix and decide what you have
  7. Questions asked

WinCC Professional Runtime starts, loads its screens and raises no error because screen execution and PLC communication are separate functions: the application executes locally while the connection subsystem reaches the controller through whichever PC adapter the access point resolves to. When the HMI connection's access point is set to choose the interface automatically, it rebinds to an adapter that is not on the PLC network, and the tags stay dead with nothing on screen to say why. Disable the automatic selection in the HMI connection's access-point parameter and assign that access point to the PLC-facing adapter in Set PG/PC interface, then re-download the runtime project and restart. A configured PC station, a shared subnet and a running S7-1500 do not prevent this fault: the controller address stays valid while the path to it is wrong.

Why Runtime starts cleanly with no live values #

A supervisory application can open successfully while its process values are unavailable. The runtime loads the application from local disk; the communication subsystem separately establishes the configured connection to the controller. Those two functions fail independently, which is why screens full of frozen or empty values are a communication symptom, not an application bug.

In a WinCC Professional V17 installation with an S7-1500, the project was exported with download to file system and opened by starting Runtime, the PLC was running, the PC and the PLC shared an IP subnet, and the PC station configuration was complete. All of that was true, and none of it repaired the communication path, because the PC interface the runtime used kept being reassigned. A completed download and a running Runtime prove the application side only.

The two places an access point is chosen #

An access point is a named communication entry that the software resolves to a network interface; the adapter is the physical or virtual interface that carries the frames. Two settings decide which adapter your tags use, and both must agree:

  • In the project: the TIA Portal connections editor, HMI Connection, then Parameters -> Access Point (the same field appears under Properties > General > Access point). This names the access point the runtime will call. A V18 discussion of this setting describes choosing the correct network driver there and warns about confusing the s7 online access point with CP-TCPiP. Write down the name your project uses.
  • On the runtime PC: Start > Control Panel > Set PG/PC interface, opened on the computer that actually runs the application, not the engineering workstation. This tool maps the access point name to one specific adapter.

The fault sits between the two. The access-point setting offers an option to set it automatically, and that option rewrites the interface assignment, in the case here to the adapter with no link to the PLC. The addresses stay correct; the binding does not. A PC carrying wired, wireless and virtual adapters gives the automatic selection several wrong candidates.

Checks that isolate the wrong binding #

Work through these on the runtime PC, in this order, before changing the project:

  • Confirm what you are testing: the application is a WinCC Professional runtime, running on this PC.
  • Open the connections editor, select the HMI Connection, read Parameters -> Access Point, and record the access point name and whether the automatic option is active.
  • Open Start > Control Panel > Set PG/PC interface and note which adapter that access point is assigned to right now.
  • Identify the adapter cabled to the PLC network by its address, its link state and the physical connection.
  • Read every adapter's address and subnet mask and compare them with the PLC's using the arithmetic below.
  • Ping the PLC and interpret the result correctly: ping follows the Windows routing table and leaves by whichever adapter owns the route, so a reply proves the network is healthy, not that the runtime uses that adapter.
  • Confirm the SIMATIC NET communication components that install with WinCC Professional are present on this PC; they are what make the runtime-to-PLC connection possible.

Example: subnet arithmetic that proves the binding #

The addresses here are an illustrative example; your numbers differ, the method does not.

Let the S7-1500 PROFINET interface be 192.168.0.20 with mask 255.255.255.0, the PC's wired adapter on the PLC network be 192.168.0.10 with the same mask, and the PC's second adapter be 192.168.1.50, also masked 255.255.255.0.

  • 192.168.0.10 AND 255.255.255.0 = 192.168.0.0
  • 192.168.0.20 AND 255.255.255.0 = 192.168.0.0

Both hosts sit on network 192.168.0.0 with distinct host parts 10 and 20, so the wired adapter delivers straight to the controller.

  • 192.168.1.50 AND 255.255.255.0 = 192.168.1.0

The second adapter lives on 192.168.1.0, a different network. Bound there, the runtime asks that segment for 192.168.0.20, nothing answers, and the attempt times out in silence, which is precisely the no-error symptom. Meanwhile ping still succeeds from the PC, because Windows sends it through the wired adapter holding the 192.168.0.0 route.

Fix: disable the automatic selection and pin the adapter #

  1. Record the current state: the access point named in the HMI connection, the adapter assigned to it in Set PG/PC interface, and the addresses of both adapters.
  2. In the TIA Portal connections editor, open the HMI Connection, Parameters -> Access Point, select the explicit access point, and switch off the automatic selection that was rewriting the interface.
  3. On the runtime PC, open Start > Control Panel > Set PG/PC interface and assign that same access point to the adapter that shares the PLC's subnet, the wired adapter in the example.
  4. Close the tool and reopen it. If the assignment changed back, an automatic option is still active somewhere; find it before going on.
  5. Compile and repeat the runtime download by the same download-to-file-system route, then restart Runtime so the changed connection parameters load.
  6. Leave the controller program alone. This is a PC-side assignment, and downloading the PLC interrupts the machine while changing nothing on this path.

Accept the fix and decide what you have #

  • Runtime opens, values follow the process, connection diagnostics show the link established: fixed. Re-check the assignment once after the next PC reboot; an assignment that reverts means the automatic option was not fully disabled.
  • Values arrive, then the connection drops and recovers on its own: a different fault, covered in the WinCC Professional intermittent PLC connection loss diagnosis article.
  • The download itself fails before Runtime ever starts: also different; read why an HMI transfer fails in initial start mode despite ping.
  • Screens showing numbers that never move prove nothing, because a screen can hold retained or last-known values. Toggle a spare input at the process and watch it move in Runtime; that change plus an established connection status is the acceptance test.

Questions asked

Why does ping reach the S7-1500 while Runtime shows no values?

Windows ping follows the routing table and leaves through whichever adapter owns the route to the PLC subnet. WinCC Professional leaves through the interface assigned to the access point. When automatic selection binds that access point to the second adapter, the network is healthy and the runtime path is still wrong, which is why nothing reports an error.

Where exactly is the automatic access-point option?

Open the HMI connection in the TIA Portal connections editor and read the Access Point parameter; the automatic option belongs to that setting. The interface assignment it controls is visible in Set PG/PC interface on the runtime PC. Check both places after every change, because the automatic option can rewrite the assignment when settings are applied.

Do I need to download the PLC program again?

No. The fault is a PC-side interface assignment; the S7-1500 program, its address and its subnet are untouched. Repeat only the runtime download so the changed connection parameters reach the PC, then restart Runtime. A controller download interrupts the machine and fixes nothing on this path.

Can a screen still show numbers while the connection is down?

Yes. A runtime screen can display retained or last-known values, so a static number is not evidence of communication. Accept the repair only when a value you can change at the process moves on screen and the connection status reads established.

Keep reading

  • Troubleshooting

    WinCC flexible Runtime shows ### on a copied target PC

    ### on a copied target PC means Runtime's S7 connection never opened; a passing ping proves IP reachability only. Open Set PG/PC Interface on the target PC, select the S7ONLINE (STEP 7) access point and bind it to the adapter wired to the S7-300. If the adapter list is empty, reinstall WinCC flexible Runtime from licensed media.

    HMI and touchscreens

  • Troubleshooting

    Why rebuilt HMI runtime files show #### for PLC tags

    Hashes on every tag after transferring a rebuilt WinCC Runtime Advanced project are a display symptom, not a communication code. Restore the working runtime files as a baseline, add an alarm view showing buffered System alarms, and branch on the message text: connection establishment, TLS certificates and clocks, hidden project pairing, or single-field formatting.

    HMI and touchscreens

  • How-to

    Connecting an HMI Panel to an S7-1500 PLC

    Confirm the HMI's documented driver covers the S7-1500 for your exact panel model and software revision, put the panel and CPU on the same subnet, permit the connection in the CPU protection settings, then validate one known PLC tag before building screens. A working Ethernet link alone proves nothing about tag access.

    HMI and touchscreens