AFDZP0BA – VCM Zapi 2uC - User Manual
Page - 43/54
A) A real undervoltage situation happened. The alarm should disappear by
simply switching off and on again the key. The cause of the
undervoltage event has to be found on the application. For example: a
truck function requesting a very large battery current may decrease too
much the battery voltage.
B) Fault in the circuit which detects the undervoltage condition. The board
must be replaced.
3) WRONG
PARAMETER
Cause:
This is an alarm related to the throttle configuration.
Troubleshooting:
Check the parameters.
4) WRONG SLAVE VER
Cause:
Wrong software version on supervisor uC.
Troubleshooting:
Install the correct software version in the supervisor uC.
5) HM
MISMATCH
Cause:
Mismatch between VCM and traction regarding the Hour Meter .
Troubleshooting:
Check the parameter setting concerning the HM.
6)
BATTERY
LOW
Cause:
It occurs when the battery charge is calculated being less than or equal to
10% of the full charge and the BATTERY CHECK setting is other than 0
(refer to SET OPTION menu).
Troubleshooting:
Get the battery charged. If it doesn’t work, measure with a voltmeter the
battery voltage and compare it with the value in the BATTERY VOLTAGE
parameter. If they are different adjust the value of the ADJUST BATTERY
function.
7) EEPROM
KO
Cause:
Fault in the area of memory where the parameters are stored or problems
during the read/write operations of this memory. This alarm does not inhibit
machine operation but default parameters are used.
Troubleshooting:
If the fault continues when the key switch is re-cycled, replace the board. If
the fault disappears, the previously stored parameters will have been
replaced by the default parameters.
8) PARAM
RESTORE
Cause:
This warning appears when the controller restored the default values.
Troubleshooting:
If a CLEAR EEPROM was mode before the last keyon-recycle, this warning
just means that the EEPROM was correctly cleared. A travel demand or a
pump request cancel the alarm. If this alarm appears at keyon without any
CLEAR EEPROM request by the operator, there could be a problem inside
