Operating systems on the plant floor
Windows IoT, LTSC and Linux on the plant floor: imaging, patching, BIOS and drivers.
Latest articles
Troubleshooting
Why PI Network Manager fails before the SAN disk is ready
PI Network Manager fails because it starts before the SAN-backed E: volume with the PI home directory is mounted. The iSCSI initiator dependency orders startup but does not prove the volume is ready; make the target reconnect and the mount persistent, add delayed automatic startup as the buffer, and verify at the next controlled reboot. The post-failover data delay is unrelated to the dependency change.
Troubleshooting
When AOA Manager shows server stopped after install
Server Stopped in AOA Manager is a service state, not an install state: open services.msc and confirm AOANginx, AOANodeRed and AOAPython are running. A standalone Node-RED install proves nothing about them. On Windows 7 Embedded 32-bit, AOA 2.6 is outside its documented requirements, which start at 64-bit Windows 10 or 11 Professional and 16 GB of RAM.
Troubleshooting
Why an Industrial PC Pings an S7-1500 but Runtime Stays Disconnected
Ping proves the IP path only. When Runtime shows the S7-1500 disconnected with an unsafe-connection error, make the IE General interface, the Windows adapter and the Runtime connection resolve to the same NIC, make the station name and PROFINET device name match, then trust the certificate in both directions.
Troubleshooting
Fixing IRMQMessage FlexPendant Interface load error
The error names a missing controller system option, not a code fault: the virtual controller's system was built without FlexPendant Interface, so the RAPID module is rejected at load and the PC SDK receive path is never tested. Build the virtual system with the option (a backup of the real controller is the reliable source), then debug the IpcQueue exchange only after the module loads.
Troubleshooting
Fixing the fd_mask error when building an MQTT library
The fd_mask error that stops a third-party MQTT library build comes from the compiler installation's C headers, not from the MQTT source. In the confirmed Automation Studio 4.12 case, the definition in types.h had been commented out during an earlier duplicate-declaration fix and never restored; restoring the supplied definition fixed the build with no library changes.
Troubleshooting
Fix CoDeSys communication error 0 when ping succeeds
When ping, FTP and Telnet succeed but CoDeSys login returns Communication error (#0), the network is proven and the station is not: the documented minimum is the CPU, at least one I/O or communication module, and a K-bus termination module. Install the missing terminator, then verify the controller's Ethernet settings and that CoDeSys targets 192.168.1.20 on port 1200.
Troubleshooting
X550 driver install fails on Windows 10 IoT Enterprise
Most X550 driver failures on Windows 10 IoT Enterprise are package mismatches, not dead cards: the installer checks the OS build and the device hardware ID against the package's support list, and a build it does not list is rejected. Capture the exact installer error, the OS build number and the Device Manager hardware ID before choosing a package; the same card working in another PC proves only that PC's build and image accepted it.
Troubleshooting
When a PLC runtime installer fails on the controller OS
The installer fails because the controller OS, Windows Embedded Compact 7 on the CX5120, is not on the runtime vendor's supported list; there is no WEC7 build of the product. No retry, timeout change or repackaged file fixes that. Move the controller to an operating system both the runtime package and the controller manufacturer document, and protect the application and license before you image.
Troubleshooting
TwinCAT Visual Studio freezes when connected to an IPC target
The 5 to 10 second stalls in Visual Studio are ADS timeouts on the link between the engineering PC and the IPC, not real-time or CPU problems: pointing the target at the local system or pulling the cable clears them. Work link negotiation, hostname routes, competing adapters and the ADS TCP session on port 48898, then finish with static addresses and an IP-based route.
Comparison
TwinCAT on a third-party PC: license class and NIC checks
TwinCAT runs on third-party PCs, but licensing for such hardware is assigned the highest performance class, which raises license cost. Before moving the project: verify the exact Ethernet controller against the supported-network-controller list, and for motion or fast I/O validate the PC's clock and real-time behavior under load. If those checks fail, a Beckhoff IPC costs less overall.
How-to
Set up a PXE boot server for an industrial PC
Put dnsmasq on an isolated 192.168.0.0/24 segment as its only DHCP server, serve pxelinux.0 and syslinux.efi from the TFTP root, open UDP 67, 69 and 4011, and set the industrial PC's firmware to boot from the network first. A Debian netinst menu arriving over TFTP proves the full DHCP-to-TFTP chain without touching the plant DHCP server.
How-to
Running TwinCAT 3 in a Hyper-V VM on Windows 11
Yes, TwinCAT 3 runs in a Hyper-V VM on a Windows 11 host. Give the guest at least two virtual CPUs and isolate one core for the TwinCAT runtime, which Build 4026 requires, or install the TwinCAT 3 Usermode Runtime where real time is not needed. Keep the guest on a static IP address so the host ADS route survives restarts, and pass USB devices in through enhanced RDP redirection or a USB-over-IP service.