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.
73, Bill, KK4ZIU ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Peter ptlambert@sbcglobal.net Sent: Friday, November 9, 2018 4:00 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Communication Issues with new UV-5R EX
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.
(Peter)
________________________________ From: Rich Freemanmailto:r-chirp@rich0.org Sent: 11/9/2018 12:42 PM To: chirp_users@intrepid.danplanet.commailto:chirp_users@intrepid.danplanet.com Subject: [chirp_users] Communication Issues with new UV-5R EX
I just purchased a UV-5R EX off of Amazon and am having trouble getting it to communicate with CHIRP. The same hardware/software config works just fine with my BF-F8HP. I get the problem whether I select Raddiodity/UV-5R EX or Baofeng/UV-5R. This is on linux, and I have the problem with the latest Mercurial commit as well as 20180906 and 20181018. I've also reproduced the problem on Windows, which also communicates just fine with the BF-F8HP just fine. I just unplug the one radio from the mic connection and plug in the other and it starts/stops working, so I'm pretty certain it isn't a driver/permissions/etc issue. This is with an FTDI-based USB cable.
The radio reports its firmware version (when holding down 3) as BFS001. I couldn't tell you whether this is correct as it isn't communicating with CHIRP so I'm not getting more than that.
I also tried fiddling with the baud settings on the serial device in linux and it didn't make any difference.
Has anybody run into issues with newer radios? Is it possible there was a firmware change not handled by the software?
I'm happy to debug or test patches/etc if helpful. The radio is just in factory config so I don't really care about losing any settings as long as it isn't bricked.
-- Rich _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to (Peter) at ptlambert@sbcglobal.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com