Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25;
Message-ID: <5314C73C.8040507@abelian.org>
Date: Mon, 03 Mar 2014 18:17:32 +0000
From: Paul Nicholson <vlf0403@abelian.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <BLU180-W814352324BEEA9B61B3933AC8F0@phx.gbl>,<53147DD2.8020201@iup.uni-heidelberg.de> <BLU180-W932D8816F74827A83457A0AC8F0@phx.gbl>
In-Reply-To: <BLU180-W932D8816F74827A83457A0AC8F0@phx.gbl>
Subject: Re: LF: 29.499 QRSS 180 for remainer of night...
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

I made a spectrogram of the Morse transmission using a
transform width equal to the 180 second dot length, advancing
the transform by 60 seconds each time

  http://abelian.org/vlf/tmp/29499_140303_180_60_rect.png

As expected, the signal is now 'in the yellow'.

Markus advised me that using a shorter transform aids readability
even though it discards some S/N.   Here it is with 90 second
transform advancing by 45 seconds,

  http://abelian.org/vlf/tmp/29499_140303_90_45_rect.png

and sure enough it is now quite easy to read the Morse letters.
There is one 'B' where the dash is broken into two dots by
a noise spike.

I tried Hann and some other windows but rectangular seemed to do
best.

The 10mHz shift was very effective and ought to ID the signal
even if the trace was very faint on a spectrogram.   Fingers
crossed for some reports from further into Europe.

The signal was showing no sign of fading out by 08:00 UT so I
guess it would still come through for another hour or maybe
two.

--
Paul Nicholson
--