Replacing Siemens MMC103 with PC on SINUMERIK 840D Systems

Overview

The SINUMERIK 840D operator panel architecture separates the NCU (Numerical Control Unit) from the HMI station. On classic 840D systems, the HMI station is an MMC103 (or MMC102/MMC100) module that runs the HMI Advanced software stack on a Windows NT/2000/XP embedded base. When the MMC fails but the NCU remains healthy, the instinctive field question becomes: can I simply move the original hard disk into an off-the-shelf PC and run HMI Advanced there?

Direct, undocumented replacement of an MMC103 with a generic PC is not supported. Siemens requires the HMI Advanced host to provide specific firmware, BIOS extensions, license handling, and bus interface hardware. However, Siemens does offer an approved migration path through the IPC Retrofit for PCU kit (MLFB 6FC5210-0DA20-2AA1), which substitutes the legacy MMC/PCU with an industrial PC pre-imaged with HMI Advanced and an MPI/PROFIBUS interface. This reference documents the engineering constraints, supported topologies, and the verified procedure for the migration.

SINUMERIK 840D HMI Hardware Hierarchy

Three generations of HMI hosts appear in 840D installations:

When a failure occurs on an MMC103, the engineering decision is not whether to clone the disk, but which Siemens-qualified host replaces it. The CPU/NPU modules of the 840D NCU (e.g., NCU 561.x, NCU 571.x, NCU 572.x, NCU 573.x) communicate with the HMI host over MPI (187.5 kbaud default) or PROFIBUS (up to 12 Mbaud), and the host's link layer is part of the HMI boot contract.

Why a Direct MMC103 → Generic PC Swap Fails

Field engineers frequently attempt a disk-swap approach: pull the HDD from the failed MMC103, attach it to a desktop PC via USB-to-IDE/SATA adapter, and boot. This fails at one of the following layers:

1. BIOS layer: The MMC103 uses a Siemens custom BIOS that exposes the front-panel keys, the CF/HDD geometry, and a boot signature expected by the HMI loader. A generic PC BIOS does not match, so the Siemens loader either halts or skips the HMI partition.
2. Driver layer: The HMI Advanced installation references Siemens-specific device IDs for the integrated PROFIBUS/MPI chipset (CP 5611 A2 / CP 5613 / CP 5603). A generic PC lacks these cards; without the driver, the link to the NCU is absent and the HMI shows "NCU not reachable" or alarm 410000 / 410100 series.
3. License layer: HMI Advanced locks options (e.g., additional axes, HMI sl, ShopMill) against a Siemens license file stored on the HDD. The license is hardware-bound to the MMC103 mainboard via a registry/fingerprint. Cloning the disk to another mainboard voids the license and triggers alarm 8020 "HMI license missing or invalid".
4. Real-time layer: The HMI loader reserves a region of physical memory and configures APIC/IRQ vectors for the PROFIBUS interface that may conflict with the ACPI defaults on a consumer motherboard, producing blue screens during HMI start.
5. Power and panel layer: The MMC103 routes the OP 010 / OP 010C / OP 012 / OP 015 front-panel keys via a Siemens-proprietary front-panel connector. A generic PC has no such input, so even if the HMI boots, the keys are dead.

Siemens-Approved Path: IPC Retrofit for PCU

Siemens offers a turnkey kit for exactly this migration scenario: the IPC Retrofit for PCU, MLFB 6FC5210-0DA20-2AA1. The kit provides:

• An industrial PC (Simatic IPC) pre-imaged with Windows 10 IoT Enterprise LTSB and the matching HMI Advanced version.
• An integrated MPI/PROFIBUS interface (CP 5603-compatible) wired to the NCU bus.
• The legacy TCU/OP topology preserved by mapping the existing operator panel to the IPC.
• The license container migrated from the failed MMC103 to the IPC.

Per the Siemens service note, the retrofit is supported only on installations where the original HW (NCU firmware, PLC firmware, drive version, HMI version) is on a Siemens-supported matrix. Before deploying, the engineer should confirm the following prerequisites.

Contact Siemens Customer Service in your region (regional support line) with the MLFB 6FC5210-0DA20-2AA1 and the serial number of the existing NCU (e.g., T-H11001206) to validate eligibility before commissioning.

HMI Advanced Software Version Matrix

HMI Advanced is the human-machine interface program that runs on the host and renders the operator screens for the 840D. The following matrix is critical for a successful swap.

Per the SINUMERIK 810D/840D Upgrade Guide HMI Advanced V06.02.10, installation of HMI Advanced V06.02.10 requires a PCU 50 or MMC103 with at least 128 MB RAM and the pre-installed basic software version 06.01.04 or higher. The same document shows that earlier PCU platforms cannot run this version. Always cross-check the target HMI Advanced build against the host's basic software version before any image transfer.

Pre-Migration Engineering Checklist

Before the failed MMC103 is removed from the cabinet, capture the following:

1. HDD image. Use a sector-level tool (Ghost, Acronis True Image, or dd on Linux) to image the entire HDD, including the hidden HMI service partition and the MBR. The standard image size is approximately 4–8 GB depending on the basic SW build. Store the image on a separate medium — never rely on the same spindle for restoration.
2. MMC part and serial data. Capture the MMC103 MLFB and serial number from the front-panel rating plate. This is needed for license rehosting and for the Siemens service request.
3. Front-panel type. Identify whether the cabinet is wired for OP 010, OP 010C, OP 012, OP 015, or PCU 50.3 with TCU. The IPC retrofit must provide the same front-panel interface or a TCU.
4. Bus topology. Trace the MPI/PROFIBUS cable from the MMC103 to the NCU. Confirm whether the bus is MPI 187.5 kbaud (typical for legacy 840D) or PROFIBUS 1.5 Mbaud / 12 Mbaud (typical for 840D sl or upgraded NCU). The IPC retrofit's CP 5603 must be configured for the same bus profile.
5. Licenses. Run License Monitor on the running MMC103 (Start → SINUMERIK → License → License Monitor) and export the active options (e.g., HMI sl, 5-axis transformation, ShopMill/ShopTurn). The export is required to rehost the licenses onto the IPC.
6. PLC and NC data. Back up the PLC program (via STEP 7 / S7-PCT) and the NC data (series commissioning, tool data, R parameters, machine data). These are stored on the NCU side and are unaffected by the HMI host swap, but a backup is mandatory before opening the cabinet.
7. Drive and motor commissioning data. Record the drive version (SIMODRIVE 611, SINAMICS S120) and the motor encoder assignments. These are also on the NCU but must match the HMI version to avoid alarm cascades.

Step-by-Step Migration to the Siemens IPC Retrofit

The following procedure assumes that an IPC Retrofit for PCU kit (6FC5210-0DA20-2AA1) has been procured and delivered. Field engineers should not improvise substitutions.

Step 1 — Bench-Staging the IPC

1. Unpack the IPC, mount it in the cabinet (or on a bench rig for dry-run), and connect a keyboard, monitor, and the Siemens MPI/PROFIBUS cable to the CP 5603 port.
2. Power on and verify that the Siemens HMI Advanced boot loader appears within 60 s. The boot loader text is the strongest indication that the Siemens image is intact.
3. Confirm that the operating system reports the expected Windows version (Windows 10 IoT Enterprise LTSB on the latest kit). Avoid accepting any Microsoft updates that have not been validated by Siemens.

Step 2 — Restoring the Original HDD Image

1. Per the SINUMERIK 810D/840D Upgrade Instructions HMI Advanced V06.03.14, the HMI Advanced installation expects a directory C:\MMC102 (note: even when running on an MMC103, the directory name remains MMC102 by Siemens convention). If you intend to restore the original MMC103 HDD image, copy the HMI_Advanced directory from the source medium to C:\ and rename it MMC102.
2. Restore the sector image of the original MMC103 HDD to a matching HDD or SSD (Siemens-approved models only). If an SSD is used, verify that the controller supports the TRIM/NCQ profile expected by the HMI loader.
3. Apply license rehosting using the Siemens License Manager. The license server on the IPC must be pointed at the new hardware fingerprint before the migrated licenses become valid.

Step 3 — Wiring the Bus to the NCU

1. Power off the entire system. Disconnect the original MPI/PROFIBUS cable from the failed MMC103 at the NCU side.
2. Connect the IPC's CP 5603 PROFIBUS port to the NCU's X122 (MPI/PROFIBUS) connector. Use a Siemens PROFIBUS cable with the integrated terminating resistor at the IPC end (the CP 5603 has a switchable termination; enable it only if the IPC is the bus end node).
3. Verify the bus address. The default MPI address of the HMI host is 0; the NCU default is 0; the PLC default is 2. Do not duplicate addresses on the same segment.
4. Set the baud rate on the CP 5603 to match the NCU. For legacy 840D NCU 561/571, set 187.5 kbaud. For 840D sl or upgraded NCU 572/573, 1.5 Mbaud is typical. The CP 5603 must be re-parameterised through the Siemens PG/PC interface configuration tool.

Step 4 — First Power-Up and License Activation

1. Power on the NCU first. Wait for the NCU 7-segment display to reach the operating state (typically "6" with a steady dot for run).
2. Power on the IPC. Allow the HMI loader to complete (approximately 90 s on a clean boot).
3. When the HMI Advanced main screen appears, navigate to Start-up → License and verify that all expected options are present and dated. If any option is missing, the license rehosting step was incomplete.
4. Run Diagnostics → Bus Diagnostics to confirm the NCU is reachable over PROFIBUS/MPI. The expected result is the NCU identifier (e.g., NCU 573.4) with a green status indicator.

Step 5 — Program Restoration and Hand-Back

1. Restore the NC series commissioning file and any part programs from the backup. Verify tool data and zero offsets.
2. Restore the PLC program if the NCU's CF was also replaced; otherwise the existing PLC program is retained.
3. Execute a controlled reference run (axis-by-axis) at reduced rapid (10%) to confirm that all drives follow setpoints and that the HMI displays the correct actual positions.
4. Run a part program in single-block mode to verify end-to-end operation before releasing the machine to production.

Verification

The migration is verified by the following checks:

Troubleshooting Matrix

Alternate Paths When the Retrofit Kit Is Not Available

On rare occasions the IPC retrofit kit is unavailable and the machine must be brought back into service with a temporary host. The following constraints apply:

• A spare PCU 50 with a current HMI Advanced license can substitute for an MMC103. The PCU 50 boots the same basic SW family and can be re-imaged with the standard upgrade kit.
• A spare MMC103 from another retired 840D machine can be used, but the licenses must be transferred. Siemens treats license rehosting as a service operation.
• A generic PC with HMI Advanced installed is not a supported substitute and should not be used in production. If used temporarily for diagnostics only, the engineer must explicitly acknowledge the unsupported status and ensure that no NCU write operations are performed from the host that could destabilise the machine.

Safety Considerations

Migrating the HMI host while the machine is in production is not safe. The following safety rules apply:

1. Disconnect the main contactor, lock it out, and verify zero energy before opening the cabinet.
2. Ensure that the NCU's emergency-stop chain remains active throughout the swap. The E-stop is wired through the NCU and is independent of the HMI host, but verify that the safety relay (SIRIUS 3TK28 / 3SK1) is still powered before touching anything.
3. After hand-back, perform a controlled emergency-stop test from each operator panel button to confirm that the safety chain is intact.
4. Document the migration in the machine log, including the new HMI host MLFB, the new hardware fingerprint, and the date/time of the swap. This is required for auditability and for any subsequent warranty or service request.

Field-Proven Caveats

• The original MMC103 HDD must be imaged before the unit is decommissioned, even if the failure is suspected to be the mainboard only. Once the HDD spins down in a failed unit, the license fingerprint and the partition table can become unreadable.
• The Siemens HMI Advanced boot loader does not tolerate a disk controller change without a re-init. SSDs must be on the Siemens-approved list; consumer NVMe drives are not supported.
• The CP 5603 MPI/PROFIBUS interface on the IPC is not hot-swappable. Power off both the IPC and the NCU before plugging or unplugging the bus cable.
• Some earlier HMI Advanced versions (V06.02.x) display the directory name as MMC102 even when the host is an MMC103. This is a Siemens naming convention, not a bug.
• After a host swap, the NCU may report the new bus partner ID and ask for re-initialisation. Acknowledge the prompt only after confirming that the new bus address is correct; an incorrect acknowledgement can desynchronise the NCU's bus configuration from the drive configuration.

FAQ