![]() |
Cam/Timing Sprocket Replacement?
I didn't get any answers from the last post about codes so I'm not holding out much hope that there is anyone on this forum that's done more than swapping headers or injectors/tunes, but one last try. I am getting a p000a code for camshaft A slow to respond bank 1. My question is this. Since this is the intake cam on passenger side, would it be acceptable to only remove the right timing chain, keeping the engine in time and switch the intake sprocket? Provided that the camshaft A is the only affected part, ensure that it is set to it's proper timing marks, reinstall chain and ensuring that all timing marks are still aligned, seal it up and it will be good to go? This seems like an easier way to go rather than resetting entire timing set. Have yet to find any info on the procedure but I'm assuming there is a tool that will lock camshaft in place while performing this task however I don't seem to find any specific toolset for timing the FA20 in a BRZ/FR-S. Any help is greatly appreciated.
|
Ask better questions, get better answers. There is literally a thread discussing cleaning the internals of the sprockets recently active. So obviously there are quite a few of us who have cracked these open.
Yes, you can do one bank at a time as each bank has it's own timing chain and tensioner. Though if you have one cam sprocket doing it you should probably replace all. It is caused by contamination. I would also pull the cam carrier off the head and check the VVT filters in the oil passageway. Those can get plugged too. I would personally swap VVT solenoids around first and see if the problem moves before pulling the engine. |
I'm not trying to be an asshole......I thought my questions in my previous post that still has yet to be answered was pretty straight forward. Is there a diagnostic procedure to give a definitive cause to this code or do I start firing the parts cannon? As I stated in my previous post, I already swapped solenoids and the code stayed with cam A bank 1. I also swapped CPS with the same result. I do also have a simultaneous code C1201. Trying to determine which is causing the other. I have no interest in cleaning the VVT. I'll simply replace it. I appreciate the reply, I'm a BMW and Ford guy. I've been around the block a few times with timing on those makes. Just trying to get my bearings with these FA20 engines. The only thing I have yet to try is an engine flush. I have a bottle of LiuqiMoli Flush but I'm not a fan of anything that compromises the integrity of lubricating properties. This is a fairly low mileage engine (51000). Again thanks for the reply and if I'm not specific enough please just let me know what other info you need....I will gladly supply it if I'm able. That's why we are all here.
|
Quote:
From some quick googling C1201 has come up do to runnability issues in other threads so I would focus on the P0000A and not worry about that code. Here is an example on that caused by a P0301. https://www.ft86club.com/forums/showthread.php?t=32484 There are some confirmation driving pattern procedures that can be done but you need techstream to do it and have no experience with techstream. They look like they are just confirmations tests after attempting fixes. The listed fixes are: move/replace vvt solenoid(done) engine flush valve timing(doubt this has jumped) oil control valve filter cam gear ecu I'd try the flush next. If that doesn't work it sounds like it's either the OCV filter or the cam gear. To me I would check both at the same time due to how far you have to take the engine apart to check either. Might as well check valve lash while in there too. As far as any other less intrusive tests I don't really have much idea. It doesn't seem like a common code that pops up. A lot of the threads on it are dead ends. |
| All times are GMT -4. The time now is 08:06 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by
Advanced User Tagging v3.3.0 (Lite) -
vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.