mrfred

iTrader: (50)

Folks - I've been working on a revised 3D SD implementation that will be incorporated into a modified tephra v7. The SD coding is 95% complete, and as I get to the point where I consider incorporating it into a tephra v7, I am thinking about what size tables to use. I plan on having a single size table for AFR, timing, and SD. I have found that the tephra big maps are too large for my needs, even as I get up into the 550 whp range, so I would like to implement a slightly smaller table with 26 elements across and 21 elements down. See the attached example. Question is whether there is a real need for something larger, in particular for the 600-800 whp cars. I'd like to think that the tables could be rescaled to get the necessary rpm or load, but let me know.

merlin.oz

looks pretty good sizing to me, I have done something similar to several v7 roms.
The main thing is to avoid having steps in the spark map.

211Ratsbud

iTrader: (1)

Still appears to be plenty of resolution to me. I posted a screen shot of 88586714 that donner patched reduced ve table and I had no issues with that. I think it was 21x19 but don't hold me to that.

evo8426

iTrader: (27)

In my opinion the maps are still too large, even on SD cars that run 32psi and make over 500whp I don't go over 330 load. I'm excited to see what changes are implemented.

todd6027

iTrader: (10)

Agreed

wreckleford

iTrader: (2)

I am okay with the map size you are proposing.

This brings up another point. I have seen someone post (I believe it was Merlin) say that a better tune is possible with the standard timing maps as the 1 degree resolution creates problems with the load values being so close together.

Anyone else agree? I haven't really looked into it, but I do know that it certainly was possible to get a great tune with the smaller maps.

Mrfred, if I am taking this too far off topic let me know and I will make a new topic. I am okay with the map size you are proposing.

mrfred

iTrader: (50)

I will eventually have an update that allows 0.35 degree timing increments.

wreckleford

iTrader: (2)

Any idea what the cost will be?

mrfred

iTrader: (50)

A one-time purchase will cover all future updates. Probably will be around $125.

todd6027

iTrader: (10)

version for 9055 ???

evo8426

iTrader: (27)

I'm out, Tephra charged nothing for his work and don't see myself paying for modified work of someone else. I did donate to Tephra when V7 can out back in the day. I only tune other evos for my own enjoyment.

Good luck on your efforts as I'm sure you are putting in a good deal of effort.

wreckleford

iTrader: (2)

I would assume that MrFred would send a portion of the $125.00 in Tephra's direction .

evo8426

iTrader: (27)

I am a nonprofit Evo enthusiast. In my opinion if anything is charged, the full amount should be split between everyone that put in any effort to make any of this possible. Tephra charged for certain ROMs on a "pay what you think it is worth" basis, which seems as though that could be $5 or $500. Not saying mrfred is a dishonest person, but based on the logic of your post we could assume the $125 would all be going straight to his pocket.

mrfred

iTrader: (50)

Actually, tephra's Evo 7-9 ROMs are donationware. If you haven't noticed, he is now charging for his Evo 10 ROMs. They are VIN locked just like what I'm doing.

What I'm doing is pretty far from changing the label and putting a price on it. The SD code I've written bares no resemblance to what's out there now - More tuning options, easier to setup (one ROM contains both MAF and SD capability). And the flex fuel patch will have to be a complete separate entity from tephra's code. Beyond all that, my main goal is to produce a ROM that satisfies my needs. I'm dreading the thought of porting the code to other MYs, so to some extent, I'd be happy if no one wanted to buy my ROM.

Ding ding. $50 -> tephra.

mrfred

iTrader: (50)

See above. I've already discussed with tephra over a year ago. BTW - several features in tephra's ROMs are patches first written by me.