Posted: 6/1/2015 11:27:19 PM EDT
|
After having successfully used VX7 commander, FTB270, and FTB7800 in the past (about 4 or 5 years ago), I now find myself unable to get the software to read or write to any of my radios.
I bought a legit USB data cable from RT systems, and still cannot get it to recognize or write to the radio. I'm pretty positive there's something wrong with my COM port setup, but after trying a number of combinations (and reassigning COMM port assignment to my USB cable) I've given up. I'm wondering if it just simply doesn't play well with Windows 7. Any advice? Thank you. |
|
I don't have any experience with this; however, I remembered reading about RT systems cables not being compatible with other software. This site might be helpful: http://chirp.danplanet.com/projects/chirp/wiki/CableGuide_FTDI_OEM_Cables It is specifically for CHIRP, but it might be useful for commander software, too, since it is just to get your computer to recognize the chip in the cable.
A brief excerpt from the above page: "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. By default CHIRP (and some other software) will not be able to use these cables because CHIRP needs a serial port. Most notably RT Systems sells such cables. There are also some Icom cables that are sold this way. 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 use such a cable with CHIRP there are two options. 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." |