[RTTY] X-QSO -- was: After the tough qso

Sat Feb 17 09:15:46 EST 2018

Larry, in the actual Cabrillo file the 'QSO:' at the beginning of a QSO line is replaced with 'X-QSO:'.
73,Ed W0YK
-------- Original message --------From: Ed W0YK <ed at w0yk.com> Date: 2/17/18  6:10 AM  (GMT-08:00) To: "Larry (K8UT)" <K8UT at charter.net>, David G3YYD <g3yyd at btinternet.com> Subject: Re: Re[2]: X-QSO -- was: After the tough qso 
A red 'X' is put at the beginning of the QSO line in the native WriteLog log when the QSO line is tagged as unclaimed.  This feature has been in WriteLog for many years.  Before the we added X-QSO to the Cabrillo definition a few years ago, this feature resulted in the unclaimed QSO not being included in the Cabrillo file.  With the advent of X-QSO, WriteLog was changed to put the unclaimed QSO in the Cabrillo log as X-QSO.
73,Ed W0YK
-------- Original message --------From: "Larry (K8UT)" <K8UT at charter.net> Date: 2/17/18  3:56 AM  (GMT-08:00) To: Ed W0YK <ed at w0yk.com>, David G3YYD <g3yyd at btinternet.com> Subject: Re[2]: X-QSO -- was: After the tough qso 
{off reflector}
X-QSO? Fascinating. Had never heard of it.

How is an X-QSO indicated in the WriteLog Cabrillo output?

-larry (K8UT)

------ Original Message ------
From: "Ed W0YK" <ed at w0yk.com>
To: "David G3YYD" <g3yyd2 at btinternet.com>
Cc: rtty at contesting.com
Sent: 2018-02-17 06:40:37
Subject: Re: [RTTY] After the tough qso

>This is an excellent suggestion (X-QSO).  It is easy with WriteLog.  
>Just log the QSO and when convenient, right-click it in the log.  
>Select 'Mark QSO as unclaimed' and it becomes an X-QSO line in the 
>Cabrillo file.
>For loggers without this feature I simply make a note on the QSO, 
>either with the logger's note feature or on a noterpad I use during the 
>contest for corrections afterward.  After creating the Cabrillo file I 
>edit those QSO lines I want to be X-QSO.
>73,Ed W0YK
>-------- Original message --------From: David G3YYD via RTTY 
><rtty at contesting.com> Date: 2/17/18  1:09 AM  (GMT-08:00) To: 
>rtty at contesting.com Subject: Re: [RTTY] After the tough qso
>Whether I log a potentially incorrect QSO or not depends on the contest 
>scoring system. If there are no penalties for busted calls, incorrect 
>SR and so forth then I will log it.
>
>But if there are penalties for busted calls, etc then I will not log 
>it. I will have tried to complete the QSO but if it does not conclude 
>to my satisfaction I will not log it. Because I do not want to suffer a 
>penalty.
>
>There is away round this and that is to log the QSO and mark it as 
>X-QSO in the Cabrillo format. This means it is a check QSO and not one 
>submitted for points so then the other guy does not suffer a NIL. You 
>do not loose points either nor do you gain points. But how many contest 
>logging programs allow for this to be done at the time of logging the 
>Q? N1MM+ doesn't and that is the contest logger I have used for must be 
>2 decades now.
>
>73 David G3YYD
>
>
>-----Original Message-----
>From: RTTY [mailto:rtty-bounces at contesting.com] On Behalf Of Ed W0YK
>Sent: 16 February 2018 19:58
>To: Pierre Fogal; RTTY at contesting.com
>Subject: Re: [RTTY] After the tough qso
>
>This is an excellent  question, Pierre.
>I say log it.  If he didn't log it, then you will get a NIL.  But, if 
>he did log it and you didn't  then he gets the NIL.
>In a 50/50 situation like this, I take the risk of a NIL rather than 
>put that on the other station.  I think its good sportsmanship. 73,Ed 
>W0YK
>-------- Original message --------From: Pierre Fogal 
><pierre.fogal at gmail.com> Date: 2/16/18  10:09 AM  (GMT-08:00) To: 
>RTTY at contesting.com Subject: [RTTY] After the tough qso Hi folks,
>
>I haven't been doing RTTY contesting all that long, and I have done 
>what I can to read everything you sage folk out there write about 
>exchanges.  So, I hope I'm keeping mine succinct enough!
>
>What I'm not completing sure about, in the case of tough qsos 
>(interrupted or non-existent print) are the expectations of verifying 
>that it was actually completed and the other guy hasn't just given up.
>
>For example
>
>.... AB1CD  cq
>
>VE3KTB VE3KTB
>
>VE3KTB 599 991 991
>
>AB1CD 599 001 001 VE3KTB
>
>NR? NR?
>
>001 001 001
>
>Nr &%$#
>
>001 001 001
>
>@#$@#$ %4 &%$#
>
>001 001 001
>
>##$#$%^%$#
>
>& KTB $%*( AB1CD CQ
>The various %$&@ are to represent the non printable signals coming 
>through.  I can recognize things like '57' as 'TU' but I don't know if 
>he's got it or he's saying sorry ...
>
>So far, I've logged it unless I have a really strong sense that they 
>gave up.
>
>73,
>Pierre VE3KTB
>_______________________________________________
>RTTY mailing list
>RTTY at contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty
>_______________________________________________
>RTTY mailing list
>RTTY at contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty
>
>_______________________________________________
>RTTY mailing list
>RTTY at contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty
>_______________________________________________
>RTTY mailing list
>RTTY at contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty