3512B Oil Well Servicing Engine (ADEM III) 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 functional test or the 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.

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.

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	g01138880
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 Code List" for additional information on diagnostic codes.

Events are represented in two formats. In the first format, the "E" means that the code is an event code. The "XXX" represents a numeric identifier for the event code. This is followed by a description of the code. If a warning, a derate, or a shutdown is applicable, the numeric identifiers are different. Refer to the following example:

• E004 Engine Overspeed Shutdown

In the second format, the "E" means that the code is an event code. The "XXX-X" represents a numeric identifier for the event code. The fourth "X" identifies the event as a warning, a derate, or a shutdown. This is followed by a description of the code. Refer to the following example:

• E360-1 Low Oil Pressure Warning

• E360-2 Low Oil Pressure Derate

• E360-3 Low Oil Pressure Shutdown

The definition for a warning, a derate, and a shutdown are defined below:

Warning - This condition represents a serious problem with engine operation. However, this condition does not require a derate or a shutdown.

Derate - For this condition, the engine's Electronic Control Module (ECM) reduces the engine's power in order to help prevent possible engine damage.

Shutdown - For this condition, the ECM shuts down the engine in order to help prevent possible engine damage.

Logged Event Codes

When the 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 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 conditions that are monitored and the default trip points for each condition. Each condition has an associated parameter. The 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.

Illustration 2	g00863970
Map of the engine oil pressure versus the engine rpm (X) Engine rpm (Y) Engine oil pressure in kPa (1) Hysteresis (minimum and maximum engine oil pressure) (2) Normal engine oil pressure

Default Conditions for the Monitoring System

Table 3 contains the default conditions that cause an event code to be generated. Table 3 also contains a column that describes the system response when the conditions indicate that an abnormal operating condition exists.