Big Joe EZ30, Operation, Maintenance, Repair Parts List

Page: 26 / 134

4-6 BL-EZ30-0815 - 07-28-2019
4-2.5. Diagnostic History
The handheld programmer can be used to access the
controller's diagnostic history file. When the program-
mer is connected to the unit, the error log file is auto-
matically uploaded into the handheld programmer.
To see the present status of the unit, use the Menu
Navigation Key (1,
Figure 4-2 ) to select:
Faults->System Faults.
To access this log, use the Menu Navigation Key to
select:
Faults->Fault History
The faults are shown as a code and descriptive text. If
there are multiple faults, you have to scroll through the
list using the Up and Down Buttons on the Menu Navi-
gation Key
The faults may be intermittent faults, faults caused by
loose wires, or faults caused by operator errors. Faults
such as HPD or over-temperature may be caused by
operator habits or by overloading.
After a problem has been diagnosed and corrected,
clearing the diagnostic history file is recommended.
This allows the controller to accumulate a new file of
faults. By checking the new diagnostic history file at a
later date, you can quickly determine whether the
problem has been completely fixed.
To clear the diagnostic history file, select:
Faults->Clear Fault History.
You will be asked to confirm your actions. Use the
"plus" arrow (+) for yes to clear the menu and the
"minus" arrow (-) (3) to cancel your selection and not
clear the Fault History.
4-2.6. Test the Fault Detection Circuitry
1. Put the vehicle up on blocks to get the drive wheel
off the ground.
2. Turn off the key switch (20, Figure 12-23 ) and
emergency disconnect (17).
3. Using an inline fuse holder fitted with a 10 amp
fuse and alligator clips, connect the controller's M
and B- terminals.
4. Turn on the emergency disconnect (17) the key
switch (20). Release the brake and apply the
throttle. The motor should not operate.
5. Leave the key switch on and remove the in-line
fuse wire. The vehicle status should continue to
remain off.
6. Cycle the key switch off and on. Release the
brake and apply the throttle. The vehicle should
now operate normally.
4-2.7. Diagnostics and Troubleshooting.
The motor controller provides diagnostics information
to assist in troubleshooting drive system problems.
The diagnostics information can be obtained in two
ways:
• Reading the appropriate display on the programmer
• Observing the fault codes issued by the panel
mounted Status LED.
4-2.7.1. LED Diagnostics
During normal operation with no faults present, the
Status LED is steady on. If the controller detects a fault
the Status LED flashes a fault identification code con-
tinuously until the fault is corrected.
NOTE: The Status LED can only indicate one fault at
a time. If multiple faults are detected, the
highest priority fault code flashes until it is
cleared.
With Fault Code Type parameter is set to 0, the status
LED uses the fault codes listed in
Table 4-2 . Six sin-
gle-digit codes are used: 2, 3, 5, 6, 7, and 9.
For suggestions about possible causes of the various
faults, refer to
Table 4-3 Troubleshooting Chart.
4-2.8. Programmer Diagnostics
With a programmer, diagnostics and troubleshooting is
more direct than with the LED alone. The programmer
presents complete diagnostic information in plain lan-
guage - no code to decipher. Faults are displayed in
the Diagnostic Menu, and the status of the controller
inputs/outputs is displayed in the Test Menu.
The following 4-step process is generally used for
diagnosing and troubleshooting an inoperative vehicle
using the programmer:
1. Visually inspect the vehicle for obvious problems:
2. Diagnose the problem:
3. Test the circuitry with the programmer:
4. Correct the problem.
Repeat the last three steps as necessary until the
vehicle is operational.
Refer to the Table 4-3 for suggestions covering a
wide range of possible faults.