May 2020 - Users - lists.chirpmyradio.com

[chirp_users] New Daily Build
by Build System 16 May '20

16 May '20

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20200516 A list of the changes included in this build (since the last daily) follows: Changes for Build #621 [Jim Unroe <rock.unroe(a)gmail.com>] [PX-777] Update Tuning Steps List for Puxing PX-777 This patch updates rf.valid_tuning_steps for the Puxing PX-777 to include 6.25 KHz and 12.5 KHz. #7849

1 0

Re: [chirp_users] chirp_users Digest, Vol 137, Issue 13
by Gary Nobody 15 May '20

15 May '20

adding frequencies with chirp ________________________________ From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> Sent: Friday, May 15, 2020 2:00 PM To: chirp_users(a)intrepid.danplanet.com <chirp_users(a)intrepid.danplanet.com> Subject: chirp_users Digest, Vol 137, Issue 13 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Re: chirp_users Digest, Vol 137, Issue 12 (IT1 Stuart Blake Tener, USNR) 2. Re: Yaesu FT-8500 (W Paul Mills) 3. Re: Yaesu FT-8500 (Nigel A. Gunn G8IFF/W8IFF) 4. Re: Yaesu FT-8500 (Nigel A. Gunn G8IFF/W8IFF) ---------------------------------------------------------------------- Message: 1 Date: Thu, 14 May 2020 15:31:13 -0400 From: "IT1 Stuart Blake Tener, USNR" <stuart.tener(a)bh90210.net> Subject: Re: [chirp_users] chirp_users Digest, Vol 137, Issue 12 To: chirp_users(a)intrepid.danplanet.com Message-ID: <20200514153113.Horde.-Zn2TpRTN4d2IcjKv7IKjge(a)mgtmail.com> Content-Type: text/plain; charset="utf-8" Nolan, Indeed you might be thinking that you are reminding people of some obvious piece of wisdom to conduct a search for old articles, but indeed this is a fools errand (unless you are suggesting such messages were very recent in the last 30 to 45 days, which I did not get the impression you were). Why you ask? Python is still under heavy development and unless these older messages specifically substantiate what the exact version of Python existed at the time the messages were written and what specific Python version they were referring to, their content and meaning may be entirely inapplicable now as perhaps the technical concerns at issue at the time may well have been overcome my changes to the Python language or been amended in the current instantiation of the Chirp source code base. In either event, we would not gain such insights from old messages. Thus, obviously asking what the issues are now is a very different question from "what were the issues then?", a question I did not ask and therefore had no need to research the answer for. Secondly, you can't agree with me that "Python 3 would be nice to have", because I did not say that. I meant to assert in the most compelling manner that I could articulate that the idea of moving to Python3 is an imperative and to not do so terribly disadvantages users and retards the security of a system they are expected to continue to keep Python2 running upon. Let me clear here, I appreciate all the hard work that Dan, et alia, have put into Chirp and mean in no way to diminish the excellence of that work or to suggest any lack of appreciation. Moreover, if the argument is "We can't move to Python2 because its a part time project and nobody has time." I understand and accept that fully. However, that in no way changes the fact that distributing software in a now virtually unsupported language instigates a very high risk for the users of that software in such a case. Moving to Python3 is something that must happen, just as many programs written for Amateur Radio are no longer used because they ran on TRS-80s and Apple IIs, and we don't use that technology anymore. Chirp will eventually move in such a direction if it is not ported to Python3 soon (or some other secure language) as people that care about the security posture of their systems will be loath to remain to keep an environment running that is not longer be actively patched with security patches and having bugs remediated there within. 73, Stuart, N3GWG ?

1 0

[chirp_users] Yaesu FT-8500
by Claes Harde 15 May '20

15 May '20

Hello, I don’t see my radio listed. Is there another “close enough” that I could use? Thanks, Max

3 3

Re: [chirp_users] chirp_users Digest, Vol 137, Issue 12
by IT1 Stuart Blake Tener, USNR 14 May '20

14 May '20

Nolan, Indeed you might be thinking that you are reminding people of some obvious piece of wisdom to conduct a search for old articles, but indeed this is a fools errand (unless you are suggesting such messages were very recent in the last 30 to 45 days, which I did not get the impression you were). Why you ask? Python is still under heavy development and unless these older messages specifically substantiate what the exact version of Python existed at the time the messages were written and what specific Python version they were referring to, their content and meaning may be entirely inapplicable now as perhaps the technical concerns at issue at the time may well have been overcome my changes to the Python language or been amended in the current instantiation of the Chirp source code base. In either event, we would not gain such insights from old messages. Thus, obviously asking what the issues are now is a very different question from "what were the issues then?", a question I did not ask and therefore had no need to research the answer for. Secondly, you can't agree with me that "Python 3 would be nice to have", because I did not say that. I meant to assert in the most compelling manner that I could articulate that the idea of moving to Python3 is an imperative and to not do so terribly disadvantages users and retards the security of a system they are expected to continue to keep Python2 running upon. Let me clear here, I appreciate all the hard work that Dan, et alia, have put into Chirp and mean in no way to diminish the excellence of that work or to suggest any lack of appreciation. Moreover, if the argument is "We can't move to Python2 because its a part time project and nobody has time." I understand and accept that fully. However, that in no way changes the fact that distributing software in a now virtually unsupported language instigates a very high risk for the users of that software in such a case. Moving to Python3 is something that must happen, just as many programs written for Amateur Radio are no longer used because they ran on TRS-80s and Apple IIs, and we don't use that technology anymore. Chirp will eventually move in such a direction if it is not ported to Python3 soon (or some other secure language) as people that care about the security posture of their systems will be loath to remain to keep an environment running that is not longer be actively patched with security patches and having bugs remediated there within. 73, Stuart, N3GWG

1 0

[chirp_users] Upload stalls with Mac OS10.14 Mojave
by glenmac 13 May '20

13 May '20

I posted this last month and tried some new things. but, still stuck. Previously, used a 2018 15 inch MacBook Pro with OS10.14.6 (Mojave) that required a Kensington USB-C dock for the IOGear USB-Serial adapter. Uploading to an iCom 2200H stalled, forcing a reboot to get Chirp running again. Resurrected a mid-2012 MBP with Mojave, this one has 'real' USB ports, eliminating the Kensington dock. Installed the IOGear driver and KK7DS Python runtime. About Chirp: Chirp daily-20200430, GTK 2.24.32, PYGTK 2.24, Python 2.27,10. Kextstat: com.ATEN.driver.PL2303 (1.6.0) Download from Radio: dev/cu.UC-232AC/iCom/IC-2200H Still stalls when I immediately attempt to upload back to the 2200H, which displays “CL IN”. Force Quit on Chirp leaves it unable to re-open until I reboot. the IOGear driver and convertor worked under Win 7 with the iCom software. Any suggestions? Other recommended USB-serial converters? TIA, Glen KE7HIM

1 0

[chirp_users] chirp flatpak (In need of a few brave souls)
by Richard Shaw 13 May '20

13 May '20

Well thanks to the help and pointers here I was able to navigate the truly atrocious documentation for flatpaks and was able to create a bundle. I need a few brave souls to test: https://hobbes1069.fedorapeople.org/chirp-20200430.flatpak I put the version in the name, so be careful, if I update it it, you could install more than one version. I still have yet to learn how you update flatpak packages. I went through and did a "cleanup" of a lot of files we don't actually need. The original version was ~140MB... It should be practical to get it listed on flathub. The archives are called "daily" but really it's whenever something significant has been committed and the date is the version. Let me know if it works fine or needs some fixes. Thanks, Richard KF5OIM

7 15

Re: [chirp_users] Using Chirp On A Mac
by IT1 Stuart Blake Tener, USNR 13 May '20

13 May '20

Tycen, You state: "You can use Chirp on Mac if you are pre-Catalina (due to python2/python3)." I am very confused by the comments you make here regarding the usage of Chirp within a macOS environment that is based on Catalina. I just upgraded to Catalina and would wonder why Chirp is not capable of running there? I am dumbfounded by what you could possibly be implying by this (that no steps have been taken to migrate Chirp to Python3). Python2's deprecation was enunciated in 2008 and scheduled for 2015, it is 2020 now and we are just getting to it being taken out of service. I am not familiar with Chirp's internal programming constraints, but I cannot even begin to imagine that over all these years the forthcoming end of support for Python2 was outright ignored by Dan. I've met Dan several times, he is an extremely bright individual, what you are implying makes absolutely no sense. If this is true, then within one year Mac users will done with Chirp since by then (for security reasons) we will have all upgraded to Catalina. Moreover, Brew does provide Python2 I believe (granted, I will not run it after this year, also for security reasons absent future updates). But, can you please disambiguate as to what you mean by "due to Python2/Python3"? 73, Stuart, N3GWG Very Respectfully, Stuart B. Tener Computer Scientist / FCC Licensed Radio Operator -- IT1 Stuart Blake Tener, USNR, N3GWG (Extra), MROP Las Vegas, NV / Philadelphia, PA / Beverly Hills, CA (310) 358-0202 Mobile Phone (215) 338-6005 Google Voice

2 1

[chirp_users] Using Chirp On A Mac
by Glenn K0LNY 13 May '20

13 May '20

Hi, Someone just asked me about using Chirp on a Mac, and if it can be used in the Mac CLI. Thanks. Glenn

2 1

[chirp_users] Using Chirp to program the Yaesu FT-50r
by Richard K Parrish 12 May '20

12 May '20

Trying to Program a Yaesu FT-50r. I follow the instructions to hold the mon key and press the PTT 3 times. Unit goes into Clone mode, Send, then gets a CERR Any suggestions? Richard K. Parrish, NREMT-P, PC Course Administrator, Woodstock FD, Com 5 35 Park Drive Woodstock, NY 12498 845-679-6504 Ritchkp(a)gmail.com

3 6

[chirp_users] How to read Kenwood TH-D7?
by Ernesto Xload 12 May '20

12 May '20

Hello, How can I read Kenwood my TH-D7 fron CHIRP? Best regards

2 3