HELI G3 Series, Operation & Service Manual

Page: 72 / 110

69
237
ANALOG
INPUT
Cause:
This alarm occurs when the A/D conversion of the analog inputs returns frozen
values, on all the converted signals, for more than 400 ms. The goal of this
diagnosis is to detect a failure in the A/D converter or a problem in the code flow
that skips the refresh of the analog signal conversion.
Troubleshooting
If the problem occurs permanently it is necessary to replace the logic board.
239
CONTRO
LLER
MISM.
Cause
The software is not compatible with the hardware. Each controller produced is
“
signed
”
at the end of line test with a specific code mark saved in EEPROM
according to the customized Part Number. According with this
“
sign
”
, only the
customized firmware can be uploaded.
Troubleshooting
- Upload the correct firmware.
- Ask for assistance to a Zapi technician in order to verify that the firmware is
correct.
240
OUT
MISMAT
CH PU
Cause:
This is a safety related test. Supervisor
μ
C has detected that the Master
μ
C is
driving DC motor in a wrong way (not correspondent to the status of operator
commands).
Troubleshooting:
- Checks the correspondence of the parameters between Master and Supervisor
- Ask the assistance of a Zapi technician.
- If the problem is not solved it is necessary to replace the logic board.
241
SP
MISMAT
CH
PUMP
Cause:
This is a safety related test. The Master
μ
C has detected a Supervisor
μ
C wrong
set point for DC Pump motor.
Troubleshooting:
- Checks the correspondence of the parameters between Master and Supervisor
- Ask the assistance of a Zapi technician.
- If the problem is not solved it is necessary to replace the logic board.
242
SP
MISMAT
CH XX
Cause:
This is a safety related test. The master
μ
C has detected a supervisor
μ
C wrong
set point.
Troubleshooting:
- Check the matching of the parameters between master and supervisor.
- Ask for assistance to a Zapi technician.
- If the problem is not solved, replace the logic board.
248
NO CAN
MSG. XX
Cause
CANbus communication does not work properly. The hexadecimal value
“
XX
”
identifies the faulty node.
Troubleshooting
- Verify the CANbus network (external issue).
- Replace the logic board (internal issue).