Results 1 to 2 of 2

Thread: New help with new cables not working

  1. #1
    Carb and Points!
    Join Date
    Oct 2018
    Posts
    2

    Need help with ALDL new cables not working (OBD1)

    Need your help guys! First off wanted to say thanks to all for the countless efforts you guys put into making things available for crazies like me!
    I had 6pin FTDI FT232RL serial adapter wired to OBD1 cable and worked perfectly, using Scan9495, eehack and TunerPro as I have downloaded several new tunes. Well, I damaged my cable and purchased a new FTDI USB serial converter (same as before, cheapo from China off ebay). Wired it up the same way and procedure as before except this time it would connect and scan data using Scan9495 but would not connect to eehack. So I emailed back and forth with Steveo, who is cool as a fan!, and he helped with a few things it could be. I ordered another new serial converter, thinking as cheap as they are, I could have gotten a bad one. Received another one, wired it up and upon trying to connect to eehack I get the following:
    Loading Definition DEVICE=0xE4 MSG=0x0
    Loaded 1014 elements into 8 definitions.
    VERSION re-checking, network went online!
    VERSION offline status, skipping versioning
    Using monotonic reference clock.
    EEHack Version 4.70
    Current OS : Windows 7
    Built with THROTTLE_MS=2
    Opened serial port COM5 Description USB Serial Port MFR FTDI
    START SILENCE ROUTINE
    WRITE ERROR write could not be completed!
    WRITE ERROR write could not be completed!
    WRITE ERROR write could not be completed!
    START SILENCE ROUTINE
    WRITE ERROR write could not be completed!
    WRITE ERROR write could not be completed!
    WRITE ERROR write could not be completed!
    [SERIAL WRITE]*F45608AE
    WRITE ERROR write could not be completed!
    START SILENCE ROUTINE
    Listening 2000ms for broadcast heartbeat...
    Timeout waiting for heartbeat after: 2000ms
    SHUTUP DEVICE f4
    [SERIAL WRITE]*F45608AE
    WRITE ERROR write could not be completed!
    SHUTUP DEVICE f9
    [SERIAL WRITE]*F95608A9
    WRITE ERROR write could not be completed!
    DATASTREAM: Send MODE8 keepalive*F95608A9
    [SERIAL WRITE]*F45608AE
    WRITE ERROR write could not be completed!
    [SERIAL WRITE]*F45608AE
    WRITE ERROR write could not be completed!
    START SILENCE ROUTINE
    Listening 2000ms for broadcast heartbeat...
    Timeout waiting for heartbeat after: 2000ms
    SHUTUP DEVICE f4
    [SERIAL WRITE]*F45608AE
    WRITE ERROR write could not be completed!

    I have done a ton of reading and researching, which I normally find all my answers to and never have a need to post or bother anyone. But I am no computer genius and this one has driven me crazy. I have read that this error generally results from "bad usb cable, bad driver, wrong serial port selected, defective interface". So I have tried changing and using different serial converters, OBD 12 pin connectors, etc. etc. I have tried new driver versions and older versions with no luck. I downloaded Realterm and chose my com port and it communicates and seems to show that there are no driver problems. I have tried to change all types of settings back and forth, deleted and reinstalled the eehack program and many other things.

    I feel like it is something simple or stupid but I am on such a lower level of understanding as many of you are, that I cant seem to resolve my issue. I am using an older Dell laptop on Windows 7 and practically nothing has changed from the time everything worked fine until I screwed my last cable up and now none of the new cables with properly connect. I have even tried restoring the laptop to an earlier date.

    Thanks in advance and any help would be greatly appreciated!
    Last edited by nutz4sale; 12-11-2018 at 07:04 PM.

  2. #2
    Carb and Points!
    Join Date
    Oct 2018
    Posts
    2
    Also, Scan9495 is currently stating that it cannot open up ComPort 5 and when trying to disconnect from eehack, after an unsuccessful connect, it says failed to open Com Port 5 and after a while of not disconnecting, if you manually disconnect it will finally cause eehack to crash and force to close program.

Similar Threads

  1. Can someone explain proper USB cables
    By EDZIP in forum Other EFI systems and related topics
    Replies: 4
    Last Post: 01-05-2018, 01:11 AM
  2. USB cables - charging vs data cables
    By EDZIP in forum Gear Heads
    Replies: 0
    Last Post: 05-18-2017, 02:33 PM
  3. Support The Forum: Buy ALDL Cables!
    By RobertISaar in forum TunerPro Tuning Talk
    Replies: 0
    Last Post: 02-13-2013, 12:47 AM
  4. WTB - Old OBD2 tuning cables
    By cmaje72 in forum Buy - Sell - Trade - Wanted
    Replies: 9
    Last Post: 02-01-2013, 09:27 AM
  5. OBDII cables flasher and tuner
    By EagleMark in forum Gear Heads
    Replies: 3
    Last Post: 03-21-2012, 10:05 PM

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
  •