Bug #10784: Radio did not respond - CHIRP

Actions

Copy link

Bug #10784

closed

Radio did not respond

Added by Bill Hooper almost 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

08/14/2023

Due date:

% Done:

Estimated time:

Chirp Version:

Model affected:

BF-F8HP & UV-50x2

Platform:

Windows

Debug Log:

I read the instructions above:

Description

I have 4 Baofeng radios the I have programmed with Chirp in the past.
Today I tried to download form my radio to chirp but it failed to connect

See attached photos

Files

Download all files

Chirp Ver.jpg (54.8 KB) Chirp Ver.jpg		Bill Hooper, 08/14/2023 08:58 AM
Chirp Info.jpg (284 KB) Chirp Info.jpg		Bill Hooper, 08/14/2023 08:58 AM
debug_log.png (44.7 KB) debug_log.png		Jim Unroe, 08/14/2023 02:33 PM
BTECH_models.png (36.3 KB) BTECH_models.png		Jim Unroe, 08/14/2023 02:40 PM

Actions

Copy link

Updated by Jim Unroe almost 2 years ago

You should supply a clean debug.log file for each radio. Start CHIRP (to start a new log), cause the error, then access the debug.log file from the Help menu.

But going strictly from the pictures...

The photo shows that the UV-5X model is selected. This would be incorrect for the models listed in the Model affected field of this issue.

The Radio did not respond error could also be an indication that you do not have a working connection between the radio and computer. For example, if you leave the plug completely unattached from the radio and attempt a download for a BF-F8HP, the same error would be displayed. Make sure that the plug is fully engaged in the radio's socket. Sometimes with these low cost handheld radios you have press on the plug to ensure that there is a connection during the cloning process.

Actions

Copy link

Updated by Bill Hooper almost 2 years ago

Thanks for the reply Jim.
There is no link on the Help tab for the debug log in the Chirp App.
The Model UV-5X was the closest to My radio UV-50X2.
I read some similar issues about the connector not making contact.
All 4 radios ... I held the connector as tight as I could (really tight!) no luck.

Actions

Copy link Download all files

Updated by Jim Unroe almost 2 years ago

File debug_log.png debug_log.png added
File BTECH_models.png BTECH_models.png added

Bill Hooper wrote in #note-2:

Thanks for the reply Jim.
There is no link on the Help tab for the debug log in the Chirp App.

There most certainly is. The Help menu list has the Open debug log and under it the Show debug log location depending on your needs. See screen capture.

The Model UV-5X was the closest to My radio UV-50X2.

This is wrong because the Baofeng UV-5X is a very old variant of the UV-5R. The BTECH UV-50X2 sold by Baofeng Tech (the radio dealer in the USA) is not manufactured by Baofeng. All BTECH labeled radios will be found after choosing BTECH for the Vendor. See screen capture.

I read some similar issues about the connector not making contact.

Yes. This is a common problem. No programming software will be able to read from or write to a radio until the user supplies a working connection.

All 4 radios ... I held the connector as tight as I could (really tight!) no luck.

OK. So now we know that the wrong Vendor/Model is being chosen to program the UV-50X2. That can't work. So try again using the correct Vendor/Model selections. And if you have the Second Generation UV-50X2 be sure to select UV-50X2_G2 for the model.

And just for clarification... The Baofeng BF-F8HP uses a PC03 style programming cable (2 pins). The BTECH UV-50X2(_G2) uses a PC04 style programming cable (1 pin). You can't use the same programming cable for both radios.

Actions

Copy link