<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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.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">I had the same problem, and the same solution (squeezing hard on the plug). Then I discovered that the plug on my programming cable was a little too wide to fit easily into the recess around the socket on the radio. So I carved a little
bevel onto the edge of the plastic body of the connector and the cable worked much better after that. Best of luck. 73.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chris Doutre KC9AD<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com>
<b>On Behalf Of </b>Peter<br>
<b>Sent:</b> Friday, November 09, 2018 1:01 PM<br>
<b>To:</b> Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
<b>Subject:</b> Re: [chirp_users] Communication Issues with new UV-5R EX<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I bought some BTech MURS-V1 radios for my unlicensed family members and two of them have the same issue. I had to apply continuous side pressure on the programming cable connector where it enters the radio
to get a successful read from CHIRP. The second replacement radio from BTech still seems a bit iffy in this regards. Need to wiggle it side-to-side after insertion to get a clean connection. So definitely a hardware issue with the Kenwood connector. These
radios are Baofeng UV-82 clones with locked down firmware.<br>
<br>
(Peter)<br>
<br>
<o:p></o:p></p>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b>From: </b><a href="mailto:r-chirp@rich0.org">Rich Freeman</a><br>
<b>Sent: </b>11/9/2018 12:42 PM<br>
<b>To: </b><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<b>Subject: </b>[chirp_users] Communication Issues with new UV-5R EX<o:p></o:p></p>
</div>
<p class="MsoNormal">I just purchased a UV-5R EX off of Amazon and am having trouble<br>
getting it to communicate with CHIRP. The same hardware/software<br>
config works just fine with my BF-F8HP. I get the problem whether I<br>
select Raddiodity/UV-5R EX or Baofeng/UV-5R. This is on linux, and I<br>
have the problem with the latest Mercurial commit as well as 20180906<br>
and 20181018. I've also reproduced the problem on Windows, which also<br>
communicates just fine with the BF-F8HP just fine. I just unplug the<br>
one radio from the mic connection and plug in the other and it<br>
starts/stops working, so I'm pretty certain it isn't a<br>
driver/permissions/etc issue. This is with an FTDI-based USB cable.<br>
<br>
The radio reports its firmware version (when holding down 3) as<br>
BFS001. I couldn't tell you whether this is correct as it isn't<br>
communicating with CHIRP so I'm not getting more than that.<br>
<br>
I also tried fiddling with the baud settings on the serial device in<br>
linux and it didn't make any difference.<br>
<br>
Has anybody run into issues with newer radios? Is it possible there<br>
was a firmware change not handled by the software?<br>
<br>
I'm happy to debug or test patches/etc if helpful. The radio is just<br>
in factory config so I don't really care about losing any settings as<br>
long as it isn't bricked.<br>
<br>
--<br>
Rich<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">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to (Peter) at <a href="mailto:ptlambert@sbcglobal.net">ptlambert@sbcglobal.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>
</div>
</body>
</html>