Table of Contents
Advertisement
The EB driver (pin
A28
(A18)) is not able to drive the load. The device itself or its
driving circuit is damaged.
Troubleshooting:
This type of fault is not related to external components. Replace the logic board.
EB. DRIV.SHRT. (MDI/LED code = 40)
Cause:
The EB driver is shorted (pin
A28
(A18)).
The microcontroller detects a mismatch between the setpoint and the feedback at
the EB output.
Troubleshooting:
Check if there is a short or a low impedance path between the negative coil
terminal and -B.
Check if the voltage applied is in accordance with the settings of the EB-related
parameters (see paragraph 8.2.5).
If the problem is not solved, replace the controller.
EEPROM KO (MDI/LED code = 13)
Cause:
A HW or SW defect of the non-volatile embedded memory storing the controller
parameters. This alarm does not inhibit the machine operations, but it makes the
truck to work with the default values.
Troubleshooting:
Execute a CLEAR EEPROM procedure (refer to the Console manual). Switch the
key off and on to check the result. If the alarm occurs permanently, it is
necessary to replace the controller. If the alarm disappears, the previously stored
parameters will be replaced by the default parameters.
ED SPLIP MISMATCH (MDI/LED code = 7)
Cause
The control detects a mismatch between the expected slip and the evaluated
one. This diagnostic occurs only if ED COMPENSATION = TRUE.
ENCODER D.ERR XX (MDI/LED code = 3)
Cause:
This alarm occurs only when the controller is configured as PMSM and the
feedback sensor selected is the encoder. The A and B pulse sequence is not
correct. The hexadecimal value "XX" facilitates Zapi technicians debugging the
problem.
Troubleshooting:
Check the wirings.
If the motor direction is correct, swap A and B signals.
If the motor direction is not correct, swap two of the motor cables.
If the problem is not solved, contact a Zapi technician.
ENCODER ERROR XX
Cause:
The frequency supplied to the motor is above 40 Hz and the feedback from the
feedback sensor has a jump greater than value define by parameter DIAG.JUMP
SENS in few tens of millisecond (see paragraph 8.2.5)Special Adjustment. This
condition is related to an encoder failure.
AFNZPxxx– DUALACE2 NEW GENERATION – User Manual
Page 131/169
- Quick Links:
- Table of Contents
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
Need help?
Do you have a question about the DUALACE2 NEW GENERATION and is the answer not in the manual?
Questions and answers
Como comprobar el funcionamiento del controlador dualac2 sin display
You can check the operation of the Zapi DUALACE2 NEW GENERATION controller without a display using the following methods:
1. Zapi Smart Console – Connect the Zapi Smart Console to the CAN bus to access diagnostics and parameter settings.
2. PC CAN Console – Use the PC CAN Console software to monitor and adjust controller settings.
3. Self-Diagnosis Feature – The controller performs self-diagnosis, and faults can be displayed using Zapi tools.
4. Alarm History Log – Check the log of alarms to review past faults and system behavior.
5. TESTER Function – Use the TESTER function to monitor key operational readouts.
These methods allow you to diagnose and verify the controller’s operation without an external display.
This answer is automatically generated
A brumby electrical truck that has a zapi inv.dace2, records the failure 244 "Warning Slave It depends on the supervisor uc", and the alarm 248 "Mc is Opened, eb is applied". On the other hand, the LED does not turn on, but in the manual I did not find the LED code. I would like more certainty about whether the failure is from the controller and the LED code for this Zapi model.
Failure 244 "Warning Slave" depends on the supervisor microcontroller (µC). No specific effect or troubleshooting steps are provided in the available context.
Alarm 248 "MC is Opened, EB is Applied" indicates that the main contactor (MC) is open, and the electric brake (EB) is applied. This typically occurs during start-up, standby, or other system states.
The LED code for this model is not explicitly provided in the available context.
This answer is automatically generated