Project

General

Profile

Actions

Bug #4979

closed

Baofeng uv 5r error downloanding and uploanding configuration.

Added by Paco Pineda over 7 years ago. Updated almost 5 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5R
Platform:
Linux
Debug Log:
I read the instructions above:

Description

Hi,

When I try to download configuration from radio-walky, more or less at middle of process I get the following message:

"Radio sent incomplete block xxxxxx" (where xxxxxx are a hexadecimal memory address -I suppose-)

If I try to upload a pre-existent configuration to radio, in the same way, more or less at middle of process I get the following message:

"Radio refused to accept block xxxxxx" (where xxxxxx are a hexadecimal memory address -I suppose-)

Environmento:

Radio: Baofeng uv 5r
Radio Firmware (pressing key 3 while switching ON): BFB297
CHIRP Version: Daily-20170627 (periodically and correctly updated from official CHIRP PPA-repository)
GTK: 2.24.30
PyGTK: 2.24.0I'
Pyton: 2.7.12
Computer Operating System: Ubuntu Linux 16.04-1 64Bits
Kernel: 4.4.0-83

Cable used: Standard USB to radio cable.

I'm exclusive linux user, so have not access to windows environment. Anyway, I've tried to send and receive data from radio using different radio software like GNUAis, JWX, JNX... and it works (I use the same exact cable).

Any help or suggestion to help me?.

Thank you in advance.

Actions #1

Updated by Paco Pineda over 7 years ago

As I've read... this issue can be produced by the Bug #1773, but at same time, I must suppose that bug was solved/patched about 2 years ago... so, how it can happens again? -confused-.

Thank you in advance for your future help.

Actions #2

Updated by Mike K about 7 years ago

I ran into the same problem on a Raspberry Pi. It was happening with my UV-5R, BF-F8HP, and UV-82HP. With the UV-82X it just shows "radio did not respond". I found this problem was due to newer fake/clone Prolific cables made within the past year or so. As soon as I switched to a cable with a real Prolific chip or genuine FTDI chip, it read and wrote to radios no problem.

Actions #3

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from New to Closed
  • Model affected changed from Baofeng uv 5r to Baofeng UV-5R

A solution has been suggested.

Actions

Also available in: Atom PDF