Checklist
Qualifying a SINUMERIK 840D operator PC retrofit before you buy
Short answer
Do not order an 840D operator PC retrofit until you hold one written line from the vendor naming the HMI release and operating-system image released for your installed NC software version. The retrofit replaces only the operator-interface PC; the NC, PLC and drives stay. Back up everything, image the old disk, and gate acceptance on five clean production programs.
On this page
The go/no-go on a SINUMERIK 840D operator PC retrofit is one written line from the vendor naming the HMI software release and the operating-system image released for your installed NC software version. Without that line, order nothing. The package exists: Siemens released the PCU Retrofit for the 840D solution line in April 2020 around HMI Advanced, and the listing describes an industrial PC, the thin-client unit (TCU), HMI Advanced and, where a machine needs them, the NCU, the operator panel and further control modules. A published offer can coexist with a support organisation that has retired the older 810/840 generation, which is why the written release note, not the listing, decides the purchase. There is no public price to compare, so the written scope comes first.
What the retrofit replaces, and what it leaves running #
On an 840D the NC and the PLC run in the numerical control unit. The operator-interface computer — an MMC103-class MultiMedia Controller on the older machines, a PCU 50.3-class unit later — runs the HMI software, stores part programs and machine-builder screens, and talks to the NCU over a dedicated link. The retrofit replaces that computer only, with a current industrial PC such as a Simatic IPC 427D delivered with Windows 10. Decide at quoting stage whether your scope is PC-only or includes the NCU, operator panel and control modules; the installed options decide that, not preference. A PC-only scope leaves the NC software, the PLC program, the drives and the machine control panel exactly as built.
The one written line that decides the purchase #
Send your machine data to the regional sales channel and require written answers to four questions:
- Which HMI release ships with the package, and on which operating-system image is it released?
- Is that pairing released for your installed NC software version and machine generation — the version you recorded, not the family name?
- Which card or onboard port connects the PC to the NCU link?
- Who commissions the result, and what does their acceptance consist of?
If the reply cannot name the HMI release and its operating-system pairing, compatibility is unverified and the order is a no. A Windows 10 image is not qualification: HMI releases are tied to specific OS pairings, and a newer OS can drop the driver for the communication card. The discipline is the same as when you are verifying an obsolete HMI replacement before ordering — a part number or a catalogue listing proves nothing on its own.
Pre-order checklist #
- Record the NC software version, the HMI version and the full option list from the machine's version and service screens. Photograph the nameplates of the NCU and the old operator PC.
- Back up NC data, drive data and the PLC project, following the practice of backing up a PLC program the right way so the archive is complete rather than logic-only.
- Take the HMI-side archive and prove it reads back on another computer before you rely on it.
- Image the entire old disk, not just the archive file. Machine-builder screens, cycles and settings live in that file system and nowhere else. If no archive exists at all, start from replacing an old HMI when no project files exist before any hardware decision.
- Export the licence records and licence-media references for every installed option.
- Send all of the above with the four questions, and file the written answer.
- Compare the answer with the offered PC's datasheet: ports, slots, supply voltage, mounting depth. A form-factor mismatch with the existing enclosure forces a front-panel change and a new quote.
- Keep the old PC intact and bootable until the release gate below is passed.
Before anyone opens the operator panel cabinet: IEC 60204-1 requires machines to have a supply disconnecting device — open it, lock it off and prove the circuit dead before you disconnect the old PC or its link wiring.
What the checklist is protecting you from #
Retrofits on this class of control fail on versions and licences, not on PC hardware. A newer HMI against an older NC can connect yet show missing screens, refuse program transfer, or drop functions such as tool management and alarm texts, because the HMI-to-NC interface changes behaviour between software generations. A newer operating system can break the driver for the communication card and leave the HMI with no link at all. And HMI and option licences bind to hardware or licence media; replacing the PC invalidates the binding, so licences must be transferred or re-issued, or the new PC starts with a reduced function set.
Sizing the swap window: a worked example #
These times are illustrative for a mid-size machine; your numbers move with archive size and link type, so re-run the sum with your own estimates.
| Task | Time |
|---|---|
| NC, drive and PLC backup with read-back check | 30 min |
| Full disk image of the old operator PC | 45 min |
| Mount new PC, load the delivered image | 60 min |
| Restore HMI archive and settings | 45 min |
| Run the acceptance list | 60 min |
| Total | 240 min = 4 h 0 min |
The sum is 30 + 45 + 60 + 45 + 60 = 240 min, and 240 min × 1.5 = 360 min = 6 h. Decision: book six hours. If the window you can get is shorter than 1.5 × your own sum, do the backups only and reschedule the swap — never leave the machine stopped halfway between old and new.
Acceptance checks and the release gate #
- Power-up: the NC boots with the new PC connected, no communication alarm, live HMI start screen.
- Version screen: NC and HMI versions match the values recorded before the swap.
- Option screen: every option present before is licensed and no licence warning shows. One missing option stops the release; escalate it, do not work around it.
- Program transfer: copy one part program each way between PC and NC; the files must be byte-identical.
- Alarm texts: trigger a known PLC alarm; the correct text displays.
- Dry-run a production program with the feed override at zero, then run it at reduced feed.
- Release gate: five production programs and zero communication alarms. Only then does the old PC come out of service.
Who does the work #
Mounting the PC, loading the delivered image and restoring the HMI archive are in-house work for a maintenance team that holds the backups. The NC link configuration, the licence transfer and any change to PLC-HMI interface data need the vendor or a service company with 840D experience. If your regional support states the generation is out of support, the specialist work falls to that third party under its own stated warranty, and the machine builder's documentation becomes the authority for interface settings.
If the vendor will not commit #
No written pairing means no order. Two paths remain: a like-for-like replacement of the operator PC by a specialist, or moving the operator station to industrial panel PCs running PC-based HMI software that reaches the NCU over the network.
Questions asked
How long does an 840D operator PC retrofit take from enquiry to a running machine?
Weeks, not days, before anyone touches the machine: the written release confirmation and the package lead time set the pace, and you want both in hand before booking downtime. The on-machine work fits the window you sized from your own estimates. Plan a follow-up visit for the acceptance runs instead of stretching the first day.
What do we do if the vendor says our 840D generation is no longer supported?
Ask once more, in writing, for the last HMI release and operating-system pairing that was released for your exact NC software version, even if the package is no longer sold as new. If no such pairing exists, buy nothing new: a like-for-like replacement of the operator PC by a specialist, under a stated warranty, is the safer route, with the machine builder's documentation as the authority on interface settings.
Which backup saves us if the old PC dies mid-project?
The full disk image of the old operator PC. NC data, drive data and the PLC project can be reloaded from their archives and the HMI archive can be restored, but machine-builder screens, cycles and licence references that exist only on that disk cannot be recreated if it fails. Take the image before you order anything, not on swap day.
Do we keep the old operator PC after acceptance passes?
Yes. Label it with the machine number and the removal date and store it with its disk untouched. It is the last-known-good boot device if the new PC fails in the first months, and it holds the licence-media references if an option needs re-issuing. Wipe nothing until the new station has run a full production month.
Is a Windows 10 image on the new PC enough to run the old HMI?
No. An HMI release is validated for specific operating-system pairings, and a generic Windows image can lack the runtime components and the driver for the communication card that links the PC to the NCU. Accept only the vendor's delivered image for the stated pairing, and note in the project file which image you loaded.