Bug #3917
closedradio refused to send block code 0x1ec0 Baofeng UV82
0%
Description
I got a new Baofeng UV82. I tried to clone my old UV5R to it. Everything was working before I tried the clone. I could see everything on both radios.I got an error message during the process of cloning and it would not transfer to the new uv82. Now when I try to connect the UV82 it gives me this message : radio refused to send block code 0x1ec0 . The UV5R still works, I can download it to chirp. I done a reset on my uv82 and it did not help. PLEASE HELP. Thanks
Files
Updated by Jim Unroe almost 9 years ago
- Status changed from New to Incomplete
Colby,
Which version of CHIRP are you using? It should be the latest daily build.
Which chip is in your programming cable? If it is a Prolific type chip, have do downgraded the driver that Windows installed to v3.2.0.0?
You can't directly upload from a UV-5R to a UV-82 (or the other way around). You have to import the UV-5R image into a tab from the UV-82. Some like to just open a tab for each radio and copy-and-paste between them.
Jim KC9HI
Updated by Colby G. almost 9 years ago
Jim,
I am using the latest CHIRP daily build. The cable is the common cable that comes with the new Baofeng's. It goes to the speaker mike. I ended up programming some frequencies in manually. At the beginning I exported a file from the UV-5R and then hooked up the UV82 and tried to copy it to it. It wouldn't do it and then it stopped seeing the UV82. It gives me that error now when I hook up the UV82 to the computer for the CHIRP program. Thanks for your help.
Updated by Jim Unroe almost 9 years ago
- File ProlificDrivers2.jpg ProlificDrivers2.jpg added
If it is the "common" programing cable, then it has the common counterfeit Prolific chip in it. You can confirm this in Device Manager. If that is the case, then the v3.2.0.0 device driver must be downloaded, installed and selected before the programming cable with function reliably. You can only avoid this by getting a programming cable with an FTDI (or some other non-Prolific type chip).
See in the attached screen capture where I have 4 Prolific device drivers installed. The v3.2.0.0 driver has been selected to work with my cheap programming cable with counterfeit Prolific type chip.
Take a look at this "web page":http://www.miklor.com/COM/UV_Drivers.php for instructions.
Jim KC9HI
Updated by Bernhard Hailer over 5 years ago
- Status changed from Incomplete to Closed
- Model affected changed from (All models) to Baofeng UV-82
No morew feedback by submitter.