Adding load columns and RPM rows to maps
Hmm.
Looking through John's old notes, it looks like 0xffff9c00 through 0xffff9fff gets reset to zero at key-off, so that's unusable, and I can't imagine we can go much beyond 0xffffa800 without stomping on the stack. So, moving this (as a contiguous block) really isn't going to work.
That said, I think this will actually fit, assuming we make better use of the space. Fuel and timing maps are each 736 bytes long, so of our 2k space, we'll be using 1472 bytes just for them. But, we're not doing live adjustment of many other items: injector scaling (2 bytes), MAP VE (24 bytes), and RPM VE (23 bytes).
So, assuming I'm not forgetting something important, that leaves 527 bytes for "other"; RAM MUT table, etc.
Well damn. This might work quite nicely.
Looking through John's old notes, it looks like 0xffff9c00 through 0xffff9fff gets reset to zero at key-off, so that's unusable, and I can't imagine we can go much beyond 0xffffa800 without stomping on the stack. So, moving this (as a contiguous block) really isn't going to work.
That said, I think this will actually fit, assuming we make better use of the space. Fuel and timing maps are each 736 bytes long, so of our 2k space, we'll be using 1472 bytes just for them. But, we're not doing live adjustment of many other items: injector scaling (2 bytes), MAP VE (24 bytes), and RPM VE (23 bytes).
So, assuming I'm not forgetting something important, that leaves 527 bytes for "other"; RAM MUT table, etc.
Well damn. This might work quite nicely.
initial beta 96530006 sent to those that emailed me
for those that are interested:
FACT: the ignition routine does LOTS of maps lookups based on the normal Axis's.
This means that we can't modify those axis's without impacting the other maps (EGR, ColdStart, etc)
What I have done is implemented a small routine which does the new axis's lookups at the beginning of the Ignition lookup routine.
So essentially the old axis's stay the same and they are used for the existing extra maps.
I could have left the axis lookup so that it ONLY occurred in the fuel map lookup routine, but I figured it is better to do it as mitsu designed.
for those that are interested:
FACT: the ignition routine does LOTS of maps lookups based on the normal Axis's.
This means that we can't modify those axis's without impacting the other maps (EGR, ColdStart, etc)
What I have done is implemented a small routine which does the new axis's lookups at the beginning of the Ignition lookup routine.
So essentially the old axis's stay the same and they are used for the existing extra maps.
I could have left the axis lookup so that it ONLY occurred in the fuel map lookup routine, but I figured it is better to do it as mitsu designed.
~Zach
P.S. - I have a wilson v0 and ppi 65mm tb sitting in my garage waiting to be installed! So once i get this ironed out and the tune set I will be installing and posting a review to see what kind of flow I pick up! Will be easy to see running SD now!
So it looks like all of this will fit together nicely, just need to defregment the hard drive space?(for lack of a better way of saying it)
God, if we can make use of all of the great features that everyone has created in one organized file, that would be specatactular!
Do a VDR or DLL A/B comparison for us too!
God, if we can make use of all of the great features that everyone has created in one organized file, that would be specatactular!
Do a VDR or DLL A/B comparison for us too!
Thoe99 - Nope, the memory is part of the SH chip itself.
Regarding John's stuff I will reposition the new big altmaps along with the current altmaps (so that they are all together) That will make it easier for someone to adjust John's code so it still works
Regarding John's stuff I will reposition the new big altmaps along with the current altmaps (so that they are all together) That will make it easier for someone to adjust John's code so it still works
I'm not sure if I missed it but did Tephra settle on an exact BIGMAP size yet? was it just the 10 load/5 RPM version (29 load/25 RPM) he originally posted a screenshot of? Or is it like the 12 load/5 RPM (31 load/25 RPM) like the screenshot I posted?
Last edited by Jack_of_Trades; Oct 3, 2009 at 06:29 PM.
I personally think that should be big enough...the screenshot posted shows more resolution in the stock map areas, such as RPM jumps by 250 instead of 500 and load jumps at the high end by 10.
Following the same resolution and pattern as the stock maps, a 29x25 map gives us RPM up to 10500 and load up to 460. Although I guess it's up to the majority...may as well do it once and be done with it for good.
Following the same resolution and pattern as the stock maps, a 29x25 map gives us RPM up to 10500 and load up to 460. Although I guess it's up to the majority...may as well do it once and be done with it for good.