Return-Path: Received: from rly-dc04.mx.aol.com (rly-dc04.mail.aol.com [172.19.136.33]) by air-dc05.mail.aol.com (v120.9) with ESMTP id MAILINDC053-b184743f35f36b; Wed, 21 Nov 2007 03:59:18 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc04.mx.aol.com (v120.9) with ESMTP id MAILRELAYINDC044-b184743f35f36b; Wed, 21 Nov 2007 03:59:13 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1IulPO-0003sG-Mw for rs_out_1@blacksheep.org; Wed, 21 Nov 2007 08:58:10 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1IulPO-0003s7-3c for rsgb_lf_group@blacksheep.org; Wed, 21 Nov 2007 08:58:10 +0000 Received: from sighthound.demon.co.uk ([80.177.174.126]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1IulPL-0000ig-8d for rsgb_lf_group@blacksheep.org; Wed, 21 Nov 2007 08:58:09 +0000 Received: from lurcher.twatt.local (lurcher.twatt.local [127.0.1.1]) by lurcher.twatt.local (Postfix) with ESMTP id 5A118DA4D8 for ; Wed, 21 Nov 2007 08:58:01 +0000 (GMT) Date: Wed, 21 Nov 2007 08:58:00 +0000 From: John Pumford-Green GM4SLV To: Message-ID: <20071121085800.35fcfb1d@lurcher.twatt.local> Organization: The Gammy Bird X-Mailer: Claws Mail 2.10.0 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 X-Spam-Score: 0.2 (/) X-Spam-Report: autolearn=disabled,RCVD_ILLEGAL_IP=0.234 Subject: LF: Cross-band etiquette Content-Type: text/plain; charset=US-ASCII 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 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