Bug #4629

Baofeng GT-3 TP "Radio did not respond" - Mac OSX

Added by Matteo Sta over 3 years ago. Updated 4 months ago.

Status:Feedback Start date:03/16/2017
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Baofeng GT-3WP

Description

Trying to download from Radio, selecting BF-F8HP model I get an error "Radio did not respond". The cable seems to be ok: to try I used also different models. With UV-5R i get same error but using GT-3WP i get "Error reading data from radio:not the amount of data we want". I used same computer, same cable to program / download from a UV-5R and it works.

With GT3 TP

[2017-03-16 11:46:31,507] chirp.ui.mainapp - DEBUG: User selected Baofeng BF-F8HP on port /dev/cu.usbserial
[2017-03-16 11:46:31,516] chirp.ui.clone - DEBUG: Clone thread started
[2017-03-16 11:46:31,517] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.

[2017-03-16 11:46:32,604] chirp.drivers.uv5r - ERROR: Radio did not respond
[2017-03-16 11:46:34,609] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 14 04 13 00 P.......

[2017-03-16 11:46:35,692] chirp.drivers.uv5r - ERROR: Radio did not respond
[2017-03-16 11:46:37,693] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.

[2017-03-16 11:46:38,781] chirp.ui.reporting - DEBUG: Reporting exception
[2017-03-16 11:46:38,781] chirp.ui.common - ERROR: -- Exception: --
[2017-03-16 11:46:38,781] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/Applications/chirp-daily-20170311.app/Contents/Resources/chirp/chirp/ui/clone.py", line 249, in run
self.__radio.sync_in()
File "/Applications/chirp-daily-20170311.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 729, in sync_in
self._mmap = _do_download(self)
File "/Applications/chirp-daily-20170311.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 542, in _do_download
data = _ident_radio(radio)
File "/Applications/chirp-daily-20170311.app/Contents/Resources/chirp/chirp/drivers/uv5r.py", line 537, in _ident_radio
raise error
RadioError: Radio did not respond

Same Chirp version, same cable, different radio (UV-5R)

2017-03-16 11:49:41,252] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-5R on port /dev/cu.usbserial
[2017-03-16 11:49:41,258] chirp.ui.clone - DEBUG: Clone thread started
[2017-03-16 11:49:41,259] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.

[2017-03-16 11:49:41,357] chirp.drivers.uv5r - INFO: Valid response, got this:
[2017-03-16 11:49:41,358] chirp.drivers.uv5r - DEBUG: 000: aa 30 76 04 00 05 20 dd .0v.....

[2017-03-16 11:49:41,705] chirp.drivers.uv5r - INFO: Radio Version is 'HN5RV011\xff\xff\xff\xff\xff\xff'
[2017-03-16 11:49:41,705] chirp.drivers.uv5r - DEBUG: downloading main block...
[2017-03-16 11:49:58,426] chirp.drivers.uv5r - DEBUG: done.
[2017-03-16 11:49:58,426] chirp.drivers.uv5r - DEBUG: downloading aux block...
[2017-03-16 11:49:59,296] chirp.drivers.uv5r - DEBUG: done.
[2017-03-16 11:49:59,349] chirp.ui.clone - DEBUG: Clone thread ended

History

Updated by Bernhard Hailer 4 months ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • Model affected changed from (All models) to Baofeng GT-3WP

This looks like a cable issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)

I know you said that the same cable works on another Baofeng radio, so it might be a problem with the connector not going in far enough. Try pressing hard, holding it at an angle.

Also available in: Atom PDF

prevent spam