![]() While your system likely already has the FTDI USB Serial driver, the problem is that driver won't be used, because the VID/PID on your cable has been changed to the one set by your cable's vendor.įTDI's driver has two components. USB devices have a Vendor ID (VID) and a Product ID (PID) that identifies the device so the operating system can figure out what driver to load, "plug-and-play" style. You can either get your computer to recognize the OEM cable as a generic serial port by tweaking the driver setup, or you can change the cable to use the default FTDI codes, so the standard FTDI driver present in most operating systems will recognize the cable and create a standard serial port.Ī little more background maybe helpful in understanding the information here: There use such a cable with CHIRP there are two options. Using a vendor specific code on the USB chip allows software that is specifically written for that cable, usually under Microsoft Windows, to identify the cable and eliminates the guessing about which port the radio is connected to. There are also some Icom cables that are sold this way. We have tested 3 RT Systems cable types and confirmed that they appear as normal COM ports on Windows 10 if the installation instructions are followed. An early version of one RT Systems cable had this issue, though none of their present cables have this issue. ![]() By default CHIRP (and some other software) will not be able to use these cables because CHIRP needs a serial port. Some cable vendors use the FTDI serial chip in their USB radio cables, but have changed the chip's ID codes so that the cable will not be recognized as a generic serial communications port, e.g. Note: this page is currently a work in progress ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |