USB-TTL Serial Converter Question

[victorf]

I wanted to use a USB-TTL Serial Converter on another desktop. I downloaded the FTDI drivers and got things organized to install. When I plugged the Converter into a USB port the LEDs flashed on the board but nothing happened on the PC. I had expected the "Found New Hardware" message to come up and the Wizard to install drivers appear. Absolutely nothing! I looked in the Device Table. Nothing. I verified that the USB ports were OK by plugging in a Flash Drive. The computer recognized the Flash Drive.

Then I plugged the Converter into my other computer and it was recognized and came up as COM2 as normal.

I am not sure how to proceed now? I am at a loss.

Any Enlightenment will be appreciated!

Vic

[victorf]

I forgot to mention that both computers run WXP SP3 and all updates.

Vic

[dkinzer]

I am not sure how to proceed now?

What happens when you select "Scan for Hardware Changes" from the Action menu in the Device Manager when the USB-TTL is connected?

[victorf]

Don,

When I do this, the system only displays the COM1 standard serial port on the PCI bus. The driver is provided by Microsoft. The scan fails to detect the USB Converter.

Vic

[dkinzer]

The scan fails to detect the USB Converter.

The only thing I've found so far is a suggestion to power down the computer and restart it, first with the device attached and that doesn't work then do so without the device attached.

[victorf]

Don,

Neither case worked.

Vic

[cerickson]

You may have a USB port on that PC that has been blown out by ESD.

Try other USB ports (if it has them) and other USB devices, like a simple USB mouse.

Also try different USB cables, just in case of loose connections that work better on one machine versus another.

ESD is the #1 killer of USB and Ethernet ports.

[victorf]

cerickson,

Thanks for answering my plea!

I mentioned that in my OP that I have tested the ports by plugging in a Flash drive into them and the computer sees these devices. I have also used several cables with the converter just in case a cable was bad. None of these potential problem areas seem bad. I have successfully connected the converter to my other computer and it is instantly recognized.

My conclusion is that the converter is OK and the ports are OK and the cable is OK so I must say that I have no clue.

Vic

[dkinzer]

You might try running the FTClean Utility. It will remove all FTDI devices, COM ports and drivers from your system. The next time you add an FTDI-based device it should prompt you for the drivers.

More about this can be found on the FTDI Utilities page.

[deadmm]

You might also find a google for USBDeview.exe useful for checking what is/has been installed on your machine.

Mal

[victorf]

Well, I ran the FTClean utility and that seemed to do the trick. I was able to install the converter drivers and the system recognizes the converter. I placed it on to COM2 from the installed COM5 and I guess things are ready to go.

I want to thank everyone for their suggestions. I would never have been able to get up and running without your help.

BTW: USBDeview.exe name is USBview.exe and it works well too. Thanks deadmm

Vic

[stevech]

I have these COM port struggles in XP all the time. Most often, I change the installed USB thing to use a COM lower than 10 due to software that has such limits.

A big issue is that my Verizon USB modem sets up COM ports. The Smith Micro software for that modem is so very badly designed that it can't cope with such changes.

Anyone else dealt with this?

PS: Edgeport's USB/serial drivers are really trouible free.