Project

General

Profile

Actions

Bug #5127

closed

BF-F9V2+ Unable to download Radio - Radio did not respond

Added by Michael Gray over 6 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-F9V2+
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I'm trying to program my radio. I had a bad cable before and just got my FTDI cable today, while I can get the radio to recognize, I can't download the radio.

Baofeng BF-F9V2+, firmware bfp3-25 (3-key on startup)
CHIRP daily-20170714
USB Serial Converter, FTDI, 2.12.28.0 08/16/2017

Download from Radio > COM3, Baofeng, BF-F8HP > "An error has occurred. Radio did not respond"

Other troubleshooting, beside driver updates and latest versions... rebooted machine after updated FTDI driver. Visually inspected (flashlight) dual-ports on radio. Firm grip-pressed the cable to the radio during "download". Log file has been attached.

Any guidance would be appreciated. Thanks,
Michael.
K2EXO

Snippet:

[2017-09-04 13:29:55,510] chirp.drivers.uv5r - ERROR: Radio did not respond
[2017-09-04 13:29:57,513] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 14 04 13 00 P.......

[2017-09-04 13:29:58,586] chirp.drivers.uv5r - ERROR: Radio did not respond
[2017-09-04 13:30:00,586] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 00 P.....(.

[2017-09-04 13:30:01,661] chirp.ui.reporting - DEBUG: Reporting exception
[2017-09-04 13:30:01,663] chirp.ui.common - ERROR: -- Exception: --
[2017-09-04 13:30:01,663] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 249, in run
File "chirp\drivers\uv5r.pyo", line 806, in sync_in
File "chirp\drivers\uv5r.pyo", line 542, in _do_download
File "chirp\drivers\uv5r.pyo", line 537, in _ident_radio
RadioError: Radio did not respond

[2017-09-04 13:30:01,663] chirp.ui.common - ERROR: ----------------
[2017-09-04 13:30:01,663] chirp.ui.clone - ERROR: Clone failed: Radio did not respond
[2017-09-04 13:30:01,706] chirp.ui.clone - DEBUG: Clone thread ended
[2017-09-04 13:30:01,706] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_BF-F8HP,download,True
[2017-09-04 13:30:01,707] chirp.ui.reporting - DEBUG: Reporting exception
[2017-09-04 13:30:01,707] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not respond ---
[2017-09-04 13:30:01,707] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 64, in
AttributeError: 'NoneType' object has no attribute 'split'

[2017-09-04 13:30:01,709] chirp.ui.inputdialog - ERROR: ----------------------------


Files

debug - Copy.log (21.9 KB) debug - Copy.log Michael Gray, 09/04/2017 10:40 AM
Actions #1

Updated by Michael Gray over 6 years ago

bump

Actions #2

Updated by Jim Unroe over 6 years ago

  • Status changed from New to Feedback

Does the factory software work? Unless it does, this is most likely do to a cabling issue (probably a poor connection between the 2-pin plug of the programming cable and the socket of the radio).

Jim KC9HI

Actions #3

Updated by Matt Price over 6 years ago

What version of windows are you running? If you are running 8 or newer you will have to run CHIRP in compatibility mode windows 7. Thats the issue i had with my bf-F9

Actions #4

Updated by Michael Gray over 6 years ago

I misplaced the factory software somewhere on my 5TB NAS...

I am running Windows 10 - I will try compatibility mode later tonight hopefully that's it.

Michael K2EXO

Actions #5

Updated by Michael Gray over 6 years ago

No success with compatibility mode nor with run as administrator.

Any new ideas? Instead of querying the radio to download, is there a way to push stock firmware back up (or something like that? Upload to radio is greyed out currently).

Actions #6

Updated by Bernhard Hailer about 4 years ago

  • Target version set to chirp-legacy
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to Baofeng BF-F9V2+

Did you try the factory software as suggested?
You might want to try again with a recent version and to share the debug log.

Actions #7

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Actions

Also available in: Atom PDF