G3520B Industrial Engines Caterpillar

Cross-Reference Information for Diagnostic Codes

Table 1 is a list of the diagnostic codes for this engine. 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.

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. Caterpillar Electronic Technician (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 for an ECM. Diagnostic codes may consist of the component identifier (CID), and the failure mode identifier (FMI).

Component Identifier (CID) - The CID indicates the component that generated the code. For example, the CID number 301 identifies the ignition transformer primary for the number one cylinder.

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 procedure.

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".

Illustration 1 is an example of the operating range of a sensor.

Illustration 1	g01365757
Example of the typical operating range of a sensor (1) This area represents the normal operating range of the engine parameter. (2) In these areas, the engine is operating in an unsafe operating range of the monitored parameter. An event code will be generated for the monitored parameter. The sensor circuit does not have an electronic problem. Refer to Troubleshooting, "Event Codes" for additional information on event codes. (3) In these areas, the signal from the sensor is outside of the operating range of the sensor. The sensor circuit has an electronic problem. A diagnostic code will be generated for the sensor circuit.

Active Diagnostic Codes

An active diagnostic code represents a problem with the electronic control system. Correct the problem as soon as possible.

When the engine's ECM generates an active diagnostic code, the "Active Alarm" indicator ("Engine Control Alarm Status" on Cat ET) is activated in order to alert the operator. If the condition that generated the code is momentary, the message disappears from the list of active diagnostic codes. The diagnostic code becomes logged.

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.