<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 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The cable I am having issues with is the PC03 from Baofeng Tech and I also bought it from Amazon. It is not a driver issue as the computer sees and identifies the USB electronics just fine.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The radio goes thru a restart when the radio error is reported.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I see if the new Wouxon cable works like the one I already have when it get here. I bet it will.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ken KC9QV<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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"'> chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] <b>On Behalf Of </b>Jim Pruitt<br><b>Sent:</b> Wednesday, July 27, 2016 9:14 PM<br><b>To:</b> Discussion of CHIRP<br><b>Subject:</b> Re: [chirp_users] FTDI drivers<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:.25in'><span style='font-size:18.0pt'>Ken this was how my problem also started out. Windows did not find the right driver (or any driver) for the FTDI chip. When I went to the FTDI VCP driver site that is listed on the chirp page and ran the bus driver install from the zip file on Windows 7 then it found the cable and worked with my GT3. Granted, I am not using Windows 10 but this was the behavior I ran into. Also as I noted a day or so ago, the above did not work with the cheap FTDI chip clones but I bought the PC03 from Baofeng Tech via Amazon and that cable did work. The disconcerting part was that Windows reported that it saw the clone cable and it was working correctly but trying to use it returned the error that you also got.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:.25in'><span style='font-size:18.0pt'>Good luck.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:.25in'><span style='font-size:18.0pt'>Jim Pruitt<o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Jul 27, 2016 at 6:06 PM, Ken Rugaber (KC9QV) <<a href="mailto:krugaber@gmail.com" target="_blank">krugaber@gmail.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have a brand new Btech cable PC03 FTDI Cable Dual Pin for programming a Baofeng UV-82HP which is also new. The cable installs fine on the windows 10 computer however when using it I get the radio did not respond error message. Watching the radio display shows a reboot screen after trying for a few seconds. This tells me that there is some communication there.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I then setup a Wouxon CP210x USB to UART Bridge cable that does the same thing and it works just fine.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>These two scenarios follow exactly no matter what radio I try to use them on.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This tells me there is an issue with the Btech cable not plugging in to the radios properly. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have ordered an additional Wouxon cable. I’m done playing around.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ken</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>KC9QV</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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"'> <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> [mailto:<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a>] <b>On Behalf Of </b>John LaMartina<br><b>Sent:</b> Wednesday, July 27, 2016 7:35 AM<br><b>To:</b> 'Discussion of CHIRP'<br><b>Subject:</b> Re: [chirp_users] FTDI drivers</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'>To clarify, I’ve never gotten a bad cable from BaofengTech.<br>John</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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"'> <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> [<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">mailto:chirp_users-bounces@intrepid.danplanet.com</a>] <b>On Behalf Of </b>John LaMartina<br><b>Sent:</b> Wednesday, July 27, 2016 8:31 AM<br><b>To:</b> 'kc6iih'; 'Discussion of CHIRP'<br><b>Subject:</b> Re: [chirp_users] FTDI drivers</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'>Ahh, you are correct. I misread your email.<br><br>If you have a cloned chip, yes, like the cloned Prolific, you need the backdated driver.<br>Here is the link I have to the FTDI drivers.<br><a href="http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx" target="_blank">http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'>The clones FTDI chips were found in some of the Arduino products.<br>It looks like they’re slipping into the cable market. <br><br>John</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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"'> <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> [<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">mailto:chirp_users-bounces@intrepid.danplanet.com</a>] <b>On Behalf Of </b>kc6iih via chirp_users<br><b>Sent:</b> Wednesday, July 27, 2016 12:57 AM<br><b>To:</b> Discussion of CHIRP<br><b>Subject:</b> Re: [chirp_users] FTDI drivers</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It doesn't pay to be cheap with the cables .<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I have found thru experience that good cables like those from <a href="http://www.rtsystems" target="_blank">www.rtsystems</a> are the best .<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Sent from my Samsung Galaxy Tab®|PRO<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br><br>-------- Original message --------<br>From: Jim Pruitt <br>Date:07/26/2016 9:44 PM (GMT-08:00) <br>To: Discussion of CHIRP <br>Subject: Re: [chirp_users] FTDI drivers <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:18.0pt'>Hello John.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:18.0pt'>What you missed (or I did not make clear) was that when I switched cables to the real FTDI cable (also says Baoefeng) it worked. When I went back to the other cable (FTDI clone) the same GT3 (UR5 definitions) then it said radio was not responding. The only change was the cable itself. It works now but none of the 4 cheap cables that appear to be FTDI clones do not work. That was why I was looking for the old drivers and info as to which drivers worked with the FTDI copies.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:18.0pt'>I also have an XP machine that I have to set up as well and that will be fun.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:18.0pt'>Thank you.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:18.0pt'>Jim Pruitt</span><o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Jul 26, 2016 at 5:21 PM, John LaMartina <<a href="mailto:JohnLa@usa.net" target="_blank">JohnLa@usa.net</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'>Jim,<br>I don’t believe your issue is driver related.<br>When you stated Win7 stated the cable was recognized and everything was working, I believe that is correct.<br>The cable and driver are not the issue.<br><br>The GT3 is more than likely the issue.<br><a href="http://www.miklor.com/COM/UV_ErrorMess.php#error1" target="_blank">http://www.miklor.com/COM/UV_ErrorMess.php#error1</a><br>Radio did Not Respond is stating the radio isn’t seeing the cable.<br><br>You may need to trim the cable or the yellow rubber on the case.<br>The lip on the yellow GT3 edge may be preventing some cables to plug in completely.<br><br>I hope this assists.<br><br>John</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span style='font-family:"Calibri","sans-serif";color:black'>Miklor</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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"'> <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> [mailto:<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a>] <b>On Behalf Of </b>Jim Pruitt<br><b>Sent:</b> Tuesday, July 26, 2016 7:19 PM<br><b>To:</b> Discussion of CHIRP<br><b>Subject:</b> [chirp_users] FTDI drivers</span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:14.0pt'>I set up my pc for the latest build of Chirp this past weekend. I ran into trouble as I went out and grabbed the (latest) drivers from FTDI as suggested. When I tried to upload the current list from my GT3's it reported that they were not responding. Windows 7 said the cable was recognized and everything was working. I fought this for several minutes then switched cables. Then it worked so the first cable had to have been a clone even though it had the Baeofeng stamp on it.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:14.0pt'>I see some other posts with new users having trouble and it looks similar to what I was experiencing until I changed cables. This cable cost $21 (Amazon) compared to $3 for the other cables so I am sure others will have the non FTDI cables and not know it. I know that there has been a lot of discussion on here in the past about this. I didn't see a link on FTDI's site to get the older drivers that work with clone cables.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:14.0pt'>Does anyone have that link for the older FTDI drivers that still work with FTDI clone cables? Is there any problem with replacing the new drivers with the older ones?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:14.0pt'>Thank you.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:.25in'><span style='font-size:14.0pt'>Jim Pruitt</span><o:p></o:p></p></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>_______________________________________________<br>chirp_users mailing list<br><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">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 Jim at <a href="mailto:jpruitt67@gmail.com" target="_blank">jpruitt67@gmail.com</a><br>To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></div><p class=MsoNormal><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 Jim at <a href="mailto:jpruitt67@gmail.com">jpruitt67@gmail.com</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></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>