[chirp_devel] Architectural question: skip-only memory in chirp?
I’ve an basic architectural question: my Yaesu FT2D has a subset of memory space wholly devoted to "skip" frequencies: ones that are not scanned during VFO scanning They're formatted just the same as (repeater) memories, but they're always skipped in VFO mode. I've not used 'em, so they weren't high priority when playing with the candidate FT2D driver. Indeed, I “lied” and told the driver to only use memories up to 900; 901-999 are actually defined in the radio as the always-skip memories.
Does chirp natively support an alternate memory of always-skipped frequencies? I feel it’d be better for chirp to be able to read/write memories 901-999, but I’d really hate for somebody to think that they can store [really important] operational items in those spaces.
Declan Rieb WD5EQY
Does chirp natively support an alternate memory of always-skipped frequencies? I feel it’d be better for chirp to be able to read/write memories 901-999, but I’d really hate for somebody to think that they can store [really important] operational items in those spaces.
Just refuse to store a memory in that range if the skip bit is not set, and always return it as set when you fetch those out. The user will get an immediate error that the memory can't be saved if they try to unset the skip flag.
--Dan
participants (2)
-
Dan Smith -
NNN Wx