[chirp_users] using chirp for first time.

Chuck Barnett charlesfbarnett at gmail.com
Sun Jun 6 17:27:08 PDT 2021

Thanks, Kenneth, for your time and help.  Jim's instructions were enough to
get me in.

This is the cable that D.J.J.Ring Jr. advised me to get in place of the
other.  Amazon had it for $22.xx.  Until I looked at the listing more
closely, just now, I had no idea what chip was in it.  Now I see that the
name contains FTDI.

"Once you have the correct driver loaded, plug your cable into a USB port,
in Device Manager,
look under Ports (Comm and LPT) to find which port Windows has assigned to
your cable."

I've looked in Device Manager several times in this process and have never
seen Ports...
This last time, the only one that showed up when I clicked on the Find
Radio or Download from Radio command was COM3, and no error messages.  Then
it started to clone

Thanks, again!

Chuck K7CFB

On Sun, Jun 6, 2021 at 5:00 PM Kenneth G. Gordon <kgordon2006 at frontier.com>

> On 6 Jun 2021 at 16:11, Chuck Barnett wrote:
> > Instructions ask and answer the question "My computer did not
> automatically install the driver..."
> > the Answer was to go to http://www.ftdichip.com/Drivers/VCP.htm and
> download the latest FTDI
> > driver...
> That would ONLY be true IFF your cable contained the FTDI chip.
> Most cheap cables (under $20.00) usually contain the Prolific (trade name)
> chip, or a
> Chinese rip-off of it, and NOT the FTDI chip. Rarely, the cable could
> contain some other
> make of interface chip, as Jim Unroe mentioned
> If it contains the Prolific chip, you must download and install an older
> version of the driver for
> that chip when you are using Windows because the driver that Windows
> automatically loads
> for it won't work.
> > I found that search quite confusing.  finally downloaded something
> called CH341ER.ZIP and
> > extracted and clicked on 64 bit setup and got a pop up which I couldn't
> manipulate.
> Yes. Windows does that. But there is a fairly simple way around that.
> > Opened Device manager and still cannot find com ports. Tho I see under
> "Other devices",
> > something called 'FT232R USB UART.  Didn't get anywhere with that.
> >
> > This isn't going well.
> Yes. We can see that. You have to be somewhat more familiar with computer
> hardware and
> software, and with the internal workings of Windows than you presently are
> in order to do
> what you wish to do.
> Following Jim Unroe's advice would be an EXCELLENT place to start.
> Once you have the correct driver loaded, plug your cable into a USB port,
> in Device Manager,
> look under Ports (Comm and LPT) to find which port Windows has assigned to
> your cable.
> Click on the > symbol to the far left of the Ports entry to see your
> cable.
> If you can't easily determine which USB port Windows assigned to your
> cable, watch that
> Ports window, then unplug your cable, then look again at Ports. One in the
> list shown will
> have disappeared. That should tell you which one it is. Or you can plug
> your cable back in
> and look to see which one suddenly appears.
> Good luck.
> Ken W7EKB
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Chuck Barnett at charlesfbarnett at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com

*Chuck Barnett*
(425) 530-0328
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20210606/d961dc62/attachment.html 

More information about the chirp_users mailing list