Error handling ► ET/MT-3x6, ET/MT-2x8 series error messages ► Error message format ► Error types
Error type is a shortcut of the error event meaning. The error event meaning may be driver dependent and therefore the following description covers only most general cases. To precise the error event identification use parts label and supplementary_data of the error message.
• | 136: Bus error - timeout of the bus |
• | 138: Checksum error - check sum error in the response telegram |
• | 139: Communication error - the response or request telegram was not received completely |
• | 140: No communication - no communication response |
• | 141: Address error - command in the application order or in the request telegram makes access to the memory that is not available |
• | 142: Command error - bad command in the application order or in the request telegram |
• | 143: Configuration error - error in the driver configuration |
• | 144: No memory - there is not enough available operating memory in the terminal |
• | 145: Synchronisation error - the order synchronisation failed |
• | 146: Telegram error - an regular error response received |
<< return
|