IMD SolutionComputing LibraryShop main store

Comparison

TwinCAT on a third-party PC: license class and NIC checks

Operating systems on the plant floor Published 7 min read

Short answer

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.

On this page
  1. Platform level: the license follows the hardware class
  2. The EtherCAT port: check the controller, not the connector
  3. Clock quality: where motion splits the decision
  4. Screening an Intel I350 PC on TwinCAT 3.1 build 4026.17
  5. Moving the project without losing the configuration
  6. The decision, case by case
  7. Questions asked

TwinCAT is built to turn standard PC hardware into a real-time controller, including PCs Beckhoff did not build, so the third-party industrial PC sitting on your shelf is a legitimate target for this machine's project. The project transfer is the smallest part of the job. Three checks decide the migration: the platform level the licenses are priced at, which for a PC with no documented performance class lands at the top of the scale; whether the exact Ethernet controller is on the supported-network-controller list for your TwinCAT build; and whether the PC sustains real-time behavior for motion under load. The table below sets the third-party route against a Beckhoff IPC, and the worked example screens a concrete candidate.

Platform level: the license follows the hardware class #

TwinCAT 3 licenses are organized by platform level, and the documented levels correspond to the performance classes of Beckhoff's own PCs. From TwinCAT 3.1 build 4020.10 upward there are additional high-performance levels: 81 to 84 above level 80, and 91 to 94 above level 90, assigned by computing power. A PC from another manufacturer has no documented class and therefore no derived level. In practice the target registers at the top of the scale, and engineers who run TwinCAT on third-party PCs report that every license on such a machine is priced at the highest performance class.

That makes the license quote the first number to obtain, before any project work. Price the third-party PC's complete license set at the top platform level and set it against the Beckhoff IPC with its mapped level; the gap depends on how many runtime systems the project uses, so compare per project. The mechanics of getting the licenses onto the target are covered in Install licensed software on an industrial edge PC.

The EtherCAT port: check the controller, not the connector #

An Ethernet jack proves nothing. Not every port carries EtherCAT properly, which is why the manufacturer maintains a supported-network-controller list. The TwinCAT 3.1 list, last revised for build 4026.17, names supported Intel chips; the Intel I350 controller with PCI device ID 0x1533 is on it. TwinCAT 2.11 keeps its own list, which includes older controllers such as the Intel 82542 at device ID 0x1001. The published lists are dominated by Intel chips, which is why the search usually starts with Intel-based ports. Match the release line first, then the chipset and device ID.

In the engineering environment, the EtherCAT adapter dialog is where the configured network adapter is selected and checked; that adapter is the link between the computer and the EtherCAT bus, so the configured entry must be the physical port the cable lands on. Decision rule: a port whose controller is not on the list for your build is not a candidate. Fit a card whose controller is listed, or change the target.

Clock quality: where motion splits the decision #

Transport and timing are separate gates. A clean bus scan proves frames arrive; it says nothing about whether the PC holds timing over a shift. For motion axes or extremely high-speed I/O, engineers who run TwinCAT on third-party hardware report that a standard PC's internal clock can lack the accuracy the application needs, and that Beckhoff builds its IPCs with higher-grade clock hardware for this reason. Treat it as a question your machine answers: run the third-party PC through its operating modes under production load and watch the real-time diagnostics for missed cycles and frame errors across a full shift. Values that hold with margin pass the gate; values that wander send that machine to the Beckhoff IPC.

Screening an Intel I350 PC on TwinCAT 3.1 build 4026.17 #

Inputs, each with its source:

  • Machine: your Beckhoff panel PC driving I/O terminals through an EK1100 EtherCAT coupler; the example assumes PLC logic and digital I/O only, no motion axes. Confirm your terminal list before relying on that assumption.
  • Candidate PC: a third-party industrial PC whose onboard port runs on an Intel I350 controller, PCI device ID 0x1533 (device ID from the documented supported-controller entry).
  • Runtime: TwinCAT 3.1 build 4026.17, assumed as the installed build; it is the build the current controller-list revision documents.
  • Reference points: high-performance platform levels 81-84 and 91-94 exist above levels 80 and 90 from build 4020.10, and the supported-network-controller list revision for 4026.17 includes Intel I350 0x1533 (both from the manufacturer's licensing and controller documentation).

Rule in words: a third-party target qualifies only when its EtherCAT port's controller appears on the supported list for the installed build, and its licenses are generated at the top platform level that build supports.

Arithmetic:

  1. List match: Intel I350, device ID 0x1533 on the candidate PC equals Intel I350, device ID 0x1533 in list revision 4026.17, and the installed build is 4026.17 - exact match on release line and device ID, so the port is a supported EtherCAT adapter.
  2. Build comparison: 4026.17 is greater than 4020.10, so the runtime supports the high-performance levels; the third-party PC registers above level 90, in the 91-94 band, and every license for it is quoted at that top band.
  3. Timing gate: no motion axes in the assumed terminal list, so the clock question is open but not decisive; it still needs a loaded run before sign-off.

Result: the candidate passes the port gate outright, passes the license gate mechanically at the top band, and leaves one gate to measurement.

Decision: for this I/O-only machine, use the available PC when its top-band license total is lower than the Beckhoff IPC's total for the same license set. A motion axis in the terminal list, or a port off the list, ends the third-party route.

Moving the project without losing the configuration #

Separate the engineering project from the active configuration, and keep the old PC bootable until the new one passes its tests; it is the rollback path.

  1. Prepare the target's operating system first; the image decision has its own article, Choosing an operating system image for an industrial PC.
  2. Install the TwinCAT runtime and generate licenses for the new target at its platform level.
  3. Bind the EtherCAT adapter to the listed port and confirm the cable lands on that physical port and reaches the EK1100.
  4. Activate the configuration and scan the bus; the coupler and every configured terminal must report present.
  5. Run first starts with personnel clear and the machine's safety chain proven per its own safety design; a PC swap does not carry prior safety validation over with the project.
  6. If the target sits in Config mode after a power cycle, that is a known pattern with a documented fix, covered in Fix TwinCAT IPC staying in Config mode after power cycle.

Validate in stages afterwards: communication first (device states, terminal presence), then plausible I/O updates, then a full pass through the operating modes under load while watching real-time and EtherCAT diagnostics. Copying files is not configuration, and a successful startup is not a timing qualification.

The decision, case by case #

Decision factor Available third-party PC Beckhoff IPC
License platform level No documented class; registers at the top band, 91-94 above level 90 on build 4020.10 and later Level mapped to the documented PC performance class
EtherCAT port Valid only if the controller and device ID are on the list for your build Documented with the machine
Clock and timing Measured under load before any motion sign-off Higher-grade clock hardware
Work to get there License, port and timing checks plus staged validation Project and machine verification
Fitting case PLC with digital I/O, listed controller, top-band license total below the IPC alternative Motion or high-speed I/O, or a license quote that erases the saving

Commit per case:

  • The machine runs PLC logic and digital I/O, the port's controller is on the list for your build, and the top-band license total is lower than the Beckhoff total: use the available PC, validated in stages.
  • The project carries motion or extremely high-speed I/O: default to the Beckhoff IPC unless a loaded run proves the third-party PC's real-time values hold with margin.
  • The port's controller is not on the list: the third-party route stops here; fit a listed controller or take the IPC.
  • The top-band license total reaches or passes the IPC alternative: buy the IPC. If this is where your comparison lands, the like-for-like replacement for the failed panel PC is a current industrial panel PC.

Questions asked

Does the TwinCAT license from the old PC transfer to the new one?

No. Licenses are generated for a specific target system and platform level, so the new PC needs licenses generated for it at its own platform level - for a third-party PC, the top band. Copying project files or license files between PCs does not carry the entitlement, and the old license stays with the old hardware.

How do I read the device ID of the Ethernet controller in Windows?

In Device Manager, open the network adapter's Details tab and select Hardware Ids. The string shows VEN_ and DEV_ numbers; DEV_1533, for example, identifies an Intel I350 controller. Match the full vendor and device pair against the supported-network-controller list for your TwinCAT build before planning the cutover.

Can I add a network card instead of using the PC's onboard port?

Yes. The qualification applies to the controller that carries the EtherCAT frames, not to the PC as a whole. An add-in card whose chipset and device ID appear on the supported list for your build is as valid as an onboard port; bind the project to that card in the EtherCAT adapter dialog.

Does the EK1100 coupler need changes after the PC swap?

The coupler and terminals keep their identities on the EtherCAT bus; nothing is reconfigured on the coupler side. The work is on the PC: the adapter binding, the license, and the bus scan. After the swap, confirm the coupler reaches its expected state and every configured terminal reports present before enabling outputs.

Keep reading

  • How-to

    Running TwinCAT XAR on a third-party industrial PC

    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.

    Operating systems on the plant floor

  • 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.

    Operating systems on the plant floor

  • Selection guide

    Choosing an operating system image for an industrial PC

    Order the industrial PC with the vendor image closest to your runtime: Windows IoT Enterprise LTSC where the vendor documents it for your model, the vendor's qualified Linux for a Linux stack, or the BSD image if your code builds on FreeBSD. Bring-your-own images are the fallback for monitoring-class loads. Qualify your binaries on the exact model and image; support and real-time behavior are model-specific.

    Operating systems on the plant floor