P0016 on a 60k mile car

[ermax]

Originally Posted by ninjabutt

Ok thanks. is this screenshot from techstream or from obdlink? I plugged my obdlink in this morning before the baby woke up but didn't see these options.



I know you said that the values are likely only available through techstream but this looks like a cell phone screenshot and I was under the impression that I would be using techstream with my laptop.

Edit: thanks again for any help, I'll do more digging during naptime later today

The "learned values" you were talking about are only visible in Techstream.

[armstrom]

Well, I'm now a member of the club. Filled up with gas this morning and pulling out of the station CEL came on. Pulled P0018 Just read all 33 pages of this thread so at least I have a decent idea of where to start. Car is a '13 BRZ w/ 47k miles. I bought it as a certified used subaru so it came with a 7yr/100k powertrain warranty. I'm going to take it to the dealer to see if they will do the repair under warranty or not. If not, guess I'm digging in!

[armstrom]

Just as a follow-up. Someone pointed out to me that if your car falls within the VIN range for the valve spring recall you may be able to get the dealer to replace the cam gears for the price of parts even if you're out of warranty. Considering all those parts have to be removed to do the valve spring replacement anyway... Of course, this doesn't take into account the engine failures some people are reporting after the valve spring recall.. but it's an option.

[flyboy]

Deleted!

[ninjabutt]

Ok so I've been trying to get my laptop to run techstream in my spare time, after a while I figured out how to do the 64 bit workaround for the j2534 cable but my laptop didn't have any usb2.0 ports and said it couldn't read them so I bought a different cheap laptop, ended up being 32bit so I'm running techstream now and able to connect to the ECU but whenever I ask for the data list, the program shuts down. Anyone have the same issue?

I have another ECU to put in but I'd really like to get my initial learned values before swapping in the new ECU, then I can follow the new ECU to see if they drop out of range over time

[Ultramaroon]

Originally Posted by ninjabutt

I have another ECU to put in but I'd really like to get my initial learned values before swapping in the new ECU, then I can follow the new ECU to see if they drop out of range over time

Very nice plan. Would love to see results when you get the software issue worked out. Bummer about the app failing. What version do you have? It seems like there are many flavors floating around.

[ninjabutt]

V13.something. I'm trying to get up with a friend to borrow his cable to see if it's the cable or the computer and I have another friend with ecuflash that offered to throw a tune on while we were checking, just gotta find the time to get out to them lol.

[ninjabutt]

Just an update, I got techstream to run on my other laptop but it shuts down every time I try to pull the data list. I'm trying to get it running non my home PC when I can grab a few minutes off work and baby duty but so far the v13 won't recognize the xhorse as an option for VIM select so I uninstalled and reinstalled v8 that was in the write-up but my windows 10 won't run the firmware diagnostics tool so I can't confirm the drivers are installed correctly. It's not showing up in yellow on the device manager and it says all the drivers are being pulled from the xhorse mvci folder so I'm not sure what's going on. I'd like to help with the flowchart for fixing this problem but I'm real close to just throwing new parts on and seeing what happens. Wrenching is so much easier than waiting for computers to load lol.

[ninjabutt]

A good news (?) Update, I installed version 8 from the write-up on my 32 bit laptop and was able to pull the ILVs

[ninjabutt]

[Ultramaroon]

Originally Posted by ninjabutt

A good news (?) Update, I installed version 8 from the write-up on my 32 bit laptop and was able to pull the ILVs

Looking good


edit: Well, looking good in the sense that P0016 matches up with the bank 1 intake ILV drifting out of whack.

[ninjabutt]

Haha yeah, sad but true! Anyway, I thought of an additional benefit to properly diagnosing (or at least what I think will be properly diagnosing) the issue is that I'll be able to look at the number for bank 2 while I'm watching the bank 1 number to see if they're falling. This way I won't waste money on prematurely/unnecessarily swapping bank 2 if it's not necessary. Cam gear cost is now $210 after tax/shipping so I may do it anyway, just to get the updated cam gear in case the fault on the old design is a single event failure and could happen at any time in the future.

[Ultramaroon]

Originally Posted by ninjabutt

Haha yeah, sad but true! Anyway, I thought of an additional benefit to properly diagnosing (or at least what I think will be properly diagnosing) the issue is that I'll be able to look at the number for bank 2 while I'm watching the bank 1 number to see if they're falling. This way I won't waste money on prematurely/unnecessarily swapping bank 2 if it's not necessary. Cam gear cost is now $210 after tax/shipping so I may do it anyway, just to get the updated cam gear in case the fault on the old design is a single event failure and could happen at any time in the future.

If you really want to go deep, just take apart that phasor, clean it, and put it back together. That's precisely what I would do in your situation.

I remain convinced that in all these cases a small particle of schmutz makes its way into the spool valve to block its operation. I felt it the first time I tinkered with my friend's engine.

[ninjabutt]

I like that idea, but I don't have enough desire to pull the timing cover twice if it doesn't work.

Another note, I got the replacement ECU in and the ILVs are within spec so I'm driving it to work and when I get home tonight I'll recheck the ILVs and see if they have moved.

Another note lol, Im getting a u0155 code so I'm unable to drive past 3500 RPMs. When attempting to change the VIN before putting the ECU in comms mode, this code was there. Hopefully it will go away within a few cycles. Of not, more digging.