Bug #10441
closedUnable to clone UV5R
0%
Description
I am attempting to update the programming on my UV5R using a Baofeng-supplied cable. I have used the cable with CHIRP successfully several previous times, but have been unable to make it work now.
Have tried both CHIRP-next and -legacy downloads.
Using -next with COM4, I get the following error: "could not open port 'COM4': OSError(22. The semaphore timeout period has expired.', None,121'"
Switching to COM5: "could not open port 'COM5': PermissionError(13, 'Access is denied.', None,5)
I also have an option that reads "PL2303HXA PHASED OUT SINCE 2012. PLEASE CONTACT YOUR SUPPLIER. (COM7). Choosing this option doesn't work either.
I've included the debug.log ¶
I also attempted using CHIRP-legacy, which defaults to COM5 (the only listed option.) No error message, but the "CLONING PROGRESS" never starts.
--
As I said, I have used this cable and previous CHIRP versions successfully. I am using a Lenovo ThinkPad laptop running Windows 10.
--
Debug.log:
[2023-03-13 11:50:15,423] chirp.logger - DEBUG: CHIRP next-20230313 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-03-13 11:50:16,643] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230313 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-03-13 11:50:16,644] chirp.wxui - DEBUG: System locale: en_US (276)
[2023-03-13 11:50:16,690] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (de,el,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2023-03-13 11:50:16,710] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-03-13 11:50:17,277] chirp.wxui.main - INFO: Server reports next-20230313 is latest
[2023-03-13 11:50:27,216] chirp.wxui.clone - DEBUG: Using port 'COM7'
[2023-03-13 11:50:27,216] chirp.wxui.clone - DEBUG: Selected
[2023-03-13 11:50:27,233] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-03-13 11:50:28,525] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-03-13 11:50:34,029] chirp.wxui.clone - DEBUG: Using port 'COM5'
[2023-03-13 11:50:34,029] chirp.wxui.clone - DEBUG: Selected
[2023-03-13 11:50:34,045] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-03-13 11:50:35,147] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-03-13 11:50:40,354] chirp.wxui.clone - DEBUG: Using port 'COM4'
[2023-03-13 11:50:40,355] chirp.wxui.clone - DEBUG: Selected
[2023-03-13 11:50:40,370] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-03-13 11:50:41,673] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
Updated by Jim Unroe over 1 year ago
- Status changed from New to Not a bug
CHIRP (or any other programming software) can't work because you don't have a working connection between your radio and computer. The reason it is not working is because you do not have device driver installed that is compatible with the USB-to-Serial chip (Prolific PL2303HXA) in your programming cable.
The Prolific company has considered the PL2303HXA chip EOL (end of life) for over 10 years and for this reason has removed support for it from the driver that they supply to Microsoft to be used in Windows. So when this chip is detected, the driver installed by Windows will not work as confirmed by the "PL2303HXA PHASED OUT SINCE 2012. PLEASE CONTACT YOUR SUPPLIER." notification supplied by the device driver.
There are a variety of workarounds available. Here are 3...
- Purchase a programming cable that doesn't use the Prolific type chip. Programming cables with the FTDI chip are recommended because the listing will usually state when the FTDI chip is used. There are also Silicon Labs and WCH chips available but they aren't always mentioned in the listing and you run the risk of getting another Prolific chip based programming cable. An example of an FTDI chip based programming cable would be the PC03 FTDI programming cable offered by Baofeng Tech (the radio dealer in the USA). https://baofengtech.com/product/pc-03-programming-cable/ If a listing doesn't mention FTDI, then move on and keep looking.
- Swap out the USB module of the programming cable that you have to one that doesn't use a Prolific type chip. I actually built a programming cable from scratch using one of these modules. It can be seen in this project detailed on the Miklor radio information website. https://www.miklor.com/COM/UV_ProgrCable.php
- Download, install and select a Prolific driver that was available before support for the PL2303HXA driver was dropped. The Prolific v3.2.0.0 driver is recommended for Windows Vista, 7, 8.x, 10 and 11. I have been using it here for over 10 years. This can be the simplest workaround because it doesn't require buying anything or soldering anything, but some people have trouble following the steps to get it installed and selected. A link for downloading the driver and instructions for installing and selecting it are also on the Miklor website. https://www.miklor.com/COM/UV_Drivers.php
Once you get your programming cable issues resolved, CHIRP should work.
Jim KC9HI