Event codes alert the operator that an abnormal engine operating condition such as low oil pressure or high coolant temperature has been detected. When the event code is generated, the event is active.
The Electronic Control Module (ECM) can log events. Logged events usually indicate a mechanical fault instead of an electronic system fault or the engine is operating outside the design specification.
Note: If a diagnostic code has already been logged then any associated event code to that fault will not be logged as well. If an event code is already active, a diagnostic code that is associated with the same sensor will not be active.
An active event code represents a fault with engine operation. Correct the fault as soon as possible.
Active event codes are listed in ascending numerical order. The code with the lowest number is listed first.
Event codes will cause a warning lamp to illuminate on the control panel and a warning horn will sound.
Illustration 1 is an example of the operating range of an oil temperature sensor. Do not use the Illustration to troubleshoot the oil temperature 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 fault. (3) In these areas, the signal from the sensor is outside of the operating range of the sensor. The sensor circuit has an electronic fault. A diagnostic code will be generated for the sensor circuit. Refer to Troubleshooting, "Self Diagnostics" for additional information on diagnostic codes. | |
The following format is used for event codes:
"EXXX (Y) Description of the event"
The "E" means that the code is an event code. The "XXX" represents a numeric identifier for the event code. The "(Y)" represents a numeric identifier for the severity of the event. This is followed by a description of the event. Refer to the following example:
"E004 (3) Engine Overspeed Shutdown"
In this example, the number 3 indicates the severity of the event. The ECM has three levels of response to events:
Level (1) - This level can be referred to as the "Warning Level". This condition represents a serious problem with engine operation. However, this condition does not require a derate or a shutdown.
Level (2) - This level can be referred to as the "Derate Level". For this condition, the ECM reduces the engine's power in order to help prevent possible engine damage.
Level (3) - This level can be referred to as the "Shutdown Level". On this machine, a "Level 3" event code will be logged in the ECM but the engine will not shut down.
Responses to certain events may be programmed into the ECM. Refer to Troubleshooting, "System Configuration Parameters".
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 faults. Logged codes can also be used to review the performance of the engine.
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 fault which generated the code.
For basic troubleshooting of the engine, perform the following steps in order to diagnose a malfunction:
- Obtain the following information about the complaint from the operator:
- 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.
- Verify that the complaint is not due to normal engine operation. Verify that the complaint is not due to error of the operator.
- Narrow the probable cause. Consider the operator information, the conditions of operation, and the history of the engine.
- 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 faults that are intermittent. Refer to Troubleshooting, "Electrical Connectors - Inspect".
If these steps do not resolve the fault, identify the procedures in this manual that best describe the event. Check each probable cause according to the tests that are recommended.