WTF!?! Random misfire happening around 3k RPMs at 71-74 MPH in 5th gear only.
#18
Evolving Member
Thread Starter
Sorry I have not been on to updated later, I just got back from a detachment. Anyhow, I changed out the coil packs and it has not misfired again. .... Yet. So hopefully it is good to go. I will post back up if something happens.
#19
Evolving Member
Thread Starter
Well, I guess the coil packs did not fix the problem. My car started misfiring again today. It is happening the same as before and this time I tried holding the RPMs steady at 3 to 3.5K in 3rd, 4th, and 5th gear. It misfired in all gears. I have no idea what is wrong. Does anyone else have any ideas?
#22
Evolving Member
iTrader: (3)
How do you know that you are misfiring??
Unless I miss my guess your knock sensor is hearing the transmission and thinks that it is knock and retards the timing to save the engine. Releasing the throttle and getting back on it will temporarily fix this while driving, correct?
I believe there is a TSB for this, but the dealership will want to reflash your ECU first. The other option to fix this, would be a transmission rebuild. I'm not exactly sure what it is that needs replaced in the transmission. Hope this helps.
Unless I miss my guess your knock sensor is hearing the transmission and thinks that it is knock and retards the timing to save the engine. Releasing the throttle and getting back on it will temporarily fix this while driving, correct?
I believe there is a TSB for this, but the dealership will want to reflash your ECU first. The other option to fix this, would be a transmission rebuild. I'm not exactly sure what it is that needs replaced in the transmission. Hope this helps.
#23
Evolving Member
Thread Starter
So if your guess is right, I should be able to unplug the knock sensor and be great then right? The TSB is listed here, and from what I can tell, it is to fix the P0300 code that randomly pops. http://www.lancerlogic.com/forum/eng...m-misfire.html I also tried the troubleshooting listed in this TSB (disengage/re-engage the clutch at highway speed to trigger the "code") This did not work. But, I will try driving with the knock sensor unplugged the next couple times that I go driving and see if the misfiring stops.
Last edited by dave3kgt; May 8, 2009 at 05:53 AM.
#24
Evolved Member
iTrader: (42)
Join Date: Feb 2007
Location: Utah
Posts: 758
Likes: 0
Received 0 Likes
on
0 Posts
So if your guess is right, I should be able to unplug the knock sensor and be great then right? The TSB is listed here, and from what I can tell, it is to fix the P0300 code that randomly pops. http://www.lancerlogic.com/forum/eng...m-misfire.html I also tried the troubleshooting listed in this TSB (disengage/re-engage the clutch at highway speed to trigger the "code") This did not work. But, I will try driving with the knock sensor unplugged the next couple times that I go driving and see if the misfiring stops.
#26
Evolved Member
iTrader: (38)
Have you tried upgrading your ROM from 0008 to 0015?
This was Mitsu's fix for the P0300 back in 04 when all the 03's were going back to the dealer for the code. Mitsu found out that the code is actually triggered by drivetrain harmonics.
A couple other cause were as other stated. Large jumps in timing from one cel to another. Too much timing in those cruising load cells. If it comes down to it just disable the test routine in the ROM and you'll never see the code again
This was Mitsu's fix for the P0300 back in 04 when all the 03's were going back to the dealer for the code. Mitsu found out that the code is actually triggered by drivetrain harmonics.
A couple other cause were as other stated. Large jumps in timing from one cel to another. Too much timing in those cruising load cells. If it comes down to it just disable the test routine in the ROM and you'll never see the code again
#27
Evolving Member
Thread Starter
Well, thats the problem. I am not only experiencing the code, but also the associated misfire. The car literally loses power, and starts to sound like a sick Subaru. Still think it can be the ROM? If so, where could I download a 0015 ROM?
#29
Evolved Member
iTrader: (67)
Join Date: May 2006
Location: FL
Posts: 753
Likes: 0
Received 0 Likes
on
0 Posts
Have you tried upgrading your ROM from 0008 to 0015?
This was Mitsu's fix for the P0300 back in 04 when all the 03's were going back to the dealer for the code. Mitsu found out that the code is actually triggered by drivetrain harmonics.
A couple other cause were as other stated. Large jumps in timing from one cel to another. Too much timing in those cruising load cells. If it comes down to it just disable the test routine in the ROM and you'll never see the code again
This was Mitsu's fix for the P0300 back in 04 when all the 03's were going back to the dealer for the code. Mitsu found out that the code is actually triggered by drivetrain harmonics.
A couple other cause were as other stated. Large jumps in timing from one cel to another. Too much timing in those cruising load cells. If it comes down to it just disable the test routine in the ROM and you'll never see the code again
I have a real good theory on this but need to find out what clutch you are running first but driveline harmonics are the root cause as stated above
Where can we get 0015 for download?
#30
Evolved Member
iTrader: (7)
definately not the rom. I did not read through the entire thread but from what I have gathered the car drops a cylinder under load. I know you mentioned getting new coil packs but did you replace plugs and wires? Plugs are kind of obvious but if you ever pulled the plug wires off the plugs by the wire you can ruin them ( learned the hard way ) it is nearly impossible to spot where they are damaged but id be willing to bet plug wires is your issue