How do I find the Com Port for Chirp? (

[@sar11809redwork]

Dave you are a blessing to all Hams old and new.

[@ohyeawhosurpoppy]

I love it. This is one of those simple things that lack real directions. Like power-poles, so simple but only when an ELMER takes the time to pass it on.

[@agaveboy]

Ahh I hate those types of things!!!!!

[@FBiTOPDOG]

Thanks it finally worked

[@jeffsumpter9631]

I fought all day yesterday trying to figure this out for my Btech UV-50X2! Thanks for the simple fix!

[@bgonzand5]

You can also hit the "windows" key + letter X to bring up the menu list that contains the Device Manager option.

[@walteredwards544]

Thank you. I've always wondered about this. Another question. Does the computer decide which Com Port to use or is it something in the connection cable?

[@davecasler]

the computer

[@3dPrint_and_chill]

I didn't know this, that's very useful.

[@deadbang241]

Using the latest build from chirp , my liexon 898 on the computer pop up says the radio refuses programming mode ?

[@jeffs9302]

If you are using Linux Mint (or probably any Ubuntu distro) and have this problem, you need to turn on your permissions to access the ports. This is how you do it: To have permission to use the serial port of your machine your user account has to be part of the group “dialout”. To check / add this group to your account type “user” into the menu’s search box, select “User and Groups”. After authentication select your username. Check if “dialout” is listed next to “Groups” - if not, click into the list (isn’t it nice?) and select it from the pop up. Done.

[@ChuckYufarley]

Did that but cannot generate the list of ports in Chirp. Any idears?

[@WA4TKG]

I stumbled upon your video and instantly recognized the first HF radio I ever put my hands on at the age of maybe 12; a Hallicrafters S-20-R (you don’t want to know my special phonetics for that). Anyway, is that puppy fully operational and who can I get to rebuild my dad’s radio ? WA4TKG, in Tokyo, at the moment. 73

[@sixpapavictor]

You have to update the software for the cable wether it be RT systems or another brand and it will show up in device manager in commport..right click on that comport and it will tell you what port number you need for chirp

[@davecasler]

Yes, both the programming software and the cable driver software need to be up to date. Note that CHIRP changes every few days.

[@sixpapavictor]

@@davecasler I've only seen one chirp update recent...its working fine with my ft 60r....29repeaters in so far

[@drcsep]

Where do I buy that cable that supports windows 11 or later? I have the same error but the cable that I have is not working doesn’t support windows 11 or later. Thanks for the information

[@williamtrinkle4369]

I was wondering if you have had success using Chrip with Windows 11? I just got a new computer and as I was trying to set up Chirp I got a message that says it is not supported. My error message on the Device Manager says: "PL2303TA Do not support Windows 11 or later, please contact your supplier." I tried to update the drivers and it said I was up to date. So I am wondering if I need a new cable or need to go back to Windows 10. Your thoughts?

[@boydbailey6332]

This is a super sticky problem I am still struggling to solve. If Dave can enlighten on this, he will advance this issue greatly!

[@invalidcactus76]

I don't see any options for mine? Maybe my cable is bad? I'm on windows 11 but I'm not sure if that should matter. It says I have PI2303 chip. From abbree. (Came with my radio)

[@W3DRE]

Thanks Dave!

[@rogerlafrance6355]

Not all computers have the correct driver for the cable. Support pages will provide needed info.

[@maritimedronefilming9511]

my chirp will not work on windows 11

[@robertbeda959]

Great info. Thank you!

[@Xanifur]

Thank you!

[@psychodad11]

Awesome, thanks Dave! N2SCD

[@laparmusik7854]

how about mac?

[@ZaxCal]

God Bless you sir.

[@javierpolendok5mhc]

I have used Chirp and it’s a great programing software

[@ChuckYufarley]

How would one go about this on Ubuntu Linux?

[@tacticool_twitorists]

THANK YOU SO MUCH!

[@esseel7896]

thanks man!

[@HarryHamsterChannel]

The new version of Chirp helps deal with this.

[@schauman1]

Had the same problem!

[@rayh592]

I just do one radio at a time and go through the comm ports until I find the one that works. Not that hard.

[@jkyontz]

Thanks, David. 73 de AA6JY

[@stevebates3573]

Ah be damn! My problem is now solved. Mine was com6 lmao

[@wannabecarguy]

I try every port until I find one that works.

[@ianharling9569]

Cheers Dave. 73.G7HFS/PA3IKH

[@tomnorman5461]

5:34 "Remarkably well hidden"...really? Am I the only viewer that's ever installed a Windows operating system? Device Manager has been part of Windows for over 20 years.

[@crewsgiles9499]

The reality is, that it is not intuitive to go to Device Manager, nor are you likely to intuit the name of your cable as it reports there. Furthermore, it is counter-intuitive that it changes between uses and between reboots. That Device Manager has been around for more than twenty years is part of the problem- it is literally one step above DOS; and, by the way, “plug and play” has been a thing for all of the 21st Century, and connecting my radios to my laptop is the first time (and have been the only times) in this Century that I needed to use Device Manager to identify or configure a port setting.

[@tomnorman5461]

@@crewsgiles9499 Anytime I suspect a hardware issue it's very "intuitive" for me to go directly to the device manager, that's where hardware conflicts present themselves via the yellow exclamation dot. Plug & "Pray" (as we used to call it back in the late 90's) is far from perfect, but it's still better than setting IRQ's & Com Port addresses via jumper pins. My point was (and still is) that Device Manager is not a hidden feature of Windows...so put down your whisky bottle & mind your manners...sometime this "century" (LAUGH!) would be good.

[@crewsgiles9499]

@@tomnorman5461 And yet, here you are watching a video on something you already know how to do-just like me. I was here, hoping knew a way to skip this step by automatically identifying and assigning a port.

[@tomnorman5461]

@@crewsgiles9499 Although I tend to give Mr. Casler a hard-time (mainly over his occasional inaccuracies) I do enjoy watching his channel. I've been installing & configuring Microsoft operating systems (100's of installs) since the early DOS days. I started browsing the Internet when it was just ASCII text only via a Unix Shell account. My point was (and still is) that Device Manager is not a hidden feature of Windows. Nuff-said!