CQ-Contest
[Top] [All Lists]

RE: [CQ-Contest] arrl dx cw spotting

To: "David Robbins K1TTT" <k1ttt@arrl.net>,"'reflector cq-contest'" <CQ-Contest@contesting.com>
Subject: RE: [CQ-Contest] arrl dx cw spotting
From: "SM3CER (7S3A)" <jan-eric.rehn@telia.com>
Date: Mon, 23 Feb 2004 20:03:19 +0000
List-post: <mailto:cq-contest@contesting.com>
At 19:16 2004-02-23, David Robbins K1TTT wrote:
> Hello,
>
> Here's a dumb question:
> I searched the DX-Summit Spot Database and found this:
>
> Spotter    Freq   DX                     Time Date
> K1TTT      1834.4 K1TTT                  2335 21 Feb 2004
>
> Someone using the call K1TTT as the spotter or self spotting???
>
> Just curious...
>
> 73 de Jan/SM3CER

Must have been an operator error making a log entry and spot.  Here is
what is in the log around that time...
       DATE    TIME   NUMBER FREQ   CALL         RCVD    NEW MULTS   PTS
    21-Feb-04  2240    101   1830  GM3UA        599 100       GM      3
    21-Feb-04  2242    102   1830  OL1A         599 KW                3
    21-Feb-04  2243    103   1830  G3MLO        559 400               3
    21-Feb-04  2248    104   1826  HA8BE        599 K                 3
    21-Feb-04  2259    105   1831  OE8CIQ       599 400               3
    21-Feb-04  2300    106   1831  DL7CX        599 400               3
    21-Feb-04  2301    107   1830  LY3UM        599 KW                3
    21-Feb-04  2316    108   1839  UX5NQ        599 100       UR      3
    21-Feb-04  2323    109   1834  K1TTT        599 KW                0
    21-Feb-04  2338    110   1832  EI3IO        599 400               3

    21-Feb-04  2347    111   1834  HB9BLQ       599 600       HB      3
    21-Feb-04  2353    112   1834  G3LZQ        599 400               3
    21-Feb-04  2356    113   1837  DL5CT        599 500               3
    21-Feb-04  2357    114   1837  GM0F         599 400               3
    21-Feb-04  2358    115   1837  DL8LAS       599 100               3
    22-Feb-04  0002    116   1837  OE4PWW       599 100               3
    22-Feb-04  0003    117   1837  G3NEO        599 100               3
    22-Feb-04  0009    118   1841  HA0DU        599 500               3
    22-Feb-04  0012    119   1833  G3XTT        599 400               3
    22-Feb-04  0013    120   1833  G3HBR        599 300               3

the operator must have deleted the call at 1834z by replacing it with
k1ttt (ct doesn't let you delete, so this is common practice if you
enter something accidentally)  then he must have tried to send a spot
and if you haven't typed in a new call ct spots the last thing you
logged on that station.  As you can see we aren't running on that
frequency at the time.


David Robbins K1TTT e-mail: mailto:k1ttt@arrl.net web: http://www.k1ttt.net AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net


Hello,

Thanks Dave!
It's quite clear it could have happened as you describe it...
As I wrote earlier - I was just curious.
On the other hand - I learned a new thing about CT - again... :-)

73 de Jan/SM3CER

---------------------------------------------------------------
   The world's top contesters battle it out in Finland!
THE OFFICIAL FILM of WRTC 2002 now on professional DVD and VHS!
      http://home1.pacific.net.sg/~jamesb/
---------------------------------------------------------------

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>