Project

General

Profile

Actions

Bug #11672

closed

Default frequency offset wrong

Added by John Oliver 13 days ago. Updated 12 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/10/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
N/A, CHIRP itself
Platform:
Linux
I read the instructions above:
Yes

Description

When I'm programming a GMRS repeater on 462 MHz, at least some of the time the offset defaults to 0.6 MHz If the input frequency is 462 MHz, the offset will always be 5 MHz, and in the rare case that someone has done something weird, they can manually fix.


Files

AnyTone_5888UV_20241109.img (32.2 KB) AnyTone_5888UV_20241109.img John Oliver, 11/10/2024 06:51 AM
config.txt (1.55 KB) config.txt John Oliver, 11/10/2024 07:55 AM
AnyTone_5888UV_20241109.img (32.2 KB) AnyTone_5888UV_20241109.img John Oliver, 11/10/2024 07:55 AM
linux_system_info.txt (806 Bytes) linux_system_info.txt John Oliver, 11/10/2024 07:55 AM
debug_log.txt (578 KB) debug_log.txt John Oliver, 11/10/2024 07:55 AM
Actions #1

Updated by Dan Smith 13 days ago

Can you update this from your running chirp so I can see your config please? Instructions on How_To_Report_Issues.

Updated by John Oliver 13 days ago

[Uploaded from CHIRP next-20241108]

Updating from CHIRP as requested

Actions #3

Updated by Dan Smith 13 days ago

Okay, I see what's going on. The fix won't be deliver-able in a module because of where it is so it'll have to come in the next build.

Actions #4

Updated by John Oliver 13 days ago

Looks like there are some standard offsets that could make programming just a little bit easier!
https://wiki.radioreference.com/index.php/Offset
Thanks, please LMK when that build will be released, I'm happy to test!

On Sunday, November 10, 2024 at 09:22:00 AM MST, Dan Smith redmine@chirpmyradio.com wrote:

Actions #5

Updated by Dan Smith 13 days ago

CHIRP already has extensive support for band-based defaults (including more than just offset/duplex). The GMRS channels are not in that list because they're not always duplex. Meaning, you certainly don't want to always default 462.60 to +5 because most people are putting those in for the simplex version. The Band data structure in CHIRP didn't have a way to say "suggest 5MHz, but only once they choose a duplex" and so it just wasn't listed. I think most people would be putting these in by copying them from the stock config (File->Open stock config) and thus not entering them by default. But, I've got a change queued that will make this a little smoother for hand-editing.

It'll be in the next build, so that's the one to look for :)

Actions #6

Updated by John Oliver 13 days ago

Simplex users would probably not touch the Duplex column.  If they do, I'd argue that they already know they're duplexing, and it's a small help to have CHIRP assume the offset for them.
I look forward to it!  I wind up manually entering repeaters more than I thought I would, as I join new groups.  And sometimes it's faster for me to enter one manually than to open another image just to copy-and-paste one line.

On Sunday, November 10, 2024 at 10:09:17 AM MST, Dan Smith redmine@chirpmyradio.com wrote:

Actions #7

Updated by Dan Smith 13 days ago

Simplex users would probably not touch the Duplex column.  If they do, I'd argue that they already know they're duplexing, and it's a small help to have CHIRP assume the offset for them.

They obviously wouldn't. I'm saying the internal data structure for the defaults did not have a way to suggest an offset without also forcing the duplex. Thus, until the change I have queued, we couldn't suggest 5Hz for GMRS channels without also forcing them to duplex=+.

Actions #8

Updated by John Oliver 13 days ago

Gotcha!  Thanks.

On Sunday, November 10, 2024 at 10:19:09 AM MST, Dan Smith redmine@chirpmyradio.com wrote:

Actions #9

Updated by Dan Smith 12 days ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF