Wesley BC-6200-8SA - Manual (Page 56)

Curtis 1268 Manual, Rev. D
50
MAINTENANCE
There are no user serviceable parts in the Curtis 1268 controller. No attempt
should be made to open, repair, or otherwise modify the controller. Doing
so may damage the controller and will void the warranty.
It is recommended that the controller be kept clean and dry and that its
diagnostics history file be checked and cleared periodically.
CLEANING
Periodically cleaning the controller exterior will help protect it against cor-
rosion and possible electrical control problems created by dirt, grime, and
chemicals that are part of the operating environment and that normally exist
in battery powered systems. When working around any battery powered
vehicle, proper safety precautions should be taken. These include, but are
not limited to: proper training, wearing eye protection, and avoiding loose
clothing and jewelry.
Use the following cleaning procedure for routine maintenance. Never use a
high pressure washer to clean the controller.
1. Remove power by disconnecting the battery.
2. Discharge the capacitors in the controller by connecting a load (such as
a contactor coil or a horn) across the controller’s B+ and B- terminals.
3. Remove any dirt or corrosion from the power and signal connector areas.
The controller should be wiped clean with a moist rag. Dry it before
reconnecting the battery.
4. Make sure the connections are tight. Refer to Section 2, page 7, for
maximum tightening torque specifications for the battery and motor
connections.
FAULT HISTORY
The programmer’s Faults menu can be used to access the controller’s fault his-
tory file. The programmer will read out all the faults that the controller has
experienced since the last time the fault history file was cleared. The faults may
be intermittent faults, faults caused by loose wires, or faults caused by operator
errors. Faults such as contactor faults may be the result of loose wires; contactor
wiring should be carefully checked. Faults such as HPD or overtemperature
may be caused by operator habits or by overloading.
After a problem has been diagnosed and corrected, it is a good idea to
clear the fault history file. This allows the controller to accumulate a new file
of faults. By checking the new fault history file at a later date, you can readily
determine whether the problem was indeed fixed.
7
☞
C A U T I O N
7 — MAINTENANCE