i just got my usb aldl cable from aldlcables.com and downloaded WINALDL so i could datalog my car, but i'm having major issues with it, i cannot datalog at all, ive tried everything, i have a 89 trans am with 1227165 ecm, the calbe came w/ the 10k ohm resistor, ive tried it with and without it. Ive installed and unistalled the cable plenty of times, one of my laptops which is a sony vaio with vista said the usb cable was installed succesfully and is ready to use but still nothing.

I tried it on my older laptop with XP and still nothing,
i didnt think dataloggin would be this complicated, what do you guys think is going on here?

 

I think i have the same problem, is it a usb cable? I buy the usb cable and run it with an old xp laptop when i start logging in the small square on top of the program it is flashing red and that should be green. I think winaldl would'nt work with usb. I make a new cable by myself (from joby's site) and everything works.

 

I've got the same problems with the 165 ECM

Turn the laptop off, hook up the USB->Serial adapter
Turn the laptop on, check the com port
Open WinALDL,
Set the proper computer type in options, and set the proper comport
Comport should read OK when you select it, Change it to 4800 baud

Then turn the key on, engine off
Check for the data stream, the box at the top should blink green and will show 24, 25 or 26 in there and you should see the data populated.

If that doesnt work, with everyone still on, put the usb->serial into another USB port and try again, change the comport etc.

Keep trying till you get some data feed. Sometimes mine will drop randomly, other times it will work perfectly.

Its a pain in the *** to get it but I can usually get it running on 2 or 3 tries.

Good luck

 

I had no problem with serial/UBScable(RS) with winALDL running win98. Is winALDL compartible with Vista?

 

Im not sure if its compatible with Vista or not. I use XP SP3 and it works fine.

TunerproRT works fine in Vista for programming, but not sure about WinALDL

 

It does work with vista, it was just user error on my side.