CHIRP

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

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.

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

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]

Is it a Prolific chip? Check the DeviceManager, it will tell you; perhaps the USB-to-serial chip is another brand.

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

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