Error Codes¶
Caution
For compatibility reasons, the error codes at output ERNO of the RCOM function blocks are not RCOM specific. To obtain the RCOM error code, 8000 hex has to be subtracted from the original value.
Various errors displayed by numbers can occur when using the RCOM Communication Module. The error number is indicated at output ERNO of the corresponding connection elements.
The errors can be divided into two groups: recoverable errors and fatal errors.
The recoverable errors include all errors which occur during transmission of telegrams (character losses, parity errors etc.). In some cases, the Communication Module attempts retransmission in case of transmission errors. The number of attempts can be specified via the parameter “Retransmissions” in the PLC configuration. Further information can be found in section Basic configuration of CM574-RCOM CM574-RCOM: Module Parameters
In case of recoverable errors, the “RUN” LED flashes cyclic. The LED turns into normal operation mode (“ON”) as soon as the error has been fixed.
Fatal errors
If fatal errors occur, the Communication Module terminates communication with the AC500 CPU and the RCOM partners. Fatal erros are indicated by the “ERR” LED.
A reset is required in order to reactivate the Communication Module, e.g. by switching it off and on again.
Table of error codes
The following table contains all possible error codes (hexadecimal and decimal), the error cause and the type of error (fatal or recoverable error).
| Error code | Cause | |
|---|---|---|
| (hex) | (dec) | |
| 0000 | 0 | No error |
| 0001 | 1 | CPU does not respond (possible cause: missing connection element or CPU stopped) |
| 1001 | 4097 | Event queue full |
| 2001 | 8193 | Initialization error: Incorrect address (parameter NODE) |
| 2002 | 8194 | Initialization error: Incorrect address (parameter NODE) |
| 2005 | 8197 | Initialization error: Incorrect parity |
| 2006 | 8198 | Initialization error: Incorrect duplex mode |
| 2007 | 8199 | Initialization error: Incorrect line stab. Time (TLS) |
| 2008 | 8200 | Initialization error: Incorrect carrier delay |
| 2009 | 8201 | Initialization error: Incorrect character timeout |
| 2010 | 8208 | Initialization error: Incorrect turnaround time |
| 2011 | 8209 | Initialization error: Incorrect retransmissions |
| 2012 | 8210 | Initialization error: Incorrect number of preambles |
| 2015 | 8213 | Initialization error: Incorrect type of modem |
| 2018 | 8216 | Initialization error: Incorrect debug level |
| 3001 | 12289 | No CTS during transmission |
| 3002 | 12290 | Timeout, no response telegram |
| 3003 | 12291 | Telegram error (incorrect length code) |
| 3004 | 12292 | Telegram error (incorrect checksum) |
| 3005 | 12293 | Incorrect slave responding |
| 3006 | 12294 | Telegram error (incorrect response code) |
| 4001 | 16385 | Service not known |
| 4002 | 16386 | Incorrect length entry (input LEN) |
| 4003 | 16387 | Incorrect length entry (input LEN) |
| 4004 | 16388 | Incorrect network number (currently unused) |
| 4005 | 16389 | Incorrect data set number (input ID) |
| 4006 | 16390 | Response telegram does not match service |
| 4007 | 16391 | Slave not normalized |
| 4008 | 16392 | Event queue blocked (not normalized) |
| 4010 | 16400 | Invalid time (connection element RCOM_CLOCK) |
| 4020 | 16416 | Slave responds: “application part not ready” (e.g. EN = FALSE) |
| 4030 | 16432 | Slave responds: “application part not ready” (e.g. EN = FALSE) |
| 5000 | 20480 | Communication Module not initialized (after reset) Remark: Requires restart of the AC500 PLC (abort and restart of the program |
| 6001 | 24577 | Telephone directory or setup data not found |
| 6002 | 24578 | Incorrect entry in telephone directory or setup data |
| 6003 | 24579 | No telephone modem planned |
| 6004 | 24580 | Modem not yet online (service started without RCOM_DIAL) |
| 6005 | 24581 | Modem already online (repeated RCOM_DIAL without RCOM_HANGUP) |
| FFFF | -1 | Internal error (fatal) |