[RTTY] Not in log errors
Jim Preston
jpreston1 at cox.net
Thu Jun 20 13:04:03 EDT 2013
Here's another example of how NIL happens.
I'm S&P in a contest where the exchange is already known, or can be done
from pre-fill.
W1XYZ: CQ TEST W1XYZ
ME: N6VH N6VH
W1XYZ: N6VH 599 [GIBBERISH]
ME: ? ?
W1XYZ: TU QRZ?
Since I didn't send my exchange, we did not have a valid QSO.
I go back to him and get B4.
I try calling him a few minutes later and get B4 again.
Since we didn't have a valid QSO, he is not in my log.
Incidentally, this actually happened in a recent contest.
73,
Jim N6VH
On 6/20/2013 6:55 AM, John GW4SKA wrote:
> That's good advice and should be part of normal good operating. It doesn't
> help when in run mode though. My CQ gets answered by W1XYZ, I send 'W1XYZ
> 599 001 001 ' and most times the response will be 'QSL 599 002 002 W1XYZ'. I
> have no way of knowing if he has logged my call correctly. Do I then ask him
> what call he has for me? No, he's already gone!
>
> It's just another example of balancing accuracy and rate; they will never
> both be optimum.
> John GW4SKA
>
>
>> --------------------------------------------------
>> From: "Derek Steele" <pixie at spiceisle.com>
>> Sent: Thursday, June 20, 2013 7:05 AM
>> To: "John GW4SKA" <ska at bartg.org.uk>
>> Subject: Re: [RTTY] 2013 Roundup Results
>>
>>> Just to add a little clarity to the NOT - IN - LOG problem. It does
>>> help to not assume that the other station received your report
>>> and wait for the QSL/TU message or a request for a retransmit
>>> from the other station before moving on.
>>>
>>> Derek - J35X
>>>
>>>
>>> See response to N5UWY below..............
>>>
>>>
>>> ___________________________________________________________
>>> That's just embarrassing. Lost a mult, even. Yeesh. Still get
>>> wallpaper for 1st, SOLP, OK section. But, man.
>>>
>>> ************************* Not In Log *************************
>>>
>>> 21115 RY 2013-01-05 2300 N5UWY OK W7YES OR
>>> 7081 RY 2013-01-06 0104 N5UWY OK VE3KI ON
>>> 7084 RY 2013-01-06 0257 N5UWY OK AA2DT NY
>>> 7049 RY 2013-01-06 0721 N5UWY OK G6PZ 0950
>>> 14090 RY 2013-01-06 2312 N5UWY OK J35X 1041
>>>
>>>
>>>
>>> --
>>> Peter Laws | N5UWY | plaws plaws net | Travel by Train!
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>> ___________________________________________________
>>>
>>>
>>> My response to Peter as follows.......
>>>
>>> --------------------------------------------------------
>>> Hello Peter,
>>> Was reading your post and saw you mention the
>>> not in log from me.
>>> Curiosity got the better of me and I checked the MMTTY log
>>> file from the contest. See for yourself what happened.
>>> -------------------------------------------------------------------
>>> .N4NIA QSL J35X CQ
>>> <130106 23:11:49 RX>
>>>
>>> W7/UYEQ89h
>>> 8X DWP
>>> W7 YAQMU
>>> N5UWY
>>> <130106 23:12:05 TX>
>>>
>>> .N5UWY 599 1041 1041
>>> <130106 23:12:11 RX>
>>> HJETXM/?SKX 5UXZQK
>>> <130106 23:12:18 TX>
>>> N5UWY
>>> .QRM AGN PSE ??
>>> <130106 23:12:24 RX>
>>>
>>> L?h V
>>> BX
>>> <130106 23:12:31 TX>
>>> N5UWY
>>> .QRM AGN PSE ??
>>> <130106 23:12:36 RX>
>>> WZN5UWY DE K6Z
>>> DK
>>> <130106 23:12:43 TX>
>>>
>>> .N5UWY 599 1041 1041 N5UWY
>>> <130106 23:12:50 RX>
>>> <130106 23:12:54 TX>
>>>
>>> .N5UWY 599 1041 1041 N5UWY
>>> <130106 23:13:01 RX>
>>> <130106 23:13:05 TX>
>>>
>>> .RU J35X J35X TEST
>>> <130106 23:13:10 RX>
>>> UQ
>>> -----------------------------------------
>>> Your report to me was lost in the QRM.
>>> Could not log anything. Sri about that.
>>>
>>> Derek - J35X
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------
>>> From: "John GW4SKA" <ska at bartg.org.uk>
>>> Sent: Thursday, June 20, 2013 4:05 AM
>>> To: "Mark" <n2qt at yahoo.com>; <ed at w0yk.com>
>>> Cc: "Don AA5AU" <aa5au at bellsouth.net>; "Jim W7RY" <w7ry at centurytel.net>;
>>> <rtty at contesting.com>
>>> Subject: Re: [RTTY] 2013 Roundup Results
>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Mark" <n2qt at yahoo.com>
>>>>> I assume the NILs are pure errors on my part, wish I knew what I did as
>>>>> they always seem
>>>>> to be the majority of my errors. I don't track uniques as I typically
>>>>> only have 1 or two,
>>>>> which I guess is from being in a well represented state/section.
>>>>>
>>>>> Mark. N2QT
>>>>
>>>> That's the wrong assumption. NILs are most likely to be because someone
>>>> copied your call wrong in their log. Not much you can do about that
>>>> other than watch the screen and hope to see your call is correct at the
>>>> time of the QSO. Anything else takes too long and breaks the rhythm.
>>>> John GW4SKA
>>>> _______________________________________________
>>>> 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
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.3345 / Virus Database: 3199/6425 - Release Date: 06/19/13
>>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
More information about the RTTY
mailing list