Error codes on the console screen

Error codes of the EtherCAT platform are also output to the Console Screen.

../_images/WMX3_PLATFORM_FUNC_EC_ERRCODE_SERVERCONSOLE_image1.png

The error codes of the EtherCAT platform output to the console screen is divided into several categories.

  1. Error message

    In the message section, a message explaining the error code will be output.

  2. WMX3 internal error code of 4-byte

    The error code is 4-byte in hexadecimal, and the 0xFFFFFFFF area is divided into 5 areas.

    These may be represented by logical ORs. This means that errors will be output in all five areas at most.

    • Communication Error (0x0000000F)

    • Register Operation Error (0x000000F0)

    • MailBox, SDO, FoE Operation Error (0x0000FF00)

    • Slave Error (0x00FF0000)

    • Master Error (0xFF000000)

  3. Error codes defined by ETG

    The error code is displayed as 4-byte SDO Abort Codes or 2-byte AL Status Codes in hexadecimal.

    • SDO Abort Codes (Conforms to ETG.1000.6)

    • AL Status Codes (Conforms to ETG.1000.6)

For example, from the first error in the illustrated case, following information can be read.

  1. Error message

    WMX3 failured to change EtherCAT state machine of slave 0 from PreOP (0x02) to SafeOP (0x04).

  2. WMX3 internal error code of 4-byte

    The 4-byte WMX3 internal error code = 0x00090000 means [AL error occurred during state change].

  3. Error codes defined by ETG

    AL Status Codes = 0x001E means [SM configuration for input process data is invalid]. The SyncManager setting in the ENI file may be incorrect. The utility needs to generate the correct ENI file.

Communication Error (0x0000000F)

Error

Code (Decimal)

Code (Hex)

Description

Resolution

Invalid Parameter

1

0x00000001

This error occurs when an invalid parameter is passed to the send/receive function.

Please contact our technical support.

Initialization error

2

0x00000002

NIC driver initialization error.

Make sure that the NIC board is supported by the NIC driver, and that the Location key setting value in the RtxTcpIp.ini file is correct.

Frame allocation error

3

0x00000003

Failed to allocate memory to the frame.

Increase the amount of memory allocated to RTX in the RTX control panel.

Packet decode error

4

0x00000004

Packet could not be decoded.

Check the status of your network.

Transmission timeout

5

0x00000005

Packet could not be sent within the specified time.

Reduce the load on the NIC driver by changing the amount and cycle of cyclic communication or asynchronous communication. Or increase the communication priority in the RtxTcpIp.ini file.

Packet fetch timeout

6

0x00000006

Packet could not be received within the specified time.

Either packets have been lost or too many NIC drivers have been loaded. Remove the NICs that are not used for EtheCAT communication from the RtxTcpIp.ini file. Also, please check the network status.

Transmission error

7

0x00000007

Packet transmission error has occurred.

Make sure that the RtxTcpIp.ini file is properly configured.

Packet format error

8

0x00000008

Packet was discarded during packet transmission.

Check the network status and slaves.

Packet size error

9

0x00000009

Invalid packet size was detected.

Packet may have been discarded during transmission. Check the network status and the slave.

Not fetched packet is overwritten

10

0x0000000a

Received packet has been overwritten by a received packet of the next cycle.

The cycling process inside WMX3 may be taking too much time. Please reduce the amount of WMX3 processing.

NIC driver not found

11

0x0000000b

The NIC driver was not found in the correct location.

Verify that the NIC driver file exists in the specified location.

Register Operation Error(0x000000F0)

Error

Code (Decimal)

Code (Hex)

Description

Resolution

General register read/write error

16

0x00000010

Register read/write error.

Check the error message in the log console window.

Data size of register read/write is too large

32

0x00000020

The data size for read/write registers is too large.

Reduce the size of the data used to read/write registers.

Packet size of register read/write is too small

48

0x00000030

The size of the packet specified as a register read/write is too small.

Please contact our technical support.

Invalid EtherCAT packet index

64

0x00000040

Failed to retrieve packet index.

Multiple threads may be attempting to read/write registers simultaneously. It is not possible to import a unique packet index at a time. Please call the function again.

Invalid EtherCAT protocol type

80

0x00000050

Invalid EtherCAT protocol type was detected.

Please contact our technical support.

Invalid ethercat work out

96

0x00000060

Invalid EtherCAT job count was detected.

Packets may have been discarded during transmission. Please check the network status. It is also possible that the specified slave is not responding to register read/write commands. Check to see if the slave supports the command.

Register read/write packet transmission error

112

0x00000070

Failed to send register read/write packet.

Check for Communication Error (0x0000000F).

Invalid EtherCAT address mode

128

0x00000080

The EtherCAT packet contains an invalid EtherCAT address mode.

Please contact our technical support.

Invalid SyncManager or FMMU id

144

0x00000090

Invalid synchronization manager or FMMU ID was used.

Check the ENI file to see if a synchronization manager or FMMU has been specified.

Register read/write packet transmission timeout

160

0x000000a0

Transmission of read/write packets timed out.

Check for Communication Error (0x0000000F).

MailBox, SDO, FoE Operation Error(0x0000FF00)

Error

Code (Decimal)

Code (Hex)

Description

Resolution

General SII read/write error

256

0x00000100

SII read/write error.

Check the error message in the log console window.

SII is not idle

512

0x00000200

SII read or write failed because the SII is not in idle state.

Wait for a while, and then run the function again.

SII state clear error

768

0x00000300

SII status clear error.

Could not clear the SII status of the slave. The slave may not have responded to the SII status clear command.

SII set address error

1024

0x00000400

An error occurred when setting the address for SII read/write.

Make sure that the slave supports reading/writing of the specified SII address.

SII set size error

1280

0x00000500

An error occurred when setting the size for SII read/write.

Verify that the slave supports read/write of the specified SII size.

SII set command error

1536

0x00000600

An error occurs during setup of SII commands.

Please contact our technical support.

SII read error

1792

0x00000700

Could not read SII.

Check the message in the log console window.

SII write error

2048

0x00000800

Could not write SII.

Check the message in the log console window.

General Mailbox error

4096

0x00001000

This is a common error in mailboxes.

Check the message in the log console window.

Not exist Mailbox

4352

0x00001100

The mailbox does not exist.

Check the ENI file to make sure that the mailbox is configured correctly.

Wrong Mailbox type

4608

0x00001200

This is the wrong kind of mailbox.

Check the ENI file to make sure that the mailbox is configured correctly.

Mailbox polling timeout

4864

0x00001300

Timed out for polling mailboxes.

Verify if the slave is in an emergency state.

Mailbox frame prepare error

5120

0x00001400

Mailbox frame preparation error.

Please contact our technical support.

Mailbox transmission error

5376

0x00001500

Mailbox transfer error.

Examine the remaining error codes to determine the cause of the transfer error.

Mailbox responce is wrong

5632

0x00001600

Incorrect mailbox response.

Please contact our technical support.

Mailbox parameter is invalid

5888

0x00001700

Invalid parameter was passed to the MAILBOX function.

Please contact our technical support.

Mailbox is being used

6144

0x00001800

The mailbox is being used by another thread.

Another thread is using the mailbox. Please run the function again after a while.

Mailbox buffer size is too small

6400

0x00001900

Buffer size is less than required for MAILBOX processing.

Please contact our technical support.

Mailbox fragmentation

6656

0x00001a00

MAILBOX Fragmentation process failed.

Please contact our technical support.

Mailbox service error

6912

0x00001b00

MAILBOX service processing failed.

Please contact our technical support.

SDO wrong subindex

8192

0x00002000

Invalid sub-index for SDO.

Verify that the sub-index is supported by the slave.

SDO abort

8704

0x00002100

SDO has been cancelled.

Determine the cause of the error from the Abort code.

SDO is emergency state

8960

0x00002200

SDO is in a state of emergency.

The slave is currently in an emergency state and SDO operations are not allowed. First, release the emergency state, and then execute the function again.

Invalid SDO data size

9216

0x00002300

SDO data size is invalid.

Verify that the slave supports the specified SDO data size.

EoE set IP failed

9984

0x00002700

EOE IP address setting error.

Please make sure that the EOE IP address is set correctly and contact technical support.

AoE initialization failed

10752

0x00002a00

AOE initialization failure.

Please contact our technical support.

AoE R/W failed

11008

0x00002b00

AOE Read/Write failed.

Please contact our technical support.

FoE file open error

12288

0x00003000

FoE file access failed.

Make sure that the specified FoE file is in the correct location and is being used by another thread or process.

FoE wrong response

12544

0x00003100

Invalid response from FoE.

Capture the packets and check the response packets.

FoE error request

12800

0x00003200

The request from FoE is invalid.

Please contact our technical support.

FoE busy

13056

0x00003300

FoE is busy.

Another FoE process is in progress. Please execute the function again after the other FoE process is finished.

DC set cycle period error

16384

0x00004000

An error occurred while setting the DC (EtherCAT Distributed Clock) cycle.

Check the transfer error with another error code that appears. Also make sure that the slave supports DC.

DC set cycle period wrong response work count

16640

0x00004100

An invalid number of response jobs was detected while setting the DC (EtherCAT Distributed Clock) cycle.

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC set system time error

16896

0x00004200

Failed to set the DC (EtherCAT Distributed Clock) cycle.

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

Get DC system start time

17152

0x00004300

Could not get the system startup time of DC (EtherCAT Distributed Clock).

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC set time offset error

17408

0x00004400

Failed to set the offset of DC (EtherCAT Distributed Clock).

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC set start time error

17664

0x00004500

The start time of DC (EtherCAT Distributed Clock) could not be set.

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC calculate propagation delay error

17920

0x00004600

Failed to calculate propagation delay.

Check the message in the log console window.

DC set propagation delay error

18176

0x00004700

Failed to set the propagation delay time of DC (EtherCAT Distributed Clock).

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC latch time error

18432

0x00004800

Could not latch the DC (EtherCAT Distributed Clock) time.

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC get difference between cuurent time and next DC time error

18688

0x00004900

The difference between the current time and the next time of DC (EtherCAT Distributed Clock) could not be obtained.

Check for different error codes displayed in the log console. Also, check the network status. Also make sure that the slave supports DC.

DC ring root slave detect error

18944

0x00004a00

Could not find the root slave in the ring topology.

Check the error messages displayed in the log console. Also, check the connection and topology between the slaves.

DC ring port detect error

19200

0x00004b00

Could not detect the ring port of DC (EtherCAT Distributed Clock).

Check the error messages displayed in the log console. Also, check the connection and topology between the slaves.

DC propagation delay calculate related port error

19456

0x00004c00

The port status used to calculate the propagation delay time of DC (EtherCAT Distributed Clock) could not be obtained.

Check the error messages displayed in the log console. Also, check the connection and topology between the slaves.

DC propagation delay calculate related neighbor slave error

19712

0x00004d00

Could not find any nearby slaves.

Check the error messages displayed in the log console. Also, check the connection and topology between the slaves.

First DC slave is innaccessible

19968

0x00004e00

The first DC slave could not be accessed.

The first DC slave may have left the network for some reason. Please check the network.

DC slave is not generating sync signal

20224

0x00004f00

The DC slave is not generating a DC signal.

Check if the slave in question supports DC. Also, check if the synchronization mode specification in the ENI file is correct.

DC first dc slave is inaccessible

19968

0x00005000

The first DC (EtherCAT Distributed Clock) slave is no longer accessible.

Connect to the first DC (EtherCAT Distributed Clock) slave and try again.

Get DL state error

20736

0x00005100

Could not get DL status.

Check the error message displayed in the log console.

Not all linked port is opened

20992

0x00005200

Some of the connected ports are not open.

Verify that the connected ports are functioning properly.

Port open timeout

21248

0x00005300

The port was opened beyond the specified timeout.

Run the function again.

Scan network failed

21504

0x00005400

Failed to scan the network.

Check the error message displayed in the log console.

Apply new topology error

21760

0x00005500

The new topology could not be applied.

Check for another error code displayed in the log console.

Initialize new slaves error

22016

0x00005600

Could not initialize the new slave.

Check for another error code displayed in the log console.

Set port auto close error

22272

0x00005700

Failed to configure the port to close automatically.

Check for different error codes displayed in the log console. Check the error message displayed on the log console. Check the configuration and status of the slave.

Recalculate DC error

22528

0x00005800

DC (EtherCAT Distributed Clock) could not be recalculated.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Other port related error

24576

0x00006000

Other port association errors.

Check the error message displayed in the log console. Check the port status of the slave.

SyncManager config error

24832

0x00006100

The synchronization manager could not be configured.

Check for another error code displayed in the log console; check the ENI file to make sure sync Manager is configured correctly.

ENI file related error

25088

0x00006200

ENI file association error.

Make sure that the ENI file is placed in the correct location. Also, make sure that the ENI file is formatted correctly.

Serial channel initialization failed

28672

0x00007000

Serial Channel initialization failed.

Please make sure that the InitComBuffer/ComOutChnl/ComInChnl settings in ENI are correct and contact Technical Support.

Invalid serial channel data

28928

0x00007100

Invalid serial channel data.

Please make sure that the InitComBuffer/ComOutChnl/ComInChnl settings in ENI are correct and contact Technical Support.

Serial buffer space is not enough

29184

0x00007200

Serial buffer space is not enough.

Increase the buffer size with ENI’s InitComBuffer directive.

Serial buffer is empty

29440

0x00007300

Serial buffer is empty.

This is a internal error.

Serial buffer is too small

29696

0x00007400

Serial buffer is too small.

ComOutChnl/ComInChnl in ENI is incorrect. Please set the correct Pdo size.

Invalid serial buffer size

29952

0x00007500

Invalid serial buffer size.

Set the size of InitComBuffer in ENI to at least 1024.

Slave Error (0x00FF0000)

Error

Code (Decimal)

Code (Hex)

Description

Resolution

General slave error

65536

0x00010000

This is a common slave error.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Invalid parameter

131072

0x00020000

Incorrect parameters were passed to slave-related functions.

Please contact our technical support.

Get state error

196608

0x00030000

Could not get the status of the slave.

Check for another error code displayed in the log console.

Set state error

262144

0x00040000

Slave status could not be set.

Check for another error code displayed in the log console.

Get AL error code error

327680

0x00050000

Could not obtain the AL status of the slave.

Check for another error code displayed in the log console.

Not allowed AL state change

393216

0x00060000

AL state changes are not allowed.

Verify that the state change request is allowed.

Current state not match

458752

0x00070000

Does not match the current state.

Check the error message displayed in the log console.

State change timeout

524288

0x00080000

The state change timed out.

Examine the AL error code to find out why the state change failed.

AL error occurred during state change

589824

0x00090000

An AL error occurred during a state change.

Check the AL error code to see why the state change failed.

Slave initialization error

655360

0x000a0000

Slave initialization error.

Check for another error code displayed in the log console.

SyncManager initialization error

720896

0x000b0000

Sync manager initialization error.

Check for different error codes displayed in the log console. Check the error message displayed in the log console. check the Sync Manager configuration in the ENI file.

FMMU initialization error

786432

0x000c0000

FMMU initialization error.

Check the different error codes displayed in the log console. Check the error message displayed in the log console. check the FMMU configuration in the ENI file.

SDO download error

851968

0x000d0000

SDO download error.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Initialization by eni file error

917504

0x000e0000

Initialization error by ENI file.

Check the different error codes displayed in the log console. Check the error message displayed in the log console. check the setting of the ENI file.

Configuration error

983040

0x000f0000

Configuration error due to ENI file.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Slave is in a ring

1048576

0x00100000

The slave is in a ring topology.

Check the topology to see if the slave exists in the ring.

Slave is reverse connected

1114112

0x00110000

The slave is connected in the reverse direction.

Check the topology and make sure that the slaves are connected in the right direction

Slave is not connected

1179648

0x00120000

No slave is connected.

Verify that the slave is connected.

Can not reset eni file

1245184

0x00130000

Unable to reset the ENI file.

Check to see if another thread or process is running the ENI file.

Open eni file error

1310720

0x00140000

Unable to open ENI file.

Make sure that the ENI file is placed in the correct location. Make sure that another thread or process is executing the ENI file.

Get slave information error

1376256

0x00150000

Unable to acquire slave information.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Get Slave port information error

1441792

0x00160000

Unable to obtain the port information of the slave.

Check for different error codes displayed in the log console. Check the error message displayed in the log console. Verify that the slave supports the port-specific registers.Check to see if PacketLoss or PacketTime is occurring.

Serial data transmittion error

1507328

0x00170000

Transmission failed in Serial function.

Please contact our technical support.

Serial service error

1572864

0x00180000

Reception failed in Serial function.

Please contact our technical support.

PM mailbox is not ready

1638400

0x00190000

Mailbox in PM mode slave is in Not Ready state.

Internal error.

Master Error (0xFF000000)

Error

Code (Decimal)

Code (Hex)

Description

Resolution

General master error

16777216

0x01000000

This is a common master error.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Invalid Parameter

33554432

0x02000000

Invalid parameter was passed to the master related function.

Please contact our technical support.

State error

50331648

0x03000000

The master is in an invalid state.

Re-run the master.

Not any slaves detected

67108864

0x04000000

No slave detected.

Check the connection between the master and slave, then start communication again.

Initialize slave error

83886080

0x05000000

Failed to initialize the slave.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Initialize master error

100663296

0x06000000

Failed to initialize the master.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Slave state error

117440512

0x07000000

The slave state could not be changed to the specified state.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Not DC Slave

134217728

0x08000000

Communication was started in DC mode, but the DC slave could not be detected.

Turn off the DC mode. Or add a new DC slave to the network.

Reach max frame number

150994944

0x09000000

Reached the maximum number of frames it can support.

If you need to support more frames, please contact our technical support.

Reach max slave number

167772160

0x0a000000

Reached the maximum number of slaves it can support.

If you need to support more slaves, please contact our technical support.

DC initialization error

184549376

0x0b000000

DC initialization failed.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

Slave position error

201326592

0x0c000000

The slave is not in the specified location.

Make sure the position of the slave is correct.

Slave index error

218103808

0x0d000000

The slave is not in the specified index.

Verify that the slave index is correct.

Master calculate DC propagation delay error

234881024

0x0e000000

The master failed to calculate the DC propagation delay.

Check for different error codes displayed in the log console. Check the error message displayed in the log console.

DC packet decode error

251658240

0x0f000000

DC-related packets could not be decoded.

A DC-related packet may have been discarded during transmission. Please check the AL status code and packet loss count of the network.

Communication is stopped

268435456

0x10000000

Communication has stopped.

Execute the communication stop function, and then start communication again.

Master scan network failed

285212672

0x11000000

The master failed to scan the network.

Check for another error code displayed in the log console.

Master apply new topology failed

301989888

0x12000000

The master could not apply the new topology.

Check for another error code displayed in the log console.

Master initialize new slave failed

318767104

0x13000000

The master could not initialize the new slave.

Check for another error code displayed in the log console.

Open def file failed

335544320

0x14000000

The ec_network.def file could not be opened.

Make sure that the ec_network.def file exists in the specified location. Make sure that the ec_network.def file is being used by another thread or process.

Invalid user definition in def file

352321536

0x15000000

Invalid user definition exists in ec_network.def file.

Check the user definition list. Or, if the user definition is not needed, disable it.

Not all linked port are open

369098752

0x16000000

Some of the connected ports are not open.

Check for another error code displayed in the log console.

User defined slave not match

385875968

0x17000000

Does not match the slave defined by the user.

Check the actual slave connections and the user-defined slave connections.

One or more slaves are connected n reverse

402653184

0x18000000

One or more slaves are connected n reverse.

Check the connection order of the slaves.

PM data encoding error

419430400

0x19000000

Data encoding failed in PM mode.

Please contact our technical support.

PM data decoding error

436207616

0x1a000000

Data decoding failed in PM mode.

Please contact our technical support.

PM SDO download error

452984832

0x1b000000

SDO Download failed in PM mode.

Please contact our technical support.

Reached maximum size

469762048

0x1c000000

General Error. Maximum size reached.

Check function return value or other error information output to console screen.

Loading dll failed

486539264

0x1d000000

Loading dll failed.

Please contact our technical support.