Difference between revisions of "Error List AIO"

From OpenMotics
Jump to navigation Jump to search
(Created page with "This page provides an overview of the error codes used in the All In One design. == Versioning == This document describes the Action Type Bytes available for the All In One...")
 
 
(48 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page provides an overview of the error codes used in the All In One design.  
+
This page provides an overview of the error codes used in the Brain(+).  
  
 
== Versioning ==
 
== Versioning ==
This document describes the Action Type Bytes available for the All In One design
+
 
 
{| class="wikitable"
 
{| class="wikitable"
!Gateway Module FW version
+
!Brain(+) FW version
 
|-
 
|-
|align="center"|NOT IN PRODUCTION V0.4
+
|align="center"|NOT IN PRODUCTION V1.0.69 or higher
 
|}
 
|}
  
== Action Type Bytes ==
+
== Error codes AIO ==
 
{| class="wikitable" width="100%"
 
{| class="wikitable" width="100%"
! width="5%"|Type
+
! width="5%"|Type (byte)
! width="5%"|Action
+
! width="5%"|Parameter A (byte)
! width="5%"|DeviceNr
+
! width="5%"|Parameter B (word)
! width="5%"|Extra parameter
+
! width="5%"|Parameter C (word)
 
!Description
 
!Description
 
|-
 
|-
 
!<div align="center">0</div>
 
!<div align="center">0</div>
 
!<div align="center">0</div>
 
!<div align="center">0</div>
!<div align="center">x</div>
+
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Output Error: Output module nr y (0-79) is not responding
 +
|-
 +
!<div align="center">0</div>
 +
!<div align="center">1</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|Output Error: Double found while initialising output module,  y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
 +
|-
 +
!<div align="center">0</div>
 +
!<div align="center">2</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|Shutter Error: tried to switch output y ON while the paired output z was already ON, both outputs will be switched OFF
 +
|-
 +
!<div align="center">1</div>
 +
!<div align="center">0</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Input Error: Input module nr y (0-79) is not responding
 +
|-
 +
!<div align="center">1</div>
 +
!<div align="center">1</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|Input Error: Double found while initialising input module,  y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
 +
|-
 +
!<div align="center">1</div>
 +
!<div align="center">2</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Input Error: While requesting pulse counter information from input nr y, a communication error occurred (resulting in CRC error for example)
 +
|-
 +
!<div align="center">1</div>
 +
!<div align="center">3</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Input Error: While requesting pulse counter information from input nr y, the external module didn't respond
 +
|-
 +
!<div align="center">1</div>
 +
!<div align="center">4</div>
 +
!<div align="center">y</div>
 
!<div align="center">-</div>
 
!<div align="center">-</div>
|OUTPUT: Output x (0-479) OFF
+
|Input Error: No pulse counter information available for input nr y
 
|-
 
|-
 +
!<div align="center">2</div>
 
!<div align="center">0</div>
 
!<div align="center">0</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Sensor Error: Sensor module nr y (0-15) is not responding
 +
|-
 +
!<div align="center">2</div>
 
!<div align="center">1</div>
 
!<div align="center">1</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|Sensor Error: Double found while initialising sensor module,  y.msb=ID0, y.lsb=ID1, z.msb=ID2, z.lsb=ID3
 +
|-
 +
!<div align="center">2</div>
 +
!<div align="center">2</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|Sensor Error: Configured sensor y didn't update sensor value in the last 2 minutes
 +
|-
 +
!<div align="center">3</div>
 
!<div align="center">x</div>
 
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when the "default" of the switch statement is executed, parameters are for the development team only.
 +
|-
 +
!<div align="center">4</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|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
 +
|-
 +
!<div align="center">5</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|UART Receiving error happened. x indicates in which state machine phase the error happened, y is the UART port (1-4).
 +
|-
 +
!<div align="center">6</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "UPDATE_TIME_DATE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">7</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "IMMEDIATE_QUEUE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">8</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "GROUP QUEUE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">9</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "TIMER" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">10</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "EEPROM_ACTIVATE_STATE," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">11</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "PERFORM_EEPROM_ACTIVATE," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">12</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "CLI_PRINT," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">13</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "CAN_QUEUE," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">14</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when "MICRO CAN WATCHDOG RESET," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">15</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when "MICRO CAN WARM RESET," has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">16</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "CAN" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">17</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "EXECUTE EVERY MINUTE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">18</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "EXECUTE GROUP ACTION" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">19</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when  "MISSING ENDIF" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">20</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "GROUP DELAY QUEUE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">21</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|This error is triggered when state machine "CAN TX QUEUE" has got blocked, parameters are for the development team only.
 +
|-
 +
!<div align="center">22</div>
 +
!<div align="center">0</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|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.
 +
|-
 +
!<div align="center">23</div>
 +
!<div align="center">0</div>
 +
!<div align="center">y</div>
 +
!<div align="center">0</div>
 +
|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.
 +
|-
 +
!<div align="center">24</div>
 +
!<div align="center">0</div>
 +
!<div align="center">0</div>
 +
!<div align="center">0</div>
 +
|This error is triggered when API Instruction "BA" has the wrong length (length must be 6).
 +
|-
 +
!<div align="center">25</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|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
 +
|-
 +
!<div align="center">26</div>
 +
!<div align="center">x</div>
 +
!<div align="center">y</div>
 +
!<div align="center">z</div>
 +
|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
 +
|-
 +
!<div align="center">254</div>
 +
!<div align="center">0</div>
 +
!<div align="center">y</div>
 +
!<div align="center">-</div>
 +
|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.
 +
|-
 +
!<div align="center">254</div>
 +
!<div align="center">10</div>
 +
!<div align="center">y</div>
 
!<div align="center">-</div>
 
!<div align="center">-</div>
|OUTPUT: Output x (0-479) ON with current dimmer & Timer
+
|PARAMETER ERROR: API Parameters send not in range to be an acceptable value, y.msb and y.lsb represents the instruction used.
 +
|-
 +
!<div align="center">254</div>
 +
!<div align="center">11</div>
 +
!<div align="center">-</div>
 +
!<div align="center">-</div>
 +
|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

Latest revision as of 18:35, 4 March 2022

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