GPD315/V7 Modbus RTU Technical Manual TM 4325
Page
34
Chapter 6
Error Codes and Troubleshooting
Communication Error
Once the data sent from the PLC is received the drive, the received data is checked for CRC,
parity, overrun, framing, and receiving buffer overflow. If all checked items pass, the data has
been received normally. A communication error (CE) is declared if any data item cannot be
received within 2 seconds.
The GPD315 drive will operate according to the setting of parameter n151 when a
communication error (CE) occurs. The settings of n151 are as follows:
Table 6-1 n151 Settings
n151 Setting Description
0 Coast to Stop (fault)
1 Ramp to Stop using n020 (fault)
2 Ramp to Stop using n022 (fault)
3 Operation continues (alarm)
Modbus Error Codes
If there is an error in the command message, an error code will be returned in the response
message. A fault response message is structured as follows:
Table 6-2 Modbus Error Message
Slave Address 02h
Function Code 83h
Error Code 02h
Lower 30h
CRC-16
Upper F1h
The following table indicates the fault code for the specific type of fault that occurred.
Table 6-3 Modbus Error Codes
Error Code Name Fault Content
01h Function Error Unregistered Function Code
02h Register No. Error Unregistered Register Number
03h No. of Errors Number of data > 16
21h Data Setting Error Upper/Lower limit exceeded in write-in data
22h Write-in Error Write-in is disabled for the register specified*
*Write-in would be disabled during the following conditions:
1. Parameters and/or Enter command was attempted to write-in during a run command
from the PLC.
2. Parameters and/or Enter command was attempted to write-in during UV occurence from
the PLC.
3. When “F04” fault occurred, and parameters other than the n01= 0,8,9,10,11, and 20
(initialize) were attempted to write-in from the PLC.
4. Parameters were attempted to write-in during data store from the PLC.
5. Read data was attempted to write-in from the PLC.
To Next Page
Loading...