<div dir="ltr">I used one with Chirp on Mac OS and Linux, no problems at all. VERY well built cable. the custom vid/pid are basically the license key to the RT Systems software ( they used to use a really awful copy protection scheme).<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 11, 2018 at 2:08 PM, Gary D. Schwartz <span dir="ltr"><<a href="mailto:gary-yg@pobox.com" target="_blank">gary-yg@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<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<span class=""><br><br>
At 02:51 PM 2/11/2018, Nigel A. Gunn G8IFF/W8IFF wrote:<br><br>
<blockquote type="cite" class="m_5322518045955887312cite">RT Systems cables work fine with
Chirp. Chirp doesn't check.<br><br>
<br>
<blockquote type="cite" class="m_5322518045955887312cite">On 11 February 2018 at 14:17
Brandon Clark <<a href="mailto:kl7bsc@gmail.com" target="_blank">kl7bsc@gmail.com</a>> 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 </blockquote></blockquote></span></font><font size="3"><br><span class="">
<blockquote type="cite" class="m_5322518045955887312cite">Nigel A. Gunn, 1865 El Camino
Drive, Xenia, OH 45385-1115, USA. tel <a href="tel:(937)%20825-5032" value="+19378255032" target="_blank">+1 937 825 5032</a><br>
Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail <a href="mailto:nigel@ngunn.net" target="_blank">nigel@ngunn.net</a> www
<a href="http://www.ngunn.net/" target="_blank">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.</blockquote></span></font><br>
</div>
<br>
<br>
<div>------------------------------<wbr>--------------------------</div>
<div>Gary D. Schwartz, N1ZCE</div>
<div>Needham, MA</div>
Please reply to: <a href="mailto:n1zce@arrl.net" target="_blank">n1zce@arrl.net</a> OR <a href="mailto:n1zce@averagebear.us" target="_blank">n1zce@averagebear.us</a>
<br>______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to Tom KG4CYX at <a href="mailto:blueneon@gmail.com">blueneon@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Tom Morris, KG4CYX</div><div>Chief Engineer, Results Radio of Redding<br></div><div><span title="Call with Google Voice">786-228-7087</span></div></div></div></div></div></div></div></div></div>
</div>