Beckhoff EP23xx EtherCAT Box Selection Troubleshooting

Restore factory settings and firmware version recognition

6.1 Restore default parameters

Through TwinCAT's CoE online access, modules can be restored to delivery status with just one click:

Switch TwinCAT to Config mode.

Find object 1011:0 'Restore default parameters'.

Write 0x64616F6C (decimal 1684107116) in its sub index 1011:01.

For some early modules, the alternative value is 0x6C6F6164 (decimal 1819238756).

6.2 Hardware/firmware version identification

The D-number format on the side of the module is D: WWYYFFHH:

WW: Production Week

YY: Year

FF: firmware version (hexadecimal)

HH: Hardware version

For example, D: 29100201 represents production in the 29th week of 2010, firmware version 02, hardware version 01.

The new Beckhoff product also uses Data Matrix Code (BIC), which can be obtained by reading the CoE object 0x10E2:01 online through TwinCAT, where the unique traceability number starts with SBTN.

Typical Fault Case Analysis

Case 1: All outputs cannot be restored after a short circuit

Phenomenon: After a short circuit is caused by a misconnected output, all output lights of the module turn off, and even if the short circuit is repaired and powered on again, the output still does not work.

Reason: The module defaults to "global latch" mode (F800:01=False). After a short circuit occurs, all outputs are locked and cannot be reset by simply powering on.

Solution: Send a rising edge (from 0 to 1) to the Reset outputs variable of the process data through TwinCAT, or set F800:01=TRUE to automatic recovery mode.

Case 2: Output not turned off as expected after communication interruption

Phenomenon: After unplugging the EtherCAT cable, the output of a certain control brake still remains engaged, causing the vertical axis to slide down.

Reason: The security status of the channel is not activated (8000:n=False), and the module continues to maintain the last received output value.

Solution: Set the corresponding channel's 8000:0n to TRUE and 8001:0n to False, so that the output automatically shuts down after a network interruption.

Case 3: EP2338-2002 cutting offUpUp

Some outputs are still charged afterwards

Phenomenon: External safety relay disconnected UpUp

Power supply, but the solenoid valve connected to port X01 remains engaged.

Reason: The output driver of X01/X02 channels is driven by UsUs

Power supply, and UsUs

Still exists (unless separately cut off).

Solution: reallocate the load and connect the safety critical actuators to ports X03/X04 (via) UpUp Power supply), ensure safe shutdown and cut off at the same time. Or cut off simultaneously during design UsUs andUpUp.