Bug #9001
closedcould not open com port
0%
Description
using a Icom Ic-80AD
Windows 10
getting message could not open com port ?
Files
.png){kind=link}
%20Properties.png){kind=link}
Updated by Jim Unroe about 4 years ago
I would suspect that you are either choosing the wrong COM port or you do not have a device driver installed that is compatible with the USB-to-Serial chip in your programming cable. Visit this "Drivers and USB Cables":http://www.miklor.com/COM/UV_Drivers.php page for links to the most common drivers and how to use Device Manager to determine which driver is installed and which COM port to choose.
Jim KC9HI
Updated by yves girard about 4 years ago
Thank you Jim, I am seeing the com port 5 .
I am getting the error on the device saying: Peripheral won't start error code 10.
Not sure what to do next.
Thank you
Yves.
Updated by Jim Unroe about 4 years ago
yves girard wrote:
Thank you Jim, I am seeing the com port 5 .
I am getting the error on the device saying: Peripheral won't start error code 10.Not sure what to do next.
Thank you
Yves.
Which is a pretty good indication that your programming cable has a counterfeit Prolific chip it in and the installed Prolific driver is refusing to function with it. To make your programming cable work, you must download, install and select the older Prolific v3.2.0.0 driver as shown in the link I provided above.
Jim KC9HI
Updated by yves girard about 4 years ago
Jim ,
I did install prolific v3.2.0.0 .
I am still seeing a yellow triangle on my USB-to-serial comm port (com 5) in windows.
when I run chirp a get the following message:
could not open port com 5: [Error 2]
Updated by Bernhard Hailer about 4 years ago
Is it a Prolific chip? Check the DeviceManager, it will tell you; perhaps the USB-to-serial chip is another brand.
Updated by Jim Unroe about 4 years ago
- File 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png added
- File 2021-01-28 08_18_43-Device Manager.png 2021-01-28 08_18_43-Device Manager.png added
- File 2021-01-28 08_20_06-Prolific USB-to-Serial Comm Port (COM3) Properties.png 2021-01-28 08_20_06-Prolific USB-to-Serial Comm Port (COM3) Properties.png added
yves girard wrote:
Jim ,
I did install prolific v3.2.0.0 .
I am still seeing a yellow triangle on my USB-to-serial comm port (com 5) in windows.when I run chirp a get the following message:
could not open port com 5: [Error 2]
You have to do more than install the older driver, you must choose it instead of any newer driver that is present in Windows.
Jim KC9HI
Updated by yves girard about 4 years ago
Hello Jim , I have attached 2 files (they are the same) one in PDF and the other in excel.
this is to show you my device manager info.
I am still getting error code 10.
Thanks
Updated by yves girard about 4 years ago
Updated by Jim Unroe about 4 years ago
yves girard wrote:
Hello Jim , I have attached 2 files (they are the same) one in PDF and the other in excel.
this is to show you my device manager info.
I am still getting error code 10.
Thanks
You have to double-click the entry in the Device Manager tree (second picture) and then click the "Driver" tab (third picture) to reveal the "Driver Version". A screen capture of that would be helpful.
Jim KC9HI
Updated by yves girard about 4 years ago
- File USB_Serial_80AD.png USB_Serial_80AD.png added
Hello Jim,
I am using the cable OPC-478UC from Icom.
I have attached the picture from my driver as requested.
Thanks
Yves VE2DTJ
Updated by Jim Unroe about 4 years ago
yves girard wrote:
Hello Jim,
I am using the cable OPC-478UC from Icom.
I have attached the picture from my driver as requested.Thanks
Yves VE2DTJ
Ok. So apparently your programming cable uses an Icom driver. It is and issue between the programming cable, the driver and Windows. Once you get that solved, then CHIRP will most likely work.
Jim
Updated by Bernhard Hailer almost 4 years ago
- Model affected changed from (All models) to Icom IC-80AD
Yves, have you been able to resolve this?
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Incomplete to Closed
No more traffic on this ticket.