P0196

Fuel System - Troubleshooting - P0196

Component Location:

GENERAL DESCRIPTION
The fluid of the CVVT is the engine oil and its density changes according to the engine oil temperature. At this time the Oil Temperature Sensor (OTS) helps compensation against the temperature differences. The Oil Temperature Sensor measures the engine oil temperature before the engine oil comes into the Oil-flow Control Valve (OCV). According to the measured temperature, the Engine Control Module (PCM) compensates the oil-flow control valve operation time.

DTC DESCRIPTION
The purpose of this diagnosis is to detect a stuck oil temperature signal or implausibly low high signal. For the stuck signal detection, the PCM checks whether after a variation of the calculated oil temperature also a variation of the measured oil temperature is detected and sets DTC P0196 if the variation of the measured oil temperature is lower than the threshold. For the implausibly high, low signal detection, the PCM compares measured engine oil temperature with calculated oil temperature or coolant temperature and sets DTC P0196 when one of following conditions is met.

1. Measured oil temperature is implausibly low when calculated oil temperature is high.
2. Measured oil temperature is implausibly high when coolant is low without any relevant failure.

DTC Detecting Condition:

MONITOR DTC STATUS

NOTE: If any codes relating to OTS are stored, do ALL REPAIRS associated with those codes before proceeding with further troubleshooting.

1. Connect scan tool and select "Diagnostic Trouble Codes(DTCs)" mode.
2. Press F5(INFO) to select DTC information from the DTCs menu.
3. Confirm that "DTC Readiness Flag" indicates "Complete". If not, drive the vehicle within conditions noted in the freeze frame data or enable conditions.
4. Read "DTC Status" parameter.
5. Is parameter displayed "History(Not Present) fault"?

NOTE:
1. History (Not Present) fault : DTC occurred but has been cleared.
2. Present fault : DTC is occurring at present time.

YES - Fault is intermittent caused by poor contact in the sensor's and/or PCM's connector or was repaired and PCM memory was not cleared. Thoroughly check connectors for loose or poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and go to "Verification of Vehicle Repair" procedure.

NO - Go to next step.

TERMINAL AND CONNECTOR INSPECTION
1. Many malfunctions in the electrical system are caused by poor harness(es) and terminals. Faults can also be caused by interference from other electrical systems, and mechanical or chemical damage.
2. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage.
3. Has a problem been found?

YES - Repair as necessary and go to "Verification of Vehicle Repair" procedure

NO - Go to "Component Inspection" procedure

Specification:

COMPONENT INSPECTION
1. Ignition "OFF"
2. Disconnect OTS connector.
3. Measure resistance between terminals 1 and 2 of OTS connector.(Component side)
4. Is sensor switching properly?

YES - Check for poor connection between PCM and component: backed out terminal, improper mating, broken locks or poor terminal to wire connection. Repair as necessary and go to "Verification of Vehicle Repair" procedure.

NO - Check OTS for contamination, deterioration, or damage. Substitute with a known-good OTS and check for proper operation. If the problem is corrected, replace OTS and then go to "Verification of Vehicle Repair" procedure.

VERIFICATION OF VEHICLE REPAIR
After a repair, it is essential to verify that the fault has been corrected.
1. Connect scan tool and select "Diagnostic Trouble Codes(DTCs)" mode.
2. Press F5(INFO) and confirm that "DTC Readiness Flag" indicates "Complete". If not, drive the vehicle within conditions noted in the freeze frame data or enable conditions.
3. Read "DTC Status" parameter.
4. Is parameter displayed "History(Not Present) fault"?

YES - System performing to specification at this time. Clear the DTC.

NO - Go to the applicable troubleshooting procedure.

Schematic Diagram: