Menu
When inserted into the USB port, Windows will automatically download the latest. Some of these cables may even have the Baofeng name printed on them. Programming your Baofeng GT-3 with the cable on WIndows 10: I could. Software to work and ran into.
.Baofeng UV5R / UV82 (and variants)This page provides general tips and troubleshooting for the Baofeng UV-5R, UV-82, and related radios (See ). 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 Common Errors - 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 ModeThis 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 - Error has Occurred, Could not open Com Port xEach 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 8Error occurs if Prolific driver version is higher than v3.2.0.0You need to - CHIRP does not support my (Model Radio)- Radio Version Not Supported- Failed to communicate with radio: global name 'vendors' is not definedThese 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 andprior, and BFB291andlater 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. Store the file name in nullityOccurs 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 LoopbackThis 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.Driver IssuesMany 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.
The final definitive guide for fixing the failure of the (PL2303) Prolific USB-to-Serial Comm Port driver in Windows 10, step by step:First, install the latest driver for the PL2303 USB-to-Serial adapter from Prolific's website; thenDownload older driver that is compatible with Windows 10:1. Download the core driver files (.cab.sys.inf) for version 3.3.2.102 (32bit and 64bit files):Uncompress into a directory.Install older driver to fix error/failure:1. Open Device Manager and right click on the failed Prolific USB-to-Serial Comm Port device;2. Select 'Update Driver software.' Select 'Browse my computer for driver software';4.
Select 'Let me pick from a list of device drivers on my computer' (other driver versions visible here);5. Select 'Have Disk.' , and then browse or paste the path to the 'ProlificWin8x64x86' directory;6. Click Next to install;7. Close.Stop Windows from loading the latest driver and overwriting the fix:1. Open 'Device Manager';2.
Locate the adapter and check if the Exclamation mark is showing for the Code 10 error;If the error doesn't show, remove and re-insert the adapter from the USB port until it does (this will load the latest version);3. Right-Click on the failed device and Select 'Uninstall';4. Complete the uninstall process (delete installed files!) and remove and re-insert the adapter from the USB port. This will remove the latest version driver files but leave the compatible version in place;5. The failed driver will not load.Please let me know if the steps here need modification due to error or changes in the OS.
This worked for the Anniversary version of Windows 10. Cheers!For a Terminal I use Token2Shell/MD, which is a Universal Windows Platform application and can be found in the Windows Store. It supports Serial, Bluetooth and SSH connections and is awesome. No more Putty and no need for SecureCRT. It is by far the bestTerminal/SSH product for Windows 10 that I have found.Check it out here.