Bug #3345

Radio refused to send second block 0x1fc0

Added by Ricky Fleming over 4 years ago. Updated 7 months ago.

Status:Closed Start date:02/17/2016
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Baofeng UV-5R

Description

I've followed the other pose referring to this issue however the error number differs by 1 character. I've tried all potential solutions including downloading the cv5r.py that was given by someone but I have not yet been able to get my UV5R to clone. I purchased my radio from Amazon and have had this same issue with another one that was purchased from Amazon. I currently am running the dailybuild-20160215 but have tried other builds with no success. Looking for any insight on how I can get this to work.


Related issues

duplicates Bug #6681: Baofeng UV-5R refused to send second block 0x1f00 Closed 04/09/2019

History

Updated by Ricky Fleming over 4 years ago

I have also successfully cloned and updated my UV-5R with the Baofeng software however it will not allow me to add a custom channel name so I am stuck with just the Freqencies.

Updated by Jim Unroe over 4 years ago

  • Status changed from New to Feedback

My guess is that you have a programming cable with a Prolific type chip. If you are running with the Windows auto installed Prolific device driver, the auto installed device driver is incompatible with Prolific chip clones. You will have to downgrade to the 2007 device driver which is compatible with all Prolific chips, genuine or counterfeit. Get links to the driver and instructions to install and select the Prolific v3.2.0.0 device driver on the miklor.com USB Cables and Drivers for Microsoft XP, Vista, Win7, Win8 and Win10 page.

Note: The OEM software does program channel names and has for the nearly 4 years that I have had my UV-5R.

If you don't want to do the above, then get a programming cable with and FTDI chip or convert your existing programming cable to a CP2102 type chip as shown on this guide to Build your own programming cable.

Updated by Ricky Fleming over 4 years ago

Jim Unroe wrote:

My guess is that you have a programming cable with a Prolific type chip. If you are running with the Windows auto installed Prolific device driver, the auto installed device driver is incompatible with Prolific chip clones. You will have to downgrade to the 2007 device driver which is compatible with all Prolific chips, genuine or counterfeit. Get links to the driver and instructions to install and select the Prolific v3.2.0.0 device driver on the miklor.com USB Cables and Drivers for Microsoft XP, Vista, Win7, Win8 and Win10 page.

Note: The OEM software does program channel names and has for the nearly 4 years that I have had my UV-5R.

If you don't want to do the above, then get a programming cable with and FTDI chip or convert your existing programming cable to a CP2102 type chip as shown on this guide to Build your own programming cable.

I have already downloaded what you are suggesting. The driver I am currently running is the 3.2.0.0

Updated by Bernhard Hailer 7 months ago

  • Status changed from Feedback to Closed
  • Assignee deleted (Ricky Fleming)
  • Priority changed from Urgent to Normal
  • Target version set to chirp-daily
  • Model affected changed from UV-5R to Baofeng UV-5R

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

Also available in: Atom PDF

prevent spam