3512C HD and 3516C HD IPP Rental Power Modules Caterpillar

Diagnostic Codes

Diagnostic codes alert the operator that a problem in the electronic system has been detected. Diagnostic codes are also used by the service technician to identify the nature of the problem. The technician must have access to a diagnostic tool in order to read diagnostic information.

The following Module Identifiers (MID) are used to identify the control modules that are associated with engine operation:

• MID No. 036 is used to identify the engine Electronic Control Module (ECM)

• MID No. 094 is used to identify the Temperature Control Module (TCM)

Tables1 and 1 lists the diagnostic codes that apply to the engine ECM.

Table 1 lists the diagnostic codes that apply to the TCM for the engine cooling system.

Use Caterpillar Electronic Technician (ET) in order to determine the diagnostic codes that are active or logged. Then refer to the appropriate troubleshooting procedure for more information.

Note: Do not confuse diagnostic codes with event codes. Event codes alert the operator that an abnormal operating condition such as low oil pressure or high coolant temperature has been detected. If an event code is active, refer to Troubleshooting, "Event Codes".

Diagnostic information is transmitted over data links. This engine uses the following two types of data links for communication. The data links are described below:

Cat Data Link

The Cat Data Link is used by the engine ECM to communicate with Caterpillar controllers or display modules. Cat ET is a software program that is designed to run on a personal computer. The software can be used by the service technician in order to view the diagnostic code information that is generated by the engine ECM. The diagnostic code is displayed as a two-element code. The following terms describe the elements of the code:

Component Identifier (CID) - The CID indicates the component that generated the code.

Failure Mode Identifier (FMI) - The FMI indicates the type of failure.

CAN data link

The CAN data link is used by the engine ECM to communicate with aftermarket controllers or display modules. The CAN data link is referred to as the J1939 data link. When a diagnostic code is activated, the ECM can transmit information about the diagnostic code over the J1939 data link to aftermarket controllers. The diagnostic code will be displayed as a two-element code. The following terms describe the elements of the code:

Suspect Parameter Number (SPN) - The SPN is a code which is assigned to each component in order to identify data via the data link to the ECM.

Failure Mode Identifier (FMI) - The FMI indicates the type of failure.

Refer to Table 1 for a complete list of the diagnostic codes and the appropriate troubleshooting procedures. Further explanations of diagnostic codes are explained after Table 1.

Cross-Reference Information for Diagnostic Codes that are Generated by the Engine ECM

Table 1 is a list of the diagnostic codes that are generated by the engine ECM. The diagnostic codes are cross-referenced with the appropriate procedure that can be used to troubleshoot the code.

Portions of this material are reprinted with permission from SAE J1939DA_201607^© 2016 SAE International. SAE International is not responsible for any use or translation of this material, in whole or in part. Please contact SAE International to obtain a complete copy of SAE J1939DA_201607, the official definitive source of this standard.

SPN-FMI Code to CID-FMI Code to the Appropriate Test Procedure

Logged Diagnostic Codes

When the ECM generates a diagnostic code, the ECM logs the code in permanent memory. The ECM has an internal diagnostic clock. Each ECM will record the following information when a code is generated:

• The hour of the first occurrence of the code

• The hour of the last occurrence of the code

• The number of occurrences of the code

This information is a valuable indicator for troubleshooting intermittent problems.

A code is cleared from memory when one of the following conditions occur:

• The service technician manually clears the code.

• The code does not recur for 100 hours.

• A new code is logged and there are already ten codes in memory. In this case, the oldest code is cleared.

Some diagnostic codes may be easily triggered. Some diagnostic codes may log occurrences that did not result in complaints. The most likely cause of an intermittent problem is a faulty connection or damaged wiring. The next likely cause is a component failure. The least likely cause is the failure of an electronic module. Diagnostic codes that are logged repeatedly may indicate a problem that needs special investigation.

Note: Always clear logged diagnostic codes after investigating and correcting the problem which generated the code.