Speed Density 2.0 (3D VE Tables, Baro)
May 4, 2018, 09:27 PM
#931
Awesome man that's what I wanted to know. So with sd 2.0 the 3d table is pretty much the load ve table and rpm ve from the original sd rom mixed into one table right? That's the only table I will have to touch? The 3d ve table. I noticed now theres baro vs kpa. Does that have to be messed with? What does it do?
May 4, 2018, 10:13 PM
#932
Ok Thank you man. I have the car tuned on regular sd but I want to try this. When I enable closed loop on regular sd I have a lean tip in issue I cant get rid of no matter what table I touch. I was told 9417 rom had bugs and evo 8s are best ran on 9653 and that it may be the issue. I was going to switch to 9653 but after reading this whole thread people are saying that 9417 is best on 2.0 so now I'm undecisive. I was thinking to just trying both of them and seeing what works for me but man that's a lot of work. Now, am I right to assume that with the factory rom settings on the 3d table the car will be rich? Reason I ask is I need to make wot pulls sooner or later to have a baseline to tune from but afraid it may lean out...
May 5, 2018, 01:51 PM
#933
Ok Thank you man. I have the car tuned on regular sd but I want to try this. When I enable closed loop on regular sd I have a lean tip in issue I cant get rid of no matter what table I touch. I was told 9417 rom had bugs and evo 8s are best ran on 9653 and that it may be the issue. I was going to switch to 9653 but after reading this whole thread people are saying that 9417 is best on 2.0 so now I'm undecisive. I was thinking to just trying both of them and seeing what works for me but man that's a lot of work. Now, am I right to assume that with the factory rom settings on the 3d table the car will be rich? Reason I ask is I need to make wot pulls sooner or later to have a baseline to tune from but afraid it may lean out...
May 11, 2018, 03:36 PM
#936
Hey guys so finally got around to trying 2.0. I started with a clean map and car was super rich at idle 11s. Evoscan shows about 40 1byte load at idle and i kept dropping fuel from 10 - 50 kpa and nothing happened. Got pissed off and dropped fuel at 60kpa and this is where idle reponded. It went to 15s. Now, obviously something is off. I checked the formulas and 2byte to 1byte factor and the sensors selected and everything seems right. Im dissapointed. I really want to try 2.0. Has someone come across this issue before? How can i correct this? Thanx guys.
May 12, 2018, 08:39 AM
#939
Hey guys so finally got around to trying 2.0. I started with a clean map and car was super rich at idle 11s. Evoscan shows about 40 1byte load at idle and i kept dropping fuel from 10 - 50 kpa and nothing happened. Got pissed off and dropped fuel at 60kpa and this is where idle reponded. It went to 15s. Now, obviously something is off. I checked the formulas and 2byte to 1byte factor and the sensors selected and everything seems right. Im dissapointed. I really want to try 2.0. Has someone come across this issue before? How can i correct this? Thanx guys.
The following users liked this post:
ronaldo9 (May 13, 2018)
May 12, 2018, 11:52 AM
#941
I am logging 1byte load and it is telling me at idle it is 38 - 40. When making changes to 30 - 40 kpa cell on 3d map nothing happened. The 60kpa cell is where it made the change. So something is off. If kpa to load table is 1:1 then what can it be?
so you’re saying I don’t use 1byte load to log anymore?
so you’re saying I don’t use 1byte load to log anymore?
May 13, 2018, 11:50 AM
#943
Log your map sensor, because thats the actual load value that you will be going off of for tuning your ve map, your fuel map, and your timing map. 1byte load may show a different value than the actual value from your map sensor which may be your issue. For example if i'm trying to tune a cell in the ve map that is under 270kpa, I do a log and check the map sensor reading and find 270kpa and make adjustents depending how far off that cell is. Speed density tuning is simple, you use a pressure reading as your load and rpm and thats it, so to be able to tune accurately and easily use your map sensor!! I can also check your rom to see if there is anything wrong if you wanna pm me I can give you my email address. But again its simple, ditch the 1byte load and use the map sensor instead.
The following users liked this post:
ronaldo9 (May 13, 2018)
May 13, 2018, 02:45 PM
#944
What I did is set up Omni 4 bar for psi and barometer for kpa. I used the formula for kpa in barometer value. Now the high ignition tables x axis is load. You’re telling me you still use kpa reading from map sensor to tune ignition table? When I start messing with it again I’ll take you up on that offer. Thank you.
Jun 10, 2018, 07:22 AM
#945
Newbie
Join Date: Dec 2013
Location: R/F Vladivostok
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
Hello
Where to get firmware
Where to get firmware