Bad Flash? Knock?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Bad Flash? Knock?
Hi Guys,
I am quickly coming to the conclusion that random cruise knock is caused by a "bad" flash.
Anyone have an experience with this?
ie sometimes you do a flash and you get 0 knock, then other times you do a flash and get 15 KS randomly when driving...
Cheers
D.
I am quickly coming to the conclusion that random cruise knock is caused by a "bad" flash.
Anyone have an experience with this?
ie sometimes you do a flash and you get 0 knock, then other times you do a flash and get 15 KS randomly when driving...
Cheers
D.
Last edited by tephra; Oct 22, 2009 at 04:09 AM.
Only way this would be possible is if your battery voltage was lower than desired during a flash?
Define a bad flash please....
I've had the random part throttle knock b4 at low rpm but haven't seen it in a while and I haven't changed anything in that area....I have done recent flashes thou tuning for new parts...
Define a bad flash please....
I've had the random part throttle knock b4 at low rpm but haven't seen it in a while and I haven't changed anything in that area....I have done recent flashes thou tuning for new parts...
Hi teph, I'm also experiencing some of these random knocks myself... it would be around 3-6 knocksums at 60-80% load (fuel), between 1250-1500 RPM. My car is completely stock using NJ's generic 91oct ROM (slightly tweaked). Since this is in closed loop and the timing at that range is stock, I can't blame it on the tune. I've tried lowering the timing by a degree in that troublespot and it has helped a lot, but still sometimes i see the occasional knocks. I would say averagely, 2 out of 5 days of driving (dd to work)... I would see it once.
I don't think the flash has anything to do with it, since flashing the ECU is ultimately in binary (like all digital hardware) and there are builtin safeguards (ie. checksum) to make sure data is intact upon flashing. I know for sure since I've been flashing the ECU close to 40 times (started from Gunzo's and a lot of tweaks up to this point)... this troublespot has always showed up in the logs occasionally no matter what generic/tweaked tune I put in.
I don't think the flash has anything to do with it, since flashing the ECU is ultimately in binary (like all digital hardware) and there are builtin safeguards (ie. checksum) to make sure data is intact upon flashing. I know for sure since I've been flashing the ECU close to 40 times (started from Gunzo's and a lot of tweaks up to this point)... this troublespot has always showed up in the logs occasionally no matter what generic/tweaked tune I put in.
Last edited by tipoytm; Oct 22, 2009 at 11:24 AM.
Hi teph, I'm also experiencing some of these random knocks myself... it would be around 3-6 knocksums at 60-80% load (fuel), between 1250-1500 RPM. My car is completely stock using NJ's generic 91oct ROM (slightly tweaked). Since this is in closed loop and the timing at that range is stock, I can't blame it on the tune. I've tried lowering the timing by a degree in that troublespot and it has helped a lot, but still sometimes i see the occasional knocks. I would say averagely, 2 out of 5 days of driving (dd to work)... I would see it once.
I don't think the flash has anything to do with it, since flashing the ECU is ultimately in binary (like all digital hardware) and there are builtin safeguards (ie. checksum) to make sure data is intact upon flashing. I know for sure since I've been flashing the ECU close to 40 times (started from Gunzo's and a lot of tweaks up to this point)... this troublespot has always showed up in the logs occasionally no matter what generic/tweaked tune I put in.
I don't think the flash has anything to do with it, since flashing the ECU is ultimately in binary (like all digital hardware) and there are builtin safeguards (ie. checksum) to make sure data is intact upon flashing. I know for sure since I've been flashing the ECU close to 40 times (started from Gunzo's and a lot of tweaks up to this point)... this troublespot has always showed up in the logs occasionally no matter what generic/tweaked tune I put in.
Going back to tephra's concerns, I don't see how a bad flash could cause knock unless the maps actually got screwed up when getting written. One way to double check is to re-read the ROM from the ECU and see if the timing and fuel maps etc all look ok. If the actual procedural code were messed up, then I don't think the car would run at all. I've flashed over 40 times and haven't seen any random knock like that aside from the low load/rpm knock coming from a stop.
^ Good to know someone else is experiencing this on a stock X.. and you even tested it out with the factory tune/ROM. I agree, a good way would be to test and compare the ROM by using the built-in ECUflash "compare to ECU" function also. Is Tephra getting the knocks in high-boost or WOT?
Did you guys check your fuel pump relay? Been several accounts of it failing and causing car to run lean and then knock. Anticipate a recall to hit eventually, but the current fix is to replace with a new green relay from Mitsu if you don't want to wait for your motor to get harshed. Just something to maybe look at.
Here is some more info.
http://www.***************/forums/sh...ad.php?t=18887
Edit: Well that's interesting it won't accept the link. Anyway maybe research that.
Here is some more info.
http://www.***************/forums/sh...ad.php?t=18887
Edit: Well that's interesting it won't accept the link. Anyway maybe research that.
Last edited by 2Fst4U; Oct 22, 2009 at 02:18 PM. Reason: Bad Link
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post





