Extended Map Check.

[CrazyM]

Just for anyone who has done or knows about the extended maps. After I put in the Fuel Enrichment maps as well as the Timing maps.


Is around the middle section to highs supposed to drop down to AFR's of 10-9.0?

Would I have to tune and adjust for this via my SAFC?

Also where exactly do i put in the Octane map at?

Thanks, Mike

EDIT: Also if by entering the Octane Maps by Hex, it says to start at "FE08"(7E08 on my chip) Do I start out at the point closest to 4.13 or 1.25 at 500 RPMS?

 

[toofast82]

They have the timing and fuel settings in the extended map guide, which im assuming you downloaded. As for the octane map, you can either eliminate it via hex or set it the same as your other timing table so there is no timing loss.
I personally dont run the extended maps because when making changes it is a pain to find what load level you need to modify as you may cross different load points throughout the rpm band. I use the stock that way i always know im on the last load level above 15psi or so and makes it easier to edit. You can edit it to still read the 3200hz on the logger though.

 

[CrazyM]

I did download the extended Maps Guide from DSM-ECU. But am Using TunerPro\ Easypro Programmer(Program that came with my programmer).

I thought it might be better to use the tables as it does look like they are much smoother than the stock maps? But I'm also new at tuning so I should probably go for the easiest but best way..

 

[toofast82]

On the guide: For the timing, they have the actual numbers you can just edit in the tunerpro tables. For the A/f, it looks like its in decimal. Therefore you will need to use a decimal/hex converter for the figures and edit them manually via tunerpro's hex editor.
The extended maps are very smooth, but when making changes are more trouble than they're worth in my opinion

 

[CrazyM]

I did input them Via TunerPro, the guide also gives you the numbers to directly input into the ECU(as Hex) and this is what I did. The only one I am really confused on now is where to start the Octane maps, at the point closest to 4.13 or 1.25 at 500 RPM.

At the location of '7E08' which point would I start with is what I am asking on the octane maps, to clear that up.

I was just worried that my AFR dropped into the 9.0's, but if thats Normal, I can always datalog and tune for perfect AFR's.

 

[toofast82]

Im not sure if you are understanding the octane map. It is used for when the ecu detects low octane fuel or a lot of knock. it switches over to this map which has considerably less timing and poor performance. you want to tell the ecu to avoid them via hex or just copy/paste your regular timing table to octane so there are no issues with timing.
Also, according to the guide im looking at the hex values they give are for stock maps and not extended. Using this will make you regret using extended maps rather quickly

 

[CrazyM]

Oh ok, right. I kinda remember reading that somewhere's now(was up LATE last night doing reading) the Octane map is like a little safety so say if you 87 Octane it goes into a safety mode correct?

I am programming by following the First Generation Tuning page, and I noticed under the Octane Map\Reset, there was this easier looking code that Jeff sent.

"Just change the byte at $D0B5 from $2C to $28. This bumps the
warmboot address back 4 bytes to $D0DE which resets the octane byte
to 255 during a coldboot. now it will reset octane on a cold or warm
boot."

Would it be best to go with that code?

Thanks, Mike

PS. The help is REALLY appreciated!

 

[sbiggi]

They have the timing and fuel settings in the extended map guide, which im assuming you downloaded. As for the octane map, you can either eliminate it via hex or set it the same as your other timing table so there is no timing loss.
I personally dont run the extended maps because when making changes it is a pain to find what load level you need to modify as you may cross different load points throughout the rpm band. I use the stock that way i always know im on the last load level above 15psi or so and makes it easier to edit. You can edit it to still read the 3200hz on the logger though.

It interpolates the cells, there shouldnt really be that big of a variance between the load cells anyways that it causes a tuning issue.

Besides, you can log load, and know where you are on the maps.

 

[toofast82]

It interpolates the cells, there shouldnt really be that big of a variance between the load cells anyways that it causes a tuning issue.

Besides, you can log load, and know where you are on the maps.

That would help out quite a bit with the extended map and logging/editing
Is the load logging available with mmcd or is it pocketdyno/logger?

 

[CrazyM]

It interpolates the cells, there shouldnt really be that big of a variance between the load cells anyways that it causes a tuning issue.

Besides, you can log load, and know where you are on the maps.

Not quite sure if you're saying go ahead and use the Octane Map off the extended maps guide or just reset it to max like I posted just above?

 

[toofast82]

Not quite sure if you're saying go ahead and use the Octane Map off the extended maps guide or just reset it to max like I posted just above?

Thats your call, most choose to eliminate it the ecu from using it

 

[CrazyM]

Thats your call, most choose to eliminate it the ecu from using it

Ok, Perfect. Thanks for all the help!

 

[Zenja]

That would help out quite a bit with the extended map and logging/editing
Is the load logging available with mmcd or is it pocketdyno/logger?

You can hex edit the code to make the load related values show up in whatever logger variable you want. You should be able to find information on how to do this, on the yahoo groups I think. For example, I'm using the TMO logger and I made "Air volume" on the logger display a 0-255 value representing no load to full load. That makes it easy to tell where exactly on the maps you are. All that's involved is changing a single value in the .bin.

 

[toofast82]

. For example, I'm using the TMO logger and I made "Air volume" on the logger display a 0-255 value representing no load to full load. That makes it easy to tell where exactly on the maps you are. All that's involved is changing a single value in the .bin.

I think its nice to do this, but it still doesnt give you an exact load point, so therefore you still have to look around a bit. It will give you an approximate start to look.
I just think its pretty easy just to go and edit the last line, but to each their own.

 

[Zenja]

It does give you an exact load point. A logged value of 168 will always be exactly the 8th cell. 192 would be the 9th cell. Anything in between would tell you where in between those two you are. You can even very easily set up the table labels for each row in TunerPro to be that 0-255 number rather than the row number. (ie first row is labeled 32, next is 48, etc). It's very simple. But yes, your method does work and it's personal preference, but extending the maps is more "correct."

 

[toofast82]

It does give you an exact load point. A logged value of 168 will always be exactly the 8th cell. 192 would be the 9th cell. Anything in between would tell you where in between those two you are. You can even very easily set up the table labels for each row in TunerPro to be that 0-255 number rather than the row number. (ie first row is labeled 32, next is 48, etc). It's very simple. But yes, your method does work and it's personal preference, but extending the maps is more "correct."

That would definitely work well with what youre stating, thanks for the info You learn something new everyday.
Im currently running speed density so i am tuning off of pressure these days

 

[->PrOjEcTGS<-]

I used the extended maps for pretty much one purpose only. Before, for some reason at WOT I would always run .5-1.0AFR off of what was set in the fuel map. Once I started using the extended maps I started hitting my target AFR or at least closer to it. It gives the ECU more control to correct for airflow changes. While it was easier to tune your way by editing just the top cells, this seems to be more accurate.