IMD SolutionComputing LibraryShop main store

Troubleshooting

Fix TwinCAT IPC staying in Config mode after power cycle

Operating systems on the plant floor Published 7 min read

Short answer

Set Auto Boot to Run mode under Boot Settings (Target) in SYSTEM > SETTINGS and activate the configuration. If the IPC still boots to Config mode, read the TwinCAT runtime build on the target itself: one reported 4024-to-4026 migration behaved this way until the runtime was returned to 4024.67.

On this page
  1. Why does the IPC return to Config mode after every power cycle?
  2. How do I set the IPC to start in Run mode automatically?
  3. Is Autostart boot project the same as Auto Boot Run mode?
  4. Do missing licenses hold the IPC in Config mode?
  5. Can the TwinCAT build keep the IPC in Config mode after migration?
  6. Should I disable the unused Ethernet adapter?
  7. How do I prove the fix survives a real power cycle?
  8. Questions asked

An industrial PC that runs your code after a manual activation but falls back to Config mode on every power cycle has a startup-chain fault, not a code fault. Fix the target's boot request first: in SYSTEM > SETTINGS, set Auto Boot under Boot Settings (Target) to Run mode and activate the configuration again. If that setting is already correct, the next suspect is the TwinCAT runtime build installed on the IPC itself, and a migration case closed only by a runtime change shows how far up the chain this fault can sit. Work it in order: boot setting, boot project, licenses, runtime build, adapters, one change per restart.

Why does the IPC return to Config mode after every power cycle? #

Because nothing in the saved configuration asks the target to enter Run mode at boot, or the runtime fails before that request completes: open SYSTEM, SETTINGS, and check that Boot Settings (Target) has Auto Boot set to Run mode.

A manual activation proves the configuration is valid, meaning the project builds, I/O comes up and code runs. It does not prove what the target will request on the next cold start, which is decided by the boot settings saved to the target. The blue LED is the quick verdict after a power cycle: still blue means the target sits in Config mode with nothing executing.

Split the fault into two families before touching hardware. A target that never requests Run mode has a boot-setting or saved-configuration fault. A target that requests Run mode and never arrives has a runtime fault, such as build, migration state or a startup failure. EtherCAT device faults can stop I/O inside Run mode; they do not by themselves explain a target that never leaves Config mode.

How do I set the IPC to start in Run mode automatically? #

Open SYSTEM, select the SETTINGS tab, set Auto Boot under Boot Settings (Target) to Run mode, activate the configuration, and restart the IPC, because this one setting decides the mode TwinCAT requests at boot.

  1. In the TwinCAT project connected to the target, open SYSTEM and select the SETTINGS tab.
  2. Under Boot Settings (Target), set Auto Boot to Run mode.
  3. Activate the configuration so the setting is written to the target.
  4. Restart the IPC in a planned window and read the state before touching anything else.

With this enabled, TwinCAT starts in Run mode as soon as the operating system is up and running, and no user has to be logged in. Auto Logon is a separate option that logs a user on automatically; it does not change the mode the target requests. On a newly commissioned IPC this is the first setting to rule out, because the symptom of manual activation working while a power cycle does not matches a target that was never set to request Run mode.

Is Autostart boot project the same as Auto Boot Run mode? #

No. Auto Boot under Boot Settings (Target) decides the mode TwinCAT requests at startup, while Autostart boot project decides whether the saved PLC project launches; a controller can sit in Run mode with nothing executing if only the first is set.

Most of the advice online covers the project side: enable Autostart boot project, tick the PLC's autostart checkbox, build and activate. Those steps govern the project, not the mode. Do them in this order:

  • Confirm the activated configuration is the one that must survive the restart, with the PLC project built and activated on the target.
  • Enable Autostart boot project for that project.
  • Keep the target boot setting for the mode and the project setting for the code; neither substitutes for the other.

The symptom split tells you which side failed. An IPC that never leaves Config mode has a mode or runtime problem. An IPC that enters Run mode but executes nothing has a boot-project problem, and a program shortcut in the startup folder <TwinCAT>\3.x\Target\StartUp only behaves as documented when TwinCAT itself starts in Run mode.

Do missing licenses hold the IPC in Config mode? #

Rarely the whole story, because the reported IPC held valid licenses for TC3 ADS, TC3 IO and TC3 PLC, read under About TwinCAT System, and still booted to Config mode, so licenses explain function-level faults, not the mode request.

Check the license view anyway. A missing license typically stops one function with a clear diagnostic while the controller stays in Run mode, such as I/O that will not start or a PLC that will not run. That is the opposite failure shape. A target stuck in Config mode before any function initializes is failing earlier than licensing, at the mode transition or in runtime startup.

Can the TwinCAT build keep the IPC in Config mode after migration? #

Yes. In one reported installation an IPC migrated from 4024 to 4026 started in Config mode after every power cycle even with Auto Boot set to Run mode, and the failure cleared only after the runtime was returned to 4024.67.

Read the build on the IPC, not on the engineering workstation. The number in the corner of the XAE shell, 4026.15 in that report, is the engineering shell, and the runtime installed on the target is versioned separately, which is the distinction behind resolving XAE and XAR version mismatches. The runtime side of that pair is the XAR, the component covered in running the TwinCAT XAR on a third-party industrial PC.

Migration is a documented procedure, and the installation manual walks a Migration tab with a Start Migration step for TwinCAT 3.1.4026, so a migrated installation is not broken by definition. The decision rule from the report: with both boot settings proven correct and the IPC still cold-booting to Config mode after a 4024-to-4026 migration, treat the target's runtime build as the suspect, record the exact build, and take it to vendor support before re-flashing anything.

Worked example, that reported installation: boot settings 2 of 2 correct (Auto Boot on Run mode, Autostart boot project enabled); licenses 3 of 3 valid (TC3 ADS, TC3 IO, TC3 PLC); OS Ethernet devices 2, of which 1 carried EtherCAT and 1 was disabled with no change; runtime builds tried 2 (4026, then 4024.67); clean automatic cold starts after the runtime change, 1 of 1. Six checks that did not move the symptom, 2 settings + 3 licenses + 1 adapter test, are what made the build the deciding variable.

Should I disable the unused Ethernet adapter? #

Only as an isolation test, never as the fix: the same symptom was reported when an RTE adapter sat in the configuration, but in that case the IPC listed two OS Ethernet devices and disabling the one not carrying EtherCAT changed nothing.

Run the test properly if you run it at all:

  • Record which interface carries EtherCAT and which configured devices depend on each interface before changing anything.
  • Disable one OS-level device, activate, restart, and compare the boot mode and diagnostics.
  • Never disable the interface that carries EtherCAT, and treat an ordinary OS adapter and a configured RTE device as different things.

If the result does not change, restore the intended network configuration and move to the runtime build. The reported case closed on the build, not the adapter.

How do I prove the fix survives a real power cycle? #

Restart once after each single change and verify three outcomes: the IPC enters Run mode with no manual activation, the intended PLC boot project executes, and the EtherCAT I/O reaches its operational state, and a successful manual activation proves none of the three.

  1. Make one change, whether boot setting, project setting, adapter or runtime build, and nothing else.
  2. Power-cycle in a planned window: a controller that boots to Config mode has stopped executing code, and the machine must be in a state where that is safe.
  3. Before activating anything by hand, capture the target build, the boot mode, the PLC state, the adapter assignments and the first diagnostic message, because manual activation overwrites the evidence.
  4. Close the fault only when all three outcomes hold on a cold start.

If any outcome fails, you now hold a recorded contrast between the failed boot and the working manual activation, which is exactly what vendor support asks for first.

Questions asked

Is auto login required for TwinCAT to start in Run mode?

No. Auto Logon only logs a user on automatically; the documentation describes choosing it so TwinCAT then executes the loaded and released boot projects without anyone at the keyboard. The mode request itself comes from Auto Boot, so enable Auto Logon for unattended project execution, not as a fix for Config mode.

Why does my engineering shell show 4026.15 if the target is the problem?

The number in the corner of the XAE shell, 4026.15 in the reported case, is the engineering shell running on your workstation, not the runtime installed on the IPC. The two are versioned separately, so record the build the target itself reports, and quote that number, not the shell's, when you open a support case.

Does updating to 4026.17 fix the Config mode problem?

That build was not tested in the reported case: the operator saw 4026.17 as the latest available at the time but restored 4024.67, which cleared the symptom. Treat the build choice as a decision made with the vendor's release information for your platform and a saved rollback image, not as a universal verdict against 4026.

What should I capture before contacting the vendor about this?

The exact runtime build on the IPC, the boot settings as activated, the boot project state, the adapter assignments, and the first diagnostic message from the failed boot, captured before any manual activation. Add what changed at each restart, one change per cold boot, because that sequence is what support uses to separate a setting fault from a build fault.

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

  • Selection guide

    Plant historian selection by scale and support needs

    Pick the tier first: a control-room or automation-vendor historian for one site's process trends, an enterprise platform only when several sites share one operational history, and a self-built time-series stack only when your team owns connectors, dashboards, backups and upgrades. Size by stored events per second — the sum of each tag group's tags times its stored events per second — times retention, never by tag count alone.

    Edge computing and IIoT

  • Troubleshooting

    Why OneDrive sync does not belong on a machine controller

    Run the OneDrive sync client on an office PC, not on the machine controller. A TwinCAT PC reserves cores for real time, and a sync client adds burst CPU, disk and network load on the Windows side that shows up as task exceeds and EtherCAT lost frames. Sync the SharePoint library to a separate PC and let the controller read and write the folder over a file share.

    Operating systems on the plant floor