RTTY
[Top] [All Lists]

Re: [RTTY] Spotting question

To: RTTY Reflector <rtty@contesting.com>
Subject: Re: [RTTY] Spotting question
From: Al Kozakiewicz <akozak@hourglass.com>
Date: Mon, 10 Jan 2011 21:02:35 -0500
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Don't know if it's a related problem, but when I first started using RTTY it 
was with AFSK.  I would setup MMTTY so that the mark/space tones were within a 
reasonable place in the receiver passband, which was never at 2295/2125.

Which meant that if I had spotted a station, the spot frequency would never be 
the "real" carrier +/- 2295 or whatever the math is.

As a result, I avoided spotting RTTY DX until I set up for FSK.

Al
AB2ZY

-----Original Message-----
From: rtty-bounces@contesting.com [mailto:rtty-bounces@contesting.com] On 
Behalf Of David Levine
Sent: Monday, January 10, 2011 8:53 PM
To: RTTY Reflector
Subject: Re: [RTTY] Spotting question

Thanks to Jim, AD1C, on what command to send to the cluster so I can see what 
was spotted around the frequency I was on. All I found though was one other 
legitimate call 2 Khz up. So I'm really at a loss why during those 15 mins of 
calling CQ I had multiple ops already logged call me again. No other time 
during the entire contest did I have a single station call me that was logged 
as a dup.  I guess the mystery continues unless someone has another idea.

And thanks again to AD1C for the info on how to check. In case others are 
interested the command was:
SH/DX/99 3579-3581

73,
David

On Mon, Jan 10, 2011 at 4:10 PM, David Levine <david@levinecentral.com>wrote:

> I ran unassisted without the cluster in this weekends contest. Sunday 
> between 22:44 and 23:02 I noticed a few stations calling me again on 
> 80m after I had already worked them on that band. Despite me sending 
> my call at least 1 additional time to each, they kept sending theirs 
> so I logged them again. My only guess is that there was a bad spot posted.
>
> I checked DXSummit and searched for my call and there were just 3 from 
> Sat
> night:
>
> W1MAW      <http://www.qrz.com/db/W1MAW>      3567.2 K2DSL        
> <http://www.qrz.com/db/K2DSL>                                    0327 09 Jan  
>  United StatesW4EE       <http://www.qrz.com/db/W4EE>      3567.9 K2DSL       
>  <http://www.qrz.com/db/K2DSL>                                    0322 09 Jan 
>   United StatesN2FF       <http://www.qrz.com/db/N2FF>      3565.8 K2DSL      
>   <http://www.qrz.com/db/K2DSL> RTTY                               0321 09 
> Jan   United States
>
> I checked my log and N2FF posted the correct frequency so I'm guessing the 
> other two were probably not adjusted properly for their offset. But my 
> question is if there is a way to see what might have been spotted between 
> 22:44 and 23:02 Sunday around the frequency of 3580 +/- 1? Any trick on 
> DXSummit or another site to try and find out? DXWatch also allows searching, 
> but again only by callsign for what I can find. Any suggestions?
>
> K2DSL - David
>
>
>
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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