From: Stephen Hurd <shurd@sa...> - 2013-07-10 18:48:19
I'm also curious about how scanning is supposed to work. For the TS-940
for example, there are two types of scan, a memory scan, which pauses at
each memory frequency for about six seconds then moves on to the next,
and a programmed scan which sweeps between two specific memories (nine
and zero - just to be a pain defining the RIG_MTYPE_MEM entries).
Both of these scans types, when stopped, restore the VFO to the state
when the scan was started... that is, if I'm, in CW mode on 160m and do
a program scan of the voice segment of 10m, it switches to 10m USB, does
the scan, and when I stop, returns to 160m CW. There is a scan hold
which pauses the scan at which point you can tune.
So, how is the scan supposed to work? I could have hamlib do the scan
hold, store the frequency, stop the scan, then restore the frequency...
is that what's expected?
Basically, is the SCAN_STOP expected to copy the scan frequency to the
current VFO, is it expect to pause the scan until a SCAN_NONE is sent,
or is it actually expected to revert to the VFO settings when scan was
Currently I'm doing the last and I can't imagine it being very useful
without access to the scan hold function.
Get latest updates about Open Source Projects, Conferences and News.