C13, C15, and C18 Tier 4 Interim Engines Event Codes Caterpillar

Parts of the Event Code

Event Code - The "E" identifies the code as an event code. The "XXX(X)" represents a numeric identifier for the event code. The fourth "(X)" assigns one of three levels to the active event code according to the severity of the abnormal system condition. Refer to the following example:

• E360(1) Low Oil Pressure

• E360(2) Low Oil Pressure

• E360(3) Low Oil Pressure

The definition for the levels of severity for an event are defined below:

Level 1 - Level 1 alerts the operator that an engine system requires attention. The operator should check that the involved system condition or the operator should perform maintenance on the involved system at the earliest possible time.

Level 2 - Level 2 requires a change in the operation of the engine or the performance of a maintenance procedure. Failure to correct the problem that caused this warning may result in damaged engine components.

Level 3 - Level 3 requires an immediate safe shutdown of the engine in order to avoid damage to the engine or injury to personnel around the engine. The problem that caused the event must be corrected before engine operation can resume.

Active Event Codes

An active event code represents a problem with engine operation. Correct the problem as soon as possible.

Active event codes are listed in ascending numerical order. The code with the lowest number is listed first.

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. (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. Refer to Troubleshooting, "Diagnostic Trouble Codes" for additional information on diagnostic codes.

Logged Event Codes

When the Electronic Control Module (ECM) generates an event code, the ECM logs the code in permanent memory. The ECM has an internal diagnostic clock. The ECM will record the following information when an event 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

Logged events are listed in chronological order. The most recent event code is listed first.

This information can be helpful for troubleshooting intermittent problems. Logged codes can also be used to review the performance of the engine.

Autoclear and Clearing of Event Codes

A non-critical event code is cleared from memory when one of the following conditions occur:

• The code does not recur for 100 service hour meter hours.

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

• The service technician manually clears the code.

Always clear logged event codes after investigating and correcting the problem which generated the code.

Critical Event Codes

Critical event codes that are critical to engine life will not automatically clear and are only cleared from memory when one of the following conditions occur:

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

• The service technician manually clears the code.

Note: Examples of critical event codes include "Engine Over Speed", "Low Oil Pressure", "High Intake Temperature" and "High Coolant Temperature".

Always clear logged event codes after investigating and correcting the problem which generated the code.

Troubleshooting

For basic troubleshooting of the engine, perform the following steps in order to diagnose a malfunction:

1. Obtain the following information about the complaint:

   • The event and the time of the event

   • Determine the conditions for the event. The conditions will include the engine rpm and the load.

   • Determine if there are any systems that were installed by the dealer or by the customer that could cause the event.

   • Determine whether any additional events occurred.

2. Verify that the complaint is not due to normal engine operation. Verify that the complaint is not due to error of the operator.

3. Narrow the probable cause. Consider the operator information, the conditions of operation, and the history of the engine.

4. Perform a visual inspection. Inspect the following items:

   • Fuel supply

   • Oil level

   • Oil supply

   • Wiring

   • Connectors

Be sure to check the connectors. Connector inspection is important for problems that are intermittent. Refer to Troubleshooting, "Electrical Connectors - Inspect".

If these steps do not resolve the problem, refer to Table 1 for the procedure to troubleshoot the event code.

Cross-Reference Information for Event Codes

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

Event codes are generated when abnormal operating conditions exist.

Note: A requirement for all troubleshooting is that the troubleshooting is based on active and/or passive diagnostic trouble codes. Do not troubleshoot based on flash codes alone.