Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
From: MarkusVester@aol.com
Message-ID: <238.1feba4e4.326949a0@aol.com>
Date: Thu, 19 Oct 2006 17:35:28 EDT
To: rsgb_lf_group@blacksheep.org
MIME-Version: 1.0
Subject: Re: LF: Re. TA Last Night
Content-Type: multipart/alternative; boundary="part1_238.1feba4e4.326949a0_boundary"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O


--part1_238.1feba4e4.326949a0_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Dear John and LF,

yes my grabber seems to be plagued a lot. Most of the QRN is currently 
emanating from the Mediterranan sea area. I believe the unilateral directivity of 
the K9AY E-H-loops does help a lot for Hartmurt and Jean-Pierre. However up to 
now my own attempts on H-field reception have always resulted in decreased SNR 
due to all sorts of local QRM.

The QRN was probably emphasized a little by the increased dynamic headroom 
which was required here to cope with the Budapest telegrams. Apparently these 
have also affected the software noise blanker performance, which I have tried to 
improve now by inserting a bandpass filter before the trigger.

Judging by the fat CFH trace last night, LF propagation looks quite favorable 
in the aftermath of the recent period of geomagnetic activity. On the 100 kHz 
monitor, all stations from the the Far East Loran chains (including Minami 
Torishima island) were well visible this evening.

73 and best wishes
de Markus, DF6NM

w1tag@w1tag.com wrote:
 
> Laurie,
> 
> I was looking at the various Grabbers in the 0100-0200 period, and 
> Jean-Pierre, F1AFJ, had clearly visible signals while Dave Pick's screen 
> only showed one or two (Loran) lines. The DF6NM screens have been buried 
> in noise on most nights lately, so that's all I had for comparison from 
> across the pond. Perhaps there was a storm that was affecting your copy 
> (and Dave's) more than the others on the continent.
> 
> John A.
> 


--part1_238.1feba4e4.326949a0_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><HTML><FONT  SIZE=3D2 PTSIZE=3D10 FAMILY=
=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"2">Dear John and LF,<BR>
<BR>
yes my grabber seems to be plagued a lot. Most of the QRN is currently emana=
ting from the Mediterranan sea area. I believe the unilateral directivity of=
 the K9AY E-H-loops does help a lot for Hartmurt and Jean-Pierre. However up=
 to now my own attempts on H-field reception have always resulted in decreas=
ed SNR due to all sorts of local QRM.<BR>
<BR>
The QRN was probably emphasized a little by the increased dynamic headroom w=
hich was required here to cope with the Budapest telegrams. Apparently these=
 have also affected the software noise blanker performance, which I have tri=
ed to improve now by inserting a bandpass filter before the trigger.<BR>
<BR>
Judging by the fat CFH trace last night, LF propagation looks quite favorabl=
e in the aftermath of the recent period of geomagnetic activity. On the 100=20=
kHz monitor, all stations from the the Far East Loran chains (including Mina=
mi Torishima island) were well visible this evening.<BR>
<BR>
73 and best wishes<BR>
de Markus, DF6NM<BR>
<BR>
w1tag@w1tag.com wrote:<BR>
 <BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Laurie,<BR>
<BR>
I was looking at the various Grabbers in the 0100-0200 period, and <BR>
Jean-Pierre, F1AFJ, had clearly visible signals while Dave Pick's screen <BR=
>
only showed one or two (Loran) lines. The DF6NM screens have been buried <BR=
>
in noise on most nights lately, so that's all I had for comparison from <BR>
across the pond. Perhaps there was a storm that was affecting your copy <BR>
(and Dave's) more than the others on the continent.<BR>
<BR>
John A.<BR>
</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>
--part1_238.1feba4e4.326949a0_boundary--