 Common Error Messages |
||
|
||
|
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 (see Drivers Page) |
||
|
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. (Other possibilities are listed below) |
||
  Graphic by Mike KF5DEY GT3
 Click to Enlarge Graphic by Lukas Hess |
||
| Many programming cables supplied with the radios are not manufactured by Baofeng, even if they have Baofeng stamped on the USB connector.
If you are still having issues after trimming the cable, you may want to refer to the
Drivers and Software sections of
Miklor.com Other possibilities have also been identified: - CHIRP - Message appears if selecting the wrong model radio. i.e. Selecting Baofeng if the radio is actually a BTech. - Radio is not turned ON while downloading. - The device driver is not compatible with the programming cable. - Programming cable is defective. - Wrong COM port is selected. NOTE: The driver does Not follow the cable. If a backdated driver is loaded to a particular COM port, the cable must continue to use that physical USB slot. If the cable is plugged into a different physical slot, the backdated driver must be loaded again for that USB port. |
||
|
Error has Occurred, Could not open Com Port x (see Drivers Page) |
||
|
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. |
||
|
Run-time error 8020: Error reading from comm device. Cannot Start (Code 10) in Windows 8 (see Drivers Page) |
||
|
Error occurs if Prolific
driver version is higher than v3.2.0.0 Downgrade to v3.2.0.0 and the error should go away. |
||
|
CHIRP does not support my (Model Radio) Radio Version Not Supported Failed to communicate with radio: global name 'vendors' is not defined (see CHIRP Page) |
||
| These messages are generated if you are running a much older version of CHIRP. You must upgrade to CHIRP's Latest Daily Build. | ||
|
Fail Connect with Transceiver (UV5R / UV82 series) |
||
|
This message is generated by the Factory Software.
It can occur when: 1. (UV-5R) Incorrect software version for your firmware release. BFB290_and_prior and BFB291_and_later require different software. They are not interchangeable. 2. Your radio is not turned ON when trying to program. 3. You are receiving a signal while trying to connect. (tune to a quiet channel or remove antenna.) 4. Your cable is not plugged in all the way. (See above) 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. |
||
|
Could not open port com xx (2, 'CreateFile, 'The system cannot find the file specified.') |
||
| This message is generated by CHIRP. The USB Com Port entered is not correct. Plug the programming cable into the desired USB port and run: Find Com Port (Windows). Enter the com port shown into the CHIRP software. |
||
|
Store the file name in nullity |
||
|
Occurs when trying to save a data file using the Factory
Software. 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 |
||
|
Cable without Echo Loopback |
||
| 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. | ||
|
Radio NAK'd block at address 0xF010 (CHIRP / UVB5 / UVB6) |
||
|
Some more recent UV-B5 / B6 radios ship with only 27 menu options as compared to the 29.
Menu 24 (TX-AB) and Menu 29 (Companding) were eliminated. When using CHIRP, the above message can be ignored. All data has transferred properly. |
||
|
Application cannot run because application configuration is incorrect |
||
This message is generated by Windows XP. The following needs to be loaded to your PC.
|
|
|
