Currently the ignition timing in v7 is only adjustable in whole degrees of timing advance. With the addition of v7 and the increased breakpoints (resolution) the interpolation only happens within a small change in load/rpm. This results in a "rocky" looking timing map and not a smooth one that would've been experienced/generated from a v5 timing map.

I give you Fast_Freddies v7 timing map on pump. Notice how the timing map looks like it's super choppy.... if we could adjust timing to a tenth of a degree OR even a 1/3 of a degree of timing I think we could smooth the timing map and get a better surface.

https://www.evolutionm.net/forums/at...oct-timing.png

 

Another reason why I stopped using the V7 on top of the overly humongous fuel/timing maps

 

you don't HAVE to use all the breakpoints, but if we had the ignition step change we COULD use all of them even if we didn't need them.

 

I am sure some of the "tuners" will chime in and say that "smooth" maps are not necessary.

 

I use the bigmaps with the same breakpoints of normal maps, just higher max values. For example, load up to 500 and RPM up to 11000. Making too many breakpoints is just a waste of time with the resolution that we have for timing, unless you are having a problem area where you want to have more room for adjustments.

 

Exactly my point. I have a problem area where there is something strange with the AFR's and to keep the perfect... I have to have 3 breakpoints close together. Since the timing and fuel maps share axis... now I have this problem on my timing map because the values have to change by 0 or 1.

I am a "tooner" and yes smooth maps are necessary.

 

HA.....I knew you would get a kick out of that one. I know you can change the table to show more decimal places. It might help a little.

 

The ignition is done in integer values, changing the decimal places won't do anything.

I could be wrong, but it seems like there isn't much scaling done with the ignition. With the fuel, there are places where it divides by various numbers so rescaling would be more possible without coding changes. It seems like the link to 1 hex = 1 degree is pretty solid through all the maps. The knock control does have the capability of 1/3 degree increments so the ECU can do it, but getting the tables to target those increments seems like it would be more difficult.

1/3 degree increments would be awesome with the big maps and there should be enough range to make it cover everything.

 

I went through most all of the ignition routines several months ago. 1/3 deg looks to be doable, but would be quite a bit of work.

 

Any chance for 1/2 degree increments? or is 1/3 more likely since the ECU already does it (though knock control)?

 

I think 1/3 deg is the base unit coded into the ROM.

 

Changing timing by 1/3's would be very helpful..

 

This would be handy, I would love to get rid of the "choppy" looking transitions in V7...

 

I don't really see the problem with bigmaps?

just because the map looks nice in the 3d viewer doesn't mean its any different in the way the ECU calculates it..

ie
2500 = 0*
3000 = 1*

is exactly the same as
2500 = 0*
2625 = 0*
2875 = 1*
3000 = 1*

the ECU will still calculate the same end result..

bigmap was meant to allow finer tuning IF required, like others have said you dont need to use it...

 

Maybe that's so... but I can tune my DTA Fast to one tenth of a degree. IIRC the AEM does it to .3 of a degree. It would be REALLY nice IMO.

If Mychailo is running out of things to do... I might be persuaded to trade some fabrication time for some code magic