This might be old hat to some but since it seems that information isnt shared quite like the 8/9 ECU stuff was or it hasnt gotten to that level, I wanted to post what I found that has fixed it. Also now when you google P1320 Fix something should come up rather than the zero level it seems to be. This works independent of map upgrade (i.e. 0022 vs a 0015 in the 2008) or any of the Tephra ROMs to fix it.

In my MR I purposely switched to an older map from a Tephra 0122 ROM (which had zero issues) to see if I could induce the P1320.

The map in question -

Ignition Warmup Retard (seems extremely obvious) - stock version -



Modded-



I also made sure that my changes in the lowerbound timing table didnt conflict and that it was set to the factory -20*. My car would throw the light every other start before this and since it hasnt thrown it in over 20 starts for the last week. I find it odd that this code exists at all since the Ignition has so many correction trims to ADD timing rather than keep it low. I dont log lower timing but with the map altered to make it think its there apparently its happy.

More input is always welcome as to the "how" if there is something I have missed in the various trim maps.

Aaron

 

Also, out of curiosity, has anyone zero'd the 1320 out in the OBD-II codes at 0Bx1? I cant recall a 100% but I dont think it throws a 0000 when you do that, it just doesnt throw anything. I suppose I need to play with that more.

 

The ECU of course wants to keep the timing very low during warmup to get the cat to light off. I always assumed this code states that the ECU was not able to keep the ignition timing near the "target" low ign advance due to the fact that it's having to raise timing to keep the idle smooth and/or high enough.

I also assume that the Ignition Warmup Retard table is a subtractor table, meaning that a value of 5 actually subtracts 5* from the base timing value. I'd think that putting -15 here would actually increase timing when cold, which of course would hurt cold emissions badly. However, maybe this also increases the "target" ignition timing, meaning the ECU doesn't have the same trouble it did before keeping the idle on target?

Just speculating here..

 

Thats what it seems like it is doing. It is simply a target value and is never actually used. It's set to use it but with the trim tables it doesnt run less than 20 or so positive when I log it. Over a week with no code so its working

 

Update-

I am now on the beginning of Week 4 with this 1320 fix and still no codes. Not sure if anyone else has tried it yet other than me but if so, dont be shy, post results.

Aaron

 

gonna do it.

 

FWIW I still have no codes. I think this particular issue can be laid to rest...stupid background maps.

 

Seems to be working, only odd side effect is it seems to jump in RPM about a minute after starting from cold. Doesn't bother me. It just acts like I've blipped the throttle up to about 3k and comes back down. I think its where it all the sudden gets a ton of timing.

Edit: caught it on a log last night. See pic.

 

Ive tried this patch too and experienced the same thing as honki24

 

Do either of you guys have cams? My MR doesnt and for whatever reason doesnt have the rev up blip but an S2 car I just did yesterday will do it...only once in the morning and then it doesnt seem to again. The timing map and timing error correction on that car is cranked to make the cams work so I wondered if that was related.

 

Back from the dead!

So the pics are dead...any chance you can repost or pm them to me?
just ran across the first one of these.

#thanksphotobucket

Thanks

 

NVM found them!

 

To be clear, you're saying the -15* did it?

 

My car had this problem and it was the timing in the tune at idle it had like 20 to 23 degrees went back to stock idle timing and problem solved.