How-to
Run WinCC 7.0 PC Runtime over a PROFIBUS card
Short answer
No panel-versus-PC switch exists: launch WinCC Runtime on the PC, but the PROFIBUS link only works after the card driver is installed, the PC interface points at that card, and the WinCC connection carries the PLC's station address, rack and slot — then a moving tag value proves the link.
On this page
There is no panel-versus-PC switch to set in WinCC 7.0. Runtime executes the project on whatever PC it is installed and licensed on, so on the new machine you start Runtime and the screens come up — but starting it proves nothing about the PLC. The PROFIBUS link exists only after four configurations line up: the interface card with its communication software in the PC, the interface selection pointing at that card, the project connection carrying the PLC's bus address, rack and slot, and a tag test against a value that actually moves. The quick answer — start Runtime and configure the network — is half right: the network half is the whole job.
Why the panel habit does not carry over #
A panel project is transferred to a target device; a PC project is opened and run by the Runtime living on that same PC. Nothing inside the project declares a target type. What changes on the PC is that the communication driver has to find real interface hardware instead of a simulator.
How a project reaches its runtime and which PLC driver it uses are two separate decisions, which is why separating the HMI transfer method from the PLC driver selection settles most of the panel-habit confusion. The PC adds two prerequisites a panel never asks about: a runtime license on that machine — WinCC RT and RC licensing and moving a runtime key covers what has to travel with it — and an installed runtime at least equal to the project version, since a 7.0 SP2 project does not run on an unpatched 7.0 installation. When this PC is also the machine's operator station, industrial panel PCs put the touchscreen and the runtime in one housing.
Install the card and its communication software #
A PROFIBUS card seated in the slot is inert until the PC communication software binds its driver. The documented example configuration here is a CP5613A2 PCI card in a standard PC talking to a CPU 313C-2 DP; the same steps apply to a CP 5512 card in a laptop, with that card's own name appearing wherever a selection is made.
- Install the SIMATIC NET PC software delivered with the card. Windows alone does not bind the driver, and a card that appears in the device list without it still cannot carry S7 communication.
- Open the card's configuration view and confirm it reports the card present and error-free. Physical presence is not evidence of a working driver.
- Open Set PG/PC Interface from the SIMATIC NET group in the Windows Start menu. If the card's PROFIBUS entry is not in the interface list, stop and fix the installation before touching the project.
Point the PC interface at the card #
Set PG/PC Interface is where the PC declares which physical adapter carries S7 communication. Assign the online access point to the installed card's PROFIBUS entry, then open that entry's parameterization and set the card's bus address to the one your network plan reserves for the PC — the address set under the parameterization must match the address the plan assigns, never an improvisation. Three numbers decide whether the card joins the bus:
- Bus addresses run 0–126 and must be unique. The example CPU 313C-2 DP ships at address 2, so the card takes a free address such as 3.
- The transmission rate must equal the existing bus — commonly 187.5 kbit/s or 1.5 Mbit/s, with 12 Mbit/s the DP ceiling.
- At 1.5 Mbit/s a Type A cable segment is good for 200 m, and termination is active only at the two physical ends of the segment.
Write the chosen card address into the commissioning record before moving on.
Create the PLC connection in the project #
The card gives the project a path to the wire; the project still has to name the PLC. That happens in the tag management area of the project, where the S7 communication driver for S7-300 and S7-400 controllers is added and where the PROFIBUS adapter is selected.
- Add the S7 communication driver for S7-300/S7-400 to tag management.
- In the driver settings, select the PROFIBUS adapter entry that names your installed card — the CP 5512 entry on the laptop, the CP5613 entry on the PCI machine.
- Create a connection on that adapter and enter the PLC identity: bus address, rack and slot.
- For the CPU 313C-2 DP that is address 2, rack 0, slot 2. The S7-300 layout fixes the CPU in slot 2 — slot 1 is the power supply — so on any S7-300 you count to slot 2 instead of guessing. On an S7-400, read rack and slot from the PLC's hardware configuration, because they follow the actual mounting.
- Match the connection's bus settings to the real bus values from the previous section. Values chosen by trial produce faults that masquerade as wiring problems.
Put the tags on that connection #
Every process tag belongs to a connection. Create the live tags on the new PROFIBUS connection with the address and data type the PLC program actually uses — MW20 as a 16-bit word, an input as a bit — and keep simulation tags off the test screens so a static value cannot pass as communication. If the project was built on another computer, the driver selection travels with the file but the card does not: card, software and interface selection exist only on the runtime PC, and each has to be verified there before the first start.
Start Runtime and prove the link with a moving value #
A frozen display is not a passed test: a broken link often leaves the last value on screen behind healthy-looking graphics. Reserve a safe test value in the PLC and make it move. With the machine in an approved test state — never force production logic just to generate a signal — the pass criterion is arithmetic, not opinion.
Example test: the PLC program increments MW20 by 1 every second. Note MW20 at the PLC and on the WinCC screen, wait 30 seconds, and read both again. Expected change = 30 s × 1 count/s = 30 counts. Both ends must show the same delta, and the screen value must step up during the window rather than jump once at the end. Then return the counter to 0 by the approved method and watch the display follow it down; a value that only ever rises was never live.
| Commissioning item | Value | Basis |
|---|---|---|
| PLC | CPU 313C-2 DP | Example configuration |
| PLC bus address | 2 | S7-300 factory default |
| PC card | CP5613A2, PCI | Example configuration |
| Card bus address | 3 | Free address on this bus |
| Transmission rate | 1.5 Mbit/s | Must equal the existing bus |
| Connection identity | Station 2, rack 0, slot 2 | S7-300 fixed slot layout |
| Test counter | MW20, 1 Hz, 30 s window | Engineered for this test |
If the tag stays dead while the PLC counts, tracing the path when WinCC receives no data from an S7 PLC narrows the fault layer by layer.
Where each failure points #
Change one item at a time and rerun the same 30-second counter test so every correction proves itself. The decision order:
- Runtime starts, no tag ever updates and the connection never establishes: card or interface layer. Reinstall the communication software and reassign the access point before editing the project.
- Connection establishes but individual tags are wrong: connection identity or tag mapping. Recheck station, rack, slot, address and data type against the PLC.
- Link drops intermittently: physical layer. Look for colliding addresses, missing termination at a segment end, or a segment stretched past its length limit for the transmission rate.
- The value looks plausible but never moves: you are reading a simulation tag or a different address than the one the program increments. Verify at the PLC side first, then fix the tag.
Questions asked
Is there a setting that tells WinCC 7.0 the project runs on a PC instead of a panel?
No. The project carries screens, tags and a communication configuration; it does not carry a target type. Wherever Runtime is installed and licensed, it runs the project, and the only thing that differs on a PC is that the communication driver has to find real interface hardware. A single-user project on one PC also needs none of the server-and-client configuration you would use to serve several stations.
Which PROFIBUS address should the PC card take?
Any free one. PROFIBUS addresses run 0 to 126 and every station must be unique, so list the addresses already used on the bus, keep the PLC at its configured address — S7-300 CPUs commonly leave the factory at 2 — and give the card a number nothing else owns, such as 3 on a small bus. Two stations answering to one address produce intermittent faults that look like cabling, so write the choice into the network plan.
Can several operator PCs read the same PLC over PROFIBUS this way?
Yes, when each PC has its own card, its own unique bus address and its own configured connection; the PLC simply sees independent communication partners. Past two or three stations, consider reshaping the project instead: one PC as the WinCC server and the others as clients that view it, which leaves one connection set to maintain instead of one per machine.
Runtime started and every tag shows an old value. What do I check first?
Check the interface layer before the project. Open Set PG/PC Interface and confirm the access point is assigned to the installed card's PROFIBUS entry. Projects copied from another computer only keep communicating when this PC's selection matches the hardware, and a missing or mismatched entry fails every tag at once, which distinguishes it from a single bad tag address. If the entry checks out, move on to station, rack and slot.