DP2 DIAGNOSTIC AND TROUBLESHOOTING [CURTIS CODES]
Learn to diagnose and troubleshoot DP2 systems using Curtis codes in this comprehensive guide.
7—DIAGNOSTIC & TROUBLESHOOTING
DIAGNOSTIC AND TROUBLESHOOTING
The 1212 and 1212P controllers provide diagnostics information to assist technicians in troubleshooting drive system problems. The diagnostics information can be obtained in two ways: by reading the appropriate display on the programmer or by observing the fault codes by the status LED.
PROGRAMMER DIAGNOSTICS
The programming devices present complete diagnostic information in plain language. Faults are displayed in the Faults/Diagnostics menu, and the status of the controller inputs/outputs is displayed in the Monitor menu. Additionally, the fault history file in the Faults/Diagnostics menu provides a list of the faults that have occurred since the file was last cleared. Checking (and clearing) the faults history file is recommended each time the vehicle is brought in for maintenance. Refer to the troubleshooting chart (Table 3) for suggestions about possible causes of the various faults. For information on programming devices, see Appendix D.
LED DIAGNOSTICS
During normal operation, with no faults present, the status LED is steadily on. If the controller detects a fault, the status LED flashes a 2-digit fault identification code continuously until the fault is corrected. For example, code “1,4”—undervoltage—appears as:

The fault codes are listed in Table 2. Refer to the troubleshooting chart (Table 3) for suggestions about possible causes of the various faults.
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
FAULT HANDLING
When a fault is detected, the controller operates in a manner that is safe in the presence of that fault. Depending on the severity of the fault, the response can range from reduction of current to complete shutdown of drive.
Curtis 1212/1212P Manual, Rev. c 37
7—DIAGNOSTIC & TROUBLESHOOTING
TABLE 2 STATUS LED FAULT CODES | ||
LED CODES |
FAULT |
|
LED off solid on |
|
No power or defective controller powered up; no faults |
| ||
1,1 |
|
THERMAL FAULT |
1,2 |
|
THROTTLE FAULT |
1,3 |
|
SPEED POT FAULT |
1.4 |
|
UNDERVOLTAGE FAULT |
1,5 |
|
OVERVOLTAGE FAULT |
|
|
|
2,1 |
|
MAIN OFF LIMIT |
2,2 |
|
EMR SEQUENCE FAULT |
2,3 |
|
MAIN FAULT * |
2,4 |
|
MAIN ON FAULT * |
2,5 |
|
(not used) |
|
|
|
3,1 |
|
WIRING FAULT * |
3,2 |
|
BRAKE ON FAULT |
3,3 |
|
PRECHARGE FAULT* |
3,4 |
|
BRAKE OFF FAULT |
3,5 |
|
HPD FAULT |
|
|
|
4,1 |
|
CURRENT SENSE FAULT* |
4,2 |
|
HARDWARE FAILSAFE * |
4,3 |
|
EE CHECKSUM FAULT Ť |
4,4 |
|
(not used) |
4,5 |
|
BATTERY DISCONNECT FAULT * |
*= Must cycle keyswitch to clear. | ||
Ť= Must use programmer to clear; as follows: select Program menu, alter data value of any parameter; cycle keyswitch. |
8—MAINTENANCE
8 MAINTENANCE
There are no user serviceable parts in Curtis 1212/1212P controllers. No attempt should be made to open, or otherwise modify the controller. Doing so may damage the controller and will void the warranty. However, it is recommended that the controller's fault history file be checked and cleared periodically, as part of routine vehicle maintenance.
DIAGNOSTIC HISTORY
The handheld programmer can be used to access the controller's fault history file. The programmer will read out all the faults that the controller has experienced since the last time the history file was cleared. The faults may be intermittent faults, faults caused by loose wires, or faults caused by operator habits or by overloading.
After a problem has been diagnosed and corrected, clearing the history file is advisable. This allows the controller to accumulate a new file of faults. By checking the new history file at a later date, you can readily determine whether the problem was indeed completely fixed.
Table 3 TROUBLESHOOTING CHART | |||
LED CODE
|
PROGRAMMER LCD DISPLAY |
EXPLANATION |
POSSIBLE CAUSE |
1,1 |
THERMAL FAULT |
Over-/under-temperature cutback |
1. Temperature>80C or <-10C. |
2. Excessive load on vechicle | |||
3. Operation in extreme environment | |||
4. Electromagnetic brake not releasing. | |||
1,2 |
THROTTLE FAULT |
PotLow and/ or PotWiper out of range |
1.Throttle input wire open or shorted. |
2. Throttle pot defective | |||
3. Wrong throttle type selected | |||
1,3 |
SPEED POT FAULT |
speed limit pot wiper out of range |
1.Speed limit pot wire(s) broken or shorted. |
2.Broken speed limit pot. | |||
1,4 |
UNDERVAULT FAULT |
battery voltage too low |
1.Battery voltage <17 volts. |
2. Bad connection at battery or controller | |||
1,5 |
OVERVOLTAGE FAULT |
battery voltage too high |
1.Battery>31 volts. |
2.Vehicle operating with charger attached. | |||
3. Intermittent battery connection | |||
2,1 |
MAIN OFF FAULT |
Main contactor driver Off fault |
1.Main contactor driver failed open. |
2,2 |
EMR SEQUENCING FAULT |
Improper sequencing |
1.Emerg. Rev. Switch pressed before KSI on. |
2,3 |
MAIN FAULT |
Main contactor fault |
1. Main contactor welded or stuck open. |
2. Main contactor driver fault. | |||
2,4 |
MAIN ON FAULT |
Main contactor driver On fault |
1.Main contactor driver failed to closed. |
3,1 |
WIRING FAULT |
HPD fault present> 10 sec. |
1. Misadjusted throttle. |
2. Broken throttle pot or throttle mechanism | |||
3,2 |
BRAKE ON FAULT |
brake On fault |
1. Electromagnetic brake driver shorted. |
2. Electromagnetic brake coil open. | |||
3,3 |
PRECHARGE FAULT |
pre-charge fault |
1.Brake driver shorted. |
2.Precharge circuit damaged. | |||
3.MOSFET failure | |||
3,4 |
BRAKE OFF FAULT |
Brake Off fault |
1.Electromagnetic brake coil open. |
2. Electromagnetic brake coil shorted. | |||
3,5 |
HPD FAULT |
HPD (High Pedal Disable) |
1. Improper sequence of throttle and KSI, push, or inhibit inputs. |
2. Misadjusted throttle pot. | |||
4,1 |
CURRENT SENSE FAULT |
Current sense out of range |
1. Short in motor or in motor wiring. |
2. Controller failure* | |||
4,2 |
HARDWARE FAILSAFE |
Motor voltage out of range |
1. Motor voltage does not correspond to throttle request. |
2.Short in motor or in motor wiring. | |||
3.Controller failure.* | |||
4,3 |
EEPROM CHECKSUM FAULT |
EEPROM fault |
1.EEPROM failure or fault. |
4,5 |
BATTERY DISCONNECT FAULT |
Battery disconnected |
1.Battery not connected. |
2.Poor connection to battery terminal |
*Jack up vehicle and retest to confirm diagnosis. Clean connection, inspect system wiring, and retest.
*Click on link to see original document: