- Users - lists.chirpmyradio.com

[chirp_users] Corrupted memories
by Gary Halleen 05 Sep '23

05 Sep '23

I’m using CHIRP next-20230905, but had the same problem with the last release as well. When programming my Yaesu FT-65R, I’m running into a couple issues: 1. If I set even a single memory to NFM instead of FM, then the next time I upload to my radio, all memories after that one are set to NFM. Example: I set memory 36 to NFM. Memories 36-100 all are set to NFM, even though in CHIRP, they look like they should be set to FM. I’ve tried doing a full reset of the radio, and also tried a memory reset of the radio. Next time I upload, they go back to NFM. 2. If I have memories assigned to Banks, and then delete a memory without first unchecking the box for the bank, the memory stays as a phantom memory. To replicate: Add a new memory and assign it to a bank number (Bank 2 is what I used). Then, after it’s been uploaded to the radio, delete the memory in CHIRP, and re-upload to the radio. When the radio is not set on a Bank, the memory does not show up in the radio. Now, switch the radio to Bank 2. The memory and all of its settings are there even though it was deleted. To resolve it, set a new memory to the same memory number, and go into banks, and uncheck Bank 2. Then, save and go back to memories and delete the memory. Re-upload to the radio and the memory is now gone. Thanks for your hard work keeping CHIRP running for all of us! Gary K7TRO

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 05 Sep '23

05 Sep '23

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: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: 19dc13de Fix for issue #10226 --

1 0

Re: [chirp_users] chirp_users Digest, Vol 177, Issue 3
by Chris Hastie 04 Sep '23

04 Sep '23

Tried to manually delete each from the download from radio, then queried the FRS-GMRS, but went to radio to upload to radio but was not highlighted in the radio menu to upload to radio. On Mon, Sep 4, 2023, 12:02 PM <chirp_users-request(a)intrepid.danplanet.com> wrote: > 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. Ten Way UV-8Pro (Chris Hastie) > 2. Re: Ten Way UV-8Pro (Steve Horning) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Sep 2023 10:22:46 -0700 > From: Chris Hastie <c.hastiessho(a)gmail.com> > Subject: [chirp_users] Ten Way UV-8Pro > To: chirp_users(a)intrepid.danplanet.com > Message-ID: > < > CAMSQg9_qfQhK76qfDg_Ogbh4euQB2iVunTUHpQJSsXVfxUDbZw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > How can I delete the info downloaded from the radio and then reload the > FRS-GMRS from the query ? I have two radios that I want to use for the GMRS > frequencies. > Thank you. >

1 0

[chirp_users] Querying statewide using radioreference.com
by Steve Horning 04 Sep '23

04 Sep '23

Hello! When I query radioreference.com for a specific location I can easily query by zip code. "Query RadioReference" requires a zip code so I don't see how to add statewide frequencies. Am I overlooking something? 73 de N0XVZ, Steve -- This email has been checked for viruses by Avast antivirus software. www.avast.com

1 0

[chirp_users] Ten Way UV-8Pro
by Chris Hastie 04 Sep '23

04 Sep '23

How can I delete the info downloaded from the radio and then reload the FRS-GMRS from the query ? I have two radios that I want to use for the GMRS frequencies. Thank you.

2 1

[chirp_users] UV5R gmrs not recognized but instead Radioddity 8G!
by Larry Massey 03 Sep '23

03 Sep '23

Obtained this radio and attempted to download using Chirp, but was not successful since Chirp doesn't see UV5R(gmrs). Vendor denies this, either Chirp or vendor is in error.

2 1

[chirp_users] UV-17R
by Bob DeFranco 02 Sep '23

02 Sep '23

Does anyone have experience with the UV-17R? Is it just a 5R variant within CHIRP? I don't have one, but they seem like an amazing value with excellent performance. Bob

3 2

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 30 Aug '23

30 Aug '23

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: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: e3b64f2a Ignore same-row drag-and-drop --

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 29 Aug '23

29 Aug '23

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: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: ee851f1d radioddity_r2.py: Add Retevis RT24V - fixes #10816 --

1 0

[chirp_users] is chirp_next recommended for production use?
by Greg Troxel 28 Aug '23

28 Aug '23

I know this project doesn't believe in releases, but pkgsrc currently provides a package with a date as the version. Because chirp-next is labeled next, we are still providing the old codebase, which has not seen an update in a long time. Should we consider the latest chirp-next to be the releaes of record and provide it to users, vs the latest chirp-daily? In other words, should a random user who is not paying attention be handed the old chirp-daily (currently 20221217), or yesterday's chirp-next? Which of these is in this not-paying-attention-user's interest, this week? (If it's one now and in the future will be different, that's ok.) 73 de n1dam

5 7