Return-Path: Received: from mtain-dj03.r1000.mx.aol.com (mtain-dj03.r1000.mail.aol.com [172.19.187.139]) by air-md05.mail.aol.com (v129.4) with ESMTP id MAILINMD051-8b844d57a87521c; Sun, 13 Feb 2011 04:46:29 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dj03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0ADC9380001BE; Sun, 13 Feb 2011 04:46:27 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PoYVs-0004ky-JT for rs_out_1@blacksheep.org; Sun, 13 Feb 2011 09:45:04 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PoYVr-0004kp-2N for rsgb_lf_group@blacksheep.org; Sun, 13 Feb 2011 09:45:03 +0000 Received: from out1.ip06ir2.opaltelecom.net ([62.24.128.242]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PoYVp-0002pB-Af for rsgb_lf_group@blacksheep.org; Sun, 13 Feb 2011 09:45:03 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AikBAK82V01cHYtw/2dsb2JhbACIW45MjltzuRmFXgSPSw X-IronPort-AV: E=Sophos;i="4.60,464,1291593600"; d="scan'208";a="490445929" Received: from unknown (HELO xphd97xgq27nyf) ([92.29.139.112]) by out1.ip06ir2.opaltelecom.net with SMTP; 13 Feb 2011 09:44:54 +0000 Message-ID: <001101cbcb62$a9befa10$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <00c301cbcb04$b57989a0$0401a8c0@xphd97xgq27nyf><00dd01cbcb0a$b7f1f4f0$0401a8c0@xphd97xgq27nyf><00eb01cbcb0d$6a82ee10$0401a8c0@xphd97xgq27nyf> <012001cbcb15$e63c14c0$0401a8c0@xphd97xgq27nyf> <433CFC410770450186BB307A8AD28484@JimPC> Date: Sun, 13 Feb 2011 09:44:51 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: Re: CQ WW 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-global-disposition: G x-aol-sid: 3039cdbc9d074d57a8735e29 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Jim Not sure to whom u are addressing your QSO procedure remarks. I have made numerous QSO'S over the years on QRS mode and know exactly how to proceed and do agree with you, but I hope others take notice. I have noticed this year that QRS QSO'S are getting far too long winded by some sending Name and Locator for example. also prolonged sending of callsign when an ID is already established. Some have got so used to Beacon mode that they have forgotton how to engage in a QSO. QSO mode needs procedural Skill whereas the beacon operator just plugs away hoping that he might be heard/seen and generates lots of QRM into the bargin. I copied XGJ solid last nite on his first call but unfortunately he had QRM problems and I did a QSY and he missed my request to STOP so that I could give him a OOO report and hopefully receive one back. The previous nite I was visible on the Jay and Dex grabbers which they kindly switched on. With my antenna system at present, same TX/RX antenna, TA signals peak around 2400 utc building up before and tapering off after then peak again just before sunrise. You know my LF antenna system, 3 x inv L in parallel each approx 100 ft vertical and 450 ft horizontal tapering down at the far end, small litz wound loading coil and matched to 50 ohms going to TX/RX Power at present about 0.5 w erp and can QRO to 1 w erp from home made TX 73 de mal/g3kev ----- Original Message ----- From: "James Moritz" To: Sent: Sunday, February 13, 2011 2:46 AM Subject: LF: Re: CQ WW > Dear Warren, Mal, LF Group, > > I took the opportunity of your sked to try simultaneous reception of the Eu > / NA QRSS windows - really, I was hoping G3XDV would be transmitting as > well, since he is only about 11km from me and would be a good challenge for > the receiver. I think it is possible by carefully adjusting the various > gains to reduce the "splatter" caused by such a local signal to allow the > copy of relatively DX signals within a few hertz. This didn't happen, but I > was able to simultaneously receive WD2XGJ, G3KEV, PA0A, RA3AGC and DF6NM. > The attachment shows signals from about 2245 - 0112utc; it is screen shots > from two instances of SpecLab edited together, and the scroll rate was > increased at about 0000, which is why the time markers don't match up > perfectly. > > Concerning QSOs in QRSS with very long dot periods, I think this shows how > it is most important to agree the format and the protocol for the QSO before > starting. I think the generally accepted format goes something like: > > XGJ KEV K (for a sked, or CQ KEV K for a random QSO, repeat as necessary) > ...then... > KEV XGJ O K > XGJ KEV R O K > KEV XGJ R TU SK ...(end of QSO) > > It is probably best to decide from experience who is likely to be the weaker > received signal, and for that station to make the initial calls, since then > subsequent overs are most likely to succeed. If one station fails to > completely receive an over, they should repeat their previous over so that > the other station can repeat also. Some will insist that complete callsigns > should be used for the initial overs, but I think most agree on the > abbreviated calls, especially for a sked. Some people omit the "K" at the > end of an over, or substitute an "E", but I think this is a bad idea because > under marginal conditions it is harder to tell when the other station has > stopped transmitting. > > Hope this is helpful - better luck next time! > > Cheers, Jim Moritz > 73 de M0BMU >