Page - 88/100 AE0ZP0EC - AC-0 SSL SENSORED - User Manual
11.1.9 No Blink Alarms
1) WRONG CONFIG
MDI-PRC Code = 1
- Cause: It occurs the first time a controller is switched on when the non
volatile eeprom memory is not initialized yet. Then it is
necessary to specify if the controller is AC-0 or AC-1 type (see
AC TYPE 0 in the hidden hardware setting Zapi menu). If the
alarm is present, by switching off the key the AC TYPE 0 setting
will be turned automatically On (and the controller is specified to
be an AC-0). The AC TYPE 0 setting can be changed only
when a WRONG CONFIG alarm is present. If it is not present it
is necessary to clear the eeprom memory in order the WRONG
CONFIG alarm occurs.
- Remedy: The AC TYPE 0 setting must be factory adjusted and so this
alarm never should happen when the controller is on the field.
So ask for the assistance of a Zapi technicians when this alarm
occurs.
2) WAITING FOR NODE
MDI-PRC Code = Null
- Cause: The controller expects to receive a message from a remote
module via CAN Bus. When this message is not received after
a time out this alarm occurs.
- Remedy: Check the communication via CAN between the controller and
the other modules.
3) CURRENT SENS KO
MDI-PRC Code = 94
- Cause: This alarm occurs when the procedure for the maximum current
set-up is in progress.
- Remedy: The maximum current set-up is factory adjusted and so this
alarm never should happen when the controller is on the field.
So ask for the assistance of a Zapi technicians when this alarm
occurs.
11.1.10 Thirty Two Blinks Alarms
1) BATTERY LOW
MDI-PRC Code = Local
- Cause: It occurs when the battery charge is calculated being less than
10% of the full charge and the BATTERY CHECK setting is
other than 0.
- Remedy: Get the battery charged.
2) WRONG SET BATT.
MDI-PRC Code = 93
- Cause: When the key is turned ON, the controller check the battery
voltage and verifies it is within a window around the nominal
value.
- Remedy: Replace the battery with a correct battery.
To Next Page
Loading...
Need help?
General
