<html>
<body>
<font size=3>Using the RT Systems version 4 cable (red) for the Yaesu
FT-60 with Chirp (Win 7) a couple of months ago, I had zero issues as
well.<br><br>
Agree about the quality of their cablesl<br><br>
Gary<br><br>
At 02:51 PM 2/11/2018, Nigel A. Gunn G8IFF/W8IFF wrote:<br><br>
<blockquote type=cite class=cite cite="">RT Systems cables work fine with
Chirp. Chirp doesn't check.<br><br>
<br>
<blockquote type=cite class=cite cite="">On 11 February 2018 at 14:17
Brandon Clark <kl7bsc@gmail.com> wrote: <br><br>
Good morning, <br><br>
Question: Has anyone had luck with changing the VID and PID on RT Systems
cables? I saw from the CHIRP documentation that it can be done with the
FTDI utility, but I'm not sure which utility to use (the FTDI site has
many available). <br>
Also, is it worth the trouble to do so, or is it better to just get
different cables? <br><br>
Background: I have three of these RT Systems cables that I've been using
for a few years now, but I've been switching my computers to run Linux
and now want to use CHIRP as my programming software. The cables are very
well-constructed, so I would like to keep them if possible. If anyone is
familiar with the reprogramming process I would appreciate the help.
<br><br>
(Feel free to email em off-list, since I'm sure this has been asked
before.) <br>
73, <br>
Brandon </font></blockquote></blockquote><font size=3><br>
<blockquote type=cite class=cite cite="">Nigel A. Gunn, 1865 El Camino
Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032<br>
Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel@ngunn.net www
<a href="http://www.ngunn.net/" eudora="autourl">http://www.ngunn.net</a>
<br>
Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club
International #385,<br>
Dayton ARA #2128, AMSAT-NA LM-1691, GCARES,
EAA382.</font></blockquote><br>
</body>
<br>
<br>
<div>--------------------------------------------------------</div>
<div>Gary D. Schwartz, N1ZCE</div>
<div>Needham, MA</div>
Please reply to: n1zce@arrl.net OR n1zce@averagebear.us</html>