- Users - lists.chirpmyradio.com

[chirp_users] No USB Port Error
by Glenn K0LNY 22 May '20

22 May '20

Hi, I just got a new used radio, a Kenwood TH-F6. So I plugged in the radio using a non-Kenwood cable and I went into "radio" and download from radio and selected my radio model and USB0 and I get the message: error no 2 cannot open tty/usb0 error cannot locate tty/USB0. or something similar. I have used this cable and that Ubuntu with Chirp in the past for my other radios, and other than different brands of radios, I have always been able to do this. I know a guy who has done this to this model using the Baofeng cable using a different software in Windows, not the Kenwood software, but one that they purchased. I don't recall the name, but I think it starts with an R. At any rate, I'd sooner buy a Kenwood cable than that other software and keep using Chirp. Hopefully I didn't get it mixed up with the Radioddity cable. I thought I had the right cable with the Radioddity when I sent it off. I don't know if they put the name of the associated radio on the cables, since I'm Blind. But any who, would this be an error for the wrong cable? Thanks. Glenn

4 7

Re: [chirp_users] chirp_users Digest, Vol 137, Issue 18
by tommy 22 May '20

22 May '20

4 3

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

21 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-20200521 A list of the changes included in this build (since the last daily) follows: Changes for Build #622 [Jaroslav Škarvada <jskarvad(a)redhat.com>] Add support for IC-E90/IC-T90 Fixes #579 [Joe Milbourn <joe(a)milbourn.org.uk>] [AnyTone778] Initial, read and write, support for AnyTone 778UV, partially closes #4901 Probably also supports similar looking things, like the retevis RT95. Supports frequency, offset, name, power, duplex, CTCSS, and DTCS. Doesn't support any settings.

1 0

Re: [chirp_users] chirp_users Digest, Vol 137, Issue 16
by Dave B 20 May '20

20 May '20

I think you need to visit the main Chirp website, and get the PPA details, then add that to your system. https://launchpad.net/~dansmith/+archive/ubuntu/chirp-snapshots Chirp Daily, is not distributed by Ubuntu, but by their own PPA. 73. Dave G0WBX. On 20/05/2020 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Subject: [chirp_users] Ubuntu FF with PPA: Unable to locate package > chirp-daily? -- Created on and sent from a Unix like PC running and using free and open source software:

3 2

[chirp_users] Pyenv and CHIRP
by D.J.J. Ring, Jr. 20 May '20

20 May '20

Hi CHIRPers, I was going to submit something about pyenv separately but I mentioned it in a post about Ubuntu current. The application pyenv which allows using specific versions with certain programs. I'm trying to get that very program working to allow me to use python 3.7 on a distro SLINT (Slackware) that only has python 2.7. I've gotten pyenv working nicely, but I'm having problems installing slpkg a new unofficial package installer. Haven't mastered yet, but I'm stubborn. I'm sure the devs know other means to keep CHIRP working but I just heard of this, it gives a particular program the python environment it needs and a shortcut with environmental settings can be put in ,profile file. 73 David N1EA

1 0

[chirp_users] Baofeng T-57
by Richard Setford 20 May '20

20 May '20

Hi, I'm running Linux Mint 19.10 with CHIRP daily-20200516 and it would appear that my Baofeng T-57 isn't supported by CHIRP. Can this radio be added please or is there a workaround? Thanks, Rich

2 1

[chirp_users] Using Python 2 and Python 3 in Linux
by D.J.J. Ring, Jr. 18 May '20

18 May '20

Various versions of Python can be used in Linux. These instructions were for Slackware, but I suppose they work well in other distributions. Install pyenv as root: 1. cd /root 2. curl -L https://github.com/pyenv/pyenv-installer/raw/master/bin/pyenv-installer | bash update your .bashrc (or create it if not exists) and add this: export PATH="$HOME/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)" load the new .bashrc with source .bashrc now install the python version that you want like: pyenv install 3.7.2 (you can have multiple versions installed at the same time) (you can check for the available versions with: pyenv install --list) Switch to the new version with: pyenv global 3.7.2 and run slpkg. When you finish with it you can switch back to your original python with: pyenv global system And finaly check for the available python versions in your system with: pyenv versions (the first 'system' means the python that is installed by your system) For example this is from mine: root@lab:~# pyenv versions system 3.1.2 3.5.5 * 3.7.2 (set by /root/.pyenv/version) References: https://github.com/pyenv/pyenv It seems that pyenv only reports the python versions installed into it. My system python is: Python 2.7.17 73 David N1EA

1 0

[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 16 May '20

16 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