C9 Engine for the 816F Series 2 Landfill Compactor, the 815F Series 2 Soil Compactor, and the 814F Series 2 Wheel Dozer Caterpillar

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. A further explanation of event codes and the engine's monitoring system are described after Table 1.

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. This is followed by a description of the code. 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 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 damage to the 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 temperature sensor. Do not use the Illustration to troubleshoot temperature sensors.

Illustration 1	g01341654
Example of the typical operating range of a temperature sensor (1) This area represents the normal operating range of the parameter. The normal output voltage of the sensor is between 0.2 VDC and 4.2 VDC. (2) In this area, the temperature above 107 °C (225 °F) is higher than normal. The output voltage of the sensor will generate an event code. The sensor does not have an electronic problem. (3) In these areas, the output voltage of the sensor is too high or too low. The voltage is outside of the normal range. The electronic problem will generate a diagnostic code. Refer to Troubleshooting, "Diagnostic Trouble Code List" 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.

Clearing Event Codes

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

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

• The service technician manually clears the code.

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. This is very important for problems that are intermittent. Refer to Troubleshooting, "Inspecting Electrical Connectors".

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

Trip Points for the Caterpillar Monitoring System

The monitoring system determines the level of action that is taken by the ECM in response to a condition that can damage the engine. When any of these conditions occur, the appropriate event code will be generated.

Table 2 contains the parameters that are monitored and the appropriate event code(s) that can be generated for that parameter. Table 2 also contains the minimum and maximum ranges for the parameter and the default trip points for each parameter. The actual settings for each parameter can be viewed with Caterpillar Electronic Technician (ET). The trip points for some of the parameters may be adjustable with Cat ET.