Re: Bandmap

[Ervin Hegedüs]

Hi Ed,

it depends on what you want.

Btw. I think the apostrophes are not necessary, so the correct form is
something like this:

BANDMAP=BM,300

My 2 cents: 300 secs is a bit small, it means after 5 mins the spot will
disappear from your bandmap.

73, Ervin
HA2OS




On Thu, Jul 28, 2022 at 3:30 PM Ed  wrote:

>
> Is this correct ?
>
> BANDMAP='B''M',300
>
> Ed W3NR
>
>

Bandmap

[Ed]

Is this correct ?

BANDMAP='B''M',300

Ed W3NR

Re: Moving the bandmap

[flynth]

Thanks for the reply Zoli. This does solve my problem. It would be nice if
this was in the FAQ. I'll try to remember to submit a change request next
time I'm on github (not too soon).

BTW. Sorry for the late reply and possility this post creates a new thread.
I spent days unsuccessfully searching for a Linux GUI imap email client
that can properly reply to a message contained in a digest preserving
message id. Unfortunately I found none so I'm simply copy/pasting the
subject line to respond.

Regards,
Lukasz


Date: Mon, 1 Nov 2021 18:47:48 +0100
From: Thomas Beierlein 
To: tlf-devel@nongnu.org
Subject: Re: Moving the bandmap.
Message-ID: <20211101184748.3dfade03@Andromeda>
Content-Type: text/plain; charset=UTF-8

Hi Zoli, Hi Lukasz,

how about adding it to the FAQ?

73, de Tom

Am Mon, 1 Nov 2021 08:11:48 +0100
schrieb Csahok Zoltan :

> Hi Lukasz,
>
> Even though Tlf can be started without rig control but some of its
> functionality will be limited as you have exprienced it.
> To overcome this you can use rigctld in dummy mode.
> Here is how:
> 1) start rigctld for Dummy radio (ignore the warnings)
> $ rigctld -m 1 &
> 2) check if it works by reading freq and mode (default is 2m FM)
> $ rigctl -m 2 f m
> 14500
> FM
> 15000
> 3) set your real radio's freq+mode for dummy rigctld (freq unit
> is Hz) $ rigctl -m 2 F 2120 M USB 0
> 4) configure Tlf to use rigctld
> RIGMODEL=2
> RIGPORT=127.0.0.1
> 5) from Tlf freq can be changed either by
> a) Ctrl-F or
> b) direct freq entry on call field: enter a kHz value (no
> fraction, e.g. 21195) as call and press enter or
> c) moving around on bandmap by Ctrl-G (grab) / Ctrl-V
> (direction).
>
>
> Hope this helps.
>
> 73,
> Zoli
>
>
>
> On Sun, Oct 31, 2021 at 07:17:15PM +0100, Lukasz Olszewski wrote:
> >Hi,
> >I apologise if this is a trivial question, but I've read the man
> > page multiple times and I cannot figure out how to move the bandmap
> > display. I have no rig control. My frequency is simply logged as
> > 15m for example. Today I was on 15m and the bandmap window was
> > showing spots from 21.200 to 21.300. I needed to see ones below
> > 21.200. I tried ctrl-f (it did nothing.
> >- probably because it requires rig control).
> >However, somehow later the bandmap shifted to display range
> > 21.100 to 21.200 just when I needed 21.200~21.300...
> >Can someone help me, please by telling me how to navigate the
> > bandmap window?
> >Many thanks,?
> >Lukasz?
>

Re: Moving the bandmap.

[Thomas Beierlein]

Hi Zoli, Hi Lukasz,

how about adding it to the FAQ?

73, de Tom

Am Mon, 1 Nov 2021 08:11:48 +0100
schrieb Csahok Zoltan :

> Hi Lukasz,
> 
> Even though Tlf can be started without rig control but some of its
> functionality will be limited as you have exprienced it.
> To overcome this you can use rigctld in dummy mode.
> Here is how:
> 1) start rigctld for Dummy radio (ignore the warnings)
> $ rigctld -m 1 &
> 2) check if it works by reading freq and mode (default is 2m FM)
> $ rigctl -m 2 f m
> 14500
> FM
> 15000
> 3) set your real radio's freq+mode for dummy rigctld (freq unit
> is Hz) $ rigctl -m 2 F 2120 M USB 0
> 4) configure Tlf to use rigctld
> RIGMODEL=2
> RIGPORT=127.0.0.1
> 5) from Tlf freq can be changed either by
> a) Ctrl-F or
> b) direct freq entry on call field: enter a kHz value (no
> fraction, e.g. 21195) as call and press enter or
> c) moving around on bandmap by Ctrl-G (grab) / Ctrl-V
> (direction).
> 
> 
> Hope this helps.
> 
> 73,
> Zoli
> 
> 
> 
> On Sun, Oct 31, 2021 at 07:17:15PM +0100, Lukasz Olszewski wrote:
> >Hi,
> >I apologise if this is a trivial question, but I've read the man
> > page multiple times and I cannot figure out how to move the bandmap
> > display. I have no rig control. My frequency is simply logged as
> > 15m for example. Today I was on 15m and the bandmap window was
> > showing spots from 21.200 to 21.300. I needed to see ones below
> > 21.200. I tried ctrl-f (it did nothing.
> >- probably because it requires rig control).
> >However, somehow later the bandmap shifted to display range
> > 21.100 to 21.200 just when I needed 21.200~21.300...
> >Can someone help me, please by telling me how to navigate the
> > bandmap window?
> >Many thanks, 
> >Lukasz   
> 



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: Moving the bandmap.

[Csahok Zoltan]

Hi Lukasz,

Even though Tlf can be started without rig control but some of its
functionality will be limited as you have exprienced it.
To overcome this you can use rigctld in dummy mode.
Here is how:
1) start rigctld for Dummy radio (ignore the warnings)
$ rigctld -m 1 &
2) check if it works by reading freq and mode (default is 2m FM)
$ rigctl -m 2 f m
14500
FM
15000
3) set your real radio's freq+mode for dummy rigctld (freq unit is Hz)
$ rigctl -m 2 F 2120 M USB 0
4) configure Tlf to use rigctld
RIGMODEL=2
RIGPORT=127.0.0.1
5) from Tlf freq can be changed either by
a) Ctrl-F or
b) direct freq entry on call field: enter a kHz value (no fraction,
e.g. 21195) as call and press enter or
c) moving around on bandmap by Ctrl-G (grab) / Ctrl-V (direction).


Hope this helps.

73,
Zoli



On Sun, Oct 31, 2021 at 07:17:15PM +0100, Lukasz Olszewski wrote:
>Hi,
>I apologise if this is a trivial question, but I've read the man page
>multiple times and I cannot figure out how to move the bandmap display.
>I have no rig control. My frequency is simply logged as 15m for example.
>Today I was on 15m and the bandmap window was showing spots from 21.200 to
>21.300. I needed to see ones below 21.200. I tried ctrl-f (it did nothing.
>- probably because it requires rig control).
>    However, somehow later the bandmap shifted to display range 21.100 to
>21.200 just when I needed 21.200~21.300...
>Can someone help me, please by telling me how to navigate the bandmap
>window?
>Many thanks, 
>Lukasz 

Moving the bandmap.

[Lukasz Olszewski]

Hi,

I apologise if this is a trivial question, but I've read the man page
multiple times and I cannot figure out how to move the bandmap display.

I have no rig control. My frequency is simply logged as 15m for example.

Today I was on 15m and the bandmap window was showing spots from 21.200 to
21.300. I needed to see ones below 21.200. I tried ctrl-f (it did nothing.
- probably because it requires rig control).

However, somehow later the bandmap shifted to display range 21.100 to
21.200 just when I needed 21.200~21.300...

Can someone help me, please by telling me how to navigate the bandmap
window?

Many thanks,
Lukasz

Re: graphical bandmap view

[EI6KW]

Hi,

Great idea!

For a while I trying to use simultaneously tlf and cqrlog's bandmap 
window amd rigctld fired up. Didn't try it in any contest yet but it 
looks that it is possible to get it working. Only problem for a while is 
that after clicking call sign in cqrlog's band map window focus is 
moving from tlf to new qso window in cqrlog but it is just one click to 
return to tlf.


W dniu 04.02.2021 o 19:19, Zoltan Csahok pisze:

In case one is interested in a non-curses bandmap for Tlf:
https://github.com/zcsahok/tlf_bandmap

73,
Zoli



--
73!
de Slav, EI6KW

FISTS #19019
SOC #1251
TRC #015-Ireland

Re: graphical bandmap view

[Nate Bargmann]

I don't see a Reply-to in the headers.  As I use neomutt, the L commands
lets me reply to a mailing list.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: graphical bandmap view

[Zoltan Csahok]

Hi Tom,

CW segment was for simplicity only. Now it's extended to SSB or full band watch.

73,
Zoli

Re: graphical bandmap view

[Zoltan Csahok]

Hi Drew,

I saw pyside also and the different licensing. Not sure about
the long term issues, but for the moment -and being a non-commercial
SW anyway- pyqt seems ok. Correct me if I'm wrong.

What was missing or done differently in tlf? Maybe we could learn from it.

73,
Zoli

(somehow when I reply to an email from the list it goes to the poster
instead of the list. I this just me? Or missing Reply-To:?)

Re: [Tlf/tlf] Bandmap improvements (#31)

[Thomas Beierlein]

Hi Fred,

the problem should be fixed in
https://github.com/dl1jbe/tlf/tree/fix_bandmap

I runs now stable with N8NOEs 7373 port with around 600 active spots.

73, de Tom DL1JBE

Am Tue, 2 Feb 2021 22:19:01 +0100
schrieb Fred Siegmund :

> Hi Tom, I will test at the weekend in EUDX contest with 'gdb'.
> 
> 73 Fred
> 
> Am 02.02.21 um 21:18 schrieb Thomas Beierlein:
> > Hi Fred,
> >
> > Just saw Zolis test results for the RBN. Normally bandmap seems to
> > be very stable even during large contests (at least with normal DX
> > cluster).
> >
> > There is one possible variation to test during next major contest.
> >
> > Prepare and build  tlf as follows and make sure to have the 'gdb'
> > debugger installed.
> >
> > CFLAGS="-g" ./configure --prefix=
> >
> > That will build tlf with debug information built in. Install the
> > program like normal and than start tlf with
> >
> > gdb path/to/tlf 
> >
> > Tlf should work like before but in case of a segmentation fault
> > stop in gdb's command line.
> >
> > Just do a 'bt' command for getting backtrack information and send us
> > the output. you can quit gdb afterwards with 'q'.
> >
> > 73, de Tom
> >
> >
> > Am Sun, 31 Jan 2021 13:40:10 +0100
> > schrieb Fred Siegmund :
> >  
> >> Also something I see from time to time (repeatedly):
> >>
> >> 73 Fred
> >>
> >> Am 31.01.21 um 12:58 schrieb Fred Siegmund:  
> >>> Hi Tom, i install always with --prefix option and start from /bin.
> >>> But its acually easier now to edit logcfg.dat, only that it is at
> >>> 2 locations was confusing (for me).
> >>>
> >>> For the bandmap crashes its kind of hard to reproduce, I always
> >>> use ARcluster like N8NOE, because of the great filtering options
> >>> (much better than with DXspider). I just notice that with high
> >>> load (like in major contests) it happens quite often. Right now
> >>> just dawdling in REF contest its no problem, I have no crashes.
> >>> Maybe there is some way to instrument the code, I just see
> >>> segmentation fault if it happens.
> >>>
> >>> 73 Fred
> >>>
> >>> Am 30.01.21 um 17:01 schrieb Thomas Beierlein:  
> >>>> Hi Fred,
> >>>>
> >>>> Am Sat, 30 Jan 2021 14:19:59 +0100
> >>>> schrieb Fred Siegmund :
> >>>> 
> >>>>> Also I noticed that logcfg.dat gets copied to the /bin directory
> >>>>> and used from there. Seems to be new.
> >>>>> 
> >>>> maybe by accident TLf got started there?
> >>>>
> >>>> It normally assumes to be started from a contest working
> >>>> directory. If there is no logcfg.dat in that directory old
> >>>> versions used the default (readonly) version
> >>>> (/usr/(local)/share/tlf/logcfg.dat). Newer version copies the
> >>>> default file into the actual directory so you can adapt it to
> >>>> your needs.
> >>>>
> >>>> 73, Tom
> >>>>
> >>>> P.S. How do you connect to the reverse beacon server? Maybe we
> >>>> can reproduce your problems
> >>>> 
> >>>>> 73 Fred
> >>>>>
> >>>>> Am 27.01.21 um 20:04 schrieb Zoltan Csahok:  
> >>>>>> @dh5fs <https://github.com/dh5fs> I suggest closing this issue
> >>>>>> (if the solution is OK) and opening a new one on further
> >>>>>> improvement options.
> >>>>>>
> >>>>>> —
> >>>>>> You are receiving this because you were mentioned.  
> >>>> 
> >
> >  
> 



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: [Tlf/tlf] Bandmap improvements (#31)

[Thomas Beierlein]

Hi Fred,

I think you can stop that tests. I can now reproduce the problem here
myself.

I am just looking for the problem. But it may take some time. So please
do not expect a quick solution.

73, de Tom DL1JBE

 Am Tue, 2 Feb 2021 22:19:01 +0100
schrieb Fred Siegmund :

> Hi Tom, I will test at the weekend in EUDX contest with 'gdb'.
> 
> 73 Fred
> 
> Am 02.02.21 um 21:18 schrieb Thomas Beierlein:
> > Hi Fred,
> >
> > Just saw Zolis test results for the RBN. Normally bandmap seems to
> > be very stable even during large contests (at least with normal DX
> > cluster).
> >
> > There is one possible variation to test during next major contest.
> >
> > Prepare and build  tlf as follows and make sure to have the 'gdb'
> > debugger installed.
> >
> > CFLAGS="-g" ./configure --prefix=
> >
> > That will build tlf with debug information built in. Install the
> > program like normal and than start tlf with
> >
> > gdb path/to/tlf 
> >
> > Tlf should work like before but in case of a segmentation fault
> > stop in gdb's command line.
> >
> > Just do a 'bt' command for getting backtrack information and send us
> > the output. you can quit gdb afterwards with 'q'.
> >
> > 73, de Tom
> >
> >
> > Am Sun, 31 Jan 2021 13:40:10 +0100
> > schrieb Fred Siegmund :
> >  
> >> Also something I see from time to time (repeatedly):
> >>
> >> 73 Fred
> >>
> >> Am 31.01.21 um 12:58 schrieb Fred Siegmund:  
> >>> Hi Tom, i install always with --prefix option and start from /bin.
> >>> But its acually easier now to edit logcfg.dat, only that it is at
> >>> 2 locations was confusing (for me).
> >>>
> >>> For the bandmap crashes its kind of hard to reproduce, I always
> >>> use ARcluster like N8NOE, because of the great filtering options
> >>> (much better than with DXspider). I just notice that with high
> >>> load (like in major contests) it happens quite often. Right now
> >>> just dawdling in REF contest its no problem, I have no crashes.
> >>> Maybe there is some way to instrument the code, I just see
> >>> segmentation fault if it happens.
> >>>
> >>> 73 Fred
> >>>
> >>> Am 30.01.21 um 17:01 schrieb Thomas Beierlein:  
> >>>> Hi Fred,
> >>>>
> >>>> Am Sat, 30 Jan 2021 14:19:59 +0100
> >>>> schrieb Fred Siegmund :
> >>>> 
> >>>>> Also I noticed that logcfg.dat gets copied to the /bin directory
> >>>>> and used from there. Seems to be new.
> >>>>> 
> >>>> maybe by accident TLf got started there?
> >>>>
> >>>> It normally assumes to be started from a contest working
> >>>> directory. If there is no logcfg.dat in that directory old
> >>>> versions used the default (readonly) version
> >>>> (/usr/(local)/share/tlf/logcfg.dat). Newer version copies the
> >>>> default file into the actual directory so you can adapt it to
> >>>> your needs.
> >>>>
> >>>> 73, Tom
> >>>>
> >>>> P.S. How do you connect to the reverse beacon server? Maybe we
> >>>> can reproduce your problems
> >>>> 
> >>>>> 73 Fred
> >>>>>
> >>>>> Am 27.01.21 um 20:04 schrieb Zoltan Csahok:  
> >>>>>> @dh5fs <https://github.com/dh5fs> I suggest closing this issue
> >>>>>> (if the solution is OK) and opening a new one on further
> >>>>>> improvement options.
> >>>>>>
> >>>>>> —
> >>>>>> You are receiving this because you were mentioned.  
> >>>> 
> >
> >  
> 



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: graphical bandmap view

[Thomas Beierlein]

Am Thu, 4 Feb 2021 20:19:22 +0100
schrieb Zoltan Csahok :

> In case one is interested in a non-curses bandmap for Tlf:
> https://github.com/zcsahok/tlf_bandmap
> 
> 73,
> Zoli
> 
> 

Looks nice. Especially as you can have more than one running for each
band.

As I see it is limited to CW at the moment. Is that be intention?


73, de Tom

-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: graphical bandmap view

[Nate Bargmann]

* On 2021 04 Feb 13:35 -0600, Zoltan Csahok wrote:
> In case one is interested in a non-curses bandmap for Tlf:
> https://github.com/zcsahok/tlf_bandmap

Neat!  Next up a CW skimmer!  ;-)

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: graphical bandmap view

[Juanjo EA8BGO]

wonderful!


El jue, 4 feb 2021 a las 19:34, Zoltan Csahok () escribió:

> In case one is interested in a non-curses bandmap for Tlf:
> https://github.com/zcsahok/tlf_bandmap
>
> 73,
> Zoli
>
>
>

graphical bandmap view

[Zoltan Csahok]

In case one is interested in a non-curses bandmap for Tlf:
https://github.com/zcsahok/tlf_bandmap

73,
Zoli

Re: [Tlf/tlf] Bandmap improvements (#31)

[Fred Siegmund]

Hi Tom, I will test at the weekend in EUDX contest with 'gdb'.

73 Fred

Am 02.02.21 um 21:18 schrieb Thomas Beierlein:

Hi Fred,

Just saw Zolis test results for the RBN. Normally bandmap seems to be
very stable even during large contests (at least with normal DX
cluster).

There is one possible variation to test during next major contest.

Prepare and build  tlf as follows and make sure to have the 'gdb'
debugger installed.

CFLAGS="-g" ./configure --prefix=

That will build tlf with debug information built in. Install the
program like normal and than start tlf with

gdb path/to/tlf 

Tlf should work like before but in case of a segmentation fault stop in
gdb's command line.

Just do a 'bt' command for getting backtrack information and send us
the output. you can quit gdb afterwards with 'q'.

73, de Tom


Am Sun, 31 Jan 2021 13:40:10 +0100
schrieb Fred Siegmund :


Also something I see from time to time (repeatedly):

73 Fred

Am 31.01.21 um 12:58 schrieb Fred Siegmund:

Hi Tom, i install always with --prefix option and start from /bin.
But its acually easier now to edit logcfg.dat, only that it is at 2
locations was confusing (for me).

For the bandmap crashes its kind of hard to reproduce, I always use
ARcluster like N8NOE, because of the great filtering options (much
better than with DXspider). I just notice that with high load (like
in major contests) it happens quite often. Right now just dawdling
in REF contest its no problem, I have no crashes. Maybe there is
some way to instrument the code, I just see segmentation fault if
it happens.

73 Fred

Am 30.01.21 um 17:01 schrieb Thomas Beierlein:

Hi Fred,

Am Sat, 30 Jan 2021 14:19:59 +0100
schrieb Fred Siegmund :
  

Also I noticed that logcfg.dat gets copied to the /bin directory
and used from there. Seems to be new.
  

maybe by accident TLf got started there?

It normally assumes to be started from a contest working
directory. If there is no logcfg.dat in that directory old
versions used the default (readonly) version
(/usr/(local)/share/tlf/logcfg.dat). Newer version copies the
default file into the actual directory so you can adapt it to your
needs.

73, Tom

P.S. How do you connect to the reverse beacon server? Maybe we can
reproduce your problems
  

73 Fred

Am 27.01.21 um 20:04 schrieb Zoltan Csahok:

@dh5fs <https://github.com/dh5fs> I suggest closing this issue
(if the solution is OK) and opening a new one on further
improvement options.

—
You are receiving this because you were mentioned.
  

Re: [Tlf/tlf] Bandmap improvements (#31)

[Fred Siegmund]

Yes, I also see that. Usually no problem as it disappears quite quickly.

73 Fred

Am 02.02.21 um 20:18 schrieb Zoltan Csahok:

Hi Fred,
I took the RBN spots from the last CQ WW and replayed them at a 10x 
speed to Tlf.
It didn't crash but some spots somehow get partially visible. Could be 
an issue with ncurses

or the way we use it.
The network code is nevertheless quite a mess, will need a review/rewrite.
73,
Zoli
*Sent:* Sunday, January 31, 2021 at 1:40 PM
*From:* "Fred Siegmund" 
*To:* tlf-devel@nongnu.org
*Subject:* Re: [Tlf/tlf] Bandmap improvements (#31)

Also something I see from time to time (repeatedly):

73 Fred

Am 31.01.21 um 12:58 schrieb Fred Siegmund:

Hi Tom, i install always with --prefix option and start from /bin.
But its acually easier now to edit logcfg.dat, only that it is at
2 locations was confusing (for me).

    For the bandmap crashes its kind of hard to reproduce, I always
use ARcluster like N8NOE, because of the great filtering options
(much better than with DXspider). I just notice that with high
load (like in major contests) it happens quite often. Right now
just dawdling in REF contest its no problem, I have no crashes.
Maybe there is some way to instrument the code, I just see
segmentation fault if it happens.

73 Fred

Am 30.01.21 um 17:01 schrieb Thomas Beierlein:

Hi Fred,

Am Sat, 30 Jan 2021 14:19:59 +0100
schrieb Fred Siegmund :

Also I noticed that logcfg.dat gets copied to the /bin
directory and
used from there. Seems to be new.

maybe by accident TLf got started there?

It normally assumes to be started from a contest working
directory. If
there is no logcfg.dat in that directory old versions used the
default
(readonly) version (/usr/(local)/share/tlf/logcfg.dat). Newer
version
copies the default file into the actual directory so you can
adapt it to
your needs.

73, Tom

P.S. How do you connect to the reverse beacon server? Maybe we can
reproduce your problems

73 Fred

Am 27.01.21 um 20:04 schrieb Zoltan Csahok:

@dh5fs <https://github.com/dh5fs> I suggest closing
this issue (if
the solution is OK) and opening a new one on further
improvement
options.

—
You are receiving this because you were mentioned.

Re: [Tlf/tlf] Bandmap improvements (#31)

[Thomas Beierlein]

Hi Fred,

Just saw Zolis test results for the RBN. Normally bandmap seems to be
very stable even during large contests (at least with normal DX
cluster).

There is one possible variation to test during next major contest. 

Prepare and build  tlf as follows and make sure to have the 'gdb'
debugger installed.

CFLAGS="-g" ./configure --prefix= 

That will build tlf with debug information built in. Install the
program like normal and than start tlf with

gdb path/to/tlf 

Tlf should work like before but in case of a segmentation fault stop in
gdb's command line.

Just do a 'bt' command for getting backtrack information and send us
the output. you can quit gdb afterwards with 'q'.

73, de Tom


Am Sun, 31 Jan 2021 13:40:10 +0100
schrieb Fred Siegmund :

> Also something I see from time to time (repeatedly):
> 
> 73 Fred
> 
> Am 31.01.21 um 12:58 schrieb Fred Siegmund:
> > Hi Tom, i install always with --prefix option and start from /bin.
> > But its acually easier now to edit logcfg.dat, only that it is at 2 
> > locations was confusing (for me).
> >
> > For the bandmap crashes its kind of hard to reproduce, I always use 
> > ARcluster like N8NOE, because of the great filtering options (much 
> > better than with DXspider). I just notice that with high load (like
> > in major contests) it happens quite often. Right now just dawdling
> > in REF contest its no problem, I have no crashes. Maybe there is
> > some way to instrument the code, I just see segmentation fault if
> > it happens.
> >
> > 73 Fred
> >
> > Am 30.01.21 um 17:01 schrieb Thomas Beierlein:  
> >> Hi Fred,
> >>
> >> Am Sat, 30 Jan 2021 14:19:59 +0100
> >> schrieb Fred Siegmund :
> >>  
> >>> Also I noticed that logcfg.dat gets copied to the /bin directory
> >>> and used from there. Seems to be new.
> >>>  
> >> maybe by accident TLf got started there?
> >>
> >> It normally assumes to be started from a contest working
> >> directory. If there is no logcfg.dat in that directory old
> >> versions used the default (readonly) version
> >> (/usr/(local)/share/tlf/logcfg.dat). Newer version copies the
> >> default file into the actual directory so you can adapt it to your
> >> needs.
> >>
> >> 73, Tom
> >>
> >> P.S. How do you connect to the reverse beacon server? Maybe we can
> >> reproduce your problems
> >>  
> >>> 73 Fred
> >>>
> >>> Am 27.01.21 um 20:04 schrieb Zoltan Csahok:  
> >>>> @dh5fs <https://github.com/dh5fs> I suggest closing this issue
> >>>> (if the solution is OK) and opening a new one on further
> >>>> improvement options.
> >>>>
> >>>> —
> >>>> You are receiving this because you were mentioned.  
> >>
> >>  



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: [Tlf/tlf] Bandmap improvements (#31)

[Fred Siegmund]

Also something I see from time to time (repeatedly):

73 Fred

Am 31.01.21 um 12:58 schrieb Fred Siegmund:
Hi Tom, i install always with --prefix option and start from /bin. But 
its acually easier now to edit logcfg.dat, only that it is at 2 
locations was confusing (for me).


For the bandmap crashes its kind of hard to reproduce, I always use 
ARcluster like N8NOE, because of the great filtering options (much 
better than with DXspider). I just notice that with high load (like in 
major contests) it happens quite often. Right now just dawdling in REF 
contest its no problem, I have no crashes. Maybe there is some way to 
instrument the code, I just see segmentation fault if it happens.


73 Fred

Am 30.01.21 um 17:01 schrieb Thomas Beierlein:

Hi Fred,

Am Sat, 30 Jan 2021 14:19:59 +0100
schrieb Fred Siegmund :


Also I noticed that logcfg.dat gets copied to the /bin directory and
used from there. Seems to be new.


maybe by accident TLf got started there?

It normally assumes to be started from a contest working directory. If
there is no logcfg.dat in that directory old versions used the default
(readonly) version (/usr/(local)/share/tlf/logcfg.dat). Newer version
copies the default file into the actual directory so you can adapt it to
your needs.

73, Tom

P.S. How do you connect to the reverse beacon server? Maybe we can
reproduce your problems


73 Fred

Am 27.01.21 um 20:04 schrieb Zoltan Csahok:

@dh5fs <https://github.com/dh5fs> I suggest closing this issue (if
the solution is OK) and opening a new one on further improvement
options.

—
You are receiving this because you were mentioned.

Re: [Tlf/tlf] Bandmap improvements (#31)

[Fred Siegmund]

Hi Tom, i install always with --prefix option and start from /bin. But 
its acually easier now to edit logcfg.dat, only that it is at 2 
locations was confusing (for me).


For the bandmap crashes its kind of hard to reproduce, I always use 
ARcluster like N8NOE, because of the great filtering options (much 
better than with DXspider). I just notice that with high load (like in 
major contests) it happens quite often. Right now just dawdling in REF 
contest its no problem, I have no crashes. Maybe there is some way to 
instrument the code, I just see segmentation fault if it happens.


73 Fred

Am 30.01.21 um 17:01 schrieb Thomas Beierlein:

Hi Fred,

Am Sat, 30 Jan 2021 14:19:59 +0100
schrieb Fred Siegmund :


Also I noticed that logcfg.dat gets copied to the /bin directory and
used from there. Seems to be new.


maybe by accident TLf got started there?

It normally assumes to be started from a contest working directory. If
there is no logcfg.dat in that directory old versions used the default
(readonly) version (/usr/(local)/share/tlf/logcfg.dat). Newer version
copies the default file into the actual directory so you can adapt it to
your needs.

73, Tom

P.S. How do you connect to the reverse beacon server? Maybe we can
reproduce your problems


73 Fred

Am 27.01.21 um 20:04 schrieb Zoltan Csahok:

@dh5fs <https://github.com/dh5fs> I suggest closing this issue (if
the solution is OK) and opening a new one on further improvement
options.

—
You are receiving this because you were mentioned.
  

Re: [Tlf/tlf] Bandmap improvements (#31)

[Thomas Beierlein]

Hi Fred,

Am Sat, 30 Jan 2021 14:19:59 +0100
schrieb Fred Siegmund :

> Also I noticed that logcfg.dat gets copied to the /bin directory and 
> used from there. Seems to be new.
> 
maybe by accident TLf got started there?

It normally assumes to be started from a contest working directory. If
there is no logcfg.dat in that directory old versions used the default
(readonly) version (/usr/(local)/share/tlf/logcfg.dat). Newer version
copies the default file into the actual directory so you can adapt it to
your needs.

73, Tom

P.S. How do you connect to the reverse beacon server? Maybe we can
reproduce your problems

> 73 Fred
> 
> Am 27.01.21 um 20:04 schrieb Zoltan Csahok:
> >
> > @dh5fs  I suggest closing this issue (if
> > the solution is OK) and opening a new one on further improvement
> > options.
> >
> > —
> > You are receiving this because you were mentioned.
> >  



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: [Tlf/tlf] Bandmap improvements (#31)

[Fred Siegmund]

Hi Zoli, just build from master. Working very well, thanks. 
Unfortunately, the bandmap seems not to be very stable, esp. under high 
spot load from reverse beacon. This was not the case in my previous 
master build but did also not improve. It seg faults quite often.


Also I noticed that logcfg.dat gets copied to the /bin directory and 
used from there. Seems to be new.


73 Fred

Am 27.01.21 um 20:04 schrieb Zoltan Csahok:


@dh5fs <https://github.com/dh5fs> I suggest closing this issue (if the 
solution is OK) and opening a new one on further improvement options.


—
You are receiving this because you were mentioned.

Re: [Tlf-devel] Fwd: Bandmap.

[Ervin Hegedüs]

Hi,

On Thu, Aug 13, 2015 at 08:59:33AM +0200, Tomasz Pabich wrote:
 Ervin of course most of trxes have memorys and vfo b, but not everyone.

I think (but I can't prove :)), a modern RIG, which has CAT interface,
that has a B VFO (but may be I'm wrong).

RIG memories is an unnecessary function in my opinion :), I've
never used that - I just wrote, that there is any other help.

 But
 more functions moved on keybord means less time sped to search something in
 rig. And of course not everyone have ft-1000 or other comfortable rig that
 have everything on fromt panel. Some rig eg. ft-817, its bit innoing to use
 it.in contest without good contest log.

yes, of course, you're absolutely right - I just want to understand the user
requirements, and see, what's the boundary conditions.

Anyway, I'm still not see why doesn't good the CTRL+A and CTRL+G
combinations to maintain the required stations (with or without
cluster).


73, Ervin

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Fwd: Bandmap.

[Tomasz Pabich]

Ervin of course most of trxes have memorys and vfo b, but not everyone. But
more functions moved on keybord means less time sped to search something in
rig. And of course not everyone have ft-1000 or other comfortable rig that
have everything on fromt panel. Some rig eg. ft-817, its bit innoing to use
it.in contest without good contest log.
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Fwd: Bandmap.

[Tomasz Pabich]

you are more concentrated on listening not on keyboard ;)
13 sie 2015 09:38 Ervin Hegedüs airw...@gmail.com napisał(a):

 Hi,

 On Thu, Aug 13, 2015 at 08:59:33AM +0200, Tomasz Pabich wrote:
  Ervin of course most of trxes have memorys and vfo b, but not everyone.

 I think (but I can't prove :)), a modern RIG, which has CAT interface,
 that has a B VFO (but may be I'm wrong).

 RIG memories is an unnecessary function in my opinion :), I've
 never used that - I just wrote, that there is any other help.

  But
  more functions moved on keybord means less time sped to search something
 in
  rig. And of course not everyone have ft-1000 or other comfortable rig
 that
  have everything on fromt panel. Some rig eg. ft-817, its bit innoing to
 use
  it.in contest without good contest log.

 yes, of course, you're absolutely right - I just want to understand the
 user
 requirements, and see, what's the boundary conditions.

 Anyway, I'm still not see why doesn't good the CTRL+A and CTRL+G
 combinations to maintain the required stations (with or without
 cluster).


 73, Ervin

 ___
 Tlf-devel mailing list
 Tlf-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tlf-devel

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Fwd: Bandmap.

[Pierre Fogal]

Earvin,

I'm saying the code would read the log and show me the stations near the
frequency.  In that case, I would set N to be something like 3600 and I
would see in a band-map all the stations worked near that frequency
(perhaps +/- 10 KHz) in the past hour or less.

I figured Tlf should work with rigctl and model 2, but my one attempt
didn't work and it seems my contest prep time is always limited by other
things and so I never tried again.  And I did download pydxcluster some
time ago, but I usually do contests unassisted and I forget to try it out
when doing other operating as cqrlog as a cluster built in.

Pierre

On Wed, Aug 12, 2015 at 4:56 PM, Ervin Hegedüs airw...@gmail.com wrote:

 Hi Perre,

 On Wed, Aug 12, 2015 at 09:38:15AM -0400, Pierre Fogal wrote:
  Hello Ervin, Tomasz,
 
  The problem I find is that after having cruised up and down a band
 several
  times, I basically forget the location of worked stations on the band.
  So, I will hear a station I can work, and then wait for the station to
 ID.
  With some operators, this can take awhile ;-)  So, if somehow I can see
  that in the past N minutes (N can be defined as it is now) I worked AB1CD
  on 14.240 as I approach 14.240 then I'll know not to wait too long as I
  likely worked him already.

 may be I don't understand something, but Tlf knows to handle
 this. First, most RIG has 2 VFO (and many memory's). If I hear a
 selected station, I just press A=B key on RIG, and moving away,
 if I don't hear the callsign. If I hear, then I press CTRL+A,
 which add the callsign to bandwith, and it stays till N secods
 (N is 900 in default in Tlf).

 So, it works - but as I wrote, may be I don't understand
 something.

  My thought initially on the Python add-on, was a simple gui or ncurses
  display that gave the current frequency and mapped worked calls before
 and
  after it.

 that's clear - but how do you connect it with Tlf? Do you want to
 read the log periodically?

  I figured Python, because that's mostly what I use these days
  (unless working on the hardware level with a need for speed) and Python
  makes it sooo much easier to deal with parsing of strings.

 That's true,

  I had once
  quickly  tried to run tlf using rigctld and the generic rig def (2?) but
  wasn't able to get that working and haven't gone back to it.  I'm
 thinking
  this would be the cleanest way to add secondary codes accessing the rig
  information.

 I'm sorry, but I don't understand this above - how relates this
 to Python, and Tlf bandmap?

 Anyway, in last year, I've made two contest in paralell: JI-DX CW
 and Gagarin Memorial (Russian contest). I've run two Tlf instances, but one
 RIG. I've configured Tlf RIG as like this:

 RIGMODEL=2
 RIGPORT=127.0.0.1

 in both instance, and run rigctld. That worked as very well.
 Cluster config must be defferent on the two instance, any other
 features worked (eg. netkeyer...)

  The ideas pointed to by Fred would also do most if not all of this, I
  think.
 
  Also on the Python front, I have written a number of scripts (using
  Ipython) to do post-contest scoring for some unsupported contests that
 are
  important to me, like the RAC Canada Day and Winter Contests, NAQP, IARU,
  and now IOTA.

 Take a look at this:

 https://sourceforge.net/projects/pydxcluster/

 may be that will be helps to you. And please share your
 experience with us :).

  As for N1MM logger ... I haven't actually used it since 2004.  I could
 use
  it here at home, but I can't justify it while on NA-008 as I would have
 to
  dedicate a pc to it. So, it's tlf for the win!

 good to hear :)


 73, Ervin

 --
 I � UTF-8

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Fwd: Bandmap.

[Ervin Hegedüs]

Hi Perre,

On Wed, Aug 12, 2015 at 09:38:15AM -0400, Pierre Fogal wrote:
 Hello Ervin, Tomasz,
 
 The problem I find is that after having cruised up and down a band several
 times, I basically forget the location of worked stations on the band.
 So, I will hear a station I can work, and then wait for the station to ID.
 With some operators, this can take awhile ;-)  So, if somehow I can see
 that in the past N minutes (N can be defined as it is now) I worked AB1CD
 on 14.240 as I approach 14.240 then I'll know not to wait too long as I
 likely worked him already.

may be I don't understand something, but Tlf knows to handle
this. First, most RIG has 2 VFO (and many memory's). If I hear a
selected station, I just press A=B key on RIG, and moving away,
if I don't hear the callsign. If I hear, then I press CTRL+A,
which add the callsign to bandwith, and it stays till N secods
(N is 900 in default in Tlf).

So, it works - but as I wrote, may be I don't understand
something.

 My thought initially on the Python add-on, was a simple gui or ncurses
 display that gave the current frequency and mapped worked calls before and
 after it. 

that's clear - but how do you connect it with Tlf? Do you want to
read the log periodically?

 I figured Python, because that's mostly what I use these days
 (unless working on the hardware level with a need for speed) and Python
 makes it sooo much easier to deal with parsing of strings. 

That's true,

 I had once
 quickly  tried to run tlf using rigctld and the generic rig def (2?) but
 wasn't able to get that working and haven't gone back to it.  I'm thinking
 this would be the cleanest way to add secondary codes accessing the rig
 information.

I'm sorry, but I don't understand this above - how relates this
to Python, and Tlf bandmap?

Anyway, in last year, I've made two contest in paralell: JI-DX CW
and Gagarin Memorial (Russian contest). I've run two Tlf instances, but one
RIG. I've configured Tlf RIG as like this:

RIGMODEL=2
RIGPORT=127.0.0.1

in both instance, and run rigctld. That worked as very well.
Cluster config must be defferent on the two instance, any other
features worked (eg. netkeyer...)

 The ideas pointed to by Fred would also do most if not all of this, I
 think.
 
 Also on the Python front, I have written a number of scripts (using
 Ipython) to do post-contest scoring for some unsupported contests that are
 important to me, like the RAC Canada Day and Winter Contests, NAQP, IARU,
 and now IOTA.

Take a look at this:

https://sourceforge.net/projects/pydxcluster/

may be that will be helps to you. And please share your
experience with us :).
 
 As for N1MM logger ... I haven't actually used it since 2004.  I could use
 it here at home, but I can't justify it while on NA-008 as I would have to
 dedicate a pc to it. So, it's tlf for the win!

good to hear :)


73, Ervin

-- 
I � UTF-8

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

[Tlf-devel] Fwd: Bandmap.

[Pierre Fogal]

Hello Ervin, Tomasz,

The problem I find is that after having cruised up and down a band several
times, I basically forget the location of worked stations on the band.
So, I will hear a station I can work, and then wait for the station to ID.
With some operators, this can take awhile ;-)  So, if somehow I can see
that in the past N minutes (N can be defined as it is now) I worked AB1CD
on 14.240 as I approach 14.240 then I'll know not to wait too long as I
likely worked him already.

My thought initially on the Python add-on, was a simple gui or ncurses
display that gave the current frequency and mapped worked calls before and
after it.  I figured Python, because that's mostly what I use these days
(unless working on the hardware level with a need for speed) and Python
makes it sooo much easier to deal with parsing of strings.  I had once
quickly  tried to run tlf using rigctld and the generic rig def (2?) but
wasn't able to get that working and haven't gone back to it.  I'm thinking
this would be the cleanest way to add secondary codes accessing the rig
information.

The ideas pointed to by Fred would also do most if not all of this, I
think.

Also on the Python front, I have written a number of scripts (using
Ipython) to do post-contest scoring for some unsupported contests that are
important to me, like the RAC Canada Day and Winter Contests, NAQP, IARU,
and now IOTA.

As for N1MM logger ... I haven't actually used it since 2004.  I could use
it here at home, but I can't justify it while on NA-008 as I would have to
dedicate a pc to it. So, it's tlf for the win!

73,
Pierre VE3KTB

On Tue, Aug 11, 2015 at 2:05 PM, Ervin Hegedüs airw...@gmail.com wrote:

 Hi Pierre,

 On Tue, Aug 11, 2015 at 10:06:10AM -0400, Pierre Fogal wrote:
  If you are looking to gauge interest, then a band-map that displays
 worked
  calls around your frequency as does N1MM logger would be a great
 feature, a
  boon to SP operation.

 sometimes I use N1MM (only from my club). Basicly, I don't like
 this feature in both direction. If we will touch this part of
 code of Tlf, may be it could be good to disjoin the directions:
 - op could configure, if he types a callsign (and do something
   which triggers the add function, eg. tune the VFO up/down
   minimum 1kHz), then callsign will be added
 - op could configure, if Tlf uses rigctl, and it gets the freq
   which exists in bandmap, then the callsign (which is on that
   freq) will be added back to callsign field

 More features, if we will touch the code:
 - bandmap columns scrolling: now there are 3 columns for bandmap,
   but on most contest, these are very few for the number of
   competitors. It could be good, than Tlf follows the freq of
   TRX, and detects that the freq leaves the freq of last station
   in first column, then shifts columns to left
 - mark the nearest stations on bandmap with different background
   (or something else), or if there isn't any station between N
   kHz, then mark the previous and next nearest (with other sign)

 Other ideas are welcome.


  I was thinking of trying to write something like
  that as an add-on Python program.

 How do you think about it? What do you think about the add-on
 program?

 (Otherwise, I'm a big Python fan :))

  I saw a stat that suggested that less than 20% of operators in a contest
  ever call CQ.  I call, but not as much as I do SP given the little
  pistol nature of my station(s).   So, I would guess that any assistance
 on
  the SP side would help many users. :-)

 yes, bandmap is a big help. I've used that on WAE, and Tlf showed
 the number of QTC's, what a station gave me - that was a _very_
 big help. Idea came from DJ1YFK (thanks Fabian :)).


 73, Ervin


 --
 I � UTF-8

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Tomasz Pabich]

Yes I know that, and I use that, but i mean that functiom should work
automaicly (as an option) like in TRlog or N1MM
When you have radio connected via hamlib and looking around on band, when
frequency is similiar +/-100Hz ( that allso should.be configurable) the
callsign field fills automaticly :)
11 sie 2015 08:49 Ervin Hegedüs airw...@gmail.com napisał(a):

 Hi Tomasz,

 On Tue, Aug 11, 2015 at 01:52:53AM +0200, Tomasz Pabich wrote:
  Are they some plan to add automtic fill callsign from bandmap in SP mode
  ?? also autoadding spot to bandmap when you heard somebody and wat to
 back
  later. Both propositions are timesavers for opertors.

 yes, these are implemented.

 If you're working in SP mode, and you hear a station with too
 heavy pile up, you can put it to your bandmap with CTRL+A (I
 think that means ADD). These callsigns signed it with a *
 (asterix) character, then you can see, those are your own spots.

 Then you can grab the callsigns from bandmap with CTRL+G (what
 possible means GRAB :)), sequentially. CTRL+G grabs not just
 your own spots, it reads all BUT NOT WORKED callsigns. CTRL+G
 works circurally, that means if you grab the last callsign from
 your visible bandmap, then the next CTRL+G will load the first
 callsign again from your visible bandmap.

 Worked callsigns seems with lower case form, and they are with
 black color.

 If you work in non-assisted mode, and you didn't configured
 cluster, the own-spot-handling feature is works as well.


 Hope this helps to you,


 73, Ervin



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Ervin Hegedüs]

Hi Tomasz,

On Tue, Aug 11, 2015 at 01:52:53AM +0200, Tomasz Pabich wrote:
 Are they some plan to add automtic fill callsign from bandmap in SP mode
 ?? also autoadding spot to bandmap when you heard somebody and wat to back
 later. Both propositions are timesavers for opertors.

yes, these are implemented.

If you're working in SP mode, and you hear a station with too
heavy pile up, you can put it to your bandmap with CTRL+A (I
think that means ADD). These callsigns signed it with a *
(asterix) character, then you can see, those are your own spots.

Then you can grab the callsigns from bandmap with CTRL+G (what
possible means GRAB :)), sequentially. CTRL+G grabs not just
your own spots, it reads all BUT NOT WORKED callsigns. CTRL+G
works circurally, that means if you grab the last callsign from
your visible bandmap, then the next CTRL+G will load the first
callsign again from your visible bandmap.

Worked callsigns seems with lower case form, and they are with
black color.

If you work in non-assisted mode, and you didn't configured
cluster, the own-spot-handling feature is works as well.


Hope this helps to you,


73, Ervin



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Pierre Fogal]

If you are looking to gauge interest, then a band-map that displays worked
calls around your frequency as does N1MM logger would be a great feature, a
boon to SP operation.  I was thinking of trying to write something like
that as an add-on Python program.

I saw a stat that suggested that less than 20% of operators in a contest
ever call CQ.  I call, but not as much as I do SP given the little
pistol nature of my station(s).   So, I would guess that any assistance on
the SP side would help many users. :-)

Thanks again to all the tlf developers!

73,
Pierre VE3KTB sometimes /VY0 from NA-008

On Tue, Aug 11, 2015 at 12:18 AM, Thomas Beierlein dl1...@gmail.com wrote:

 Hi Tomek,
 yes, in next weeks there will be more work on the bandmap logic.

 - adding spots to bandmap is already possible - type in call and press
   ctrl-a.

 - 'automatic fill in' is not supported yet, but on the list of
   extensions.

 73, de Tom DL1JBE

 Am Tue, 11 Aug 2015 01:52:53 +0200 schrieb Tomasz Pabich sq7...@gmail.com
 :

  Are they some plan to add automtic fill callsign from bandmap in SP
  mode ?? also autoadding spot to bandmap when you heard somebody and
  wat to back later. Both propositions are timesavers for opertors.
 
  Tomek ex. SQ7IQI
  http://sp7q.blogspot.com
  http://sp7kzk.blogspot.com
  The Art of Morse Code



 --
 Do what is needful!
 Ursula LeGuin: Earthsea
 --


 ___
 Tlf-devel mailing list
 Tlf-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tlf-devel

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Thomas Beierlein]

Hi Tomek,
yes, in next weeks there will be more work on the bandmap logic. 

- adding spots to bandmap is already possible - type in call and press
  ctrl-a. 

- 'automatic fill in' is not supported yet, but on the list of
  extensions.

73, de Tom DL1JBE

Am Tue, 11 Aug 2015 01:52:53 +0200 schrieb Tomasz Pabich sq7...@gmail.com:

 Are they some plan to add automtic fill callsign from bandmap in SP
 mode ?? also autoadding spot to bandmap when you heard somebody and
 wat to back later. Both propositions are timesavers for opertors.
 
 Tomek ex. SQ7IQI
 http://sp7q.blogspot.com
 http://sp7kzk.blogspot.com
 The Art of Morse Code



-- 
Do what is needful!
Ursula LeGuin: Earthsea
--


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Ervin Hegedüs]

Hi Pierre,

On Tue, Aug 11, 2015 at 10:06:10AM -0400, Pierre Fogal wrote:
 If you are looking to gauge interest, then a band-map that displays worked
 calls around your frequency as does N1MM logger would be a great feature, a
 boon to SP operation. 

sometimes I use N1MM (only from my club). Basicly, I don't like
this feature in both direction. If we will touch this part of
code of Tlf, may be it could be good to disjoin the directions:
- op could configure, if he types a callsign (and do something
  which triggers the add function, eg. tune the VFO up/down
  minimum 1kHz), then callsign will be added
- op could configure, if Tlf uses rigctl, and it gets the freq
  which exists in bandmap, then the callsign (which is on that
  freq) will be added back to callsign field

More features, if we will touch the code:
- bandmap columns scrolling: now there are 3 columns for bandmap,
  but on most contest, these are very few for the number of
  competitors. It could be good, than Tlf follows the freq of
  TRX, and detects that the freq leaves the freq of last station
  in first column, then shifts columns to left
- mark the nearest stations on bandmap with different background
  (or something else), or if there isn't any station between N
  kHz, then mark the previous and next nearest (with other sign)

Other ideas are welcome.


 I was thinking of trying to write something like
 that as an add-on Python program.

How do you think about it? What do you think about the add-on
program?

(Otherwise, I'm a big Python fan :))
 
 I saw a stat that suggested that less than 20% of operators in a contest
 ever call CQ.  I call, but not as much as I do SP given the little
 pistol nature of my station(s).   So, I would guess that any assistance on
 the SP side would help many users. :-)

yes, bandmap is a big help. I've used that on WAE, and Tlf showed
the number of QTC's, what a station gave me - that was a _very_
big help. Idea came from DJ1YFK (thanks Fabian :)).
 

73, Ervin


-- 
I � UTF-8

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Ervin Hegedüs]

Hi Fred,

On Tue, Aug 11, 2015 at 10:23:36PM +0200, Fred Siegmund wrote:
 Have a look here: https://github.com/Tlf/tlf/issues/31
 
 Some proposals for the bandmap...

yep, good ideas!


Thanks,


73, Ervin


-- 
I � UTF-8

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] Bandmap.

[Fred Siegmund]

Have a look here: https://github.com/Tlf/tlf/issues/31

Some proposals for the bandmap...

73 Fred

---
Am 11.08.2015 8:05 nachm. schrieb Ervin Hegedüs airw...@gmail.com:

 Hi Pierre,

 On Tue, Aug 11, 2015 at 10:06:10AM -0400, Pierre Fogal wrote:
  If you are looking to gauge interest, then a band-map that displays worked
  calls around your frequency as does N1MM logger would be a great feature, a
  boon to SP operation.

 sometimes I use N1MM (only from my club). Basicly, I don't like
 this feature in both direction. If we will touch this part of
 code of Tlf, may be it could be good to disjoin the directions:
 - op could configure, if he types a callsign (and do something
   which triggers the add function, eg. tune the VFO up/down
   minimum 1kHz), then callsign will be added
 - op could configure, if Tlf uses rigctl, and it gets the freq
   which exists in bandmap, then the callsign (which is on that
   freq) will be added back to callsign field

 More features, if we will touch the code:
 - bandmap columns scrolling: now there are 3 columns for bandmap,
   but on most contest, these are very few for the number of
   competitors. It could be good, than Tlf follows the freq of
   TRX, and detects that the freq leaves the freq of last station
   in first column, then shifts columns to left
 - mark the nearest stations on bandmap with different background
   (or something else), or if there isn't any station between N
   kHz, then mark the previous and next nearest (with other sign)

 Other ideas are welcome.

  I was thinking of trying to write something like
  that as an add-on Python program.

 How do you think about it? What do you think about the add-on
 program?

 (Otherwise, I'm a big Python fan :))

  I saw a stat that suggested that less than 20% of operators in a contest
  ever call CQ.  I call, but not as much as I do SP given the little
  pistol nature of my station(s).   So, I would guess that any assistance on
  the SP side would help many users. :-)

 yes, bandmap is a big help. I've used that on WAE, and Tlf showed
 the number of QTC's, what a station gave me - that was a _very_
 big help. Idea came from DJ1YFK (thanks Fabian :)).

 73, Ervin

 -- 
 I � UTF-8

 ___
 Tlf-devel mailing list
 Tlf-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tlf-devel
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel