what do you mean?
Printable View
what do you mean?
different vehicles/engines need different ADXs. it's not a one-size-fits-all like OBD2.
91 chevy pickup ecm 1227747
you'll need the $42 ADX then, i'm sure Mark about has the link memorized by now.
sorry im very new to this. how do i get the adx file?
in post #3, there are a few files there than can be used.
http://www.gearhead-efi.com/Fuel-Inj...2&d=1375131735
i THINK that is the one you'll need.
i got it thank you for your help
2.8.14.0 are the drivers XP installed when I plugged the cable in , worked fine on that machine.
I used phonedawgz link in his post to the 2.8.14.0 drivers , downloaded them to my Dell E5520 machine and viola , the cable was found and functions as intended on the machine.
Thank you everyone for all of the responses to my problem , thanks to phonedawgz for the driver link and a big thank you again to Mark for taking his time to try to help yesterday. Time to put this thing to work finally :rockon:
TOM
TOM
So you have not read the TunerPro RT tutorial marked Must Read? :innocent2:
http://www.gearhead-efi.com/Fuel-Inj...-a-must-read!-)
That's great news Tom. And thanks to you for tracking down and testing what phondawgz has reported!
I've changed the TunerPro RT cable installatation tutorial to include these FTDI driver version numbers and linked back to phonedawgz post with the info. :thumbsup:
i read the tutorial but i didnt know where to get the files from till i googled it
did some more investigating tonight, i could not get the most current drivers to work the 1213-C batch no matter how much i messed with them. i did get them working with the .28 revision though, after about an hour of cleaning, reinstalling, restarting, etc.
from the looks of it, one of the cables i built back in 2009(my personal cable, complete in it's prototyping case and all) also had issues with the current drivers.
and for some reason, i couldn't get the .14 revision to work reliably... one time i restarted, connects just fine, unplug, wait a few seconds, plug back in, no connection. restart the computer, sometimes fixed it.
it's weird, but i guess it is just something that will need to be tested on every chip until official word gets out on a fix.
Sounds like chips have issues and then FTDI has made driver updates while no consistency in chips?
Man I thought we were done with driver issues, seems we had a few years there...
Try removing all the drivers in Control Panel - Add/Remove Programs - Then go to the bottom - Windows Driver Package and remove all but the .14 drivers.
I include the .14 drivers with my cables. I have found that only the people who have had other than .14 drivers installed at one time are the only ones that have problems. First time scanner people never do.
Windows uninstaller sometimes doesn't always work, but that is where I would start. Uninstalling all the other than .14 drivers gives me 100% working on the 1213-C chips.
I will be talking to FTDI again next week about this.