S7-1500 Software Controller on IPC 127E: Compatibility and Errors

Problem Overview

The SIMATIC IPC 127E is a compact, fanless industrial box PC marketed as an IoT gateway/edge device, while the SIMATIC S7-1500 Software Controller (CPU 1505SP / 1507S / 1508S) is a PC-based soft-PLC runtime that requires a Siemens-approved IPC with the SIMATIC Hypervisor. Engineers frequently ask whether the IPC 127E can host the 1507S or 1508S because the apparent silicon is sufficient: an Intel Atom x5-E3940, 4 GB RAM, and a 64–128 GB SATA SSD. Field experience and the official entry ID 109976331 in the Siemens Support database confirm that the IPC 127E is not listed as a compatible host, and the controller typically fails to install with the alarm "Failure with creating CPU volume".

This reference consolidates the hardware and firmware requirements, the underlying hypervisor dependency, the two recurring fault scenarios, and the validated recovery path that engineers have used on the related IPC 227E.

Hardware Inventory of the IPC 127E

Software Controller Variants and Approvals Matrix

Why the IPC 127E Looks Compatible but Isn't

The IPC 127E superficially appears to meet the headline numbers: a quad-core 64-bit x86 CPU, 4 GB RAM, SATA SSD, and Intel i210/i211 NICs. Three structural reasons prevent it from running a Software Controller cleanly:

1. Hypervisor mismatch. The Software Controller is delivered as a VHDX that boots inside a Type-1 hypervisor partition. Siemens ships approved IPCs with a pre-configured, signed SIMATIC Hyper-V layer that exposes virtual PCIe slots for PROFINET IRT and hardware-accelerated timing. The IPC 127E ships with a generic Windows 10 IoT image and no SIMATIC hypervisor component.
2. PROFINET IRT capability. Even if you side-load a Windows 10 with the 1507S/1508S image, the standard i210/i211 NIC in the IPC 127E does not carry the Siemens PROFINET IRT firmware, so you lose the deterministic real-time channel and the CP 1625 / Intel i82574/i210 IRT-mode functionality.
3. Siemens support policy. The official support entry ID 109976331 states that installing/activating a virtual machine on the IPC while a Software Controller is already installed is not permitted, and that the hypervisor is designed for specific hardware. Field failures on non-listed hardware are explicitly excluded from Siemens support.

Root Cause of the "Failure with Creating CPU Volume" Error

This alarm is raised by the SIMATIC Software Controller installer (Setup.exe of the 1505SP/1507S/1508S image, V21.9 or later) when the virtual CPU volume – a hidden VHDX container holding the soft-PLC's firmware, retentive data, and project – cannot be created on the boot drive. The most frequent root causes in chronological order are:

On the IPC 127E specifically, the typical outcome is root cause #1: the stock firmware has the SIMATIC hypervisor components stripped, so the installer cannot create the protected partition and aborts with Failure with creating CPU volume. The installer does not distinguish this from a generic I/O error, which is why field engineers frequently mis-attribute the failure to disk space.

Root Cause of "No Accessible Device" in TIA Portal

When the Software Controller runtime does start (for example on an approved IPC 227E or IPC 227G), a second common failure is the TIA Portal message "No accessible device" in Online → Accessible nodes. The runtime is up, but the PG/PC cannot see it. The diagnostic tree is:

1. Network interface binding. The Software Controller binds only to the Intel NIC that is whitelisted in the TIA PC Station configuration (typically Intel I210 / I211, slot 1 on the approved IPCs). If TIA is bound to a different NIC (e.g. the second LAN port, a USB-Ethernet adapter, or a virtual Hyper-V switch) the controller is invisible.
2. PG/PC interface assignment. Set PG/PC Interface in the Windows Control Panel must point to S7ONLINE (TCP/IP) → <Intel NIC>. Selecting TCP/IP (Auto) frequently picks the wrong interface when multiple NICs are present.
3. Firewall and transient. Windows Defender Firewall on the IPC blocks UDP/TCP discovery ports 102, 34964, 34965, 34966 used by S7-PCT and TIA. Create inbound rules or temporarily disable the firewall for the first download.
4. Time skew. The Software Controller rejects downloads if the IPC time differs from TIA by more than 5 seconds; certificate validation fails silently. Synchronize the IPC against a domain controller or NTP server.
5. Configuration file not loaded. A first download requires the PC Station configuration (*.pcx) to be applied to the IPC, either via SIMATIC Automation Tool or by running SiemensAutomationTool.exe with the exported config from TIA → PC Station → Create PC station configuration file.

Validated Workaround: Command-Line Configuration File Download

On the IPC 227E (the documented path), engineers have successfully applied the PC Station configuration directly from the command line, bypassing the TIA Portal discovery dialog:

1. In TIA Portal, configure the PC Station with the correct Software Controller slot, the S7-1500 software CPU, and the PROFINET interface.
2. Export the PC Station: PC Station → Export Station to Configuration File → produces ConfigFile.pcx.
3. Copy ConfigFile.pcx and the corresponding .pck project to a USB stick or network share on the IPC.
4. On the IPC, open an elevated Command Prompt and run:

5. Verify the service SIMATIC S7-PCT Server is running (sc query S7PCT) and that CPU 1507S appears in the SIMATIC Manager's accessible nodes.

IPC 127E vs. IPC 227E vs. IPC 227G – Field Comparison

Approved Path: Migrate to IPC 227G (BX-39A Equivalent)

When the application truly needs a nanobox form factor, the documented substitute is the SIMATIC IPC 227G (MLFB 6AG4022-0AA21-...), which carries the SIMATIC Hyper-V out of the box, supports the 1505SP / 1507S / 1508S as of firmware V21.9, and ships with a usable PROFINET IRT interface. For tight cabinet installations, the related BX-39A platform shares the same firmware baseline.

Alternatives Outside the Siemens Line

Engineers who only need a deterministic soft-PLC in a 127E-class form factor have reported good results with the following platforms after replacing the Siemens image with their own runtime:

• Beckhoff C6015 / C6017 – Intel x86/IPC, TwinCAT 3 runtime, identical footprint and I/O driver support.
• Kontron KBox A-150 – Atom E3940-class, supports TwinCAT 3 and CODESYS SoftMotion.
• CODESYS Control RTE / Win on the stock IPC 127E (no Siemens hypervisor required) – acceptable when the application is pure soft-PLC logic and does not need PROFINET IRT or S7-1500 motion.

Verification Checklist After a Successful Install

1. Service SIMATIC S7-PCT and SIMATIC Software Controller both show Running in services.msc.
2. Task Manager → Performance → CPU shows the right-half partition "SIMATIC Software Controller" consuming a fixed share of one core.
3. TIA Portal Online → Accessible nodes lists the CPU 1507S or CPU 1508S with the configured IP.
4. PROFINET diagnosis: Online & Diagnostics → PROFINET interface → Port statistics shows no CRC or late errors after 15 minutes of bus traffic.
5. Retentive tags survive a 10-second power cycle: write a marker, pull the plug, restore power, and confirm the value via TIA online watch table.

Troubleshooting Matrix (Symptom → Action)

FAQ