This table gets fubared if the timing map load gets rescaled. If the timing advance values vs load values are not corrected this can result in tip in knock.

 

That's interesting. Can you post an example?

 

Depending which lower cell values you eliminate you shift the timing to higher load

...in this example Stock timing is at 70



After eliminating the 30 column loads are shifted to the left and timing values end up at a higher load.



The more lower load columns are eliminated the more additive timing end up in the tip in or spool areas

 

Seems like a potential issue for other situations where a set of axes serves more than just the table where the user is looking to make the change.

 

Ouch. And I just eliminated a few more of those columns to get more resolution in the 220-250 load areas . I removed 30 and 70 which means that now those tables extend into the 90 load column.

Have these tables been found in 96940011 as of yet so I can at least lower them?

 

Yes they are the Boost Enhancement Adv/Ret Map (Anti-lag) maps 1 and 2

 

Woah, that's an awesome point. I have been chasing some damn knock in another thread in the 70-90 areas under light loads.. I bet this may be the cause... I might have to start playing with those maps now...

 

I assume we could 0 out the dyn advance map without any problem ???

 

the only draw back is that mpg may suffer . I adjusted(or eliminated) the timing to correspond the original values in the 70 load column.

 

very good point, I've done the same for my 80 column since I've gotten rid of the 70.

 

Never noticed those before . Ok time to compare to the stock one and reset for the scaling

Thanks

 

BTW I also corrected the values shifted when rescaling load in the Boost Enhancement Enrich/Enlean (Anti-lag) Map ( the one that displays AFR in a timing map)

 

I moved these over to their appropriate positions based on my current Load/RPM scale. Lost a bit of resolution but I think it should be fine.

 

I mentioned that too on post 41, cant remember who I said that to

https://www.evolutionm.net/forums/sh...9&postcount=41

Nonrtheless, I like it set to 0* on the #2 map, I think it's purpose is to adjust for the slower burn with excess CO2 from exhaust dilution. Knocks less that way

 

I discovered the other day while I was logging that 1 count will cause the car to switch from the low det back to the base timing table. There must be a timer in there somewhere because if you hit 1 count of knock again it will go to the high det table and then in my case take 1* out. We need to look for a timer control or knock amount table I think next. I have verified that it still adds timing in open loop, for awhile I thought it might be just closed loop that it was working in but its not.