Bug #2845
closedRadio did not respond (Baofeng UV-5R5)
0%
Description
User selected Baofeng UV-5R on port /dev/ttyUSB0
Clone thread started
Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
Ident:
000: fe 30 fe 04 00 c1 fe 00 .0......
Radio refused clone
Sending Magic: 000: 50 bb ff 01 25 98 4d 00 P...%.M.
Radio did not respond
-- Exception: --
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/chirpui/clone.py", line 227, in run
self.__radio.sync_in()
File "/usr/local/lib/python2.7/dist-packages/chirp/uv5r.py", line 638, in sync_in
self._mmap = _do_download(self)
File "/usr/local/lib/python2.7/dist-packages/chirp/uv5r.py", line 460, in _do_download
data = _ident_radio(radio)
File "/usr/local/lib/python2.7/dist-packages/chirp/uv5r.py", line 456, in _ident_radio
raise error
RadioError: Radio did not respond
Files
Updated by Jim Unroe over 9 years ago
- Status changed from New to Feedback
From the Supported Radio Models list on the CHIRP Wiki/Home page...
- UV-5R "and variants":http://chirp.danplanet.com/projects/chirp/wiki/Baofeng_UV5R_Variants (in daily builds)
Support for most new UV-5R variants and their firmware versions released in the last year are included in the most recent CHIRP daily builds. The CHIRP v0.4.1 stable build is 17 months old and does not have this support.
Instructions for adding the snapshot repository are on the CHIRP "download":http://chirp.danplanet.com/projects/chirp/wiki/Download page. There is additional info on the CHIRP "Running_Under_Linux":http://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux page.
Jim KC9HI
Updated by Jim Unroe over 9 years ago
Not the same error. Before the radio was not responding at all. Not is it responding incorrectly.
Try making sure the cable is fully plugged into the radio's socket. Also try setting the radios volume level higher. The volume level should not make any difference with serial communications but I have has someone verify that the volume level setting does indeed affect the serial communications on some models.
Jim KC9HI
Updated by Caleb Bennett over 9 years ago
I had a similar problem try running "sudo chirpw" this allowed me to access my radio when I got "RadioError: Radio did not respond" error.
Updated by Galen Thurber about 9 years ago
I had the same error on several UV5R variants on two computers,
it was a bug that had snuck in and was fixed in 20151009
Updated by Q RS about 9 years ago
Galen Thurber wrote:
I had the same error on several UV5R variants on two computers,
it was a bug that had snuck in and was fixed in 20151009
I think this bug is still there :(
Log from terminal Ubuntu:
$ chirpw
(process:8817): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
ERROR: Invalid answer for block 0x1ec0:
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/chirp/ui/clone.py", line 238, in run
self.__radio.sync_in()
File "/usr/lib/pymodules/python2.7/chirp/drivers/uv5r.py", line 701, in sync_in
self._mmap = _do_download(self)
File "/usr/lib/pymodules/python2.7/chirp/drivers/uv5r.py", line 506, in _do_download
radio_version = _get_radio_firmware_version(radio)
File "/usr/lib/pymodules/python2.7/chirp/drivers/uv5r.py", line 475, in _get_radio_firmware_version
block1 = _read_block(radio, 0x1EC0, 0x40, True)
File "/usr/lib/pymodules/python2.7/chirp/drivers/uv5r.py", line 455, in _read_block
raise errors.RadioError("Unknown response from radio")
RadioError: Unknown response from radio
ERROR: ----------------
ERROR: Clone failed: Unknown response from radio
ERROR: --- Exception Dialog: Unknown response from radio ---
ERROR: None
ERROR: ----------------------------
Updated by Bernhard Hailer over 4 years ago
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from (All models) to Baofeng UV-5R5
Have you tried with a recent version since you submitted this?
If you haven't, and if you're still having this issue, please refer to the Wiki "How To Report Issues" and provide a fresh debug log. Thanks!
Updated by Bernhard Hailer over 4 years ago
- Status changed from Feedback to Closed
Closing, because there seems to be no more feedback.
However:
This looks like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.