Very Odd P300 Issues ... any insight?
Try the old Vishnu approach; buy a C-reader for $40, plug it in and leave it. Voila, no more p0300. Your knock cel flash will still work, so you can monitor what the engine is doing. I know it's more of a bandaid, but it works.
I am wondering if it is a flaw in either the criteria for the code or an issue with the maf?
Reason being is that 1) When the code sets, it states it happened at 80% plus throttle postion, and 2) is says Intake temp is 36F or less even on hot days.
Maybe there is a sensor failure or something like that? Ideas?
Reason being is that 1) When the code sets, it states it happened at 80% plus throttle postion, and 2) is says Intake temp is 36F or less even on hot days.
Maybe there is a sensor failure or something like that? Ideas?
Were you able to try another code scanner as I suggested? I think the odd codes are from ScanTech and not the actual data from the ECU. If the actual freeze frame were wrong, it would be several sensors acting up ... mainly the MAF and TPS. Though, TPS is a possibility with the large TB.
Either way, it's unlikely as the logged values are in line with each other. Sensor issues that severe would be visible in the logs.
Either way, it's unlikely as the logged values are in line with each other. Sensor issues that severe would be visible in the logs.
I have been told that some clutches cause vibrations that can trigger a p0300... mine started right after stepping up to 880cc injectors/65mm TB and ported intake mani (all installed at same time)... drives great, but makes me wonder how well the injectors were installed tho or if there is some type of leak around them which i have heard can trigger p0300... also check plugs, coil pack etc... wish I knew how to permanently get rid of it, because my SES light is damn annoying and I will have issues with it come emmisions testing time!!!
I would agree, BUT this issue isnt when the clutch is depressed allowing the plates to chatter. No fuel leaks from the injectors. Interesting that your started when you installed the throttle body and ported intake mani. Is there anyone else that has noticed the p0300 after installing either of those parts?
going along with the sensor failing route... you mentioned that the intake temps were recording low, very low compared to the actual temps.
I guess it would be possible that if the intake sensor is failing intermitantly, you could get the wrong timing and fuel correction, and that might result in the p0300. Have you verified that the sensor is working correctly?
I guess it would be possible that if the intake sensor is failing intermitantly, you could get the wrong timing and fuel correction, and that might result in the p0300. Have you verified that the sensor is working correctly?
I have both checked the sensor with the MUT2 and my ScanTech. At the time of the realtime readings, the temp and throttle sensors are all inline where they are suppose to be.
I have noticed that the Scantech with pick up on a P0000 code when ever the P0300 sets or is in the pending codes. MUT2 will not pick up a P0000. The code # does not exisit
I have noticed that the Scantech with pick up on a P0000 code when ever the P0300 sets or is in the pending codes. MUT2 will not pick up a P0000. The code # does not exisit
I have both checked the sensor with the MUT2 and my ScanTech. At the time of the realtime readings, the temp and throttle sensors are all inline where they are suppose to be.
I have noticed that the Scantech with pick up on a P0000 code when ever the P0300 sets or is in the pending codes. MUT2 will not pick up a P0000. The code # does not exisit
I have noticed that the Scantech with pick up on a P0000 code when ever the P0300 sets or is in the pending codes. MUT2 will not pick up a P0000. The code # does not exisit
I threw a P300 after I put in a twin disc clutch and flywheel. I did the TSB it fixed it for 2 weeks and then came back on. I decided to have my transmission and transfercase rebuilt by TRE. They replaced my input shaft with a Evo 9 input shaft and 5th gear. Now I only throw that code when I'm in 5th gear and only when I go over 100mph and slow down past 80mph, and after a couple of days the code will just go away until I do the same thing. I only have basic bolt-ons, intake, exhaust and boost controller.
I had this happen to a customers car...the car would throw the P0300 under light acceleration @ low RPMs....no matter how much we tried to remedy this the condition still existed...
It ended up being a broken Crank Angle sensor from when the timing belt job was done...One of the bolts were over torqued cracking the sensor housing....
Good Luck.
It ended up being a broken Crank Angle sensor from when the timing belt job was done...One of the bolts were over torqued cracking the sensor housing....
Good Luck.
The manual referes to something like adaptive learning:
"The adaptive learning has been completed with the vane that generates the crankshaft position signal"
What does this mean - could it be that we screw up some RAM area during one of the reflashes and the witout the proper learning procedure - it just creates problems?
"The adaptive learning has been completed with the vane that generates the crankshaft position signal"
What does this mean - could it be that we screw up some RAM area during one of the reflashes and the witout the proper learning procedure - it just creates problems?
Alrighty ... I'll be sending a new ROM over tonight. I'll try 0-ing out the EGR related advance again with the newly increased timing. That's all I can think to do. Will, what are the chances of trying a new crank position sensor?


