How-to
Running TwinCAT XAR on a third-party industrial PC
Short answer
Do not clone a factory IPC image onto other hardware. Install a licensed Windows 10 IoT Enterprise LTSC edition, install the runtime fresh, and qualify the real-time Ethernet port, CPU priority and jitter on the actual machine. A successful boot proves nothing, and network hardware the runtime vendor did not sell you is a self-supported component.
On this page
- What the factory IPC image actually is
- The operating system routes that are supported
- Qualifying the real-time Ethernet port
- Giving the runtime priority over Windows
- Commissioning sequence on a third-party machine
- Proving the timing under real load
- Checking the OS support window for a machine planned to 2034
- The decision for each case
- Questions asked
Cloning the factory IPC image onto your own hardware is the wrong question, because you do not need that image. TwinCAT XAR installs on a Windows build you license and install yourself, and Windows 10 IoT Enterprise LTSC — the channel the factory machines run — is on the runtime's supported list. The qualification work that actually decides the build is the real-time Ethernet port, the CPU priority and the jitter measurement on the target machine, none of which a successful boot proves.
What the factory IPC image actually is #
The factory image is built and delivered for the vendor's own IPCs, applied with the Beckhoff Service Tool (BST), a purpose-made restore drive. It carries the operating system, the drivers and the real-time configuration tuned to that hardware: the runtime set as the top priority, Windows taking the remaining resources after it. Restored onto different storage, chipset and network controllers, it brings driver conflicts, an activation state that belongs to other hardware and a real-time configuration tuned for a machine you do not have — Windows tolerates hardware swaps badly. Even when it boots, the boot proves only that Windows started. It says nothing about whether the EtherCAT path and the real-time scheduling behave the way your machine will demand.
The operating system routes that are supported #
The runtime's system requirements list the target platform as PC architecture, x86 or x64, with Windows 10, the Windows 10 LTSB/LTSC editions and — from TwinCAT 3.1 Build 4024.68 / 4026.16 — Windows 11; TwinCAT/BSD and TwinCAT/Beckhoff RT Linux are the non-Windows routes. The factory IPCs themselves run Windows 10 IoT Enterprise LTSC: 2019 LTSC at version 1809 (build 17763), 2021 LTSC at version 21H2 (build 19044), with Windows 11 IoT Enterprise 2024 LTSC on current machines. Microsoft supports each LTSC release for ten years, which puts Windows 10 IoT Enterprise 2021 LTSC at 2032-01-13 and Windows 11 IoT Enterprise 2024 LTSC at 2034-10-10 on the factory operating-system overview.
For your own machine that collapses to one instruction: buy a Windows 10 IoT Enterprise 2021 LTSC license, install it clean, install the runtime build you need, and you are on the same OS channel as the factory controller. LTSC also answers the bloatware objection — the long-term servicing editions carry no consumer app churn and take only security and quality fixes — but validate what is installed anyway, because an edition name does not make a build clean by itself. For a Windows 11 route, treat TwinCAT 3.1 Build 4026.16 or later as the floor, since the system-requirements pages place Windows 11 support at Build 4024.68 and 4026.16.
| Route | OS edition | Documented support end | Runtime build note | Fits when |
|---|---|---|---|---|
| Windows 10 | Windows 10 IoT Enterprise 2021 LTSC (21H2, 19044) | 2032-01-13 | supported TwinCAT 3.1 builds | machines retired before 2032 |
| Windows 11 | Windows 11 IoT Enterprise 2024 LTSC | 2034-10-10 | Build 4024.68 / 4026.16 or later; 4026.16 is the safe floor | longer service lives |
| No Windows | TwinCAT/BSD | vendor-defined | runs without Windows; needs a named maintenance owner | teams that accept a non-Windows admin role |
Qualifying the real-time Ethernet port #
On the factory machines the real-time EtherCAT traffic rides the onboard Intel L219-LM controller, and the vendor supports the network hardware it sells. A network connection the vendor did not sell is a self-supported component: the driver, the timing and every fix belong to you. That makes the Ethernet controller a shortlist criterion, not an afterthought. Read each candidate's datasheet and name the onboard controller before anything else; when you choose the machine itself, start from a cabinet-rated industrial mini PC whose datasheet states its onboard Ethernet controller, and treat any add-in network card as unqualified until the timing test passes. In the runtime configuration, bind the EtherCAT adapter by MAC address, never by physical port position, and keep office and server traffic on a second port.
Giving the runtime priority over Windows #
The factory configuration gives XAR the top priority and Windows the remainder, and nothing in that arrangement is magic. Recreate it in the real-time settings of the runtime configuration on your machine: assign the runtime its dedicated core or cores, set its priority above every other task, and keep background software off those cores. Every service, agent and telemetry component you allow competes with the control loop for exactly those cycles, which is why the installed-software list is a production document. Build the machine clean, then check what is actually running and listening before it earns a production role.
Commissioning sequence on a third-party machine #
Work the sequence on the target machine itself, not on the engineering PC:
- Record the hardware identity: processor, board, storage, firmware version, and the model and MAC address of every Ethernet controller.
- Install the licensed OS edition from the supported list and patch it to current.
- Install the TwinCAT 3.1 runtime build for your route — for Windows 11, Build 4026.16 or later.
- Run the runtime's adapter scan and bind the EtherCAT adapter to the onboard controller by MAC address.
- Assign the real-time cores and priority in the runtime settings; Windows takes what remains.
- Wire the EtherCAT segment to that port and confirm the expected devices enumerate.
- Measure cycle time and jitter, idle and loaded, as described below.
- Document the build — OS edition, runtime build, adapter binding, core assignment, measured jitter — and repeat steps 4 and 7 after every driver, firmware or runtime update.
Proving the timing under real load #
A machine that boots and enumerates devices has passed an intermediate check, not qualification. Run the real-time measurement the runtime provides, record the worst-case jitter on an idle machine, then run it again with the full server-side workload active, because this build exists to carry both at once. Historian writes, database jobs and remote sessions are exactly the background load the priority settings have to survive. If the server-side role is a historian, size its host as its own decision — the plant historian selection by scale and support needs comparison walks that choice by scale and support burden. Keep engineering tools off the production runtime as well; a separate hypervisor host is the cleaner home for SCADA and PLC engineering VMs, and the Proxmox checklist for SCADA and PLC engineering VMs covers that host. A hypervisor shares its scheduler between guests, so a virtualized runtime is its own qualification with its own measurements.
One deadline outranks every jitter number: when the OS edition passes its support end date, a running production controller stops receiving security fixes. Plan the OS life to outlast the machine.
Checking the OS support window for a machine planned to 2034 #
Inputs:
- Commissioned in 2026 with an eight-year production duty, so the last production day is 2034-06-30. These two dates are the planning assumptions of the case.
- Windows 10 IoT Enterprise 2021 LTSC is supported to 2032-01-13, Windows 11 IoT Enterprise 2024 LTSC to 2034-10-10 — the dates on the factory operating-system overview.
- Windows 11 runtime support starts at TwinCAT 3.1 Build 4024.68 / 4026.16.
Rule: an OS edition qualifies for the machine only if its support end date falls after the machine's last production day, because past that date the runtime keeps running while the security fixes stop.
Arithmetic:
- Windows 10 IoT Enterprise 2021 LTSC: 2032-01-13 to 2034-06-30. Months uncovered = (2034 − 2032) × 12 + (6 − 1) = 24 + 5 = 29 months without security updates.
- Windows 11 IoT Enterprise 2024 LTSC: 2034-06-30 to 2034-10-10 = 31 + 31 + 30 + 10 = 102 days, just over three months of margin.
Result: 2021 LTSC fails the window; 2024 LTSC clears it by about three months.
Decision: if the machine's last production day falls after 2032-01-13, Windows 10 IoT Enterprise 2021 LTSC fails the window — build on Windows 11 IoT Enterprise 2024 LTSC with the runtime at Build 4026.16 or later, or carry a planned mid-life OS migration in the project. A machine retired before 2032-01-13 can run 2021 LTSC for its whole life.
The decision for each case #
- Bench testing programs ahead of production: install XAR directly on any x86/x64 Windows PC you already have. No image work, no cloning — this is the standard path for programs written on a bench machine and deployed later.
- Production machine retired before 2032-01-13: licensed Windows 10 IoT Enterprise 2021 LTSC, fresh runtime install, onboard Ethernet controller verified in the datasheet and the adapter scan, priority set, jitter measured under full server load. The network hardware and the whole qualification are yours.
- Production machine running past 2032-01-13: Windows 11 IoT Enterprise 2024 LTSC with Build 4026.16 or later, the same qualification sequence, or a planned mid-life OS migration.
- Nobody available to own the port, the priorities and the jitter record: stay with the factory-configured IPC, where that work is already done and supported. The wait for the vendor machine is part of what that support buys.
Questions asked
Does the TwinCAT engineering seat need the same real-time hardware?
No. The engineering environment (XAE) is a development tool that runs on an ordinary office PC alongside your usual engineering work. Only the runtime (XAR) executes the real-time control loop, so only the machine running XAR needs the port, priority and jitter qualification. Programs are written and compiled on the engineering PC and downloaded to the runtime, which is why a bench laptop keeps development moving while the production qualification happens on the target.
What is the Beckhoff Service Tool for, then?
The Beckhoff Service Tool (BST) is a purpose-made restore drive for reimaging and recovering the vendor's own IPCs. It restores an image built for that hardware family, with the drivers, real-time settings and priorities configured for it. Used on a different machine it brings driver conflicts and an OS installation whose activation and tuning belong to other hardware, so it is not a general Windows installer and it does not extend vendor support to your own PC.
Is the Intel L219-LM port a hard requirement for EtherCAT?
It is the onboard controller the factory IPCs use for the real-time port, which makes it a strong hint when you shortlist third-party boards, not a written standard. What actually decides is whether the runtime's adapter scan lists your controller, whether it binds cleanly, and whether the jitter measurement passes under real load. Other controllers can often be configured, but the result stays self-supported.
Can I install XAR on the Windows 10 Pro PC I already have?
A used desktop Windows installation often boots the runtime, but it carries consumer update behavior, store apps and services a production controller should not run, and its servicing channel is not the ten-year LTSC window. For a production build, install the licensed LTSC edition clean so the OS support horizon and the installed-software list are defined from day one, then run the full qualification sequence on that machine.