Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp8075igc; Sun, 2 Mar 2014 12:55:55 -0800 (PST) X-Received: by 10.194.77.7 with SMTP id o7mr11904918wjw.35.1393793754253; Sun, 02 Mar 2014 12:55:54 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id ia6si3188374wjb.25.2014.03.02.12.55.53 for ; Sun, 02 Mar 2014 12:55:54 -0800 (PST) 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; Authentication-Results: mx.google.com; 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) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=pass header.i=@mx.aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WKBXs-0001FH-8V for rs_out_1@blacksheep.org; Sun, 02 Mar 2014 18:55:28 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WKBXr-0001F8-Ms for rsgb_lf_group@blacksheep.org; Sun, 02 Mar 2014 18:55:27 +0000 Received: from omr-d05.mx.aol.com ([205.188.109.202]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1WKBXo-00083C-Qs for rsgb_lf_group@blacksheep.org; Sun, 02 Mar 2014 18:55:26 +0000 Received: from mtaout-mab01.mx.aol.com (mtaout-mab01.mx.aol.com [172.26.249.81]) by omr-d05.mx.aol.com (Outbound Mail Relay) with ESMTP id 8CDCF70000090 for ; Sun, 2 Mar 2014 13:55:22 -0500 (EST) Received: from White (95-91-237-52-dynip.superkabel.de [95.91.237.52]) by mtaout-mab01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id AC7643800009B for ; Sun, 2 Mar 2014 13:55:19 -0500 (EST) Message-ID: <91EDCA349BE942929730C480D5D64F7F@White> From: "Markus Vester" To: References: , ,<5313677A.2020400@abelian.org> Date: Sun, 2 Mar 2014 19:55:18 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1393786522; bh=5R41EvF4h0oqyyOMbxCET2dQZW8sLQz2pTRedGIiujQ=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=VtFF/h2rBQVjL5aY/Z+wf5fGIvsPbzjbqlil0BJlXn2TfekNzHZoxLHT9un/0aaKW 3vlI7XgHU6sHGMq5eIZItxELW25PR564+RBv7gm5XF9Gkzq5T5tRWiVl68Kk8FEx1M oFBx53Seosti1uKPDhBzRLXw/0DrxeDpRDEv8XWY= x-aol-sid: 3039ac1af95153137e9761ff X-AOL-IP: 95.91.237.52 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Just added a 3.8 mHz (aka "600") window for 29.499 khz to the bottom of my grabber: http://www.df6nm.de/vlf/vlfgrabber.htm. Don't have much hope of seeing anything here. But if a miracle should happen, very slow qrss (like five minute dots) might become readable. [...] Content analysis details: (1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [205.188.109.202 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: 6ae5fe68d6708d1e4a9cbdf0f0af43e5 Subject: Re: LF: Would slower QRSS help? Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01CF3651.561177F0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.6 required=5.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,MISSING_OUTLOOK_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 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0010_01CF3651.561177F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just added a 3.8 mHz (aka "600") window for 29.499 khz to the bottom of = my grabber: http://www.df6nm.de/vlf/vlfgrabber.htm.=20 Don't have much hope of seeing anything here. But if a miracle should = happen, very slow qrss (like five minute dots) might become readable. Bob, could you give some details about your antenna capacitance, = voltage, current etc? Dex, are you intending to add some turns to your coil to come close to = Bob's QRG? Best 73, Markus (DF6NM) From: Bob Raide=20 Sent: Sunday, March 02, 2014 6:35 PM To: rsgb_lf_group@blacksheep.org=20 Subject: RE: LF: Would slower QRSS help? Paul; It appears to me that your 60 second bins has it! I see A and B very = plainly. Your RX capability is phenomenal!!! Warren Zeigler told me of your history of VLF receptions. =20 I will be running in QRSS 180 tonight. If it isn't enough I can go = slower yet and then carrier for an hour with slight freq switch if = nothing else works. Please during transmission send me e mail for any changes you might like = me to implement. Not sure if you can or want to stay up that late but I = will do whatever it takes to see your optimum results. This is only second night on and transmitter still not optimum. Have = tuned input to make and install. Would like a few more DB before corona = takes over-Bob =20 > Date: Sun, 2 Mar 2014 17:16:42 +0000 > From: vlf0403@abelian.org > To: rsgb_lf_group@blacksheep.org > Subject: Re: LF: Would slower QRSS help? >=20 > > ... QRSS 60 last night. >=20 > I guessed wrong and Markus suggests a faster > spectrogram. This one is in 60 second bins >=20 > http://abelian.org/vlf/tmp/29499_140302h.gif >=20 > And in 30 second bins >=20 > http://abelian.org/vlf/tmp/29499_140302i.gif >=20 > I don't know if it's any more readable but many > dots are clear in the 30 second one. >=20 > > Would slower be of any help for tonight's transmission? >=20 > Much. For detection at the max possible range send pure > carrier. To confirm ID, change frequency at some point, > 10 mHz or so, on the hour. >=20 > For the slow Morse each doubling of dot length would double > the brightness of your trace on the spectrogram. 120 should > put you in the red and 240 would be well into the yellow. >=20 > Background noise subsided here from about 04:30 so the S/N > improved for the final 2.5 hours of transmission. That > appears to be the European window to aim for. >=20 > -- > Paul Nicholson > -- >=20 ------=_NextPart_000_0010_01CF3651.561177F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just added a 3.8 mHz (aka "600") = window for=20 29.499 khz to the bottom of my grabber:
 http://www.df6nm.de/vlf/v= lfgrabber.htm.=20
Don't have much hope of seeing anything = here. But=20 if a miracle should happen, very slow qrss (like = five=20 minute dots) might become readable.
 
Bob, could you give some details = about your=20 antenna capacitance, voltage, current etc?
 
Dex, are you intending to add some = turns to your=20 coil to come close to Bob's QRG?
 
Best 73,
Markus (DF6NM)
 

From: Bob Raide
Sent: Sunday, March 02, 2014 6:35 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: RE: LF: Would slower QRSS help?

Paul;
It appears to me that your 60 second bins has = it!  I=20 see A and B very plainly.  Your RX capability=20 is phenomenal!!!
Warren Zeigler told me of your history of VLF=20 receptions. 
I will be running in QRSS 180 tonight.  = If it=20 isn't enough I can go slower yet and then carrier for an hour with = slight freq=20 switch if nothing else works.
Please during transmission send me e = mail for=20 any changes you might like me to implement.  Not sure if you can or = want to=20 stay up that late but I will do whatever it takes to see your optimum=20 results.
This is only second night on and transmitter still not=20 optimum.  Have tuned input to make and install.  Would like a = few more=20 DB before corona takes over-Bob
 
> Date: Sun, 2 Mar 2014 17:16:42 +0000
> From:=20 vlf0403@abelian.org
> To: rsgb_lf_group@blacksheep.org
> = Subject:=20 Re: LF: Would slower QRSS help?
>
> > ... QRSS 60 last=20 night.
>
> I guessed wrong and Markus suggests a = faster
>=20 spectrogram. This one is in 60 second bins
>
>=20 http://abelian.org/vlf/tmp/29499_140302h.gif
>
> And in 30 = second=20 bins
>
> = http://abelian.org/vlf/tmp/29499_140302i.gif
>=20
> I don't know if it's any more readable but many
> dots = are clear=20 in the 30 second one.
>
> > Would slower be of any help = for=20 tonight's transmission?
>
> Much. For detection at the max = possible=20 range send pure
> carrier. To confirm ID, change frequency at some = point,
> 10 mHz or so, on the hour.
>
> For the slow = Morse=20 each doubling of dot length would double
> the brightness of your = trace on=20 the spectrogram. 120 should
> put you in the red and 240 would be = well=20 into the yellow.
>
> Background noise subsided here from = about=20 04:30 so the S/N
> improved for the final 2.5 hours of = transmission.=20 That
> appears to be the European window to aim for.
> =
>=20 --
> Paul Nicholson
> --
> =
------=_NextPart_000_0010_01CF3651.561177F0--