Re: [Tlf-devel] TLF in CQWW CW

[Andy Summers]

Hi Tom,

Sorry for the delay in replying. I chose to upgrade the OS to Fedora 
16_64-bit and it took me a while to get back to a useful PC - hi!

Regarding ctrl-g and the bandmap, I'm using an Orion and 
hamlib-1.2.14-1. Using the hamlib rigctl utility, frequency is reported 
correctly to 1Hz resolution, so certainly that isn't to blame. Normally 
I set the Orion to step in 10Hz steps.

Here's my test:
Enter G4ABC, hit ctrl-a, is displayed in bandmap to 100Hz resolution.
Move hf a little, enter G4DEF, hit ctrl-a again.
Move hf a little, enter G4GHI, hit ctrl-a again.
Move hf a little, enter G4JKL, hit ctrl-a again.

Hit ctrl-g, G4GHI is grabbed - as desired with exactly correct frequency.
Hit ctrl-g again - it leaves G4GHI grabbed!
Keep hitting ctrl-g - nothing changes.
Move rig lf slightly, hit ctrl-g, G4DEF is grabbed.
Hit ctrl-g again, G4ABC is grabbed.
Hit ctrl-g again, gets stuck on G4ABC.
Move rig slightly hf, G4DEF is grabbed.
Hit ctrl-g again, G4GHI is grabbed.
Hit ctrl-g again, G4JKL is grabbed.
Hit ctrl-g again, gets stuck on G4JKL.
Move rig lf slightly, hit ctrl-g, G4GHI is grabbed.
And so on.

So it is definitely getting confused about whether it should be moving 
up or down the band in some situations, e.g. at the limits of the stack, 
when it should turn around.. You ought to be able to repeat this test. 
Let me know.

I tried the alt-g function, by the way, and it works as you described - 
very useful!

On the other points, well yes - I should have read the manual!

Thinking about bandmaps a bit more... Ideally, I'd like to know if some 
loud station I'm tuning through is a dupe who's been running on that 
frequency for some time. I don't want to wait to hear them give their 
call (especially those who perpetually QRZ?), and I can't remember a 
whole band in my head. On that basis it would be useful to see dupes in 
the bandmap, but it gets in the way of quickly grabbing spots. In N1MM 
logger (and similar), the call in the bandmap is automatically put into 
the exchange field when the rig frequency is within a (configurable) 
tolerance of the spot frequency. Such a feature would allow you to set 
bandmap filtering to exclude dupes and yet still give an indication that 
you're currently tuning through a probable dupe.

Keep up the good work!
73 Andy, G4KNO

On 12/08/2011 06:35 AM, Thomas Beierlein wrote:
> 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