Curtis ENABLE 40 - Manual (Page 58)

52 Curtis enAble ® 40-Series Manual, Rev. B
9
MAINTENANCE
There are no user serviceable parts in the Curtis 1740 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.
Replacement parts are, however, available for the Curtis 1741 user hand-
control and Curtis 1742 attendant control. See Appendix C for part numbers.
It is recommended that the controller and handcontrol(s) be kept clean and dry
and that the controller’s fault history file be checked and cleared periodically.
CLEANING
Cleaning the controller exterior will help protect it against corrosion and pos-
sible 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 latched.
FAULT HISTORY
The 1311 programmer’s Fault menu 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. The faults
may be intermittent faults, faults caused by loose wires, or faults caused by
operator errors.
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.
9 — MAINTENANCE