Re: [Tlf-devel] IARU HF

[FS]

Attached my rules file. Please adjust the path to the mult file. I don't 
care too much about correct scoring, so there might be improvements 
possible.


73 Fred

On 7/13/19 6:40 AM, FS wrote:
Hi guys, get ready for the IARU contest this weekend. Use the attached 
file for some help with society names with INITIAL_EXCHANGE. I needed to 
sort that keyword somewhere at the end of the rules file, right after 
CONTEST_MODE it did have no effect.


73 Fred

# General contest mode #

#
CONTEST=iaruhf
LOGFILE=iaruhf.log
CABRILLO=UNIVERSAL
CONTEST_MODE
#
#
##
##
#  Messages F1= to F12=  #
#  Message CQ_TU_MSG=#
#  Message S_TU_MSG=   #
##
#  % = call  #
#  @ = hiscall   #
#  # = serial#
#  [ = RST   #
#  + = increase cw speed #
#  - = decrease cw speed #
##
##
#
F1=CQ TEST DE % % TEST
F2=DE %
F3=@ +++5NN---28
F4=TU % 
F5=@
F6=%
F7=@ SRI QSO B4 GL
F8=AGN
F9=?
F10= QRZ?
F11= PSE K
F12=TEST % %
#
CQ_TU_MSG=TU % 
S_TU_MSG=TU +++5NN---28
MY_COUNTRY_POINTS=1
MY_CONTINENT_POINTS=3
DX_POINTS=5
ITUMULT
INITIAL_EXCHANGE=/tmp/tlf-master/bin/iaruhfmults
RECALL_MULTS
#
#ALT_0=
#ALT_1=
#ALT_2=
#ALT_3=
#ALT_4=
#ALT_5=
#ALT_6=
#ALT_7=
#ALT_8=
#ALT_9=
#
#SEND_DE
#
### END #

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

[Tlf-devel] IARU HF

[FS]

Hi guys, get ready for the IARU contest this weekend. Use the attached 
file for some help with society names with INITIAL_EXCHANGE. I needed to 
sort that keyword somewhere at the end of the rules file, right after 
CONTEST_MODE it did have no effect.


73 Fred
3V8CB,ARAT
4K7Z,FRS
4L0HQ,NARG
4O1HQ,MARP
4V0HQ,RCH
4X4ARC,IARC
5C8A,ARRAM
5Z4RS,ARSK
7X2HQ,ARA
8N1HQ,JARL
8N2HQ,JARL
8N3HQ,JARL
8N6HQ,JARL
8N8HQ,JARL
8Q7TM,AC
9A0HQ,HRS
9K2RR,R1
9K9HQ,KARS
9M2A,MARTS
9V9HQ,SARTS
9Y4HQ,TTARS
9Y4X,R2
A25HQ,BARS
A47RS,ROARS
A71HQ,QARS
AT1HQ,ARSI
B0HQ,CRAC
B1HQ,CRAC
B2HQ,CRAC
B3HQ,CRAC
B4HQ,CRAC
B5HQ,CRAC
B6HQ,CRAC
B7HQ,CRAC
BV0HQ,CTARL
C4HQ,CARS
C91HQ,LREM
CE3AA,RCCH
CR5HQ,REP
CX1AA,RCU
DA0HQ,DARC
DJ3HW,R1
DX0HQ,PARA
E2HQ,RAST
E7HQ,ARABH
EF4HQ,URE
EI0HQ,IRTS
EK0HQ,FRRA
EL2BEN,LRAA
EM5HQ,UARL
ER7HQ,ARM
ES9A,ERAU
ES9HQ,ERAU
ET3AA,EARS
EW5HQ,BFRR
F4GKR/P,R1
G5W,AC
GR2HQ,RSGB
HB0HQ,AFVL
HB9HQ,USKA
HB9JOE,R1
HC2CRC,GRC
HG0HQ,MRASZ
HI3RCD,RCD
HK3LR,LCRA
HL0HQ,KARL
HL1AQQ,R3
HP0HQ,LPRA
HQ2W,RCH
HU0YS,CRAS
IO0HQ,ARI
IO1HQ,ARI
IO2HQ,ARI
IO4HQ,ARI
IO5HQ,ARI
IO6HQ,ARI
IO8HQ,ARI
IO9HQ,ARI
IV3KKW,R1
J73Z,DARCI
J87HQ,SVGRS
JA1CJP,R3
JE1MUI,R3
JF1RPZ,R3
JT1KAA,MRSF
K0QB,R2
K1ZZ,AC
LM90HQ,NRRL
LU0HQ,RCA
LU4AA,R2
LX8HQ,RL
LY0HQ,LRMD
LZ0HQ,BFRA
NU1AW,IARU
OA4O,RCP
OE0HQ,OVSV
OH2HQ,SRAL
OL9HQ,CRC
OM8HQ,SARA
OP0HQ,UBA
OY1CT,FRA
OZ1HQ,EDR
P40HQ,AARC
PA6HQ,VERON
PB2T,R1
PJ2HQ,VRONA
PT2ADM,R2
R9HQ,SRR
S50HQ,ZRS
SE9HQ,SSA
SM6EAN,R1
SN0HQ,PZK
SU1SK,ERASD
SX0HQ,RAAG
T40HQ,FRC
T70HQ,ARRSM
TC3HQ,TRAC
TF3HQ,IRA
TG0AA,CRAG
TI0HQ,RCCR
TM0HQ,REF
TU2CI,ARAI
UN1HQ,KFRR
V31HQ,BARC
V55HQ,NARL
V8FEO,BDARA
VA2RAC,RAC
VA3RAC,RAC
VE1RAC,RAC
VE3YV,R2
VE4RAC,RAC
VE5RAC,RAC
VE6RAC,RAC
VE6SH,AC
VE7RAC,RAC
VE8RAC,RAC
VE9RAC,RAC
VK3MV,R3
VO1RAC,RAC
VO2RAC,RAC
VP2M,MARS
VP2V,BVIRL
VP9HQ,RSB
VR2HK,HARTS
VU2GMN,R3
VY0RAC,RAC
VY1RAC,RAC
VY2RAC,RAC
W1AW/7,ARRL
XE1KK,R2
XE1LM,FMRE
XR3HQ,RCCH
XV4Y,VARC
XX9A,ARM
YB0AZ,R3
YE0HQ,ORARI
YL4HQ,LRAL
YR0HQ,FRR
YS0YS,CRAS
YS1MS,R2
YT0HQ,SRS
YV5AJ,RCV
YV5AM,R2
Z30HQ,RSM
Z32TO,R1
Z60A,SHRAK
ZA1A,AARA
ZF1A,CARS
ZL2TLL,R3
ZL6HQ,NZART
ZP5AA,RCP
ZS4BS,R1
ZS9HQ,SARL
ZW0HQ,LABRE
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] CBR/adif import

[FS]

No doubt, it would be .CBR We have a contest logger! I would like to use it to 
switch logs between several programms.

73 Fred


Am 27.05.2017 10:00 vorm. schrieb Ervin Hegedüs <airw...@gmail.com>:
>
> Hi Fred, 
>
> On Fri, May 26, 2017 at 09:46:29PM +0200, FS wrote: 
> > Hi guys, is there any way to import a .CBR or .adif file? I never missed 
> > it, but now.. 
>
> I'm afraid that currently no such feature - but it's not so big 
> work to implement. Which one would be better, CBR or ADI? 
>
>
> 73, Ervin 
>
>
> -- 
> I � UTF-8 
>
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

[Tlf-devel] CBR/adif import

[FS]

Hi guys, is there any way to import a .CBR or .adif file? I never missed it, 
but now..

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

Re: [Tlf-devel] TLF Bugs

[FS]

Great!

Thanks,
Fred DH5FS/DM3F

On 10/26/2016 05:30 AM, Thomas Beierlein wrote:

As a short continuation

The bug was found in meantime but still needs a proper solution. I hope
to work on it next weekend.

In meantime please use the setting of BMAUTOGRAB as suggested below.

73, de Tom DL1JBE


Am Sun, 16 Oct 2016 09:53:00 +0200
schrieb Thomas Beierlein :


Am Sat, 15 Oct 2016 15:12:31 +0200
schrieb Fred Siegmund :


Hi, some problems with the actual master branch, found during
preparation for the WAG contest:
-G does not show the call anymore in the callsign field, when
grabbing the next call > must be a bug?


Sorry for late reply - junst coming home from a business trip.

Thanks for pointing out the problem. For now setting BMAUTOGRAB in
logcfg.dat should help.

73, Tom DL1JBE


When using a initial_exchange file it would be better, if it is in
place to show just somewhere the exchange and not to put it in the
exchange field. Because like in WAG you are getting DOKs and serial
numbers and with RECALL_MULTS it shows also the serial numbers
(which you don't want).

73 Fred

___
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

[Tlf-devel] WAE EU side Re: WAE experiences

[FS]

Hi Ervin,

the WAE edition of TLF worked great. I recorded in total 86 .wav files, 
now I just have the problem to rehear them all. :-) Some more points:

* how to stop recording in case it was accidentally started?
i had several cases where I had to kill the process

* some guys start with time 0010, and then give only the minutes, like 
11, 12 etc. so it could be nice if there are only two numbers in, TLF 
takes this as minutes and the hours from the first entry


Otherwise good short skip to HA, I heard HA2OS very well :-)

73 Fred

ps. thanks for updating py merging script soon, until then iam busy with 
QTC listening



On 08/10/2015 07:13 PM, Ervin Hegedüs wrote:

Hi everyone,

so, there was the WAE CW contest at last weekend, any if anybody
wanted to receive QTC's, this was the second chance to do it with
Tlf :).

I'll make a summary about the contest related to Tlf, but now,
please if anybody used Tlf on WAE, just share the experience with
us!

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] Wiki

[FS]

New users may don't know github or repos at all. They want to download a 
software, use it and get infos about it as easy as possible (eg. through 
a wiki or up to date static page). If we think github is the right place 
for all this ok, for me its a place to host code. But maybe we should 
start with that, otherwise we get another 100 proposals which wiki to 
use and so on... :)


73 Fred

On 01/06/2015 07:12 AM, Ervin Hegedüs wrote:

Hello,

On Mon, Jan 05, 2015 at 10:42:15PM +0100, Fred Siegmund wrote:

Ervin, can you register something like tlflogger.net and link to
http://tlf.github.io/index2.html? This site could be edited then by
several people (after registration, ok). But a serious wiki needs a
login as well. Can we save the content from wikispaces somehow?


Could github.io handle the external hostname? I mean, if I
register a domain name (tlflogger.net was just a sudden idea :)),
I can set up the with or without www A records to tlf.github.io
- but it must to configure the github.io HTTP server to handle
this (or these) hostnames (www.tlflogger.net or tlflogger.net).

Another solution could be I made a virtual host one of my server,
and set up an HTTP redirect - but that's not so nice...

Anyway, why tlf.github.io isn't good?


73,

Ervin
HA2OS




Am 05.01.2015 um 20:54 schrieb Ervin Hegedüs:

Hi all,

On Mon, Jan 05, 2015 at 07:52:03PM +0100, Fred Siegmund wrote:

Wikidot HAS ads. Probably Ervin has a adblocker on, what i took as
motivation to install it also now. :-) Thanks.


yes, I have it :)



http://en.wikipedia.org/wiki/Comparison_of_wiki_hosting_services


oh', I've missed out to include this link from my first anwser in
this thread :)


My vote:
https://meta.orain.org/wiki/Main_Page/en


looks like also useful - but I can't choose anyone.

As I proposed - choose a domain name (eg. tlflogger.net), and
I can ensure the hosting (in Hungary).


73,


Ervin
HA2OS





Am 05.01.2015 um 18:19 schrieb Ed:

On 01/05/2015 11:57 AM, Ervin Hegedüs wrote:



What do I have to do, to see any ad? I mean, a regular user how
can see any ad on wikidot? The owner of wiki page sets the Google
Ads source? Or how?


thanks,

73:

Ervin
HA2OS


Maybe Rein can fill us in how it works. Or someone could spend some time
going through the documentation.

I moderate both of the fldigi related Yahoo groups as well as try to
keep the wiki updated, so I just wouldn't have the time.

Ed W3NR


___
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




___
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

[Tlf-devel] Wiki

[FS]

Hi TLF users, maybe someone has noticed that the wiki at wikispaces is 
not useable anymore and probably will not be in the future. So the need 
for a dedicated homepage/wiki? is more urgent then ever.



73 Fred



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

Re: [Tlf-devel] IARU rules?

[FS]

Hi Mike, see attachment.

73 Fred

On 07/12/2014 12:04 PM, Mike Waters wrote:

Hello,

What would be the rules and configuration for the IARU contest today for
TLF?

http://www.hornucopia.com/contestcal/weeklycont.php#5425
http://www.arrl.org/iaru-hf-championship

Thanks,
Mike
www.w0btu.com http://www.w0btu.com


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


# General contest mode #

#
CONTEST=iaruhf
LOGFILE=iaruhf.log
CONTEST_MODE
#
#
##
##
#  Messages F1= to F12=  #
#  Message CQ_TU_MSG=#
#  Message SP_TU_MSG=   #
##
#  % = call  #
#  @ = hiscall   #
#  # = serial#
#  [ = RST   #
#  + = increase cw speed #
#  - = decrease cw speed #
##
##
#
F1=CQ TEST DE % % TEST
F2=DE %
F3=@ +++5NN---28
F4=TU % 
F5=@
F6=%
F7=@ SRI QSO B4 GL
F8=AGN
F9=?
F10= QRZ?
F11= PSE K
F12=TEST % %
#
CQ_TU_MSG=TU % 
SP_TU_MSG=TU +++5NN---28
MY_COUNTRY_POINTS=1
MY_CONTINENT_POINTS=3
DX_POINTS=5
ITUMULT
#
#ALT_0=
#ALT_1=
#ALT_2=
#ALT_3=
#ALT_4=
#ALT_5=
#ALT_6=
#ALT_7=
#ALT_8=
#ALT_9=
#
#SEND_DE
#
### END #

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

[Tlf-devel] TLF mit SDR

[FS]

Check it out: TLF 2.0 ;-)


http://dh5ym.hopto.org/wiki/?p=1088


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

Re: [Tlf-devel] TLF RTTY

[FS]

I agree that the LF after the macro could be skipped. But 2 LFs in place 
before I find useful, to start on a clean line. 73 Fred from 
https://github.com/Tlf/tlf/blob/master/ChangeLog 2012-10-13 Thomas 
Beierlein

* src/write_keyer.c: shorten macro output in digimode
  - old implementation had 5 empty lines for each macro output
(1 from message eol, 2 from write_keyer routine, 1 from echo,
1 from fldigi)
  - dropped 1 of the lines in output string
  - used '-n' switch to force echo to not append a further newline
  - simplify command formatting

Am 04.01.2014 16:14, schrieb Ed:

On 01/04/2014 10:02 AM, Ervin Hegedüs - HA2OS wrote:


ok, I think I understand - but can't reproduce that.

What do you mean when you say Tlf macro? You mean the F1..F12
shortkeys? Eg. CQ, DE, RST, 73, ... and so on macros?


Yes


I've checked all of them, from F1 to F9, and as you wrote: Tlf
sends an LF _before_ sends macro, and after it sends also an LF -
but only 3, not 6 to 8...


well 3 at the start and 3 at the end = 6, so the other op sees a total 
of 7 lines, with only 1 with the macro contents.


Needs to be 1 at start and 1 after.


Note, that 3 LF are enough to run out the text... Is that your problem?


Yes, exactly.


73,


Ervin
HA2OS



Ed W3NR





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

Re: [Tlf-devel] TLF RTTY

[FS]

Ed, this has been fixed. Use a actual version.

73 Fred
Am 03.01.2014 20:55, schrieb Ed:
Will be unuseable. It is not good operating practice to send 6 to 8 
linefeeds for one sent macro. Other ops will need to chase you on the 
screen, if you already have not scrolled off.


This is from the changelog::

tlf-0.9.30
==
Bug fixes:
- exchange needed at least 1 character in dxped mode

RTTY miniterm changed to display line feeds (reading formatted texst 
is easier)

RTTY now sends linefeeds before and after the macro.

Wish I knew where and how many.

Ed W3NR

___
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

[Tlf-devel] Quick mode change and other short cuts

[FS]

I would feel sorry if the decision is now not to do anything because 
saving important keys for some unknown function in the future.


I would go for any combination that toggles through the 3 modes. We will 
never find a optimum key for everybody on every international keyboard.


When talking about import functions: going through the bandmap with
CTRL+G in one direction is no good. For assisted contesting this must be 
as handy as possible. What about ALT+arrow up and ALT+arrow down to move 
in both directions through the bandmap?


73 Fred


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

Re: [Tlf-devel] CQWW result

[FS]

The best quick start guide is this: 
http://home.iae.nl/users/reinc/tlf/tlfdoc-0.9.9/tlfdoc.html Certainly a 
good starting point to develop this document further. The problem is 
that a lot of information is scattered over the internet, best would be 
to have a dedicated webpage (wiki). If that can be hosted at github, 
maybe there.


73 Fred

On 11/27/2013 08:48 PM, Ed wrote:

On Wed, 27 Nov 2013 21:26:03 +0100
Ervin Hegedüs - HA2OS airw...@gmail.com wrote:


On Wed, Nov 27, 2013 at 02:34:39PM -0500, Ed wrote:

On Wed, 27 Nov 2013 19:59:49 +0100
Thomas Beierlein t...@forth-ev.de wrote:



Simply try '='. That does what you look for. And '_' resends the
last number. I know it is only documented on Rein's old web site.
So maybe we should write a 'getting started' manual which
includes these tips.

73, de Tom DL1JBE.


Already on the man page.


RTFM and HOWTO/Getting started page are not equals :)


I prefer a good howto-start-to-use-Tlf page, with many
examples. I use Tlf a half year, made some patch, usually
read the code - but it still contains new things for me.


73,

Ervin
HA2OS

ps: 630 QSO on CQ-WW-CW, on 5 bands, in SO-ALL-LOW (non-assisted)




First CW contest since 1997 and the first with TLF other than RTTY. Had
a lot of trial and error mainly editing macros and logcfg.

Never used a bandmap and grab before, quite a big help. Did just SP.

The winkey server was a pain as I would forget to start it.

Any thoughts of maybe a wiki ? I referred to the man page quite a bit.

Ed W3NR















___
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] Cluster Question

[FS]

I think he has LAN activated. This is how TLF shares the QSOs between 
the nodes.


73 Fred

On 11/13/2013 06:18 AM, Thomas Beierlein wrote:

Hi Ed,

Am Tue, 12 Nov 2013 14:43:35 -0500
schrieb Ed aut...@gmail.com:


In SP when I log a qso, this appears in the cluster window

  DX de TLF-

What is it, ad what does it do ?


It sounds not as intended. Let me check where it is coming from. Btw,
which version do you use?

73, de Tom DL1JBE


Thanks

Ed W3NR

___
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

[Tlf-devel] Keys Re: WAEDC QTC - v0.002 release :)

[FS]

My proposal would be to have a ALT combination for change mode to speed 
up logging. To type :cwm and :ssb back and forth can be annoying.
I dont care about exact scoring, there are other tools ;-) But the 
programm should give a idea if you are short of mults, but that works 
for me.


73 Fred

On 11/05/2013 11:02 AM, Thomas Beierlein wrote:

Hi Martin and others,

I agree that tlf has a lot of Ctrl- and Alt-key combinations for
various control functions (e.g. turning on and off different windows)
- some of them may be not needed at all - but I do not see much of them
in normal contest operation.

I had a look at the trlog manual in meantime and there are also a lot
of that ALT- and Ctrl-key combinations. Where do you see the difference.
I would be glad to hear you suggestions for the keyboard interface.
Maybe we miss some of your points here.

It would be good if you could say which basic functionality has to work
with as few key strokes as possible and what is seldom needed (and can
require more keyboard work or maybe a menu access).


The scoring is a really bad point in the actual implementation. But as
the logic to do it is scattered around nearly a dozen places in the
program it is difficult to change. I have some ideas for a  complete
overhaul of that scoring problem - but that is another thread. It will
require also a complete change of the configuration and contest rule
base. I will try to summarize my ideas in the next time here.

For the autosend problem - see my other mail on the thread.

73, de Tom DL1JBE.


Am Sun, 03 Nov 2013 19:40:16 +0100
schrieb Martin Kratoska mar...@centrum.cz:

Hi all,

with highest respect to all the work already done, I suggest to focus
all our potential to CW and SSB modes and the usual options to get
*finally* an useful, mature contesting program for Linux. tlf still
has some bottlenecks, in many contests is possible to enter the event
but scoring does not work properly, missing the autosend option (in
the same way as TRlog N6TR does), spotting is a pain etc. The quality
of a program strongly depends on the ergonomics - the typing should
be minimized as well as the keyboard schedule should single stroke
commands (ie. no Ctrl- or Alt- keys) etc. If applicable, I will
summarize all my suggestions and send to the forum.

73,
Martin, OK1RR


- The activation of tlf's digimode ...





___
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] WAEDC QTC - v0.002 release :)

[FS]

Yes, that sound good. I am only a little bit afraid of garbage while 
decoding (because of weak signals). But thats also a question how good

the squelch is set.

73 Fred

On 11/04/2013 09:09 AM, Ervin Hegedüs wrote:

Hello Fred,

On Sun, Nov 03, 2013 at 09:55:51PM +0100, Fred Siegmund wrote:

Ok, there seems to be one significant difference to CW/SSB. The QTCs
in RTTY are transmitted in batches.


yes, that's the challenge :)

Till I made all of the WAEDC modifications (first patch was only
the correct handling of points and multipliers), I've tried to
keep in mind this difference. Eg: in CW/SSB modes, QSO's allowed
only in EU-DX relation, but in RTTY every station should work
with from anywhere. In CW/SSB modes, only the DX stations should
send QTC to only the EU stations, in RTTY all station should send
QTC to everyone, except same continent. And techically, in RTTY
the QTC are sending in batch mode, instead of one by one.


This
makes it somehow difficult to keep it compatible, but its possible
(different DIGIMODE handling).


yes, and (I hope :)) my codes handles it correctly.


There need
to be a macro to request to repeat a selected line. Another macro
for repeat all. When ALT-R is pressed TLF should be looking for a
line begining with QTC xxx/xx to have a trigger point. And then copy
the whole block in.


I found out that if a line contains '?', that will be signed as
incomplete - this is the macro. Then if you press ENTER, Tlf
will send PSE RPT #N immediately (!). If all lines are marked
as complete (simply press ENTER, and line doesn't contain '?'),
and then press ENTER, Tlf will send 'TNX QTC NNN/NN' or any other
message, and close the window. This method can work only in RTTY,
but the different from CW/SSB is not so much: in that modes, if
you marked a QTC as complete, the 'R' signal will send
immediately, not after if you get all QTC's.

Hope this should be usable, but if you have any idea, please let
me know.


73,

Ervin
HA2OS



73 Fred


Am 03.11.2013 10:49, schrieb Ervin Hegedüs - HA2OS:

hello,

On Sun, Nov 03, 2013 at 09:04:26AM +, FS wrote:

Yes, that could work. Lets say, the user enters the the series
number like xx/xx, and the QRV message is sent, TLF is triggered to
take everyting in a pattern like, by grabing it from gMFSK.log:
 cc nnn
time call   number

Till I looked the examples of QTC, especially RTTY mode, I found
this (very good) summary:

http://www.guernsey.net/~pcooper/waedc.html

On this page the author said there are several forms of QTC:

So, you will end up with something like this:
001/10
0012 G3URA 049
0013/AA5AU/056
0014-RA9FOE-012
etc for ten lines.

So, the separator sign should be   (space), / (slash), -
(hyphen/minus) character. That's no problem, but it would be nice
to know, is there any other formula to separate the fields, or
operators (and softares) only uses these?

I think I can handle all or them above.


I a not aware if they send in RTTY shortend versions, like two
figures for the time, or so.

I don't know that too... :)


Maybe the user could be asked if he
wants to accept it, if yes a ROGER is send otherwise a PSE REPEAT.

Hmmm... I'm not sure is it a good solution. Otherwise, if
somebody had WAEDC-RTTY, and received many QTC's, please confirm
that: anybody (or any software) uses the different formula that
listed above, or not?


thanks, 73:


Ervin
HA2OS




___
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] Autosend feature

[FS]

Ok, interesting indeed. The functionality is basicly there, but broken.
I always wondered what such a important key like space does in TRLOG 
mode. Well, it just doesn't work like intended (arrow down is the same).

The same is true for the :char command (autosend).
See the original meaning:
http://pa0r.blogspirit.com/archive/2005/03/29/autostart_cw_for_tlf.html

I think its a bug. ;-)

73 Fred

On 11/04/2013 07:39 PM, Martin Kratoska wrote:

Was: Re: [Tlf-devel] WAEDC QTC - v0.002 release :)
---
Dne 3.11.2013 22:09, Fred Siegmund napsal(a):
  Hi Martin, which autosend feature do you mean? I worked with TRLOGLinux
  and was not very satisfied, namely
  the bandmap is very slow and there some inherited things from the
  original program that are very stupid. Like its
  not possible to edit the complete log. These are points were a distinct
  progression from TRLog is visible (already
  developed by Rein).
 
  73 Fred


Hi Fred,

the Autosend feature is that which is in TRlog activated with

AUTO CALL TERMINATE = TRUE
AUTO SEND CHARACTER COUNT = 4

(here the autosend starts at 4th character). Better is an example:

OK1RRA comes back to your CQ and you want to reply. So you type OK1R (4
characters) and your program begins to send. You are now in a hurry (a
bit :-) because you must complete typing the whole call till the sending
procedure catches you, here you must add RA. Then follows the
exchange, the first ENTER logs in the QSO.

Some OPs hate this option, some (me including) are in love with this.
Except typing the call, you need only a single ENTER to make a complete
QSO. Isn't nice such option? Also, many other progs have this feature...

Of course, I make thorough tests of any TRLOGLinux version but it is
still far away from an useful program. Many poor bottlenecks inherited
from the obsolete DOS version - not only the impossibility to edit the
complete log but the telnet operations, the hardcoded (thus very
limited) support of quite few radio models, the predefined exchange
types (an obvious quirk when the program tries to think for the
operator) and much more. Anyway, TRlog (the original DOS version)
introduced a new philosophy which is still unbeaten today. tlf should
get much inspiration here. QTC handling in WAE is an example...

CW/SSB contesters here know all the tricks of N1MM, TR4W, WriteLog and
other powerful software packages used by winners. I believe that tlf
should come close to these top runners. First if meets all requirements
of top grade CW/SSB contesters, we should start with digimodes. Now (it
seems at least to me) is too early, there is a danger that we will have
an universal multimode program which does all, but does all quite bad,
with many unnecessary typing etc. which can make a program useless for a
tired operator, who is in a contest for whole weekend.

Anyway, I am very happy with tlf. This is the reason of my support of
this software (TRLOGLinux and so2sdr being still ignored here...). Kudos
to all authors and contributors, also my apologies that I am not a
coder, I am just operator who can make some tests and suggest and old,
forgotten feature.

73,
Martin, OK1RR



___
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] WAEDC QTC - v0.002 release :)

[FS]

Yes, that could work. Lets say, the user enters the the series number 
like xx/xx, and the QRV message is sent, TLF is triggered to take 
everyting in a pattern like, by grabing it from gMFSK.log:

 cc nnn
time call   number
I a not aware if they send in RTTY shortend versions, like two figures 
for the time, or so. Maybe the user could be asked if he wants to accept 
it, if yes a ROGER is send otherwise a PSE REPEAT.


73 Fred

On 11/02/2013 01:36 PM, Ervin Hegedüs - HA2OS wrote:

Hello,

On Sat, Nov 02, 2013 at 01:40:27PM +0100, FS wrote:

The biggest challenge is the reciving side. For CW you have to type
it anyway, maybe
that could be a intermediate solution.


CW (and phone) is clear, and no problem - I think I can handle
the fast speed CW too, and can type all data of QTC.

But the RTTY is a littlebit faster :)


But it would be nicer for
RTTY to mark a complete line
in miniterm (which is available in TLF), push a key combination and
have it in the QTC box. Any solution within a different programme
like fldigi, will be no short  term solution and probably
solved if the connection between this two programms is reworked. So
for now a mouse integration
for marking a line in miniterm seem to be the way - although not
perfect. ;-)


yes, the using miniterm should be the cleanest way, independent
from anything. But the mouse integration would be hard work at
this time, and (IMHO) Tlf should lost the magic feeling :)

If Tlf reads from RTTY client log, maybe I could make a pattern,
which recognize the first line of QTC block (NUMBER / NUMBER
NEWLINE), and when the next lines contains the QTC pattern, it
filled the QTC lines in receive window.


Any idea?


Thanks, 73:

Ervin
HA2OS




73 Fred

Am 01.11.2013 21:55, schrieb Ervin Hegedüs - HA2OS:

Dear HAM's,

I still had not enough time as I expected to made the QTC patch,
but here is the next release - please look at that.

The send directions doesn't contains relevant changes.

There is the another directions, the receive of QTC's. See, how
it's works.

If you press ALT+r when you are in exchange field (in current
QSO line), the new window opens. In that window the 1st line has
2 fields: the QTC block serial and number of QTC's.

After this there are 10 empty lines, every lines has 3 block, as
QTC: time (HHMM), callsign, and serial.

If you put the serial and number of QTC's, the left side of 1st
columns will appears the numbers, to help to the operators to
see, which rows are affected.

You can move the cursor between the fields with TAB and SHIFT+TAB
(backward direction), and UP/DOWN cursor move keys.

In a field, you can use BACKSPACE, DELETE, and LEFT/RIGHT cursor
move keys to move the cursor, and real contains of fields.

In time and serial fields, you can type only numbers, and ?
(question-mark). In callsign field, you can type letters,
numbers, '/' and '?' signs.

If a QTC line contains a '?' sign at anywhere, you can see a '?'
sign at end of the line - that means, you've marked this QTC as
incomplete. In CW mode (in future) Tlf doesn't will send 'R'
sign, instead it send 'AGN #', where # will the number of QTC.

If you type 'ESC', the QTC window will hide, but when again type
ALT+r, the filled window will open again.

If you change the callsign in QSO line (when QTC window is not
showed), the contains of QTC will be deleted.


Now, this is the current level of development.

Further plans:
- if all fields of a QTC (time, callsign, serial) is complete,
   and you type the ENTER, the QTC will be marked as complete, and
   this status will be indicated with an '*' (asterix) sign, the
   end of line
- if you are in last QTC, and all QTC's are marked as completed,
   then after the pressing of ENTER, the window will be closed
- if you save the QSO, and QTC window contains records, they will
   be saved with QSO (same as sending QTC)

I think I can do these to the next weekend, when WAEDC RTTY will
starts, but I never used QTC, and I don't know is it a good
choice to handle the receive direction of that.

To come out of this:
- merge QTC's with QSO's in Cabrillo log
- at send direction to handle the QTC's with an external program,
   eg. gMFSK - I think it's not too difficult
- at receive direction to handle the QTC's; I mean, it would be a
   good choice to implement a feature in RTTY software, when the
   operator select a TEXT in receive window, and (eg.) with right
   click it could be send the selected text as QTC to Tlf; in this
   case, the Tlf must to handle the new logtype through LAN

If anybody has a good idea one of those contexts above, please
send me an e-mail through this list or direct.


Of course, to check the Tlf, you need the git, gcc, and make
tools. The repository of this patched version is this:

https://github.com/airween/tlf/tree/waedc-qtc



73:

Ervin
HA2OS









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

Re: [Tlf-devel] WAEDC QTC - v0.002 release :)

[FS]

The file is still called gMFSK.log. What goes to FLDIGI is written to a 
file called TLFfldigi. That works pretty well, Thomas did some updates 
on the original code, eg.fixing the LF problem in the TX direction.


73 Fred

On 11/02/2013 01:48 PM, Ervin Hegedüs - HA2OS wrote:

Hello Ed,

On Sat, Nov 02, 2013 at 09:15:36AM -0400, Ed wrote:

On Sat, 02 Nov 2013 13:40:27 +0100
FS dh...@freenet.de wrote:


The biggest challenge is the reciving side. For CW you have to type
it anyway, maybe
that could be a intermediate solution. But it would be nicer for RTTY
to mark a complete line
in miniterm (which is available in TLF), push a key combination and
have it in the QTC box. Any solution within a different programme
like fldigi, will be no short  term solution and probably
solved if the connection between this two programms is reworked. So
for now a mouse integration
for marking a line in miniterm seem to be the way - although not
perfect. ;-)

73 Fred


The problem with miniterm is excessive LFs', especially using fldigi.


may be that's no problem, I could modify the source, if Tlf
detects the QTC block, it doesn't skip LF - or, in this case, the
result is showed in QTC rec window, instead of miniterm.


And gMFSK is old and no longer maintained and may not be adequate.


hmm... that's a very important news for me.

Usually I work in digimodes just sometimes, and then I use gMFSK.
In September of this year, I did the CQ WW DX RTTY, this was my
first digimode contest. I realize the deficiency of gMFSK, and
then started to make the Tlf patch.

I didn't use Fldigi anytime, yesterday I've started to explore
that. The send direction is works for me (through
gmfsk_autofile), but I couldn't conigure the receive direction,
so I didn't find the equivalent with gMFSK.log, and what Fldigi
receives, that isn't seems in Tlf miniterm.

How can I configure it?


Thanks, 73:


Ervin
HA2OS


Ed W3NR

___
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] WAEDC QTC - v0.002 release :)

[FS]

The biggest challenge is the reciving side. For CW you have to type it 
anyway, maybe
that could be a intermediate solution. But it would be nicer for RTTY to 
mark a complete line
in miniterm (which is available in TLF), push a key combination and have 
it in the QTC box. Any solution within a different programme like 
fldigi, will be no short  term solution and probably
solved if the connection between this two programms is reworked. So for 
now a mouse integration
for marking a line in miniterm seem to be the way - although not 
perfect. ;-)


73 Fred

Am 01.11.2013 21:55, schrieb Ervin Hegedüs - HA2OS:

Dear HAM's,

I still had not enough time as I expected to made the QTC patch,
but here is the next release - please look at that.

The send directions doesn't contains relevant changes.

There is the another directions, the receive of QTC's. See, how
it's works.

If you press ALT+r when you are in exchange field (in current
QSO line), the new window opens. In that window the 1st line has
2 fields: the QTC block serial and number of QTC's.

After this there are 10 empty lines, every lines has 3 block, as
QTC: time (HHMM), callsign, and serial.

If you put the serial and number of QTC's, the left side of 1st
columns will appears the numbers, to help to the operators to
see, which rows are affected.

You can move the cursor between the fields with TAB and SHIFT+TAB
(backward direction), and UP/DOWN cursor move keys.

In a field, you can use BACKSPACE, DELETE, and LEFT/RIGHT cursor
move keys to move the cursor, and real contains of fields.

In time and serial fields, you can type only numbers, and ?
(question-mark). In callsign field, you can type letters,
numbers, '/' and '?' signs.

If a QTC line contains a '?' sign at anywhere, you can see a '?'
sign at end of the line - that means, you've marked this QTC as
incomplete. In CW mode (in future) Tlf doesn't will send 'R'
sign, instead it send 'AGN #', where # will the number of QTC.

If you type 'ESC', the QTC window will hide, but when again type
ALT+r, the filled window will open again.

If you change the callsign in QSO line (when QTC window is not
showed), the contains of QTC will be deleted.


Now, this is the current level of development.

Further plans:
- if all fields of a QTC (time, callsign, serial) is complete,
   and you type the ENTER, the QTC will be marked as complete, and
   this status will be indicated with an '*' (asterix) sign, the
   end of line
- if you are in last QTC, and all QTC's are marked as completed,
   then after the pressing of ENTER, the window will be closed
- if you save the QSO, and QTC window contains records, they will
   be saved with QSO (same as sending QTC)

I think I can do these to the next weekend, when WAEDC RTTY will
starts, but I never used QTC, and I don't know is it a good
choice to handle the receive direction of that.

To come out of this:
- merge QTC's with QSO's in Cabrillo log
- at send direction to handle the QTC's with an external program,
   eg. gMFSK - I think it's not too difficult
- at receive direction to handle the QTC's; I mean, it would be a
   good choice to implement a feature in RTTY software, when the
   operator select a TEXT in receive window, and (eg.) with right
   click it could be send the selected text as QTC to Tlf; in this
   case, the Tlf must to handle the new logtype through LAN

If anybody has a good idea one of those contexts above, please
send me an e-mail through this list or direct.


Of course, to check the Tlf, you need the git, gcc, and make
tools. The repository of this patched version is this:

https://github.com/airween/tlf/tree/waedc-qtc



73:

Ervin
HA2OS









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

Re: [Tlf-devel] TLF

[FS]

Hi Stefano,

kind of TLF supports SO2R already 2day. If you have 2 radios and 2 
Computers connected via LAN, you can use a common log. I use this also 
via internet connected log (needs some modified code). You may try this 
(but the input console is far away from the TLF comfort):


http://code.google.com/p/so2sdr/

73 Fred

On 02/19/2013 03:57 PM, Rein Couperus wrote:

Hi Stefano,

I am not handling the TLF program anymore, but it has found a new
maintainer...
It would be best to send your request via the tlf-devel mailing list at
https://lists.gnu.org/mailman/listinfo/tlf-devel

There you can see the mail archive and come into contact with the
people who are still actively supporting TLF.
I am on a different project at the moment, but I still manage the list

Hope you find what you are looking for...

73,

Rein EA/PA0R/M

https://lists.gnu.org/mailman/listinfo/tlf-devel

Hi, I saw this email in the webpage of TLF
http://sharon.esrac.ele.tue.nl/pub/linux/ham/tlf/tlfdoc-0.8.16/tlfdoc.html .
I don't know If I'm addressing the question to the right guy or not. If
I'm wrong I hope you will forgive me.

I started using TLF since few months but there's still something that
prevents me to switch entirely to Linux, the lack of a contest software
that handles SO2R. Will TLF, in a future release, handle such an
operating technique?

Is it possible to link in local two terminals running tlf instances so
as to have the two input fields and to run a sort of primitive SO2R, how
can i link them?

Thanks in advance and all the best
--
Stefano Menon
IZ3NVR - KD2BGM
http://digilander.libero.it/iz3nvr



___
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] bugs in tlf-1.2.0_pre2

[FS]

The interesting thing is that, in some contests like CQWW this works, in 
some not. If it works the number is printed with 4 digits.


73 Fred

On 09/10/2012 01:19 AM, Martin Kratoska wrote:

The September CWopen by CWops discovered following bugs in tlf-1.2.0_pre2:



Another bug - if defining the part of exchange containing the serial
number (with #), the serial is actually not put into log, the #
character appears instead.


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

Re: [Tlf-devel] ARRL 10m

[FS]

Hi,

I must correct: only when using TAB for switching between the logging 
fields you have to press enter twice. Using normal EnterSendsMessage 
mode everything works as expected. RECALL_MULTS isnt intended for single

band use, so can be skipped from the rules file.

Nice weekend,

Fred

On 12/08/2011 09:24 AM, FS wrote:

Hi all,

attached there are the rules and the mult file for ARRL 10m contest. I
hope the make it through the list. I think the DX__SECTIONS definition
is valid, but there is a problem similar also when the SERIAL+SECTION
definition is active:
- you always have to enter the exchange twice before it gets logged
- running number appears again when RECALL_MULTS is on and the station
is logged again in SSB

The scoring is correct, means numbers dont get recognized as Mult exchange.

73 Fred


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

[Tlf-devel] ARRL 10m

[FS]

Hi all,

attached there are the rules and the mult file for ARRL 10m contest. I 
hope the make it through the list. I think the DX__SECTIONS definition 
is valid, but there is a problem similar also when the SERIAL+SECTION 
definition is active:

- you always have to enter the exchange twice before it gets logged
- running number appears again when RECALL_MULTS is on and the station 
is logged again in SSB


The scoring is correct, means numbers dont get recognized as Mult exchange.

73 Fred
AL
AK
AZ
AR
CA
CO
CT
DE
FL
GA
HI
ID
IL
IN
IA
KS
KY
LA
ME
MD
MA
MI
MN
MS
MO
MT
NC
ND
NE
NV
NH
NJ
NM
NY
OH
OK
OR
PA
RI
SC
SD
TN
TX
UT
VT
VA
WA
WV
WI
WY
DC
NB
NS
QC
ON
MB
SK
AB
BC
NW
NF
LB
YT
PEI
NU
AGS
BAC
BCS
CAM
CHI
CHH
COA
COL
DF
DGO
EMX
GTO
GRO
HGO
JAL
MIC
MOR
NAY
NLE
OAX
PUE
QRO
QUI
SLP
SIN
SON
TAB
TAM
TLX
VER
YUC
ZAC
###
# ARRL 10m CONTEST (DX  side) #
###
#
CONTEST=arrl10m_dx
LOGFILE=arrl10m_dx.log
CONTEST_MODE
SSBPOINTS=2
CWPOINTS=4
MIXED
DX__SECTIONS
RECALL_MULTS
MULT_LIST=arrl10m_mults_1
#
##
##
#  Messages F1= to F12=  #
#  Message CW_TU_MSG=#
#  Message SP_TU_MSG=   #
##
#  % = call#
#  @ = hiscall   #
#  # = serial#
#  [ = RST   #
#  + = increase cw speed #
#  - = decrease cw speed #
# (works only with parport   #
#   interface)   #
##
##
#
F1=CQ % % TEST
F2= %
F3=@ +++5NN---#
F4=TU
F5= @
F6=%
F7=@ SRI QSO B4 GL
F8=AGN
F9= ?
F10= QRZ?
F11= PSE K
F12=TEST % %
#
CQ_TU_MSG=TU %
SP_TU_MSG=TU +++5NN---#
#
#ALT_0=
#ALT_1=
#ALT_2=
#ALT_3=
#ALT_4=
#ALT_5=
#ALT_6=
#ALT_7=
#ALT_8=
#ALT_9=
#

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

[Tlf-devel] help.txt

[FS]

Hi all,

put the attached file into the working directory of tlf to have a 
reminder (ALT-H) of all the key combinations available in tlf.


73 Fred
Keys (shortcuts) to be used in TLF

If you want to see some of the start up parameters try: 'tlf -h'.

ALT+?
Alt-a Cluster info  Alt-b   Band up
Alt-t Tune  Alt-n   Note in log
Alt-v Band down (CW Speed?) Alt-p   turn PTT on/off
Alt-h show help.txt Alt-w   CW Weight
Alt-i See talk messages Alt-j   See QRG's
Alt-k CW from Keyboard  Alt-x   exit program (Alt-q)
Alt-m Multi display (Alt-c) Alt-s   Score window (Alt-r)
Alt-, show Bandmap  Alt-j   show frequency
Alt-z show worked zones 
Alt-g Bandmap: grab Call after inserting 2+ letters

CTRL+?
Ctrl-a add a spot to list
Ctrl-c Quit tlf Ctrl-bCluster send
Ctrl-g Grab a bandmap spot  Ctrl-pMUF display
Ctrl-page-up   Auto CQ delay +  Ctrl-page-down Auto CQ delay -
Ctrl-k CW from keyboard
Ctrl-f frequency control window
Ctrl-t Send message
Ctrl-r LPT0 pin 14 on/off (SSB mic)

direct Keyboard commands
'+'   Switch RUN/SP (default, TR Log mode)
'+'   Send exchange (CT log mode)
'Insert'  Log QSO (CT log mode)
PG-UP CW + 2wpm
PG-DWNCW - 2wpm
','   CW from Keyboard
'.'   filter bandmap content
';'   Note in log  
F1 - F12  Send F1 - F12 msg  
TAB   Switch fields
ENTER Log qso, call cq 
SPACE CW mode: send call
'\'   Log qso w/o CW   
Up-arrow  Edit prev qso
'-'   Delete last qso  
'_'   confirm last serial nr   
'='   confirm last call
L-arrow   Edit call
L/R Arrow Band change  
ESCAPEBack up, stop
''   Talk message 
'#'   save/go to a MEM Frequency
! New shell

commands from Call field
:ssb  Switch to ssb :wriWrite cabrillo
:cwm  Switch to cw  :adiWrite Adif
:dig  Switch to rtty:exiExit tlf
:hel  Help  :infNetwork info
:mes  Set cw messages   :   Telnet window
:set  Edit config file  :tonSet sidetone (0 = off)
:cfg  Edit config file  :res  Rescore
:sim  CW CQWW Simulator :souSound utility
:ZONesshow list of zones to be worked
:cty  list of coutries to be worked
:cqd  CW delay
:rit  reset RIT after QSO is logged
:VIEw show complete log
:EDIt edit the log
:LISt list CW messages
:MESsage  change CW messages
:CHEckopen Check window
:NOCheck  close Check window
:pac  open Terminal
:CLUster  open Terminal
:SPOtsonly DX spots sorted by time
:FILter   filter DX Cluster content
:map  filter band map content
:SYNc synchronize log in network
:EXIt exit program
:MULt toggle remaing multi display
:CONtest  toggle contest mode on/off
:SCOretoggle score window on/off
:FREq show frequency
:CLOffCluster off
:INFo network status
:TRXcont  toggle TRX control on/off
:CHAR number of chars to send while typing
:DEBug_tty test rig link
:SOUndrecord sound files
:SCAnner  scanner function (experimental)
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel

Re: [Tlf-devel] New TLF prelease tlf-1.1pre1

[FS]

Hi all,

while preparing for WWDX SSB I noticed that the VKSPR message is not 
sent in SP mode after inserting the zone in the numbers field. The Call 
file is sent after inserting the other stations call at call input. 
Anybody knows why? I saw a lot of g4kno editing in the sources there ;-)


73 Fred

On 10/25/2011 04:32 AM, Thomas Beierlein wrote:

Hi Andy,

thanks for your test report. Let me try to answer your questions.

Am Mon, 24 Oct 2011 20:25:10 +0100
schrieb Andy Summersg4kno.m...@gmail.com:

Thanks for the new bandmap functions. I've been trying it out with a
view to dabbling in CQWW - I'm aware it may not be stable.


I did some work in last weeks to  stabilize it and I think pre2 will be
much better there.


I've read the New_Bandmap.txt and don't think it works as described
there. If I enter a call, press ctrl-A, I see it added to the
bandmap. I tune somewhere else and do the same thing. I can do this
several times and see the calls added, but when I repeatedly hit
ctrl-g it only picks the most recent spot.


You are right, that is what is implemented. My idea behind that was
that you normally only have one spot of a station per band and mode. If
you filter your bandmap by mode or band Ctrl-g will select the right
spot.

Are there reasonable scenarios where we have would need to select
between more than one spot per band/mode for the same station? Than I
should think about a way to handle it.


Also, I see that a MEM frequency appears under the normal frequency
display, but you don't say how to get the rig back onto that
frequency. Simply switching mode back to Log, doesn't do it.


The memory recall is the same as in normal memory operation. As the man
page says hitting '#' records frequency if memory is empty and recalls
it if it is set. So after grabing a spot you can switch back to Run
mode by '+' and to old frequency by '#'.


It would be quite useful to be able to arrow up/down the spot list
and select the specific spot you want, rather than have to scroll
through the lot to get to the one you want. It's a long time since I
used CT, but it might be worth studying how that worked. I do
remember that you could toggle alt-F4 (or was it F3) to toggle
between the selected spot and the current run frequency. That was
really useful for continuing to CQ, keep your frequency warm and
periodically check back to see if the spot was workable.


I see the point and will think about to implement something similar. But
it will be at low priority at the moment.


BTW, the score or frequency window overlaps the new spot mode info
and doesn't look right.


The score window will be in the upper right in next prerelase (just did
it yesterday :-) ). As the frequency window is only temporarily visible
it may hide the bandmap for that time - should be acceptable.

Am Mon, 24 Oct 2011 20:28:04 +0100
schrieb Andy Summersg4kno.m...@gmail.com:


I also forgot to mention that if you log a call but then hit minus to
delete the last QSO, that call shows up in the bandmap as a dupe.


Same as for correcting the score after delete, see below...


On 07/10/11 18:54, Thomas Beierlein wrote:

!!! If you delete a QSO you have to manually rescore the log
(:res).



Btw, I plan to release the next prerelease version in next two week.

73, de Tom DL1JBE.



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

Re: [Tlf-devel] CTY-2111 Country Files - 27 August 2011

[FS]

Its the old format. You can look for version in the file and find it 
at KH7K. So its the latest content.


73 Fred

On 08/28/2011 09:51 PM, Graham wrote:

Thanks Jim.

I did notice that the link for the cty.dat file for TLF points to

www.country-files.com/cty/old/cty.dat

while many of the others point to

www.country-files.com/cty/cty.dat

A quick comparison shows that some entries in the /cty/cty.dat has = as
prefix on some entries whereas there are none in the /old/cty.dat file.

Is this an indication of an old format or an old file (i.e. not
current)?  My guess at this point is the former but I would like
confirmation on that point as I am using tlf.

cheers, Graham ve3gtc




On Sat, 2011-08-27 at 17:00 +, Jim Reisert AD1C wrote:

The Country (CTY) Files were updated on 27 August 2011.

 http://www.country-files.com/cty/

To install the file, follow the link to your software at the top of the page.

Here are the release notes:

27 August 2011 (CTY-2111)
VER20110827, Version entity is Kure Island, KH7K

Added/changed Callsigns/prefixes:

GS4WAB/P is Shetland and Fair Isle, *GM/s
3D2R is Rotuma, 3D2/r
ZS6KX/7 is Antarctica, CE9 in CQ Zone 38, ITU Zone 67
EA5IIG/6 is Balearic Islands, EA6
TX8 is New Caledonia, FK
GB0BRE is Wales, GW
GB2LSA is Wales, GW
JG8NQJ/JD1 is Minami Torishima, JD/m
AH0A is Hawaii, KH6
K8O is Hawaii, KH6
KL3FN is Hawaii, KH6
K7P is Alaska, KL
W4L is Puerto Rico, KP4
LW2EIY/H is Argentina, LU
SV0XBZ/5 is Dodecanese, SV5
R2011UFO is Asiatic Russia, UA9

Retired Callsigns/prefixes:

3D2AA in Rotuma, 3D2/r
I0QHM/IA0PS in Antarctica, CE9
EA3BT/6 in Balearic Islands, EA6
GB2AD in Northern Ireland, GI
GB4GS in Scotland, GM
GB0AWS in Wales, GW
GB0CSA in Wales, GW
GB8CCC in Wales, GW
LU2CM/D in Argentina, LU
LU8DIP/D in Argentina, LU
LV7E/D in Argentina, LU
UA9KAS/6/P in European Russia, UA
RT9T/2 in Kaliningrad, UA2
RU3HD/9/P in Asiatic Russia, UA9
VE3DO/7 in Canada, VE
VK0M/ZL4DB/P in Macquarie Island, VK0M

73 - Jim AD1C





___
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