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 w06M8b7m015058 for ; Sat, 6 Jan 2018 23:08:40 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eXwZE-0004yf-TM for rs_out_1@blacksheep.org; Sat, 06 Jan 2018 22:03:52 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eXwYp-0004yW-CJ for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 22:03:27 +0000 Received: from mout1.freenet.de ([2001:748:100:40::2:3]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eXwYl-000377-83 for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 22:03:25 +0000 Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (port 25) (Exim 4.89 #1) id 1eXwYg-0005fO-4y for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 23:03:18 +0100 Received: from [::1] (port=59660 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.89 #1) id 1eXwYg-0005N5-15 for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 23:03:18 +0100 Received: from mx14.freenet.de ([195.4.92.24]:57760) by mjail1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.89 #1) id 1eXwWi-00040E-Fg for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 23:01:16 +0100 Received: from dslb-088-071-238-175.088.071.pools.vodafone-ip.de ([88.71.238.175]:51875 helo=[192.168.178.26]) by mx14.freenet.de with esmtpsa (ID dl4yhf@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.89 #1) id 1eXwWi-0005dl-58 for rsgb_lf_group@blacksheep.org; Sat, 06 Jan 2018 23:01:16 +0100 To: rsgb_lf_group@blacksheep.org 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> <1962494263.101882557.1515272833756.JavaMail.zimbra@shaw.ca> From: =?UTF-8?Q?Wolfgang_B=c3=bcscher?= Message-ID: Date: Sat, 6 Jan 2018 22:59:40 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1962494263.101882557.1515272833756.JavaMail.zimbra@shaw.ca> X-Originated-At: 88.71.238.175!51875 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: Hi Jack, Yes, it takes several hours until the first spectrum (or line of pixels in the spectrogram) appears. To load a complete (FFT-) window for 47 uHz bin width, it takes 1 / 47 uHz = 21276.x seconds = 5.9 hours . That's dictated by the maths. Not related with CPU speed. "Not a bug but a feature" . [...] 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dl4yhf[at]freenet.de) 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 070d9ab39265047b7fb462cd62854f10 Subject: LF: Re: SL settings for QRSS Content-Type: multipart/alternative; boundary="------------0DE48C067053C61DF4603C25" 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 This is a multi-part message in MIME format. --------------0DE48C067053C61DF4603C25 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Jack, Yes, it takes several hours until the first spectrum (or line of pixels in the spectrogram) appears. To load a complete (FFT-) window for 47 uHz bin width, it takes 1 / 47 uHz = 21276.x seconds = 5.9 hours . That's dictated by the maths. Not related with CPU speed. "Not a bug but a feature" . That's one of the reasons why Paul's Ebnaut has completely replaced these ancient "visual" modes ;-) Cheers, Wolf . Am 06.01.2018 um 22:07 schrieb JACK ASKEW: > > 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 > > > > ------------------------------------------------------------------------ > *From: *"Wolfgang Büscher" > *To: *"rsgb lf group" > *Sent: *Saturday, January 6, 2018 10:42:14 AM > *Subject: *SL settings for QRSS (was: Re: LF: RE: Todmorden receiver > by Jack) > > Hello Jack and all, > > you wrote: > > >It comes back to using something like SL with its QRSS > capabilities. I wish I had a good file that worked at 8720kHz > for QRSS600 as an example. This would be a good start if nothing else. > < > > It's not that difficult to set up. The key 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 effect 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 some > configuration files for QRSSS. > > Back in the "old days" of extremely 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 sampling rate, > a bit out of fashion since good GPSes with sync output became > available, but anyway..) > > To make the FFT window even longer / frequency bins even shorter than > used in the default settings, > use the option 'complex input for the FFT with internal frequency > shift', as shown at > http://www.qsl.net/dl4yhf/speclab/settings.htm#fft_size > > And, last not least, there an explanation of FFT length, decimation, > windowing functions, resulting resolution / effective receiver bandwidth > versus dynamic range, etc: > http://www.qsl.net/dl4yhf/speclab/fftinfo.htm > > All the best, > Wolf DL4YHF --------------0DE48C067053C61DF4603C25 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi Jack,

Yes, it takes several hours until the first spectrum (or line of pixels in the spectrogram) appears.
To load a complete (FFT-) window for 47 uHz bin width, it takes
   1 / 47 uHz = 21276.x seconds = 5.9 hours .
That's dictated by the maths. Not related with CPU speed. "Not a bug but a feature" .

That's one of the reasons why Paul's Ebnaut has completely replaced these ancient "visual" modes ;-)

Cheers,
  Wolf .

Am 06.01.2018 um 22:07 schrieb JACK ASKEW:

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



From: "Wolfgang Büscher" <dl4yhf@freenet.de>
To: "rsgb lf group" <rsgb_lf_group@blacksheep.org>
Sent: Saturday, January 6, 2018 10:42:14 AM
Subject: SL settings for QRSS (was: Re: LF: RE: Todmorden receiver by Jack)

Hello Jack and all,

you wrote:

 >It comes back to using something like SL with its QRSS
capabilities. I wish I had a good file that worked at 8720kHz
for QRSS600 as an example. This would be a good start if nothing else.
<

It's not that difficult to set up. The key 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 effect 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 some
configuration files for QRSSS.

Back in the "old days" of extremely 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 sampling rate,
   a bit out of fashion since good GPSes with sync output became
available, but anyway..)

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

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

All the best,
  Wolf DL4YHF

--------------0DE48C067053C61DF4603C25--