Extended Maps

[belize1334]

First of all...  ... I know.

I bring this up because with the release of the new Jackal we're still on load-based tuning and as an autocrosser I just can't give up dynamic timing between 10psi and max boost. I need to tune timing through there to have good turbo response. I know we're all gonna be floating on clouds and eating rainbows when Wherewolf comes out but in the mean time it'd be nice to get a little more out of the current setup.

The extended map debate invariably comes back to the tradeoff between resolution and max-boost in the top load row. The standard double-range tutorial puts you at ~4.04 g/rev on the top load which is in the realm of 35psi. Most people don't run that high or if they do they don't care about drivability so the trade-off just isn't worth it.

But, it is possible to extend the maps through some intermediate value so that you can have the top row correspond to the max boost that YOU want to run which minimizes the loss of resolution down low. Keydiver does this on ALL his chips and I've been running with it for years.

The solution is simple. You just divide the MAF scalar (549A) by the decimal ratio corresponding to the boost you want to run. Example: 14b can't push more than 20psi to redline so I'll say I want the top row to correspond to 20psi. The stock map hits top at about 10psi so the desired scaling is (20+15)/(10+15)=1.4. I divide the value at 5498 by 1.4(in hex) and voila. The tricky bit is that I have to load an entirely new timing / fuel map which interpolates the old maps and fits them into the first however many rows. Then I put the timing and fuel values that I want in the last few rows corresponding to the new extended range. But really, with excel, that should be a no brainer.

This should be EASY to implement and user selectable. There could be a field in Jackal called (map scaling) with an input parameter from 100% to 200%. We could even have a collection of base-maps for different common choices (125%,150%,175%,200%) which have the already interpolated timing map rescaled and preloaded.

So come-on... who's with me?

[John_H]

sounds like a good idea to me.

I THINK that will be in Werewolf?

[hakcenter]

WW won't need extension, cause it'll be pressure based.  lol

[belize1334]

Exactly. WW will be MAP based tuning. But that still leaves Jackal with a significant deficiency IMHO. I'm not trying to stir up trouble... I just think that Jackal could benefit from this one addition which is known to be compatible with Nate's SD code.

[hakcenter]

There's no trouble to be stirred up.

I don't want to sound rude, but if the difference between the two softwares, isn't substantial, why would anyone buy the latter.

I would love to be all buddy buddy , but realistically I see that feature hindering the sale of what I'm trying to direct everyone into using. In any event, once your keyed, you own jackal, you are free to do whatever you want to it, except a few obvious things, mainly redistribution of course.

[belize1334]

Do you mean that, once keyed, I can go in and adjust that address manually? I thought it was all encrypted.

[hakcenter]

Do you mean that, once keyed, I can go in and adjust that address manually? I thought it was all encrypted.

Well obviously once the data is on the ostrich, it is readable in quite a few other ways. 

[belize1334]

I guess I don't really understand alot of how your software interacts with the stock code and Nick's SD code etc...

Suppose I were to load Jackal's stock ds2 onto the ostrich and then open that in a hex editor and alter the value of D49A as mentioned. If I then open Jackal again to tune the maps is it going to overwrite the value at D49A or will it leave the alteration intact as part of the now savable ds2?

edit
I also wanted to ask about the "octane" map which doesn't appear to be accessible through Jackal. When doing a map extension it becomes important to modify the "octane" map as well so that bad fuel doesn't accidentally imply an increase in timing advance... unless of course the "octane" value is premanently disabled in which case said map has no meaning... Does Jackal still use the "octane" feature or is that now obsolete? If it's still in use, could the associated map be modified directly in a hex editor?

[hakcenter]

If you want to know more about the specific innards of the eeprom it'll have to goto pms. Away from prying eyes, that think what I do is so simple.

AFAIK the octane map is bypassed, I can take a look tonight to verify.

[hakcenter]

Didn't get a chance last night, probably not going to tonight (bible class), hopefully tomorrow!

[hakcenter]

It appears to me that the octane map is still being used, but looks like the octane value is never modified (area completely no op'd)

So yes and no, lol

[Busta]

I have tried the extended maps mod with my bin using Kyle Tarry's instructions. I had issues with the extended maps load value would nose dive after reaching 26 psi. Boost would hold steady but ext. load would drop. Not sure why.

Anyways I think the pressure based maps of ww would be the way to go.

Later, Vlad.

[mikyrc]

I have tried the extended maps mod with my bin using Kyle Tarry's instructions. I had issues with the extended maps load value would nose dive after reaching 26 psi. Boost would hold steady but ext. load would drop. Not sure why.

Anyways I think the pressure based maps of ww would be the way to go.

Later, Vlad.

That's because jackal uses the same mem adress to store BCS boost control as the load value used on extended maps. 0054H if I remember correctly.