CHIRP - GMRS radio programming software

alfisya

zmaint Better ask the guy directly? Surely he will know more. This is a super niche app.

zmaint

alfisya Yeah it's the same maintainer for both the appimage and the snap. I could open a ticket on his git page.

Axios

zmaint Ya those frs radios worst thing somebody ever thought of.
If I get time will see if I can get it to talk to my yaesu
Currently all my programming dos/windows software is on windows7

zmaint

Axios Much appreciated! I've got some projects to work on, will check in later.

Axios

zmaint you could try the flatpak I found from here
https://chirpmyradio.com/projects/chirp/wiki/Running_Under_Linux
may have more success.

Note installed the flatpak and updated general flatpaks
chirp runs but my radio dead gotta charge..lol

brent

Axios
that's a great idea. in my experience, flatpak has always outperformed the appimage or snap.
in the same breath I wonder if these sandboxed apps are part of the problem.

zmaint

Axios I saw that but the latest Chirp releases do not contain the flatpak file, only the legacy. I've got a newer UV-9r, unsure if the driver would work. Also it's not listed on flathub. Assuming they've abandoned the flatpak version, which is a shame.

Axios

brent I totally agree flatpak or source or repo all I am starting to use.

Axios

zmaint I installed like it showed on the prev post link
Your radio is listed Am using CHIRP legacy-20221217

This is chirp reading my Yaesu ft-60 (Budgie)

Hmm this is neat. any questions just ask

Kinda on side note my adapter is a rt Systems on windows it installs a driver but kinda neat here
it just worked.

Axios

zmaint Your comment did not sink in when I read it earlier now that I had time to read more
from chirp.
Think for the sake of simplicity and not opening a can of worms if the legacy flatpak worked would just
use it.
Where the issue come I think the legacy was python2 the next is current python3.
Will try the other later
Maybe legacy will at least see if you can connect to radio and that part is working
Legacy appears ok for me I checked it with my normal software appears ok for my radio

Nuttin is ever simple is it.

zmaint

Axios Awesome. I will give it a try. I have zero idea on how to set up the radio.

We have 2 radios. Just want to be able to talked (encrypted if possible) between them. That's it. Hoping it's super simple. If you can provide a 5th grader level tutorial I would be eternally grateful🙂

I do have the links to get my GMRS license and call sign, but haven't had the time to wade through the top shelf Geocities experience that the FCC provides.

zmaint

Axios I just tried the flatpak and it's giving me the same error as the appimage did. Honestly at this point I'm not sure if it's not seeing the radio or it just doesn't like this specific model.

Axios

models match and all not familiar with that radio however it starts the download sequence it gives
you following that exactly?
To me its seeing the radio data isnt right for some reason my guess chirp
its weird beofang subs chirps developement think it would work.

If it has a key sequence at start you got follow those exactly!!

I am having trouble on different model myself giving error trying track it down.

zmaint

Axios I found a wiki. https://chirpmyradio.com/projects/chirp/wiki/ChirpOnLinux

Thoughts on this?

Serial port permissions
Note that you may need to add your users who want to use CHIRP to the group that owns the serial ports. This issue is often indicated by an "access denied" error when accessing serial port. First determine the USB port of your device, and then the following command should add your user to the proper group:
Note that "ttyUSB0" should be replaced with the actual device that identifies your connection to the radio and that "$USER" is a system variable that identifies the username of the individual running the command.

sudo usermod -a -G $(stat -c %G /dev/ttyUSB0) $USER
If that made a change, you will then need to log out and back in (or maybe even reboot) for it to take effect.

Axios

zmaint I have usb to 9pin adapter what am testing now has led on it
the flakpak is communicating ok
But the appimage is not even thought I have it selected

zmaint

Axios This is the cable I'm using. It says it supports the UV-9R.

https://www.amazon dot com/dp/B06XHSPJZ4?psc=1&ref=ppx_yo2ov_dt_b_product_details

It looks like it has 3 contacts.

I followed the connect instructions. Turn radio off, connect cable, turn radio on, download. Then it gives that error.

Axios

zmaint yup same here these radios take no key sequence
the yaesu ft-60 had a key sequence
I go through what you said hit ok get error both our radios cant be messed up..lol
Will keep looking

zmaint

Axios I seriously appreciate your help! I'm out for the night. Will be back in the AM. Should be around all day, work from home most days.

Axios

zmaint After abit appears a programming cable issue
My cable uses the same chip as your cable and it doesnt work
But Using the different cable on the ft-60 with the appimage it works fine.

So long story short the appimage works fine.
FTDI FT232R is the chip in the cable that works

Found this after all that work https://chirpmyradio.com/projects/chirp/wiki/CableGuide (explains issue)
Confirms what I was thinking and why mine worked I guess those cables with that chip are hard to find
Bluemax appears to have it (and cheaper than rt systems) (as with anything would ask returns policy if you get one)

Hope I helped and it fixes issue. (from the net seems be more common issue )
Note is the way I see it for good or bad you will have decide what you want to try

zmaint

Axios Ok my genuine Baofeng cable does have that PL-2303 chip in it. I went ahead and ordered an FTDI version from BlueMax49ers. Will update when that arrives.

zmaint

Axios New cable, from the bluemax49er's store as linked in the wiki, has the FTDI chip. Now I get this: