3. Find someone who knows how to install a Windows driver manually.
Vista will silently install the wrong driver which will not work.(so if you see the text" let windows decide" or "let windows find your driver..." don't go there. You can guide Windows to install the proper driver from a package you downloaded prior to driver install if you know how to install Windows drivers "manually."
The proper driver is found here: http://www.ftdichip.com/Drivers/D2XX.htm
The current driver that is Windows certified, aka "WHQL" is ver. 2.08.30
(What is WHQL? - a manufacturer of chips, in our case FTDI in Taiwan, has developed a USB Serial Port Emulator and makes the firmware code to make it all work. (a driver..). They pay Microsoft to test this code and hardware and the end result it that it is suitable for the many versions of Windows, has been tested, and is digitally signed by the manufacturer to ensure the source of the code is as advertised. Fees are paid, Microsurf engineers nod their heads, and the manufacturer gets a WHQL certificate. All is well in Windows World.
Hint: Vista 64bit INSISTS on only certified drivers, not an issue with our present case.
You will note that there are three possibilities: 32bit, 64bit, or looking to the right, "available as a setup executable."
Now, I'm guessing you have the 32 bit version of Vista, but how can you know for certain?
Do the following:
On the lower left click on the windows start button, on the panel find the "computer" entry and RIGHT click it, scroll down this screen until you see "properties" and left click it, the panel that opens will have you computer information, including if your windows has installed as "32bit" or "64bit".
OK, done with that, close it.
So if you have the 32bit windows, download the 32 bit driver package using your browser and the URL posted above.
(but keep reading)
Ok, now you have the driver package, somewhere on the ADV site someone shows how to install it manually with pictures. Please refer to that. Manual is the "Let me decide" prompt on drv. install.....then point it to your package folder location.
You may want to know what I would do, I use the "available as a setup" download. Why?
Well, if you know what's going on you only want either the 32bit or 64 bit package for download, because the setup.exe version has the whole enchilada 32 and 64 bit packages all in one so it's twice the size. But it has logic to go and ask Windows "How big is your....computer word size" and installs the proper driver for you.
Hint: For those that know how, block your internet so Windows can't find a "suitable driver" which will be wrong incase you make the wrong move....but not necessary, it's the computer equivalent to stuffing rags down your throttle bodies for safety...
For those running XP you must have the .NET framework updated to 2.0 or greater for tune-ecu to work.
To make this discussion complete, we should talk about
Window device manager screen
Setting the com port baud rate
setting the handshake (what are the differences between none, harware handshake, XON/XOFF software protocol handshake)
setting the parity, the rs-232 data bit size
setting the stop bits
Perhaps another time.
Generally speaking, serial ports usually work with:
8 bits, No parity, 1 stop bit, 9600 baud rate, No hand shaking
(this will be the default on installation, but we set/check all of this when needed in the devices screen in windows.)
Hope this adds to the discussion, I'm going for a ride.
Originally Posted by smitty141
Hooterville is just south a Petticoat Junction. Or 50 miles south of St. Louis..
Thank for the info.. . Ordering a cable today, will try to load the software tonight.
Any IT phone help out there???