How-to
How to find configuration software for a legacy TP070 touch panel
Short answer
A TP070 is configured with TP Designer, the add-on that shipped in the STEP 7 Micro/WIN Toolbox era and runs under Micro/WIN V4 — not with WinCC flexible, ProTool or TIA Portal. Read the order number on the rear label to match the toolset to the panel's firmware generation, source the package through the manufacturer's own channels, and transfer over PPI at 9.6 kbit/s.
On this page
- Which software actually configures a TP070?
- How do you tell which TP070 generation is on the wall?
- Where do you get the Toolbox or TP Designer legitimately?
- Which Windows host runs the legacy toolset today?
- How do you connect and transfer over PPI?
- Why does the transfer fail or the panel ignore the project?
- When is replacing the TP070 the right call?
- Questions asked
A TP070 that comes off the wall with no project and no CD is not a dead panel; it is a toolset-matching problem. The panel is a small SIMATIC touch terminal that Siemens sold for use in front of S7-200 CPUs over PPI, and it was never taken into the WinCC flexible or TIA Portal toolchains. The software you need is the generation-specific configuration package from the Micro/WIN era, matched to the panel by the order number on its rear label and sourced through the manufacturer's support portal and its partners. This article walks the bench sequence in the order you meet it: identify the panel generation, obtain the matched toolset, host it on a 32-bit Windows guest, and put a compiled project onto the panel over PPI.
Which software actually configures a TP070? #
The TP070 is configured with TP Designer, the add-on tool that shipped in the STEP 7 Micro/WIN Toolbox era and runs under Micro/WIN V4; WinCC flexible, ProTool and TIA Portal cannot produce a project the panel accepts.
The manufacturer's own product entry for the panel, document 4558312 on the Industry Online Support portal, describes the TP070 as configured with Micro/WIN V3.1, and support-forum answers state that TP Designer configures the TP070 only and no other HMI or panel. A working combination demonstrated in the field runs STEP 7 Micro/Win v4.0.8.06 together with TP Designer v1.0.0.31 against a TP070, and a forum answer records the tool's origin: it shipped as an add-on in the MicroWIN v3.2 Toolbox, on an accompanying CD to Micro/WIN.
The trap is reaching for the toolchain already on your laptop. ProTool, WinCC flexible and TIA Portal all address other operator-terminal families, and none of them emits a project a TP070 accepts, so no export or conversion trick bridges the gap. Matching design software to panel hardware instead of to the laptop is the discipline across every HMI family; the guide to which HMI software works with which HMI panel hardware applies it system by system.
How do you tell which TP070 generation is on the wall? #
Read the order number on the rear label: an earlier-generation panel carries an order number in the …0AA00… region, and the later Blue-Mode generation sits in the …0AA01… region, which decides the toolset before you install anything.
The order number (MLFB) is printed on the label on the back of the housing. Isolate the panel from its supply before sliding it out of the cut-out to read the label. With the order number in hand, the matching table is short:
| Rear-label order number | Panel generation | Configuration package | Host |
|---|---|---|---|
| …0AA00… region | Early firmware | Micro/WIN Toolbox-era package with STEP 7 Micro/WIN V3.1 | A Windows guest of its own day |
| …0AA01… region | Blue-Mode firmware | TP Designer under STEP 7 Micro/WIN V4 | 32-bit Windows XP-class guest |
The start-up display is the tie-breaker when a label is unreadable: a Blue-Mode panel announces that generation when it powers up with no project loaded, and a panel that comes straight up asking for its configuration without that line is the early revision. Record the order number in the panel's asset record so the next engineer does not repeat the identification.
Where do you get the Toolbox or TP Designer legitimately? #
Get the toolset from the manufacturer's support portal and its sales partners, never from a secondhand download: the support portal still hosts the TP070 documentation and a demo project that requires TP Designer and Micro/WIN, and the software itself comes only through those same channels.
Concretely, the portal carries three pieces of TP070 material worth pulling: the product entry (4558312) that pairs the panel with Micro/WIN V3.1, the TP Designer threads that confirm the tool's scope, and the TP070 demo project (7193770), which requires TP Designer and Micro/WIN and ships with a guide document explaining the set-up and configuration of the demonstration program. The demo project is useful even before your software arrives, because it shows a known-good project structure and the transfer sequence.
The configuration software itself is not something a web mirror can supply legitimately. It was distributed with the Micro/WIN products of its era, and the legitimate path today runs through the manufacturer's support portal and its sales partners; if your organisation ran TP070s, the Toolbox CDs may already sit in the software archive. A copy from a file-sharing site is an unlicensed copy, and it has no place on an engineering workstation.
Which Windows host runs the legacy toolset today? #
Run the toolset on a 32-bit Windows guest: Micro/WIN and TP Designer are 32-bit applications from the Windows 2000/XP era — the working pair documented in the field is STEP 7 Micro/Win v4.0.8.06 with TP Designer v1.0.0.31 — so a Windows XP-class virtual machine is the safe host.
The reason is dull but firm: forcing 32-bit installers of that vintage onto a current 64-bit desktop is how half-installed toolsets happen. Give the guest one real serial port, or pass the PC/PPI adapter through to it as a USB device, and the communications stack behaves as it did on original hardware. Community threads about STEP 7 Micro/WIN V4.0 SP9 against 32-bit and 64-bit Windows show how much time the compatibility question eats; one virtual machine answers it once for both tools. If your panel turns out to be the early revision, budget a second, older 32-bit guest as well, because the V3.1-era Toolbox targets the operating systems of its own day.
How do you connect and transfer over PPI? #
Connect the panel and the CPU on one PPI bus through a PC/PPI cable set to 9.6 kbit/s, give each station its own address, and transfer the compiled project from the programming tool to the panel — the same cable the S7-200 itself uses.
PPI is the S7-200's native point-to-point protocol on an RS-485 electrical interface, and the TP070 takes its place on that bus as a station of its own. The end-to-end sequence from a bare bench to a running panel:
- Wire the panel's supply exactly as its rear label specifies, power it up with no project loaded, and confirm which generation the start-up display reports.
- Set the PC/PPI cable for PPI at 9.6 kbit/s with its DIP switches, and connect it to the RS-485 bus that the S7-200 and the TP070 share.
- In the programming tool's communications settings, select the PC/PPI interface and set the same rate, so cable and tool agree.
- Give the panel a station address that does not collide with the CPU: the S7-200 leaves the factory at station address 2, so address 3 is a safe choice for the panel.
- Open or build the project in the toolset the label called for — the Toolbox-era package with Micro/WIN V3.1, or TP Designer v1.0.0.31 under Micro/WIN V4.
- Compile the project and start the transfer to the panel, power-cycling it first if the tool asks for it.
- Confirm the runtime screens come up and show live values from the CPU before declaring the job done.
Worked example: a bench panel's rear label ends in the …0AA01… region and its start-up display announces Blue-Mode. The decision writes itself: TP Designer v1.0.0.31 under STEP 7 Micro/Win v4.0.8.06 on a 32-bit Windows XP-class guest; the PC/PPI cable set to 9.6 kbit/s and the tool set to the same 9.6 kbit/s, which cancels the only rate variable; CPU at station address 2, panel at 3, so no address collision. Three numbers — order-number region, matched rate, distinct stations — decide the whole job, and every one of them is checkable before the transfer starts.
Why does the transfer fail or the panel ignore the project? #
Most failed transfers are an input disagreement, not a dead panel: the project came from the wrong toolset generation, the cable and the tool disagree about the 9.6 kbit/s rate, or two stations share one PPI address — check those three before you blame the hardware.
Start with the generation check, because TP Designer configures the TP070 only, and a project built for the other generation has nowhere to run. If the label region and the toolset agree, the remaining suspects are boring: a DIP switch leaving the cable off the agreed rate, or a station address duplicated on the bus. Transfer-mode surprises are a recurring legacy-panel theme — the TP177 Micro fault where only a serial transfer path appears is a different terminal teaching the same lesson, that the tool and the panel must agree on the route before anything moves.
When no source project exists at all, a transfer is not the job — a rebuild is. Before committing to that, check what an upload can return: uploading a program from an old touchscreen HMI explains what legacy-panel uploads give and do not give, and on the TP070 expect a rebuild in the matched toolset to be the realistic path.
When is replacing the TP070 the right call? #
Replace the panel when the matched toolset cannot be sourced legitimately or the unit is failing: a TP070 has no migration path into WinCC flexible or TIA Portal, so every hour spent hunting software is an hour a supported operator station would have saved.
The practical line: rebuild and keep running a TP070 while the matched software is in hand and the panel is healthy, and replace it the moment either condition breaks. Sourcing a decades-old toolset for every future screen change is support work the plant pays for forever. When the decision goes the other way, the successor for an operator terminal like this is a PC-based station — modern industrial panel PCs run current HMI runtime software against the same machine signals. Keep the rear-label order number in the asset record either way: it is what tells the next engineer which software generation that panel expects.
Questions asked
Can TP Designer run on a 64-bit Windows 10 or 11 PC?
Not as a native install. The toolset is 32-bit software from the Windows 2000/XP era, so keep it in a 32-bit Windows XP-class guest under a desktop hypervisor and pass the PC/PPI adapter through to the guest or map a real serial port. Community threads discuss STEP 7 Micro/WIN V4.0 SP9 against 32-bit and 64-bit Windows 7, but the virtual machine settles the question once for both tools.
Does a project from the early Toolbox open in TP Designer?
No. The early Toolbox package and TP Designer under Micro/WIN V4 are separate tools from different eras, and no conversion path between their projects is documented. Identify the panel from its rear-label order number first, then build in the toolset that matches that generation; re-creating the screens in the correct tool beats fighting a project the panel was never meant to load.
Is there a way to study a working TP070 project before building my own?
Yes. The manufacturer's support portal hosts a TP070 demo project under document 7193770 that requires TP Designer and Micro/WIN and comes with a guide document explaining the set-up and configuration of the demonstration program. Pull it, rebuild it on a bench panel, and use it as the reference for screen types, tagging and the transfer sequence before you touch the running machine.
The panel came with no project and no media. What now?
Plan on a rebuild. TP070 projects belong to the generation-specific toolset, and neither environment converts forward into current software, so there is nothing to migrate. Read the order number on the rear label, obtain the matching package through legitimate channels, and re-create the screens against the running S7-200 program. On other legacy HMI families a program upload sometimes succeeds, so it is worth an attempt before committing to a rebuild.
Is ProTool a valid alternative for this panel?
No. Outdated advice still sends TP070 owners to ProTool, but the configuration threads on the manufacturer's support portal are explicit that TP Designer is the tool for the TP070 and supports no other panel. ProTool addresses different operator-terminal families and will not produce a project the TP070 accepts, so chasing a ProTool license for this panel is effort spent on the wrong software.