I have a 2006 Element, 2wd with a 5 speed manual trans and 125k miles. The check engine light was coming on for several months, but was turning off on its own too without any repair. But for the last few months, the check engine light has been on continuously. We have checked the codes several times and are repeatedly p0010 and p1009. I replaced the camshaft positioning sensor, being told that that should fix the problem. But it did not. My oil level is fine and it doesn't appear to be dirty either. I have seen that maybe cleaning the VTC strainer may help, but it seems to be a pain to get to, requiring that I remove the power steering pump it get it out. Was wondering if anyone else has had this problem too and if they know how to fix it. I'm at my wits end with this car!

 

I have the same year Element throwing the same p1009 code and I would really love to hear what ended up being the solution to your problem over a year ago. Please let me know! Thanks, Ryan

 

Easiest thing to do will be unplug the vtc control solenoid and measure resistance between both pins. At room temp it should be within 6.75-8.25 ohms. If it's out of spec you will need a new solenoid. If it's in spec check pin 1 black wire at connector to ground to verify harness side is good. If those check good you will most likely need to take to a mechanic as there are multiple wire checks to and from pcm with scs line shorted. The other thing to check is the vtc screen filter located on front of block behind the tensioner, make sure it's not clogged.

 

The crazy thing is that- When I got back in my car after getting the great advice I received on this site, the check engine light had gone off, without me resetting it. So I guess for now, I am not going to worry about it. That said, it has come on two separate times after I had reset it, so I am not convinced I should wait it out. What do you think??

 

you can replace the vtc screen filter on the front as it is relatively cheap and is usually a prone spot for oil leak . it can be very frustrating and time consuming testing intermittent failures. With that said, I would wait til it codes again and then diagnose.