Bug #9339
closedHaving trouble with getting the Radios to respond to CHIRP for programming.
0%
Description
This all started with an old cable I have not working with anything I tried. I have gotten a new cable since and updated the drivers (All was a big circus). I am at the point now where I can't get the radio to respond to CHIRP and I have looked and tried a lot of different stuff. I hoping someone can shed light on my darkness please!
{Below is my Debug log}
[2021-08-31 18:31:24,887] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-5R on port COM4
[2021-08-31 18:31:24,887] chirp.ui.clone - DEBUG: Clone thread started
[2021-08-31 18:31:24,888] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
[2021-08-31 18:31:26,016] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2021-08-31 18:31:28,032] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d 00 P...%.M.
[2021-08-31 18:31:29,154] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2021-08-31 18:31:31,167] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.
[2021-08-31 18:31:32,290] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 06 25 00 P.....%.
[2021-08-31 18:31:33,413] chirp.ui.reporting - DEBUG: Reporting exception
[2021-08-31 18:31:33,413] chirp.ui.common - ERROR: -- Exception: --
[2021-08-31 18:31:33,414] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 255, in run
File "chirp\drivers\uv5r.pyo", line 848, in sync_in
File "chirp\drivers\uv5r.pyo", line 549, in _do_download
File "chirp\drivers\uv5r.pyo", line 544, in _ident_radio
RadioError: Radio did not respond
[2021-08-31 18:31:33,414] chirp.ui.common - ERROR: ----------------
[2021-08-31 18:31:33,414] chirp.ui.clone - ERROR: Clone failed: Radio did not respond
[2021-08-31 18:31:33,414] chirp.ui.clone - DEBUG: Clone thread ended
[2021-08-31 18:31:33,415] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_UV-5R,download,True
[2021-08-31 18:31:33,417] chirp.ui.reporting - DEBUG: Reporting exception
[2021-08-31 18:31:33,417] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not respond ---
[2021-08-31 18:31:33,417] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'
[2021-08-31 18:31:33,417] chirp.ui.inputdialog - ERROR: ----------------------------
Updated by Jim Unroe over 2 years ago
- Status changed from New to Feedback
Leave the 2-pin plug out of your radio and attempt a download. The same error will result. CHIRP won't/can't work until you get your cable issues resolved.
Review the "Cables and Drivers":http://www.miklor.com/COM/UV_Drivers.php page of the Miklor.com website. Check the Windows Device Manager app to see which chip is in your programming cable to make sure you have the correct device driver installed. Also make sure that the 2-pin plug if fully inserted into the radio's socket. Some users have had to put pressuring on the plug to get contact made during the cloning process.
Jim KC9HI
Updated by Dominic Toscano over 2 years ago
Thank you for Fast feedback Jim! I have tried what you have told me with no luck still. Applying more pressure seem to do nothing. I have seen that some people have had to trim the cable, would this be true to my case? I have come to assumption that I have a, FTDI chipset? I am sharing a screenshot of what drivers and com port I am using maybe you guys can tell me whether I am wrong or not. I am feeling defeated lol, Baofeng themselves are of no help with support.
https://prntscr.com/1qxgbe2 (Driver info)
https://prnt.sc/1qxgnon (Hardware Details)
Updated by Jim Unroe over 2 years ago
Does the factory programming software work? I expect it won't, but if it does, that would indicate that the programming cable and its connection is not problem.
As far as needing to trim the cable, only you would know. You would have to visually look at the plug of the programming cable and see that it is contacting the wall of the socket well and preventing the pins to be fully inserted. This "Radio did not respond FAQ":http://www.miklor.com/COM/UV_ErrorMess.php#error1 discusses the process.
If the factory programming software doesn't work, then other potential possibilities are...
1 the programming cable is defective (they have been know to not have the wires soldered properly to the module in the USB end of the programming cable)
2 the radio socket is defective (rare but possible)
3 the radio is something other than a UV-5R (which would require a different "magic" to initiate cloning)
Jim KC9HI
Updated by Dominic Toscano over 2 years ago
I was not able to find factory software but I have had a break through! One of the admins I was talking with from Baofeng sent me a picture of his computer screen. From there I was able to figure out it was some driver no one really talks about called CH340. I mean I am sure there is someone who does talk about this but the rabbit hole I have been in for two weeks, not once did this come up. I was able to find this driver on some back page of Baofeng themselves after searching for the factory software. I now have resolved this problem. Thank you Jim for the support I highly appreciate it! Since we are getting hit heavy with Hurricane Ida lol.
Thank you!
Updated by Bernhard Hailer over 2 years ago
- Status changed from Feedback to Closed
- Target version deleted (
chirp-legacy) - Model affected changed from UV-5r to Baofeng UV-5R
Resolved by submitter.