FTDI USB to Serial converter chip

[dhouston]

With CreateFile use "\\.\" before "COMnn" e.g. "\\.\COM99"

To modify MSCOMM32.OCX, Google using "MSCOMM32.OCX 3D 10 00".

You might also ask FTDI Support for suggestions.

[JElliott]

I also have had similiar issues with the FTDI devices. I definately know if you change the serial number of the device it will open a new comport. I don't have a solution for this but after much web searching I did find a solution for reclaiming these ports. I have enclosed PDF of the web page that provides the directions. Helps ease the pain

Regards,

Jeff E.

[tenaja]

If you are up to 82, and you aren't using it for an open free-for-all com port, then you really should get your own PID's from FTDI. You should also be using the d2xx drivers, and eliminate the vcp's all together.

Doing this will place your device in the USB controllers list of Device Mgr, and not in the Port list. Not only that, by getting your free PID number, it will make your product look a little more custom, and will remove all the hassles of selecting the proper COM port in the program.

All of this is covered in the data sheets. It is worth the effort to learn, because it makes your product more professional looking and much more user friendly--especially if someone randomly happens to have an FTDI serial converter cable plugged into their computer.

[tenaja]

By the way, there are d2xx communications code samples for using the DLL's on the ftdi web site, too. They show how to use the chip without a COMx assigned at all.