Project

General

Profile

Actions

Bug #3411

closed

UV-82HP not downloading to CHIRP

Added by Chris Welch about 9 years ago. Updated about 9 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
UV-82HP
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Hello,

My friend's new Baofeng UV-82HP does not want to be read. I connect it like normal, it starts the cloning possess, and then I get an error message "Radio refused to send block 0x1ec0" This problem doesn't exist with my UV-5R, Wouxun KG-UV6X, or other friend's radios. However, I do not have another UV-82 to test.

Running Win 7, Chirp Daily-20160301 (the latest), and the authentic Baofeng Tech computer cable.

Actions #1

Updated by David Inman about 9 years ago

System MAC OS X ver 10.11.1
Chirp Daily 20160309

I seem to be having the same issue. Just purchased the UV-82HP on Amazon via BoaFeng Tech it has firmware N82-33 / US2S35. I also purchased a USB programming cable that stated it was by Baofeng sold by Amazon (box also says mfg by Baofeng designed by SainSonic). The box also says that it is a UV-5R programming cable with a mfg date of 2015.11.14.

When I try to download the radio I get the message "Radio refused to send block 0x1ec0". So I pulled out my old Kenwood serial cable that has a Prolific USB to serial adapter. When I plugged it in and selected the correct port I was able to immediately download the radio contents. When I look in system preferences at the two USB devices they are the same prolific product/vendor id and they are both using driver version 2.0.

This cable cost about $6.25 where as I found another one today with an FTDI chip that says genuine that was around $20.

Thanks
David

Actions #2

Updated by David Inman about 9 years ago

Okay.. so I bought the FTDI cable and now I have no issues

Actions #3

Updated by Jim Unroe about 9 years ago

  • Status changed from New to Resolved

The cheap programming cables (with Prolific type chips) when used with Windows requires that you install and select an older prolific device driver (v2.0.2.1 for XP, v3.2.0.0 for Vista, 7, 8, 8.1 and 10).

Glad to hear you solved it with the FTDI based programming cable. No programming software can function with a complete and working connection between the computer and radio.

Jim KC9HI

Actions #4

Updated by Jim Unroe about 9 years ago

  • Status changed from Resolved to Closed
Actions #5

Updated by Chris Welch about 9 years ago

Wait a minute... I have and always had the FTDI programming cable! Got it from Baofeng Tech for $20...

Do the FTDI cables need to be updated or something? Every few years, do I need to buy a new one to match the new radios?

I'd like to get some help on this, I got another 4 UV-82 radios coming my way (being the comm officer for this group) in a few days, and I would like to know if I can read those radios or not.

-OP Welch

Actions #6

Updated by Jim Unroe about 9 years ago

  • Status changed from Closed to Incomplete

The FTDI cable should be fine. You can try the latest driver from the FTDI website.

Actions #7

Updated by Chris Welch about 9 years ago

I went though the FTDI website and downloaded the latest and greatest drivers (2.12.14) that was produced just last month (the last one was 2 years old). The update installed fine, but this UV-82HP still doesn't want to clone to my computer. I even uninstalled then reinstalled the drivers, still doesn't connect. Still getting the "Radio refused to send block 0x1ec0" error message.

Actions #8

Updated by Jim Unroe about 9 years ago

"0x1ec0" is the start of the "aux" block of memory. That means the "main" block of memory was received successfully. It could be your radio doesn't support sending this section of memory. The UV-B5/B6 radios with 27 menus no longer support sending the "service settings" block of memory. I would recommend that you contact Baofeng Tech.

Jim

Actions #9

Updated by Chris Welch about 9 years ago

I did that, and after about 10 emails, they said to "hold the connection down while cloning."

Guess what? It worked! Maybe add to the SOPs that sometimes the connection in the radio might be a millimeter too low, and you need to tightly grip the radio and the cable connection to push in the pins that fraction of a bit more, right as you click "read."

I'm good! Thanks!

Actions #10

Updated by Jim Unroe about 9 years ago

  • Status changed from Incomplete to Resolved

I glad to hear you have a workable solution.

Actions #11

Updated by Jim Unroe about 9 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF