Difference between revisions of "Error List AIO"
Jump to navigation
Jump to search
| Line 42: | Line 42: | ||
|- | |- | ||
!<div align="center">4</div> | !<div align="center">4</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">5</div> | ||
!<div align="center">x</div> | !<div align="center">x</div> | ||
!<div align="center">y</div> | !<div align="center">y</div> | ||
Revision as of 18:50, 6 January 2018
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 design
| Gateway Module FW version |
|---|
| NOT IN PRODUCTION V0.4 |
Error codes AIO
| Error Code | Parameter 1 | Parameter 2 | Parameter 3 | Description |
|---|---|---|---|---|
0
|
x
|
-
|
-
|
Output Error: Output module nr x (0-79) is not responding |
1
|
x
|
-
|
-
|
Input Error: Input module nr x (0-79) is not responding |
2
|
x
|
y
|
z
|
This error is triggered when the "default" of the switch statement is executed, parameters are for the development team only. |
3
|
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 |
4
|
x
|
y
|
z
|
UART Receiving error happened. x indicates in which state machine phase the error happened, y is the UART port (1-4). |
5
|
x
|
y
|
z
|
This error is triggered when state machine "UPDATE_TIME_DATE" has got blocked, parameters are for the development team only. |
Note:
- When "-" is found in the above tables, those return values can be ignored
