[chirp_users] using chirp for first time.
I can't get it to work. hangs up looking for a com port... ??
Please say which operating system, you are using.
If you're using Windows, usually the problem is your USB cable uses a counterfeit chip and Windows automatically upgrades the driver which then will no longer work for counterfeit chips. Check "Device Manager" to see if you have unrecognized USB serial port devices, if you do "roll back the driver" and it should work at least temporarily. (Cure is to buy a USB to serial port device with FTDI chip set like this one: https://smile.amazon.com/dp/B00HUB0ONK/)
73 David N1EA
On Fri, Jun 4, 2021, 7:12 PM Chuck Barnett charlesfbarnett@gmail.com wrote:
Sorry, yes I'm using Windows 10.
Chuck Barnett 425-530-0328
On Fri, Jun 4, 2021, 11:01 PM D.J.J. Ring, Jr. n1ea@arrl.net wrote:
Thanks! I ordered the cable you suggested. 🙂🙂
Chuck Barnett 425-530-0328
On Fri, Jun 4, 2021, 11:01 PM D.J.J. Ring, Jr. n1ea@arrl.net wrote:
I got the cable, plugged it in and nothing. went to the www.baofengtech.com/download page and grubbed around there awhile and figured out that I was to download CHIRP, which I alread had. Did that anyway. Nothing. 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... 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. 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.
Help?
On Fri, Jun 4, 2021 at 11:01 PM D.J.J. Ring, Jr. n1ea@arrl.net wrote:
On Sun, Jun 6, 2021 at 7:11 PM Chuck Barnett charlesfbarnett@gmail.com wrote:
If you don't already know which chip is in your programming cable, then your best course of action is to download and install all the drivers for the most common USB-to-Serial chips (FTDI, Silicon Labs, WCH and Prolific). They are all available from links on the miklor.com website.
https://www.miklor.com/COM/UV_Drivers.php
Then when you plug your programming cable, the chip will be detected, the correct driver will load and you will be able to access Device Manager to see which chip it is and what COM port has been assigned to the programming cable by the driver. Then the only additional thing will be if the chip is a Prolific type, you will have to install and select the older Prolific v3.2.0.0 driver.
Jim KC9HI
Jim KC9HI
Thanks!
Somehow, I'm in!
I'll not go into all the issues and frustrations the lack of knowledge/information raised for me in this process. Suffice it to say that 'simple instructions' leave a lot of stuff out which is vital for the non-tech
Chuck K7CFB
On Sun, Jun 6, 2021 at 4:23 PM Jim Unroe rock.unroe@gmail.com wrote:
On 6 Jun 2021 at 16:11, Chuck Barnett wrote:
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.
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
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@frontier.com wrote:
On Sun, Jun 6, 2021 at 8:29 PM Chuck Barnett charlesfbarnett@gmail.com wrote:
This is what it looks like for my Prolific type chip based programming cable. The entry for an FTDI chip should be similar. If you have more than one serial device, the best way to find the one for your cable would be to open Device Manager first, then plug in the programming cable so you can watch for the new entry that appears.
Jim KC9HI
I have 3 USB ports, one of which holds my mouse receiver. You can see from the screenshot that nothing shows up; there isn't even a category "Ports" displayed. However, exactly as predicted, when I plugged in the cable, "USB Serial Port (COM3)" displays. That's good to know, but I doubt I'll remember for the next 10 yrs until something like this occurs again.
When I got my Tech and then General licenses this spring, I didn't realize that I had to have some sort of certificate in Windows as well.
Thanks, again, folks. I'll move on to make room for somebody who needs help with a *real* problem.
On Sun, Jun 6, 2021 at 5:35 PM Jim Unroe rock.unroe@gmail.com wrote:
On 6 Jun 2021 at 17:27, Chuck Barnett wrote:
This is the cable that D.J.J.Ring Jr. advised me to get in place of the other.
Well, if D.J.J. Ring told you that, you can rely completely on practically anything he tells you. I have known him since shortly after there was hair, and sometime after there was dirt. He is a very good fellow very knowledgeable and very reliable. He is also a veteran, which, in my opinion, gives him more credence, yet.
Yes. That is the good one.
Hmmm....what version of WinDOZE (heh heh!) are you using?
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
Well then, COM3 it must be.
As long as you got it working, I would guess there is no more need for my comments. Carry on.
vy 73 for now,
Ken W7EKB
Here are a few links that may assist:
Error Messages: Miklor.com/COM/UV_ErrorMess.php Drivers: Miklor.com/COM/UV_Drivers.php
Stay safe and healthy.
John K3NXU
www.Miklor.com
From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Chuck Barnett Sent: Friday, June 4, 2021 7:10 PM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] using chirp for first time.
I can't get it to work. hangs up looking for a com port... ??
Oops, bad links. J
From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of John La Sent: Saturday, June 5, 2021 11:25 AM To: 'Discussion of CHIRP' Subject: Re: [chirp_users] using chirp for first time.
Here are a few links that may assist:
Error Messages: www.Miklor.com/COM/UV_ErrorMess.php
Drivers: www.Miklor.com/COM/UV_Drivers.php
Stay safe and healthy.
John K3NXU
www.Miklor.com
From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Chuck Barnett Sent: Friday, June 4, 2021 7:10 PM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] using chirp for first time.
I can't get it to work. hangs up looking for a com port... ??
participants (6)
-
Chuck Barnett -
D.J.J. Ring, Jr. -
Jim Unroe -
Joe Pizzi -
John La -
Kenneth G. Gordon