Johnson Controls VS3-005-4-UL1-0 Quick Start Manual page 45

Table 52. Fault Codes and Descriptions, continued
Fault
Code Fault Name
65 Replace Fan
66 Safety Torque Off
67 Current Limit Control Warning
68 Over Voltage Control Warning
69 System Fault
70 System Fault
80 FieldBus Fault
81 FieldBus Fault
82 Bypass Overload
83 FieldBus Fault
84 FieldBus Fault
85 FieldBus Fault
86 FieldBus Fault
87 FieldBus Fault
88 FieldBus Fault
89 Under Voltage Stop
Default
Fault Type Fault Type
Configurable Warning
Fault
Fault
Fault
Configurable Fault
Configurable Fault
Fault
Configurable Fault
Configurable Fault
Configurable Fault
Configurable Fault
Configurable Fault
Configurable Fault
Fault
Variable Speed Drives Series III LIT-12012996—April 2018 www.johnsoncontrols.com
Appendix A—Fault and Warning Codes
Possible Cause
Fan life is less than 2 months
STO Triggered, STO input is open.
The output current has reached the current
limit value
The DC link voltage has reached its voltage
limit value
Thermistor SPI communication error.
MCU send wrong parameters to DSP.
Loss of communication with BACnet/IP, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place
Loss of communication with SA Bus, and the
fieldbus reference is the remote reference OR
the fieldbus control place is the remote
control place
Over load when motor is in bypass mode
Loss of communication with Modbus RTU, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place
Loss of communication with Modbus TCP, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place
Loss of communication with BACnet, and the
fieldbus reference is the remote reference OR
the fieldbus control place is the remote
control place, and the fault protection is not
"NO action"
Loss of communication with EtherNet/IP, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place, and the fault protection is not
"NO action"
Loss of communication with Profibus/
CANopen/DeviceNet master on Slot A, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place, and the fault protection is not
"NO action"
Loss of communication with Profibus/
CANopen/DeviceNet master on Slot B, and
the fieldbus reference is the remote reference
OR the fieldbus control place is the remote
control place, and the fault protection is not
"NO action"
The DC link voltage has reached the Drive
under voltage stop limit value.
Remedy
Check the fan, clean out any
contamination, contact distributor near you
for replacement fan.
Reset STO Trigger and verify wiring. Reset
fault after input is enabled.
Check the load
Set the acceleration time longer
Check the input voltage
Set the acceleration/deceleration time
longer
Check thermistor chip.
Restart the drive again. Should the fault
re-occur, contact the distributor near you.
Check RS-485 communication wiring.
Verify drive parameters are set correctly.
Check master programming to verify proper
addressing.
Check RS-485 communication wiring.
Verify drive parameters are set correctly.
Check master programming to verify proper
addressing.
Check motor connection situation
Check RS-485 communication wiring.
Verify drive parameters are set correctly.
Check master programming to verify proper
addressing.
Check Ethernet communication wiring.
Verify drive parameters are set correctly.
Check master programming to verify proper
addressing.
Check RS-485 communication wiring.
Verify drive parameters are set correctly.
Check BACnet master configuration
programming to verify proper addressing.
Check Ethernet communication wiring.
Verify drive parameters are set correctly.
Check EIP master configuration
programming to verify proper addressing.
Check Profibus/CANopen/DeviceNet
communication wiring. Verify drive
parameter are set correctly. Check
Profibus/CANopen/DeviceNet master
configuration programming to verify proper
addressing.
Check Profibus/CANopen/DeviceNet
communication wiring. Verify drive
parameter are set correctly. Check
Profibus/CANopen/DeviceNet master
configuration programming to verify proper
addressing.
Check the input voltage.
43