CHIRP

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

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.

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

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: ----------------------------