[chirp_users] ... Could not open Com 3
D.J.J. Ring, Jr.
n1ea at arrl.net
Tue Sep 6 03:58:56 PDT 2016
Here is one:
On Tue, Sep 6, 2016 at 6:38 AM, Ken G <kdubya at iinet.net.au> wrote:
> Thank you Jim, also Simon, for the quick reply. Installing the old drivers
> fixed the problem. Is that alternative cable you mentioned readily
> Ken G
> -----Original Message-----
> From: chirp_users-bounces at intrepid.danplanet.com [mailto:
> chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Jim Unroe
> Sent: Tuesday, 6 September 2016 7:01 PM
> To: Discussion of CHIRP
> Subject: Re: [chirp_users] ... Could not open Com 3
> On Tue, Sep 6, 2016 at 3:58 AM, Ken G <kdubya at iinet.net.au> wrote:
> > I haven’t downloaded from my UV-5r for quite some time but today I
> > downloaded the latest version of Chirp, plugged in the cable and I get
> > the following error thrown up by Chirp - “could not open port COM3:
> > [Error 2] The system cannot find the file specified.”
> > .. and this error for the port in Device Manager of Windows 10 ..
> > “This device cannot start. (Code 10)
> It appears that you have a programming cable with a (counterfeit) Prolific
> type chips. When you first got it, you probably had to download, install
> and select the older (2007) Prolific v188.8.131.52 device driver to get it to
> work because Prolific device drivers since 2008 are intentionally
> incompatible with counterfeit Prolific chips.
> You have either plugged the programming cable into a different USB port
> causing it to be configured with the latest Prolific device driver or
> Windows 10 has, on its own, decided to upgrade the device driver back to
> the latest version. In either case, all you have to do is to go back into
> Device Manager and choose the older v184.108.40.206 device driver again.
> Basically you will be repeating steps 6 through 11.
> If you don't want to deal with this again in the future, you can get a
> programming cable with a different brand of USB-to-TTL chip. FTDI chip
> based programming cables are popular for this reason.
> Jim KC9HI
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> This message was sent to D.J.J. Ring, Jr. at n1ea at arrl.net
> To unsubscribe, send an email to chirp_users-unsubscribe@
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users