Well, this is my last resort. Here is the breakdown:

- OBD1 ALDL Cable for ALDLCable.com
- TunerPro RT (Free Version)
- 1991 7730 running $59 for my turbo 3.1l

I had no issues last year connecting and tuning my vehicle. I had some issues with my laptop where it updated to windows 10, wouldn't handle it, so I downgraded it back to windows 7. This is the same laptop I used last year.

All the drivers have been installed correctly and TunerPro works with my Burn 2. I cannot seem to get it to detect my ALDL Cable though. The computer detects it, updated with the drivers from aldlcable.com, set the com port, etc etc. I keep getting the same error when I try to test it in TunerPro.

Any help would be fantastic. Thanks!

 

Try another '7730, the current one may have a bad ALDL serial port.

RBob.

 

I do have another 7730 I can swap out and try, but shouldn't TunerPro recognize the cable? I'm wondering if the computer is faulty due to the other issues I have experience with it.

 

So just to be clear, the "Test for valid cable" test responds with a "cable not found" result?

 

Yes SixShooter, that is exactly it. Which leads me to believe it is a computer related issue as it recognizes the cable but TunerPro does not.

 

This is the confusing part. Just to make sure, the laptop detects the ALDL cable and allows the drivers to be installed. But TunerPro RT can't find the cable.

In this case I'd say that TP RT isn't set up properly. Can use the Device Manager to see which COM port is assigned to the cable.

RBob.

 

Yes it is confusing me too. I will try and reinstall Tuner Pro and also try another laptop today.

It is set to COM 3, I also tried 1,2, and 4. No luck.

 

Here are the Tunerpro settings I'm running (I have a Dell Inspiron 640m running Win7)

Under Tools, Preferences, Data Acq./Emulation tab...

Interface type = Use Plug-in

Data Acq.I/O Plug In component = TunerPro Data Acquisition I/O Interface

Pushing the button for Configure Component, the dialogue box pops up and has Port Type = Serial and my port number = {COM5}

The two boxes are checked for Load last Data Acq Def at Start and Warn of ADX/XDF Link Mismatch.

 

ULTM8Z, my settings are same besides the port number. The port number does match in the preferences along with in the device manager.

I tried this again on another laptop and my desktop with no avail. I believe this may be a cable issue instead of a software issue. I called aldlcables.com and left a message.

I don't understand how the cable works perfect with no issues last year and all of a sudden is dead out of the box. Really really irritating.

 

Well, I was able to get the cable to connect with an absurd amount of pressure on the usb connection. I believe there is something wrong inside the cable.

 

Just to update and close this thread:


Contacted aldl.com, after a few emails and calls Ken got back to me today. They offer a one year warranty on the cables but I was out of that range. He offered to ship me a new one for $30 (half off) so I decided to go that route.


Not sure how long the car will stay obd1... haha

 

make sure to update us... I had trouble datalogging myself. Going to try this fix when I get my new memcal (which I THINK I fried)


https://www.thirdgen.org/forums/diy-...pro-rt-da.html