Project

General

Profile

Actions

Bug #7115

closed

Baofeng UV-5R "Radio refused to send block 0x0000"

Added by Andrey Dias about 5 years ago. Updated almost 5 years ago.

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

0%

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

Description

Hello,

I have a Baofeng UV-5R Firewame BFB297, I bought the cable I installed the driver and CHIRP 0.3.0, everything works perfectly, I can clone save configs, etc ... all a wonder!

This week I got another Baofeng UV-5R, but when I try to clone CHIRP 0.3.0 I get the following error: "Radio refused to send block 0x0000" and the radio restarts! just stay in it ...

One thing I noticed is that this new radio's Firewame is "BFB298", ask?

Why does everything work fine on BFB297 and not work on BFB298?

Have a solution to this problem?

Andrey Dias


Files

debug.log (27.2 KB) debug.log Loren Gibson, 02/27/2020 02:16 AM

Related issues 2 (0 open2 closed)

Related to Bug #6567: Error reading Baofeng UV-6ClosedJim Unroe03/05/2019

Actions
Is duplicate of Bug #6681: Baofeng UV-5R refused to send second block 0x1f00Closed04/09/2019

Actions
Actions #1

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal
  • Target version set to chirp-legacy

Chirp 0.3.0? It's ancient :-)
Please download a daily build and see whether your problem persists. Thanks!

Actions #2

Updated by Loren Gibson almost 5 years ago

Problem persists in CHIRP daily-20200227, although now the error message states "Radio refused to send second block 0x1f00" rather than 0x0000.

debug.log attached.

Actions #3

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from Feedback to Closed

Duplicates #6681, which has attracted further input. Please leave any feedback there. Thanks!

Actions

Also available in: Atom PDF