Page 17 of 27 FirstFirst ... 71213141516171819202122 ... LastLast
Results 241 to 255 of 404

Thread: Uber-easy DIY USB ALDL Cable

  1. #241
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    ok so i am using the newest driver from january 2014. i am going to downgrade drivers under marks suggestion. i have the ground to pin a and the tx rx to pin e. i hope the driver is the issue. i will try that tomorrow. thanks for all your help. My burn 1 also arrived in the mail today so i got that set up and was able to open it in tuner pro.

  2. #242
    RIP EagleMark's Avatar
    Join Date
    Feb 2011
    Location
    North Idaho
    Age
    63
    Posts
    10,477
    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!

    1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
    1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
    -= =-

  3. #243
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    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.
    Last edited by joegreen; 07-08-2014 at 03:01 AM.

  4. #244
    Super Moderator Six_Shooter's Avatar
    Join Date
    Feb 2011
    Posts
    2,968
    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.
    The man who says something is impossible, is usually interrupted by the man doing it.

  5. #245
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    35
    Posts
    3,026
    i have a driver set as old as 2.4.16, if it were necessary.
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  6. #246
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    i would like to try that driver. does my setup look ok. tie rx and tx together. then one ground.

  7. #247
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    35
    Posts
    3,026
    here it is, along with FTClean to help remove any traces of any existing FTDI drivers.
    Attached Files Attached Files
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  8. #248
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    35
    Posts
    3,026
    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.
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  9. #249
    Electronic Ignition!
    Join Date
    Aug 2013
    Location
    rogerson,id
    Age
    49
    Posts
    10
    hi,i was having problems with a self made arduino cable at first.i noticed that it wouldn't find it if it was plugged into the aldl.the first time it just started working,intermittent stuff is irritating.now mine connects every time,but some times i get errors.even worse with an old dell laptop.i am using an asus tablet with win 8.1 .im looking forward to assembling a Bluetooth aldl for the tablet.i found plans on google.the plans i found was setup for 8192 baud,but im sure the code can be modified.i have seen a post about adding stuff to the ecm definition for tunerpro rt to solve the errors.but im a little confused about the terminology .my aldl cable wont test ok if its plugged into the aldl.but it connects.the 299/$99 ecm uses 160 baud.

  10. #250
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    Ok so i tried that driver and still no luck. When i do the cable test on tuner pro the tx light lights up for a split second. If i take the ground wire and the tx rx wire and rub them together the tx and rx lights light up. I tried different usb ports i tried winaldl nothing worked.

  11. #251
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    how about get hyperterminal going

    poke the rx pin with the 5v pin

    if it's working you should get garbage in hyperterminal.

    or type stuff in hyperterminal, tx light should light up on the board.

    with these modern FTDI chipsets, they shouldnt be that driver-sensitive. the latest driver should be fine..

  12. #252
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    Ok so using hyperterminal only the tx light lights up when i type whatever on the keyboard. I have the tx and rx hooked together. When i touch the wire from the tx/rx to 5v no lights light up.

  13. #253
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i dont care about the light, no garbage shows up in hyperterminal when you poke the rx/tx with the 5v? im calling defective board here or something.

  14. #254
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    I will recheck with my volt meter but i think the tx/rx output 5 volts. Idk if that matters any im just thinking if it outputs 5v and you touch it to its 5v supply would anything happen. Also i noticed that if i touch the tx/rx to ground the device dissapears from the pc and i have to plug it into another usb port in order for it to be recognized. Thanks for your help so far everyone.

  15. #255
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    I am excited to start data logging. Is their a definitive way to test for a bad board.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •