7 — DIAGNOSTICS AND TROUBLESHOOTING
Curtis AC F2-A, F4-A, F6-A Motor Controllers – FOS 4.5 – April 2022 Return to TOC
pg. 202
2a. CANbus Emergency Message: Main_Contactor_Did_Not_Close_Active | 0x2221 0x01
Main Contactor Did Not Close fault. Flash code 3-9 (LEDs: x3 x9)
Identier DLC Data
0A6 8 39 FF 01 21 22 01 00 00
In this example, Device ID = 26h (38d). Note the “little-endian” byte-ordering for the error code
(ash code) and fault record object index. e Data Byte 5, 01, indicates the rst fault type for
the Main Contactor Did Not Close fault. In this case, the contactor was “open” during initial closure
operation (e.g., either the Driver 3 (pin 5) or the KSI Coil Return (pin 2) were disconnected, or the
contactor is defective). e 11-bit identier assembles as: A6h = 00 01 | 0 1 0 0 1 1 0, where the top
4 bits are the Sync-Error Function code, and the bottom 7 bits are the Node ID, as explained above.
2b. CANbus Emergency Message: Main_Contactor_Did_Not_Close_Active | 0x2221 0x01
Main Contactor Did Not Close fault. Flash code 3-9 (LEDs: x3 x9)
Identier DLC Data
0A6 8 39 FF 01 21 22 02 00 00
In this example, Device ID = 26h (38d). Note the “little-endian” byte-ordering for the error code
(ash code) and fault record object index. e Data Byte 5, 02, indicates the second fault type for
the Main Contactor Did Not Close fault. In this case, the contactor “opened” during operation (e.g.,
either the Driver 3 (pin 5) or the KSI Coil Return (pin 2) were disconnected while operational). e
11-bit identier assembles as: A6h = 00 01 | 0 1 0 0 1 1 0, where the top 4 bits are the Sync-Error
Function code, and the bottom 7 bits are the Node ID, as explained above.
3a. CANbus Emergency Message: Severe_B_Plus_Undervoltage_Active | 0x2120 0x01
Severe B+ Undervoltage. Flash code 1-7 (LEDs: x1 x7)
Identier DLC Data
0A6 8 17 FF 01 20 21 01 00 00
3b. CANbus Emergency Message: Severe_KSI_Undervoltage_Active | 0x2122 0x01
Severe KSI Undervoltage. Flash code 1-7 (LEDs: x1 x7)
Identier DLC Data
0A6 8 17 FF 01 22 21 01 00 00
In examples 3a and 3b, both faults share the same LED ash code. ey are distinguished in Data
Bytes 3 & 4 – Fault Record Object Index.
e OEM-dened user faults are also accessible in a CANbus emergency message. Error category
= 0x62XX (for User Fault 1-32 are OEM/Factory dened and implemented in VCL). For example:
e User_1_fault is OEM denable and is implemented the same way as the above OS faults.
CANbus Emergency Message: User_1_Fault_Active 0x2710 0x01 0x00
Flash code 5-1 (LEDs x5 x1)
Identier DLC Data
0A6 8 51 62 01 10 27 01 00 00