Project

General

Profile

BaofengUV5R » History » Version 24

John LaMartina, 06/20/2016 03:29 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 8 John LaMartina
9 18 John LaMartina
h3. - Radio Did Not Respond
10 17 John LaMartina
- Unable to Program
11
- Radio did Not Ack Programming Mode
12
- Radio did Not Ack first command
13
- Radio Radio refused to enter Programming Mode 
14 1 Dan Smith
15 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.
16 3 John LaMartina
17 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. 
18 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
19
20
21
h3. - Error has Occurred, Could not open Com Port x
22
23
Each USB slot is connected to a separate com port to avoid conflict. Changing your USB slot will change the com port number.
24
After making this change, you must unplug and replug your USB programming cable for the new com port number to be effective.
25 1 Dan Smith
26
27 23 John LaMartina
h3. - Run-time error 8020: Error reading from comm device.
28
- Cannot Start (Code 10) in Windows 8 
29 1 Dan Smith
30 23 John LaMartina
Error occurs if Prolific driver version is higher than v3.2.0.0
31
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php
32
33
34 24 John LaMartina
h3. - CHIRP does not support my (Model Radio)
35
- Radio Version Not Supported
36
- Failed to communicate with radio: global name 'vendors' is not defined
37 22 John LaMartina
38 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.
39 23 John LaMartina
40
41
42
43
h3. - Run-time error 8020: Error reading from comm device.
44
- Cannot Start (Code 10) in Windows 8 
45
46
Error occurs if Prolific driver version is higher than v3.2.0.0
47
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php
48
49
50
51
52
h3. - Run-time error 8020: Error reading from comm device.
53
- Cannot Start (Code 10) in Windows 8 
54
55
Error occurs if Prolific driver version is higher than v3.2.0.0
56
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php
57
58
59
60
61
h3. - Run-time error 8020: Error reading from comm device.
62
- Cannot Start (Code 10) in Windows 8 
63
64
Error occurs if Prolific driver version is higher than v3.2.0.0
65
You need to "Downgrade to v3.2.0.0":http://www.miklor.com/COM/UV_Drivers.php
66
67 21 John LaMartina
68
69
70 19 John LaMartina
71
72
73 8 John LaMartina
74 3 John LaMartina
h3. Driver Issues 
75 1 Dan Smith
76 15 John LaMartina
Many of the inexpensive programming cables are not the bargain they appear. 
77 13 John LaMartina
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