Return-Path: Received: from mtain-mj01.r1000.mx.aol.com (mtain-mj01.r1000.mail.aol.com [172.21.164.85]) by air-de07.mail.aol.com (v129.4) with ESMTP id MAILINDE072-5ebb4cf68f831d7; Wed, 01 Dec 2010 13:10:11 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mj01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 348E038000161; Wed, 1 Dec 2010 13:10:08 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PNr73-000432-36 for rs_out_1@blacksheep.org; Wed, 01 Dec 2010 18:09:05 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PNr72-00042t-IK for rsgb_lf_group@blacksheep.org; Wed, 01 Dec 2010 18:09:04 +0000 Received: from mail-ww0-f47.google.com ([74.125.82.47]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PNr70-0007Dw-Q3 for rsgb_lf_group@blacksheep.org; Wed, 01 Dec 2010 18:09:04 +0000 Received: by wwb13 with SMTP id 13so11395wwb.28 for ; Wed, 01 Dec 2010 10:08:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:references:from :content-type:x-mailer:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; bh=C/BuRWgURcNrMVezbvnqTczEcIAqpSs1fTSApR5Ts1g=; b=wUYLY+cTTAWxEttb9mBQElLeSmZHTSA2advTG/PJTexe9R3ujl30wauCGs6ZMsiO3B f5CHFiG0afVsYFFC2D7R+V5dJ4WWTqukFH6hxZVkVxDpjkLHpPbhzY3jwNrcvLj71yr1 RHak/gBMz+Icril5aWQ+JH4xFbmy9JjImvbHY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; b=v1LKYWt/9KL7AWeQYVbXldpCo4NqNOSsy/amuxAQ2vxUH1diMmgKdVJiTOtEG+X9Gx bnGctC1m7h65JAl2gB+JfaYICRC3WrNNIIkGSnvmcINfrEuIq7wptMd9to4McgzuClcJ VI+lcVaY7gHY1BbUbZZ/t6ETK8TGDLP9NERiQ= Received: by 10.227.127.134 with SMTP id g6mr9865045wbs.54.1291226934101; Wed, 01 Dec 2010 10:08:54 -0800 (PST) Received: from [192.168.1.100] (cpc3-cmbg14-0-0-cust445.5-4.cable.virginmedia.com [213.106.93.190]) by mx.google.com with ESMTPS id 11sm171256wbj.13.2010.12.01.10.08.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Dec 2010 10:08:52 -0800 (PST) References: <4CF65D62.21930.96EDB2@mike.dennison.ntlworld.com> <4CF672A2.6040506@iup.uni-heidelberg.de> <005001cb917a$15cb1720$0401a8c0@xphd97xgq27nyf> From: Roger Lapthorn X-Mailer: iPod Mail (8C148) In-Reply-To: <005001cb917a$15cb1720$0401a8c0@xphd97xgq27nyf> Message-Id: <63F0E942-FAC1-4DAF-911A-2BEEDD7995F1@gmail.com> Date: Wed, 1 Dec 2010 18:09:11 +0000 To: "rsgb_lf_group@blacksheep.org" Mime-Version: 1.0 (iPod Mail 8C148) DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: QRSS120 and grabbers Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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=TO_ADDRESS_EQ_REAL 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-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d237.1 ; domain : gmail.com DKIM : pass x-aol-sid: 3039400c89a24cf68f803b2f X-AOL-IP: 195.171.43.25 So why not QSY somewhere else in the spectrum Mal and teach yourself somet= hing new? Some of us here are still learning on LF for the first time, and= can do without your "help". Roger G3XBM Sent from my iPod Touch 4g On 1 Dec 2010, at 17:06, "mal hamilton" wrote: > I have some nice pics of my signal a few years back being received TA at > QRS 3 on 137 Kcs also 500 Kcs last year. > also NC1K was able to copy G3KEV and MM0ALM on normal CW in the past. > When there was an abundance of acty on 137 a few years ago I could copy= the > USA stations on QRS1 and normal CW. > For those serious about TA qso's a well engineered station and elevated > antenna will do the trick without a struggle. There is no need for QRS > slower than 30 sec dot. > VE1JG was a big player in the past along with VE1ZZ and both able to co= py > my CW > Many TA QSO'S have taken place in the past when there was lots of acty= from > the UK in particular. and I have made dozens of contacts especially arou= nd > this time of year. In the early days the USA had to reply xband usually= for > me on 7 Mcs because they did not have a permit for 137 > At the present time some seem to be RE-INVENTING the wheel, obviously no= t > reading past history about LF. > de Mal/G3KEV >=20 >=20 > ----- Original Message ----- > From: "Stefan Sch=C3=A4fer" > To: > Sent: Wednesday, December 01, 2010 4:06 PM > Subject: Re: LF: QRSS120 and grabbers >=20 >=20 >> Hi Mike, >>=20 >> Yes, some thoughts: >>=20 >> Am 01.12.2010 15:36, schrieb Mike Dennison >>> I believe the danger is to regard this as the 'optimum' speed for DX >>> working, simply because the S/N ratio is good. >> Is that really a danger? >>> In practice, there is >>> another factor in play. There is often rapid and deep fading on a DX >>> path, often resulting in only parts of letters being received at this >>> speed, even though the peak signal is quite strong (see many of the >>> pictures of transatlantic reception regularly posted on this group). >>>=20 >>> The situation becomes worse if the final aim of experimenting with a >>> path is to have a two-way DX QSO. Even exchanging minimal >>> information, a QSO will take several hours, during which time the >>> conditions must hold up. >> When was the last real QSO done in QRSS >=3D 30? I rember the contact >> between VE7TIL and JA7NI but most of the active people are just >> transmitting a character (representing their callsign) in beacon mode.= I >> have never seen a "CQ ... K" in 60 or 120. >> So if one just wants to transmit a beacon signal it doesn't matter if >> there is some QSB. As an example, XGJ is monitored very often most of >> the nights. If the G would be lost (X_J)and in the next turn the J woul= d >> be lost (XG_), anyway everbody would know it't (XGJ). Furthermore the= DX >> interested OMs gets the confirmation on the other grabbers. >> If a QSO is wanted, i fully agree with your opinion. But a QSO means >> that both stations are sitting in front of the PC, so they can change >> the RX to the wanted QRSS/DFCW mode. >> Anyway, i am providing both QRSS-60 and QRSS-120 for TA and EU, so >> people may chosse what they like :-) >>> Take a look at VE7TIL's excellent DCF39 >>> graph to see how short a good DX opening usually is - perhaps an hour >>> if you are lucky. >> ...which wouldn't be enough for a (real) QSO in QRSS-60 but enough for >> "FC" or "NM" or "NI" in QRSS-120. >>>=20 >>>=20 >>> The very few who have had transatlantic QSOs have used QRSS30 or at >>> most QRSS60. I am not aware of a successful two-way involving a >>> longer dot length. >>>=20 >>> I would suggest that DX beacons and grabbers use a =3Dmaximum=3D of 60= s >>> dot length (though a second grabber screen could be provided for 120 >>> etc if desired). In my opinion this would be more likely to result in >>> useful propagation data. >>>=20 >> Done. >>> Any thoughts? >>>=20 >>> Mike, G3XDV >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>=20 >>=20 >> 73, Stefan >>=20 >=20 >=20