<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>No, but their software only works with  their cable. RT cables work OK with Chirp,</p><blockquote type="cite">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" rel="noopener" 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" rel="noopener" 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></blockquote></body></html>