Return-Path: Received: from rly-dc04.mx.aol.com (rly-dc04.mail.aol.com [172.19.136.33]) by air-dc05.mail.aol.com (v121_r4.4) with ESMTP id MAILINDC054-b184956295d147; Sat, 27 Dec 2008 08:11:05 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc04.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDC044-b184956295d147; Sat, 27 Dec 2008 08:10:55 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LGYvv-0002mf-9Z for rs_out_1@blacksheep.org; Sat, 27 Dec 2008 13:10:23 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LGYvu-0002mW-Ih for rsgb_lf_group@blacksheep.org; Sat, 27 Dec 2008 13:10:22 +0000 Received: from qmta01.westchester.pa.mail.comcast.net ([76.96.62.16]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LGYvt-00055P-72 for rsgb_lf_group@blacksheep.org; Sat, 27 Dec 2008 13:10:22 +0000 Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA01.westchester.pa.mail.comcast.net with comcast id wD4s1a0070ldTLk51DADWg; Sat, 27 Dec 2008 13:10:13 +0000 Received: from JAYDELL ([65.96.107.144]) by OMTA04.westchester.pa.mail.comcast.net with comcast id wDAE1a00436xPMd3QDAE5n; Sat, 27 Dec 2008 13:10:14 +0000 Message-ID: <003401c96824$74ea6700$8d01a8c0@JAYDELL> From: To: References: <01aa01c96807$c07bd310$0301a8c0@mal769a60aa920> Date: Sat, 27 Dec 2008 08:10:14 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Karma: 0: X-Spam-Score: 0.6 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,NO_REAL_NAME=0.55 Subject: LF: Re: 500 QSO Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01C967FA.8BE22B70" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_30_40,HTML_MESSAGE, NO_REAL_NAME 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 ------=_NextPart_000_0031_01C967FA.8BE22B70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mal & LF/MF enthusiasts Copy was difficult on this end but we managed - thanks for your patience. Ho= pe you guys get the higher ERP limit - it would certainly make the band more= useful and help in the study of propagation. From my observations, QSB on 5= 00 kHz is more pronounced than any other band I've worked...and not just ove= r the T/A path. Jay =20 ----- Original Message -----=20 From: mal hamilton=20 To: rsgb=20 Sent: Saturday, December 27, 2008 4:44 AM Subject: LF: 500 QSO LF/MF info Tnx Jay WE2XGR/2 for the QSO last nite on 500 khz on CW/QRS3. When u started calling about 2157 I was able to see ur sig OOO copy and st= rong. There was some slow qsb during the evening but at QRS 3 it did not see= m to be a problem this speed was fast enough to get the info before a fade t= ook place, however QRS 1 would probably have been better and in fact even no= rm CW. In the past you signal has been audible.=20 Now that we have established a contact procedure on 500 I will try this mo= re often. I think there is a possibility that had u called earlier I would have dete= cted your signal, however 2200utc - 2400 is a good time. I have been working= W stns on 160m at times as early as 2000 utc, still daylight over ur way. I can have another bash tonight and if any others want to participate plea= se do so. I will TX on 502.57 khz and use QRS3 and then speed up if necessary. A goo= d USA freq would be around 508.5 khz which is perfectly clear here. If all W stns intererested in a TR QSO work around this freq with a littl= e separation I would be able to see who is about, and QSO accordingly. QRU now and agn tnx and looking forward to another QSO soon.I will have to= ck the QRB. de mal/g3kev/IO94SH ------=_NextPart_000_0031_01C967FA.8BE22B70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mal & LF/MF enthusiasts
 
Copy was difficult on this end but we manag= ed -=20 thanks for your patience. Hope you guys get the higher ERP limit -= =20 it would certainly make the band more useful and help in the study= of=20 propagation. From my observations, QSB on 500 kHz is more=20 pronounced than any other band I've worked...and not just ove= r=20 the T/A path.
 
Jay   
 
 
----- Original Message -----
mal= =20 hamilton
To: rsgb
Sent: Saturday, December 27, 2008 4= :44=20 AM
Subject: LF: 500 QSO

LF/MF info
Tnx Jay WE2XGR/2 for the QSO last nite on= 500 khz=20 on CW/QRS3.
When u started calling about 2157 I was a= ble to=20 see ur sig OOO copy and strong. There was some slow qsb during the evening= but=20 at QRS 3 it did not seem to be a problem this speed was fast enough to get= the=20 info before a fade took place, however QRS 1 would probably have been bett= er=20 and in fact even norm CW. In the past you signal has been audible.=20
Now that we have established a contact pr= ocedure=20 on 500 I will try this more often.
I think there is a possibility that had u= called=20 earlier I would have detected your signal, however 2200utc - 2400 is a goo= d=20 time. I have been working W stns on 160m at times as early as 2000 utc, st= ill=20 daylight over ur way.
I can have another bash tonight and if an= y others=20 want to participate please do so.
I will TX on 502.57 khz and use QRS3 and=20= then=20 speed up if necessary. A good USA freq would be around 508.5 khz which is=20 perfectly clear here.
If all W stns intererested in a TR Q= SO=20  work around this freq with a little separation I would be able to se= e=20 who is about, and QSO accordingly.
QRU now and agn tnx and looking forward t= o=20 another QSO soon.I will have to ck the QRB.
 
de mal/g3kev/IO94SH
 
------=_NextPart_000_0031_01C967FA.8BE22B70--