Hitachi WL200 Series - Monitoring Trip Events, History, & Conditions; Trip History and Inverter Status

80
Monitoring Trip Events, History, & Conditions
Trip History and Inverter Status
We recommend that you first find the cause of the fault before clearing it. When a fault occurs,
the inverter stores the important performance data at the moment of the fault. To access the
data, use the monitor function (xxx) and select  details about the present fault. The
previous 5 faults are stored in  to . When a fault occurs, each error log shifts
- to -, and the latest error log is written in .
The following Monitor Menu map shows how to access the error logs. When fault(s) exist,
you can review their details by first selecting the proper function:  is the most recent,
and  is the oldest.
    
    


SET
ESC


Trip history 1 (Latest)
Error code
Hz
A
Hz
A
Hz
A
Hz
A
Hz
A
Hz
A
...
Trip history 6
    
.
.
    
.


    


     


    


    
.
Output frequency
Output current
DC bus voltage
Elapsed RUN time
Elapsed power-
ON time
Trip cause
Inverter status
at trip point
.
Note: Indicated inverter status could be
different from actual inverter behavior.
e.g. When PID operation or frequency given
by analog signal, although it seems constant
speed, acceleration and deceleration could
be repeated in very short cycle.
.
.
.
.
.
.
.
.
    
.
Power up or initial processing
Stop
Deceleration
Constant speed
Acceleration
0Hz command and RUN
Starting
DC braking
Overload restriction