i am back on 3d sd after a while on maf since i had no time to work on it. Have my off boost pretty well tuned just got to fix fuel map and see if my on boost will be less rich.

 

Well have jitter btw 2000-2600rpm

 

Try another rom version if you can. It seems that some versions get the jitter, some dont.

 

shameless bump and more info, I'm using the 8859 rom available on page 1

with my car not having been run in about 24hrs and the setting in ecuflash set to 0x03 to use the maf harness input with the maf plugged in,

evoscan shows request 3a (function x*1.8+32) at 60.8 degrees f
evoscan shows mut11 (function 1.8*x-40) as 62.6 f
evoscan shows mut44 (function x-40) as 100 f

now when I switch to the 0x0e (still with the maf plugged in but it should matter as it should be referencing the fuel temp sensor)

evoscan shows mut 3a as 69.8
mut11 as 73.4
mut44 as 121

this is all with the same formulas in evoscan and the stock scalings that come with the SD2.0 8859 rom.

Which of these requests are being used in the speed density calculation? and which one do I need to adjust to get it to read the fuel temp sensor correctly? it seems obvious that something is incorrect. Also mut3a with the maf sensor plugged in seems to be providing the signal that most closely matches the ambient temp outside. Any help would be appreciated.

The three scalings I see in ecuflash are in the SD section there is a mat for iat scalings, then the normal iat scaling and fuel temp scaling table. The first two tables are linked, changing one changes the other, so really there is only iat scaling and fuel temp scaling. If I assume that the iat scaling is correct for the maf sensor (since it reads about the right temp) and assume that the stock fuel temp scalings are correct and just copy them over to the iat scaling I still get incorrect numbers where:

request 3a is once again 69.8
request 11 becomes 174 (obviously wrong)
and request 44 is still 121........

so if request 3a is reading the fuel temp while set to 0x0e then the scaling must be incorrect because it can't possibly be 10 degrees over ambient when the car hasn't been run and has been sitting inside all day. Now since request 3a is obviously the reading the fuel temp sensor while in 0x0e does that mean that when using the fuel temp settings I will not be using either the IAT scaling or SD Mat scaling for iat scaling table? and that even if I were to wire in my GM IAT sensor to the fuel temp adc I would want to adjust the fuel temp scaling to match the gm iat for it to work properly?

and so is my fuel temp scaling wrong since its reading about 10 degrees hotter than the maf temp sensor? also which request should I be using to measure iat? 3a or 11? in evoscan it says to use 11 for 1998+ vehicles (or maf air temp scaled) and use air temperature (request 3a) for pre 1998 vehicles......

sorry for the long post.

TLR

just read it, it's all important... :P

 

ok so after a lot of searching I answered at least a couple of my own questions.

Mut11 is the address to be logged in evoscan to see what the SD calc is using as the temp. This still doesn't explain why my fuel temp sensor would be reading roughly 10 degrees higher than my stock maf sensor and scaling (bascially 10 degrees higher than ambient).

SO I suppose the only question remaining is ......is the fuel temp scaling in the 8859 rom correct?

 

Fuel temp will never be the same as ambient temp. Your using the temperature of fuel that is recirculating through the fuel lines to fake a temp curve. That temp curve will not and doesnt have to be accurate. But it will change sort of like IAT changes, so its usable.... I used it temporarily until I got full switched over to a UICP w/ a bung. Youre better off getting an IAT and using real data, since you seem to care that the data generated makes sense.

 

to account for larger displacement motors are you guys just multiplying the right hand side of the "kPa to load" table by the percentage increase in displacement then fine tuning with the 3d VE table?

 

I plan on leaving the load as 1 to 1 and tuning ve so my logged afrs match my fuel map. Its my understanding you only really need to go from 1-1 load if you want to achieve loads more closely to what you had on your maf setup.

Doing it that way will allow you to not have to modify your timing or mivec tables as much because they should be basically the same as your maf tune. This would be the same on large displacement motors or the stock 2.0

 

so, question i have. how universal is this code; the way i mean that is how easily does it transfer between ROMid's etc...

i have a 2006 eclipse 3.8L with a turbo. we have just recently gained the ability to read/write/edit our ROM with EcuFlash. our boosted community would absolutely kill to be able to switch to speed density and tune off our MAP.

from reading, with this code being able to scale for displacement, would any of you code geniuses find it feasable to be able to help me/us out in further developing our tuning ability?

 

Sup guys, just wanted to point out that the omnipower website lists different scalings for the 4 bar map sensor than are in the 8859 rom on page 1. I haven't checked the other roms.

Here is a link to the scalings.
http://omnipowerusa.com/calibrations.doc

its not off by much and I'm sure as long as the delta is very similar it doesn't matter, but I like things to be correct.

 

anyone use DMA?

I dont see fuel cut x2 any where on my 88586714 rom.

also how do I set the pointers to ROM? Theres a ton of DMA stuff in this rom that I dont understand.

 

When I save map sensor scaling it always reverts back to jdm 3 bar in my boost control settings. Anyone else have this problem ?

 

Make sure you change both tabs. You should have a tab that matches your rom and another "base" rom tab.

 

Anyone know why my alt ign map on my tuned rom would be linked to something that would prevent the car from starting? I copied the tuned tables to a new rom and it doesn't run the same and experiences a jitter at 2200 evo ix.

 

I have a quick question regarding the 3d SD that's not clear to me after reading through this thread (didn't read every post but I searched through).

The question is, in the 3D VE table, does adjusting the percentage values affect the load value, or just the injector pulse width?

EDIT:

In playing around, it seems it only affects pulse width.