|
| The MSTR Instruction |
|
|
|
|
|
|
| Hex Error Code | Meaning |
|
|
|
| 1001 | User has aborted the MSTR element. |
|
|
|
| 2001 | An unsupported operation type has been specified in the control block. |
|
|
|
| 2002 | One or more control block parameters has been changed while the |
|
| MSTR element is active (applies only to operations that take multiple |
|
| scans to complete). Control block parameters may be changed only |
|
| when the MSTR element is not active. |
|
|
|
| 2003 | Invalid value in the length field of the control block. |
|
|
|
| 2004 | Invalid value in the offset field of the control block. |
|
|
|
| 2005 | Invalid values in the length and offset fields of the control block. |
|
|
|
| 2006 | Invalid slave device data area. |
|
|
|
| 3000 | Generic Modbus fail code. |
|
|
|
| 30ss* | Modbus slave exception response. |
|
|
|
| 4001 | Inconsistent Modbus slave response. |
|
|
|
| F001 | Option Module not responding |
|
|
|
* The ss subfield in error code 30ss is shown in the following table.
ss Hex value | Meaning |
|
|
01 | Slave device does not support the requested operation. |
|
|
02 | Nonexistent slave device registers requested. |
|
|
03 | Invalid data value requested. |
|
|
04 |
|
|
|
05 | Slave has accepted |
|
|
06 | Function can’t be performed now; a |
| in effect. |
|
|
07 | Slave rejected |
|
|
An error on the TCP/IP Ethernet network itself may produce one of the following errors in the MSTR control block:
Hex Error Code | Meaning |
|
|
5004 | Interrupted system call. |
|
|
5005 | I/O error. |
|
|
5006 | No such address. |
|
|
5009 | The socket descriptor is invalid. |
|
|
500C | Not enough memory. |
|
|
500D | Permission denied. |
|
|
5011 | Entry exists. |
|
|
840 USE 115 00 Version 1.0 | 29 |
