304 Fault tracing
Warnings do not need to be reset; they stop showing when the cause of the
warning ceases. Warnings do not latch and the drive will continue to operate the
motor.
Faults latch inside the drive and cause the drive to trip, and the motor stops.
After the cause of a fault has been removed, the fault can be reset from a
) such as the control
panel, Drive composer PC tool, the digital inputs of the drive, or fieldbus.
Reseting the fault creates an event
. After the reset, the drive can
be restarted.
Note that some faults require a reboot of the control unit either by switching
the power off and on, or using parameter
– this is
mentioned in the fault listing wherever appropriate.
Pure events
In addition to warnings and faults, there are pure events that are only recorded
in the event log of the drive. The codes of these events are included in the
table on page (
).
Editable messages
For external events, the action (fault or warning), name and the message text
can be edited. To specify external events, use parameter
.
Warning/fault history
Event log
All indications are stored in the event log with a time stamp and other
information. The event log stores information on
• the last 8 fault recordings, that is, faults that tripped the drive or fault resets
• the last 10 warnings or pure events that occurred.
See section
Viewing warning/fault information
on page
Auxiliary codes
Some events generate an auxiliary code that often helps in pinpointing the
problem. On the control panel, the auxiliary code is stored as part of the details
of the event; in the Drive composer PC tool, the auxiliary code is shown in the
event listing.
Viewing warning/fault information
The drive is able to store a list of the active faults actually causing the drive to
trip at the present time. The drive also stores a list of faults and warnings that
have previously occurred.
Summary of Contents for ACQ80
Page 1: ... ABB DRIVES FOR WATER ACQ80 standard program control Firmware manual ...
Page 2: ... Related documents are listed on page 13 ...
Page 4: ......
Page 10: ...10 Table of contents ...
Page 32: ...32 Startup control with I O and ID run ...
Page 34: ...34 Using the control panel ...
Page 74: ...74 Program features ...
Page 78: ...78 Control macros ...
Page 380: ...380 Fieldbus control through a fieldbus adapter ...
Page 384: ...384 Parameterization with Drive Composer ...
Page 388: ...388 Parameterization with Automation builder drive manager ...