[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
On Fri, Nov 9, 2018 at 3:43 PM Rich Freeman r-chirp@rich0.org wrote:
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
Hi Rich,
I would be helpful if you would share the exact error message or attach a debug.log file. Without that information I am going to guess that the connection between 2-pin plug of the programming cable is not fully connected to the socket of the radio. This is a common problem with these radios. No programming software can clone a radio without a full and working connection between the computer and radio. Sometimes the workaround can be as simple as pressing on the plug to make the connection to the socket during the cloning process.
Jim KC9HI
On Fri, Nov 9, 2018 at 3:52 PM Jim Unroe rock.unroe@gmail.com wrote:
I would be helpful if you would share the exact error message or attach a debug.log file.
Here is the --verbose console output - let me know if you wanted something else:
INFO: Skipping existing stock config INFO: Server reports version 20181018 is available INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
ERROR: uv5r._ident_radio: Radio did not respond INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d 00 P...%.M.
ERROR: uv5r._ident_radio: Radio did not respond INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 256, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uv5r.py", line 807, in sync_in self._mmap = _do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uv5r.py", line 542, in _do_download data = _ident_radio(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uv5r.py", line 537, in _ident_radio raise error RadioError: Radio did not respond
ERROR: ---------------- ERROR: Clone failed: Radio did not respond ERROR: --- Exception Dialog: Radio did not respond --- ERROR: None
ERROR: ----------------------------
Sometimes the workaround can be as simple as pressing on the plug to make the connection to the socket during the cloning process.
Yeah, I did try that, but I can't be certain it is making a connection. It looks like the base of the plug extends all the way down, and from that point it seems to have the same connector depth as on a speaker mic that seems to work fine. So, I'm guessing it is ok, but the cable is right up against the side of the device so I can't be certain. No amount of wiggling seems to make a difference.
If I use the UV-5R EX driver with my BF8HP I get this output:
INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
INFO: Valid response, got this: INFO: Radio Version is 'N5R340BF8HP-1 ' ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 256, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uv5r.py", line 807, in sync_in self._mmap = _do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uv5r.py", line 565, in _do_download raise errors.RadioError("Incorrect 'Model' selected.") RadioError: Incorrect 'Model' selected.
ERROR: ---------------- ERROR: Clone failed: Incorrect 'Model' selected. ERROR: --- Exception Dialog: Incorrect 'Model' selected. --- ERROR: None
ERROR: ----------------------------
(This seems reasonable to me, since I am in fact selecting the wrong radio.)
On Fri, Nov 9, 2018 at 4:13 PM Rich Freeman r-chirp@rich0.org wrote:
On Fri, Nov 9, 2018 at 3:52 PM Jim Unroe rock.unroe@gmail.com wrote:
I would be helpful if you would share the exact error message or attach a debug.log file.
Here is the --verbose console output - let me know if you wanted something else:
INFO: Skipping existing stock config INFO: Server reports version 20181018 is available INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
ERROR: uv5r._ident_radio: Radio did not respond INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d 00 P...%.M.
ERROR: uv5r._ident_radio: Radio did not respond INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.
CHIRP is not getting any data back from the 2 clone requests. Either there is no connection between the plug and socket or the socket itself has an issue.
Unless you can get the factory software to work, this is not an issue that can be solved by CHIRP.
Jim KC9HI
On Fri, Nov 9, 2018 at 5:17 PM Jim Unroe rock.unroe@gmail.com wrote:
CHIRP is not getting any data back from the 2 clone requests. Either there is no connection between the plug and socket or the socket itself has an issue.
I went ahead and filed some plastic off of the plug and between that and a firm grip, it was able to clone to/from the radio. Thanks for the help.
This was an official Baofeng cable, but it looks like they have a newer version that I assume has more clearance...
-- Rich
My cable is an "official" BaoFeng Tech PC03 FTDI USB Programming Cable and I also had to do this to make it work with the rest of my radios. It's a fairly common problem, good to hear you got it sorted.
(This did not however solve the problem I was seeing on a few BTech MURS-V1 units, they have plenty of clearance between the cable connector and radio case. Just a batch of marginal Kenwood socket assemblies on those units, it seems.)
On 11/9/2018 3:58 PM, Rich Freeman wrote:
On Fri, Nov 9, 2018 at 5:17 PM Jim Unroe rock.unroe@gmail.com wrote:
CHIRP is not getting any data back from the 2 clone requests. Either there is no connection between the plug and socket or the socket itself has an issue.
I went ahead and filed some plastic off of the plug and between that and a firm grip, it was able to clone to/from the radio. Thanks for the help.
This was an official Baofeng cable, but it looks like they have a newer version that I assume has more clearance...
-- 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
Hello Rich,
This is Bob Burkett, K5DCZ
I have limited knowledge on this subject ... but, do have some experience programming the UV-5R.
The biggest problem I have had is having the right interface cable. Wrong cable ... no workee. A lot of the cheap knockoff cables just don’t work. Most of the cables are radio specific ... even with RT Systems software as well as CHIRP.
CHIRP works fine for me with Windows 10.
Hope this helps
Bob Burkett K5DCZ 972-839-9652 MathIsFun.Bob@hmail.com
Canon City RGARC
On Fri, Nov 9, 2018 at 1:54 PM Jim Unroe rock.unroe@gmail.com wrote:
On Fri, Nov 9, 2018 at 3:43 PM Rich Freeman r-chirp@rich0.org wrote:
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
Hi Rich,
I would be helpful if you would share the exact error message or attach a debug.log file. Without that information I am going to guess that the connection between 2-pin plug of the programming cable is not fully connected to the socket of the radio. This is a common problem with these radios. No programming software can clone a radio without a full and working connection between the computer and radio. Sometimes the workaround can be as simple as pressing on the plug to make the connection to the socket during the cloning process.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bob at mathisfun.bob@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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)
-----Original Message----- From: "Rich Freeman" r-chirp@rich0.org Sent: 11/9/2018 12:42 PM To: "chirp_users@intrepid.danplanet.com" 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
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.
Chris Doutre KC9AD
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of Peter Sent: Friday, November 09, 2018 1:01 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com 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.commailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to (Peter) at ptlambert@sbcglobal.netmailto:ptlambert@sbcglobal.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.commailto:chirp_users-unsubscribe@intrepid.danplanet.com
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
participants (6)
-
Bob Burkett -
Jim Unroe -
Not D'Arcy Cain -
Peter -
Rich Freeman -
William Thompson