November 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 29 Nov '24

29 Nov '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-20241129 A list of changes since the last build are here: 7fef7cca Updated Spanish Translation 626586c0 Fix opening the languages list when running from the sources tree 924c5696 Do a case insensitive sort of languages 6c2cffeb Make offset column hint at TX freq for split-capable radios 85cfb944 Catch driver errors during save and show a dialog d76634dd ft70: Some bank assignment fixes d7827323 Initial ICOM IC-M710 driver 1c38b735 icf: Allow drivers to skip clone result f2b00534 Make test_icom_clone honor radio _ranges 2f48001e Move STEPS in baofeng_uv17Pro to UV17Pro class, fixes #11716 d1f8504e uv17: Allow separate block list to be read 7703a97c Add Radtel RT-470X Plus BT signature, separate class and test file b2ff882d query sources: add przemienniki.eu 8276b581 Fix typos 5b41e67d Add developer serial-open-error test fixture 518cbb66 Fix clone dialog hang if serial open error Issues addressed in this build: [Bug 11700] Hanging when communicating with radio [Bug 11702] Yaesu FT-70D Memory Bank issues [Bug 11717] After introduction of banks in UV17Pro driver, UV17 driver reports multiple errors for banks [Feature 11430] SP Repaters Database - przemienniki.eu [Feature 11716] Improvement of Baofeng uv17Pro to make step lists part of class [New Model 1067] Icom IC-M710 [New Model 11695] Radtel RT-470X Plus Bluetooth --

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 22 Nov '24

22 Nov '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-20241122 A list of changes since the last build are here: 99bf4ccc Added zh_CN welcome screen e01d36e1 Remove last remaining usage of python3-six b33595c6 icv80: Fix txinhibit as duplex=off 53235e50 ft70: Fix tuning steps 5.0 and 6.25 4b030553 Improve error message for tuning step failure Issues addressed in this build: [Bug 11336] v80e duplex is missing OFF [Bug 11681] Yaesu FT-70D Wrong tuning steps --

1 0

Out Of Supported Range Error for BaoFang UV-5RH Pro Max
by robboere＠hotmail.com 17 Nov '24

17 Nov '24

I'm currently setting up a UK-5RH Pro Max which is able to monitor around 6 frequency bands as well as having the FM Radio function available on many UV-5Rs. I've been trying to set-up a number of additional FM radio frequencies in the range of 88.8 MHz to 107.5 MHz for stations in and around London here in the UK. These frequencies can for the most part be found on the FM radio function, but they can't be named with the built in FM radio scanner - so was seeking to create these as a set of defined channels in my configuration file. I have created these as a CSV and have loaded them into Chirp as a CSV import. However I don't seem to be able to insert them into the configuration file for the handset. Unfortunately, I receive the message "Some memories are incompatible with this radio" and specific errors such as "Frequency 96.400000 is out of supported range" for all 60 that I'm trying to insert. I have added other frequencies from 108 MHz onwards and there are absolutely no problems with these - so am sure that the method I'm using to add these is correct. It seems to just be the question around adding any frequencies below 108 MHz and the Chirp configuration and/or the Radio not accepting them. I've checked the radio and I can scan all of the ranges outlined below, so the radio is capable of receiving on those ranges: - 65-108 MHz FM RX - 108-136 MHz AM RX AM Air Receiving Only - 136-174 MHz FM TX/RX - 220-260 MHz FM TX/RX - 350-390 MHz FM RX - 400-480 MHz FM TX/RX - 480-520 MHz FM RX I have used both the Baofeng UV-5RH and Baofeng 5RM but neither of these allow these frequencies to be added to the listing. I was keen to have FM radio channels with names and direct selection via the channel selection capability, but it seem that this isn't possible. It means that I'd need to scan anywhere where I am and hope to guess what the radio station is. Would anyone know why the software (or Radio/Profile) isn't allowing me to add these frequencies?

3 2

No response from radio error
by Ramon Jones 16 Nov '24

16 Nov '24

I have searched the archive and could not find an answer. I just purchased a Btech FTDI programming cable. I have been unable to use this cable with the CHRIP programming software, I get a "No response from radio" error message when I try to read any Baofeng radio. I have multiple UV-5R and BF-888s radios, I have tried programming on 3 different computers using Windows 7, 10 and 11 with the same problem! When I look at the device manager, everything looks correct on all 3 computers. If I try using the BF-888 software on the BF-888s radio everything works as it should! Do you have any suggestions to fix this problem?

4 3

New chirp-next build
by donotreply＠chirpmyradio.com 15 Nov '24

15 Nov '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-20241115 A list of changes since the last build are here: 71812ad1 Fix recent dialog on linux 3413ee78 Add US GMRS bandplan defaults 15647b45 bandplan: Allow offset defaults without duplex 3713f665 Backup radio image before each upload f5c21377 Avoid force-wrapping long locale lines 3eae005b Update zh_CN.po Issues addressed in this build: [Bug 11673] "Recent" button not working on Linux [New Model 11671] Baofeng W31D --

1 0

Yaesu vs. Baofeng/TYT band memories
by Massimo Nespolo 11 Nov '24

11 Nov '24

Greetings, Two amateurs groups need to build up a common group. One has Yaesu FT-4x, the other Baofeng or TYT. Chirp supports both. However, it does not seem possible to past or export-import the band memories from one model to the other - at least I couldn't figure out how to do it. Is there a way, or one has to retype everything by hand? Thank you in advance. Massimo

2 4

Export to CSV failing when no row selected
by andy＠gamubaru.com 09 Nov '24

09 Nov '24

I have an Icom-7100. I can download from the radio OK. There are two cases where the export to CSV fails. 1) If no rows are selected. 2) if row 0 and other rows are selected. If I select valid rows, it works. On failure I get: ERROR: <function ChirpEditorSet.export_to_file at 0x7063e0c2d300> raised unexpected exception Traceback (most recent call last): File "/home/andy/.local/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/wxui/common.py", line 642, in run_safe return fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^ File "/home/andy/.local/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/wxui/main.py", line 325, in export_to_file current.export_to_file(filename) File "/home/andy/.local/pipx/venvs/chirp/lib/python3.12/site-packages/chirp/wxui/memedit.py", line 2247, in export_to_file m = self._memory_cache[row] ~~~~~~~~~~~~~~~~~~^^^^^ KeyError: 0 This seems to be from site-packages/chirp/wxui/memedit.py: def export_to_file(self, filename): if not filename.lower().endswith('.csv'): raise Exception(_('Export can only write CSV files')) selected = self._grid.GetSelectedRows() if len(selected) <= 1: selected = range(0, self._grid.GetNumberRows()) -------------------------------------^ When no rows are selected, the range includes 0. If you start from 1, it works print("selected: ",selected) r = generic_csv.CSVRadio(None) # The CSV driver defaults to a single non-empty memory at location # zero, so delete it before we go to export. r.erase_memory(0) for row in selected: m = self._memory_cache[row] This is using chirp-20241108-py3-none-any.whl I'm not sure if some radios may actually start at memory zero. The comment about deleting row zero would seem to indicate that is not the case. Thanks, Andy - KF5JLJ Thanks

3 3

New chirp-next build
by donotreply＠chirpmyradio.com 08 Nov '24

08 Nov '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-20241108 A list of changes since the last build are here: 1f4ebe12 Update SE Jaktradio 155MHz.csv 609fe945 Updated Italian Translation 31254783 Updated Spanish Translation 61c21456 tdh8: Update power definitions for TD-H3 19ac9556 tdh8: Convert all OFF/ON selections to checkboxes c98bee45 tdh8: Add settings from 240416 TD-H3 firmware e8459bfe Retry file uploads during bug report a2cfddef Fix bugreport on Linux (or older wx) 25bcdd3f Collect system information for bug reports 420a3819 Make baofeng_common radios suggest K1 help ac5e8eb4 Add richer errors for specific driver issues 57e487bc id31/51: Fix TSQL/DTCS "error" on CS-31 1d429909 id31/51: Fix 6.25kHz offsets values 29ca345e id51: Fix loading ICF files a321b1a3 dr735: Clean up style for consistency 29f81022 dr735t: Add bell and favorite to extra settings and set their default values Issues addressed in this build: [Bug 11360] Alinco DR-735T new memory slot settings [Bug 11652] Some memories read as 4MHz offset [Bug 11657] ID31/51 some TSQL/DTCS show as "error" in CS-31 --

1 0

K5 plus
by s.fairs＠btinternet.com 08 Nov '24

08 Nov '24

Chirp will download from my K5plus , but does not recognise the radio when I try to upload.

3 2