Curtis 1253 - 6 Maintenance

Curtis 1253 Manual, Rev. F
35
Blue Ox Rev. A, draft #1 [3 August 2007]
6 — MAINTENANCE
☞
CAUTION
6
MAINTENANCE
ere are no user serviceable parts in the Curtis 1253 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 that its fault
history file be checked and cleared periodically.
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. ese 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. e controller should be wiped clean with a moist rag. Dry it
before reconnecting the battery.
4. Make sure the connections are tight.
FAULT HISTORY
e programmer can be used to access the controller’s fault history file. e
programmer will read out all the faults that the controller has experienced since
the last time the fault history file was cleared. e 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 startup lockout 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 diagnostic history file. is 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.