Message-ID: <427285824B0B41ABA25C61B320EFB093@Black>
From: "Markus Vester" <markusvester@aol.com>
To: <rsgb_lf_group@blacksheep.org>
References: <492865EC.2050004@w1tag.com> <49290F1F.2080403@online.fr> <49295E14.3030205@w1tag.com>
In-Reply-To: <49295E14.3030205@w1tag.com>
Date: Sun, 23 Nov 2008 17:16:47 +0100
MIME-Version: 1.0
Subject: Re: LF: WD2XES WOLF
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


John,

Hartmut's readout showed an offset of -0.254 Hz. Assuming his calibration is perfectly correct, I might have just missed you, as I 
had set my decoder's frequency tolerance parameter to only 0.2 Hz. On the other hand, my location and setup is generally several 
dB's less sensitive than Hartmut's or Jean-Pierre's.

The closest Loran line from GRI 6731 is on 137438.71, but with 7.43 Hz line spacing, a Wolf 10 signal won't fit inbetween anyway. 
Loran is not much of a problem here in South Germany as we are fairly far from the coast and the lines are weak.

Best wishes
Markus

----- Original Message ----- 
From: "John Andrews" <w1tag@w1tag.com>
To: <rsgb_lf_group@blacksheep.org>
Sent: Sunday, November 23, 2008 2:43 PM
Subject: Re: LF: WD2XES WOLF


> Jean-Pierre, Markus, Hartmut,
>
> Thanks for looking. I was definitely on 137.441 (as proven by Hartmut's copy), but the frequency was chosen for Laurence in the 
> frozen wilds of Alaska, who did get some copy. There was likely a Loran-C problem in EU. I'll try to come up with a better 
> frequency for tonight.
>
> Hartmut -- that was amazing. Thanks.
>
> John Andrews, W1TAG/WD2XES
>
>