January 2025 - Users - lists.chirpmyradio.com

Re: Retevis H777 Unable to Connect
by Joshua Morin 12 Mar '25

12 Mar '25

I looked at the release notes for the latest build and saw the new model ticket number (11775) for the H777H_FRS shows an SKU of A9104J for the FRS version. The SKU for the radios I am trying to connect is A9294C. Is this a different H777 model that also needs support developed?

3 3

New chirp-next build
by donotreply＠chirpmyradio.com 31 Jan '25

31 Jan '25

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-20250131 A list of changes since the last build are here: 5f667291 Add support for Icom IC-F621 76af7922 Add Kenwood TK-981 679b5325 tk280: Fix padding ponmsg with 0xFF instead of spaces 62b277ea Encourage user to actually fill out bug reports 4845706c Add some missing-element tests for bitwise bea921ce Updated Spanish Translation e3e6994f tk481: Add Kenwood TK-481 radio 13463c38 Fix bitwise hex count values and array of zero d5ce1f9c tk280: Refactor internals to work with tk481 a1dfb3f4 tk8180: Remove hackaround bitwise array-of-one bug 39a30a90 Fix long-standing bitwise array-of-one bug aa6e7ff8 Fix always choosing mode FM even if unsupported 4ba46b50 Fix reloading driver keeping the same UI tab 02b5e297 Remember last-used port by model b3d5df84 Allow changing setting/group display names 4e5de794 Fixed a typo ccdd7588 Updated Italian Translation d00cdfa5 Fix sorting columns on linux Issues addressed in this build: [Bug 11793] error message when sorting [Feature 11797] Remember COM port in Recent [New Model 11490] Icom IC-F521 [New Model 11802] Kenwood TK-981 [New Model 6505] Icom IC-F621-2 --

1 0

Airport Freqs
by CN7 30 Jan '25

30 Jan '25

How does one imput freqs for an airport? Rockhampton QLD Aussie Tower freq is 118.1Mhz - BUT I do NOT want it to accidently tx on it. So, how does one, block TX mode? rgrds n 73

3 11

Chirp 20250124 ==> Yaesu FT-70D fail to communicate with the radio
by Stéphane BOUTEILLER 28 Jan '25

28 Jan '25

Hello I got this error on a mac since the last update of shirp, any ideas ? [2025-01-28 19:39:01,364] chirp.wxui.main - DEBUG: Recent is now [] [2025-01-28 19:39:01,713] chirp.wxui.main - INFO: Server reports next-20250124 is latest [2025-01-28 19:39:56,450] chirp.wxui.clone - DEBUG: All system ports: [{'device': '/dev/cu.Bluetooth-Incoming-Port', 'name': 'cu.Bluetooth-Incoming-Port', 'description': 'n/a', 'hwid': 'n/a', 'vid': None, 'pid': None, 'serial_number': None, 'location': None, 'manufacturer': None, 'product': None, 'interface': None}, {'device': '/dev/cu.usbmodem0000000000001', 'name': 'cu.usbmodem0000000000001', 'description': 'IOUSBHostDevice', 'hwid': 'USB VID:PID=26AA:001B SER=000000000000 LOCATION=1-1', 'vid': 9898, 'pid': 27, 'serial_number': '000000000000', 'location': '1-1', 'manufacturer': None, 'product': 'IOUSBHostDevice', 'interface': None}] [2025-01-28 19:39:58,766] chirp.wxui.clone - DEBUG: Using port '/dev/cu.usbmodem0000000000001' [2025-01-28 19:39:58,766] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.ft70.FT70Radio'> [2025-01-28 19:39:58,771] chirp.wxui.clone - DEBUG: Showing pre_download prompt [2025-01-28 19:40:01,542] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download [2025-01-28 19:40:01,590] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x10f0a8fa0, open=True>(port='/dev/cu.usbmodem0000000000001', baudrate=38400, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True) [2025-01-28 19:40:16,814] chirp.drivers.yaesu_clone - DEBUG: [2025-01-28 19:40:16,815] chirp.wxui.clone - ERROR: Failed to clone: Failed to communicate with the radio: No response from radio Traceback (most recent call last): File "chirp/drivers/yaesu_clone.py", line 109, in _clone_in File "chirp/drivers/yaesu_clone.py", line 91, in __clone_in chirp.errors.RadioError: No response from radio During handling of the above exception, another exception occurred: Traceback (most recent call last): File "chirp/wxui/clone.py", line 94, in run File "chirp/drivers/yaesu_clone.py", line 268, in sync_in File "chirp/drivers/yaesu_clone.py", line 111, in _clone_in chirp.errors.RadioError: Failed to communicate with the radio: No response from radio [2025-01-28 19:40:20,212] chirp.wxui.clone - WARNING: Stopping clone thread

1 0

Yaesu VX-8G
by dorn＠hetzel.org 27 Jan '25

27 Jan '25

I see several Yaesu VX-8? models in the supported list, but not the VX-8G. Should I expect it will probably work, or no?

2 1

Program ANI or PTT ID?
by John Oliver 26 Jan '25

26 Jan '25

I'm having a devil of a time figuring out how to do this... I'm looking through all sorts of fields and functions looking for anything that looks relevant. All I can find is length (3, 4, or 5) and PTT-ID that isn't a way to set the code, but just when it's transmitted. I was given a 4 digit code that is now a requirement on one of the repeaters I use, but no info on how to apply it.

2 2

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

Programmazione del Polmar DB10 MK II
by Ivano 25 Jan '25

25 Jan '25

Salve, fra gli apparati programmabili con Chirp non vedo la radio in oggetto. Esiste un prodotto similare, che non sono riuscito a trovare tra le varie possibilita' nel menu del programma? Grazie in anticipo Ivano

2 3

Running chirp on a tablet with windows 10
by Gary Chesshir 25 Jan '25

25 Jan '25

Has anyone tried using chirp on a tablet running windows 10? Did it work ok or what if any issues did you encounter? Gary Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg>

2 1

Programming the Polmar DB10 MK II.....
by Ivano 24 Jan '25

24 Jan '25

Hi, among the devices programmable with Chirp I don't see the radio in question. Is there a similar product that I couldn't find among the various possibilities in the program menu? Thanks in advance Ivan

1 0