Project data related error
Initialization error
Error Code |
Error Message |
Description |
Solution |
000 |
No error |
- |
- |
001 |
Illegal Instruction(s) |
I/O Driver Instruction Error |
Check the set value of operand for I/O Driver Instructions and re-transfer the project. |
002 |
Too many instructions |
Number of used I/O Driver Instructions is greater than 16 |
Check the number of used I/O Driver Instructions and re-transfer the project. |
003 |
Driver ID error |
The driver/unit results in an error while registering, and they have not been registered. |
The project file might not have been sent properly. Transfer the project file again. |
004 |
Repeat driver setting |
The driver is registered twice. |
|
005 |
Setting level value error |
The driver is not correct. |
|
006 |
Data obtaining address error |
The driver information is in correct. The controller information is not correct. |
|
007 |
Driver not registered |
Driver is not registered |
|
008 |
PDO Settings Error Initialization error |
PDO Settings Error Initialization error |
Confirm PDO Settings and re-transfer the project. |
009 |
Invalid terminal type |
Invalid terminal type |
The project file might not have been sent properly. Transfer the project file again. |
010 |
Concise DCF not found |
There is no concise DCF |
|
011 |
Invalid Concise DCF |
Invalid concise DCF |
|
012 |
F/W File Read Error |
Invalid firmware |
|
013 |
Inappropriate firmware |
Failure in downloading set value |
Reset the display. If the problem is unresolved, please contact your support center. |
014 |
Setting value error |
Error code is 0 when error flag is set |
Reset the display. If the problem is unresolved, please contact your support center. |
H/W related error
Hardware error
Error Code |
Error Message |
Description |
Solution |
050 |
I/O board ID different |
The connected I/O board is not correct. |
Display type may be different. Confirm the display type and transfer the project file again. |
051 |
CANopen unit initialization error |
The I/O board initialization fails. |
The project file might not have been sent properly. Transfer the project file again. If the problem is still not solved, there may be a problem with the hardware. Contact your support center. |
Application related error
Master fatal error
Error Code |
Error Message |
Description |
Solution |
100 |
Fatal error: Bus off |
Bus failure (such as noise failure), hardware failure, abnormal baud rate settings, etc. |
Confirm the connection state of the communication cable and check the baud rate settings of all the slaves to re-transfer the project. If the problem is still not solved, there may be a problem with the hardware. Contact your support center. |
101 |
Fatal error: high priority receive queue overrun |
Excessive amount of received data such as PDO, NMT, and SYNC. |
Review the network settings by decreasing PDO. |
102 |
Fatal error: high priority transmit queue overrun |
Excessive amount of sending data such as PDO, NMT and SYNC. |
|
103 |
Fatal error: low priority receive queue overrun |
Excessive amount of receiving data such as heartbeat, node guard, and SDO. |
Review the network settings by increasing node guard intervals. |
104 |
Fatal error: low priority transmit queue overrun |
Excessive amount of transmitting data such as heartbeat, node guard, and SDO. |
|
105 |
Fatal error: CAN controller overrun |
Data loss due to excessive amount of data such as PDO and SDO. |
Review the network settings by decreasing PDO and SDO. |
106 |
Fatal error: duplicate node ID detected |
More than two identical node IDs are used. |
Confirm whether node ID is duplicated and re-transfer the project. |
107 |
Unsupported slave error |
Unsupported slave exists |
Review the slave configuration. |
108 |
Fatal error: invalid Concise DCF |
Network configuration is wrong |
Please download concise DCF again. If the problem is unresolved, check all the EDS files and review the network settings. |
109 |
Mandatory slave error |
Concise DCF file of the mandatory slave is invalid |
Check the EDS file and confirm whether it matches the hardware configuration. |
110 |
Master fatal error |
Fatal error has occurred in CANopen master. |
Reset the display. |
Runtime error
Error Code |
Error Message |
Description |
Solution |
111 |
Invalid value in instruction |
An I/O driver instruction has run with an operand value that is out of range. |
Please run each I/O driver with values inside specified ranges. |
112 |
No mandatory slave |
There is a problem with the defined mandatory slave. |
Confirm whether the mandatory slave is correctly connected and that the power is on. |
120 |
SDO communication error |
Slave object information specified in SDO communication is invalid, or communication partner is unavailable for communication. *Excluding error codes 140 to 148. |
Confirm whether the specified information of the SDO communication is correct. If correct, confirm the communication state of the network or reset the network. |
121 |
CANopen module timeout (Input) |
I/O firmware is not updating input data. |
I/O firmware is not operating properly. Reset the display. |
122 |
CANopen module timeout (Output) |
I/O firmware does not update output data. |
|
123 |
CANopen module interface is busy |
I/O firmware is not running SDO communication. |
Non-fatal error
Error Code |
Error Message |
Description |
Solution |
130 |
Incorrect PDO received |
Invalid size for the received PDO |
Confirm the EDS file. |
131 |
SDO queue overrun |
Excessive SDO communication data size |
Make SDO communication data size smaller. |
132 |
Master alone |
Slave does not exist |
Confirm whether slave is correctly connected and that the power is on. |
140 |
SDO protocol error |
SDO server (slave) protocol error |
Check the abort code. |
141 |
SDO send overflow |
Overflow of sending queue with low priority (see error 104) |
See error 104. Fatal error: Overrun of receiving queue with low priority |
142 |
SDO master setting error |
Display unit is not set as a CANopen master. Therefore, SDO sending is not performed. |
Please check the network settings. |
143 |
SDO access error |
Object specified with the SDO instruction is accessed by another service via SDO. |
Check the network to see if the display unit is the only CANopen master. (multiple masters are not supported.) Check whether only one SDO instruction is executed at the same time. |
144 |
SDO receive timeout |
SDO request is not responded to within the SDO timeout period. |
Check the abort code. Check whether the node ID exists in the network. |
145 |
SDO operand error |
SDO instruction parameter error |
Check the abort code. Check the parameter of the SDO instruction. |
146 |
SDO master status error |
SDO transmission cannot be performed due to the status of the display unit. |
Check the status of the display unit with DGMT instruction or offline mode. |
147 |
SDO master status stopped |
SDO sending cannot be performed because the display unit is in the STOP mode or changed to the STOP mode during SDO transmission |
Change the display unit to RUN mode. |
148 |
SDO abort error |
SDO transmission was aborted by the SDO server (slave) |
Check the abort code. Check the status of the slave. |
Slave error
Error Code Error Message |
Error Message |
Description |
Solution |
150 |
Identity error |
The set slave is different from the connected slave. |
Check the EDS file and network settings to ensure that the node and EDS file are correct. (Node ID/EDS file correct) |
151 |
Optional slave error |
Incorrect configuration of the optional slave |
Confirm slave configuration in the network settings and re-transfer the project. |
152 |
Unexpected state for one or more mandatory slaves |
Mismatched state of the Mandatory slave and that of the network |
|
153 |
Abnormal Slave |
Abnormal Slave |
The project file might not have been sent properly. |
154 |
Inconsistent Concise DCF for one or more slaves |
CDCF is mismatched with the object dictionary of slave. |
|
155 |
Concise DCF mismatch for one or more slaves |
Slave configuration and the object directory are mismatched. |
Check whether correct EDS file is used. |
156 |
Identity error for one or more slaves |
One or multiple set slaves do not match the connected slave. |
Check the EDS file and network settings to ensure that the node and EDS file are correct. (Node ID/EDS file correct) |