P0016 Code

[Shady195]

I've seen a few threads on this but most of them end with no answers..

My car has 28k miles on it
Has been turbocharged for about 3-4k
Car idles fine, drives fine, no weird noises; aside from being in "limp" mode and having tons of timing pulled it seems fine
I cleared the code once, drove a bit seemed fine, had power felt great and shortly after I started up my car and it came on again.

Doesn't seem to come on until I start my car.

I'm not sure what to do, my VIN doesn't apply to the TSB, nor does the codes. I have no other symptoms.

Someone mentioned changing the oil, did that, cleared the code and after about 10 miles it came on after starting my car after I stopped at the store.

Was hoping someone else has any information or any idea of whats going on or what I can do.

[Shady195]

Swapped Cam Sensors

Swapped Oil Control Valves

Cleared the Code

Drove about 20 miles.. Car seemed fine, got on throttle a few times, drives perfect. Stopped and turned the car off, turned it back on and like clock work within 2 minutes it popped back on.

[steve99]

Originally Posted by Shady195

Swapped Cam Sensors

Swapped Oil Control Valves

Cleared the Code

Drove about 20 miles.. Car seemed fine, got on throttle a few times, drives perfect. Stopped and turned the car off, turned it back on and like clock work within 2 minutes it popped back on.

still P0016 or did it throw opposite bank code P0017 ?


I gather you on a B001C/D rom


Next easiest thing to do is the cam shaft sensor clearance TSB by shimming sensor.


After that its looking like cam sprocket


log the cam positions for intake/exhaust both sides and see if you can see which is laggy against the ecu requested cam position


http://www.ft86club.com/forums/showthread.php?t=67821

[Shady195]

Originally Posted by steve99

still P0016 or did it throw opposite bank code P0017 ?


I gather you on a B001C/D rom


Next easiest thing to do is the cam shaft sensor clearance TSB by shimming sensor.


After that its looking like cam sprocket


log the cam positions for intake/exhaust both sides and see if you can see which is laggy against the ecu requested cam position


http://www.ft86club.com/forums/showthread.php?t=67821

It did not follow the sensors or oil control valves stayed as Bank 1 Sensor A P0016

Everyone who has had a bad cam sprocket from what I can tell reported stalling, poor idling and poor drivabilty

I drove my car quite a bit, even got on it and it seems and sounds fine. Code only comes on after starting the car a second time after clearing the code.

I have an A01C ECU but tuned with the SBD Kit on OFT

[steve99]

Originally Posted by Shady195

It did not follow the sensors or oil control valves stayed as Bank 1 Sensor A P0016

Everyone who has had a bad cam sprocket from what I can tell reported stalling, poor idling and poor drivabilty

I drove my car quite a bit, even got on it and it seems and sounds fine. Code only comes on after starting the car a second time after clearing the code.

I have an A01C ECU but tuned with the SBD Kit on OFT

most likely it will be a B01C based tune, the cam /idle fixes were done by A01C.


grab the utility below it will check the calid of your tune, you just need a copy of tune on your computer, run it using B01C and A01C. or check it with hex editor


http://www.ft86club.com/forums/attac...9&d=1473467930

[Shady195]

Its a B01C based rom according to the Hex editor.

I honestly can't believe there is an actual mechanic issue, the car is 100% perfect mechanically as far as sounds and driveabilty, as just about everyone who had the bad cam gear had drivability issues.

I saw 1-2 posts about people who had this, never had a problem and just disabled it..

Is it possible theres something about the tune my car is starting to not like? My particualr car having certain AVCS variables the ECU just isnt coping with?

Seems unlikely, especially that it took 3k miles to happen, its also been really cool outside so that also got me thinking, but again seems unlikely.

Not quite sure what im suppose to be looking for with the log from my OFT, selected all the cam related channels but its foreign to me in what its supposed to look like.

[TheStig85]

Originally Posted by Shady195

Its a B01C based rom according to the Hex editor.

I honestly can't believe there is an actual mechanic issue, the car is 100% perfect mechanically as far as sounds and driveabilty, as just about everyone who had the bad cam gear had drivability issues.

I saw 1-2 posts about people who had this, never had a problem and just disabled it..

Is it possible theres something about the tune my car is starting to not like? My particualr car having certain AVCS variables the ECU just isnt coping with?

Seems unlikely, especially that it took 3k miles to happen, its also been really cool outside so that also got me thinking, but again seems unlikely.

Not quite sure what im suppose to be looking for with the log from my OFT, selected all the cam related channels but its foreign to me in what its supposed to look like.

Were you able to resolve the issue with the Code?

[Shady195]

Originally Posted by TheStig85

Were you able to resolve the issue with the Code?

Yep, by disabling it

I would not recommend the same unless you're certain its not a mechanical issue and you're willing to risk hurting your motor. In my case i'm fairly certain its an issue with my ECU (though my ECU is not in the range of VINS the TSB says is effected) I've had no symptoms of logs to indicate there is a problem, just a code.

Since then I've put a few thousand more miles and ran a few drift events without a problem.

I've read a few other posts of people having the same problem, some after a fresh motor/rebuild so they just disabled it.

I'm in the camp of when/if it blows it will be time to get a built motor.

[Teseo]

If flash back to stock, codes will come?

[Shady195]

Originally Posted by Teseo

If flash back to stock, codes will come?

If you have the code now, then more than likely yes.

There seems to be 2 causes of the code. An actual Mechanical issue, and an ECU issue. The ECU issue is not related to the tune from what I can tell based on what i've read, but to a problem within the unit itself, so flashing to stock will more than likely yield the same results.

[Teseo]

Originally Posted by Shady195

If you have the code now, then more than likely yes.

There seems to be 2 causes of the code. An actual Mechanical issue, and an ECU issue. The ECU issue is not related to the tune from what I can tell based on what i've read, but to a problem within the unit itself, so flashing to stock will more than likely yield the same results.

Yea, but if flashing to stock and code persist then its a mechanical issue. Asking because i have same cal id

[TheStig85]

Originally Posted by Shady195

Yep, by disabling it

I would not recommend the same unless you're certain its not a mechanical issue and you're willing to risk hurting your motor. In my case i'm fairly certain its an issue with my ECU (though my ECU is not in the range of VINS the TSB says is effected) I've had no symptoms of logs to indicate there is a problem, just a code.

Since then I've put a few thousand more miles and ran a few drift events without a problem.

I've read a few other posts of people having the same problem, some after a fresh motor/rebuild so they just disabled it.

I'm in the camp of when/if it blows it will be time to get a built motor.

Car seems to be running smoothly. No issues with idling or when I get on the throttle. My car is also an early '13 which I believe are the ones affected.

Guess I'll take it into the dealer and see what they'll do. I don't have the cable to re-flash back to stock though. Think it'd matter since there's already the TSB on the issue?

Sent from my Nexus 6P using Tapatalk

[Shady195]

Originally Posted by Teseo

Yea, but if flashing to stock and code persist then its a mechanical issue. Asking because i have same cal id

Not true at all, its an issue within the ECU itself, unrelated to the tune. Flashing back to stock/different tune is no real indication of whether its a mechanical failure or an ECU failure. I belive its strictly an ECU problem for me, I have no other codes or symptoms that those with mechanical issues noted.

Originally Posted by TheStig85

Car seems to be running smoothly. No issues with idling or when I get on the throttle. My car is also an early '13 which I believe are the ones affected.

Guess I'll take it into the dealer and see what they'll do. I don't have the cable to re-flash back to stock though. Think it'd matter since there's already the TSB on the issue?

Sent from my Nexus 6P using Tapatalk

Definitely flash it back to stock before going to the dealer, first off because its a reason for them to deny you warranty work as flashing an ECU is 100% a void of warranty..

Also, if there is some chance its not your ECU and they try to flash/update it, its possible they could brick it, and upon investigating if they find its flashed you will have to pay out of pocket for a new one.

[Ragin Gti]

The dealer can still tell if it's ever been flashed even if you flash it back to stock. Try to find TSB 02-163-16R. It's 29 pages of diag for AVCS codes.


Sent from my iPhone using Tapatalk