P0016 code

Need some advice. I have a 2014 crew cab with 75000KM/47000miles that is giving me the p0016 code. the truck is on a lease and is due this Sept. I have changed the vvt sensor with no luck. Is it worth going down the rabbit hole of end game possibly new timing chain and buying the truck out and keeping it or hand it back in. As far as I can remember regular oil changes done by Toyota servicing. Mechanically I understand why and how this happens but from an engineering quality stand point this does not jive with me. How can a vehicle with low mileage have this problem already? No off-roading, city and highway only. I drive above the speed limit but very little dragging off the light or hard braking.

 

I did a little reading on this issue.
My understanding (which may be wrong) is that this code is set by the VVT.
The VVT gets its data from the ECM.
The ECM gets its data form the Crankshaft and Camshaft Sensors.

Is it possible one of the those sensors are bad?

Like I said, I could be wrong.
Surely some one with more ( or correct) knowledge will come along and help you.

 

I highly doubt that it's the timing chain. More likely a faulty CPS sensor or possibly faulty wiring to the sensor due to engine heat.

 

Reset CEL before u turn in lease for 3rd gen

 

I am going to replace my crankshaft position sensor and then do a wire inspection. I'll see how it goes from there. Has anyone else had this problem in the later 2nd gen models? Why is this sensor intermittent as I reset it, it take a day or two to re appear. Should it not be constant?
thanks for your help
Ian

 

Usually it takes a little bit of driving for the newly reset ECU to do its check/balances to find the issue again. You should d/c the battery again after CPS sensor replacement.

 

Numerous reasons it can take time to throw a MIL.
Some checks are only run under certain criteria.
Such as Engine RPM or Temperature ranges and time duration.

Since our truck have variable timing, it could be that the code is not set until you reach a certain timing range and rpm range.

I’m going to say in this situation, it would be normal for a time delay on setting.
the MIL.

 

How's the truck performing, unintended acceleration, lack of power, poor fuel economy?

 

I haven't notice anything unusual. No unwarranted acceleration or/ deceleration. Haven't noticed anything on fuel economy as I drive a summer toy this time of year and I don't track my fill ups by mileage and odometer.

 

So all its doing is throwing a code?

 

This should help:

http://www.customtacos.com/tech.old...06toyrm/06toypdf/06rmsrc/rm2006ta/0050014.pdf

 

I had the same code on me 09 with 189k miles. Replace both oil control valve and the code went away.

 

Reviving a bit of an old thread, but I am having a similar issue. I have had this code thrown for a while, tried cleaning and testing the vvt valves, no issues there, had an engine flush, diagnostics done by toyota etc etc. The truck turns over fine, runs fine no power surges no stalling no overly high or low idling no miss fires. When the code is off on its own, the engine starts and runs beautifully. When the code is on, the engine has a slight stumble then runs beautifully. I even had toyota open the valve covers and they said the timing was retarded a hair, litterly a hair and measure and remeasured and got the straightest line spossible to check and finally concluded that the timing was so close to bang on, that they didn't recommend retiming and are stumped on why it is throwing that code. Now the biggest thing here is a very intermittent code throw. The code, p0016 bank 1 sensor a, comes and goes as it pleases. I have watched it turn off and more importantly I have watched it turn on. It goes on for a few days, then turns off for about a week and back and forth. I am going to replace the sensor on bank 1 and see if that clears it. I am stumped at this point. Anyone have any similar issues?

Edit: also my mpg tanks hard when the light is on

 

Have you checked / cleaned or replaced the VVT Oil Control Valve Filters?

 

Yessir already done, should have put that. Thanks though. Hopefully changing the sensor does the trick

 

Good luck!

 

Luis1 it’s been a few years curious if the code ultimately went away?