Uber-easy DIY USB ALDL Cable

[EagleMark]

I think a couple people recomended the older driver, I just pointed you to the thread and info thread of the people who found the issue!

Have to give credit were credit is due!

[joegreen]

whenever i test the cable on tunerpro it tests it at 8192 baud. how can i get it to test at 160 baud? I also tried winaldl and that does not work either. win aldl says com4 ok and it is set to 4800 baud. when i check on my ports the aldl cable is assigned com4. i rolled back the driver to the one that works for everybody. im extending a line of credit to all old driver recommenders.

update. i downloaded version4 tunerpro and a ads file for the ecu. now i can get the program to say aldl connected on the bottom in blue but i am not receiving any data and the tx rx lights are not flashing. when i test the cable it is still testing at 8192 baud.

[Six_Shooter]

It won't test at 160 baud, TP RT is not designed that way.

The 160 baud comms are different than the 8192 comms in how they are initiated.

160 baud is flowing all the time, where as 8192 baud needs to have a request message sent first, for the ECM to start sending data.

The differences to have TP RT communicate with each type of ECM is within the ADX set-up, it's not something you control.

[RobertISaar]

i have a driver set as old as 2.4.16, if it were necessary.

[joegreen]

i would like to try that driver. does my setup look ok. tie rx and tx together. then one ground.

[RobertISaar]

here it is, along with FTClean to help remove any traces of any existing FTDI drivers.

[RobertISaar]

when you do the tunerpro cable test, do either the Tx or Rx LED light up for a short amount of time? if Rx and Tx are connected, they should both light up at the same time.