- Users - lists.chirpmyradio.com

[chirp_users] New chirp-next build
by donotreply＠chirpmyradio.com 19 Mar '24

19 Mar '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday 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-20240319 A list of changes since the last build are here: 74a8717d idrp: Add --debug flag for verbosity 88bcaf9c tdh8: Fix and simplify FM channel settings 9315d397 tdh8: Fix TD-H3 power levels 06ae1e9b tdh8: Simplify and fix offset/split/off decoding 47840b26 tdh8: Simplify skip/add data structure 38ca750c tdh8: Fix byte ordering for used flags 7fdd01a4 tdh8: Late-evaluate mic gain setting 524493b7 tdh8: Extend RX frequency range 91c78b39 uvk5: set correct default values for extra settings in empty channels Issues addressed in this build: [Bug 11163] Tidradio TD-H3 frequency and power programming [Bug 11232] Tidradio H3 deleted memories still showing in radio [Bug 11233] cannot enter frequencies out of band.. [Bug 11242] Tidradio H3 Settings menu gone again --

1 0

[chirp_users] CHIRP Next-Build
by Christopher Knowles 17 Mar '24

17 Mar '24

The new version of CHIRP will not display recently-open files. Christopher Knowles, WD1E -- Christopher Allan Knowles, MPA P.O. Box 4632 Vineyard Haven, MA 02568 Please find my LinkedIn profile at: https://www.linkedin.com/in/chris-knowles-99aba51a/ Staff Sergeant, United States Air Force, 1970 - 1974 Call Sign: WD1E - Amateur Extra Class Accredited Volunteer Examiner (VE)

3 4

[chirp_users] New chirp-next build
by donotreply＠chirpmyradio.com 17 Mar '24

17 Mar '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday 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-20240317 A list of changes since the last build are here: 86a2ee0e idrp: Presumptive python3 conversion 749f9dca Fix displaying choice settings 5b84b4c5 uvk5: Bless k5_4.00 firmware for Quansheng UV-5R Plus 5cf61ad1 snapcraft: use archive.chirpmyradio.com df74b0a8 Initial support for Icom IC-7400 f9e5b870 Allow late eval of choice settings cef146f8 bitwise: Add lbit type for LE bit arrays Issues addressed in this build: [Bug 11240] Quansheng UV-5R Plus [New Model 11246] Icom IC-7400 --

1 0

[chirp_users] Python3 Update for rpttool?
by Kyle Brown 17 Mar '24

17 Mar '24

Is there a plan to update the rpttool to work with Python3 like the rest of Chirp? I see it hasn't been updated in a while and I am looking to use it with a ID-RP2000V Repeater.

2 1

[chirp_users] New chirp-next build
by donotreply＠chirpmyradio.com 15 Mar '24

15 Mar '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday 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-20240312 A list of changes since the last build are here: c00166ba typo fixes in Spanish translation e8c28d76 Fix default argument parsing on Linux d3a2783f kenwood_live: Fix out-of-order tone list 4c8f2720 Update Spanish Translation Issues addressed in this build: [Bug 11235] chirp 20240311 fails to launch (Debian 12, Python 3.11.2) [Bug 11236] Kenwood live tones out of order --

6 8

[chirp_users] Observations: Kenwood TM-D700A VHF/UHF Radio
by mark＠marwalk.com 11 Mar '24

11 Mar '24

This is my experience so far with CHIRP and the TM-D700A radio. The radio receives input from CHIRP in Live mode, with changes being in near real-time on the control head. Turning the radio off and on and then re-downloading the memory slots displays what was entered previously (of course it would, why are you mentioning that?). I can understand why RT Systems stopped supporting this model calling it a cranky radio. Here are some observed anomalies, and the solutions I found to work after much experimentation: * Although the frequencies and memory names from CHIRP stick with the radio, the Tones do not, and even if the correct tone is there, moving to another memory slot and back to the previous memory loses the Tone setting. This was odd as the re-download from the radio had the correct tones still there, while the radio [F] --> [T.SEL] displayed a completely different and as far as I can tell unrelated tone frequency. The solution to this has been to load the memory into the VFO and enter the correct tone in VFO mode; then re-save the complete setting back to its memory slot. Dont hold the M.IN button too long (> 1s) or it will enter as Split mode (±), and thats a cul-de-sac not to be trapped in (the escape is going into VFO mode and back to the intended memory slot using another memory slot thats in the proper +/- offset for the target repeater). Its unclear to me why this radio just wont accept what its told to configure. * This radio pays attention to which Band its in (see TM-D700 Manual, p.41). By default Band A (the Left knob) is for VHF, and Band B (the Right knob) is for UHF. Ive learned to be sure to bring up for PTT in the Band associated with the frequency in a specific memory slot (listening to anything on either Band works fine with no problem). That also is the case for programming a memory slot, that is, program VHF frequencies with Band A and UHF frequencies with Band B, including correcting the Tone setting that it received from CHIRP and didnt keep. * Im not sure this is something that CHIRP can solve: The Repeater Book look ups contain errors in the Tone settings. A couple of examples Im directly familiar with are: * The 146.13/73 repeater in Frederick, MD operates on Tone only (not CTCSS). The Repeater Book CHIRP lookup displays this repeater as TSQL (which sets the radio into CTCSS mode when applied). This repeater does not provide a downlink tone, resulting in dead silence in CTCSS mode. * The 146.295/895 repeater in Manchester, MD is a multi-access repeater listed in the manually accessed Repeater Book listing as: 146.8950 -0.6 MHz CSQ / 107.2 Manchester Carroll N3KZS OPEN FM AllStar IRLP CHIRP will not load the listing for this repeater from its Repeater Book lookup saying this radio does not support Cross Tone mode: [146.895000/-0.600/107.2] Tone Mode: Cross; Cross Mode: -> Tone However, Ive successfully accessed this repeater with this radio using the 107.2 tone listed, after manually entering it into its memory slot. Hope these observations help people use CHIRP to help them work through the TM-D700A radios crankiness. Thanks, Mark AC3EW

2 1

[chirp_users] New chirp-next build
by donotreply＠chirpmyradio.com 11 Mar '24

11 Mar '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday 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-20240311 A list of changes since the last build are here: 3cc4bf36 Warn about loading modules with open tabs e2b026a6 Add modular config dir command-line option 7fda4fd5 Stop even building fakes in normal mode 7d42bfb3 Add missing tooltip for mode column 0c1ac358 Tweaks to dev mode logging and toggling aa55cd11 Add MYEMR1 alias 32f1a5fc tdh8: Handle invalid FM VFO value 8603477f Update Spanish Translation e9600540 Fixed a typo while preparing an IC-7400 driver Issues addressed in this build: [Bug 11215] set_doc not working in the memorie tab, but working in the Settings tab [Bug 11226] Tidradio H3 Settings menu [New Model 11224] MyEmergencyRADIO - MYEMR1 --

1 0

[chirp_users] Stable low cost radio with flat audio
by Chuck Hast 09 Mar '24

09 Mar '24

I am asking this question here as I believe there is a good collection of folks who are familiar with different radios. Of course whatever is recommended I hope it can be programmed with Chirp. I am looking for a handheld radio that can do 12.5khz bw audio that can be used for data. I would hope it would have a flat audio in/out port but if not mods are part of the game. It needs to be frequency stable (I will be using it for data) and 12.5khz channel widths. and of course programmable with Chirp. The radio cost needs to be low, I would like to keep the whole project under $500. I will need two radios 1 for RX and 1 for TX. There will be a controller involved. If need be I will put each radio in a can for isolation. This is for a solar project so that is also part of the reason to try to use a handheld. -- Chuck -- KP4DJT HamHotline # 11259

5 5

[chirp_users] UV-17ProGPS
by Ryan Knowles 09 Mar '24

09 Mar '24

Hello, New to the Amateur Radio hobby, as well as the CHIRP software, and I apologize in advance as I must be missing a step in the programming of my radio. I have my Frequencies ready, and Banks individually names to match, though my CHIRP interface is missing the Banks tab to be able to apply my frequencies to each configured Bank as needed. Additionally, I do see within the Info tab, on the Features page that the has_bank and has_bank_index options are set to False. Could this be related to the absence of the Banks tab? Thank you in advance for any guidance available!

3 3

[chirp_users] New domain
by Dan Smith 06 Mar '24

06 Mar '24

Hi all, After almost 16 years as a subdomain on my personal one, CHIRP has a proper domain name of it's own: https://chirpmyradio.com This has been on my todo list for quite some time, but it has always been lower priority than other things and it just kept slipping. Once the first decade passed it was hard to imagine the change. However, some changes Google (mail) is putting into place is making this more urgent than it has ever been, which is as good an excuse as any. You'll start to see this new domain name pop up in more and more places. The new name points to the exact same place that the old one does, so there's no *need* to use one or the other at this point. Since the old domain has 16 years of rust on it, it will take some time to fully migrate over, and I plan to do it as gracefully as possible without breaking links, search results, etc. Once things are ready I'll start redirecting parts of the old domain to the new one. At some point I'll also need to move this mailing list to the new name as well. So, if you see the new domain don't panic, nothing has been hijacked. Just closing out some 16-year-old todo list items :) --Dan

6 6