Return-Path: Received: from rly-df03.mx.aol.com (rly-df03.mail.aol.com [172.19.156.16]) by air-df05.mail.aol.com (v121_r5.5) with ESMTP id MAILINDF053-53c4971063f4a; Fri, 16 Jan 2009 17:12:37 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-df03.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDF035-53c4971063f4a; Fri, 16 Jan 2009 17:12:17 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LNwv1-0007JC-V8 for rs_out_1@blacksheep.org; Fri, 16 Jan 2009 22:11:59 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LNwv1-0007J3-Ai for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 22:11:59 +0000 Received: from smtp-out-4.talktalk.net ([62.24.128.234] helo=smtp.talktalk.net) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LNwv0-0008Bc-Jl for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 22:11:59 +0000 X-Path: TTSMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUEADuVcElZ8oRO/2dsb2JhbACEVshEhXI Received: from unknown (HELO mal769a60aa920) ([89.242.132.78]) by smtp.talktalk.net with SMTP; 16 Jan 2009 22:11:52 +0000 Message-ID: <022201c97827$6faee3c0$0301a8c0@mal769a60aa920> From: "mal hamilton" To: References: <1232113286.49708e86184e6@imp.netikka.net> <1232126050.4970c0624a547@imp.netikka.net> <1232134087.4970dfc7cee7f@imp.netikka.net> <5F937BA9D0D942329876D744EEA50684@JimPC> <1232137029.4970eb4596cae@imp.netikka.net> <019401c9781c$03d88a30$0301a8c0@mal769a60aa920> <1232139746.4970f5e2b7112@imp.netikka.net> <01dc01c97820$8bb5e4d0$0301a8c0@mal769a60aa920> <1232142062.4970feeee5eb9@imp.netikka.net> Date: Fri, 16 Jan 2009 22:11:52 -0000 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: unknown: X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Re: QRG & MSG UPDATE: 136kHz test from OH1LSQ Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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 Paul Normally 136.3 khz and around that area has been used by EU stns for QRS acty and USA listeners. Since then a data stn has started up and makes it difficult for other EU stns to copy through the bursts of QRM. Normally the USA stns use 137.7 khz area. This procedure was used when the band was vy busy some years ago to avoid QRM to normal CW acty. Because band occupancy is vy low at present I do not suppose anyone is going to complain about using up to 136.8 khz. If the band suddenly became vy active then the QRS stns could move lower. My opinion and I must get my 136 TX fired up one of these days. Your signal is still strong here and no noticeable QSB all evening, very constant signal. This LF band is more reliable and consistant than 500 khz which seems to suffer badly from fade most of the time. More power is needed on 500 khz to help over come the QSB problem. 73 and gl de mal/g3kev ----- Original Message ----- From: "Paul-Henrik" To: Sent: Friday, January 16, 2009 9:41 PM Subject: Re: LF: Re: QRG & MSG UPDATE: 136kHz test from OH1LSQ Hello Mal, LF I will consider a new frequency for tomorrow, right now I know some people have set up their systems logging overnight in the hope to find something there in the morning and I can only want to make short excursions elsewhere. Keep the QRG suggestions coming. How about 136.80 or 137.00kHz? I'm not familiar with the LORAN QRM etc. you are experiencing there. 136.50kHz got thumbs down already yesterday so it needs to be higher than that. 73's Paul-Henrik Quoting mal hamilton : > Paul > Your freq is too low because of the qrm around 136 khz. A better freq > would > be 136.5 or higher. > mal/g3kev > > ----- Original Message ----- > From: "Paul-Henrik" > To: > Sent: Friday, January 16, 2009 9:02 PM > Subject: Re: LF: Re: QRG & MSG UPDATE: 136kHz test from OH1LSQ > > > Thanks for the report Mal! > > Happy to send some lower frequency signals back in return for all those > received > on 600 metres. Looks like the OH-G path is still in the same good shape it > used > to be when Reino was still active on the band. > > 73's > > Paul-Henrik > > Quoting mal hamilton : > > > Paul > > Good copy ere now OOO at 2048 utc have good photo > > mal/g3kev > > > > ----- Original Message ----- > > From: "Paul-Henrik" > > To: > > Sent: Friday, January 16, 2009 8:17 PM > > Subject: Re: LF: Re: QRG & MSG UPDATE: 136kHz test from OH1LSQ > > > > > > Thanks for the screenshot Jim! > > > > Amazing, I thought it would take more to make it down there. It is good > > to > > be > > back on 136 after a 12 year break. My best DX back then was the > > Karlsborg > > expedition in Sweden (7S6SAJ) > > > > 73's > > > > Paul-Henrik > > > > Quoting James Moritz : > > > > > Dear Paul-Henrik, > > > > > > Now copying your QRSS3 - see attachment. Signal is recovering from > > > QSB. > > > > > > Cheers, Jim Moritz > > > 73 de M0BMU > > > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > > > > > > No virus found in this incoming message. > > Checked by AVG - http://www.avg.com > > Version: 8.0.176 / Virus Database: 270.10.8/1897 - Release Date: > > 1/16/2009 > > 6:52 AM > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.176 / Virus Database: 270.10.8/1897 - Release Date: 1/16/2009 > 6:52 AM > > > -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.8/1897 - Release Date: 1/16/2009 6:52 AM