09492-38009 Suzuki JET, PILOT (38)

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, "Troubleshooting with a Diagnostic Code" for additional information on diagnostic codes.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 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. Loose connections and damaged connections are likely causes of intermittent problems. Refer to Troubleshooting, "Inspecting Electrical Connectors".If these steps do not resolve the problem, identify the procedures in this manual that best describe the event. Check each probable cause according to the tests that are recommended.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 trip.Table 1 contains conditions that are monitored and the typical default trip points for each condition. The trip points can be different for different flash files.The settings for each parameter can be viewed with the Caterpillar Electronic Technician (ET). The trip points for some of the parameters may be adjustable with Cat ET. Use Cat ET to find the adjustable ranges for the values.In some cases, a most severe event will occur before a least severe event or an event of moderate severity.In some cases, trip points and delay times are shared by the different levels of severity for an event.
Table 1
Typical Default Trip Points for the Monitoring System    
Condition    Delay Time in Seconds    Default Setting    Default State    
Altitude (atmospheric pressure)        
Moderate Severity (2)     0    
92 kPa (13.4 psi)     On    
Engine Overspeed        
Least Severe (1)
Most Severe (3)     0     2070 rpm     On    
High Aftercooler Coolant Temperature        
Least Severe (1)
Moderate severity (2)
Most Severe (3)     5    
102° C (216° F)
107° C (225° F)
107° C (225° F)     On    
High Air Filter Restriction Pressure        
Least Severe (1)
Moderate Severity (2)     5    
7 kPa (28 inch of H2O)     On    
High Boost Pressure        
Least Severe (1)
Moderate Severity (2)     0    
400 kPa (58 psi)     Off    
High Crankcase Pressure        
Least Severe (1)
Moderate Severity (2)
Most Severe (3)     3
10
3    
2 kPa (8 inch of H2O)
6 kPa (24.1 inch of H2O)
3.5 kPa (14.10 inch of H2O)     On    
High Engine Coolant Temperature        
Least Severe (1)
Moderate Severity (2)
Most Severe (3)     5
30
5    
102° C (216° F)
107 °C (225 °F)
107 °C (225 °F)     On    
High Engine Oil Filter Restriction Pressure        
Least Severe (1)     5    
103 kPa (15 psi)     On    
Least Severe (1)    
124 kPa (18 psi) (1)
High Exhaust Temperature        
Least Severe (1)
Moderate Severity (2)     5    
600° C (1112° F)
750 °C (1382 °F)     On    
High Fuel Filter Restricti