Explainer
What the TiSTAR DEU does when you migrate to WinCC
Short answer
The DEU — Data Exchange Unit — is the TiSTAR core: it polls TI 545 PLCs over TIWAY, keeps the tag database and serves the IGT operator stations, so it has no role in a WinCC system. Keep it running only until WinCC has its own verified PLC path and the data on the DEU and its storage unit is recovered.
On this page
- What is the DEU in a TiSTAR system?
- What else makes up a TiSTAR system?
- Does WinCC talk to the TiSTAR DEU?
- Do you have to keep the DEU when WinCC replaces TiSTAR?
- How does WinCC reach the TI 545 PLCs without it?
- What happens to the TiSTAR tags and operator screens?
- When can you power the DEU down for good?
- Questions asked
The DEU is the Data Exchange Unit at the heart of a TiSTAR installation: the computer that polls the TI 545 PLCs over TIWAY, keeps the TiSTAR tag database current and serves the IGT operator stations. You do not have to keep it when WinCC replaces TiSTAR: it serves TiSTAR alone and offers WinCC no way in. Keep it running only until WinCC has its own verified path to the PLCs and the data on the DEU and its storage unit has been recovered. This article works through what each TiSTAR part does, why the DEU cannot be reused as a gateway, and the order that gets the cutover done without blinding the operators.
What is the DEU in a TiSTAR system? #
DEU stands for Data Exchange Unit: one computer holding the main processor and RAM with the TiSTAR database, the TIWAY communications card, and the interfaces to every IGT operator station.
It runs two jobs at once. On one side, its TIWAY card polls every TI 545 on the network and writes the results into its own tag database. On the other side, it answers the IGTs: an operator calls up a screen and the DEU supplies the live values behind it. The IGTs have no route to TIWAY of their own, so the DEU is the only path between the process and anything an operator sees.
That concentration is what makes the migration question sharp. Replacing TiSTAR means replacing both jobs at once — PLC polling and operator serving — and neither job is inherited just because the old computer stays energized.
What else makes up a TiSTAR system? #
A TiSTAR installation has three parts: one DEU, one storage unit, and as many IGT Industrial Graphics Terminals as the operators need, each a PC that talks only to the DEU, never directly to the PLCs.
| Part | What it holds or does | Disposition in the WinCC migration |
|---|---|---|
| DEU | Processor and RAM with the TiSTAR database, TIWAY communications card, IGT interfaces | TiSTAR data broker; no role once WinCC runs on its own path |
| Storage unit (DSU or DSS) | Hard-drive storage attached to the DEU | Stays until required history and configuration are recovered |
| IGT | Operator station displaying screens fed by the DEU | Replaced by WinCC operator stations |
The storage unit is the box your paperwork may call DSU, for Data Storage Unit, or DSS — the old documentation used both names for what is physically the same thing, a large hard-drive store hanging off the DEU. Read the label on the hardware in your own cabinet rather than trusting the abbreviation on a drawing.
The IGTs are PCs of their era whose only communications run back to the DEU, which makes their replacement a hardware decision and not just a software one. The station that takes an IGT's place is a PC running WinCC at the machine, and panel-mounted industrial panel PCs are the hardware class that replaces a dedicated operator terminal of that kind.
Does WinCC talk to the TiSTAR DEU? #
No documented interface lets WinCC read or write through a TiSTAR DEU, and the DEU was never designed as a transparent TIWAY gateway: it exists to poll PLCs and serve TiSTAR terminals, so WinCC cannot use it as a path to the TI 545.
The DEU is a data broker, not a gateway. Its documented purpose is to poll the PLCs into its own database and serve TiSTAR stations; nothing about it exposes TIWAY to a second SCADA package, and building a design on an undocumented pass-through means engineering against a system nobody ever specified. It is the same situation as any HMI package facing a controller it has no driver for — When the HMI Software Has No Driver for Your PLC covers how that failure shows up and what the realistic options are.
The decision is the firm version: design WinCC's communications as if the DEU did not exist. If a supplier claims a DEU-based path, the claim stays out of the design until it has been demonstrated live on your network, on your tags, at your poll rates.
Do you have to keep the DEU when WinCC replaces TiSTAR? #
No — the DEU has no role in the finished WinCC system. Keep it running through the migration only under two conditions: TiSTAR must stay live while WinCC is built and verified, or required data on the DEU and its storage unit has not yet been recovered.
Both conditions come straight from what the DEU owns. While TiSTAR serves the floor, it is the only thing operators can see through, so it lives until WinCC proves itself. And the DEU with its storage unit holds the only copies of the legacy tag database and any stored history, so recovery happens before removal, never after. Outside those two conditions the DEU contributes nothing: it cannot serve WinCC stations, and a WinCC system with its own PLC path does not read its database. Keeping it in the final architecture leaves a dead system energized for no return.
The staging logic — criteria first, parallel running, cutover, decommissioning last — is the same one used for any aging operator terminal, and Planning an HMI terminal replacement from an older operator panel works through it terminal by terminal; scale that sequence up from one panel to the whole TiSTAR installation.
How does WinCC reach the TI 545 PLCs without it? #
WinCC needs its own communications path to each TI 545 — a channel the migration supplier documents and supports for TIWAY and PEERLINK networks, engineered and verified without the DEU, not an assumed pass-through of the legacy broker.
Start with an inventory, because the network carries more than the screens show. List every TI 545 and its TIWAY drop, every PEERLINK peer exchange, every tag the operators read or write, every alarm, and everything stored on the DEU and its storage unit. PEERLINK deserves its own pass: it moves data between nodes on the network without an operator screen in the path, so a dependency can stay invisible until after the HMI already works. Trace who talks to whom before any network hardware is moved or powered down.
The target design then gives WinCC a channel to the PLCs that your migration supplier documents and supports for TIWAY; what that channel is and how it is set up is theirs to specify and demonstrate. Verify it under real load: with TiSTAR still running beside it, open every WinCC screen at every station and check each value's update rate against the TiSTAR display and the PLC itself. The DEU polled continuously for years, and the new path has to carry that traffic with all stations active, not just one bench test.
What happens to the TiSTAR tags and operator screens? #
The TiSTAR tag database and IGT screens do not import into WinCC automatically: you rebuild the tag set and screens in WinCC, then map every rebuilt tag back to the same TI 545 address the DEU used to poll.
The DEU's database is the authoritative list, so census it rather than working from memory of the screens. Worked example — sizing the migration from a tag census. Suppose the TiSTAR database holds 4,000 tags. Counting the IGT screens finds 2,750 tags displayed or entered, the alarm configuration uses 310, and the reports and logs use 540. The migration has to reproduce 2,750 + 310 + 540 = 3,600 tags, and 4,000 - 3,600 = 400 are referenced nowhere and can be left behind. The inputs are illustrative; run the census on your own database and migrate your own count.
Each rebuilt tag then maps back to the TI 545 address the DEU polled, and the census is what hands you that mapping screen by screen. The screens themselves get rebuilt for the WinCC station layout; where an import route exists for your panel generation, Importing legacy HMI screens when migrating to a new panel sets out what converts cleanly and what has to be redrawn. Either way, verification runs side by side: with TiSTAR and WinCC both live, compare every required display — values, alarm behavior, communications status — before anyone cuts over.
When can you power the DEU down for good? #
Power the DEU down only after three gates are closed: WinCC runs without it on its own PLC path, every required display has been compared side by side with TiSTAR, and all data on the DEU and its storage unit has been copied and verified.
Close the gates in that order. Build and verify the WinCC PLC path while TiSTAR still serves the floor. Move the operator stations over once the side-by-side comparison passes, and leave the DEU powered but unused so a rollback stays possible. Recover and verify the stored data before final acceptance, not after. When the process has run on WinCC alone through a full production cycle, the DEU has lost its last reason to be energized.
One check protects the operators through all of it: with the DEU still available, force a communications failure on the new path and confirm every WinCC screen raises its communication alarm instead of holding the last values — a screen that keeps displaying stale process data through a fault is the failure to catch during the migration, not during a shift.
That is the whole decision. The DEU is a bridge for as long as the migration runs and nothing afterwards: recovered, verified, then powered down for good.
Questions asked
Can I leave one IGT in place as a fallback after the WinCC cutover?
Only while the DEU stays powered. An IGT has no path of its own to the TI 545: it displays whatever the DEU serves it, so with the DEU off every IGT is blind. One IGT plus a running DEU is a legitimate legacy fallback until final acceptance; after that it can never show WinCC data.
In what order should I cut over several IGT operator stations?
Move one station first — the one whose loss for a shift would hurt least — and run it on WinCC through a full production cycle next to its IGT. Compare displays, alarms and update behavior, then convert the rest in stages, keeping the last IGT and the DEU available until final acceptance so the process stays visible somewhere.
How do I recover the data on the DEU and its storage unit before shutdown?
Copy the drives while the hardware still runs: image or copy the storage unit and any storage inside the DEU itself, open the copies on another machine to confirm they read back, and keep at least two sets on equipment outside the migration. If the DEU will not start, its drives become a job for a drive recovery service, so avoid repeated power-cycling attempts.
What happens to the DEU hardware once WinCC is accepted?
It has no live role left. Keep the unit and its drives powered off and labeled as the last copy of the legacy database and configuration for as long as the TI 545 system runs, because that archive can answer questions a rebuilt WinCC project cannot. Beyond that it is retired control equipment like any other.