Project

General

Profile

BaofengUV5R » History » Version 27

John LaMartina, 06/20/2016 03:39 PM

1 1 Dan Smith
{{toc}}
2
3 11 John LaMartina
h1. Baofeng UV5R / UV82 (and varients)
4 1 Dan Smith
5 12 John LaMartina
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
6 1 Dan Smith
7
h2. Common Errors
8 26 John LaMartina
 
9 8 John LaMartina
10 18 John LaMartina
h3. - Radio Did Not Respond
11 17 John LaMartina
- Unable to Program
12
- Radio did Not Ack Programming Mode
13
- Radio did Not Ack first command
14
- Radio Radio refused to enter Programming Mode 
15 1 Dan Smith
16 2 Dan Smith
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.
17 3 John LaMartina
18 19 John LaMartina
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. 
19 21 John LaMartina
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
20 26 John LaMartina
 
21 21 John LaMartina
22
h3. - Error has Occurred, Could not open Com Port x
23
24
Each USB slot is connected to a separate com port to avoid conflict. Changing your USB slot will change the com port number.
25 1 Dan Smith
After making this change, you must unplug and replug your USB programming cable for the new com port number to be effective.
26 26 John LaMartina
 
27 1 Dan Smith
28 23 John LaMartina
h3. - Run-time error 8020: Error reading from comm device.
29
- Cannot Start (Code 10) in Windows 8 
30 1 Dan Smith
31
Error occurs if Prolific driver version is higher than v3.2.0.0
32 23 John LaMartina
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php
33 26 John LaMartina
 
34 23 John LaMartina
35 24 John LaMartina
h3. - CHIRP does not support my (Model Radio)
36
- Radio Version Not Supported
37 1 Dan Smith
- Failed to communicate with radio: global name 'vendors' is not defined
38 22 John LaMartina
39 24 John LaMartina
These messages are generated if you are running a much older version of CHIRP.   You must upgrade to CHIRP's Latest Daily Build.
40 26 John LaMartina
 
41 23 John LaMartina
42 25 John LaMartina
h3. - Fail Connect with Transceiver (UV5R / UV82 series)
43 23 John LaMartina
44 25 John LaMartina
This message is generated by the Factory Software.  It can occur when:
45
1.  (UV-5R)   Incorrect software version for your firmware release. BFB290 and_prior, and  BFB291_and_later require different software. They are not interchangeable. 
46
2.  Your radio is not turned ON when trying to program.
47 1 Dan Smith
3.  You are receiving a signal while trying to connect.
48 25 John LaMartina
         (tune to a quiet channel or remove antenna.)
49
4.  Your cable is not plugged in all the way.  (See above)
50
5.  This can also occur if other software is running on your PC that may be loading down the CPU.  Close ALL unrelated software and try again.
51 26 John LaMartina
 
52 1 Dan Smith
53 25 John LaMartina
h3. - Store the file name in nullity
54 23 John LaMartina
55 25 John LaMartina
Occurs when trying to save a data file using the Factory Software. 
56 21 John LaMartina
This error occurs when you don't have a valid filename for the file being saved. The filename entered MUST include the .dat suffix. filename.dat
57 26 John LaMartina
 
58 25 John LaMartina
59 19 John LaMartina
h3. - Cable without Echo Loopback 
60 25 John LaMartina
61 19 John LaMartina
This indicates that the RX and TX serial lines have not been connected together with a loopback device (a plug that connects the RX and TX lines of a serial port connector for testing) so the characters being sent on the TX line are not being echoed back on the RX line.
62 26 John LaMartina
 
63 3 John LaMartina
64 27 John LaMartina
h3. - - Driver Issues 
65 15 John LaMartina
66 13 John LaMartina
Many of the inexpensive programming cables are not the bargain they appear. 
67 1 Dan Smith
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