Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w06LCjIr014916 for ; Sat, 6 Jan 2018 22:12:46 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eXvgg-0004p8-If for rs_out_1@blacksheep.org; Sat, 06 Jan 2018 21:07:30 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eXvgZ-0004oz-92 for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 21:07:23 +0000 Received: from smtp-out-no.shaw.ca ([64.59.134.13]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eXvgV-0002vL-GT for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 21:07:22 +0000 Received: from cds110.dcs.int.inet ([10.0.153.158]) by shaw.ca with ESMTP id XvgPeXSXcZ8gBXvgQeK3Kt; Sat, 06 Jan 2018 14:07:16 -0700 X-DKIM-Result: Domain=shaw.ca Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1515272836; bh=Kz83kuB/XQ/fhKFi1ZnTNG/DlgOjWPmlM/pNf1z+3+g=; h=Date:From:To:In-Reply-To:References:Subject; b=B8UwEHst3HdE9+C7QmF3Tt5eF4w9UnE+HYO26lzkUOtLH+Rk19bSHyA6o1NAIEwds nuTulNxdxdVPoH0OtrhVKuGAvr1O8pi819TQTg3Dm9Cti0w3Ytgj2zlnpzNzaMdmC6 5CPHnM4znKegW8VTeaZ//e++lg8G/XhcNAMjkmn9eB+TDlHeTOR1QtKt+4tVcrhs3J ++IpEpQ9iiNzKYAYrRn1gLqCoyuMEyV6bx/Yj+cQxuqhr92b4t7SH+IA9g1dmR/NbL FJXS5oKkVPPQXP9lhDIqA4/v1bOk2UPTt/61mQ6PyMVepF5fPzfGkyLIfA5M3HtAAU lfFSRs2ZFt/KQ== X-Authority-Analysis: v=2.2 cv=M/g9E24s c=1 sm=1 tr=0 a=waJNmSTfdSAeIyX21TZnUA==:117 a=FKkrIqjQGGEA:10 a=d_JjZ9m1VnQA:10 a=x7bEGLp0ZPQA:10 a=F3M5lZpKAAAA:8 a=QejfARXMAAAA:8 a=6kPX_8LikpPz-_hgqJIA:9 a=HE_5MM5XJdqTN49w:21 a=tMLFfqz8khgBkCvG:21 a=QEXdDO2ut3YA:10 a=Dj0Wr0CfYGAA:10 a=5RQzskvRfGAA:10 a=qzcSvxuARP4A:10 a=gsfju52ycb1kcvTkW7UA:9 a=lSwisArVyfFYS_kQ:21 a=_W_S_7VecoQA:10 a=slCku8JSH3TyizEDQ3pD:22 a=BC3gsuZa1vz2YJYxs7Nf:22 Date: Sat, 6 Jan 2018 14:07:13 -0700 (MST) From: JACK ASKEW To: rsgb lf group Message-ID: <1962494263.101882557.1515272833756.JavaMail.zimbra@shaw.ca> In-Reply-To: References: <4d96a9d4-5f22-7650-872b-6344e9aea8e3@abelian.org> <1117988114.95527491.1515092735528.JavaMail.zimbra@shaw.ca> <1944603203.95803107.1515098735558.JavaMail.zimbra@shaw.ca> <1178238001.101520499.1515262806879.JavaMail.zimbra@shaw.ca> MIME-Version: 1.0 X-Originating-IP: [96.54.64.165, 142.165.85.187] X-Mailer: Zimbra 8.6.0_GA_1200 (ZimbraWebClient - FF57 (Win)/8.6.0_GA_1200) Thread-Topic: SL settings for QRSS (was: Re: LF: RE: Todmorden receiver by Jack) Thread-Index: Zm2yGpirRBSPczLR4sSy4xYMPaXaWQ== X-CMAE-Envelope: MS4wfP25aHHKy4li1hU3vp14SRfMo20Qu0DLdZX0pW8phE705wjvzrurxU4dAXdaLd301C7F8sXvC89pxP9RiBxJpTEgnp/XFxKR6f9iAR3oMEwyrzUXr0wE FOeASwTRKiiykIlI5hPYt4KXTLsySO7n71bWpdIkBTmJwVOKU6amY+lMGnxpmLJBwh3UdflqsL03GQ== X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Thanks Wolf, lots to read up on, excellent information on learning how to use SL for these slower speeds. Also thanks for pointing me to Stefan's site regarding the configuration files for QRSSS, I wondered if anyone still had them available. I recall playing with SL's ability to use VLF stations to lock onto but they were too weak here in Canada. I do have GPS on my Tx now but I still see some un-explainable instability over a period of 4-5hrs but far less than 0.05Hz...so maybe not an issue when I was using file 8270Hz_QRSSS_4mHz.usr. Not sure what equates to in QRSSS though. I find that if I try anything like 'VLF_Soundcard_32K_47uHz.USR' it takes several hours to load up in SL but I guess that stands to reason...I hope. Regards Jack Askew [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_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 X-Scan-Signature: 982d53dbb4bb82e9ed4f38562b2a1556 Subject: Re: SL settings for QRSS (was: Re: LF: RE: Todmorden receiver by Jack) Content-Type: multipart/alternative; boundary="----=_Part_101882556_1885573768.1515272833755" 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=HTML_MESSAGE 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 ------=_Part_101882556_1885573768.1515272833755 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks Wolf, lots to read up on, excellent information on learning=20 how to use SL for these slower speeds. Also thanks for=20 pointing me to Stefan's site regarding the configuration=20 files for QRSSS, I wondered if anyone still had them available.=20 I recall playing with SL's ability to use VLF stations to lock onto but=20 they were too weak here in Canada. I do have GPS on my Tx now=20 but I still see some un-explainable instability over a period of 4-5hrs=20 but far less than 0.05Hz...so maybe not an issue when I was using=20 file 8270Hz_QRSSS_4mHz.usr. Not sure what equates to in QRSSS=20 though. I find that if I try anything like 'VLF_Soundcard_32K_47uHz.USR'=20 it takes several hours to load up in SL but I guess that stands to reason..= .I hope.=20 Regards=20 Jack Askew=20 From: "Wolfgang B=C3=BCscher" =20 To: "rsgb lf group" =20 Sent: Saturday, January 6, 2018 10:42:14 AM=20 Subject: SL settings for QRSS (was: Re: LF: RE: Todmorden receiver by Jack)= =20 Hello Jack and all,=20 you wrote:=20 >It comes back to using something like SL with its QRSS=20 capabilities. I wish I had a good file that worked at 8720kHz=20 for QRSS600 as an example. This would be a good start if nothing else.=20 <=20 It's not that difficult to set up. The key point in SL to get into the=20 microhertz-resolution is the decimation (of the sampling rate), along=20 with complex frequency to have a complex FFT spanning just a few Hz=20 around the "frequency of interest". The effect is similar as a=20 super-long FFT (concerning the frequency bin width, and thus the=20 "gain"). I think on Stefan (DK7FC's) site you can find some=20 configuration files for QRSSS.=20 Back in the "old days" of extremely slow Morse, I wrote this short=20 how-to (for Spectrum Lab):=20 http://www.qsl.net/dl4yhf/speclab/qrss_quickstart.htm=20 (it shows how to pick one of the VLF transmitters to stabilize the=20 soundcard's sampling rate,=20 a bit out of fashion since good GPSes with sync output became=20 available, but anyway..)=20 To make the FFT window even longer / frequency bins even shorter than=20 used in the default settings,=20 use the option 'complex input for the FFT with internal frequency=20 shift', as shown at=20 http://www.qsl.net/dl4yhf/speclab/settings.htm#fft_size=20 And, last not least, there an explanation of FFT length, decimation,=20 windowing functions, resulting resolution / effective receiver bandwidth=20 versus dynamic range, etc:=20 http://www.qsl.net/dl4yhf/speclab/fftinfo.htm=20 All the best,=20 Wolf DL4YHF=20 ------=_Part_101882556_1885573768.1515272833755 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Thanks = Wolf, lots to read up on, excellent information on learning
how = to use SL for these slower speeds.  Also thanks for
pointing me to Stefan's site regarding the configuration<= br data-mce-bogus=3D"1">
files for QRSSS, I wondered if anyone st= ill had them available.
I recall playing= with SL's ability to use VLF stations to lock onto but
they wer= e too weak here in Canada. I do have GPS on my Tx now
but I stil= l see some un-explainable instability over a period of 4-5hrs
bu= t far less than 0.05Hz...so maybe not an issue when I was using
= file 8270Hz_QRSSS_4mHz.usr. Not sure what equates to in QRSSS
though. I find that if I try anything like 'VLF_Sound= card_32K_47uHz.USR'
it takes several hou= rs to load up in SL but I guess that stands to reason...I hope.
Regards
Jack Ask= ew

<= br data-mce-bogus=3D"1">


From: "Wolfgang B= =C3=BCscher" <dl4yhf@freenet.de>
To: "rsgb lf group" <rs= gb_lf_group@blacksheep.org>
Sent: Saturday, January 6, 2018 10= :42:14 AM
Subject: SL settings for QRSS (was: Re: LF: RE: Todmord= en receiver by Jack)

Hell= o Jack and all,

you wrote:

 >It comes back to using s= omething like SL with its QRSS
capabilities. I wish I had a good file th= at worked at 8720kHz
for QRSS600 as an example. This would be a good sta= rt if nothing else.
<

It's not that difficult to set up. The k= ey point in SL to get into the
microhertz-resolution is the decimation = (of the sampling rate), along
with complex frequency to have a complex = FFT spanning just a few Hz
around the "frequency of interest". The effe= ct is similar as a
super-long FFT (concerning the frequency bin width, = and thus the
"gain"). I think on Stefan (DK7FC's) site you can find som= e
configuration files for QRSSS.

Back in the "old days" of extre= mely slow Morse, I wrote this short
how-to (for Spectrum Lab):
http:= //www.qsl.net/dl4yhf/speclab/qrss_quickstart.htm
   (it shows = how to pick one of the VLF transmitters to stabilize the
soundcard's sa= mpling rate,
   a bit out of fashion since good GPSes with syn= c output became
available, but anyway..)

To make the FFT window = even longer / frequency bins even shorter than
used in the default sett= ings,
use the option 'complex input for the FFT with internal frequency =
shift', as shown at
http://www.qsl.net/dl4yhf/speclab/settings.htm#f= ft_size

And, last not least, there an explanation of FFT length, dec= imation,
windowing functions, resulting resolution / effective receiver= bandwidth
versus dynamic range, etc:
http://www.qsl.net/dl4yhf/spec= lab/fftinfo.htm

All the best,
  Wolf DL4YHF
------=_Part_101882556_1885573768.1515272833755--