F712061 Force CARBURETOR (HO-4A) (90B/92B)

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 troubleshooting 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.
Table 1
Cross-Reference from Event Codes on Cat Data Link to J1939 Code to Troubleshooting Procedure
Code and Description Troubleshooting Procedure
E017(1) High Engine Coolant Temperature Warning Troubleshooting, "Coolant Temperature Is High"
E021(2) High Exhaust Temperature Derate Troubleshooting, "Exhaust Temperature Is High"
E035(1) Loss of Coolant Flow Warning Troubleshooting, "Coolant Flow - Test"
E038(1) Low Engine Coolant Temperature Warning Troubleshooting, "Coolant Temperature Is Low"
E072(1) Oil Level Low Mark Troubleshooting, "Oil Level - Test"
E073(1) High Oil Filter Differential Pressure Troubleshooting, "Oil Pressure Is Low"
E095(1) Fuel Filter Restriction Warning Troubleshooting, "Fuel Filter Differential Pressure -Test"
E098(1) Engine Pre-lube Override Troubleshooting, "Prelubrication - Test"
E099(1) Engine Oil Filter Restriction Warning Troubleshooting, "Oil Pressure Is Low"
E100(1) Low Engine Oil Pressure Warning Troubleshooting, "Oil Pressure Is Low"
E101(1) High Crankcase Pressure Warning Troubleshooting, "Crankcase Pressure Is High"
E190(1) Engine Overspeed Warning Troubleshooting, "Engine Overspeed"
E265(3) User Defined Shutdown Troubleshooting, "Shutdown - Test"
E272(1) Inlet Air Restriction Warning Troubleshooting, "Inlet Air Is Restricted"
E539(1) High Intake Manifold Air Temperature Troubleshooting, "Intake Manifold Air Temperature Is High" 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 PressureThe definition for the levels of severity for an event are defined below:
Table 2
Indicators (1), (2), and (3)
Warning Category Indicator Severity
(1) "Least Severe"
(2) "Moderate Severity"
(3) "Most Severe" 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 ECM generates an event code, the ECM may log the event 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 codeLogged 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:
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.
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
ConnectorsBe sure to check the connectors. This is very 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.Parameter Settings of the Engine Monitoring System
The default settings for the parameters are programmed at the factory. If the delay time or the trip point are programmable, the minimum and maximum ranges will be listed in Table 3.The parameter settings for the engine monitoring system can also be viewed on Caterpillar Electronic Technician (ET). In order to view the parameters of the engine monitoring system, refer to Troubleshooting, "Engine Monitoring System".
Table 3
Default Settings of the Programmable Monitoring System
Code and Description Action Delay Time in Seconds Trip Point Default State
Min