| LXM32M | 7 Diagnostics and troubleshooting | ||
| 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
| 
 | Excep- | Name | Description | 
| 
 | tion Code | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
| 
 | 01 | Illegal Function Code | The "Function Code" is unknown to the | 
| 
 | 
 | 
 | server. | 
| 
 | 
 | 
 | 
 | 
| 
 | 02 | Illegal Data Address | Depends on the Modbus request | 
| 
 | 
 | 
 | 
 | 
| 
 | 03 | Illegal Data Value | Depends on the Modbus request | 
| 
 | 
 | 
 | 
 | 
| 
 | 04 | Server Failure | The server was unable to properly termi- | 
| 
 | 
 | 
 | nate processing. | 
| 
 | 
 | 
 | 
 | 
| 
 | 05 | Acknowledge | The server has accepted the Modbus | 
| 
 | 
 | 
 | request. However, the execution takes a | 
| 
 | 
 | 
 | relatively long time. The server therefore | 
| 
 | 
 | 
 | only returns an acknowledgement con- | 
| 
 | 
 | 
 | firming receipt of the service request. | 
| 
 | 
 | 
 | 
 | 
| 
 | 06 | Server Busy | The server was unable to accept the | 
| 
 | 
 | 
 | Modbus request. It is the responsibility of | 
| 
 | 
 | 
 | the application on the client to determine | 
| 
 | 
 | 
 | whether and when to  | 
| 
 | 
 | 
 | 
 | 
| 
 | 0A | Gateway Problem | The gateway path is unavailable. | 
| 
 | 
 | 
 | 
 | 
| 
 | 0B | Gateway Problem | The targeted device does not respond. | 
| 
 | 
 | 
 | The gateway generates this error. | 
| 
 | 
 | 
 | 
 | 
0198441113843, V1.01, 01.2012
| 73 | 
