Speed Density 2.0 (3D VE Tables, Baro)
Mar 5, 2011, 02:25 PM
#152
So I felt it cut out at lower speed cruise and also on the freeway. I have attached two logs of this happening. Im not sure if you will beable to see it in the logs though.
Also I attached another log of a fith gear pull and it seems that I am unable to go past 15lbs even though Im using the same boost setting from the last rom. I was wondering if anyone else was having these issues.
Also I attached another log of a fith gear pull and it seems that I am unable to go past 15lbs even though Im using the same boost setting from the last rom. I was wondering if anyone else was having these issues.
Mar 5, 2011, 03:43 PM
#153
So I felt it cut out at lower speed cruise and also on the freeway. I have attached two logs of this happening. Im not sure if you will beable to see it in the logs though.
Also I attached another log of a fith gear pull and it seems that I am unable to go past 15lbs even though Im using the same boost setting from the last rom. I was wondering if anyone else was having these issues.
Also I attached another log of a fith gear pull and it seems that I am unable to go past 15lbs even though Im using the same boost setting from the last rom. I was wondering if anyone else was having these issues.
I'm having a little bit of trouble seeing the cutout in the log. I do see some places where the injector pulse width drops dramatically but this is always following a drop in throttle position. Is what I'm seeing your left foot or something the code is doing? If you could better describe where in the log the cut is taking place I could track this down a lot faster.
Mar 5, 2011, 07:07 PM
#155
This is the only spot that I saw where it cut out in one of the logs. My tps usually defaults to around 12.5%. Ill look through the other logs i did today to see if i see any more of them cutting out.
PHP Code:
LogID LogEntryDate LogEntryTime LogEntrySeconds LogNotes RPM TPS TimingAdv KnockSum KnockVoltage OmniMap WideBandAF AEM_Wideband_rear_o2 Load1B ECULoadCalc Baro MAT CoolantTemp Battery AirTemp AirFlow InjPulseWidth InjDutyCycle O2FeedbackTrim
142 3/5/2011 38:54.5 33.91164 2468.75 12.94117647 42 0 0.546 -10.6603 13.24779 20.4 51.8 156.2 14.22602 56.25 0 0 0
Mar 7, 2011, 10:31 PM
#156
This is the only spot that I saw where it cut out in one of the logs. My tps usually defaults to around 12.5%. Ill look through the other logs i did today to see if i see any more of them cutting out.
PHP Code:
LogID LogEntryDate LogEntryTime LogEntrySeconds LogNotes RPM TPS TimingAdv KnockSum KnockVoltage OmniMap WideBandAF AEM_Wideband_rear_o2 Load1B ECULoadCalc Baro MAT CoolantTemp Battery AirTemp AirFlow InjPulseWidth InjDutyCycle O2FeedbackTrim
142 3/5/2011 38:54.5 33.91164 2468.75 12.94117647 42 0 0.546 -10.6603 13.24779 20.4 51.8 156.2 14.22602 56.25 0 0 0
9417:
<table name="Maf Reset Disable (stock 0x2BA1) -> 0x9 (nop)" address="26540" type="1D" level="1" scaling="Hex16"/>
9653:
<table name="Maf Reset Disable (stock 0x2BA1) -> 0x9 (nop)" address="277F0" type="1D" level="1" scaling="Hex16"/>
Mar 7, 2011, 11:57 PM
#157
Evolved Member
iTrader: (12)
Join Date: Aug 2009
Location: ma
Posts: 1,589
Likes: 0
Received 0 Likes
on
0 Posts
I just realized something that first rom i had used with the auto baro where I had to set it to 7500 so it wasnt adjusting with the car on didnt have the stuttering problem. I compelety forgot that 45min trip I took that day not once did it do it.
Mar 8, 2011, 10:04 AM
#159
Evolving Member
Join Date: Jul 2009
Location: MA
Posts: 274
Likes: 0
Received 0 Likes
on
0 Posts
I have been driving around a bit with this now, Im on an Omni 4 bar so the only thing I have touched is the KPA/load table and the 3D VE map. I got it working pretty well although the "stutter" is pervasive. I tried 1,2+3 standard fixes, but not the new one you just put up yet.
It almost feels like a brief fuel cut. When RPM is falling and the throttle is re-applied it seems to happen most often. Any particular parameters I should log for you?
I have no issues with boost, although I have not really hammered on it yet.
I like the tuning interface BTW.
It almost feels like a brief fuel cut. When RPM is falling and the throttle is re-applied it seems to happen most often. Any particular parameters I should log for you?
I have no issues with boost, although I have not really hammered on it yet.
I like the tuning interface BTW.
Mar 8, 2011, 10:41 AM
#160
I have been driving around a bit with this now, Im on an Omni 4 bar so the only thing I have touched is the KPA/load table and the 3D VE map. I got it working pretty well although the "stutter" is pervasive. I tried 1,2+3 standard fixes, but not the new one you just put up yet.
It almost feels like a brief fuel cut. When RPM is falling and the throttle is re-applied it seems to happen most often. Any particular parameters I should log for you?
I have no issues with boost, although I have not really hammered on it yet.
I like the tuning interface BTW.
It almost feels like a brief fuel cut. When RPM is falling and the throttle is re-applied it seems to happen most often. Any particular parameters I should log for you?
I have no issues with boost, although I have not really hammered on it yet.
I like the tuning interface BTW.
Mar 8, 2011, 02:15 PM
#164
I had a question on SD 2.0 on another thread that I thought best to continue here.
I thought I read a while back that SD 2.0 was supposed to have baro correction. I even remember something about SpoolinUp making the adapter for a GM baro sensor. Why didn't that pan out? Wouldn't the baro sensor make SD more repeatable despite seasonal and altitude variations? AFAIK the lack of baro adjustment was the only parameter that would sway someone to stay with their MAF, if they drive between places of different altitudes often (me).
I thought I read a while back that SD 2.0 was supposed to have baro correction. I even remember something about SpoolinUp making the adapter for a GM baro sensor. Why didn't that pan out? Wouldn't the baro sensor make SD more repeatable despite seasonal and altitude variations? AFAIK the lack of baro adjustment was the only parameter that would sway someone to stay with their MAF, if they drive between places of different altitudes often (me).
Mar 8, 2011, 02:38 PM
#165
I had a question on SD 2.0 on another thread that I thought best to continue here.
I thought I read a while back that SD 2.0 was supposed to have baro correction. I even remember something about SpoolinUp making the adapter for a GM baro sensor. Why didn't that pan out? Wouldn't the baro sensor make SD more repeatable despite seasonal and altitude variations? AFAIK the lack of baro adjustment was the only parameter that would sway someone to stay with their MAF, if they drive between places of different altitudes often (me).
I thought I read a while back that SD 2.0 was supposed to have baro correction. I even remember something about SpoolinUp making the adapter for a GM baro sensor. Why didn't that pan out? Wouldn't the baro sensor make SD more repeatable despite seasonal and altitude variations? AFAIK the lack of baro adjustment was the only parameter that would sway someone to stay with their MAF, if they drive between places of different altitudes often (me).
The baro correction really seemed to have the most effect in startup then it became pretty static later on. SD runs fine at altitude once its running so the code i made just uses the map sensor to emulate baro until it starts up.