IMDTouchKnowledge BaseShop main store

Comparison

TIA Portal vs STEP 7 plus WinCC hardware configuration

HMI and touchscreens Published 8 min read

Short answer

Configuring the same PLC and HMI in TIA Portal instead of STEP 7 plus WinCC needs no extra PLC, panel, module or network hardware — the cabinet stays exactly as it is. The difference is where devices, networks and tags are configured: one integrated project instead of two. The one hard limit: S7-1200 and S7-1500 CPUs engineer only in TIA Portal, and CPU firmware sets the minimum release, so a V2.9 CPU needs TIA Portal V17 or higher.

On this page
  1. What changes and what does not
  2. Which CPUs force the tool choice
  3. The same cabinet in both environments
  4. Matching the device catalog to your cabinet
  5. Worked example: a V2.9 CPU and a WinCC flexible panel against TIA Portal V17
  6. The PLC-to-HMI link needs no new hardware
  7. Migrating the project is not a hardware change
  8. The decision for each cabinet
  9. Questions asked

No. Moving a PLC-and-HMI project from STEP 7 plus WinCC into TIA Portal does not add a single device to the cabinet: the same CPU, the same panel and the same network cable run the machine either way. What changes is the engineering environment. TIA Portal configures the controller, the panel and the connection between them inside one integrated project; the classic arrangement keeps the controller project in SIMATIC Manager and the panel project in a separate WinCC tool.

One hard limit decides the tool before anything else: S7-1200 and S7-1500 CPUs engineer only in TIA Portal, and the CPU's firmware sets the minimum release — a V2.9 CPU needs TIA Portal V17 or higher. This article compares the two environments side by side, shows how to match the device catalog to what is actually bolted into the cabinet, and works a V2.9 example through to its decision.

What changes and what does not #

The controller's job and the panel's job are identical in both environments. The PLC executes the control program; the HMI exchanges process data with that controller and presents it to the operator. TIA Portal integrates the engineering for both in one application, and its integrated configuration lets you create the PLC program and the HMI configuration through one software interface — devices, connections and HMI tags live in the same project and can reference each other directly.

None of that integration changes an electrical interface, adds a protocol or calls for a gateway. Extra hardware enters a project for one reason only: the installed equipment lacks the interface or protocol the chosen connection needs. A tool change is never that reason. Fix the order of decisions accordingly: inventory the cabinet first, then choose the engineering environment that covers that inventory.

Which CPUs force the tool choice #

The CPU family is the deciding input. S7-1200, S7-1500 and S7-1500T CPUs configure and program only in TIA Portal; SIMATIC Manager cannot be used on them at all, so no version of classic STEP 7 is an option for a cabinet that holds one. S7-300 and S7-400 CPUs sit the other way: those families are engineered in SIMATIC Manager, and TIA Portal does not configure them — such a cabinet keeps the classic tool unless the hardware itself is replaced.

Firmware then sets the minimum release. The manufacturer's compatibility documentation for these CPU families pairs firmware versions with engineering releases: a V2.9 CPU connects to a current programming device running TIA Portal V17 or higher and additionally, for example, to an HMI device. Read that as two rules in sequence: the CPU family selects TIA Portal, and the firmware shown on the CPU or in its diagnostics selects how new the release on your engineering station must be.

The word WinCC alone is not a specification, either. WinCC flexible is the classic panel engineering tool, WinCC (TIA Portal) is the HMI engineering inside TIA Portal, and classic WinCC is the PC-based SCADA that pairs with SIMATIC Manager. Name the exact product, its release and its target panel before you judge what it supports.

The same cabinet in both environments #

The cabinet is the constant in the comparison; the project layout is the variable.

Aspect TIA Portal STEP 7 plus WinCC classic
Controller families engineered S7-1200, S7-1500, S7-1500T (these three only) S7-300, S7-400
Project structure One integrated project holds controller, panel and connections A controller project and a separate HMI project
HMI-to-PLC connection Selected from the PLC inside the same project Entered separately in each tool, matched by hand
HMI tags Reference controller variables directly through the integrated connection Mapped across the project boundary by the engineer
Cabinet hardware required None beyond the installed PLC, panel and network None beyond the installed PLC, panel and network

Matching the device catalog to your cabinet #

A device catalog is the list of hardware a given engineering installation can configure, and the entry you select must represent the cabinet, not merely compile.

  • Select the CPU entry that matches the order number on the CPU label, not a convenient family member that makes the project compile. Compilation checks the project against itself; it says nothing about whether the project describes your cabinet.
  • Reproduce the installed module arrangement, each module in its actual slot.
  • Set the configured firmware to the version the CPU actually runs, because the firmware-to-release pairing is what the online connection follows.
  • Pick the exact panel entry for the HMI device. A family name is not an entry; if your installed TIA release does not list the exact panel, that release cannot configure it.
  • Before any download, compare the configured hardware against the CPU's online identification, so you know the connected device is the one the project describes.

One safety note belongs here: downloading a changed hardware configuration to a CPU that is running a live process can stop that process, so take the download in a planned stop, after the online comparison agrees.

The engineering product must also support the panel on the other end of the cable, which is its own matching problem — the article on which HMI software works with which HMI panel hardware covers that pairing.

Worked example: a V2.9 CPU and a WinCC flexible panel against TIA Portal V17 #

The inputs #

  • CPU: from the S7-1200/S7-1500/S7-1500T group, showing firmware V2.9 — read from the CPU itself; the manufacturer's compatibility documentation pairs that firmware with TIA Portal V17 or higher.
  • Engineering station: a laptop with TIA Portal V16 installed (illustrative input; substitute your own installed release).
  • HMI: a panel whose project was built in WinCC flexible — the classic arrangement this article started from.
  • Network: one Ethernet link already in service between panel and CPU; it must exist, because the pair already runs under STEP 7 plus WinCC.

The rule in words #

  1. The CPU's family selects the tool: this group configures only in TIA Portal, so SIMATIC Manager is out regardless of what the station owns.
  2. The firmware selects the minimum release: V2.9 requires TIA Portal V17 or higher.
  3. The panel project needs a conversion step, not a purchase.
  4. The physical link is reused exactly as found.

The arithmetic #

  • Tool check: the CPU belongs to the one group SIMATIC Manager cannot touch, so the tool must be TIA Portal.
  • Release check: station at V16 < required V17, one release below the threshold, so update the station to V17 or higher before going online with the V2.9 CPU.
  • Hardware check: PLC present (1), panel present (1), network link present (1); new modules required (0), new panels required (0), new switches or cables required (0). The compatibility documentation itself shows the single CPU serving a programming device with TIA Portal V17 or higher and additionally an HMI device — no third device enters the picture.
  • Project check: WinCC flexible panel project, so one migration step into the TIA project.

Result and decision #

Result: the cabinet stays as built, the engineering station moves from V16 to V17 or higher, and the panel project converts once.

Decision: buy no PLC, no panel, no module and no switch — the tool change adds zero hardware. Spend the effort on the release instead: below V17 with V2.9 firmware means step up to V17 or higher. The threshold flips only with an S7-300 or S7-400 in the same cabinet: keep SIMATIC Manager plus the classic WinCC tool, because TIA Portal does not configure those families.

An integrated project configures the connection; it does not create the wire. The panel still needs a compatible interface, correct IP addressing on the same subnet as the controller for an Ethernet link, and a connection entry that points at the intended CPU. In TIA Portal you select the PLC from inside the same project; under the classic arrangement you enter the same parameters in two separate tools and keep them matched by hand. The work moves location; the parameters and the cable do not change.

Then split two diagnostic questions that look alike: can the engineering station reach each device, and can the panel reach the controller? A download that succeeds from your laptop proves the laptop's path; it proves nothing about the panel's configured connection until the panel displays live values. The article on connecting an HMI panel to an S7-1500 PLC walks that connection setup end to end.

Migrating the project is not a hardware change #

Migration converts an existing project into another engineering environment — a software step that stands apart from every hardware decision in this article. For a panel project built in WinCC flexible, the route into TIA Portal is the documented migration path, and the article on migrating a WinCC flexible project to TIA Portal follows it step by step. Copy the original project before converting anything, so the classic route stays open.

Conversion proves structure, not content. A migrated project that compiles has passed a syntax check, not a data check; tags, screens and connections can still be wrong or missing. Verify the variables against the running controller before trusting the screens — the article on validating HMI variables during a software migration gives that check sequence.

The decision for each cabinet #

  • An S7-1200, S7-1500 or S7-1500T CPU in the cabinet: TIA Portal, with the release sized to the CPU's firmware — V2.9 calls for V17 or higher — and no new PLC, panel, module or network hardware.
  • An S7-300 or S7-400 CPU: SIMATIC Manager plus the classic WinCC tool, and again no new hardware.
  • Either way the cabinet stays as built. What a move to TIA Portal changes is where you configure devices, connections and tags: one integrated project instead of two, with the panel's project converted once through migration.

Questions asked

Can SIMATIC Manager and TIA Portal live on one engineering PC?

Yes. The two tool sets install side by side, and existing classic projects keep opening in SIMATIC Manager. Many engineering stations carry both: SIMATIC Manager for S7-300 and S7-400 cabinets and their classic WinCC projects, TIA Portal for anything with an S7-1200, S7-1500 or S7-1500T CPU. Installing TIA Portal does not convert or retire the classic projects by itself.

How do I find the firmware version my CPU runs?

Read it on the CPU's display where the model has one, or read it in the online diagnostics after the engineering station goes online with the CPU. The firmware series is the input to the release rule: it sets the minimum TIA Portal version, so a V2.9 CPU calls for V17 or higher. Check it before you install anything.

Does one engineer own the whole integrated project?

No. TIA Portal includes multi-user engineering, in which several engineers work in one integrated project at the same time instead of passing project files around, so controller work and panel work no longer queue behind a single copy of the project.

Do I have to replace a panel that my TIA release does not list?

No — the panel is rarely the problem; the release is. Newer TIA Portal releases carry wider device catalogs, so step the release up until the catalog lists your exact panel. Replace the panel only when it physically lacks the interface the connection needs, which is an equipment decision, never a software one.

Keep reading

  • How-to

    How to migrate a WinCC flexible project to TIA Portal

    One TIA Portal installation replaces both STEP 7 Classic and WinCC flexible, but the two project types move differently: the STEP 7 V5.x project is imported, and the WinCC flexible 2008 project is migrated through an intermediate release because the newest TIA Portal versions no longer offer that migration. Verify the exact S7-300 CPU and panel against the device lists and license STEP 7 and WinCC Comfort separately.

    HMI and touchscreens

  • How-to

    Decoding SLC N-File ASCII and Bit Arrays in FactoryTalk View ME

    20549 is hex 0x5045, the packed ASCII bytes for P and E — correct data read as an integer because FactoryTalk View ME has no Character Array object. Rebuild the text on a string-capable mapping (on ControlLogix, COP the bytes into a String tag's .DATA and set .LEN), and extract two-bit multistate codes with AND masks 3, 12, 48, 192 shifted right 0, 2, 4, 6.

    HMI and touchscreens

  • How-to

    How to Disable a Remote HMI Display Through PLC Control

    Put the interlock in the PLC, not the panel. Read each panel's current screen through Remote Display Number, force display 21 through Replace Display Number while the disable bit is latched, and on release write the stored number back, hold one second, then write 0 so the panel never reports it is being controlled remotely.

    HMI and touchscreens