1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
-= =-
its an hp windows 7 64 bit operating system with a few printer installed on it
Since the driver update or change makes registry changes I'm wondering if that is an issue? Registry errors?
For both you guys go get Advanced System Care 6.x, it's free. The registered version does more and is like $20 for three PCs. Install and run, when I run this on other peoples PCs I get thousands of registry errors as many as 6,000 on one, 3,000 is normal fixed along with a lot of other things. Great improvements of PC speed etc... it will also make sure your windows updates are done and sometimes needs a restart.
If it does not work you will still like your PC much more... we started using this years ago at "Rehab" which is a bunch of old guys with nothing better to do on Tuesday nights then rehab old corporate computers donated, then we give them away to qualified needy people...
lilhumper, I have 2 HP WIndows 7 64 bit machines and no issues. So this may not be a manufacturer specific. Since the USB ports are working? I'm still stuck on driver issue, registry issue because of driver?
Robert, could PC possibly need a FTCLean?
1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
-= =-
FTDI is still having troubles with their drivers. I have two batches of FT232RL boards here. One of the batches works 100% with the 2.08.30 (8.1.2013 release). The other batch works only 10% on the new .30 driver, or .28 or .24. 2.08.14 solves the problem however and works on all of them.
Below is the CDM 2.08.14 exe program. Down load it, unzip it and then run Setup_CDM2.08.14.exe. That will load the .14 drivers onto your PC. Then in Device Manager "update" BOTH the USB Serial Port (Under Ports (COM & LPT) and under Universal Serial Bus controllers update the entry USB Serial Converter.
In Update select "Install from a list or specific location" then choose "Don't search. I will choose the driver to install." Next you should see a screen with the drivers in your computer's library along with the 2.08.14. Select that for BOTH entries in Device manager.
You might have to reboot after this procedure, however I found that I did not have to.
Here is the installer for CDM 2.08.14 in my dropbox - https://dl.dropboxusercontent.com/u/...%202.08.14.zip
Unplugging and replugging the cable shouldn't give you any problems once the .14 is assigned to your cable. However if you use a different FT232RL chip (cable), Windows will then install the latest version of the driver in your computer's library. You either need to delete the other driver versions from your computer or manually update the cable's driver to the .14 when using a board your computer hasn't seen.
I have sent samples Friday to FTDI of chips that work and chips fail.
-------
If you want to see if the drivers are the issue - Download Real Term - http://sourceforge.net/project/showf...group_id=67297 and install it on your PC. Have your cable plugged into your PC, but not your vehicle. Start Real Term and go to the PORT tab, then select your port and then hit CHANGE! Then click in the black box and start typing. If the characters you type are displayed, your cable is working correctly. If you get a 'nul' for any letter you press, then you have the driver problem.
-----
**To remove the offending .24 .28 .30 driver install programs from your PC, go to "Add or Remove Programs" and under "Change or Remove Programs" scroll all the way down to "Windows Driver Package" and find the FTDI's with the non-working versions. There may be more than one for each version. Click remove, and if the magic of Windows is working, that will remove them from your computer's library. Leaving only the .14 will insure you get the version that currently works.
** Only needed if you de-install and re-install your cable
Last edited by phonedawgz; 08-11-2013 at 07:51 PM.
its a dv7 ive tried changing drivers tried the registry still nothing im going to grab a different pc and try it
Well I have 2 DV7 laptops and no issues. So it's not brand specific.
Looks like phondawgz has this figured out. I don't have one of his cables but I do have at least one of everything else and been using FTDI 2.08.24 driver on all PCs since it has came out. Same one that is listed in my cable install write up.
Even though there are newer one's out and even auto installed by Windows, I can not update mine, if I try it says I have the latest?
TOM, what drivers were installed on your XP machine when you did the cable and it worked?
1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
-= =-
1994 3500 Dually , 502 (509) , 264HR , Edelbrock MPFI , PFI '7427
1992 S-10 434 SBC/Tremec - '7427
1986 Monte Carlo SS
1984 S-10 , SAS, 496/700R4/205 , D44/14BFF -'7427
1980 Z-28 496/700R4
1979 Corvette 496/700R4
1977 Olds 98 Regency 403/700R4
The date code on the chips that have had the highest failure rate with the .24, .28 and .30 drivers is 1213-C. That is 2012 - 13th week.
I have the problem however on other date codes, but rarely.
The guy at FTDI seemed truly excited to get samples of chips from the same lot that both worked and failed. Up to that point I had assumed that FTDI knew about the problems but weren't super interested in fixing them.
.30 is the driver on FTDI's website now. I do have .14, .24 and .28 if you want to play with any of them.
On my install disk I only have .14 so I don'[t get many complaints. I figured it out finally when I put it together that all the failures were coming from people who had more, not less experience with ALDL cables. They were the people who had already had the other drivers on their machines. It then clicked that it wasn't just the cable's driver, but the Universal Serial Bus Controller driver that needed changing. Testing on my computer showed that the Universal Serial Bus Controller driver was the cause of this latest problem.
Weird that chips from the same date would work on the old drivers, but some would work and some would fail on the new ones. Multiple tests showed that certain chips would be the ones that always failed and others were perhaps resilient enough and just always worked with the new drivers.
Last edited by phonedawgz; 08-12-2013 at 12:40 AM.
i can get the cable to function but as soon as it is plugged into the truck it is not functioning anymore
That is normal. The cable test procedure is meant to be preformed with the cable disconnected from the vehicle.
Try your .adx and see if you can connect now.
do i make my own .adx?
Bookmarks