Zapi ACE3, Руководство пользователя

Страница: 95 / 139

AFFZP0BB – ACE3 – User Manual Page – 95/139
18)
VMN LOW
Cause 1
Start-up test. Before switching the LC on, the software checks the power bridge:
it turns on alternatively the high-side power MOSFETs and expects the phase
voltages increase toward the positive rail value. If one phase voltage is below
66% of the rail voltage, this alarm occurs.
Cause 2
Motor running test. When the motor is running, the power bridge is on and the
motor voltage feedback tested; if it is lower than expected value (a range of
values is considered), the controller enters in fault state.
Troubleshooting
- If the problem occurs at start up (the LC does not close at all), check:
o
motor internal connections (ohmic continuity);
o
motor power-cables connections;
o
if the motor connections are OK, the problem is inside the controller;
replace it.
- If the alarm occurs while the motor is running, check:
o
motor connections;
o
that the LC power contact closes properly, with a good contact;
o
if no problem is found, the problem is inside the controller. Replace it.
19)
VMN HIGH
Cause 1
Before switching the LC on, the software checks the power bridge: it turns on
alternatively the low-side power MOSFETs and expects the phase voltages
decrease down to -BATT. If the phase voltages are higher than 10% of the
nominal battery voltage, this alarm occurs.
Cause 2
This alarm may also occur when the start-up diagnosis has succeeded and so
the LC has been closed. In this condition, the phase voltages are expected to be
lower than half the battery voltage. If one of them is higher than that value, this
alarm occurs.
Troubleshooting
- If the problem occurs at start-up (the LC does not close), check:
o
motor internal connections (ohmic continuity);
o
motor power cables connections;
o
if the motor connections are OK, the problem is inside the controller.
Replace it.
- If the alarm occurs while the motor is running, check:
o
motor connections;
o
that the LC power contact closes properly, with a good contact;
o
if no problem is found, the problem is inside the controller. Replace it.