FIC Injector Data

[ferocity02]

So, are you cutting down the VE table in the decel area and it won't lean out?

While I'm datalogging I have B0120 set to 400 RPM, so it should only be running off the MAF sensor, correct?

I have not been making changes to the VE table (not yet at least) because I was focusing on why my fuel trims were going max negative. Once I got that sorted I was going to get the VE table dialed in and then set B0120 back to 4000 RPM.

Is my thinking here off?

[BLK02WS6]

Yes, if you have B0120 set to 400 rpm, you are on the MAF table. I generally do it the other way around and tune the VE first and then the MAF - but, that's just me... Are you trying to lean it out by reducing the MAF table in the decel area? It would seem that the Hz that it sees during decel are the same ones that it will see at idle - so if you lean out the decel, you will lean out the idle. Is that what you are running up against? This is why I tune the VE first - if you look at the VE cells you are in during decel, they are different than the idle cells. After getting the entire VE right, then I put the MAF back on line and tune the MAF table (I keep the VE on line when tuning the MAF - if you got the VE right in SD, any correction needed now is from the MAF). To me, things just seem to fall into place a lot better doing it that way - but, like I said, that is just my way of doing things.

[ferocity02]

Yes, if you have B0120 set to 400 rpm, you are on the MAF table. I generally do it the other way around and tune the VE first and then the MAF - but, that's just me... Are you trying to lean it out by reducing the MAF table in the decel area? It would seem that the Hz that it sees during decel are the same ones that it will see at idle - so if you lean out the decel, you will lean out the idle. Is that what you are running up against? This is why I tune the VE first - if you look at the VE cells you are in during decel, they are different than the idle cells. After getting the entire VE right, then I put the MAF back on line and tune the MAF table (I keep the VE on line when tuning the MAF - if you got the VE right in SD, any correction needed now is from the MAF). To me, things just seem to fall into place a lot better doing it that way - but, like I said, that is just my way of doing things.

The decel MAFFREQ is around 3250, and idle is more like 2800, so they are not the same. The issue was that no matter how much I reduce the MAF table in decel it always goes rich. I think it was because my injectors were staying open too long hitting a minimum pulsewidth. I kept reducing the MAF table until there was a dip at 3250 and I said no more, something else had to be the issue.

I went back to the FIC settings, made B9021 equal to B4003 and B4004 (0.125ms) and then dropped B3701 by 10%, now the fuel trims are much better and aren't going max negative with the stock MAF table.

I'm still on the edge of going to 2 bar COS and ditching the MAF. Waiting to hear back from my tuner.

[joecar]

Sanity check: check the tables to make sure idle is not enabling (if for some reason idle is enabling while traveling, then it will alter the airmass and fueling).

[ferocity02]

Sanity check: check the tables to make sure idle is not enabling (if for some reason idle is enabling while traveling, then it will alter the airmass and fueling).

Max speed and throttle for idle B0107 and B0108 are both zero.

[5.7ute]

Log GM.VOLTS, GM.AFR, GM.INJFLOW, DYNCYLAIR_DMA, CYLAIR_DMA, IBPW1 or 2, as well as speed, TP etc & I will crunch some numbers when I get a chance.
Cheers Mick

[joecar]

Hey Mick, thanks.

[ferocity02]

Mick, I haven't gotten a chance to log that data for you, been busy getting COS5 2bar SD working. I was hoping it would help but I'm having a similar issue I think. Instead now the low MAP columns of my VE table are getting the shaft.

I made B9012, B4003, and B4004 all zeros. It helped a little, but it's still going rich around 1200 RPM on decel. Next thing would be to reduce the small pulse adjust.

I can still log that data for you. Do you want me to put the above calibrations back to what FIC recommended first?

[5.7ute]

Mick, I haven't gotten a chance to log that data for you, been busy getting COS5 2bar SD working. I was hoping it would help but I'm having a similar issue I think. Instead now the low MAP columns of my VE table are getting the shaft.

I made B9012, B4003, and B4004 all zeros. It helped a little, but it's still going rich around 1200 RPM on decel. Next thing would be to reduce the small pulse adjust.

I can still log that data for you. Do you want me to put the above calibrations back to what FIC recommended first?

Yes. Use the stock calibrations from FIC & set minimum transient pulsewidth (B9021) to the same 0.125ms. Make sure with the CYLAIR & DYNCYLAIR pids that you log the ones with the _DMA added. These are Direct Memory Access pids & let us know exactly what the pcm is using for airmass.

[ferocity02]

Got that data for you Mick. But, for some reason the CYLAIR_DMA and DYNCYLAIR_DMA would not validate on my COS5 OS 2bar OLSD, but I attempted to log them anyways and it looks like I got data for them... Not sure if its correct data or what...

I put all of the injector data back to FIC's and made B9021 0.125ms to match B4003 and B4004. It was running rich everywhere because I was tuning it with B3701 reduced 10% from FIC's data.

Let me know if you can draw any conclusions from this data. Thanks!