Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Poor\s+SO2R\s+Operators\s+in\s+BARTG\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Poor\s+SO2R\s+Operators\s+in\s+BARTG\s*$/: 12 ]

Total 12 documents matching your query.

1. [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Dick Kriss <aa5vu@att.net>; Date: Sat, 26 Jan 2013 13:15:16 -0600; 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 e; /archives//html/RTTY/2013-01/msg00272.html (6,631 bytes)
2. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Sat, 26 Jan 2013 12:03:47 -0800; 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 -- Jeff Stai ~ wk6i.jeff@gmail.com; /archives//html/RTTY/2013-01/msg00273.html (9,165 bytes)
3. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Dick Kriss <aa5vu@att.net>; Date: Sat, 26 Jan 2013 14:06:32 -0600; Good point! _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/mailman/listinfo/rtty; /archives//html/RTTY/2013-01/msg00274.html (8,122 bytes)
4. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Dick Kriss <aa5vu@att.net>; Date: Sat, 26 Jan 2013 14:11:05 -0600; 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.; /archives//html/RTTY/2013-01/msg00275.html (9,709 bytes)
5. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Tom Haavisto <kamham69@gmail.com>; Date: Sat, 26 Jan 2013 15:21:55 -0500; Maybe he fell asleep. Went for dinner, went to the can, whatever, and left his gear running to "hold the frequency" Poor operation? YES. Does not mean he is an SO2R op. Tom - VE3CX __________________; /archives//html/RTTY/2013-01/msg00276.html (8,949 bytes)
6. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Sat, 26 Jan 2013 12:27:00 -0800; Fair enough, though are other possible reasons. I agree that an SO2R station should not CQ if they are not ready to respond. - jeff wk6i -- Jeff Stai ~ wk6i.jeff@gmail.com Twisted Oak Winery ~ http:/; /archives//html/RTTY/2013-01/msg00277.html (10,479 bytes)
7. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Dick Kriss <aa5vu@att.net>; Date: Sat, 26 Jan 2013 14:28:11 -0600; Another good point or he took a potty break and did not want give up the freq. I may have been too quick to blame it on SO2R. HiHi _______________________________________________ RTTY mailing list RT; /archives//html/RTTY/2013-01/msg00278.html (8,470 bytes)
8. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Sat, 26 Jan 2013 12:32:29 -0800; Every potty break is an opportunity to learn how to find a run freq. faster. ;) (pun not intended!) My first guess would have been that he isn't listening where he is transmitting. An AFC/NET problem; /archives//html/RTTY/2013-01/msg00279.html (9,241 bytes)
9. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: "Dave Hachadorian" <k6ll@arrl.net>; Date: Sat, 26 Jan 2013 13:37:21 -0700; 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-; /archives//html/RTTY/2013-01/msg00281.html (10,898 bytes)
10. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: "Jeff Blaine" <keepwalking188@yahoo.com>; Date: Sat, 26 Jan 2013 17:27:45 -0600; 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; /archives//html/RTTY/2013-01/msg00282.html (11,746 bytes)
11. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Phil Snyder <n9lah@comcast.net>; Date: Sat, 26 Jan 2013 19:23:38 -0600; "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. Ph; /archives//html/RTTY/2013-01/msg00283.html (12,657 bytes)
12. Re: [RTTY] Poor SO2R Operators in BARTG (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Sat, 26 Jan 2013 18:27:05 -0800; <snip> REPLY: It seems to me that with an S9 noise level you shouldn't be CQing. Do S&P only and the problem goes away. Bill, W6WRT _______________________________________________ RTTY mailing list R; /archives//html/RTTY/2013-01/msg00284.html (8,741 bytes)

Current List: 1 - 12
Page: [1]