Bug #6311: BF-F8HP - Radio did not respond - CHIRP

Actions

Copy link

Bug #6311

closed

BF-F8HP - Radio did not respond

Added by Joey Adair over 5 years ago. Updated over 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

chirp-legacy

Start date:

12/18/2018

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Baofeng BF-F8HP

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Radio was previously programming with Chirp. After latest CHIRP update, get message on any connect attempt "Radio did not respond".

Clone Progress bar displays, but does not advance, radio backlight comes on and radio reboots, Clone progress bar still does not advance, then the message "Radio did not respond" appears.

debug file attached.

I am helping an old Vietnam vet who is trying to get into HAM radio. He lives alone and doesn't have a lot of money. Any help would be greatly appreciated!

Files

debug.log (23.4 KB) debug.log

Joey Adair, 12/18/2018 08:48 PM

Related issues

Actions

Copy link

Updated by Bernhard Hailer almost 4 years ago

Target version set to chirp-legacy
Model affected changed from (All models) to Baofeng BF-F8HP

Sorry for the late response. Have you been able to resolve this on your own since you submitted this?

Thanks for the log. Unfortunately, this looks like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]

Windows: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.

Actions

Copy link