Hi Andy,
I know some of your comments regarding the bandmap are still
unanswered. Sorry, was a busy time here. So let me try to answer here
and continue the discussion.
Am Wed, 7 Dec 2011 13:24:43 +0000 schrieb
Andy Summers<address@hidden>:
On the new bandmap, I notice that ctrl-g grabs all calls, including
those you've worked.
It grabs any call which is displayed. If you filter your display by
band, mode or filter out the dupes ctrl-g grabs only the next
*displayed* station up from your working frequency (as documented in
Newbandmap.txt).
If your S&P rate is high enough you can get into
a situation where a lot of ctrl-g presses are required to get to the
spot you're after. I didn't use the Cluster, BTW.
On the one hand, it's useful to have worked calls in the bandmap so
you know who you've just tuned through and don't wait to listen for
the call. On the other hand, they get in the way of quickly grabbing
spots.
Well, it should be simple enough to not select any dupe and skip it
over. Let me experiment.
One feature not documented in the original post is to selectively call
a special spot. Type in some characters of the call you want and press
Alt-g (make sure it works in your terminal) and TLF will grab the first
spot with that characters in the call. Be aware that it will grab the
first spot which matches.
Traversing the bandmap spots is still inconsistent for me, as I
explained earlier.
I beleive you are speaking about that sentence:
I think I've figured out what's happening. If you tune the rig just
below the frequency of a spot then hit ctrl-g it grabs that spot.
Hitting ctrl-g again without retuning the rig just picks the same
spot.
Tune the rig HF a little and then when you hit ctrl-g it goes to the
next spot. So I imagine you have some logic in there something like:
for (i = 0, i< noOfSpots) {
if (currentFreq<= SpotFreq(i)) {
goto(SpotFreq(i));
}
}
No. It is a
if (spotfreq> currentfreq) {
goto spotfrequ;
}
in the case of searching upwards. It also works very stable and well
here.
Maybe let us ask which rig you use? What is the frequency resolution
if you set a frequency and if you read the frequency back from it.
Normally it gets recorded down to 1 Hz resolution. The spots from
cluster are in 100 Hz steps and your own recorded spots (ctrl-a) are as
precise as your rig can report. Maybe there is some discrepancy between
setting frequency and aksing it back.
73, Tom DL1JBE