Zapi ACE3, User Manual

Page: 104 / 139

Page – 104/139 AFFZP0BB – ACE3 – User Manual
9.2.1 Troubleshooting of supervisor-uC alarms
1)
INPUT MISMATCH
Cause:
The supervisor microcontroller records different input values with respect to the
master microcontroller.
Troubleshooting:
- Compare the values read by master and slave through the TESTER
function.
- Ask for the assistance to a Zapi technician.
- If the problem is not solved, replace the logic board.
2)
W.SET. TG-EB
Cause:
Supervisor microcontroller has detected that the master microcontroller has
imposed a wrong setpoint for TG or EB output
Troubleshooting:
- Check the matching of the parameters between master and supervisor.
- Ask for the assistance of a Zapi technician.
- If the problem is not solved, replace the logic board.
3)
LOGIC FAILURE #1
Cause:
This fault is displayed when the controller detects an undervoltage condition at
the key input (A1).
Undervoltage threshold is 11V for 36/48V controllers and 30 V for 80V
controllers.
- Fault can be caused by a key input signal characterized by pulses below
the undervoltage threshold, possibly due to external loads like DC/DC
converters starting-up, relays or contactors during switching periods,
solenoids energizing or de-energizing. Consider to remove such loads.
- If no voltage transient is detected on the supply line and the alarm is
present every time the key switches on, the failure probably lies in the
controller hardware. Replace the logic board.
Troubleshooting (fault displayed during motor driving)
- If the alarm occurs during motor acceleration or when there is a
hydraulic-related request, check the battery charge, the battery health and
power-cable connections.
4)
LOGIC FAILURE #3
Cause
A hardware problem in the logic board due to high currents (overload). An
overcurrent condition is triggered even if the power bridge is not driven.
Troubleshooting
The failure lies in the controller hardware. Replace the controller.