December 2024 - Users - lists.chirpmyradio.com

Re: Users Digest, Vol 186, Issue 1
by Dave B 25 Jan '25

25 Jan '25

Re:- On 01/06/2024 21:38, users-request(a)lists.chirpmyradio.com wrote: > I don't want to specify a specific version here because it's specified in the package and mentioned when you install (see above). Putting it here is just asking for it to be stale if it doesn't get updated the next time we bump. However, I'll be glad to add to the page that if you see something like the above error message it means your python is too old if you think it's necessary for clarity. > >> (Sorry to shout, but...) > Yeah, but please don't do that again. Your responses here have already been quite rude and I'm sure the other volunteers who work on this (and the docs, thanks Jeff!) will join me in appreciating you being a lot more respectful. Thanks! > > --Dan OK Dan. Apologies for "shouting", but things could be somewhat easier for us (the less experience Python users out here) than your good self, who only get involved with installs and updates when needed. Just having something on the download page (and in the archive) that states what the minimum Python version (and wxPython perhaps) is needed for any particular version of Chirp, would save "A Lot" of user time (+ cost for those on a $-per-kByte connection) and confusion re Chirp, when they find after waiting (and or paying for) the download, that it won't install. I see you updated the download info page some hours ago now, at least your name is at the bottom of the page, not Jeff's. (Sorry, I don't know who Jeff is in this respect.) As to "needing" to update my distro (LMDE 5 just now) that is still in full support for nearly another 80 days, it keeps telling me. I don't doubt that things move on over time, that's the nature of stuff, but some appreciation for us the users would help us a lot. As for what pipx is telling us when it fails, that's rather cryptic and embedded in a lot of other text, and looks at first, to be something that was spat out as some code crashed and burnt. OK. For now, I've installed one of the 2024 January 11th version, as that still works with Python 3.9.x So I have the use of Chirp again, for now. FYI: There are several LTS versions of Linux, that last a lot longer than the 2 to 2 1/5 years of the mainstream distro's. Many are popular with Radio Amateurs, just because they /*do not*/ keep messing messing with utility version changes and such. "Stability" is preferable to many of us, rather than living on the bleeding edge of development. If a distro (as mine is) still receives security patches, that for the most part, is all we need. However... For those who would like to know if it's viable to try to install a CHIRP update, before doing so. First, in a terminal command line session. (Ctrl + Alt + T will launch a fresh terminal/command line session.) These commands will show you what you are running. (The '$' indicates the command line prompt, you do not need to enter it.) The result is shown on the next line. Find out the currently installed Python version. $ python3 --version Python 3.9.2 (https://devguide.python.org/versions/ is good to view, in relation to what you discover above. 3.9.x doesn't die, until October 2025, nearly a year and a half away, just for info...) To find out the installed version of wxpython... $ python3 -c "import wx;print(wx.__version__)" 4.0.7 Both as discovered on my present system. In a downloaded .whl file, using an archive browser, look for the folder 'chirp-yyymmdd.dist-info' (Where yyyymmdd equals the date part of whatever file you downloaded.) In that folder, look in the file METADATA and you'll find a string (it is a plain text file) like:- 'Requires-Python: >=3.7,<4' That (in this case) indicates that a Python version between 3.7 and 4 is needed. (Greater or equal to v3.7 and less than v4 That example comes from the 20240111 dated .whl file.) If you download the .tar.gz file instead, look for the file 'requirements.txt' Again, that has some minimum version info re wxpython, but not python itself, that can be found in the file PKG-INFO Again, both are plain text files. Sadly, you do have to download an entire file first to discover that info in either case.. Frankly, I'd suggest doing that first, */before/* uninstalling an existing working version of Chirp! Oh, I'd also keep a local copy of the downloaded file, especially when you do install it successfully. You may need it to repair things if something else goes bad, or to revert to a known working state if a future install goes bad. Perhaps without i'net access at that time. FYI: The immediate past day-job (thankfully I'm retired now!) I used to be the customer support and service guru, in-house and on-site, both hardware and software. I learnt very early on, that making as much information available to users, /before/ they commit themselves, saves a lot of time, effort (and cost) and greatly increases a customers likelihood to come back for more of whatever we were doing at the time, and giving us more of their money! That is with hardware, and especially software! Yes, Chirp is largely free to us the users, other than the cost of time and effort to install and learn. For that we are all grateful indeed. But wasting even "free" time does not go down well with many of us. Retired I might be now, but I'm as busy as ever, just working for other "managers". (Domestic and/or feline!) 73. Dave G8KBV. -- Created on and sent from a Unix like PC running and using free and open source software:

9 14

New chirp-next build
by donotreply＠chirpmyradio.com 27 Dec '24

27 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241227 A list of changes since the last build are here: 43449629 Add basic support for Baofeng W31D and BF-T20D - closes #11671 and #11742 67d51a73 Updated Italian Translation d9949018 Fix marking some untranslated strings aba99276 ga510v2: Fix reading memory block list 855276b7 TK690: Additional Settings options added group names, setting basic/full control head, setting welcome message, setting channel/group name lengths, and compander enable/disable per channel 7db6b122 Fix reloading volatile settings 204f4f78 chore: Bump gh action versions Issues addressed in this build: [Bug 11209] seems some strings, for example "Name" and "Skip" columns are missing from translations. [Bug 11739] Radioddity GA-510

1 0

Question
by Thomas Bain 22 Dec '24

22 Dec '24

Hello. I have a simple question. Is CHIRP software compatible with Windows systems that use the new Qualcomm ARM-based processors? Thank you, Tom

3 4

New chirp-next build
by donotreply＠chirpmyradio.com 20 Dec '24

20 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241220 A list of changes since the last build are here: 605037de bankedit.py: remove redundant memory_changed function, now that _cell_changing handles both cases 48c33155 handle spacebar selection of cells properly ef723140 fix style issues in alinco_dr735t.py to resolve tox -e style failing tests 9deeb0e1 Make RadioSettingValueMap support lazy init 7e5be48c tk690: Remove stray print() debug 81f6e5da Fix RadioSettingValueMap deprecated current-value ef3502e1 Fix missing EOL in FRS/GMRS stock config 58664d97 Add driver for Kenwood TK690, TK790, and TK890. d8bb14bb uv5r: Expose rich "K1 connection" error c58ef444 Updated Italian Translation 0b5af16d Updated Spanish Translation Issues addressed in this build: [Bug 11738] Upload from Radio [New Model 1093] Kenwood TK-690/790/890 [New Model 3363] Kenwood TK-790 Single Head --

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 13 Dec '24

13 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241213 A list of changes since the last build are here: 3991158d fix typo in CSV column name, fixing TStep c7d02403 add legal power limits for US FRS and GMRS, replacing chirp's auto-populated 50W on all channels 409312fe Add MaxTalker P15 301c2fea Add filtering capability to the memory editor ded11074 repeaterbook: Fix memory number sequence 22e3642f baofeng_uv17Pro.py: support BF-F8HP-PRO firmware v0.33 - fixes #11729 68d2fc9b Fix reporting bugs with UTF-8 in debug.log 78ad1411 radtel_rt490: Fix deprecations 3f65fa40 radtel_rt490: Add language toggle cc5db82a rt490: Fix channel names in chinese characters Issues addressed in this build: [Bug 11722] Is it possible to display the channel name in Chinese? [Bug 11724] Language toggle for radtel_rt490 and related [Bug 11725] Log upload with UTF-8 chars fails on Windows [Bug 11729] Update support for Baofeng BF-F8HP-PRO to include changes brought about by firmware version 0.33 [Feature 11731] Add filter querying ability to the memory editor --

1 0

Settings content problem
by Lofgren, Charles 08 Dec '24

08 Dec '24

I'm trying to fix the missing 222 mHz band problem with my Radioddity UV-5rx3, and I've gotten these directions from Chirps' Issues section: Without a copy of an original image (or at least one that wasn't blanked, the best I can offer for you is to do the following... 1. Save the Radioddity_UV-5RX3_20230722(factory).img file that I just attached to a convenient location on your computer 2. Start CHIRP 3. Load the image file that was saved in step 1 into CHIRP 4. Click Settings -> Advanced Settings 5. Click in the field for the bottom Range Override Parameter setting 6. Type CTRL + A to highlight the whole field 7. Type the Delete key to empty the field 8. Manually type in UseAtOwnRisk (do not copy-and-paste from your browser) 9. Upload to your radio 10. Restart CHIRP My problem is that when I go to the Advanced Settings tab, I don't find the indicated Range Override Parameter. The Settings tab itself is at the top of a column on the left side of the screen. I've seen several YouTube videos where the Chriip Settings tab appears about the middle of the screen after some preliminary material. The Settings option on my screen seems to have different content. How do I get to the right version of Settings? Thanks, Charlie

2 2

New chirp-next build
by donotreply＠chirpmyradio.com 06 Dec '24

06 Dec '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20241206 A list of changes since the last build are here: c233a006 Fix GDK_BACKEND hack on Linux 581819f7 ftlx1011: Preliminary py3 conversion ec34595c Update repeaterbook tests for more coverage 39a1b12b Make repeaterbook errors more verbose 351b31df wouxun: Initialize bands after mmap parse a1268a0e Add TYT TH-350US version 44d6ad76 Updated Italian Translation 2560148f Initial support for Radtel RT-620 (GPS) radio, based on UV17 Fixes: #11699 8f0d16ba uv17: Fix missing setting warning message Issues addressed in this build: [Bug 10887] TYT TH-350 Jumbled Names column from Download [Bug 11487] channel names all scrambled [Bug 11715] KG-UV6D rejects 6M frequencies with KG-UV7D [Bug 11721] Glitchy scroll on Ubuntu [New Model 11699] New Model Radtel RT-620 (Ruyage UV6D) GPS --

1 0

Vertex FTL-1011 on Next
by Mark Phillips 05 Dec '24

05 Dec '24

I'm guessing someone already knows this but I tried programming a recently received Vertex FTL-1011 using the latest build of Next and it did not work. I tried on both Linux and Windows to no avail. The initial read crapped out instantly with an error message. Trying it with Legacy worked just fine on both platforms. Should I report this to the developers list? Mark NI2O

2 1