Explainer
What STEP 7 is in a PLC project, and which one you need
Short answer
STEP 7 is the engineering software you use to program, configure, diagnose and download to SIMATIC PLCs — a workstation tool, not a part of the PLC itself. SIMATIC Manager, also called STEP 7 Classic, configures S7-300 and S7-400 CPUs; STEP 7 inside TIA Portal configures S7-1200 and S7-1500. Read the CPU family from the module label or the existing project, open the matching environment, and confirm the project's hardware configuration matches the installed CPU before you edit or download.
On this page
STEP 7 is the engineering software for SIMATIC PLCs: the tool on your workstation that creates the program blocks, configures the hardware and networks, downloads them to the controller and shows you live values when something needs fixing. It is not a module, a card or a runtime part of the PLC — take the workstation away and the controller keeps executing what it holds. The name covers two different environments, and the CPU family decides which one you need: SIMATIC Manager, also called STEP 7 Classic, for S7-300 and S7-400; STEP 7 inside TIA Portal for S7-1200 and S7-1500. Read the family off the CPU label or out of the project the plant keeps, open the matching environment, and before you edit or download anything, make the project's hardware configuration match the machine it will run on.
What STEP 7 holds, and what it does not #
STEP 7 is the environment between you and the controller. One installation holds the project, and the project is a database with three parts that must stay consistent with each other: the hardware configuration, which names the CPU, every module and the slot each occupies; the network configuration, which defines how the devices communicate; and the program blocks, which are the logic itself. A download sends configuration and blocks to the controller, and the online functions — value monitoring, diagnostics, program changes — are how you work on a machine that is running.
The controller needs none of this to run. A SIMATIC CPU scans its inputs, executes the loaded program and drives its outputs every cycle with no engineering station attached. STEP 7 observes and changes that behavior; it is not a component of it.
The programming languages are those of IEC 61131-3, the international standard that defines how PLC programs are written. Day to day you will mostly meet its two graphical languages, ladder logic (LAD) and function block diagram (FBD), next to the textual statement list (STL) and structured text.
One name, two environments #
STEP 7 survived a generational change in the tooling, so the name now covers two environments. The older one is SIMATIC Manager, whose releases carry V5 version numbers — the manufacturer's own migration guide compares STEP 7 V5.5 directly with STEP 7 in TIA Portal. The current one is TIA Portal, a single project framework in which the controller program, the operator visualization and the drives live together; STEP 7 is its PLC part.
| Environment | Project container | CPU families it configures | Where you meet it |
|---|---|---|---|
| STEP 7 Classic | SIMATIC Manager project | S7-300, S7-400 | the installed base of S7-300 and S7-400 machines |
| STEP 7 in TIA Portal | TIA Portal project | S7-1200, S7-1500 | new projects and stations migrated onto S7-1500 |
The environments are not interchangeable: a Classic project cannot reach an S7-1200 or S7-1500, and TIA Portal does not configure S7-300 or S7-400 stations. That is exactly why the manufacturer documents a migration path between them instead of a compatibility mode.
Which environment a machine needs #
Decide from the CPU, not from the machine's age, the label on the operator panel or a colleague's recollection.
- Read the family designation printed on the CPU module itself and read it against the table above; the generation number on that label is the whole decision.
- Open the project the plant actually keeps for the machine and check the CPU named in its hardware configuration. A SIMATIC Manager project confirms the Classic environment; a TIA Portal project confirms Portal.
- If the label and the project disagree, stop before editing or downloading. The download follows the project, not the rack, so an unresolved mismatch is an undiagnosed fault.
The family settles the environment; it does not have to settle the exact CPU. Families span variants — the S7-300 line alone comes in standard, compact and fail-safe versions — and the variant is pinned when you complete the hardware configuration, not when you pick the tool.
None of this needs a running production line to learn on: the walkthrough on building ladder logic practice projects in STEP 7 gives you a project where a wrong hardware configuration or a bad download costs nothing.
Worked example: one line, two generations #
This example is illustrative, with example inputs chosen to show the arithmetic. A packaging line has four controller stations: stations 1 through 3 are older S7-300 and S7-400 CPUs, each kept in a SIMATIC Manager project, and station 4 is a new S7-1500 that extends the line.
The count: 3 + 1 = 4 CPUs. The environments: 2, one SIMATIC Manager and one TIA Portal. The conversions if every project stays native to its CPU: 0.
If the plant standard instead demands a single environment, the three legacy stations each become a migration project — the documented path takes an S7-300 or S7-400 project into a TIA Portal world built on S7-1500 hardware, so each one involves a CPU generation change plus the software and hardware differences the migration guide catalogs. That is 3 hardware-and-software projects, not 3 file conversions.
Decision: keep each project native to its CPU and run both environments on the engineering workstation; treat migration as scheduled work for a maintenance window, machine by machine, with the migrated project accepted against the new CPU before it runs the line. Before putting two environments on one workstation, confirm its Windows release is a documented pairing for both packages.
Match the project to the rack before you download #
Before you edit anything, the project has to describe the machine it will run on. Compare three things: the CPU designation in the hardware configuration against the label on the installed CPU; the configured module layout against what is actually snapped into the racks, slot by slot; and the network configuration against the ports and cables you can see. When the three agree, the project represents the machine and an edit lands where you think it will.
A mismatch shows up two ways. The download is refused outright, which is the harmless case. The harmful case is a download that goes through into a machine the project does not describe: the logic addresses I/O where the project believes it sits, not where it sits, and the machine obeys a program written for a different station.
If the station you are standing up is a modular remote I/O station, work through the remote I/O commissioning checklist instead of improvised checks; it sequences these same comparisons at station level.
A download overwrites the program the controller is executing and can replace its configuration. Before downloading to a controller that drives a live machine, confirm the target station, the content of the change and how you will back the machine out if the change misbehaves.
What the software can and cannot tell you #
Online monitoring shows values: the input bit, the intermediate condition, the output command. It does not prove the field device or the wiring is correct — a miswired sensor still produces a clean-looking value. Trace a fault from the physical input through the logic to the commanded output, then watch the machine's physical response; commissioning is finished when command and response agree, not when the download completes.
The dependence runs one way: the controller runs without STEP 7, so a missing engineering station is never itself a fault, and no amount of software work corrects a rack that does not match the project. Settle the hardware and configuration agreement first, and the software work becomes straightforward.
Questions asked
Does the PLC need STEP 7 running to keep working?
No. Once the program is downloaded, the CPU scans its inputs, executes the logic and drives its outputs every cycle with no engineering station connected. What you lose without STEP 7 open is the engineering view: live monitoring, controller diagnostics, forcing and any program or configuration change. A plant full of SIMATIC controllers runs its shifts without a single STEP 7 seat in use, which is why a missing laptop is never by itself a machine fault.
Can a STEP 7 Classic project be opened in TIA Portal?
Not by opening it. The two environments keep separate project formats, and the documented path runs one way, from Classic to Portal: the manufacturer's migration guide moves SIMATIC S7-300 and S7-400 projects toward S7-1500 targets, and nothing documented moves a Portal project back into SIMATIC Manager. Plan migration as an engineering project with its own hardware changes and acceptance testing, not as opening and saving the same file in a newer tool.
Which Windows version does STEP 7 run on?
There is no single version. Each STEP 7 release pairs with specific Windows versions, and the manufacturer publishes a compatibility list that matches STEP 7 package versions, SIMATIC optional packages and Windows releases. Check the list for your exact release before installing or upgrading the engineering workstation. If you want Classic and Portal on one machine, the same list is what tells you whether that combination is documented; if it is not, put one environment on a second workstation or in a virtual machine.