Error List AIO

This page provides an overview of the error codes used in the Brain(+).

Versioning

Brain(+) FW version
NOT IN PRODUCTION V1.0.69 or higher

Error codes AIO

Type (byte)	Parameter A (byte)	Parameter B (word)	Parameter C (word)	Description
0	0	y	-	Output Error: Output module nr y (0-79) is not responding
0	1	y	z	Output Error: Double found while initialising output module, y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
0	2	y	z	Shutter Error: tried to switch output y ON while the paired output z was already ON, both outputs will be switched OFF
1	0	y	-	Input Error: Input module nr y (0-79) is not responding
1	1	y	z	Input Error: Double found while initialising input module, y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
1	2	y	-	Input Error: While requesting pulse counter information from input nr y, a communication error occurred (resulting in CRC error for example)
1	3	y	-	Input Error: While requesting pulse counter information from input nr y, the external module didn't respond
1	4	y	-	Input Error: No pulse counter information available for input nr y
2	0	y	-	Sensor Error: Sensor module nr y (0-15) is not responding
2	1	y	z	Sensor Error: Double found while initialising sensor module, y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
2	2	y	-	Sensor Error: Configured sensor y didn't update sensor value in the last 2 minutes
3	x	y	z	This error is triggered when the "default" of the switch statement is executed, parameters are for the development team only.
4	x	y	z	I2C error happened. x indicates in which state machine phase the error happened, y is the I2C port (1 or 2), z is the number of I2C errors
5	x	y	z	UART Receiving error happened. x indicates in which state machine phase the error happened, y is the UART port (1-4).
6	x	y	z	This error is triggered when state machine "UPDATE_TIME_DATE" has got blocked, parameters are for the development team only.
7	x	y	z	This error is triggered when state machine "IMMEDIATE_QUEUE" has got blocked, parameters are for the development team only.
8	x	y	z	This error is triggered when state machine "GROUP QUEUE" has got blocked, parameters are for the development team only.
9	x	y	z	This error is triggered when state machine "TIMER" has got blocked, parameters are for the development team only.
10	x	y	z	This error is triggered when state machine "EEPROM_ACTIVATE_STATE," has got blocked, parameters are for the development team only.
11	x	y	z	This error is triggered when state machine "PERFORM_EEPROM_ACTIVATE," has got blocked, parameters are for the development team only.
12	x	y	z	This error is triggered when state machine "CLI_PRINT," has got blocked, parameters are for the development team only.
13	x	y	z	This error is triggered when state machine "CAN_QUEUE," has got blocked, parameters are for the development team only.
14	x	y	z	This error is triggered when "MICRO CAN WATCHDOG RESET," has got blocked, parameters are for the development team only.
15	x	y	z	This error is triggered when "MICRO CAN WARM RESET," has got blocked, parameters are for the development team only.
16	x	y	z	This error is triggered when state machine "CAN" has got blocked, parameters are for the development team only.
17	x	y	z	This error is triggered when state machine "EXECUTE EVERY MINUTE" has got blocked, parameters are for the development team only.
18	x	y	z	This error is triggered when state machine "EXECUTE GROUP ACTION" has got blocked, parameters are for the development team only.
19	x	y	z	This error is triggered when "MISSING ENDIF" has got blocked, parameters are for the development team only.
20	x	y	z	This error is triggered when state machine "GROUP DELAY QUEUE" has got blocked, parameters are for the development team only.
21	x	y	z	This error is triggered when state machine "CAN TX QUEUE" has got blocked, parameters are for the development team only.
22	0	y	z	This error is triggered when API Instruction "SM" has set the wrong RS485 mode. y indicates the maximum possible mode (0->y), z is the requested mode.
23	0	y	0	This error is triggered when API Instruction "TW" has set the wrong time or date. y indicates if the wrong date (y=0) or the wrong time (y=1) has been set.
24	0	0	0	This error is triggered when API Instruction "BA" has the wrong length (length must be 6).
25	x	y	z	This error is triggered when a remote (x=="R" -> RS485 slave, x=="C" -> Micro CAN module) slave module is not responding on an eeprom read/write request. y.MSB=ID0, y.LSB=ID1, z.MSB=ID2, z.LSB=ID3
26	x	y	z	This error is triggered when a wrong (x=="R" -> RS485 slave, x=="C" -> Micro CAN module) slave module type is used. y.MSB=ID0, y.LSB=ID1, z.MSB=ID2, z.LSB=ID3
254	0	y	-	CRC ERROR: A received API instruction (RS232) has generated a CRC error and has not been interpreted, y.msb and y.lsb represents the instruction used.
254	10	y	-	PARAMETER ERROR: API Parameters send not in range to be an acceptable value, y.msb and y.lsb represents the instruction used.
254	11	-	-	PARAMETER ERROR: Factory reset cannot be executed because: The prepare instruction (BA254 2) has not been executed yet OR wrong parameters are used to initiate the factory reset

Note:

• When "-" is found in the above tables, those return values can be ignored
• Type is a byte value, Parameter A is a byte value, Parameter B is a word value, Parameter C is a word value