Lenze ESVZAR0 RS-485 - Manual (Page 31)

29 CMVMB401C
Troubleshooting and fault elimination
11 Troubleshooting and Fault Elimination
11.1 Faults
Table 18 lists faults relating to Modbus communication. Refer to section 9.2.10, Present Fault, for a list of drive faults.
Table 18: Communication Faults
Display Status Cause Remedy
n Module to Drive communication
time out
Connection between drive and module is not
made.
Check cable and connection between module
and drive
n Network Time-out Fault Drive under NETWORK control and network
communications have been lost.
See parameters P425, P426
11.2 Troubleshooting
Table 19 lists common communication errors and suggests methods to verify and correct the problem.
Table 19: Communication Errors
Symptom Possible Cause Remedy
No communication from the drive Module is not initialized properly • Verify the module connection
• Check P400 and P402
Incorrect Modbus settings • Use P403 to reset Modbus parameters.
• Verify P410 and P411, P412
Improper wiring • Check wiring between the Modbus Network and
communication module.
• Ensure that terminal block is properly seated.
• Check connection between module and drive.
Modbus write commands are ignored or
return exceptions. “Network Enabled terminal is either open
or not configured. Configure one of the input terminals (P121, P122, or
P123) to “Network Enabled” function (selection 9)
and close the corresponding contact.
Drive stops without obvious reason Modbus message monitoring time-out
occurred. The timeout reaction is set to
STOP, Quick stop or Inhibit.. Modify the setting of time-out time (P425) or the
reaction to the time-out (P426).