How-to
How to Configure WinCC 7.0 PLC Connections With STEP 7
Short answer
No. WinCC 7.0 and STEP 7 5.4 never connect to each other; each one talks to the PLC, so configure two separate paths: the S7Online access point for STEP 7, and in WinCC Tag Management the MPI channel's Logical device name set to MPI (PLSIM for simulation). Acceptance is one known PLC value displayed live with valid status.
On this page
- Does WinCC 7.0 connect to STEP 7 5.4 at all?
- Which cable and adapter carry both paths?
- How do you set the STEP 7 side so SIMATIC Manager goes online?
- Where is the logical device name set in WinCC?
- What rack and slot go in the WinCC connection for an S7-300?
- How do you add the WinCC project to SIMATIC Manager as an OS?
- What proves the whole setup works at runtime?
- Which setup do you actually need?
- Questions asked
WinCC 7.0 and STEP 7 5.4 never connect to each other, and no setting will make them. WinCC is the visualization and data-acquisition side; STEP 7 5.4 programs the PLC. Both reach the same controller over two separately configured paths, and each path is proven on its own. What follows configures both: the Set PG/PC interface access point S7Online that SIMATIC Manager uses for programming, and the MPI channel with its Logical device name that WinCC runtime uses for data. The acceptance check at the end, one known PLC value displayed live and then following a change, is what signs the setup off.
Does WinCC 7.0 connect to STEP 7 5.4 at all? #
No — the two programs exchange nothing at runtime; the only things they share are the PLC and, optionally, one project container in SIMATIC Manager, so you configure two separate paths and test each one.
WinCC builds the screens, collects process values and issues operator writes. STEP 7 5.4 holds the user program and downloads it into the CPU. The connections you actually need are WinCC to PLC and STEP 7 to PLC. You can also place the WinCC project inside the SIMATIC Manager station tree as an OS so testing and parameter changes happen from one engineering project, which is a convenience and not a communication path. For the division of work between the two tools, how WinCC and STEP 7 work together in a PLC project is the companion page, and if you are still matching editors to the CPU in the cabinet, what STEP 7 is in a PLC project and which one you need settles that side.
Which cable and adapter carry both paths? #
Use one MPI bus for both tools — a PC Adapter on USB or a CP5711 at the PC into the PLC's MPI port — because the S7 MPI driver and the PC Adapter are designed for more than one master, so the programming path and WinCC share the network.
MPI, the Multi-Point Interface, is the classic route for this software generation. Before touching either program, record three facts: the adapter as Windows reports it, the PLC port the cable actually lands on, and the CPU's MPI node address as it stands in the STEP 7 hardware configuration. Every later setting is checked against those three. For the same port seen from the panel side, connecting an HMI panel to an S7-300 MPI port with a PG shows the wiring arrangement.
How do you set the STEP 7 side so SIMATIC Manager goes online? #
Set the access point to S7Online in Set PG/PC interface (Control Panel), assign it the adapter's interface parameterization, and confirm the CPU shows up in SIMATIC Manager as an accessible station.
An access point is the software name a communication request is routed to; S7Online is the one the STEP 7 side uses. Assigning it the interface parameterization of the adapter you recorded makes the programming path concrete. Open the project in SIMATIC Manager and check the CPU appears as an accessible station before you touch WinCC. That online check proves the programming path only: it does not prove WinCC selected the same interface, and it does not prove any tag address is valid. Keep the working settings untouched as the baseline while you configure the WinCC side.
Where is the logical device name set in WinCC? #
In WinCC Explorer under Tag Management, add the S7 driver, right-click the MPI channel, open System Parameters, click the Unit tab, and pick MPI in the Logical device name drop-down list.
The channel is the driver family; the channel unit is the physical route through it, and the Unit tab decides which PC interface runtime drives. A Logical device name of MPI selects the installed MPI adapter directly. An access-point selection instead follows whatever Set PG/PC interface currently maps to that name, which is how the integrated SIMATIC Manager arrangement keeps both tools on one mapping. Re-check this tab whenever the adapter changes or a second adapter appears in the PC.
Under the MPI channel, create the PLC connection: station name, the CPU's node address from the hardware configuration, then rack and slot. For bench runs with no CPU wired, the same Unit tab is the simulation switch — set Logical device name to PLSIM and the channel talks to the simulated controller, a workflow testing HMI simulation against a live PLC covers in full.
What rack and slot go in the WinCC connection for an S7-300? #
Rack 0 and slot 2 — the S7-300 CPU's position in the rack addressing — entered on the WinCC PLC connection; take rack and slot for any other CPU straight from its STEP 7 hardware configuration.
The S7-300 CPU occupies slot 2 of rack 0 in the STEP 7 addressing scheme, and the WinCC connection parameters must repeat exactly that position. A wrong slot is the classic reason a connection with a healthy adapter and the right node address still delivers nothing: the driver reaches the rack and finds no CPU where it was told to look.
How do you add the WinCC project to SIMATIC Manager as an OS? #
Close the project in WinCC, exit WinCC entirely, then create the OS in SIMATIC Manager and open the project from that entry — the integration fails when the project is open in the standalone editor at the same time.
The steps:
- Close the project in WinCC Explorer.
- Exit WinCC completely.
- In SIMATIC Manager, create the OS in the station tree and point it at the intended project.
- Open the project through the OS entry.
- Re-check the MPI channel, the PLC connection and the Logical device name; integration must not have disturbed them.
Worth adding when parameter changes and testing dominate commissioning; skip it when you only need live values, since a standalone project connects to the PLC the same way.
What proves the whole setup works at runtime? #
One known value, read live: put 120 in a PLC memory word and require the WinCC tag to show 120 with valid communication status, then change it to 150 and require the display to follow — anything less is not a passed connection.
Worked example, illustrative, on a bench CPU: in the STEP 7 program, move the constant 120 into memory word MW100 every cycle. Create one WinCC tag on the MPI connection — unsigned 16-bit word, address MW100 — and place it in an I/O field. Start runtime and the field must read 120. Change the constant to 120 + 30 = 150 and download: the field must move to 150. Two correct reads out of two is a pass; a field stuck on the old value, or grayed out, is a fail regardless of what the offline checks said.
One safety note: do the write-direction test with actuators disconnected, because an operator entry in runtime lands on the real output with nothing in between. When the value never arrives, work through WinCC receives no data from an S7 PLC: trace the path next.
The full acceptance list, in order:
- Windows reports the adapter, and the cable sits on the CPU's MPI port.
- Set PG/PC interface maps S7Online to that adapter, and SIMATIC Manager sees the CPU.
- The Unit tab shows Logical device name MPI — PLSIM while running against the simulator.
- The PLC connection carries the CPU's node address, rack 0 and slot 2.
- Runtime shows the known value, then follows the change: 2 of 2 reads.
Which setup do you actually need? #
All three pieces, in this order: the S7Online access point when you program the CPU, the MPI channel with Logical device name MPI when you want live values, and the OS entry only when you want WinCC to open from SIMATIC Manager.
Decisions by job:
- Live values and operator writes: the channel configuration above is the whole requirement, and integration adds nothing to the data flow.
- Programming and downloads only: the access point is all you touch.
- Commissioning with frequent parameter changes: add the OS entry once the channel already passes the runtime test.
- Development before the CPU is wired: run the same project against PLSIM, then switch the Unit tab back to MPI.
Questions asked
What is the difference between logical device name MPI and S7Online?
MPI points the channel at one specific installed interface, so WinCC keeps its route even if Set PG/PC interface changes. An access-point selection such as S7Online makes the channel follow whatever interface that access point is currently assigned to, so one Control Panel setting steers both STEP 7 and WinCC. Choose MPI when only WinCC uses the adapter; choose the access-point route when you want one mapping shared by both tools.
Why does STEP 7 go online while WinCC tags stay invalid?
Because the two paths are configured separately. STEP 7 going online proves the S7Online access point is mapped to a working adapter; WinCC additionally needs its own Unit tab setting, the CPU's node address, and rack and slot on the connection. Check them in that order. On an S7-300 the frequent culprit is a slot other than 2, or a node address that differs from the CPU's MPI address in its hardware configuration.
How do you run the same test against PLCSIM instead of the real CPU?
Download the STEP 7 program to the simulated CPU first. In WinCC, change only the Unit tab of the MPI channel: Logical device name PLSIM instead of MPI. Leave the PLC connection as it is, because the simulated controller answers with the same addressing you configured for the real CPU. Switch the tab back to MPI before reconnecting the physical adapter, since this one setting decides which target runtime actually uses.
Does the OS entry in SIMATIC Manager replace the WinCC channel configuration?
No. The OS entry decides where the project opens from, not how it communicates, because runtime always reads the channel, PLC connection and logical device held in Tag Management. Integration is optional and changes the container rather than the communication settings, but after creating it, open the project once and confirm the Unit tab still shows the logical device you set before you trust it.