Connecting to ECM for ALDL datalog
Thread Starter
Member
Joined: Feb 2003
Posts: 242
Likes: 0
Car: Green 1991 Firebird Formula
Engine: 305 TPI
Transmission: T5
Connecting to ECM for ALDL datalog
I made my first few attempts at aldl datalogging today, the outcome was that tunerpro could not detect any hardware.
I am using a max232 cable attached to a thinkpad760.
The thinkpad is attached to a docking station which has the serial port on it.
I have tried every com setting in tunerpro and it will not detect the cable.
I had the other end of the cable plugged into the ecm with the car running when I was trying to connect to the ecm and initialize the hardware.
I built the cable myself, and i'm not 100% confident in the laptop/docking station combo.
I'm not sure which com number to use or how to tell which number is assigned to which port. I've never used windows 95 before and i have huntch the computer is at fault.
Can anyone recommend some tests to perform to see what works and what doesn't?
I am using a max232 cable attached to a thinkpad760.
The thinkpad is attached to a docking station which has the serial port on it.
I have tried every com setting in tunerpro and it will not detect the cable.
I had the other end of the cable plugged into the ecm with the car running when I was trying to connect to the ecm and initialize the hardware.
I built the cable myself, and i'm not 100% confident in the laptop/docking station combo.
I'm not sure which com number to use or how to tell which number is assigned to which port. I've never used windows 95 before and i have huntch the computer is at fault.
Can anyone recommend some tests to perform to see what works and what doesn't?
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
TunerPro does not "detect" ALDL cables.
Figure out what COM port your cable is installed to (for MAX232 it's almost always COM1) and configure TunerPro to use that port. The latest version of TunerPro includes a cable test feature in the preferences. Try it out to make sure your cable is working properly (disconnect it from your car first).
If it checks out, hook it up to your car and go!
Figure out what COM port your cable is installed to (for MAX232 it's almost always COM1) and configure TunerPro to use that port. The latest version of TunerPro includes a cable test feature in the preferences. Try it out to make sure your cable is working properly (disconnect it from your car first).
If it checks out, hook it up to your car and go!
Member
Joined: May 2003
Posts: 263
Likes: 0
From: Lakeland,Florida
I just tried the ALDL feature of TP4, and I couldnt connect. I havent tried earlier versions of TP's ALDL, but I have been using WinALDL successfully. I have a two tans cable, and have a 165 ECM running 6E.
When connected to WinALDL, I see correct data-TPS changes with throttle position, water temp/IAT seem correct, RPM seems accurate, ect.
When I try TP4, I get crazy data when using the 165 ads file for 160 baud (I know it should be 8192 baud), but it *connects*
When I try any other listed 165 ads file- it wont connect at all. I have the COM Port to "2", the same setting that works on WinALDL. I tried all the other COM port settings too- with even lesser results.
Could this be bin related? I am running a modified WBO2 patch 6E bin- APYP, with the ALDL idle speed increase deleted. I also just downloaded TP4, and tried the internet update where I was prompted that I have the newest version. I tried leaving the 10k in place, and also removing the 10K after *connection*.
Any help would be appreciated.
Sorry for attaching to someone elses thread, but the topic seemed appropriate.
When connected to WinALDL, I see correct data-TPS changes with throttle position, water temp/IAT seem correct, RPM seems accurate, ect.
When I try TP4, I get crazy data when using the 165 ads file for 160 baud (I know it should be 8192 baud), but it *connects*
When I try any other listed 165 ads file- it wont connect at all. I have the COM Port to "2", the same setting that works on WinALDL. I tried all the other COM port settings too- with even lesser results.
Could this be bin related? I am running a modified WBO2 patch 6E bin- APYP, with the ALDL idle speed increase deleted. I also just downloaded TP4, and tried the internet update where I was prompted that I have the newest version. I tried leaving the 10k in place, and also removing the 10K after *connection*.
Any help would be appreciated.
Sorry for attaching to someone elses thread, but the topic seemed appropriate.
Member
Joined: May 2003
Posts: 263
Likes: 0
From: Lakeland,Florida
Mangus, I found this on your site in the forum section, as a reply that you wrote;
This is probably why I cant connect, as I am using a Radio Shack USB to serial converter (sorry I forgot to mention that above), but I am interested in how you believe(d) that 4.0 would solve that. I have a baud selection in WinALDL, but I couldnt find any such option in TP4.0. Am I not looking in the right places, or is it that this just doesnt exist as planned?
If ALDL, there are a couple serial->USB adapters taht can't handle being opened at 8192 baud.
If doing 160 baud logging with a serial->USB adapter, you'll have to wait until TunerPro 4.0, as USB adapters require the port to be opened at 4800 baud instead of 2400 baud. You can certainly use WinALDL in the interim. It should work fine.
If doing 160 baud logging with a serial->USB adapter, you'll have to wait until TunerPro 4.0, as USB adapters require the port to be opened at 4800 baud instead of 2400 baud. You can certainly use WinALDL in the interim. It should work fine.
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
TP 4 always opens the port at 4800 baud for 160 baud ECMs. Thats how I believe(d) it would solve it.
Thread
Thread Starter
Forum
Replies
Last Post
wigmobile
Electronics
5
Feb 26, 2025 02:56 PM
gta892000
Cooling
6
Sep 16, 2015 12:37 AM
