Project

General

Profile

Actions

Bug #5181

closed

UV-82 reading problems with chirp-daily-20170714

Added by D Berastau over 6 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
09/21/2017
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-82
Platform:
All
Debug Log:
I read the instructions above:

Description

I am running into issues getting Chirp to talk to my newly purchased UV82. Details below:

Firmware (#3): Version NUV82
Firmware (#6): 161102N
Driver: CH340
Chirp Version: daily-20170714

The driver seems to have been installed properly (I can see it in USB Devices, no errors are reported, tried this on Windows 7 and on OS X 10.12.x Sierra).

I am getting this in the debug.log:
[2017-09-21 23:18:47,988] chirp.ui.inputdialog - ERROR: ----------------------------
[2017-09-21 23:20:10,279] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-82 on port /dev/cu.wchusbserial1420
[2017-09-21 23:20:10,287] chirp.ui.clone - DEBUG: Clone thread started
[2017-09-21 23:20:10,533] chirp.ui.reporting - DEBUG: Reporting exception
[2017-09-21 23:20:10,533] chirp.ui.common - ERROR: -- Exception: --
[2017-09-21 23:20:10,534] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/private/var/folders/fq/1v9f456d2z7739cg2w0_r5m0000gn/T/AppTranslocation/206B838B-2E15-45BD-8019-73903A9AB78D/d/chirp-daily-20170714.app/Contents/Resources/chirp/chirp/ui/clone.py", line 249, in run
self.
radio.sync_in()
File "/private/var/folders/fq/1v9f456d2z7739cg2w0
r5m0000gn/T/AppTranslocation/206B838B-2E15-45BD-8019-73903A9AB78D/d/chirp-daily-20170714.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 806, in sync_in
self._mmap = _do_download(self)
File "/private/var/folders/fq/1v9f456d2z7739cg2w0
r5m0000gn/T/AppTranslocation/206B838B-2E15-45BD-8019-73903A9AB78D/d/chirp-daily-20170714.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 544, in _do_download
radio_version = _get_radio_firmware_version(radio)
File "/private/var/folders/fq/1v9f456d2z7739cg2w0
r5m0000gn/T/AppTranslocation/206B838B-2E15-45BD-8019-73903A9AB78D/d/chirp-daily-20170714.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 498, in _get_radio_firmware_version
block1 = _read_block(radio, 0x1EC0, 0x40, True)
File "/private/var/folders/fq/1v9f456d2z7739cg2w0
_r5m0000gn/T/AppTranslocation/206B838B-2E15-45BD-8019-73903A9AB78D/d/chirp-daily-20170714.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 478, in _read_block
raise errors.RadioError("Unknown response from radio")
RadioError: Unknown response from radio

The error is pretty much identical between OS X and Windows 7.

I've looked through a bunch of stuff other people have reported and it looks like the error is not identical. Anyone has any ideas? My next step would be to try a different cable but before I go down that route, I'd appreciate if somebody could confirm that it's not code/firmware related.

Thanks!


Files

debug.log (25.6 KB) debug.log D Berastau, 09/21/2017 11:57 PM

Related issues

Is duplicate of Bug #6567: Error reading Baofeng UV-6ClosedJim Unroe03/05/2019

Actions
Actions #1

Updated by D Berastau over 6 years ago

Looks like posting has ignored a chunk of the debug log output I've included, I've included it below:

[2017-09-21 23:18:47,988] chirp.ui.inputdialog - ERROR: ----------------------------
[2017-09-21 23:20:10,279] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-82 on port /dev/cu.wchusbserial1420
[2017-09-21 23:20:10,287] chirp.ui.clone - DEBUG: Clone thread started
[2017-09-21 23:20:10,288] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 13 01 05 00   P.......

[2017-09-21 23:20:10,428] chirp.drivers.uv5r - INFO: Valid response, got this:
[2017-09-21 23:20:10,428] chirp.drivers.uv5r - DEBUG: 000: aa 20 79 00 00 05 00 dd   ..y.....

[2017-09-21 23:20:10,531] chirp.drivers.uv5r - ERROR: Invalid answer for block 0x1ec0:
[2017-09-21 23:20:10,531] chirp.drivers.uv5r - DEBUG: CMD: 88  ADDR: 1e80  SIZE: 00
[2017-09-21 23:20:10,533] chirp.ui.reporting - DEBUG: Reporting exception
Actions #2

Updated by Bernhard Hailer about 4 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-legacy
  • Model affected changed from (All models) to Baofeng UV-82

Some (not very satisfactory) input can be found at #6567.

Actions #3

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from Feedback to Closed

Duplicates #6567 (different radio, same problem). Please follow and post there. Thanks!

Actions

Also available in: Atom PDF