BECKHOFF CX9000/CX9010 Hardware Maintenance Guide

BECKHOFF CX9000/CX9010 Embedded PC: Complete Guide to On site Hardware Diagnosis and Maintenance

In the field of industrial automation, Beckhoff's CX9000 and CX9010 series embedded controllers are widely used in PLC and motion control tasks due to their compact design, fanless operation, and powerful Intel XScale technology. However, like all industrial hardware, field engineers inevitably encounter startup failures, bus errors, or the need to perform system recovery during the device lifecycle.

This document aims to provide engineers with an in-depth maintenance and troubleshooting manual for the CX9000/CX9010 hardware platform. The content is entirely based on official hardware documentation, focusing on practical operational scenarios, covering the entire process from DIP switch recovery function, precise interpretation of LED status lights, K-Bus diagnostic code analysis, to battery replacement and system image updates.

Hardware Initial State Recovery: The Four Major Functions of DIP Switches

When the system encounters serious errors, such as configuration file corruption or registry exceptions, conventional operations cannot solve them. At this point, the DIP switch located inside the battery compartment is crucial for performing hardware level recovery. The switch group is located in the battery compartment between the two Ethernet ports on the front of the device, and all switches are in the "OFF" (downward) state during normal operation.

Before performing any DIP switch operation, the CX90x0 system must be powered off. Use a small flat head screwdriver (recommended Beckhoff order number ZB8700) to carefully turn the switch. The following are the specific functions and application scenarios of the four independent switches:

Switch 1: Restore factory settings

Operation steps:

Turn DIP switch 1 to the "ON" position.

Power on the CX system again and wait for the system to fully start.

After system startup, the registry will be forcibly regenerated and restored to its default state.

Turn off the power, turn switch 1 back to the "OFF" position, and close the compartment cover.

Application scenario: Used when the system cannot start properly due to incorrect registry modifications or software configuration.

Switch 2: Output debugging information

Operation steps:

Turn DIP switch 2 to the "ON" position.

Connect a serial monitoring device (such as a terminal or printer) through the COM1 port, and set the communication parameters to 38400 baud rate, 8-bit data bits, no checksum, and 1-bit stop bit.

To power on the system, debugging information will be output in real-time to the monitoring device.

After the diagnosis is completed, power off and reset switch 2.

Application scenario: Used for deep analysis of the underlying hardware or boot loader status during the system startup process, to locate startup freeze issues.

Switch 3: Enter BootStrap mode (for image updates)

Operation steps: This operation is used for updating system images, and the detailed steps will be explained in Section 4 of this article. In short, turn switch 3 to "ON" and start, and the system will search for the mirror server through the network.

Application scenario: Used when the operating system files are damaged or when a complete reinstallation of the Windows CE system is required.

Switch 4: Force TwinCAT into "Configuration Mode"

Operation steps:

When the startup project of TwinCAT contains incorrect logic, causing the system to loop errors, turn DIP switch 4 to "ON".

Power on and restart the system. At this point, TwinCAT will not automatically run the wrong startup project, but will remain in 'Config Mode'.

Connect programming devices, correct PLC projects or change settings.

After completion, power off and reset switch 4.

Application scenario: Used to solve problems where the controller cannot connect properly or restarts frequently due to incorrect PLC startup projects.

State analysis without diagnostic tools: in-depth interpretation of LED indicator lights

When programming software is not connected, the LED indicator on the front panel of CX9000/CX9010 is the most intuitive basis for judging the health status of the system. The meaning of LED varies depending on whether the I/O system you are using is K-Bus (Bus Terminal Module) or E-Bus (EtherCAT Terminal Module).

2.1 For E-Bus version (EtherCAT terminal)

PWR (Power/System Status)

Red constantly on: TwinCAT is in STOP mode.

Green constantly on: TwinCAT is in RUN mode (normal automation operation state).

Blue constantly on: TwinCAT is in CONFIG mode.

Extinguish: The system is offline.

LAN 1 / LAN 2

Green: Indicates the link/activity status of the corresponding RJ45 port.

L/A (Link/Activity)

Flashing: Indicates data traffic on the E-Bus (EtherCAT bus).

HDD (or Flash Access)

Red: Indicates that the Compact Flash card is being read or written (if the module is configured).

2.2 For K-Bus version (bus terminal module)

This version has added a key 'K-Bus' LED for diagnosing terminal module buses. The meaning of its status is as follows:

Extinguished: K-Bus is not activated (possibly not connected to any bus terminals or with abnormal power supply).