PCM

Victor Technician Glendora, California Posted   Latest   Edited  
Question
Driveability
2006 Toyota Tacoma 4.0L (1GR-FE) 4-spd (A340E)
P0606 - Control Module Processor

P0606 with no driveability concerns. Anybody out there come across this before? Looking for a direction to go on this one. 

0
Chris Diagnostician
Bryans Road, Maryland
Chris Default
 

I think you are missing some information

+4 Default Ð Bounty Awarded
Victor Technician
Glendora, California
Victor Default
 

Chris, you are correct, updated it. Thanks

0 Default Ð Bounty Awarded
Steven Technical Support Specialist
Commack, New York
Steven Default
   

I would check the rear o2 sensors and wiggle the wires.. I have seen a faulty o2 sensor trip this code before.. And I have also seen rear double filament brake light bulbs with one shorted to the other cause this code once.. But a majority of the time it usually played out to be a bad heater or wiring on a rear o2

+1 Default Ð Bounty Awarded
Danny Technician
Losangeles, California
Danny Default
 

Does the code reoccur immediately after clearing the code? I had a 2008 Toyota RAV4 that would set that P0606, but would also set a P0138 B1S2 O2 Sensor Signal high. Replacing the O2 sensor fixed the P0138, and the P0606 hasn't reoccurred. There is a post by Robert Powell on another forum where he documents that a bad post cat O2 sensor caused a P0606.

+2 Default Ð Bounty Awarded
Victor Technician
Glendora, California
Victor Default
 

Throws the code very randomly. No other codes

0 Default Ð Bounty Awarded
Bob Owner/Technician
East Longmeadow, Massachusetts
Bob Default
 

Victor, as Danny mentioned, I have seen this before and posted info on that "other" site. ;-) Use your scanner and graph all the O2 sensors and the impedance pids. Carefully wiggle and tug on the sensor wires where they enter the sensor and you may be able to induce the fault. If you do you, it will be very obvious on the scanner. I did it with the engine running.

+3 Default Ð Bounty Awarded
Dean Owner
Albany, New York
Dean Default
 

Go into mode 6 and see what o2 failed. Diagnose that o2. Do not replace the PCM.

+4 Default Ð Bounty Awarded
Pj Technician
Pleasant Hills, Pennsylvania
Pj Default
 

That code sets because the ECM knows that an oxygen sensor can't produce the voltage that it is seeing. Usually when an oxygen sensor signal wire is shorted to the signal circuit. So the ECM is seeing 12 volts from the oxygen sensor. In turn, the ECM thinks that it has an internal failure. But it is almost always an oxygen sensor. If you look in freeze frame, I'd bet you'd find an oxygen sensor…

+5 Default Ð Bounty Awarded
Jim Curriculum Developer
Frederick, Maryland
Jim Default
   

Excellent explanation. If you will allow me to add an observation on code set criteria. Early in a failure, one may see both the O2 and Logic codes since the performance of the sensor tests are getting erratic. The O2 related code sets then the 606 sets. If this is cleared and the ECU sees the irrational circuit value prior to the O2 monitors completing one will only likely see the 606 code. The…

+3 Default Ð Bounty Awarded
Victor Technician
Glendora, California
Victor Default
 

O2 monitors will run and pass even after the 606 is set.

0 Default Ð Bounty Awarded
Victor Technician
Glendora, California
Victor Default
 

Here’s my freeze frame.

0 Default Ð Bounty Awarded
Jim Curriculum Developer
Frederick, Maryland
Jim Default
 

What is the run time? I would graph the downstream sensors and the impedance PIDs during warm-up.

0 Default Ð Bounty Awarded
Victor Technician
Glendora, California
Victor Default
 

run time was 24 min

0 Default Ð Bounty Awarded
Michael Mobile Technician
Clinton, Utah
Michael Default
 

Victor, I would try hooking up to your gas analyzer and see what is coming out of the tailpipe. I have seen the AFR sensors (B1S1/B2S1) degrade at the same rate confusing the ECU. The fuel trims don't support this but stranger things have happened. B2S2 output is suspect. It should be closer to 700mV. -Mike

0 Default Ð Bounty Awarded