When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Hi, I'm converting my 9653 based SD 1.0 rom to SD 2.0, 2.3L stroker motor using Omni 4 bar and GM IAT. Do I leave the KPA to load and map sensor KPA tables stock and use the 3D ve table to tune or do I have to adjust them? And the 3D ve table only effects fueling and timing is that correct? Or can i use that table to modify loads?
Did anyone ever answer this? I have some old logs with my Maf and map sensor logging boost. If I'm using that to set up my tables should I leave kpa to load 1:1 or adjust it and then adjust the ve table?
Did anyone ever answer this? I have some old logs with my Maf and map sensor logging boost. If I'm using that to set up my tables should I leave kpa to load 1:1 or adjust it and then adjust the ve table?
I usually leave the kpa to load tables 1:1. I've also found that adjusting the MAF scaling and compensation tables can be more helpful and predictable than adjusting the VE tables.
I usually leave the kpa to load tables 1:1. I've also found that adjusting the MAF scaling and compensation tables can be more helpful and predictable than adjusting the VE tables.
never mind i got it
Last edited by wordword; Jan 30, 2021 at 05:35 AM.
I have my load to kpa 1:1, but in my logs 100kpa is showing around 65load causing me to run lean. Is this normal? I have 1000cc injectors and hks 272 cams. I can use maf scaling to correct it, but shouldn't it be closer to 1:1?
also changes to ve does not do much at higher loads 100+
I have my load to kpa 1:1, but in my logs 100kpa is showing around 65load causing me to run lean. Is this normal? I have 1000cc injectors and hks 272 cams. I can use maf scaling to correct it, but shouldn't it be closer to 1:1?
also changes to ve does not do much at higher loads 100+
Load to kpa will be 1:1 up to about 100kpa, but beyond that it will diverge. To understand how to define that table properly you need to log boost (kpa) and Load and then graph boost (kpa) as a function of Load, which I show below and this then gives you the correlation. Remember, you must log the Load value that corresponds to the load value used in your ignition, MIVEC, and fuel table (not VE table). What this table does, as best I can tell, is applies the VE correction to the correct LOAD in your Fuel Maps. Therefore, the VE table is the only table that actually references boost (kpa) whereas all the other tables reference the calculated load. I explain it all here.... https://www.evolutionm.net/forums/ec...onversion.html
If you look below as an example, the Load:kpa ratio is 400:320. Therefore, when load is 400 I have 320kpa of boost.
Load to kpa will be 1:1 up to about 100kpa, but beyond that it will diverge. To understand how to define that table properly you need to log boost (kpa) and Load and then graph boost (kpa) as a function of Load, which I show below and this then gives you the correlation. Remember, you must log the Load value that corresponds to the load value used in your ignition, MIVEC, and fuel table (not VE table). What this table does, as best I can tell, is applies the VE correction to the correct LOAD in your Fuel Maps. Therefore, the VE table is the only table that actually references boost (kpa) whereas all the other tables reference the calculated load. I explain it all here.... https://www.evolutionm.net/forums/ec...onversion.html
If you look below as an example, the Load:kpa ratio is 400:320. Therefore, when load is 400 I have 320kpa of boost.
Great information. I also discovered that for some reason the folder where ECU flash is stored, is set to read only and when I make changes like set the proper scaling for my map sensor, it's not saved and goes back to the 4 bar map sensor every time I reopen ECU flash.
Load to kpa will be 1:1 up to about 100kpa, but beyond that it will diverge. To understand how to define that table properly you need to log boost (kpa) and Load and then graph boost (kpa) as a function of Load, which I show below and this then gives you the correlation. Remember, you must log the Load value that corresponds to the load value used in your ignition, MIVEC, and fuel table (not VE table). What this table does, as best I can tell, is applies the VE correction to the correct LOAD in your Fuel Maps. Therefore, the VE table is the only table that actually references boost (kpa) whereas all the other tables reference the calculated load. I explain it all here.... https://www.evolutionm.net/forums/ec...onversion.html
If you look below as an example, the Load:kpa ratio is 400:320. Therefore, when load is 400 I have 320kpa of boost.
new problem now, 3d ve map does not seem to affect afr or pretty much anything
So been away for a while, been tuning a lot of subarus lately but getting back into the evo side. A vehicle I have been trying to setup lately has been giving me issues. It is a JDM evo 8 with original ROM ID 93670005. I have been trying to get it configured on the 965 version of the 3D SD rom. Issue i'm having is as soon as I change the immobilizer ECU internal ID the ecu file seems to get corrupted. I save all the changes and open the map and a whole bunch of stuff is missing. Has anyone else had any issues like this? Can someone confirm that the 965 variation is compatible with JDM evo 8s?
So been away for a while, been tuning a lot of subarus lately but getting back into the evo side. A vehicle I have been trying to setup lately has been giving me issues. It is a JDM evo 8 with original ROM ID 93670005. I have been trying to get it configured on the 965 version of the 3D SD rom. Issue i'm having is as soon as I change the immobilizer ECU internal ID the ecu file seems to get corrupted. I save all the changes and open the map and a whole bunch of stuff is missing. Has anyone else had any issues like this? Can someone confirm that the 965 variation is compatible with JDM evo 8s?
Hello Buddy,
I have flashed many Evo 8s with 9653 rom but i use the 2d original SD roms that is more stable and does not get corrupted, works very well for me.
I experienced Load issues and jitter fix didnt seem to work on the 3d rom.
Hello Buddy,
I have flashed many Evo 8s with 9653 rom but i use the 2d original SD roms that is more stable and does not get corrupted, works very well for me.
I experienced Load issues and jitter fix didnt seem to work on the 3d rom.
Thanks for the reply mines. Have you been able to get any JDM evos running on the SD 2.0? I suppose I can try the 1.0 but I have never used it before. I went straight to the 2.0 as I didn't like the fact that it didn't have an actual VE table which after tuning standalones I was like whats this lol.
Thanks for the reply mines. Have you been able to get any JDM evos running on the SD 2.0? I suppose I can try the 1.0 but I have never used it before. I went straight to the 2.0 as I didn't like the fact that it didn't have an actual VE table which after tuning standalones I was like whats this lol.
Well , i have tried a couple of times , car starts and runs but logged load varies alot no matter what values you put in it.
On the other hand, S.D 1.0 ran perfect .
Well , i have tried a couple of times , car starts and runs but logged load varies alot no matter what values you put in it.
On the other hand, S.D 1.0 ran perfect .
Yeah I tried the 965 variation of the 1D SD and still no go. Since its been a while sine setting a rom up from scratch, the only things I swap from the old rom to the new rom in the immobilizer section is Immobilizer right? I have the hex set to 0055 since its an 04, init code is still at 0001, and ecu internal ID is left alone as well correct?
Yeah I tried the 965 variation of the 1D SD and still no go. Since its been a while sine setting a rom up from scratch, the only things I swap from the old rom to the new rom in the immobilizer section is Immobilizer right? I have the hex set to 0055 since its an 04, init code is still at 0001, and ecu internal ID is left alone as well correct?
