Speed Density Help
well i found the correct table, u are right like usual there is a async vs rpm table where it was 0 for many cells so i bumped them up to the next highest number in that table which was six, and tada the tip in problem seems gone! VR should verify on their customer cars. also reined in more of the crazy rich boost condition to where it didn't stutter and accelerated under some knocksum cause of the richness?
i see it here. values are
27
5
0
0
0
6
10
10
16
20
26
32
32
32
32
so you changed the 0's and it resolved it without the open loop and mapping or did you still have to do the mapping?
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
88590715
i have asynch_accel_vsrpm
address is 32e4
left side is rpm
500
1000
1500
2000
2500
3000
3500
4000
4500
5000
then right side
0
0
0
0
0
6
10
10
16
20
i have asynch_accel_vsrpm
address is 32e4
left side is rpm
500
1000
1500
2000
2500
3000
3500
4000
4500
5000
then right side
0
0
0
0
0
6
10
10
16
20
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
nvm fail, it didn't work
i am really lost what else to adjust. atleast boost is doing better, i am just down to fine tuning.
i am really lost what else to adjust. atleast boost is doing better, i am just down to fine tuning.
Maybe you should just bump the VE up when the load is over idle kpa for the lower rpm. It could be that the lower VE is just too lean for the car. You could test it by bogging the car at super low rpm to get a reading of what the VE should be at those kpa values.
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
i will try but i don't think thats it cause even when the car was running super rich it still did the same thing, also i think i am still a bit rich because in forced open loop it was running a bit richer than in closed loop.
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
hey i got an interesting question, my car seems to do this since i went SD on occasion when going idle. https://www.evolutionm.net/forums/ec...eird-stft.html
hey i got an interesting question, my car seems to do this since i went SD on occasion when going idle. https://www.evolutionm.net/forums/ec...eird-stft.html
The RAM tables are if you are using a DMA/LiveMAP version of the ROM. If you are and have those tables in RAM, then you can use the LiveMAP client to adjust them on the fly. (I don't know if the ROM you have is the DMA/LiveMap ROM or not, so to be safe, just adjust both RAM and SD tables to be the same, and you'll be fine.)
Sounds like you did something wrong. You must use the correct scaling for the map sensor that you are using. Otherwise, the kpa column of your tables won't make any sense...they will be way off from what the kPa really is. If you are using a 3.5 bar sensor, then make sure you set the scaling accordingly and it keeps.
If you are referring to the injector scaling and injector latency, no, there is no reason to adjust those if your trims are good. There are numerous ways to tune your fueling with the SD patch and the VE tables.
Sounds like you did something wrong. You must use the correct scaling for the map sensor that you are using. Otherwise, the kpa column of your tables won't make any sense...they will be way off from what the kPa really is. If you are using a 3.5 bar sensor, then make sure you set the scaling accordingly and it keeps.
If you are referring to the injector scaling and injector latency, no, there is no reason to adjust those if your trims are good. There are numerous ways to tune your fueling with the SD patch and the VE tables.
I know I need the correct scaling for the map sensor but I thought when I went through every map sensor related table and changed the settings from omni 4 bar to klavico 3.5 it would be set. Do I need to find the scalings and manualy put them into the SD tables for the other tables to actually save as 3.5 and not 4?
Black:
Looks like you changed the scaling but neglected to fix the numbers for Map(KPA)
Copy the right hand side (Load%) into the left hand side (kpa) and it shouldn't run as rich. Keep adjusting until its right. There is my recommendations for the vacuum side only 1 or 2 pages back in this thread.
Looks like you changed the scaling but neglected to fix the numbers for Map(KPA)
Copy the right hand side (Load%) into the left hand side (kpa) and it shouldn't run as rich. Keep adjusting until its right. There is my recommendations for the vacuum side only 1 or 2 pages back in this thread.
Thanks for your responses!
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
back to ve tuning i go
, i think i need a good explanation on how to correctly use map trace then. cause i think that is messing me up.
I know I need the correct scaling for the map sensor but I thought when I went through every map sensor related table and changed the settings from omni 4 bar to klavico 3.5 it would be set. Do I need to find the scalings and manualy put them into the SD tables for the other tables to actually save as 3.5 and not 4?
The problem is Ive opened up the original rom that I downloaded and the settings are all the same. When I go into the tables and change all the 4 bars to the klavico 3.5, those numbers never changed. As I asked above, do I need to manually put those numbers in?
Thanks for your responses!
The problem is Ive opened up the original rom that I downloaded and the settings are all the same. When I go into the tables and change all the 4 bars to the klavico 3.5, those numbers never changed. As I asked above, do I need to manually put those numbers in?
Thanks for your responses!
Scaling is a formula it just coverts number A into number B thats it. In the rom that number is still the same as it always was it just the display in the ECUflash program differently. For example when you switch it out from 4 bar to 3.5 bar you'll see a lot of negative kPa numbers because the numbers behind are the same.
The numbers behind the scene are volts so YES you MUST change them for it to be right. I think i've stated this a couple times already to start simply copy the right hand side into the left and begin tuning.
Thread Starter
Evolved Member
iTrader: (21)
Joined: Jan 2006
Posts: 1,453
Likes: 0
From: Clifton New Jersey Lived: Daytona Beach, Florida Lived: Port Orange, Florida
First what you really need to do is stop single point editing maps. If you view you map with graphing it looks like star wars canyon so you're fueling is going everywhere. Try to be smooth in your changes always have graphing enabled when your mapping changes VE is smooth and it changes smoothly. I changed the general trend of your VE so its smooth again and emailed you.
Secondly the o2 sensor trim is screwing you up. The o2 sensor trim just isn't fast enough to compensate for a barely tuned SD map. When your beginning like this you need to look at what the map is doing and not what the fuel sensor is doing to your map some time later. The best way to open loop is to change the open loop load and i'm including that change with your rom. Your async changes may need to go near default to really have the best effect.
Tips:
Since your really starting from scratch like I did I think it will be best to make changes in the beginning solely to the kPA vs load% table (2d one). This is a broad change to all the fuel and it will help you center the fuel and VE map for fine tuning later on. Once you have the kpa vs load down to where only quarkyness remains, ie stomp the throttle and slight lean or letting off the throttle a little rich in certain RPM areas its time to focus on the VE map.
Last edited by RoadSpike; Mar 8, 2011 at 12:10 AM.



