3176C ENGINE FOR USE IN CPT372 & Caterpillar

Section 4: Troubleshooting With A Diagnostic Code

Usage:

Diagnostic Codes

Diagnostic codes are used by the electronic system to alert the operator that a problem exists and indicates to the service technician the nature of the problem.

Diagnostic Codes may be viewed using Electronic Service Tools (ET or ECAP). The CID, or Component IDentifier, tells which component in the system the diagnostic code is for. The FMI, or Failure Mode Identifier indicates what the failure mode is.

The code number will direct you to a procedure in Section 5: Troubleshooting With A Diagnostic Code. Do not confuse diagnostic codes with diagnostic events (refer to LOGGED Events in this section). Events can be logged in the ECM to track information about the engine. An example would be a low oil pressure event. An event is generated when the engine oil pressure is low but not out of range for the sensor. This does not indicate a problem with the sensor, rather it indicates a problem with the engine oil pressure. Refer to Logged Events later in this section for more information.

ACTIVE Diagnostic Codes

An ACTIVE diagnostic code represents a problem with the electronic control system that should be investigated and corrected as soon as is practical. When an ACTIVE diagnostic code is generated, a Diagnostic Lamp will indicate the diagnostic code. If the condition generating the diagnostic occurs only for a brief moment, the message will disappear and the diagnostic code will be LOGGED in the ECM memory.

To troubleshoot an active diagnostic code, refer to the Diagnostic Code Cross Reference to Functional Test Procedures in the beginning of this manual under the specific code number.

LOGGED Diagnostic Codes

When the ECM generates a diagnostic code, it will log the code in permanent memory within the ECM. The ECM has an internal diagnostic clock and will record the hour of the first occurrence, the hour of the last occurrence and the number of occurrences of the code. Knowing when and how often the code was generated can be a valuable indicator when troubleshooting intermittent problems.

NOTE: The ECAP Electronic Service Tool can be used but does not support all logged codes. Logged codes can be retrieved or erased using an Electronic Service Tool. Logged diagnostic codes will automatically be deleted if no additional occurrences are recorded in 100 hours. When investigating logged diagnostic codes, keep in mind the following information.

Some diagnostic codes may log occurrences that did not result in operator complaints. If the time the code was logged does not correlate to a complaint, there may be nothing to fix.

The most likely cause of an intermittent problem is a faulty connection or damaged wiring. Next likely is a component failure (sensor or switch). Least likely is failure of the ECM itself.

Diagnostic codes that are logged repeatedly may indicate a problem that needs special investigation.

To troubleshoot an logged diagnostic code, refer to the Diagnostic Code Cross Reference to Functional Test Procedures in the beginning of this manual under the specific code number.

The code number will direct you to a procedure in troubleshooting guide. If the symptoms continue, use the proper procedure for troubleshooting the symptoms that have been experienced by the operator. Refer to Troubleshooting Without A Diagnostic Code.

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

Events

The ECM can log engine events which refer to engine operating conditions such as low fuel pressure or an Engine Overspeed Warning. Logged events do not indicate an electronic system problem, but may indicate an engine system problem.

Diagnostic Codes Effect on Engine Performance

When the ECM detects an engine problem, it generates an Active diagnostic code, and logs the code to indicate when and how many times the problem has occurred. There are two types of diagnostic codes: Fault Codes and Event Codes.

Diagnostic Codes are provided to indicate an electrical or electronic problem has been detected by the ECM. In some cases the engine performance can be affected when the condition causing the code exists. More frequently, however, the operator cannot detect any difference in the engine performance.

If the operator indicates a performance problem occurs whenever the Diagnostic Lamp is flashing, the diagnostic code may indicate the cause of the problem, and should be corrected.

If the operator does not indicate a problem with the engine performance and a diagnostic code is logged by the ECM, it indicates the ECM detected an abnormal condition, but it did not affect performance.

If this is the case, unless there are several occurrences of the code in a very short period of time, or, the ECM is indicating an Active Code at the present time, there is most likely nothing wrong with the system.

Event Codes

Event Codes are issued by the ECM for each engine event. They are not necessarily an indication of problems within the Electronic system. These event codes are read and interpreted by the Electronic Service Tool, which displays a numeric code and a description of the LOGGED EVENT. The LOGGED ID's can be found under the DIAGNOSTIC window on the electronic service tool. The code is logged and some can only be cleared by factory passwords.

NOTE: Events can only be viewed with a Caterpillar Electronic Technician service tool.

The information displayed for a LOGGED Event is as follows:

* CID- Event Identifier. The CID is a three digit number that corresponds to an ACTIVE or LOGGED engine event.

* Test Description- The text which describes the event.

* Number Of Occurrences- The number of "good to bad" transitions that have occurred.

* Time Of First Occurrence- The time that the first logged event occurred, measured in the ECM hours, by the diagnostic clock is shown on the Logged Events service tool screen.

* Time Of Last Occurrence- The time that the last logged diagnostic occurred, measured in ECM hours by the diagnostic clock.

This manual contains a table listing all of the CID-FMI diagnostic codes, along with the page number where details regarding the cause, performance affect, and troubleshooting of the code can be located.

Using ET and ECAP to Display Active Diagnostic Codes

1. Connect ET to the Communication Adapter Tool to the Service Tool Connector.

2. Connect ECAP to the Service Tool Connector.

3. Turn the keyswitch to the ON position, engine OFF.

4. For ET select the Display Active Diagnostics option.

5. For ECAP select the Industrial Functions and select the Diagnostic Function.

6. For ECAP select the Active Diagnostic Code Function.

7. Each Diagnostic Code CID and FMI are listed and followed by a text description.

Figure 4.1 - ET/ECAP Active Diagnostic Code Screen

Using ET and ECAP to Display Logged Diagnostic Codes

1. Connect ET to the Communication Adapter Tool to the Service Tool Connector.

2. Connect ECAP to the Service Tool Connector.

3. Turn the keyswitch to the ON position, engine OFF.

4. For ET select the Display Logged Diagnostics option.

5. For ECAP select the Industrial Functions and select the Diagnostic Function.

6. For ECAP select the Logged Diagnostic Code Function.

7. Each Diagnostic Code CID and FMI are listed and followed by a text description.

Figure 4.2 - ET/ECAP Logged Diagnostic Code Screen

Using ET and ECAP to Display Status

1. Connect ET to the Communication Adapter Tool to the Service Tool Connector.

2. Connect ECAP to the Service Tool Connector.

3. Turn the keyswitch to the ON position, engine OFF.

4. For ET select the Display Status option.

5. For ECAP select the Industrial Functions and select the Display Status Function.

6. Each Display Option is listed and followed by a text description.

Figure 4.3 - ET/ECAP Status Screen

Programmable Shutdown, Alarms And Derates

On some applications, shutdown, alarms and derates are programmable. The Electronic Service Tool can be used to turn these features ON and OFF. When the features are turned ON, the indication will appear on an electronic display module (i.e. Caterpillar Monitoring System) and an Event will also be logged in the ECM. When the features are turned OFF, the display will not appear on a monitoring module, but an Event will still be logged. Refer to Section 2 for additional information.

Engine Monitoring Programmed to Warning

Engine Monitoring Programmed to Derate

ECM Snapshot

The ECM can record a "snapshot" of engine parameters for a period of 13 seconds surrounding an event. The event is either a diagnostic code or an external trigger.

DO NOT replace electronic components based on snapshop data alone. The snapshot information is stored in frames every 0.24 seconds (if externally triggered) or every 0.48 seconds (if diagnostic code triggered). Frequently, the parameters are changing faster or slower than 0.24 seconds, the result will be a misdiagnosed problem if too much is interpreted from this information.

DO NOT attempt to interpret the information and analyze how the engine is operating from this historical information. Looking at this information under a "microscope" will lead to misdiagnoses because some parameters are not what are expected, even though they are completely unrelated to the problem under investigation.

When to Use a Snapshot

Use the snapshot data feature ONLY to help determine engine operating conditions when an intermittent problem occurs. If an intermittent diagnostic code is causing problems, use the snapshot data to determine if the problem occurs (or appears to occur) at specific engine speed, coolant temperature ranges, etc. Use this data to attempt to duplicate these conditions and allow the code to reoccur.

Engine Snapshot Data

Whenever most diagnostic codes occur, the ECM records the time (in engine hours), as well as engine operating parameters for 9.6 seconds before and 3.4 seconds after the diagnostic code. The engine operating parameters recorded are similar to those in the ECAP or ET status screens. Not all ECAP or ET status screens or parameters are recorded.

The Engine Snapshot is triggered from the ECAP or Electronic Technician Electronic Service Tools.

Diagnostic Code Triggered Snapshot

When viewing diagnostic triggered snapshots, the ECM sets a sensor value with an ACTIVE diagnostic code to a default value when the code is Active. The sensor value will suddenly jump to a specific value at the trigger point and remain there for the rest of the snapshot frames.

After the diagnostic code occurs, the ECM records many of the status parameters available on the Electronic Service Tool. The ECM records this information for 9.6 seconds before the code occurs, and 3.4 seconds after the code.

External Triggered Snapshot

If desired, a snapshot can be externally triggered using an Electronic Service Tool. The snapshot can be triggered from the Display/Trigger Snapshot screen, located under the Display Diagnostic Messages screen (follow the on-screen instructions).

ECM Storage of Snapshots

The ECM can store up to six diagnostic code triggered snapshots, and four externally triggered snapshots. They are stored in a "circular buffer". The newest snapshot will replace the oldest if a seventh diagnostic code triggered snapshot or fifth externally triggered snapshot is taken.

The ECM stores the snapshots in memory that is maintained through the Unswitched +Battery connection. If the Unswitched +Battery connection is disconnected, or if the unit batteries are disconnected, the snapshot information is cleared.

The snapshots can also be manually cleared using an Electronic Service Tool. Snapshots, like most diagnostic codes are automatically cleared by the ECM after 100 hours of operation.

Reference Sheet For Diagnostic Codes

NOTE: The following diagnostic codes are for engine Electronic Control Module diagnostics ONLY. To obtain diagnostic codes for your electronic display module refer to the service manual for your electronic display module.

Diagnostic Terminology

Component Identifier (CID): Two or three digit code which is assigned to each component or system.
Event Identifier (EID): Two or three digit code which is assigned to each component or system.
Failure Mode Identifier (FMI): Type of failure the component experienced (adopted from SAE standard practice J1587 diagnostics).

Active Code: The CID and FMI can be sent through the data link through the display module or through the Communication Adapter Tool, then to the Electronic Service Tool or various electronic display modules.
Logged Code: The diagnostic will be entered into the permanent memory (Diagnostic Log) when it becomes active. The number of occurrences will be saved in the "good to faulty counter" in the permanent memory (Diagnostic Log). First and last occurrence time (engine hours) will also be saved in the permanent memory (Diagnostic Log). This information is then available for display on the Electronic Service Tool.