June 2020 - Users - lists.chirpmyradio.com

[chirp_users] Radioddity gs-5b
by isumano＠me.com 15 Jun '20

15 Jun '20

I would love for Chirp to support this radio!

3 3

[chirp_users] Program a TYT 8600. HELP
by Ruthann Brightwell 09 Jun '20

09 Jun '20

2 1

[chirp_users] TYT TH-UV3R - Channels not available after Upload to Radio
by djdman 2k 09 Jun '20

09 Jun '20

Filed a bug with details @ https://chirp.danplanet.com/issues/7969. Any suggestions would be most appreciated! Cheers, Tom

1 0

[chirp_users] CRT Micron Frequency Issue
by Paul G7BHE 09 Jun '20

09 Jun '20

Hi everyone I have just bought an expanded CRT Micron UV. It has frequency coverage of 136-174 and 400-490. CHIRP is not allowing me to enter frequencies outside of 144-146 & 430-440. Has anyone else encountered this? Is it a CHIRP issue perhaps? I am able to enter the frequencies manually onto the radio and using the OEM software. But frankly that is a really bad program. Thanks Paul G7BHE Sent from my iPhone

4 4

[chirp_users] (no subject)
by Tommy Long 08 Jun '20

08 Jun '20

I like to know if you can copy and paste from something to the radio ?

3 2

[chirp_users] CHMOD ...
by Peter 08 Jun '20

08 Jun '20

Hi all: I am not sure who came up with the brilliant tip of chmod 777 /dev/ttyUSB0 as I have deleted the email suggesting that. So THANK YOU for that suggestion. I was getting frustrated trying to get Chirp on Linux Mint 19.2 to up/download from my new (to me) Icom 2100H. All I got was error messages that the radio had responded inappropriately. Until I did the chmod thing. IT WORKED. So, thanks again. Now I can get going on the next step of a very long march. Peter, VE3BBN -- "There is nothing - absolutely nothing - half so much worth doing as messing about in boats" - Kenneth Grahame in “The Wind in the WIllows”

4 5

[chirp_users] Chirp Linux - Sorting frequencies
by Fernando Pompeo 08 Jun '20

08 Jun '20

2 1

Re: [chirp_users] chirp_users Digest, Vol 138, Issue 5
by Ken Auggie 05 Jun '20

05 Jun '20

> On Fri, Jun 5, 2020 at 12:14 PM Ken Auggie <kbauggie(a)gmail.com> wrote: >> >> CHIRP (as of daily-202000603) is having errors “cloning” a new Baofeng UV-82 High Power using a Baofeng USB cable (both purchased through Amazon). The errors occur on both a 2012 Mac Pro running Mojave 10.14.6 and 2012 MacBook Pro running Catalina 10.15.. >> >> On the Mac Pro, I always get the error “Radio did not respond”. I tried with the built-in driver as well as the driver on the FTDI Chip website (v2.4.2) but same error. >> >> On the MacBook Pro, CHIRP was able to initiate the cloning process but then error’ed out with “Radio refused to send second block” or something to that effect. I then installed the FTDI Chip v2.4.2 driver and now always get the “Radio did not respond” error. >> >> I booted the MacBook Pro to Windows 10, and without installing any drivers (I believe I already had appropriate FTDI drivers for my OBDII cable), CHIRP successfully cloned the UV-82 High Power, so this validates that both the Baofeng UV-82 High Power and the Baofeng USB cable are operating correctly. >> >> The Mac OS X tips have not provided any solution. >> >> So this comes down to, IMO, the CHIRP software. As there appears to be reports of success with using OS X CHIRP, I can only assume it’s specific to the UV-82 (the newer “High Power” version, which seems to be distinct to the original UV-82HP) and/or my 2012 Mac computers (doubtful its a problem with the computers are they are different hardware-wise and OS version-wise). >> >> Can anyone provide any insight, guidance, suggestions that may work for the hardware mentioned? > > Hi Ken, > > I have no issues here with my Baofeng UV-82HP on my MacBook Air > running macOS Catalina. I'm even using a programming cable with a > counterfeit Prolific USB-to-Serial chip. > > What I had to learn when I got my first UV-82 was that the metal pins > of the programming cable stick in the metal rings of the speaker/mic > socket. That "stiction" made me think that it was fully inserted when > in reality it still had a tiny way to go. It took a little wiggle and > a press to get it to snap in the rest of the way. Now that I am aware > that this can happen, I've mastered the technique of getting it fully > inserted the first time so it rarely happens any more. > > Jim KC9HI Thanks for the advice Jim. But I don’t believe this is connection issue for me since under OS X on my laptop, I booted to Windows without touching the cable nor reseating the connections, and CHIRP/Windows 10 worked just fine. Again, I believe this issue may be software related involving the “newer” Baofeng UV-82 High Power (which technically is not the same as the UV-82HP), but only on the OS X version of CHIRP (perhaps OS X driver-related as well).

1 0

[chirp_users] Ubuntu 20.04 chirp not found
by Ronald Scott Moody 05 Jun '20

05 Jun '20

Just added the repo to my Ubuntu MATE 20.04 install, updated apt, but when I run apt-get install chirp-daily I get Unable to locate package chirp-daily.

8 19

[chirp_users] Mac OS X (Mojave and Catalina) CHIRP, Baofeng UV-82 High Power and Baofeng USB cable
by Ken Auggie 05 Jun '20

05 Jun '20

CHIRP (as of daily-202000603) is having errors “cloning” a new Baofeng UV-82 High Power using a Baofeng USB cable (both purchased through Amazon). The errors occur on both a 2012 Mac Pro running Mojave 10.14.6 and 2012 MacBook Pro running Catalina 10.15.. On the Mac Pro, I always get the error “Radio did not respond”. I tried with the built-in driver as well as the driver on the FTDI Chip website (v2.4.2) but same error. On the MacBook Pro, CHIRP was able to initiate the cloning process but then error’ed out with “Radio refused to send second block” or something to that effect. I then installed the FTDI Chip v2.4.2 driver and now always get the “Radio did not respond” error. I booted the MacBook Pro to Windows 10, and without installing any drivers (I believe I already had appropriate FTDI drivers for my OBDII cable), CHIRP successfully cloned the UV-82 High Power, so this validates that both the Baofeng UV-82 High Power and the Baofeng USB cable are operating correctly. The Mac OS X tips have not provided any solution. So this comes down to, IMO, the CHIRP software. As there appears to be reports of success with using OS X CHIRP, I can only assume it’s specific to the UV-82 (the newer “High Power” version, which seems to be distinct to the original UV-82HP) and/or my 2012 Mac computers (doubtful its a problem with the computers are they are different hardware-wise and OS version-wise). Can anyone provide any insight, guidance, suggestions that may work for the hardware mentioned?

2 1