I have been trying for hours to get tunerpro v5 and winaldl to detect my usb aldl cable with no success. It is the cable with jumper pins near the usb end to select resistance of pin a and b.

Ive been searching all day and tryed setting the com port on both along with latency timer. Tryed latency timer of 1 and com ports 1-6 still nothing.

Does anyone know whats going on?

Will tunerpro find the hardware with no .adx file selected? I just need to get past the hardware part so I can see if it will connect to my vehicle and eventually start datalogging.

why wont the programs detect this cable even tho the com port is the same?

 

did you install the usb to serial driver? i'd start there. you have to make sure the cable is showing up in the device manager correctly.

 

I bought the cable from someone on here and it didnt come with drivers all it says in devices and printers is FT232R USB UART Unspecified. I am using windows 7. When I click update drivers it says they are up to date and device is working properly. When I go Into device manager it says usb serial port (com4).

 

In TP RT V5, there is a "detect cable" button in the set-up pop up box. You can use this to see if TP RT can "see" the cable. No ADX file is needed for this.

As long as the drivers are fine, and the com port is set correctly in TP RT V5, it should detect the cable.

The "Detect Attached Hardware" buttom is for use with emulators, it will NOT detect an ALDL cable.

 

I am also running Windows 7 and was unable to get my cable, prom burner, and Ostrich 2.0 working correctly until I installed the latest driver from moates.net despite the fact that windows told me that my hardware was detected.

 

ok under test for valid cable interface in tunerpro cable is found and functional but will not connect. I am downloading the drivers from moates.net.

Is there a special way to install usb drivers or do I just save them?

Edit NM I found the instructions.

 

ok just installed the drivers from moates and now it connects to the vehicle. I am able to get values on the dash I created. Thank you for the help, I am new at this and excited to datalog tommorow.

What exactly is the latency timer anyway. Does it have anything to do with the delay of the readings. for example it takes a second or two for tps value to change when moving accelerator.

I know the latency timer is supposed to make something faster just dont know what?

 

Sigh. A common source of confusion. Need to find a way to make that clear.

 

Maybe change it to "Detect Emulation Hardware"? "Detect Attached Emulation Hardware"?

 

Frustrated again now it only logs with key on, when running it counts errors and values update only a couple times.