<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
With the same issue on my radios, I resorted in using an emery board to gently work the plastic two pin connector to a better fit and found that it didn't affect the radios that it fit properly to begin with. Be extra careful to avoid the metal pins.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
73,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Bill, KK4ZIU<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Peter <ptlambert@sbcglobal.net><br>
<b>Sent:</b> Friday, November 9, 2018 4:00 PM<br>
<b>To:</b> Discussion of CHIRP<br>
<b>Subject:</b> Re: [chirp_users] Communication Issues with new UV-5R EX</font>
<div> </div>
</div>
<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">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>
<br>
</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">From:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:r-chirp@rich0.org">Rich Freeman</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Sent:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">ý11/ý9/ý2018 12:42 PM</span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">To:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Subject:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">[chirp_users] Communication Issues with new UV-5R EX</span><br>
<br>
</div>
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>
chirp_users@intrepid.danplanet.com<br>
http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>
This message was sent to (Peter) at ptlambert@sbcglobal.net<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
</div>
</body>
</html>