Aug 17, 2004 | 10:47 AM
  #16  
Quote: The knock sensor isnt involved. Please we arent here to argue Ive seen plenty of other tuners cars with 0300s.
Dave,

Well, I guess you don't know me as well as Shiv or Brett as you would know I have better things to do than to troll my #1 tuning shop.

In any case, I will never try to argue this topic. I just want an understanding of it all. I haven't gotten the P0300 code and hopefully won't ever get it. The fact that you could get it at any time during the entire lifecycle of owning the car is very scary.

I was under the impression from posts that Dynoflash *has* a fix for it. And the guy at that company definitely stated that Buschur also had the fix - both reflashable.

-Marlin
Aug 17, 2004 | 11:01 AM
  #17  
At first Al thought he had fixed the P0300 code, then admitted that he hasn't...

https://www.evolutionm.net/forums/sh...134#post997134
Aug 17, 2004 | 11:08 AM
  #18  
Quote: At first Al thought he had fixed the P0300 code, then admitted that he hasn't...

https://www.evolutionm.net/forums/sh...134#post997134
Ah!! That clears things up then! Didn't read that.

Thanks. So what is *actually* causing this misfire code?

-M
Aug 17, 2004 | 11:35 AM
  #19  
cam angle sensor?
Aug 17, 2004 | 12:15 PM
  #20  
Some say it's due to a resonance from the tranny that the engine is picking up as knock, but I don't know for certain...
Aug 19, 2004 | 08:34 PM
  #21  
;(
Aug 19, 2004 | 08:38 PM
  #22  
I get the 0300 every few weeks and know how to reproduce it. It is not big deal at all, even my friend who is a Mitsu tech said other Mitsu's have the same problem and the sensor picks up noise and throw's it. There is one turn on the way to work where I can get the 0300 everytime, it seems like 3-4th gear at high RPM turning lol. If you don't get it don't worry about it, if you start to get it just thank Shiv for the only one having a REAL fix for it, everyone else just tries.



Quote: Ah!! That clears things up then! Didn't read that.

Thanks. So what is *actually* causing this misfire code?

-M
Aug 19, 2004 | 10:20 PM
  #23  
Aug 20, 2004 | 05:36 AM
  #24  
I agree that the PO300 code itself is not a big deal. But if the light is on for that you wouldn't know if the car is throwing another legit code (in the absence of outward symptoms of course).
Aug 20, 2004 | 08:06 AM
  #25  
Shiv,

Are you going to come up with a solution to the misfire code for our cars with just your Xflash?
Aug 20, 2004 | 09:16 AM
  #26  
I got it for one tank of gas after my custom tune, and have gotten it like twice since. Only on crappy gas and under heavy load conditions though, since I've switched haven't had the problem since.
Aug 20, 2004 | 09:32 AM
  #27  
Shiv since my updates with the idle issue i have not gotten that po300 code. Did you also update my car with this fix already or is my car just a happy camper right now. That 420 (no cat) is going crazy though. No fix for that I guess except for the obvious.
Aug 20, 2004 | 12:48 PM
  #28  
My car runs fine no codes
Aug 20, 2004 | 12:56 PM
  #29  
Funny I ran 12.2s all day with the check engine light on. I was too lazy to reset and the car was hauling a$$ down the track so why should I reset.
Aug 23, 2004 | 01:13 PM
  #30  
Quote: Well, we think we found a fix. At least on the car we have been playing around with. But to confirm things, we'd like to test it on more EVOs. So if anyone local has cronic (more cronic the better) P0300 issues, PM me and we can try something out on your car. It involves a quick diagnostic and a few runs of dyno testing. All free of charge.

This "fix" is done through the XEDEFlash and XEDE so you will need to be equipped with both items. This fix does not apply to XFlash-only cars since a good portion of the "fix" in incorporated in the XEDE hardware. I'm putting "" around "fix" until we can confirm that it is indeed a fix But we're pretty hopeful...

Regards,
shiv
sent you a PM