Bug #11672
closed
Default frequency offset wrong
Added by John Oliver 13 days ago.
Updated 12 days ago.
Model affected:
N/A, CHIRP itself
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
Can you update this from your running chirp so I can see your config please? Instructions on How_To_Report_Issues.
[Uploaded from CHIRP next-20241108]
Updating from CHIRP as requested
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.
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 :)
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:
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=+.
- Status changed from New to Closed
Also available in: Atom
PDF