Zapi ACE0 2mC, User Manual

Page: 116 / 155

Page – 116/155 AF6ZP0CA – COMBIAC0 & ACE0 2uC – User Manual
- Check the SR/HB input state through the TESTER function.
- Check the wirings.
- Check if there are failures in the microswitches.
- If the problem is not solved, replace the logic board.
HOME SENS.ERR XX
(MDI/LED code = 3)
Cause
The controller detected a difference between the estimated absolute
orientation of the rotor and the position of the index signal (ABI encoder).
It is caused by a wrong acquisition of the angle offset between the orientation
of the rotor and the index signal. The hexadecimal value “XX” facilitates Zapi
technicians debugging the problem.
Troubleshooting
Repeat the auto-teaching procedure.
HW FAULT EB. XX
(MDI/LED code = 34)
Cause:
At start-up, the hardware circuit dedicated to enable and disable the EB
driver (output
A4 ) is found to be faulty. The hexadecimal value “XX” facilitates
Zapi technicians debugging the problem.
Troubleshooting:
This type of fault is not related to external components. Replace the logic
board.
HW FAULT EV. XX
(MDI/LED code = 16)
Cause:
At start-up, the hardware circuit dedicated to enable and disable the EV
drivers is found to be faulty. The hexadecimal value “XX” facilitates Zapi
technicians debugging the problem.
Troubleshooting:
This type of fault is not related to external components. Replace the logic
board.
HW FAULT XX
(MDI/LED code = 32)
Cause
At start-up, some hardware circuit intended to enable and disable the power
bridge or the LC driver (output
A12 ) is found to be faulty. The hexadecimal
value “XX” facilitates Zapi technicians debugging the problem.
Troubleshooting
This type of fault is related to internal components. Replace the logic board.
INCORRECT START
(MDI/LED code = 79)
Cause:
Incorrect starting sequence. Possible reasons for this alarm are:
- A travel demand active at key-on.
- Man-presence sensor active at key on.
Troubleshooting:
- Check
wirings.
- Check microswitches for failures.