OK, I got a chip that seems to run ok.

One quick question though, does it take our computers a few minutes to "learn" the new chip? Because when I first put the chip in, it ran like total crap, but after a few minutes it evened out pretty good.

Anyways. . . so I've got my little ALDL cable pluged into the E and A slots and I've got the program pulled up on the laptop. So I press the "datalogger" button and select "RAW data" then I hit the "start" button. I let this do whatever it is that it does for about 2 minutes, then I stop it. So now I have this file in a Notepad format that pretty much tells me nothing.

OK, so how the hell do I operate this program?

 

Don't worry about using the data logger feature yet. All that does is data log every piece of data about once every second or so (our tbi ecm's data log slow). You'll see there are several tabs along the top, raw,sensor data, blm, int, o2, and knock. What you want to be looking at is the blm table, this is your block learn memory or basically how your ecm compensates your fueling. Above 128 is lean, below is rich. Thats why your car ran like crap and first and then shaped up. Your car was basically filling in this table. Once it got itself tuned in everything was better. You'll notice at the bottom there are different filtering methods for these tables. You probably want to use the wide avg at first till you get your blm pretty close. I like +- 3 blm. Some guys like +-10. The closer you get your blm the better your WOT fueling is going to be.

You can look at the sensor data table to see whats going on with the rest of your sensors. Pay attention to IAC counts. The closer your idle gets the lower these counts will get. Data logging basically records what this page displays realtime which is handy if you want to go back to a full throttle run and see where you had some knock counts at. This feature is kinda hit and miss with TBI or any ecm at the slower 165 baud rate, since you only get a snapshot of data every second or so.