OK, it's time to try again.

I have the ALDL cable, a laptop, and WinALDL. So what I need is step-by-step instructions on how to use ALDL. I can't figure it out. I don't know how to use the program and I don't know how I should run the car in order to log, nor how long I should let it datalog.

Please be gentle.

The PROMinator is on the way and I've got emissions this week. I'm also going TAD to VA Beach for the summer, so I've got to get this thing tuned.

 

i would calculate BPW first and burn you first bin with that correction as a basis. assuming that done winaldl has to be set on proper eprom or proper ECU. i forget which. also needs to be set to proper COM port if i recall. once that done it should begin logging data. i guess the first thing i looked at was the BLM's. they populate when there are sufficient hits at that rpm/map. i would think at idle would be first hit/log. then in neutral off idle you can populate other BLM cells and look for a trend(rich/lean). best results would be a level road and slow deliberate steady speeds after you get in neutral data. dont get frustrated if you fail to connect to winALDL at first.

 

If you havnt already, dp a tuneup before you do any tuning. I would at least put in a new O2 if the other one is more then a year or two old.

Man, its been quite some time since Ive used winaldl, lets see how much I can remember.

To datalog, you stick the two signal wires in their respective places in the ALDL connector (this will be coverd in the GIFs sent with winaldl). If the ALDL cable has a female ALDL connector, then plug 'er in.

First, open up the setup dialog box in winaldl.

Hook up the cable to your laptop and select the serial port that the cable is hooked up to. If the laptop has a serial port, then it'll probably be something like COM2 or maybe COM1, but I think the first serial port is sometimes reserved for the mouse on the older machines. If your using a USB adaptor, then see the instructions. Set the baud rate to 2400, or whatever the default is in winaldl. Lastly, select the ecm you have so the raw values sent from the ecm will be formatted correctly

Turn the car on, if all is well the upper box will flash '20' with a green background every 1.2 seconds. This tells you there is a fulll 20 byte frame being sent from the ecm at regular time intervals. If its some other number flashing randomly with a red background, then theres a problem. If theres nothing at all, then its likely the pc isnt configured right.

To datalog, drive the car around normally with no high throttle or sudden acceleration. You want to get lots of data so you can use it to tune the parts of the VE table that the motor will be in when its getting the sniffer. WinALDL has built in features that plot out the averaged, narrow averaged, latest, wide averaged, etc. BLMs on a rpm vs kpa tables. These will correspond to locations in your VE table. Each table from winaldl also has a # of samples table that shows the number of samples obtained for the data in each cell. If there are less then a dozen or so samples, then disregard the BLM value there. Wide average works well for tuning teh P/T side of the VE if you have lots of data. After your done datalogging, just save the tables before you exit winALDL and theyll be stored in the directory tha winaldl is in.

This would be alot easier to explain with screen shots from the program. Maybe someone has a few?

 

Good advice on replacing the O2 sensor!

I wish someone had told me to replace the O2 sensor before I started logging/tuning. I bet I burned over 50 chips before I realized the O2 sensor was "lazy".

If you used any silicone (RTV) on the intake anywhere, there's a good chance the O2 sensor has been "posioned".

Here's some reading on the subject.
https://www.thirdgen.org/techbb2/sho...silicon+sensor

 

Everything on the motor is new along with the O2 sensor.

Dimented: Some screen shots would definately help.

 

Dim: could you explain further?

i am aware multiple samples in a specific cell are helpfull. i sometimes find 50-100 in some cells. why would a few hits in a cell not be considered? say we hit 2800 rpm/70 map and show 10 hits @ say 136 blm. what harm would it do to change the VE(enrichen) in that cell?

 

Is there a more user friendly program out there to datalog with?

 

all i am aware of is datamaster and tunerpro. i am sure there are others. i use winaldl currently. i i use it for is flag CL - IAC counts - BLM's. seems lately i only use the WB for datalogging.

 

some tuning programs do not support all ECU's.

 

winaldl one of the easier ones to use.

 

BLMs only have meaning during steady state operation. With only one or two samples, the computer still couldve been chasing the AFRs at that point and the BLMs would have little meaning. the more samples, the closer the BLMs are to representing what the actual fueling is.

 

makes sense. the INT i understand reloads back to 128 every time the BLM moves 1 point so few hits means an incomplete correction of BLM? is it possible it is a trend (rich/lean) however?