Curtis 1239E - 11 - DIAGNOSTICS AND TROUBLESHOOTING

Return to TOC Curtis 1239E-1269E Manual, os 37.0 RevA – May 2021
11 — DIAGNOSTICS AND TROUBLESHOOTING
pg. 137
11 — DIAGNOSTICS AND TROUBLESHOOTING
e controller detects a wide variety of faults or error conditions. Faults can be detected by the operating
system or by the VCL code. is chapter describes the faults detected by the operating system.
Faults detected by VCL code (faults 51–67 in Table 6) cannot be dened here as they will vary from
application to application. Refer to the appropriate OEM documentation for information on these faults.
DIAGNOSTICS
Diagnostics information can be obtained in either of two ways: (1) by reading the display on a 1313
handheld or 1314 PC programmer or (2) by observing the fault codes issued by the Status LEDs. See
Table 5 for a summary of LED display formats.
e 1313 /1314 programmer will display all faults that are currently set as well as a history of the
faults that have been set since the history log was last cleared. e 1313/1314 display the faults
by name.
e pair of LEDs built into the controller (one red, one yellow) produce ash codes displaying all the
currently set faults in a repeating cycle. Each code consists of two digits. e red LED ashes once
to indicate that the rst digit of the code will follow; the yellow LED then ashes the appropriate
number of times for the rst digit. e red LED ashes twice to indicate that the second digit of the
code will follow; the yellow LED ashes the appropriate number of times for the second digit.
Example:
B+ Undervoltage Cutback (code 23).
In the Fault menu of the 1313/1314 programmer, the words B+ Undervoltage Cutback will be
displayed; the real-time battery voltage is displayed in the Monitor menu (“Capacitor Voltage”).
e controller’s two LEDs will display this repeating pattern:
Red Yellow Red Yellow
(rst digit) (2) (second digit) (3)
e numerical codes used by the yellow LED are listed in the troubleshooting chart (Table 6), which
also lists possible fault causes and describes the conditions that set and clear each fault.
Identifying Prototype Software
In recent years, many global functional safety standards have changed to include requirements for
formal verication/validation of soware for production vehicles. Curtis has included a feature in the
soware to allow both Curtis internal soware development teams and OEM development engineers
to make it clear to someone working with a prototype vehicle that the soware is not fully veried. If a
prototype OS coming from Curtis is not fully veried, the LED blink pattern when no faults are present
will change to a fast ashing red LED rather than the standard slow yellow ashing LED.
In addition, there is now a VCL variable called VCL_Prototype_Soware. Setting this variable to a non-
zero value in the initialization section of a VCL program will cause the same fast ashing red LED