Wesley BC-620-4CA - Manual (Page 124)

120 Curtis 1234/36/38 Manual,
OS
11
9 — MAINTENANCE
9
MAINTENANCE
There are no user serviceable parts in Curtis 1234/36/38 controllers. 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 and connections be kept clean and
dry and that the controller’s fault history file be checked and cleared periodi-
cally.
CLEANING
Periodically cleaning the controller exterior will help protect it against corrosion
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 system, 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) 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 5,
for maximum tightening torque specifications for the battery
and motor connections.
FAULT HISTORY
The 1311 programmer can be used to access the controller’s fault history file.
The programmer will read out all the faults the controller has experienced
since the last time the fault history file was cleared. Faults such as contactor
faults may be the result of loose wires; contactor wiring should be carefully
checked. Faults such as 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.
☞
C A U T I O N