3830
[Top] [All Lists]

Re: [3830] ARRLDX CW ON4UN SOSB/80 HP

To: "Dave Lawley" <g4buo@compuserve.com>
Subject: Re: [3830] ARRLDX CW ON4UN SOSB/80 HP
From: "john devoldere" <john.devoldere@pandora.be>
Date: Tue, 22 Feb 2005 23:46:43 -0000
List-post: <mailto:3830@contesting.com>
Hello Dave:

 I did not want to drag this into the open, but, as you copied "3830", I feel I 
must do the same.

Here is a copy of that periode of time of my log:

 3513 CW 2005-02-19 0618 OO4UN         599 KW     K3NK          599 PA          
   3
 3513 CW 2005-02-19 0618 OO4UN         599 KW     N0FP          599 MN          
   0
 3513 CW 2005-02-19 0620 OO4UN         599 KW     K4IK          599 FL          
   3
 3513 CW 2005-02-19 0621 OO4UN         599 KW     W6RBR         599 MO          
   3
 3513 CW 2005-02-19 0621 OO4UN         599 KW     K0HIP         599 AR          
   3
 3513 CW 2005-02-19 0622 OO4UN         599 KW     WB5STU        599 TX          
   3
 3513 CW 2005-02-19 0623 OO4UN         599 KW     K3WW          599 PA          
   3
 3513 CW 2005-02-19 0624 OO4UN         599 KW     N8IY          599 WV          
   3
 3513 CW 2005-02-19 0625 OO4UN         599 KW     N5CHA         599 TX          
   3
 3513 CW 2005-02-19 0625 OO4UN         599 KW     WA2DKJ        599 NJ          
   3
 3513 CW 2005-02-19 0627 OO4UN         599 KW     N6AA          599 CA          
   3
 3513 CW 2005-02-19 0628 OO4UN         599 KW     WB0HCH        599 MN          
   3
 3513 CW 2005-02-19 0628 OO4UN         599 KW     K5AM          599 NM          
   3
 3513 CW 2005-02-19 0629 OO4UN         599 KW     NE8Z          599 MI          
   3
 3503 CW 2005-02-19 0634 OO4UN         599 KW     W0FS          599 IA          
   3
 3503 CW 2005-02-19 0635 OO4UN         599 KW     WB9NMN        599 CO          
   3
 3503 CW 2005-02-19 0636 OO4UN         599 KW     K2YLH         599 NJ          
   3
 3503 CW 2005-02-19 0638 OO4UN         599 KW     K0TG          599 MN          
   3
 3503 CW 2005-02-19 0638 OO4UN         599 KW     NX7U          599 AZ          
   3
 3503 CW 2005-02-19 0639 OO4UN         599 KW     K5BOC         599 AR          
   3
 3503 CW 2005-02-19 0640 OO4UN         599 KW     WB9FIU        599 IN          
   3
 3503 CW 2005-02-19 0640 OO4UN         599 KW     VE7CC         599 BC          
   3
 3503 CW 2005-02-19 0642 OO4UN         599 KW     N6MW          599 VA          
   3
 3503 CW 2005-02-19 0644 OO4UN         599 KW     W3BC          599 VA          
   3
 3503 CW 2005-02-19 0647 OO4UN         599 KW     WB0TEV        599 TX          
   3
 3503 CW 2005-02-19 0648 OO4UN         599 KW     K7RAT         599 OR          
   3
 3503 CW 2005-02-19 0649 OO4UN         599 KW     N6IG          599 CA          
   3
 3503 CW 2005-02-19 0650 OO4UN         599 KW     K9RS          599 IL          
   3
 3503 CW 2005-02-19 0650 OO4UN         599 KW     K7OX          599 WA          
   3
 3503 CW 2005-02-19 0651 OO4UN         599 KW     K5CM          599 OK          
   3
 3503 CW 2005-02-19 0651 OO4UN         599 KW     WA7FKV        599 NV          
   3
 3503 CW 2005-02-19 0652 OO4UN         599 KW     N6RK          599 CA          
   3
 3503 CW 2005-02-19 0652 OO4UN         599 KW     AA5AM         599 TX          
   3
 3503 CW 2005-02-19 0654 OO4UN         599 KW     K4OH          599 SC          
   3
 3503 CW 2005-02-19 0654 OO4UN         599 KW     N5AW          599 TX          
   3
 3503 CW 2005-02-19 0655 OO4UN         599 KW     K1BD          599 NH          
   3
 3503 CW 2005-02-19 0656 OO4UN         599 KW     K7WP          599 AZ          
   3
 3503 CW 2005-02-19 0659 OO4UN         599 KW     KD0IE         599 NE          
   3
 3503 CW 2005-02-19 0702 OO4UN         599 KW     NU4B          599 TN          
   3
 3503 CW 2005-02-19 0704 OO4UN         599 KW     N8NQ          599 MI          
   3

So at 0628 I was on 3513 (actually it was 3513.1 my log shows the extra digit, 
the export file does not). My clock is synchronized using Tardis, so it is 
correct within a second or better. Then, at 06:34, after a couple minutes 
break) I moved to 3503.2. My strategy when moving is always: ask a "?" on a 
seemingly clear frequency, wait 1 second, then a second and a third "?" with a 
second or two in between. Then just send my call once. When still nothing heard 
I go "QRL?" 2  or 3 times. And when at that time nobody replies it is "my 
frequency". If I want to keep a frequency, I will also never go away from my 
operating position, not even for a "pee". 

 

As to spots on the cluster: here is what I find (in chronological order) on the 
cluster:

 

06:28     3513.2

06:38     3503.4

06:49     3503.1

 

Notice in  my log I never went to 3504.3 ten minutes later, as you wrote. I 
said on 3503 and a a shade, just until about the end of the contest (my sunrise 
around 07:00z) 



>From my log and from the spots I conclude I was on 3513 at 06:28 when Dave 
>says "trouble started"

 

The spots confirm my log, I moved to 3503 somewhere between 06_28 and 06:38, in 
fact it was 06:34.

 

All I can say is that all of a sudden I heard G4BUO very close (but lower) than 
the frequency I was on. I always use 300-400 Hz selectivity in this kind of 
contest, and sometimes, when  it get rough I can narrow it down to 200 Hz or 
even less. 

 

Either your comments are off 6 minutes (that a real rubber clock situation)  
and in that case I am 100% pertinent that when I came on this "new" frequency 
at 0634, it was clear and remained clear all the time I went through the "clear 
frequency" procedure as outlined above.

 

This situation happened only once in this contest, during the past 160 CW even 
2 or 3 times. I was so positively sure that I was on a clear frequency that 
your reply really upset me. I am very, very strict in this respect, and will 
always follow the outlined procedure. Despite all of this it happens every now 
and then that after a minute or two someone comes back and says "..., I was 
here. Look on the cluster, I was spotted here". That of course does not mean a 
thing. A frequency is yours as long you are there. If you go but for 30 
seconds, during which someone else goes through the "clear frequency?" 
procedure than it is no longer yours, even if you have been spotted there for 
hours before. I do not say that this is what happened in this case, but that 
happens all too frequently, and in many case they do not go away for a pee but 
to work a multiplier they read of the cluster screen. 

 

Now what did I do after our short argument? I moved up a couple hundred Hz, to 
avoid your signal, and that was it. With the 300 or 400 Hz selectivity that can 
make a lot of difference. Also, like I wrote, I had the impression that you had 
"drifted" up  a bit. Well, I immediately checked the TX frequency on the log 
(logs with 10 Hz accuracy) and I had not moved. I always take into 
consideration that I could have made an error, but after checking the frequency 
on the log, it proved I sure had not moved. But, to avoid more of an argument I 
moved a few hundred Hz. After that I did not hear you any more. 



I know you Dave, and you are a good operator, and just like you I thought "why 
does he not think for a minute he made an error"? But it all was not worth a 
"real" fight, like I said I went up a little after an argument that did not 
last more than one minute. 

 

I think that I worded the incident very nicely in my little story, not arrogant 
at all, so I really feel no need to change the wording. You asked for comments, 
so here they were.

 

I hope you did enjoy the contest and made a great score. 

 

73, John, ON4UN



----- Original Message ----- 
From: "Dave Lawley" <g4buo@compuserve.com>
To: "3830" <3830@contesting.com>
Cc: <john.devoldere@pandora.be>
Sent: Tuesday, February 22, 2005 10:16 PM
Subject: Re: ARRLDX CW ON4UN SOSB/80 HP 


> ON4UN wrote:
> 
> >Talking about "my" frequency, I only had one
> >"little" frequency "argument", with G4BUO, who drifted onto my channel.
> >My logging program (N1MM, the best), logs the transmit frequency with
> >10 Hz accuracy, so I know where I am. Also, I never use a RIT, I always
> >use one VFO (B) to transmit, while the A VFO is used for receive, this
> >way I stay "put".
> 
> Here it is from the other side:
> 
> I operate with wide filters when possible and had been on 3503.5 for 
> about 25 minutes. OO4UN was nowhere either side that I could hear, then 
> all of a sudden he sends "TU OO4UN" and starts trying to use my frequency.
> 
> My run radio doesn't have memories, nor a second VFO, and the dial and
> frequency display stayed put. It doesn't have a beverage input either, 
> so I had the MP tuned to the same frequency so that I could use the 
> beverage to pick out weak ones. Some time after this frequency fight 
> started, I switched to receive on the MP just to confirm my transmit 
> frequency had indeed not changed.
> 
> After some minutes of slugging it out we had an "exchange". I told him I 
> had been on there for 30 minutes to which the reply was "that is a lie". 
> Now I don't like to hear that sort of response and tried to suggest he 
> consider the possibility that he was the one at fault, but that I would 
> not stoop to using that sort of language.
> 
> Using alt-N I made a note that the time when the trouble started was at 
>  0628z. Now I've looked for OO4UN on the cluster and he was spotted at 
> 0628z on 3513.4, he's then spotted on 3504.3 ten minutes later. So if 
> one of us had been on 3503.5 for the past 30 minutes, it wasn't OO4UN.
> 
> John, a little humility is called for and acceptance of the possibility 
> that you might be the one who was in the wrong on this occasion.
> 
> 73, Dave G4BUO
> 
> 
>
______________________________________________
3830 mailing list
3830@contesting.com
http://lists.contesting.com/mailman/listinfo/3830

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