Yeah itll take some time but I can definitely say that the car feels smoother to drive now.

 

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.

 

I'm willing to bet the boost problem is unrelated to the SD code as it really doesn't have any hooks to the Maf routine. I do see your load capping out at 200 so i'm guessing the desired engine load is too low or your wastegate duty cycle is set to 0 becuase it goes from 100% to 0 and then when it drops under 200 load it goes back to 100 again.

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.

 

alright ill look through the logs and see what I can find. The drops in IPW may be where Im on decel.

 

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.

 

Found a spot that may be the bit thats used in fuel cut on decel. I think by disabling this we may gain some insight to whats going on. If it still cuts out I can concentrate on the multiplier value that applied to the SD code instead of the SD values themselves.

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"/>

 

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.

 

Thats interesting but the new one just adjust the baro in the same way just the rpm is a max thing now not a min thing. If the baro is causing the faults i can look into that too.

 

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.

 

I'm thinking the problem may really be some sort of decel fuel cut like when your going downhill. All i need to know is basics like load, rpm, and the ipw so when it cuts out if its cutting fuel i can see that.

 

The stutter happens between 2-2.6k and will happen even if Im lightly accelerating, but doesnt happen if I go over maybe 40%tps or like 0vac.

 

Thats good info means the stutter is definitely load dependent. Maybe there is something to that magic range of load and rpm where a check happens.

 

my solution wot till 3k then cruise lmao.

 

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).

 

It does have a baro correction in it just a couple things to note about it.

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.