Injector scaling vs actual afr in close loop? Also does ve change closed loop fueling
Feb 12, 2013, 08:44 AM
#91
If you just log ve and kpa can you not just enter the ve by what it read at that kpa?
I still don't comprehend how to get around the difference in load to kpa on a maf to sd rom. My load reads higher on sd per boost level than on maf.
So are we using the right kpa formula then 10isace?
Ya know I looked at your handle for a while and said ten-ac-ious
Ten is ace. Comprehension > me
I still don't comprehend how to get around the difference in load to kpa on a maf to sd rom. My load reads higher on sd per boost level than on maf.
So are we using the right kpa formula then 10isace?
Ya know I looked at your handle for a while and said ten-ac-ious
Ten is ace. Comprehension > me
I'm going to see what Jamie suggests. I think I will go through that log and eliminate all decel rows and set it up so evoscan can read them in the Map Tracer. That would be minutes compared to hours.
I'm using x*1.63345239 now. I felt my kpa #'s were slightly off when I was using 2D Rom with the 1.6667 formula.
That's a great interpretation of my handle. I'm a tennis pro/personal trainer. I teach/coach/play for a living, but I'm getting older and possibly going to let that dream come to it's conclusion. It's actually "Tennis Ace".
I may have to come up with a new handle when I get my new venture up and running.
Feb 12, 2013, 08:49 AM
#92
Lol!
ddd2ner?
Hrm, was that formula written somewhere else to be correct? Jamie took his post down an I was anxious to see what the approved calc was
I just make sure I'm logging while always increasing throttle position . Usually have a hot key to start logging .
And load the car up with brake and or gear
ddd2ner?
Hrm, was that formula written somewhere else to be correct? Jamie took his post down an I was anxious to see what the approved calc was
I just make sure I'm logging while always increasing throttle position . Usually have a hot key to start logging .
And load the car up with brake and or gear
Last edited by 211Ratsbud; Feb 12, 2013 at 08:52 AM.
Feb 12, 2013, 08:59 AM
#93
Lol!
ddd2ner?
Hrm, was that formula written somewhere else to be correct? Jamie took his post down an I was anxious to see what the approved calc was
I just make sure I'm logging while always increasing throttle position . Usually have a hot key to start logging .
And load the car up with brake and or gear
ddd2ner?
Hrm, was that formula written somewhere else to be correct? Jamie took his post down an I was anxious to see what the approved calc was
I just make sure I'm logging while always increasing throttle position . Usually have a hot key to start logging .
And load the car up with brake and or gear
ddd2ner, nice!
SD2pt0I'll have to try that type of logging today. It's a wash either way I think, eliminating decel or your way. Does cruise skew the numbers?
Last edited by 10isace; Feb 12, 2013 at 09:44 AM.
Feb 12, 2013, 09:49 AM
#94
I think I'm onto what Jamie was talking about. I deleted all my decel rows in Excel. Then I loaded it into EvoScan Map Tracer to get an average of VE. It's pretty SWEET! Minutes versus hours!
You can see there still needs to be some smoothing and common sense, but it's a lot less labor intensive.
You can see there still needs to be some smoothing and common sense, but it's a lot less labor intensive.
Feb 12, 2013, 01:16 PM
#97
Also, dont start logging until the scaled coolant temp is above 170*F so you know there aren't any fuel compensations happening. There are tons of little things like that I just know about and forget to mention.
Ideally, we need an adjustable "Throttle > than" feature in evoscan. There is a built-in "throttle > 80" feature but that doesn't help with decel filtering.
-Jamie
Ideally, we need an adjustable "Throttle > than" feature in evoscan. There is a built-in "throttle > 80" feature but that doesn't help with decel filtering.
-Jamie
Feb 12, 2013, 01:22 PM
#99
Also, dont start logging until the scaled coolant temp is above 170*F so you know there aren't any fuel compensations happening. There are tons of little things like that I just know about and forget to mention.
Ideally, we need an adjustable "Throttle > than" feature in evoscan. There is a built-in "throttle > 80" feature but that doesn't help with decel filtering.
-Jamie
Ideally, we need an adjustable "Throttle > than" feature in evoscan. There is a built-in "throttle > 80" feature but that doesn't help with decel filtering.
-Jamie
I'm actually tuning a couple of peoples cars and they keep sending me logs with their cars "warmed up" at 80*F trying to scale LTFT's and WOT. I'm like, "NOOOO!"
Last edited by 10isace; Feb 12, 2013 at 01:35 PM.
Feb 12, 2013, 01:33 PM
#101
My 2d sd rom was very different than my maf fuel table. It was almost a direct AFR target. Huge blocks of 12's at 120 and beyond. I was still getting some lean tip in and some rich conditions at highway cruising right around 0-3psi.
Feb 12, 2013, 04:37 PM
#102
To properly swap over the MAF tune to the 3D SD tune with the VE logging I have suggested, you need to copy over your injector scaling and latencies, fuel & timing maps, RPM and load axis's on those maps, MAF scaling (if you modified that table). Basically every table you have modified from the stock settings.
Then you ideally want the load-to-KPA and all of those SD tables to be set to 1:1 by making sure the left and right columns have the same values.
-Jamie
Then you ideally want the load-to-KPA and all of those SD tables to be set to 1:1 by making sure the left and right columns have the same values.
-Jamie
Mar 20, 2013, 12:09 PM
#104
Evolving Member
iTrader: (2)
Join Date: Jan 2007
Location: Las Vegas
Posts: 124
Likes: 0
Received 0 Likes
on
0 Posts
I am having a little bit of trouble getting the VE logging working. I am using a GM 3 BAR map sensor on my car and have the formula in EVOscan ([LOAD1B]/[GM MAP])*100. The load and GM map both log fine and both are in the logging list above VE but I get "0" in EVOscan. I have also tried using other MAP sensor settings just to see if setting the formula to use the factory map sensor even though it is the wrong scaling as well as adding a space on both sides of the "/" just to see if it works but I still get nothing. Any suggestions would be appreciated.