Bug #7455

Baofeng UV-5R radio not responding

Added by John Kilco about 1 month ago. Updated 14 days ago.

Status:Feedback Start date:12/12/2019
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Linux
Model affected:(All models)

Description

Chirp daily latest version used
original FTDI radioddity usb cable used
It appears from the error.log that the Radio id (Baofeng UV-5R)is rejected thus causing an error
Firmware (3 + Power on) BFB298
Radio UV-5R 136-174mhz 400-520mhz S/N 13u38131131

error file

[2019-12-12 10:46:06,249] chirp.ui.reporting - DEBUG: Checking for updates
[2019-12-12 10:46:06,911] chirp.ui.reporting - DEBUG: Server reports version daily-20191206 is latest
[2019-12-12 10:49:34,784] chirp.ui.mainapp - DEBUG: User selected Baofeng BF-F8HP on port /dev/ttyUSB0
[2019-12-12 10:49:35,070] chirp.ui.clone - DEBUG: Clone thread started
[2019-12-12 10:49:35,073] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.

[2019-12-12 10:49:35,213] chirp.drivers.uv5r - DEBUG: '\x00'
[2019-12-12 10:49:35,214] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2019-12-12 10:49:37,217] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 14 04 13 00 P.......

[2019-12-12 10:49:37,292] chirp.drivers.uv5r - DEBUG: '\xfc'
[2019-12-12 10:49:37,293] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2019-12-12 10:49:39,298] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.

[2019-12-12 10:49:39,375] chirp.drivers.uv5r - DEBUG: '\x87'
[2019-12-12 10:49:39,382] chirp.ui.reporting - DEBUG: Reporting exception
[2019-12-12 10:49:39,383] chirp.ui.common - ERROR: -- Exception: --
[2019-12-12 10:49:39,388] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 809, in sync_in
self._mmap = _do_download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 543, in _do_download
data = _ident_radio(radio)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 538, in _ident_radio
raise error
RadioError: Radio did not respond

[2019-12-12 10:49:39,389] chirp.ui.common - ERROR: ----------------
[2019-12-12 10:49:39,390] chirp.ui.clone - ERROR: Clone failed: Radio did not respond
[2019-12-12 10:49:39,400] chirp.ui.clone - DEBUG: Clone thread ended
[2019-12-12 10:49:39,412] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_BF-F8HP,download,True
[2019-12-12 10:49:39,418] chirp.ui.reporting - DEBUG: Reporting exception
[2019-12-12 10:49:39,418] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not respond ---
[2019-12-12 10:49:39,430] chirp.ui.inputdialog - ERROR: None

[2019-12-12 10:49:39,431] chirp.ui.inputdialog - ERROR: ----------------------------

History

Updated by bit basher 25 days ago

Where is error.log generated? You need to enable it from the Help->Enable Developer Functions first, yes?

I did search chirp website and did not find this answer. TIA.

Updated by Jim Unroe 17 days ago

  • Status changed from New to Feedback

The radio is either not communicating with CHIRP (which could be a programming cable, device driver or connection issue between the 2-pin plug and the speaker/mic socket) or the user is selecting the wrong radio model.

Why are you choosing BF-F8HP when you have a UV-5R?

Jim KC9HI

Updated by Jim Unroe 17 days ago

bit basher wrote:

Where is error.log generated? You need to enable it from the Help->Enable Developer Functions first, yes?

I did search chirp website and did not find this answer. TIA.

You do not have to enable anything. CHIRP always generates a debug.log file when it runs. The How To Report Issues page shows how to locate the debug.log file in all 3 supported operating systems.

Jim KC9HI

Updated by John Kilco 14 days ago

I have been unable to respond before but her is current error log, the issue with false radio being chosen is not the issue. Cable is producing electrical output as checked with multimeter...

current error log below:

2020-01-07 19:45:55,563] chirp.ui.reporting - DEBUG: Checking for updates
[2020-01-07 19:45:56,099] chirp.ui.reporting - DEBUG: Server reports version daily-20200107 is latest
[2020-01-07 19:47:53,683] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-5R on port /dev/ttyUSB0
[2020-01-07 19:47:53,687] chirp.ui.clone - DEBUG: Clone thread started
[2020-01-07 19:47:53,688] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.

[2020-01-07 19:47:53,760] chirp.drivers.uv5r - DEBUG: '\x00'
[2020-01-07 19:47:53,760] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2020-01-07 19:47:55,763] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d 00 P...%.M.

[2020-01-07 19:47:55,836] chirp.drivers.uv5r - DEBUG: '\xf0'
[2020-01-07 19:47:55,837] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2020-01-07 19:47:57,838] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.

[2020-01-07 19:47:57,911] chirp.drivers.uv5r - DEBUG: '\x87'
[2020-01-07 19:47:57,913] chirp.ui.reporting - DEBUG: Reporting exception
[2020-01-07 19:47:57,913] chirp.ui.common - ERROR: -- Exception: --
[2020-01-07 19:47:57,914] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 809, in sync_in
self._mmap = _do_download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 543, in _do_download
data = _ident_radio(radio)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 538, in _ident_radio
raise error
RadioError: Radio did not respond

[2020-01-07 19:47:57,915] chirp.ui.common - ERROR: ----------------
[2020-01-07 19:47:57,915] chirp.ui.clone - ERROR: Clone failed: Radio did not respond
[2020-01-07 19:47:57,917] chirp.ui.clone - DEBUG: Clone thread ended
[2020-01-07 19:47:57,920] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_UV-5R,download,True
[2020-01-07 19:47:57,931] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not respond ---
[2020-01-07 19:47:57,932] chirp.ui.inputdialog - ERROR: None

[2020-01-07 19:47:57,932] chirp.ui.inputdialog - ERROR: ----------------------------
[2020-01-07 19:47:57,934] chirp.ui.reporting - DEBUG: Reporting exception

it appears cable is ok....
radio wake up not working

I am a dumbo but trying#

Updated by John Kilco 14 days ago

Have decided that output from software is ok, Drivers & cables are ok.. so its a radio connection problem.... I am going to take it apart to see what it is......

Will update solution (I hope here)

Also available in: Atom PDF