Return-Path: Received: from rly-mg09.mx.aol.com (rly-mg09.mail.aol.com [172.20.83.115]) by air-mg03.mail.aol.com (v120.9) with ESMTP id MAILINMG033-a324744020719d; Wed, 21 Nov 2007 05:02:04 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mg09.mx.aol.com (v120.9) with ESMTP id MAILRELAYINMG094-a324744020719d; Wed, 21 Nov 2007 05:01:46 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1IumOU-000490-Qp for rs_out_1@blacksheep.org; Wed, 21 Nov 2007 10:01:18 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1IumOU-00048r-5u for rsgb_lf_group@blacksheep.org; Wed, 21 Nov 2007 10:01:18 +0000 Received: from smtpout0163.sc1.he.tucows.com ([64.97.136.163] helo=n066.sc1.he.tucows.com) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1IumOQ-0001HQ-VR for rsgb_lf_group@blacksheep.org; Wed, 21 Nov 2007 10:01:18 +0000 Received: from sc1-out05.emaildefenseservice.com (64.97.139.2) by n066.sc1.he.tucows.com (7.2.069.1) id 47030B3A003E57E7 for rsgb_lf_group@blacksheep.org; Wed, 21 Nov 2007 10:01:08 +0000 X-SpamScore: 30 X-Spamcatcher-Summary: 30,2,0,982ccae85b97e822,abc867c618cd1129,g3kev.ham@virgin.net,-,RULES_HIT:355:379:539:540:541:542:543:567:599:600:601:945:946:960:966:973:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1535:1543:1587:1593:1594:1711:1730:1747:1766:1792:2073:2075:2078:2110:2194:2196:2198:2199:2200:2201:2379:2393:2540:2551:2553:2559:2562:2693:2729:2828:2892:2916:3027:3294:3354:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:4225:4250:4385:4648:5007:6119: 6248:7576,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none X-Spamcatcher-Explanation: (100%) BODY: contains "rx"; Received: from g3kev (unknown [64.97.206.40]) by sc1-out05.emaildefenseservice.com (Postfix) with SMTP for ; Wed, 21 Nov 2007 10:01:06 +0000 (UTC) Message-ID: <003201c82c25$6f6d3820$16e4fc3e@g3kev> From: "hamilton mal" To: References: <20071121085800.35fcfb1d@lurcher.twatt.local> Date: Wed, 21 Nov 2007 09:45:36 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: Cross-band etiquette Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-AOL-IP: 193.82.116.20 X-AOL-SCOLL-AUTHENTICATION: listenair ; SPF_helo : n X-AOL-SCOLL-AUTHENTICATION: listenair ; SPF_822_from : n Its the way you "TELL THEM" john. Have you heard the one about the " WHINGING POME" G3KEV ----- Original Message ----- From: "John Pumford-Green GM4SLV" To: Sent: Wednesday, November 21, 2007 8:58 AM Subject: LF: Cross-band etiquette > Hello LF, > > It is normal, polite amateur practice to a) listen for a few minutes and > b) send a signal such as QRL? when selecting an operating frequency. > > On 500kHz itself this is rarely a problem, as band occupancy is > generally low. This doesn't mean it is never an issue, even on > 500, though. > > However I've become aware recently of neglect of this courtesy when > using cross-band for contacts with non-UK or non-NoV stations. > > Last night, as an example, a 3-way cross-band QSO was ongoing between > 2 UK stations on 501.316kHz and a PA station on 3533kHz. > > A 500kHz station (no names, no pack drill) was heard calling "CQ QSX > 3533/7033" on another 500 frequency (the beauty of having 2 receivers on > 500) and then, without checking if 3533 was in use.... no "QRL?" or > other courtesy was given..... he started calling on 3533 "CQ QSX > 502"... and then proceeded to alternate between the 2 bands until he > got his desired cross-band QSO. Why he calls on 80m "QSX 502" is > a mystery to me ...surely he isn't expecting a "reverse cross-band QSO" > with an existing 500 NoV holder? Why not do it all on 500? > > > > The QSO already underway was swiftly and politely abandoned, both on 500 > and 3533 to make way, without any fuss and in a way that was perhaps > unnoticed to the station concerned. > > Sadly this isn't the first time I've observed such behaviour. > > Occasionally a non-MF aware station will call on 3533, not knowing that > it's being monitored for cross-band replies, and it's perhaps > excusable - not everyone knows of, or is interested in, MF. Even if > they call "QRL? it might not be possible to reply to them. Many of us > have "RX only" setups for the 80m side. In this instance the correct > thing for us is to move our 80m RX frequency and announce it in our CQ > calls. > > > I find it disappointing however that active MF stations seem to blindly > assume that 3533 is free for their use and don't first a) check 500 for > obvious cross-band activity away from their own 500 frequency nor > b) check 3533 itself. A quick tune round 500 would have quickly made it > obvious that a cross-band QSO was underway. > > If 3533 is in use they are free to find another nearby frequency and > announce it in their calls, surely? I've done this many times and still > had successful contacts. There's nothing magic in 3533 itself. > > > I see regular complaints here decrying the poor operating abilities of > the current "non-CW" generation, mainly from one source. > > I suggest we all need to check our methods and motives. > > For some stations the driving force seems to be "DX DX DX" and first > sniff of an new QSO, in-band or cross-band, and out come all the shoddy > practices of general HF operation - calling without listening, ignoring > other QSOs underway, assuming ownership of certain frequencies. > > It's bad manners and poor operating. > > 500 isn't a "DX at all costs" band - it's an experimental allocation > where the passing of information and observing of signal strengths and > propagation conditions should be more important than a "569 QRU 73" > QSO just to get another new country in the log. > > Just sticking to single 500kHz and 80m frequencies and blindly calling > "CQ" regardless of what is already happening on the band(s) is simply > indicative of poor operating ability. > > Cheers, > > John > GM4SLV > > >