New cable , no workie ......

[Six_Shooter]

I've NEVER had connection when I didn't first get a "Found and Functioning" result. I've tried sometimes too. ;)

[RobertISaar]

i've had cables(both my own and aldlcables.com) fail the test, yet still function without any problems or configuration changes. it has been a while since that last happened though.

[EagleMark]

I can't see a new driver not working like an old driver? Just checked my cable on laptop and still running:
Driver FTDI
Date 4/10/2012
Version 2.8.24.0

AutoProm on pass through cable found and funtion. Com 4
ALDL cable found and funtion. Com 5

i'm up to COM30 on TP V5 without issue?

Com 30

I think I am permantly spooked by TPV4. I uninstall every USB and then restart computer and let it have what it needs. Then install all my cables and tuning devices. All under 7! Then a wireless USB mouse, printer and whatever?

[RobertISaar]

i have the computer set to assign a new COM port for every new adapter i plug in. apparently up to ~30 since the last time i installed windows, which wasn't too long ago.

[Nasty-Z]

Well,

I tried to connect to one of my '7427 trucks with no success , I also downloaded different drivers and tried those to no avail.

Today , Mark was kind enough to take some of his time (THANK YOU MARK !!!!!) to jump on my laptop and poke around a bit , we came up empty there also , after we got off of the phone I uninstalled all USB and restarted , the cable along with all of my other USB devices reinstalled but no success with the new cable.

For now I really do not know what to do , I know that Robert tests each assembly so I highly doubt there is a problem with the new cable .

I give up for now , guess i'll revisit it later and see if I can figure it out ........

Thanks for all of the suggestions , wish it would have worked out.

TOM

[RobertISaar]

i'm working on some troubleshooting steps now, i'm not sure how simple i'll be able to make everything, but it will be in-depth.

in the end, the fastest way to go about it is that the more stuff you have around to swap out to rule out what is problematic, the better. more common/supported stuff will also help immensely.



i believe you're the one that mentioning killing off your last cable? care to elaborate on that?

[Nasty-Z]

i believe you're the one that mentioning killing off your last cable? care to elaborate on that?

The cable I was using was an old setup from Andrew (AKM cables) , truthfully there is really nothing "wrong" with it other than it is old , I have repaired it a few times in the years I have had it and it needs to be re soldered where the ALDL connection is as I pulled the wires out of the junction the other night when I tripped over it ........

Figured it was just as easy to buy a new one that to keep fixing the old.

No problem Robert , I know it's not the cable , its something on my end , just need to find it .

Thanks for the support

TOM

[EagleMark]

Robert does test them all before they get shipped, this is why I thought it would be easy for me to remote desktop and set it up. But you had everything right... ?

Robert, there may be a driver issue? Tom has a 32 bit system, we downloaded new FTDI drivers and they had a date of 7-12.13 IIRC, well the new drivers are dated 8-1-13 and we could never get it installed. The drivers on my PC which is 64 bit are dated
Driver FTDI
Date 4/10/2012
Version 2.8.24.0
If I try to update them it says they are latest?

Could this be an issue?

[RobertISaar]

i've been using the FTDI drivers since..... 2008? and haven't had an issue with any of the versions they've ever released. i just downloaded the newest setup EXE from the ftdichip source while writing out a troubleshooting guide. they updated fine, the last time i did so was probably around 6 months ago. when i go into the device manager, a release date of 7/12/2013 is shown, with a version of 2.8.30.0.