Speed Density 2.0 (3D VE Tables, Baro)
The kpa Kavlico 3.5bar MAP scaling is wrong, the load values are too low (car runs lean). I added a 20kpa offset to the right side of the MAP Sensor kPa table and it was dead on at idle, but at higher loads it was off, so it's the scalar and the offset that are both incorrect. I tried to fix it but I'm not versed enough in scalings to do it properly myself. The Kavlico is the same as the SSI and AEM 3.5 bar and is as follows:
0.5v = 0kPa / 0PSIa
4.5v = 344.73kPa / 50PSIa
Old 2D SD scalings (psia) for this sensor are correct.
Beau
0.5v = 0kPa / 0PSIa
4.5v = 344.73kPa / 50PSIa
Old 2D SD scalings (psia) for this sensor are correct.
Beau
A good way to see if its scaled correctly is to set the entire VE table to 100% and adjust your injector scaling temporarily so the car is driveable. Under normal acceleration, the KPA and LOAD should log the SAME values.
-Jamie
Jamie,
I'm copying the tables over now to 94172715 and will try that one for giggles. Will report back.
Is 96534706 known to be a "bad" 3D ROM for the 2005 Evo8? I've not seen these "conversations" that 211ratsbud alluded to above. It would be useful to know if that is really the case as it would save people a bunch of time and frustration.
I'm copying the tables over now to 94172715 and will try that one for giggles. Will report back.
Is 96534706 known to be a "bad" 3D ROM for the 2005 Evo8? I've not seen these "conversations" that 211ratsbud alluded to above. It would be useful to know if that is really the case as it would save people a bunch of time and frustration.
Here's the thread that got me to change back to 9417. https://www.evolutionm.net/forums/ec...vs-9417-a.html
How is the IAT and the CLT factored into the SD calculation in this ROM? Most OEM VE/SD setups and most good standalone ECUs with true VE calculation have a "charge temp blend" table of some sort. Typically, at low airflows, the water temp is a better representation of the charge air temp actually entering the cylinder, due to low airflow and heatsoak from the manifold/head. As airflow increases, the IAT becomes more and more an accurate representation of true charge temp, usually being close to 100% at WOT.
I'm asking because of issues with hot start from heatsoaked IAT sensors. This shouldn't be happening because the calculation shouldn't be factoring the IAT into the calculation more than 10-20% or so, the majority of the charge temp correction should be coming from CLT.
Beau
I'm asking because of issues with hot start from heatsoaked IAT sensors. This shouldn't be happening because the calculation shouldn't be factoring the IAT into the calculation more than 10-20% or so, the majority of the charge temp correction should be coming from CLT.
Beau
How is the IAT and the CLT factored into the SD calculation in this ROM? Most OEM VE/SD setups and most good standalone ECUs with true VE calculation have a "charge temp blend" table of some sort. Typically, at low airflows, the water temp is a better representation of the charge air temp actually entering the cylinder, due to low airflow and heatsoak from the manifold/head. As airflow increases, the IAT becomes more and more an accurate representation of true charge temp, usually being close to 100% at WOT.
I'm asking because of issues with hot start from heatsoaked IAT sensors. This shouldn't be happening because the calculation shouldn't be factoring the IAT into the calculation more than 10-20% or so, the majority of the charge temp correction should be coming from CLT.
Beau
I'm asking because of issues with hot start from heatsoaked IAT sensors. This shouldn't be happening because the calculation shouldn't be factoring the IAT into the calculation more than 10-20% or so, the majority of the charge temp correction should be coming from CLT.
Beau
-Jamie
This is a rough 'patch' and not a true speed density setup so this isn't as ideal as you wish it to be, unfortunately. To combat heat soak, the smartest alternative it to have the IAT as low and out of the engine bay as possible. I have seen the IAT come back down to outside ambient temperature in only about 4-5 seconds at idle airflow.
-Jamie
-Jamie
lol, it sure is. I have seen more OEM SD setups use the baro sensor for the first few seconds and then switch over to the charge air temp sensor than anything else. Some even use the baro sensor as a 'clogged air filter' monitoring system as well, which I always found to be a nice feature.
-Jamie
-Jamie
Last edited by Dynotech Tuning; Feb 13, 2013 at 04:26 PM.
Jamie,
I'm copying the tables over now to 94172715 and will try that one for giggles. Will report back.
Is 96534706 known to be a "bad" 3D ROM for the 2005 Evo8? I've not seen these "conversations" that 211ratsbud alluded to above. It would be useful to know if that is really the case as it would save people a bunch of time and frustration.
I'm copying the tables over now to 94172715 and will try that one for giggles. Will report back.
Is 96534706 known to be a "bad" 3D ROM for the 2005 Evo8? I've not seen these "conversations" that 211ratsbud alluded to above. It would be useful to know if that is really the case as it would save people a bunch of time and frustration.
Can anyone send me or link me to a known "working" 94172715 ROM and XML, ideally without inheriting 94170715 XML as Roadspike's version does?
Just flashed 94172715 to the car. Started right up and drove beautifully. 
Now I just have to fine tune it. It's very rich above CL (90 Load and up). LTFT Mid is -4.5 and Low hasn't registered yet. No lean tip in. I couldn't be happier.
I'll keep you updated.

Now I just have to fine tune it. It's very rich above CL (90 Load and up). LTFT Mid is -4.5 and Low hasn't registered yet. No lean tip in. I couldn't be happier.
I'll keep you updated.
Are you using the V7 Tephra mod XML for 94170715?
I did for both but had a totally different (negative) experience so I'm trying to figure out what I did different to you.
Did you have 94170715 v7 working for you before you tried SD?
Update: I lied. I still had the MAF plugged in. Changes I made to the 3D made took affect, but as soon as I unplugged the MAF it couldn't rev past idle.
Last edited by 10isace; Feb 18, 2013 at 09:27 PM. Reason: Updating.
Hey mates!
I am having troubles with 3d SD..
I have tried a lot of kpa2load combinations, played a lot with 3d VE table, but my car behaves the same way. It starts perfect, idles well, but when i touch the throttle and try to rev it it leans out misfires etc.
Even if I floor the pedal (gradually or rapidly), the map sensor (JDM Map) reads 95-105 KPA but the load goes to 70 but never higher than that, AFR leans out to 18-20 as soon as I push the throttle. If I hold WOT it keeps super-lean AFRs and missfires, generaly regardless of any 3d VE or KPA2LOAD changes.
It seems to me that my ROM may be corrupted, or I have downloaded something nonworking. I have tried downloading that rom from the 1st and 2nd posts of the "Speed Density 2.0" topic. I am using 96534706 as I own EDM 2004 Evo8. Evo9 JDM Map and GM IAT both mounted in the inlet manifold.
I have also tried the old 2d SD rom. Set it up in a couple of minutes, transfered my fuel and ignition maps, injector parameters from my finished MAF tune and it worked fine - fired right up, idled, revved. It holded some kind of reasonable AFR at idle revved fine without any harsh enleanment and generally felt smooth. I have even tried some all-around driving in 1-3 gears, it has pretty rich AFRs for cruise, but I haven't tuned it at all.
What else can i do or check? Could you give me a link to the known working version of 96534706 3dSD ROM?
I am having troubles with 3d SD..
I have tried a lot of kpa2load combinations, played a lot with 3d VE table, but my car behaves the same way. It starts perfect, idles well, but when i touch the throttle and try to rev it it leans out misfires etc.
Even if I floor the pedal (gradually or rapidly), the map sensor (JDM Map) reads 95-105 KPA but the load goes to 70 but never higher than that, AFR leans out to 18-20 as soon as I push the throttle. If I hold WOT it keeps super-lean AFRs and missfires, generaly regardless of any 3d VE or KPA2LOAD changes.
It seems to me that my ROM may be corrupted, or I have downloaded something nonworking. I have tried downloading that rom from the 1st and 2nd posts of the "Speed Density 2.0" topic. I am using 96534706 as I own EDM 2004 Evo8. Evo9 JDM Map and GM IAT both mounted in the inlet manifold.
I have also tried the old 2d SD rom. Set it up in a couple of minutes, transfered my fuel and ignition maps, injector parameters from my finished MAF tune and it worked fine - fired right up, idled, revved. It holded some kind of reasonable AFR at idle revved fine without any harsh enleanment and generally felt smooth. I have even tried some all-around driving in 1-3 gears, it has pretty rich AFRs for cruise, but I haven't tuned it at all.
What else can i do or check? Could you give me a link to the known working version of 96534706 3dSD ROM?
First I downloaded a new copy of 96534706 3D SD 2.0 rom. Copied injector fuel and ignition tables, put 110+ ve numbers at 80+kpa in 3d VE map, but lowered the idle cells to ~70ish% to keep AFR reasonable, put JDM map sensor scaling in, and started the car. It fired up with no problems as always... ...and the whole story repeats itself...
I tried to use IAT pin instead of Fuel Temp as MAT input. That changed nothing and I couldnt see any difference. Anyway MUT 11 shows actual temperature in the engine bay, just a couple degrees higher than MAF IAT shows, as I have my GM IAT in my IM.
Despite that I have JDM MAP, I have tried to use "Omni 3 bar" and "Omni 4 bar" scalings just for giggles. Omni 3 bar behaved even worse than JDM MAP scaling. As for Omin 4 bar scaling - it surprised me that at least it gave me a chance to hold the throttle and rev my engine higher than 4K...
Anyway whatever scaling I use, whatever i put in my VE table (like 120% from 80-300 load at all RPM), I can not log load higher than 75-ish. Even when my map reads 105 KPA.
As far as I understand it's just a simple math - if my MAP reads 105 KPA and I have put 120% in apprpriate cells in 3D VE table, I should be able to see 125 Load. But whatever I try I always get 75-ish load at 100-105KPA.
I haven't tried to use any other roms including 9417.
Any input would be appreciable as I am totaly knocked down by that situation.
Last edited by Biggy VIII; Feb 14, 2013 at 10:05 AM.
At least I am not the only one with this issue. I downloaded the pack and everytime I open it there is an error that pops up about no definition file. I have re-downloaded several times and double and triple check my addresses.
So you used the same source files that I did..hmmmm...I did not have 94170715 working before SD...I'm coming from 96530706 and copied fuel, injector scaling & latencies, ignition, MAF Comp, inserted my 3D VE table built from MAF logging.... I'm using a JDMMAP sensor and GMIAT in the IM wired into fuel ADC....so there has to be some difference between your XMLs and mine.
Can you email me your XMLs to cdrinkh2o@gmail.com so I can filediff them?
I didn't have much time to play with my car, but today I made several experiments that might help to diagnose my case.
First I downloaded a new copy of 96534706 3D SD 2.0 rom. Copied injector fuel and ignition tables, put 110+ ve numbers at 80+kpa in 3d VE map, but lowered the idle cells to ~70ish% to keep AFR reasonable, put JDM map sensor scaling in, and started the car. It fired up with no problems as always... ...and the whole story repeats itself...
I tried to use IAT pin instead of Fuel Temp as MAT input. That changed nothing and I couldnt see any difference. Anyway MUT 11 shows actual temperature in the engine bay, just a couple degrees higher than MAF IAT shows, as I have my GM IAT in my IM.
Despite that I have JDM MAP, I have tried to use "Omni 3 bar" and "Omni 4 bar" scalings just for giggles. Omni 3 bar behaved even worse than JDM MAP scaling. As for Omin 4 bar scaling - it surprised me that at least it gave me a chance to hold the throttle and rev my engine higher than 4K...
Anyway whatever scaling I use, whatever i put in my VE table (like 120% from 80-300 load at all RPM), I can not log load higher than 75-ish. Even when my map reads 105 KPA.
As far as I understand it's just a simple math - if my MAP reads 105 KPA and I have put 120% in apprpriate cells in 3D VE table, I should be able to see 125 Load. But whatever I try I always get 75-ish load at 100-105KPA.
I haven't tried to use any other roms including 9417.
Any input would be appreciable as I am totaly knocked down by that situation.
First I downloaded a new copy of 96534706 3D SD 2.0 rom. Copied injector fuel and ignition tables, put 110+ ve numbers at 80+kpa in 3d VE map, but lowered the idle cells to ~70ish% to keep AFR reasonable, put JDM map sensor scaling in, and started the car. It fired up with no problems as always... ...and the whole story repeats itself...
I tried to use IAT pin instead of Fuel Temp as MAT input. That changed nothing and I couldnt see any difference. Anyway MUT 11 shows actual temperature in the engine bay, just a couple degrees higher than MAF IAT shows, as I have my GM IAT in my IM.
Despite that I have JDM MAP, I have tried to use "Omni 3 bar" and "Omni 4 bar" scalings just for giggles. Omni 3 bar behaved even worse than JDM MAP scaling. As for Omin 4 bar scaling - it surprised me that at least it gave me a chance to hold the throttle and rev my engine higher than 4K...
Anyway whatever scaling I use, whatever i put in my VE table (like 120% from 80-300 load at all RPM), I can not log load higher than 75-ish. Even when my map reads 105 KPA.
As far as I understand it's just a simple math - if my MAP reads 105 KPA and I have put 120% in apprpriate cells in 3D VE table, I should be able to see 125 Load. But whatever I try I always get 75-ish load at 100-105KPA.
I haven't tried to use any other roms including 9417.
Any input would be appreciable as I am totaly knocked down by that situation.






