Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 404

Thread: Uber-easy DIY USB ALDL Cable

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Carb and Points!
    Join Date
    Aug 2014
    Posts
    2
    Quote Originally Posted by delcowizzid View Post
    did you turn on cable echo in the adx or in preferences of tunerpro as they cable will pickup whats sent when you send it
    Yep, sure did.
    Also tried EFILive and "OSE Enhanced Flash Tool" but both complained about not finding a heartbeat.
    I've seen chatter in EFILive, but it wouldn't sync because it couldn't get a heartbeat

  2. #2
    Fuel Injected! CDeeZ's Avatar
    Join Date
    May 2012
    Location
    Jokelahoma
    Posts
    422
    Delcowizzid, can you elaborate on cable echo?

    I've got a buddy with a computer science degree who is going to take a look at this.

    It sounded too good and easy to be true, looks like it might be :/

  3. #3
    Carb and Points!
    Join Date
    Dec 2015
    Location
    Belgium
    Posts
    2
    hi, I built a similar cable and it works on WinALDL but I cannot get it working with other soft (TunerPro ...)
    what am I doing wrong ?
    thanks for the feedback

  4. #4
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    35
    Posts
    3,026
    if it works with other software, then you're down to a configuration or file presence issue. do you have the correct ADX loaded for the car you're dealing with? do you have the correct COM port selected from within the Tunerpro Preference menu?
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  5. #5
    Fuel Injected!
    Join Date
    Dec 2013
    Location
    Middle of Nowhere, MT
    Posts
    107
    Quote Originally Posted by pbob65 View Post
    hi, I built a similar cable and it works on WinALDL but I cannot get it working with other soft (TunerPro ...)
    what am I doing wrong ?
    thanks for the feedback
    Some links that may be of help

    http://ls1tech.com/forums/lt1-lt4-mo...-tutorial.html

    http://www.gearhead-efi.com/Fuel-Inj...-and-Tutorials

  6. #6
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,478
    The cheapest I found is here.

    http://www.aliexpress.com/item/new-1pcs-Replacement-Remote-Control-For-Panasonic-3D-TV-N2QAYB000659-free-shipping/32503962227.html


    I will order some and post result.


    I also found this. How do you think will this work with a true serial port.

    http://www.aliexpress.com/item/MAX32...867498167.html

  7. #7
    Electronic Ignition!
    Join Date
    Mar 2016
    Location
    Iowa
    Age
    42
    Posts
    16
    Hoping someone can help me with some troubleshooting. Just got the USB to serial adapter last Friday and built my harness and tried it out over the weekend with mostly failed results.

    Here's the exact one I bought: http://www.ebay.com/itm/360871019374?_trksid=p2060353.m2749.l2649&ssPageNa me=STRK%3AMEBIDX%3AIT

    I followed the simple instructions from the original post on this thread, used no diodes or resistors, just connected the Tx and Dx together and plugged that into my 8192 terminal (terminal "M" on my OBD1 12 pin port) and the ground to the ground terminal (terminal "A").

    Real quick, the car I'm working on is my 1994 Cadillac Fleetwood w/ LT1.

    When the FT232RL chip is plugged into just the car, both the tx and dx leds light up constantly with the car on (actually they appear to blink rapidly, but fast enough that they appear to be solid on).

    If I'm plugged into the laptop via USB the lights will blink when it's first plugged in and being recognized, and if I try to connect to it from any software. However if I connect it to both the car and the laptop, it mostly ceases to function.

    So let's run down quick what I've done so far: I've tried 3 different USB cables, I've tried 2 different laptops running on a different OS (my current laptop running 64-bit Win7 and my old laptop running 32-bit WinXP), I've tried several different versions of the driver, I've built two different harnesses (my first was kind of weak sauce, just threw it together quick with stuff I had laying around so I could test it out first, I then built a second one with better wire and soldered all my connections to rule out that as the culprit) and I've tried several different tuning programs.

    I believe I have the correct files, I got my $EE file from, I can't remember now, it wasn't on here because I hadn't signed up for an account yet, possibly from the TunerPro website, but I may try downloading a different definition file from this site just to rule that out. I've attempted to connect using TunerPro RT, TunerCATS RT and Datamaster. TunerPro RT will recognize the adapter if it's not connected to the car once I select the correct COM and will pass the test every time. But once I connect to the car and attempt to acquire data, it insta-fails every time.

    TunerCATS RT has yet to have any luck connecting to it, but I've messed with that program the least so I'm not confident I'm doing it correctly on there. Datamaster seems to work until I actually try to record data. It will pass the test, or at least it was until last night. Now I get an unknown error when I test it, but that may be a driver issue. One of the last times I plugged it back into the laptop and it was being recognized it identified it as a Microsoft serial mouse and loaded new drivers for it, so I think I need to go back and wipe out all the drivers and try installing those again after a reboot. BTW, I'm primarily working from the old XP laptop since that one is smaller and easier to setup inside the car.

    Before I developed that issue though I was able to record data and have several sessions recorded both from the engine and trans and alternating between both, but during every session it would lose communication, wait for a few seconds and then re-establish the connection, work for a few seconds and then drop out again. And while some of the data it collected appears to be perfectly accurate such as RPMs and engine temps, other data is completely whack. When reviewing the one session where I actually drove around for a bit, there were times when my reported speed (in MPH) would jump to well over 100. Since I was driving in town on 25-35 mph speed limit streets, I wasn't going anywhere close to 100 or above.

    I also noticed there's a window in Datamaster that monitors DTCs, and it was randomly lighting up like a christmas tree and mostly didn't make any sense to me. I do get a couple recurring trouble codes, one from a steering sensor and one for interior lighting I think, I'd have to pull those from the HVAC unit to see which ones they are, but I've never put much effort into tracking them down since the car functions perfectly. No SES lights or any idiot lights ever come on and the only real problem it's ever had was when it dropped an O2 sensor last year which I replaced. I haven't replaced the other side yet cause they're kind of a pain in the butt to get out being a 20+ year old car with 130k miles on it and pretty much still 100% of it's original equipment still on it, things like that are a little rusty and little stubborn to remove. But it's on the agenda now that spring is coming.

    If anyone is interested, I can upload the sessions I saved from Datamaster and see if anything in there makes any sense or could point you in the direction of where my problems are originating from. But at this point it's just driving me nuts. One other thing I just remembered, it seems that whenever I'm plugged into both the laptop and the car, the LEDs will blink some for a little bit, but shortly after they go dark, which doesn't make sense if it's receiving data from the PCM, but as soon as I unplug the USB from the laptop, they light right back up. Maybe I just got a bad adapter? I don't really know how to check for that, but if anyone has any ideas, I'm all ears.

    If I missed any important info, ask and I'll provide what I can. I also have pictures of my adapter and the cable I made if anyone wants to rule those out as my culprit. Or maybe I'm just missing something simple and obvious, I'm experienced with the mechanical side of cars, and I'm even pretty good with electronics and computers, but engine tuning is well outside my normal wheelhouse so I freely admit to being a complete noob as far as that is concerned. I just remembered that at one point I even grabbed my phone and filmed datamaster for a few seconds so if anyone wants to see that I can upload it as well, because while I'm not up to snuff on the tuning stuff yet, what I was seeing on the screen while it was recording really seemed strange.

    I think that's enough rambling for the moment, again any ideas, questions, let me know. And if anyone wants pics, video or the datalogs I saved say so and I'll copy them over to this laptop and upload them.

    Thank you for any and all help.

  8. #8
    Fuel Injected! EDZIP's Avatar
    Join Date
    May 2012
    Location
    Champlain, NY
    Age
    73
    Posts
    330
    Quote Originally Posted by schlicky13 View Post
    Hoping someone can help me with some troubleshooting. Just got the USB to serial adapter last Friday and built my harness and tried it out over the weekend with mostly failed results.

    Here's the exact one I bought: http://www.ebay.com/itm/360871019374?_trksid=p2060353.m2749.l2649&ssPageNa me=STRK%3AMEBIDX%3AIT

    I followed the simple instructions from the original post on this thread, used no diodes or resistors, just connected the Tx and Dx together and plugged that into my 8192 terminal (terminal "M" on my OBD1 12 pin port) and the ground to the ground terminal (terminal "A").

    Real quick, the car I'm working on is my 1994 Cadillac Fleetwood w/ LT1.

    When the FT232RL chip is plugged into just the car, both the tx and dx leds light up constantly with the car on (actually they appear to blink rapidly, but fast enough that they appear to be solid on).

    If I'm plugged into the laptop via USB the lights will blink when it's first plugged in and being recognized, and if I try to connect to it from any software. However if I connect it to both the car and the laptop, it mostly ceases to function.

    So let's run down quick what I've done so far: I've tried 3 different USB cables, I've tried 2 different laptops running on a different OS (my current laptop running 64-bit Win7 and my old laptop running 32-bit WinXP), I've tried several different versions of the driver, I've built two different harnesses (my first was kind of weak sauce, just threw it together quick with stuff I had laying around so I could test it out first, I then built a second one with better wire and soldered all my connections to rule out that as the culprit) and I've tried several different tuning programs.

    I believe I have the correct files, I got my $EE file from, I can't remember now, it wasn't on here because I hadn't signed up for an account yet, possibly from the TunerPro website, but I may try downloading a different definition file from this site just to rule that out. I've attempted to connect using TunerPro RT, TunerCATS RT and Datamaster. TunerPro RT will recognize the adapter if it's not connected to the car once I select the correct COM and will pass the test every time. But once I connect to the car and attempt to acquire data, it insta-fails every time.

    TunerCATS RT has yet to have any luck connecting to it, but I've messed with that program the least so I'm not confident I'm doing it correctly on there. Datamaster seems to work until I actually try to record data. It will pass the test, or at least it was until last night. Now I get an unknown error when I test it, but that may be a driver issue. One of the last times I plugged it back into the laptop and it was being recognized it identified it as a Microsoft serial mouse and loaded new drivers for it, so I think I need to go back and wipe out all the drivers and try installing those again after a reboot. BTW, I'm primarily working from the old XP laptop since that one is smaller and easier to setup inside the car.

    Before I developed that issue though I was able to record data and have several sessions recorded both from the engine and trans and alternating between both, but during every session it would lose communication, wait for a few seconds and then re-establish the connection, work for a few seconds and then drop out again. And while some of the data it collected appears to be perfectly accurate such as RPMs and engine temps, other data is completely whack. When reviewing the one session where I actually drove around for a bit, there were times when my reported speed (in MPH) would jump to well over 100. Since I was driving in town on 25-35 mph speed limit streets, I wasn't going anywhere close to 100 or above.

    I also noticed there's a window in Datamaster that monitors DTCs, and it was randomly lighting up like a christmas tree and mostly didn't make any sense to me. I do get a couple recurring trouble codes, one from a steering sensor and one for interior lighting I think, I'd have to pull those from the HVAC unit to see which ones they are, but I've never put much effort into tracking them down since the car functions perfectly. No SES lights or any idiot lights ever come on and the only real problem it's ever had was when it dropped an O2 sensor last year which I replaced. I haven't replaced the other side yet cause they're kind of a pain in the butt to get out being a 20+ year old car with 130k miles on it and pretty much still 100% of it's original equipment still on it, things like that are a little rusty and little stubborn to remove. But it's on the agenda now that spring is coming.

    If anyone is interested, I can upload the sessions I saved from Datamaster and see if anything in there makes any sense or could point you in the direction of where my problems are originating from. But at this point it's just driving me nuts. One other thing I just remembered, it seems that whenever I'm plugged into both the laptop and the car, the LEDs will blink some for a little bit, but shortly after they go dark, which doesn't make sense if it's receiving data from the PCM, but as soon as I unplug the USB from the laptop, they light right back up. Maybe I just got a bad adapter? I don't really know how to check for that, but if anyone has any ideas, I'm all ears.

    If I missed any important info, ask and I'll provide what I can. I also have pictures of my adapter and the cable I made if anyone wants to rule those out as my culprit. Or maybe I'm just missing something simple and obvious, I'm experienced with the mechanical side of cars, and I'm even pretty good with electronics and computers, but engine tuning is well outside my normal wheelhouse so I freely admit to being a complete noob as far as that is concerned. I just remembered that at one point I even grabbed my phone and filmed datamaster for a few seconds so if anyone wants to see that I can upload it as well, because while I'm not up to snuff on the tuning stuff yet, what I was seeing on the screen while it was recording really seemed strange.

    I think that's enough rambling for the moment, again any ideas, questions, let me know. And if anyone wants pics, video or the datalogs I saved say so and I'll copy them over to this laptop and upload them.

    Thank you for any and all help.
    After all that typing I figured I needed to say something!:-)

    FYI: I started this thread before I made my own cable:

    http://www.gearhead-efi.com/Fuel-Inj...(94-95-Camaro)

    To make a long story short I bought a couple clear top projects boxes, diodes, resistors, adapter, USB cable and ALDL male connector and assembled my own. The attached picture shows the connector and Radio Shack parts with numbers.

    The cable works great, I always read the VIN info to be sure the cable is working before doing any flashing. Had a 16188051 brick on me with my original cable but this forum has good thread that covers repairing the PCM by soldering in eeprom sockets.

    Ed

  9. #9
    Fuel Injected!
    Join Date
    Jul 2013
    Location
    Newzealand
    Posts
    483
    If anyone's after an obd2 shell and a ttl-usb board to make an aldl cable I have some spares here will post worldwide

  10. #10
    Fuel Injected!
    Join Date
    Mar 2015
    Posts
    65
    Sorry...to quick on the post. I see that another user recommended it.

    https://www.sparkfun.com/products/9718
    Last edited by tony-baroni; 12-25-2017 at 02:01 AM.

  11. #11
    Fuel Injected! -=Jeff=-'s Avatar
    Join Date
    Jun 2013
    Location
    Chicago Suburbs
    Age
    51
    Posts
    222
    I have not used that cable, but I have used their breakout PCB and that works.. So I would tend to think this one works just the same
    -=Jeff=-
    1990 Corvette ZR-1
    Black/Red Interior

  12. #12
    Electronic Ignition!
    Join Date
    Nov 2017
    Location
    Ohio
    Age
    82
    Posts
    16
    Hello fellas. Quick thanks to all of you who take the time to share your ideas, research, opinions, and results. Especially with remarkable patience. The Internet can be a very dismal place with most forums having rude and disrespectful bullies which ruin it for most. It's very refreshing to stumble upon this one and see that's there's more compassion and understanding than egos and machismo. Y'all get an 'ata boy !

    Now onto my problem. I read through countless threads on here and gathered what I need to make my OBD1 to USB connection. I bought a FTDI232 that came with a connecting cable. Before I soldered the Rx to the Tx, and since I am only interested in receiving, I figured I'd see if it worked without it. It does. Sort of. My problem is that I can see the raw data rolling through but, I do not have any sensor data. I am using WinAldl. Should my Baud be set at 4800 instead of the default 2400 ? Also, on the main screen within WinAldl there's little box, top center, to the left of the Configuration button, it is flashing red and changing numerals. I looked at many different instructions, including the readme.txt that came with the program, yet I can't find any info about that little box and what the numerals mean. I did notice in his instructional screen shots that he has 20 in his, where mine was changing from 5,4,3, and 2 randomly. Any help would be much appreciated

    1990 G20 5.7 LO5 Vin K
    ECM - 1227747 86ASDU

  13. #13
    Electronic Ignition!
    Join Date
    Nov 2017
    Location
    Ohio
    Age
    82
    Posts
    16
    WinAldl.JPG

    Here's a screenshot of the program while it was hooked to my van.

  14. #14
    Fuel Injected!
    Join Date
    Jan 2017
    Posts
    413
    Unless someone else can share their success story with WINALDL...here's the unfortunate details post #31...you can skip all the schematics and drop down to the update at the bottom of that post.
    Last edited by stew86MCSS396; 02-12-2018 at 09:01 AM.

  15. #15
    Fuel Injected!
    Join Date
    Jul 2013
    Location
    Newzealand
    Posts
    483
    I used winaldl a lot years ago on 160baud need a serial port and the techedge 160baud circuit

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
  •