TunerPro Data Log Session & .csv File (Anyone See Anything Odd?)

[fcastro]

Hi fella's well I picked up my cable from moates and installed TunerPro and with the help of a guy named Andy I got the setup working. I plan on writing a tutorial this weekend for newbies such as myself

Ok so I am attaching my data log file. I used the "updated 1227730.ads" Datastream definitions that I found on moates site. Then I started to record my data (8 minutes/car parked)

Anyone notice any oddities? Only thing I noticed is that the BLM went up to 131 once the car was getting warm. From what Andy told me the car should be at a steady 128 unless I climbing hills. I would appreciate any feedback

Here is the ADL file (my TunerPro RT saved log file) zipped up:
http://mysite.verizon.net/vze2bh7m/m...camaro_log.zip

Here is the .csv for excel:
http://mysite.verizon.net/vze2bh7m/m...camaro_csv.zip

[Pampered-Z]

Looks just fine to me. Staying in block 4, map, O2s, Map and ICC are stable, looks like it changed the TLs a small bit.

First, just scanning the car idling isn't going to tell you allot, you really need to scan the car being driven both as a constant RPM/load and at various RPMs/loads.

In general terms, the BL is not going to stay at 128. 128 is the middle on your cells, but the computer will adjust to keep the 14.7 fuel ratio. As long as your close to 128 your fine. If you start going farther away (and staying away) from the 128 you may have issues, at 20+/- of 128 (or if one bank is 5 +/- of the other on 4th gens at least) then you may have an issue. An occational change is nothing to worry about, the ECM changed the BL since it was doing allot of compensation to the injector pulse, buy dropped it back down. And again, you were just idling. Drive the car and scan it and see who the reading look.

If you do notice the differences I mention about you then need to start looking at weak O2s, vacuum leaks, bad injectors, or tune up.


John

[IROCdan330]

I honestly don't understand what just datalogging does for anyone without the ability to change something if need be, besides being able to see trouble codes and/or diag something like a faulty sensor, lean/fat issues, etc.

GM does it like this:
Block Learn Multiplier (BLM) is what is known as long term fuel trim.
Integrator (INT) is known as short term fuel trim.

When the car hits closed loop, meaning the oxygen sensor is warmed up, the computer will begin to adjust the fuel trims to make an attempt at maintaing stoich. Like pampered-z said, 128 is the middle. 128 is what would be considered perfect fuel trim.

The integrator will make very fine adjustments to the 128 BLM cell, and once it reaches its max either rich or lean, it will move a BLM cell up or down accordingly, and reset itself back to 128. This process goes on over and over and over and over. When the block learn number goes up passed 128, it means the vehicle is lean, and is adding fuel. If it falls below 128, it means it is rich and subtracting fuel.

Other things you may want to pay attention to, knock count, knock retard, spark advance, etc.

But like I said i dont see what datalogging alone is going to do for you.