follow ft86club on our blog, twitter or facebook.
FT86CLUB
Ft86Club
Delicious Tuning
Register Garage Members List Calendar Search Today's Posts Mark Forums Read

Go Back   Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB > Technical Topics > Engine, Exhaust, Transmission

Engine, Exhaust, Transmission Discuss the FR-S | 86 | BRZ engine, exhaust and drivetrain.


User Tag List

Reply
 
Thread Tools Search this Thread
Old 02-20-2017, 10:22 AM   #15
Shady195
Senior Member
 
Join Date: Jun 2014
Drives: '13 10 Series FRS #1203
Location: Albany, NY
Posts: 850
Thanks: 7
Thanked 385 Times in 220 Posts
Mentioned: 5 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by Ragin Gti View Post
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
Also true, though I don't think I've heard of anyone as of yet get denied warranty work for it?
Shady195 is offline   Reply With Quote
Old 02-20-2017, 12:41 PM   #16
Ragin Gti
Member
 
Join Date: Jan 2017
Drives: '15 Subaru BRZ
Location: Pittsburgh
Posts: 93
Thanks: 8
Thanked 58 Times in 35 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Correct. Technically they have to prove that the flash caused the failure. If they deny a claim calling SOA and complaining they'll often "goodwill" the repair and tell the dealer to fix it anyway.


Sent from my iPhone using Tapatalk
Ragin Gti is offline   Reply With Quote
Old 02-20-2017, 02:01 PM   #17
sw20kosh
Senior Member
 
Join Date: Jul 2012
Drives: 2013 Black FR-S
Location: SF
Posts: 3,030
Thanks: 881
Thanked 2,014 Times in 990 Posts
Mentioned: 153 Post(s)
Tagged: 1 Thread(s)
Quote:
Originally Posted by Shady195 View Post
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.
@CSG Mike @CounterSpaceGarage @CSG David
__________________
sw20kosh is offline   Reply With Quote
Old 02-20-2017, 02:11 PM   #18
sw20kosh
Senior Member
 
Join Date: Jul 2012
Drives: 2013 Black FR-S
Location: SF
Posts: 3,030
Thanks: 881
Thanked 2,014 Times in 990 Posts
Mentioned: 153 Post(s)
Tagged: 1 Thread(s)
My 2015 BRZ starting having Cam related codes in early 2016. No physical symptoms and the cams were responding fine (not lazy) so the codes were just cleared every time they came up.

Then late 2016 the cam control would be turned off by default every time when starting up the car even if no codes were thrown. Letting the car idle for a few minutes after cold start would wake up the cams.

Early 2017 a freshly built motor was dropped in retaining the (2013) donor motor's cam hardware (the 2013 cam gears/sprokets were inspected thoroughly). The cam control will not come online at all. Is this most likely an ecu issue (the ECU was not changed during the engine swap)?
__________________
sw20kosh is offline   Reply With Quote
Old 02-21-2017, 01:07 AM   #19
RedFRS4me
Senior Member
 
RedFRS4me's Avatar
 
Join Date: Nov 2013
Drives: Firestorm '13
Location: Portland, OR
Posts: 102
Thanks: 4
Thanked 26 Times in 16 Posts
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Garage
I had a p0018 code recently. Cam sprocket was mechanically broken upon examining them according to dealership. I knew it had to be it because during troubleshooting I watched my intake and exhaust VVT after wiping the code. As soon as the codes came back on after 2 restarts, I noticed my exhaust VVT went dead zero degrees. Toyota confirmed it as well, cam sprocket bad on the exhaust VVT It had to be replaced and when I picked it up, I drove it for 3 minutes and lights came on again. Toyota tested the ECU and it was out of spec and was replaced. Everything has been good since then. My guess is once the ECU is hit with the p0016-p0019 codes the ECU is toast and will likely need replacement to rid of the code even after the mechanical issue was repaired.
__________________
'13 Firestorm
RedFRS4me is offline   Reply With Quote
Old 02-21-2017, 07:22 AM   #20
Shady195
Senior Member
 
Join Date: Jun 2014
Drives: '13 10 Series FRS #1203
Location: Albany, NY
Posts: 850
Thanks: 7
Thanked 385 Times in 220 Posts
Mentioned: 5 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by RedFRS4me View Post
I had a p0018 code recently. Cam sprocket was mechanically broken upon examining them according to dealership. I knew it had to be it because during troubleshooting I watched my intake and exhaust VVT after wiping the code. As soon as the codes came back on after 2 restarts, I noticed my exhaust VVT went dead zero degrees. Toyota confirmed it as well, cam sprocket bad on the exhaust VVT It had to be replaced and when I picked it up, I drove it for 3 minutes and lights came on again. Toyota tested the ECU and it was out of spec and was replaced. Everything has been good since then. My guess is once the ECU is hit with the p0016-p0019 codes the ECU is toast and will likely need replacement to rid of the code even after the mechanical issue was repaired.
I honestly wonder if they actually were 100% confident that it was a mechanical issue, or just could not find anything wrong and replaced your cam assembly based on the codes.. Just about everyone i've heard that had an actual mechanical problem had drive ability issues to go along with it (stalling, jerkiness etc)

The reason I say that is because you more than likely have a VIN number out of the range that applies to the TSB for a known issue with the ECU's in relation to cam related codes. (as it was on 2013 models)

My gut tells me it wasn't until after it returned to its previous state (throwing codes) that they decided to look at the ECU.

It's no surprise when you had the codes that the cam's would sit inactive, the car goes into LIMP Mode and while i'm not sure completely what that entails as far as the ECU is its quite possible it kept the VVT system from being active as a precaution.
Shady195 is offline   Reply With Quote
Old 02-22-2017, 02:27 PM   #21
TheStig85
Senior Member
 
Join Date: Jan 2013
Drives: 2013 Subaru BRZ
Location: Miami, FL, USA
Posts: 125
Thanks: 97
Thanked 22 Times in 17 Posts
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Garage
Quote:
Originally Posted by Ragin Gti View Post
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
I've tried searching for this TSB with no luck. Do you know where I can find it?
TheStig85 is offline   Reply With Quote
Old 03-21-2017, 02:16 PM   #22
Shady195
Senior Member
 
Join Date: Jun 2014
Drives: '13 10 Series FRS #1203
Location: Albany, NY
Posts: 850
Thanks: 7
Thanked 385 Times in 220 Posts
Mentioned: 5 Post(s)
Tagged: 0 Thread(s)
Update:

Since moving to ECUTek the error code is completely gone. I've put about ~1500 miles on my car since getting rid of my OFT and switching over to ECUTek on my turbo build and have not had it pop up on me once.

I don't think the OFT itself was the cause of it, but seems weird to me that I was consistently getting this code with the OFT within 5 miles of driving if I re-enabled it, and have not had it happen again since my move to ECUTek...
Shady195 is offline   Reply With Quote
Old 03-21-2017, 04:22 PM   #23
sw20kosh
Senior Member
 
Join Date: Jul 2012
Drives: 2013 Black FR-S
Location: SF
Posts: 3,030
Thanks: 881
Thanked 2,014 Times in 990 Posts
Mentioned: 153 Post(s)
Tagged: 1 Thread(s)
Quote:
Originally Posted by Shady195 View Post
Update:

Since moving to ECUTek the error code is completely gone. I've put about ~1500 miles on my car since getting rid of my OFT and switching over to ECUTek on my turbo build and have not had it pop up on me once.

I don't think the OFT itself was the cause of it, but seems weird to me that I was consistently getting this code with the OFT within 5 miles of driving if I re-enabled it, and have not had it happen again since my move to ECUTek...
I have an ecutek tune and constantly have cam issues/codes.
__________________
sw20kosh is offline   Reply With Quote
Old 03-21-2017, 10:10 PM   #24
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
Quote:
Originally Posted by Shady195 View Post
Update:

Since moving to ECUTek the error code is completely gone. I've put about ~1500 miles on my car since getting rid of my OFT and switching over to ECUTek on my turbo build and have not had it pop up on me once.

I don't think the OFT itself was the cause of it, but seems weird to me that I was consistently getting this code with the OFT within 5 miles of driving if I re-enabled it, and have not had it happen again since my move to ECUTek...
Quote:
Originally Posted by sw20kosh View Post
I have an ecutek tune and constantly have cam issues/codes.
agree the tune system will not be an issue, but the cam timings used or the rate of change of cam timing may be a factor in the ecu triggiering the cam code if it senses the requested cam position is not matching the measured cam position within a certian time or correct correlation. OFT NA tunes for EL header (and a lot of other NA tunes by other tuners) use quite agressive cam timings and high rates of change, its probably a lot less on turbo tunes
steve99 is offline   Reply With Quote
Old 03-22-2017, 08:11 AM   #25
Shady195
Senior Member
 
Join Date: Jun 2014
Drives: '13 10 Series FRS #1203
Location: Albany, NY
Posts: 850
Thanks: 7
Thanked 385 Times in 220 Posts
Mentioned: 5 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by steve99 View Post
agree the tune system will not be an issue, but the cam timings used or the rate of change of cam timing may be a factor in the ecu triggiering the cam code if it senses the requested cam position is not matching the measured cam position within a certian time or correct correlation. OFT NA tunes for EL header (and a lot of other NA tunes by other tuners) use quite agressive cam timings and high rates of change, its probably a lot less on turbo tunes
My car was turbo before as well..

Really the only thing that changed was the move to ECUTek and the flex fuel setup.
Shady195 is offline   Reply With Quote
The Following User Says Thank You to Shady195 For This Useful Post:
steve99 (03-22-2017)
Old 03-22-2017, 07:13 PM   #26
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
Quote:
Originally Posted by Shady195 View Post
My car was turbo before as well..

Really the only thing that changed was the move to ECUTek and the flex fuel setup.

different tune on ecutek ? , maybe cam timing or cam rate of change different ?
steve99 is offline   Reply With Quote
Old 12-30-2017, 02:01 AM   #27
ApexEight
Senior Member
 
Join Date: Apr 2017
Drives: 2014 Subaru BRZ Limited 6MT SSM
Location: Atlanta, GA, USA
Posts: 293
Thanks: 195
Thanked 68 Times in 54 Posts
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Thread revival.

So I just got my first P0016 on my 2014 BRZ 6MT (build dat 09/13). It has 80K miles on it. I've had the car for the last 5K and it's the first time I've gotten the code.

Bumping this thread because it seems the most relevant to what I'm experiencing.

Once I got the code, I pulled over and cleared it. Didn't come back up and the car drove strong.

Got home and did some reading. Fired her back up and drove around the block and the code came back. The car idles perfectly and isn't exhibiting any strange behavior that would lead me to think there is an impending mechanical failure.

Is it safe to drive 30 miles to my brothers garage? I'm going to swap cam sensors and if that doesn't work change the oil. If I still get the code what's the best next step? ECU replacement? Don't want to crack open the front cover and change a sprocket if I can just do an ECU swap. Which ECU should I be looking for? Thanks in advance
ApexEight is offline   Reply With Quote
Old 12-30-2017, 06:55 PM   #28
ApexEight
Senior Member
 
Join Date: Apr 2017
Drives: 2014 Subaru BRZ Limited 6MT SSM
Location: Atlanta, GA, USA
Posts: 293
Thanks: 195
Thanked 68 Times in 54 Posts
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Update: swapped cam sensors and still got the P0016. Swapped OVCs and same thing. Thr plungers on the OVCs seemed to actuate smoothly.

The car still drives perfectly with a perfect idle, but it's clearly in limp mode. Didn't get a chance to change the oil but I don't see how 4.5K 0W-40 would cause this.

I'm thinking I need to just spring for a 15+ ECU now... Any input before I pull the trigger? Thanks.
ApexEight is offline   Reply With Quote
 
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
P0016 fixable without new ECU? Mr.Jay Issues | Warranty | Recalls / TSB 8 02-06-2022 05:15 AM
P0016/P0017 cause AVOturboworld Issues | Warranty | Recalls / TSB 18 04-16-2021 11:09 PM
p0016 need help asap lol Issues | Warranty | Recalls / TSB 25 10-30-2018 03:49 PM
p0016 issue Djratrap Issues | Warranty | Recalls / TSB 43 06-06-2017 01:27 AM
OFT P0016 and TSB question mmmcambelsoup Software Tuning 10 05-24-2017 09:24 AM


All times are GMT -4. The time now is 05:11 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.

Garage vBulletin Plugins by Drive Thru Online, Inc.