[RTTY] Poor SO2R Operators in BARTG

[Phil Snyder]

I gave up on the contest after I got a message through my telnet 
connection ( I have never gotten a message that way before, and have no 
idea how to answer) that said

  "listen im calling u on rtty"

  I have an S9 power line noise here and couldn't hear the station the 
message was from even though I was beaming almost directly at him. I am 
most definitely not SO2R.

Phil
N9LAH

On 1/26/2013 5:27 PM, Jeff Blaine wrote:
> I agree with Dave.  It's possible they are attending some other band, 
> however, they may also have tuning or AFC problems.  MMTTY (for 
> example) will fail to decode because you are not tuned properly to the 
> sender (wtih AFC off) or if the AFC is pulled by another signal to one 
> side.  Both of those can make you pull your hair out as you grumble 
> trying to figure out which button you have not pushed or whatever.
>
> 73/jeff/ac0c
> www.ac0c.com
> alpha-charlie-zero-charlie
>
> -----Original Message----- From: Dave Hachadorian
> Sent: Saturday, January 26, 2013 2:37 PM
> To: RTTY reflector
> Subject: Re: [RTTY] Poor SO2R Operators in BARTG
>
> You can tell if they are so2r by writing down the call signs, and
> checking 3830 tomorrow to see if they enter the expert category.
> There's no faking it because of the BARTG band-change limit for
> non-experts.
>
> I have seen a lot of cases where even an so1r operator just does
> not respond.  They may have terrific local QRN, or have a decode
> setting wrong, or perhaps their decode mark/space frequency has
> been pulled off nominal.
>
> Dave Hachadorian, K6LL
> Yuma, Arizona
>
>
>
> -----Original Message----- From: Dick Kriss
> Sent: Saturday, January 26, 2013 1:11 PM
> To: Jeff Stai ; RTTY Reflector
> Subject: Re: [RTTY] Poor SO2R Operators in BARTG
>
> Jeff WK6I,
>
> You may be right but to me it seemed like he may have been busy
> on another band and just had the timer set to continue calling CQ
> on the other band.  Nobody can be that deaf for that long.
>
> Dick
>
>
> On Jan 26, 2013, at 2:03 PM, Jeff Stai <wk6i.jeff at gmail.com>
> wrote:
>
>> hi Dick - Just wanting to understand... not responding to anyone 
>> sounds more like they may have a receiver problem? I don't see the 
>> connection to SO2R. - jeff wk6i
>>
>> On Sat, Jan 26, 2013 at 11:15 AM, Dick Kriss <aa5vu at att.net> wrote:
>> I will not give the call signs but there are some RTTY operators that 
>> seem to lack the skills to run SO2R.  It is very easy to spot them as 
>> they keep calling CQ over and over again and don't seem to ever 
>> listen for the stations. All they do is create confusion when several 
>> are responding to their CQ and they do not respond to anyone. I used 
>> the think telephone call waiting was rude but poor SO2R operators as 
>> just as bad.
>>
>> Dick AA5VU
>> _______________________________________________
>> RTTY mailing list
>> RTTY at contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>>
>>
>> -- 
>> Jeff Stai ~ wk6i.jeff at gmail.com
>> Twisted Oak Winery ~ http://www.twistedoak.com/
>> Facebook ~ http://www.facebook.com/twistedoak
>
> _______________________________________________
> 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
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2890 / Virus Database: 2638/6034 - Release Date: 01/15/13
> Internal Virus Database is out of date.
>
>