What is it ?
Ok here is the set up , my car idles alot better with 8*of timing vs runing 7* of timing but ....if I run more than 8* of timing @1000rpms I get a po300 code at idle . Iam not sure if a tuner gave me a po300 fix when i got my last flash from them over 2 years ago . This is the #'s iam working with
1000rpms 7* of timing @0 load and 8* of timing @10% load and the knock fliter looks like this
1000rpms 16 units @ 30.0 tar and 16 units @ 40.0 tar .

thanks guys

 

ttt

 

I feel ya... but can't help.

 

"I am out of control. Yeah, I use drugs. I can do what I waunt, biatch! Yeah, I have sex, and I don't use protection! It's my hot body; I'll do what I waunt! I don't go to school and I kill people! What-evah! I'll do what I waunt! "--- Cartman

I guess this is better that just "bump" or "ttt" ?

 

OK , soooo I put in 8*@1k and UP the "tar" in the knock fliter from 16 to 18 @1K
Ill give it some time and see how it works out .

 

matt55,

are you sure your p0300 is coming from your idle? doesn't the light come on after a drive cycle?

I guess it only happens when you are at >8 timing at idle though. lucky guy.

did you get a little info PM'ed to you about the tar? I would think that would be pretty safe to do.

 

IIRC the ses light would come on at a stoplight after 10-15mins of driving .
I did have a "idle flash" but the ses light would pop-up its ugly head so i had the part of the flash removed .
I think there is a lot to the Knock fliter that we dont know yet (more hp and better runnig car) and who does know isnt talking about what they do to it .

BTW i didnt get any tar pm ?

 

There are many unknowns about how the Knock filters are handled in the ECU, its slowly unraveling as more information about the ECU is found in the disassembly efforts.

Unfortunately we really can't make assumptions about what any of those values actually mean. I always assumed that each one of thos knock filters represented a frequency range, and each cell represented a threshold value. This may or may not be true. But until we know for sure, its REALLY unwise to alter the values unless your just copying known values from another ECU.

Its one thing to play with the values, but there is enough contradicting data on how they work, that it makes me reluctant to want to alter them.

With that said, closed loop is a funny animal, there is some evidence (and some information recently forwarded to me) that there is a target table associated with ignition timing in closed loop, as are a fuel offset target map. It doesnt set the value in stone, but what sets the range of allowable adjustment. Only we haven't had time to validate any of this new information.

 

The car has not set a SES light , yet .

The idle sounds stronger/better @ 8* .

If any thing changes Ill update

BTW my main question was what is involved in the "PO300 FIX" ?
Timing change ?
Knock fliter change ???
Can any one share there knock fliter map , If not the whole map just the 1-2k
rpm range ???

MJ iam not goint to screw with anyother part of the Knock map just want to get the idle right/best i can .

 

The P0300 fix is weird, there appears to be some changes, but they aren't clear in any of the maps, I think one or two of the knock filters were adjusted, as was some of the ISCV values. There might have also been some code changes and some alteration of closed loop Timing and fuel modifier maps that we don't have currently defined.

For the most part, if bumping the timing helped, then I'd leave it at that. The reality is timing settings affect emissions (different types of gases and other byproducts) but so do cams, and anything else you alter.

 

I run 14 degrees at idle and it keeps the p0300 gremlin away for longer... but not indefinately. Heck, I cant even get it to remain a solid 14 degrees, if you set a whole brick of 14s from 0 to 1250 RPM and 0 to 100 load, it will still bounce between 8 degrees and 18 degrees. I believe this is like Jack said, it has to do with some sort of closed loop maps that aren't yet defined.

I would like for someone to post up a stock map that has been reflashed for the P0300 though if they could. (As I'd asked in my own thread)

 

Well, if you have a stock map and a P0300 fixed map, it would be very easy to see the difference with a simply hex compare utility.

I would be more than happy to do the compare if someone has both files.


Eric

 

I've not yet had anyone successfully post a "post P0300 fix" map, even after having specifically asked for it. It would be nice though.

 

Its like Bigfoot and the Loch Ness Monster......they are either urban legends or the people that have actually seen it are either not sharing with others or have no proof.
Thats why most of us use Scan Tech, a or a straight up code reader.

 

But so many people profess to have gone to Mitsu for the P0300 and getting a flash... with ecuflash it's so easy to just rip it off and post it up. Surely someone has a copy... even if they don't feel that they can prove it. I can prove it simply with comparing it to a stock hex that I have.