<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:black;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:black'>Good to know, Nigel. Thank you.<br><br>John K3NXU<br><a href="http://www.Miklor.com">www.Miklor.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Nigel A. Gunn G8IFF/W8IFF [mailto:nigel@ngunn.net] <br><b>Sent:</b> Friday, July 26, 2019 12:59 PM<br><b>To:</b> Discussion of CHIRP; John La<br><b>Subject:</b> Re: [chirp_users] Yaesu 3200D and RT Systems cable problem<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>No, but their software only works with their cable. RT cables work OK with Chirp,<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>On 26 July 2019 at 12:17 John La <<a href="mailto:Johnla@usa.net">Johnla@usa.net</a>> wrote:<br><br><br>Is it possible the RT cable is proprietary to their software only?<br><br>John K3NXU<br>www.Miklor.com<br><br>-----Original Message-----<br>From: <a href="mailto:chirp_users-bounces@intrepid.danplanet.com">chirp_users-bounces@intrepid.danplanet.com</a> [mailto:<a href="mailto:chirp_users-bounces@intrepid.danplanet.com">chirp_users-bounces@intrepid.danplanet.com</a>] On Behalf Of Jan Ditzian<br>Sent: Thursday, July 25, 2019 8:27 PM<br>To: <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>Subject: [chirp_users] Yaesu 3200D and RT Systems cable problem<br><br>I have an RT Systems Yaesu programming cable for a Yaesu FT-1900 <br>two-meter mobile radio that fits my new FTM-3200D radio. I installed <br>the latest Chirp, as of today, and it knows about the FT-3200D. I <br>plugged the cable into the computer USB and the radio microphone jack. <br>By trial and error, I discovered that the FTM-3200D goes into CLONE mode <br>by holding in SETUP and then turning it on. Also, by trial and error, I <br>found that the FTM-3200D went into TRANSMIT mode to the computer by <br>starting the Chirp Download from Radio, and then pressing REV on the <br>FT-3200, whereupon the radio went to TX mode and began to count up, and <br>Chirp also showed that it was downloading data. The process finished, <br>the radio went back to CLONE, but Chirp returned a checksum error. <br>Chirp does not display any radio data after the failure. To sum up, the <br>radio is happy that it spoke to Chirp, but Chirp is not happy with what <br>it heard, probably at the end of the exchange.<br><br>Does anyone know how I can get past this error message?<br><br>Thank you and 73,<br><br>Jan, KX2A<br><br>_______________________________________________<br>chirp_users mailing list<br><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>This message was sent to John LaMartina at <a href="mailto:johnla@usa.net">johnla@usa.net</a><br>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br><br>_______________________________________________<br>chirp_users mailing list<br><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>This message was sent to Nigel Gunn, W8IFF at <a href="mailto:nigel@ngunn.net">nigel@ngunn.net</a><br>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><o:p></o:p></p></blockquote></div></body></html>