Project

General

Profile

Actions

BaofengUV5R » History » Revision 24

« Previous | Revision 24/30 (diff) | Next »
John LaMartina, 06/20/2016 03:29 PM


{{toc}}

h1. Baofeng UV5R / UV82 (and varients)

This page provides general tips and troubleshooting for the Baofeng UV-5R, UV-82, and related radios. The UV-5R is the base model for a lot of variants, so this page will apply to many more people than just those with that specific badge on their radio. This information is a summarized version of the Miklor page on the subject. Go there for "more detailed information":http://www.miklor.com/COM/UV_ErrorMess.php

h2. Common Errors

h3. - Radio Did Not Respond

  • Unable to Program
  • Radio did Not Ack Programming Mode
  • Radio did Not Ack first command
  • Radio Radio refused to enter Programming Mode

This is a very common problem. Slightly offset audio jacks could be the problem. Make sure the connector is snapped in all the way. Some cables require a really hard push to snap in that last 1/16 inch. One indication is that the transmitter may be keyed. A slight trimming of the cable's plug side and edge may be required.

The GT3 and similar radios with optional case designs may require a slightly different approach to trimming the cable. The cable cannot seat properly, not because it is misaligned, but rather the ridge on the case may be protruding out too far.
The cable may still need to be trimmed, but from the cable tension area. Here is a "Graphic and Possible Solution":http://www.miklor.com/COM/UV_ErrorMess.php#error1

h3. - Error has Occurred, Could not open Com Port x

Each USB slot is connected to a separate com port to avoid conflict. Changing your USB slot will change the com port number.
After making this change, you must unplug and replug your USB programming cable for the new com port number to be effective.

h3. - Run-time error 8020: Error reading from comm device.

  • Cannot Start (Code 10) in Windows 8

Error occurs if Prolific driver version is higher than v3.2.0.0
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php

h3. - CHIRP does not support my (Model Radio)

  • Radio Version Not Supported
  • Failed to communicate with radio: global name 'vendors' is not defined

These messages are generated if you are running a much older version of CHIRP. You must upgrade to CHIRP's Latest Daily Build.

h3. - Run-time error 8020: Error reading from comm device.

  • Cannot Start (Code 10) in Windows 8

Error occurs if Prolific driver version is higher than v3.2.0.0
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php

h3. - Run-time error 8020: Error reading from comm device.

  • Cannot Start (Code 10) in Windows 8

Error occurs if Prolific driver version is higher than v3.2.0.0
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php

h3. - Run-time error 8020: Error reading from comm device.

  • Cannot Start (Code 10) in Windows 8

Error occurs if Prolific driver version is higher than v3.2.0.0
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php

h3. Driver Issues

Many of the inexpensive programming cables are not the bargain they appear.
Due to Prolific USB/Serial chip 'clones' found in generic USB programming cables, an older driver is required in lieu of the driver now automatically supplied by Windows. for "more detailed information":http://http://www.miklor.com/COM/UV_Drivers.php

Updated by John LaMartina almost 8 years ago · 24 revisions