Troubleshooting
WinCC flexible Runtime shows ### on a copied target PC
Short answer
### 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.
On this page
A copied WinCC flexible 2008 SP3 runtime project shows ### in every I/O field on the target PC — a PC running the project through the runtime loader, not a panel — even though that PC can ping the S7-300. The ### signs mean the tags have no valid value: Runtime's S7 connection never opened on that machine. A ping proves IP reachability only; Runtime opens its tag session through the PG/PC interface layer, and that binding is a per-PC Windows setting which does not travel with the project. The fix is to open Set PG/PC Interface on the target PC, select the S7ONLINE (STEP 7) access point and bind it to the network adapter wired to the S7-300. If the adapter list is empty, the S7 communication components are missing and Runtime must be reinstalled from licensed media.
Why ### appears while ping works #
WinCC flexible Runtime does not open a raw socket to the CPU on its own. It calls the S7 communication layer through an access point, by default S7ONLINE, and Set PG/PC Interface binds that access point to one physical interface, typically a TCP/IP entry for a network adapter. If the access point is unbound, bound to the wrong adapter, or the adapter entry is missing, the connection never establishes. Every tag riding on it reports bad quality, and each I/O field renders ###.
That is why the development PC worked and the target PC did not: copying the project moves the connection definition, not the PC's binding. It is also why changing the IP address and plugging the cable straight into the CPU changed nothing.
Two symptoms look alike and have different causes. ### on a copied target PC means a dead S7 link on that machine; #### that turns up after a project rebuild points at stale runtime files instead. If your screen shows #### rather than ###, start with why rebuilt HMI runtime files show #### for PLC tags.
Ping the PLC before touching the interface #
The binding checks below mean nothing until a ping passes, so settle the IP layer first.
Read the target PC adapter's address and subnet mask and compare them with the CPU's. Take this illustrative setup: target PC at 192.168.0.10 with mask 255.255.255.0, S7-300 CPU at 192.168.0.2 with the same mask. The network part of each address is the address ANDed with the mask:
- 192.168.0.10 AND 255.255.255.0 = 192.168.0.0
- 192.168.0.2 AND 255.255.255.0 = 192.168.0.0
Both compute to 192.168.0.0, so PC and CPU share a subnet and a direct cable works without a gateway. If the CPU were at 192.168.10.2 instead, its masked network part would be 192.168.10.0, which does not match 192.168.0.0, and ping would fail until one of the two addresses changes — keeping the host part unique on the network.
Ping the CPU's address. Replies mean the network layer is done and the fault sits in the access point binding: go to the next section. No replies mean repair the cabling, address or subnet first.
A passing ping is also where multi-NIC PCs mislead. Note which adapter actually carries the cable to the CPU; that one — not the Wi-Fi card, not the plant-network port — is the one the binding must name. And remember that reachability is not a working application link; the same trap fills why an HMI transfer fails in initial start mode despite ping.
Bind the access point in Set PG/PC Interface #
Open the Windows Control Panel on the target PC and start Set PG/PC Interface.
In the first tab, set the application access point to S7ONLINE (STEP 7). That is the default name; if the project was built with a modified access point name, enter the name the project uses.
Below it, in the interface parameter assignment list, pick the entry that pairs TCP/IP with the adapter wired to the PLC. On a dual-NIC PC, picking the plant-network port while the CPU hangs off the second port is the classic wrong choice.
Decision: adapter entry present and selected — start Runtime and continue with the verification section. List shows no network cards at all — go to the next section.
When the adapter list is empty #
An empty interface list means the S7 communication components are missing from that PC; Windows does not fill the list in on its own. The supported repair is to reinstall WinCC flexible Runtime from the original licensed installation media, which restores the interface entries:
- Uninstall WinCC flexible Runtime from the Windows installed-programs list.
- Restart the PC.
- Install Runtime again from the licensed media of the same version and service pack as the project — 2008 SP3 here.
- Restart once more and repeat the binding selection.
The same reinstall repairs an access point name that was corrupted and can no longer be set.
Check the connection definition in the project #
If the binding is set and ### persists, review the copied connection definition itself:
- Interface type is Ethernet, using the S7-300/400 channel driver supplied together with WinCC flexible.
- Station address equals the CPU's current IP address. If you changed the CPU address on the bench, change it here too and retransfer the project.
- Rack and slot match the CPU position shown in the project's hardware configuration.
- The connection is set online.
- The four tags address data blocks that exist in the CPU and are long enough, and the CPU's protection settings do not block access to them.
Verify the fix #
Restart Runtime with the machine stopped or supervised, because the PLC link drops while Runtime closes. Then step through these expectations:
- Start Runtime on the target PC. Expected: the ### fields show live scrap-counter values within a few seconds.
- Change the counter value in the PLC. Expected: the screen follows on the next tag cycle.
- Unplug the Ethernet cable. Expected: the fields return to ###; plug it back in and the values recover without a restart.
- Reboot the PC and start Runtime again. Expected: the link comes up on its own, which confirms the binding persisted.
Pitfalls that recreate the fault #
- On a dual-NIC PC, binding the plant-network adapter instead of the port the CPU cable is on.
- Changing the PLC's IP address without updating the station address in the project and retransferring it.
- Copying the project folder to a fresh PC and expecting the access point binding to move with it.
Questions asked
Does a successful ping mean WinCC flexible Runtime can read S7-300 tags?
No. Ping exercises ICMP echo only: it proves the cable, the addresses and the subnet are right, and nothing about the S7 protocol session. Runtime opens its tag connection through the access point layer, so a PC can pass ping and still show ### in every field. When every field goes ### at once while ping still passes, the binding in Set PG/PC Interface is the first place to look, not the network.
Does the PG/PC interface binding copy with the runtime project?
No. The binding is a Windows setting on each PC and is not stored in the project file, so there is nothing to export, import or ship with a copy of the project. Each target PC is configured once in Set PG/PC Interface; a project deployed to five PCs can end up with five different bindings.
What station address, rack and slot does a WinCC flexible connection to an S7-300 use?
The station address is the CPU's IP address on the Ethernet network. Rack and slot describe where the CPU sits in the S7-300 rack: on the standard layout the power supply occupies slot 1, the CPU slot 2 and the interface module slot 3, so a single-tier station reads rack 0, slot 2. Read the position from the project's hardware configuration rather than assuming it, because a connection that names the wrong slot opens no session and the fields stay ###.
Can a missing TCP/IP entry be added to Set PG/PC Interface by hand?
No. The adapter list is enumerated by the S7 communication components that install together with WinCC flexible, so an empty list means those components never registered on that PC. Adding another network adapter in Windows does not populate the list, and no separately downloaded driver creates the TCP/IP entry. The entries reappear only when Runtime is installed again and registers its components.