MWXNE MW2000 - Troubleshooting

27
Errer Code Error Meaning Reason Solution
Protection
buzz sound
Other power source
connected with the
output cables
Output mistakenly
connected to a live power
device
Check if there are other
power sources connected
to the output cable
Long-
medium-short
buzz
Output Short Circuit Output short circuit
Check the circuit and load
of the output
6 short buzz
Output Overcurrent
Output current is too large,
instantaneous protection.
Reduce the load 5 short buzz
Output Overload
Output current is higher
than the rated power, delay
protection.
Reduce the load 4 short buzz
Over-temperature
Protection
Over Temperature
Check the fan and reduce
the ambient temperature.
2 short buzz
Battery
Undervoltage
Battery input voltage too
low
Charge or replace the
battery
3 short buzz
Battery Overvoltage
Battery input voltage too
high
Check if the input power
source or power charger is
functioning properly.
3 short buzz
DC Bus Overvoltage DC bus voltage too high
Check the input power
source
7 short buzz
Parameter
Conguration Fault
Inverter requires a
restart after parameter
reconguration.
Restart the power
Sampling Circuit
Fault
Inverter performs self-check
during power-up: Standard
value for voltage static working
point when output current is
zero is 2.5V
Check the maintenance
current sampling circuit,
restart the power source.
DC Bus Voltage too
Low
1) The DC bus voltage is below
8V after startup.
2) DC bus voltage fails to reach
minimum operating voltage
after a period of time after
startup.
1) Check if the power tube
of the rear stage are short-
circuited.
2) Check the boost circuit
or DC bus components in
the front stage.
Data Memory Error Data memory writes too
frequently
Re-power on or replace the
chip
Data Read Error
1)The data memory is not
initialized during rst write
2)The data memory need to
restart after specication
change
Restart the power
Alarm before
protection
1).Over-temperature alarm: 1 buzz each 3 seconds
2).Over-load alarm: 1 buzz each 7 seconds
3).Over-voltage alarm: 1 buzz each 15 seconds
Troubleshooting