Re: [Tlf-devel] Tlf QTC receive pre-final

[Ervin Hegedüs - HA2OS]

Hello Fred, and list,

On Sun, Nov 10, 2013 at 04:37:15PM +0100, Fred Siegmund wrote:
> Ervin, i would not skip the automatic read in completely.

ahm', ok, I agree,

> But it
> needs to be more robust. From a users perspective
> i need need all possible commands visible as help. See
> http://docs.win-test.com/wiki/WAEDC
> May be the programme can look for QTC: xx/xx automatically, but it
> needs to be confirmed by the user if the read in should
> start.

I think you mean the auto capture should be dropped - I don't
know, I think it should be discussed with other users, who wants
to use Tlf as RTTY contest program (with QTC). May be it could be
just configurable?

> Right now i have many errors while the programme starts this
> process on its own.

It would be very good to make some notes about these errors -
until the contest I started to keep my notes about the Tlf, and
especially the QTC handling. And when I heard a QTC block, I just
simple copied it and saved - I think it will be our help. If you
are using Tlf, just save the RTTY.log and gMFSK.log, those
contains all traffic.

So, it's very important that I could reproduce the problems, and
for that please make some notes and send to me.

> Or better concentrate on CW QTCs :-)) Should be easier (for the programme).

I think the main concept is a good way - I sent a few QTC's, and
that works very well, easy to use, and confortable.

To receive the QTC's by hand (CW and SSB) could also usable in my
opinion, but the RTTY is a very specially mode: too much QRM, too
much interference, and the result will an unparsable dollop - just
see this:

QTC: 17/109
1512-G0MBA-08.10#$(9FEV-085
1517-SM3DXC-006
1517-DC9ZP-265
1519-LX7I-806
18#$'1XT-002
1523-DJ6TK-267
1524-ON7LUAEPW
QTWTADL7FBDQHHPPPDL9GWA-067


With the read received QTC's from an external file (current
version) is a usable - but you're right, it's very important to
know the shortcuts. I received a few QTC's with some smaller
discomfort, I will try to fix them - after the discussion.

But the next contest - as I know - where QTC are used is the
WAEDC CW in 2014 (in august?), I think we have enough time to
make an excellent contest software :)


73,


Ervin
HA2OS


 
> 73 Fred
> Am 09.11.2013 16:31, schrieb Ervin Hegedüs - HA2OS:
> >Dear Larry,
> >
> >On Sat, Nov 09, 2013 at 09:51:19AM -0500, Larry Levesque wrote:
> >>Excellent.
> >not really :(,
> >>I have experienced a few segfaults when moving between fields in the QTC
> >>window but overall nice work!
> >I got that segfaults too... looks like MINITERM need to turned
> >ON, and if the QRM is too big, the parser couldn't catch the
> >lines, and then drops the segfault.
> >
> >I rewrite the receive method a few hours ago, and pushed to my
> >repo.
> >
> >The most common changed is now you have to put the received QTC
> >text to a file, in the contest directory. The name of file is
> >RTTY.qtc. Here is my contest directory:
> >
> >logcfg.dat
> >QTC_recv.log
> >QTC_sent.log
> >RTTYlog
> >RTTY.qtc
> >rules
> >waedc.log
> >
> >Now you can keep open that file, and everytime when you get a
> >QTC, just put it to that file, and save that. The file format is
> >something like this:
> >
> >13/10
> >0620-SP1EG-033
> >0621-;43PV-045
> >0621-R4WTAPTP
> >PYWWADF4WC-064
> >0624-EO3Q-229
> >0628-OH2HAN-130
> >0629-PC1EMR-007
> >06
> >9-PA2LP-026
> >0630-HG4I2WY
> >PYNP HG1G-115
> >
> >Before you save it, align all lines:
> >
> >13/10
> >0620-SP1EG-033
> >0621-;43PV-045
> >0621-R4WTAPTP
> >0-WWADF4WC-064
> >0624-EO3Q-229
> >0628-OH2HAN-130
> >0629-PC1EMR-007
> >069-PA2LP-026
> >0630-HG4I2WY
> >PYNP HG1G-115
> >
> >It's no problem, if there is an invalid line. Now save it, and in
> >opened window, press ALT-c, this reads qtc's from file, and fill
> >all fields.
> >
> >All invalid lines will be marked with ?, and if you move the
> >cursor to that line, the serial field, and press ENTER, Tlf will
> >asks again that qtc.
> >
> >I think this is the best solution at this time, in RTTY mode, the
> >QTC's are very fast, and it must to edit with hand to parse them
> >- there is no other choice.
> >
> >
> >Sorry for the awkwardness, as I wrote, this is my first
> >WAEDC-RTTY.
> >
> >
> >73,
> >
> >
> >Ervin
> >HA2OS
> >
> >>On 11/07/2013 07:15 PM, Ervin Hegedüs - HA2OS wrote:
> >>>Hello all,
> >>>
> >>>so, after a few weeks hard working, it looks like QTC
> >>>implementation for Tlf is ready to test at this weekend, on
> >>>WAEDC-RTTY.
> >>>
> >>>You can find it on github.com:
> >>>
> >>>   https://github.com/airween/tlf/tree/waedc-qtc
> >>>
> >>>This is a very short intro how to receive the QTC's from a
> >>>station.
> >>>
> >>>* you can use MINITERM or not, it doesn't matter
> >>>* in a normal QSO, you can fill the callsign and contest serial
> >>>   fields; first the callsign, then serial
> >>>* if all data has received, press [ENTER] ONCE!
> >>>* now Tlf send through Fldigi your report and serial, what you
> >>>   set up, eg: "CFM UR 599 111"
> >>>* always wait to Fldigi finishes the sending of actual message
> >>>* if station ask "TX/RX QTC?", or any form it asks you about
> >>>   the QTC, you press ALT+r
> >>>* then QTC receive window opened, and Tlf sends a message
> >>>   automatically: "QTC QRV"
> >>>* in the window, Tlf shows the CAPTURE mode, the default mode
> >>>   is off, when window opened
> >>>* if you start to type the QTC serial, the capture will switch to
> >>>   ON, and if the length of received line is greater than 12, it
> >>>   will be parsed
> >>>* you can turn on and off the CAPTURE with ALT+c
> >>>* if you fill the number of QTC's, the numbers will turned on at
> >>>   begin of lines
> >>>* if MINITERM is turned on, you can see the received lines;
> >>>   always the second line from bottom will be parsed; if MINITERM
> >>>   is off, you can't see, but the point is that if there is a new
> >>>   line, which length are greater than 12, will be parsed
> >>>* now the Tlf tries to parse all lines, and fill the fields
> >>>* if any field contains illegal character (eg: the time and
> >>>   serial fields can contains only numbers), it will be replaced
> >>>   with a '?', and that line will be marked as incomplete
> >>>* you can modify the fields content, just move to the field with
> >>>   top/bottom cursors, and TAB/Shift+TAB keys, and change the char
> >>>   what you think is invalid; then that line will be marked as
> >>>   incomplete
> >>>* if all field is filled right, and you are in serial (third)
> >>>   field, press [ENTER], the line will be marked as complete, and
> >>>   an '*' char will indicates this the end of line
> >>>* if the number of QTC lines reaches the number which you gave,
> >>>   the CAPTURE will be turned off
> >>>* remember: you can turn out and off the CAPTURE
> >>>* if all lines are complete and marked, and you are the last
> >>>   line, then press [ENTER]
> >>>* now Tlf will close the window, and send through Fldig a message
> >>>   to station: "QSL ALL QTC"
> >>>* then if you press [ENTER] again, the QSO and QTC block will be
> >>>   saved
> >>>* if one or more QTC is incomplete, just move to that in last
> >>>   field (serial), and press [ENTER], then Tlf send a message
> >>>   through Fldigi: "05 PSE AGN" - don't send more that one QTC
> >>>   repeat in same time! Remember, always wait wait for Fldigi
> >>>   finished the sending of message!
> >>>* then you can edit the QTC line, and if all QTC are marked,
> >>>   station will get the QSL ALL QTC message
> >>>* if all QTC are good, you can press [F2], that will be marked
> >>>   as complete all lines; then if you press [ENTER], you will
> >>>   close the window and send "QSL ALL QTC" message
> >>>
> >>>
> >>>Notes:
> >>>* there is a small Python script, which can helps to test the
> >>>   receive method; the script in tlf source root dir, and called
> >>>   by gmfsklogger.py
> >>>   to use it just type:
> >>>   /path/to/gmfsklogger.py /path/to/tlf/waedc/waedc.log
> >>>   it reads your log, and creates QTC's from that. Of course, you
> >>>   need more that 10 QSO in logfile
> >>>   for test, you can donwload a test logfile:
> >>>   https://www.dropbox.com/s/sxce83lgs4v2kk4/waedc.log
> >>>* if somebody wants to test on the air, I welcome to try; there
> >>>   is 1 day to contest, if we find any bug, I could fix it
> >>>
> >>>
> >>>73,
> >>>
> >>>
> >>>Ervin
> >>>HA2OS
> >>>
> >>>
> >>-- 
> >>*Larry Levesque
> >>KA1VGM
> >>*
> >>_______________________________________________
> >>Tlf-devel mailing list
> >>address@hidden
> >>https://lists.nongnu.org/mailman/listinfo/tlf-devel
> >
> 
> 
> _______________________________________________
> Tlf-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tlf-devel

-- 
I � UTF-8