Explainer
How WinCC and STEP 7 Work Together in a PLC Project
Short answer
STEP 7 configures and programs the Siemens PLC; WinCC builds the operator screens that read and write selected PLC variables over a configured connection. The boundary between the tools is the tag: STEP 7 owns the variable, WinCC owns the display and command objects bound to it.
On this page
- What is the difference between WinCC and STEP 7?
- Where is the boundary between the two tools?
- How does a value get from the PLC onto a WinCC screen?
- What is the difference between an internal and an external tag?
- How does an operator command get from a WinCC button into the PLC?
- Does the WinCC project have to live inside the STEP 7 project?
- Why is there no HMI station under Insert Station in SIMATIC Manager?
- Where do you start when the WinCC display shows the wrong value?
- Questions asked
STEP 7 is Siemens' engineering tool for the PLC itself - hardware configuration, wiring addresses, and the control logic - and WinCC is the separate engineering tool and runtime for the operator layer: screens, alarms, trends, and recipes. The two are joined by exactly one thing: tags on a configured connection. STEP 7 owns every controller variable; WinCC owns the display and command objects bound to those variables, and the connection moves the values between the two runtimes. This article walks the whole signal path in both directions, separates internal from external tags, explains when the HMI project lives inside the STEP 7 project, and shows where to look when a displayed value is wrong.
What is the difference between WinCC and STEP 7? #
STEP 7 configures and programs the Siemens PLC - its hardware, inputs, outputs, and logic - while WinCC builds the PC-based operator layer that supervises that PLC with screens, alarms, and trends, and the two exchange data only through tags on a configured connection.
Unlike a single-environment package where one program reads the I/O and draws the front panel, Siemens splits the job into two products with two engineering tools and two runtimes. STEP 7 is the controller side: hardware configuration, input and output addressing, and the control program. WinCC is the operator side, the supervisory layer in SCADA terms: screens, alarm lists, trend archives, recipes.
STEP 7 programs the controller in IEC 61131-3 languages - the international standard that defines PLC programming languages - offered in Siemens notation as LAD, FBD, STL, SCL, and GRAPH. WinCC never executes control logic; it displays and writes what that program produces and consumes.
The family names matter because they look alike: classic WinCC is the PC-based SCADA line, WinCC flexible engineered panel-based operator screens alongside SIMATIC Manager, and WinCC Unified is the TIA Portal visualization. Installation and integration instructions belong to one of them, not to all of them. Which edition of STEP 7 a job needs is its own question - what STEP 7 is in a PLC project, and which one you need sorts the editions from the professional versions.
Where is the boundary between the two tools? #
The boundary is the tag: STEP 7 owns the variable - its address, its data type, and the logic that writes it - and WinCC owns the display and command objects bound to that variable, so no screen object ever touches controller memory directly.
| Side | What it owns | Where it is engineered |
|---|---|---|
| Controller behaviour | Variable addresses, data types, and the logic that writes every value | STEP 7 |
| Operator presentation | Screens, external tags, bindings, alarms, trends, write targets | WinCC |
A tag is the working contract between the two sides, so keep it written down: for each exchanged variable, its meaning, data type, engineering unit, scaling, and whether the PLC or the operator owns writes to it. That list is also what you verify whenever either project moves, which is the whole discipline of validating HMI variables during a software migration.
How does a value get from the PLC onto a WinCC screen? #
A measurement passes through six stages - field device, PLC input channel, PLC processing, the configured connection, the WinCC external tag, and finally the screen object - and every wrong-value diagnosis starts by finding the first stage where the actual value differs from the expected one.
STEP 7 owns the first three stages; WinCC owns the connection, the tag, and the object. In an integrated classic project, compiling the STEP 7 side makes the block symbols available in WinCC Tag Management, and in the tag editor you open a tag's symbol cell and pick the variable from the S7 project tree that appears. The connection is created under the S7 channel in tag management, and its endpoint - which controller, and which of that controller's communication interfaces, a CP module or an onboard port - must match the STEP 7 hardware configuration.
In WinCC Unified the route is direct: access the PLC tags in the PLC tag table and connect them to the external tag, and with a non-integrated connection the addressing options depend on the type of connection configured.
What is the difference between an internal and an external tag? #
An external tag is a live reference to a variable in the controller, carried over the configured connection, while an internal tag exists only inside the WinCC project; giving an internal tag the same name as a PLC variable creates no link of any kind.
Internal tags hold screen logic: counters, calculated display values, language settings. External tags are coupled to a connection and update on the communication driver's cycle. The external tag's data type must match the controller variable - width and signedness included - and a mismatch does not always fail loudly: it shows up as values that go wrong only past a boundary, which is why an HMI writes the wrong PLC value above 9 in the classic signedness case.
One documented mapping trap sits in arrays: if you connect an HMI tag to an array in a STEP 7 data block whose lower limit is not 0, WinCC maps the elements onto an index range that starts at 0, so the block's numbering and the tag's numbering differ by that lower limit. Declare data-block arrays with a lower limit of 0, and the same index means the same element on both sides.
How does an operator command get from a WinCC button into the PLC? #
A command travels the same path in reverse - the screen object writes to the external tag, the connection delivers the write to the PLC variable, and STEP 7 logic decides whether the machine is permitted to act on it - across seven stages, never bypassing the logic.
Those seven stages are: screen object, external tag, connection, PLC variable, PLC logic, PLC output, actuator. The button writes a request; the program weighs it against operating mode, permissives, and interlocks before anything moves.
Treat every HMI write as a request to the logic, never a path around it - interlocks and safe-stop functions belong in the controller and its safety components, not in the screen.
Then display two things separately: the request, and the machine's actual feedback. A write the runtime confirms is proof the variable changed, not proof that anything moved.
Does the WinCC project have to live inside the STEP 7 project? #
No - the HMI project can be integrated, with an HMI station inside the STEP 7 project for navigation and shared tag selection, or kept entirely separate with the connection and tags configured by hand; both arrangements end up with the same runtime data exchange.
Integrated, the HMI station sits in the project tree, symbol selection reaches the S7 blocks directly, and one compile covers both sides - convenient for navigation and for keeping the tag list synchronized. Separate, you maintain a standalone WinCC project and configure the connection and tags by hand, which is the normal choice when the tools sit on different PCs or in different releases.
Project integration and runtime communication are different functions. A station visible in the engineering tree proves nothing about the runtime link, and a standalone project communicates just as well once its connection is correct. In current projects the same choice appears as TIA Portal versus the classic pair, and the TIA Portal versus STEP 7 plus WinCC hardware configuration comparison covers the configuration side.
Why is there no HMI station under Insert Station in SIMATIC Manager? #
A missing HMI station is an engineering-integration symptom, not a PLC communication fault: the integration between the installed WinCC flexible release and SIMATIC Manager did not register, usually because the components or their installation order did not match the documented combination.
Read the exact product name and release from each application's product information dialog, then confirm the pair has a documented integration and that its component was installed in the documented order. Repeating an installation sequence without checking release compatibility is the wrong diagnostic. The specific causes are covered in why the SIMATIC HMI station is missing in STEP 7 Insert Station. The WinCC flexible procedure is not transferable to classic WinCC or WinCC Unified - same family, different products.
Where do you start when the WinCC display shows the wrong value? #
Start at the screen and work backwards one stage at a time, comparing the value shown with the value in the PLC variable and then with the raw input, because the first mismatch tells you which side of the tag owns the fault.
Worked example, illustrative inputs on documented ranges - a 0 to 150.0 degree C transmitter on a 4 to 20 mA loop into an S7 analog input:
- Loop current measured at the input: 12.0 mA. Fraction of span = (12.0 - 4.0) mA / 16.0 mA = 0.5.
- The channel represents the live range as 0 to 27648 counts, so the converted value = 0.5 x 27648 counts = 13824 counts.
- STEP 7 scaling: 150.0 degrees C x 13824 / 27648 = 75.0 degrees C, written to a REAL variable in the data block.
- Expected on the screen: 75.0 degrees C.
Now compare stage against adjacent stage and commit:
- The REAL variable shows 75.0 degrees C and the screen shows 75.0 degrees C - the path is intact end to end.
- The REAL variable shows 75.0 degrees C but the screen shows 13824 - the divergence is on the WinCC side of the tag: the object is bound to the raw counts variable instead of the scaled value. Fix the binding, not the PLC.
- The REAL variable itself is wrong - 13824 or 0 - the divergence is upstream of WinCC, in the scale logic or the channel configuration. Fix it in STEP 7 before touching the HMI.
For symptoms you have not yet traced, the same layer-first logic applies:
| What you observe | Layer to inspect first | What you should find |
|---|---|---|
| The sensor changes but the input word does not | Wiring, input channel, hardware configuration | The input word tracks the measured field signal |
| The input word changes but the scaled variable does not | STEP 7 application logic | The scale or status block writes the variable it is expected to write |
| The PLC variable changes but the screen stays fixed | WinCC connection, external tag, object binding | The object references the same variable you monitor in STEP 7 |
| A command appears on screen but the machine does not act | HMI write target and PLC command handling | The write reaches the variable and the logic accepts or rejects it by mode and interlocks |
Before the floor sees any of this, exercise writes, values, and restarts against a real controller on an isolated bench - the same discipline as testing an HMI simulation against a live PLC.
Questions asked
Do I have to program the sensor itself in STEP 7 before WinCC can use it?
No. A conventional sensor is wiring plus an input channel: you configure the channel in STEP 7's hardware configuration and read it as a process input, and the sensor itself has no program. Smart sensors with their own setup, such as configuration tools or parameter files, are configured with the manufacturer's tool, and STEP 7 only consumes the values they deliver.
Does the WinCC tag name have to match the PLC variable name?
No. The link is the configured address or symbol reference, not the name. Two differently named objects can be perfectly connected, and two identically named objects can be completely unconnected - an internal tag named like a PLC variable still reads nothing but what WinCC itself writes to it.
Can one WinCC station supervise several STEP 7 PLCs?
Yes. Under the S7 communication channel you configure several connections, one per controller, and each external tag references the connection it belongs to. The practical limits are the runtime's documented connection count and the PC's load, not STEP 7, so count controllers and update rates before adding hardware rather than after.
What is WinCC OA, and is it the same product?
No. WinCC OA is the line for large, distributed systems, and it talks to S7 controllers through its own S7 Plus driver, which is built on the Siemens communication library. Its projects, engineering, and documentation are separate from classic WinCC and WinCC Unified, so installation and integration instructions do not carry over between them.
Can I engineer the WinCC project on a different PC from the STEP 7 project?
Yes. Separate projects are a normal arrangement: keep the data contract - variable names, addresses, data types, scaling - written down on both sides, configure the connection by hand in WinCC, and test the first exchange with a monitored variable before building the full screen set.