B&R X20 — CPU STOP/RESET & X2X Bus Faults

B&R · advanced · 30 min

A B&R X20 CPU that leaves its I/O dead is usually not in RUN — the X2X bus only runs when the CPU does. Learn to read the status LEDs, tell normal boot blinking from a fault, pull the real error from the Automation Studio Logger, and power-cycle correctly.

ℹ️ On a B&R X20, the X2X bus only communicates when the CPU is in RUN. A CPU stuck in STOP/RESET leaves every module uninitialised and the I/O dead. Read the status LEDs, but get the actual cause from the Automation Studio Logger, not guesswork.

The X2X bus needs the CPU in RUN

On a B&R X20 system the CPU drives the X2X Link backplane/bus to its I/O modules, and this is the key fact for most "all my I/O is dead" calls: the X2X bus requires the CPU to be in RUN mode to establish communication between the master (CPU) and the slaves (modules). A CPU sitting in STOP/RESET prevents normal module initialisation and bus communication — so the first question is always is the CPU actually running?

Normal boot vs a fault

Don't misread startup. During boot the CPU initialises the application, all bus systems and I/O modules, and several red blinking signals appear immediately after power-on — these are not errors. Give it time to complete boot before diagnosing. What is a problem is the CPU settling into a STOP/RESET state (I/O never comes alive) rather than reaching RUN.

Read the status LEDs, then the Logger

The X20 CPU shows RUN/ERROR status on its front LEDs — use them for a first read (running vs stopped vs error). But the actual fault lives in software: connect Automation Studio over Ethernet (X2X/service port), go to Service mode, and check the Diagnostic buffer / Logger for the fault codes. Read the entry, correct the fault condition it names (hardware init, memory, fieldbus, or the application), and then request the Run mode transition. The Logger is what turns "it won't run" into a named cause.

Power-cycle correctly

A sloppy power-cycle can itself cause odd states, because the CPU and X2X modules must come up in the right order. To power-cycle cleanly:

1. Disconnect all 24 VDC power to the CPU and X2X modules.
2. Wait ~60 seconds for complete discharge.
3. Reapply power to the X2X modules first, wait ~2 seconds.
4. Then apply power to the CPU.

This ensures the modules are ready when the CPU starts driving the bus.

Step-by-step

1. Is the CPU in RUN? If it's STOP/RESET, the X2X bus (and all I/O) won't run.
2. Just powered on? Let boot finish — early red blinks are normal, not faults.
3. Connect Automation Studio → Service mode → Diagnostic/Logger and read the fault code.
4. Correct the named cause (hardware, memory, fieldbus/X2X, or application), then request Run.
5. If needed, power-cycle in order: 24 V off → 60 s → X2X modules on → 2 s → CPU on.

Never do this

Don't just keep power-cycling an X20 that lands in STOP/RESET hoping it catches RUN — the Logger is telling you why it won't run. Read it, fix the named fault (often a fieldbus/X2X module or an application error), then transition to Run.