T.8.6 Errors displayed when CANopen is used

Project data related error

Initialization errors

Error No.	Error Message	Description	Solution
000	No error	—	—
001	Illegal instruction(s)	One or more I/O instructions are not correct.	Check the setting value of the operands of I/O driver instruction and transfer the project file again.
002	Too many instructions	Check the number of I/O driver instruction.	Check the number of used I/O Driver Instructions and re-transfer the project.
003	Invalid driver ID	The driver/unit registry results in an error and has not been registered.	The project file may not have been transferred successfully. Transfer the project file again.
004	Repeat driver setting	The driver is registered twice.
005	Invalid level	The level of driver is not correct.
006	Invalid address	The driver information is not correct. The controller information is not correct.
007	Driver not registered	Driver is not registered.
008	PDO configuration is not correct.	PDO Settings Error Initialization error	Confirm PDO Settings and re-transfer the project.
009	The terminal type is not correct.	Invalid terminal type	The project file might not have been sent properly. Transfer the project file again.
010	Concise DCF not found	Concise DCF file is missing.
011	cDCF Mismatch	Invalid Concise DCF
012	Invalid firmware	Invalid firmware
013	Configuration could not download to CANopen Module	Configuration could not download to CANopen Module	Reset the Display. If the problem continues, please contact the Pro-face customer care center.
014	Invalid value	Error flag is set, but Error code is 0.	Reset the display. If the problem continues, please contact the Pro-face customer care center.

H/W-related errors

Hardware Error

Error Code

Error Message

Description

Solution

050

I/O board ID mismatch

Wrong board is inserted in the AGP or the board is broken

The AGP type might not be correct.

Check the AGP type and transfer the project file again.

051

CANopen unit initialization error

The initialization of the IO board fails

The project file may not have been transferred successfully.

Transfer the project file again.

If this does not resolve the problem, the module itself may be broken. Please contact the Pro-face customer care center.

Application related error

Master fatal error

Error Code	Error Message	Description	Solution
100	Bus off	No bus connection due to hardware error (for example, short circuit)	Confirm the connection state of the communication cable and check the baud rate settings of all the slaves to re-transfer the project. If this does not resolve the problem, the module itself may be broken. Please contact the Pro-face customer care center.
101	Fatal error: high priority receive queue overrun	High priority receive queue in master module got overrun	Review the network settings such as reducing PDOs.
102	Fatal error: high priority transmit queue overrun	High priority transmit queue in master module got overrun	Review the network settings such as reducing PDOs.
103	Fatal error: low priority receive queue overrun	Low priority receive queue in master module got overrun	Review the network settings such as extending the node monitoring interval.
104	Fatal error: low priority transmit queue overrun	Low priority transmit queue in master module got overrun
105	Fatal error: CAN controller overrun	The hardware CAN controller in the master module got overrun (1 or more messages are lost)	Review the network settings such as reducing PDOs and SDOs.
106	Fatal error: Duplicate Node ID	1 or more slaves in the network use the same node ID as the AGP (127)	Confirm whether node ID is duplicated and re-transfer the project.
107	Fatal error: Module has unsupported features	One or more slaves contain features that are not supported by CANopen Master unit.	Review the slave configuration.
108	Fatal error: invalid Concise DCF	Total network configuration is inconsistent.	Please download concise DCF again. If the problem is unresolved, check all the EDS files and review the network settings.
109	Fatal error: mandatory module configuration error	The Concise DCF file is inconsistent for one or more mandatory modules.	Check the EDS file and confirm whether it matches the hardware configuration.
110	Master fatal error	Fatal error occurred without explicit description	Reset the display.

Runtime Errors

Error Code	Error Message	Description	Solution
111	Invalid value in instruction	An operand value out of range was specified in the I/O driver instruction and the instruction was executed.	Specify an operand value within the range and execute the I/O driver instruction.
112	Mandatory module is missing	A module specified as a mandatory module has a failure.	Check that the mandatory module is connected properly and that the module is turned ON.
120	SDO Communication Error	Problem occurred during SDO communication (SDOR, SDOW or during initialization of the network) *Excluding error codes 140 to 148.	Check if SDO communication specification information is correct. If correct, check the network communication status or reset the network.
121	CANopen module timeout(Input)	Firmware does not update the Input process image within given time (4ms).	Firmware is not running normally. Reset the Display.
122	CANopen module timeout(output)	Firmware did not copy the process output image from DPRAM within given time(10ms)
123	CANopen module interface is busy	I/O firmware is not running SDO communication.

Non-fatal errors

Error Code	Error Message	Description	Solution
130	Incorrect PDO received	AGP received a PDO with too few data bytes	Confirm the EDS file.
131	SDO queue overrun	Overrun of the application specific SDO interface	Make SDO communication data size smaller.
132	Master alone	No other nodes are in the network.	Check if the slave is connected normally and the power supply is on.
140	SDO Protocol error	SDO server (slave) protocol error	Check the abort code. Check the object dictionary of the slave.
141	SDO error: low priority transmit queue problem	Overflow of sending queue with low priority (see error 104)	See error 104. Fatal error: Overrun of receiving queue with low priority
142	SDO error: no master functionality	Display unit is not set as a CANopen master. Therefore, SDO sending is not performed.	Please check the network settings. Check the network status in offline mode. Reset the display.
143	SDO error: object dictionary in use	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 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. Check whether the object exists in the object dictionary of the slave. Check whether the sub index exists.
145	SDO parameter error	SDO instruction parameter error	Check the abort code. Check the parameter of the SDO instruction. Check whether the object is read-only or write-only.
146	SDO transfer not allowed	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 error: stop mode	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 aborted	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	Inconsistent cDCF	Mismatch between configured slave and slave in the network	Check the EDS file and network settings to ensure that the node and EDS file are correct. (Node ID/EDS file correct) You can find the node ID of the slave in offline mode.
151	Unexpected state for one or more optional slaves	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	Mandatory slave does not match the network status (for example, network operational, slave preoperational)
153	One or more slaves are in error	Abnormal Slave	The project file might not have been sent properly. Transfer the project file again.
154	Inconsistent	Concise DCF mismatch for one or more slaves
155	Concise DCF mismatch for one or more slaves	Slave configuration and the object directory are mismatched.	Check whether correct EDS file is used. In offline mode, you can find the slave node ID.
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) You can find the node ID of the slave in offline mode.