Calc.VET: correcting MAF and calculating VE (in single log)

Quote:

---

Originally Posted by joecar

Hi Jeff, how's it going :cheers:

---

What up Joe...just stickin my nose in few things to see what's goin on. :grin:

Got back to it today. I loaded a stock maf table in to fix the mess from forgetting the cat protection disable. After one drive it is really close. For some reason though just at wot I get a +2.3 fuel trim just on bank 2. Bank one is zero. Dont know what would be causing this, or if I should even worry about it as the wot air fuel looks really good.

I will attach the last log I did, and the resulting tune.

Wow, Len that looks like a really 'clean' run. It will be hard to get a lot better than that.

Sometimes it may not be worth it to chase down an errant +1% LTFTBEN. Once you are satisfied with your MAF Curve (looks good to me), you have a couple of choices. If you want to buffer in an always negative LTFT, you can always add +1-2% to the entire MAF curve.

Another option since you are hitting such high RPM's is to alter B3809 slightly. Just change your RPM boundaries from 6502, 6503 to 7102, 7013. Sometimes that works. If not re-set the Trims..you may have to fudge a few MAF Frequencies to eliminate that one paticular fuel cell for total perfection.

But, IMO thats a really good look MAF and VE Table. You can probably blend that VE Table easier, now that your MAF is calibrated.

Good job!

I have slightly altered the CALC.VET 'Recommended Pids' to include logging of the NB O2 sensors:

1. GM.HO2S11
2. GM.HO2S21

These pids are highly recommended and are very useful to determine the heath of the NB's, and to calculate an accurate CALC.VET.

To keep channel count at 24 or less, SAE.SPARKADV as dropped. GM.KR was retained.

http://i1126.photobucket.com/albums/...CVETPids-1.png

Page 1 of the thread was updated..Thank You.

I agree with that, we want to see what the front NBO2's are doing, we don't really need spark at the moment; yes keep KR.

Since DAT (DYNAIRTMP) is being logged, could also trade off IAT and ECT for other pids, but only if DAT looks sane.

Hi Shawn, Joe,
Thanks for the resent posts. How do I check the O2s. Or a better question how do I determine the health of the O2s in a log.
Can you give us examples? What to look for.
Jorge

Jorge:

Moved response to 'Mechanical Issues that prevent Tuning': http://forum.efilive.com/showthread....nt-Good-Tuning

Quote:

---

Originally Posted by joecar

I agree with that, we want to see what the front NBO2's are doing, we don't really need spark at the moment; yes keep KR.

Since DAT (DYNAIRTMP) is being logged, could also trade off IAT and ECT for other pids, but only if DAT looks sane.

---

Yea, I never thought about that eliminating those (ECT & IAT). Excellent point. Technically they are not needed..

It would be nice to see GM.INPW1 also..

Quote:

---

Originally Posted by joecar

I agree with that, we want to see what the front NBO2's are doing, we don't really need spark at the moment; yes keep KR.

Since DAT (DYNAIRTMP) is being logged, could also trade off IAT and ECT for other pids, but only if DAT looks sane.

---

That would be fine except for the cars that don't have GM.DYNAIRTMP_DMA and use the calculated DYNAIRTMP instead.

Quote:

---

Originally Posted by Ninety8C5

That would be fine except for the cars that don't have GM.DYNAIRTMP_DMA and use the calculated DYNAIRTMP instead.

---

Excellent point!..