Return-Path: X-Spam-DCC: paranoid 1356; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_10_20,HTML_MESSAGE,RATWARE_GECKO_BUILD autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id t5UNdiFi012308 for ; Wed, 1 Jul 2015 01:39:44 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ZA54x-00019l-MX for rs_out_1@blacksheep.org; Wed, 01 Jul 2015 00:36:39 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ZA54x-00019c-61 for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 00:36:39 +0100 Received: from mx02.posteo.de ([89.146.194.165]) by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from ) id 1ZA54v-0001SA-7y for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 00:36:38 +0100 Received: from dovecot04.posteo.de (unknown [185.67.36.27]) by mx02.posteo.de (Postfix) with ESMTPS id 897AD25AF52D for ; Wed, 1 Jul 2015 01:36:36 +0200 (CEST) Received: from mail.posteo.de (localhost [127.0.0.1]) by dovecot04.posteo.de (Postfix) with ESMTPSA id 3mLhsc2LpCzFpW0 for ; Wed, 1 Jul 2015 01:36:36 +0200 (CEST) Message-ID: <55932804.5030800@posteo.de> Date: Wed, 01 Jul 2015 01:36:36 +0200 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <5591B4B6.6080302@posteo.de> <5591C9E4.4070407@psk31.plus.com> <5591CECF.6000709@posteo.de> <55929BC9.6020804@psk31.plus.com> <5592A3A3.5030805@posteo.de> In-Reply-To: <5592A3A3.5030805@posteo.de> X-Scan-Signature: c95b9a52470b89d54f2ef38e923e05cb Subject: LF: SpecLab's frequence selective limiter: Better performance for your WSPR decoder! Content-Type: multipart/alternative; boundary="------------040602050108060307010705" 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 X-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 3584 This is a multi-part message in MIME format. --------------040602050108060307010705 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hi all, My MF RX-experiments are continuing and i discovered SpecLab's frequency selective limiter: Today it is a quite noisy night. As reported previously i'm running two SpecLab instances from the same signal source (VAC1) feeding two WSPR instances, so i can directly see the effect of the NB or other techniques. This image shows the experiment: https://dl.dropboxusercontent.com/u/19882028/MF/Frequence%20selective%20limiter.png The upper WSPR+SpecLab instance is using the NB, the lower one just makes the necessary frequency conversion and SSB filter setting (474.2 kHz "dial"). Using SpecLab's noise blanker (NB) makes an improvement of 3...7 dB tonite, as reported by WSPR-2, so it is worth to run it! Actually there were many decodes by that instance which is using the NB that didn't decode on the other one, for example G3WCB at 22:32 UTC (see text fields). Without the NB there was no trace at all! However, when running the NB, strong signals will cause the NB the rise the noise in the spectrum. DK2DB is a strong signal here, showing 40 dB above the noise (in 1 Hz), (yes i'm such a strong signal too, i know!!!). You can see the effect on the upper spectrogram at 21:50 or 22:00 UTC. A small signal like G3WCB would be lost in that background noise which is caused by the NB. However without the NB it wouldn't decode as well! So what is the solution? Maybe something like an auto notch filter but if this is very sharp, it also causes a higher noise arround. Actually it must be something which just lowers the strong signals a bit, maybe 25 dB but leaves the rest as it is. In a phone call with Markus we discussed about this and discovered the the _*frequence selective limiter*_ and it's performance. It can be found in the options register card of the filter control window and must be enabled there. I've the configured a band pass filter including this limiter. _After_ that filter and limiter, the NB is running in the blackbox between L4 and L5. Now, when enabling the filter and defining a limit just about 10 dB above the average noise floor, the signal of DK2DB is reduced to a level which does not cause the NB to rise the noise floor! You can see it at 22:08 UTC. In the list you can see that the displayed SNR dropped from +3 to -15 dB at 22:16 UTC where is reduced the limiter threshold a bit more. *So decodes of the strong local stations do still happen while the NB is not acting on the strong signal, and QRN is significantly blanked, allowing to decode weak signals!* For example, see G3XIZ at 22:44 UTC, showing -17 dB instead of -25 dB, i.e. an improvement of 8 dB! DK2DB has been active to that time. 73, Stefan --------------040602050108060307010705 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hi all,

My MF RX-experiments are continuing and i discovered SpecLab's frequency selective limiter:

Today it is a quite noisy night.

As reported previously i'm running two SpecLab instances from the same signal source (VAC1) feeding two WSPR instances, so i can directly see the effect of the NB or other techniques.
This image shows the experiment: https://dl.dropboxusercontent.com/u/19882028/MF/Frequence%20selective%20limiter.png
The upper WSPR+SpecLab instance is using the NB, the lower one just makes the necessary frequency conversion and SSB filter setting (474.2 kHz "dial").

Using SpecLab's noise blanker (NB) makes an improvement of 3...7 dB tonite, as reported by WSPR-2, so it is worth to run it! Actually there were many decodes by that instance which is using the NB that didn't decode on the other one, for example G3WCB at 22:32 UTC (see text fields). Without the NB there was no trace at all!

However, when running the NB, strong signals will cause the NB the rise the noise in the spectrum. DK2DB is a strong signal here, showing 40 dB above the noise (in 1 Hz), (yes i'm such a strong signal too, i know!!!). You can see the effect on the upper spectrogram at 21:50 or 22:00 UTC. A small signal like G3WCB would be lost in that background noise which is caused by the NB. However without the NB it wouldn't decode as well!

So what is the solution? Maybe something like an auto notch filter but if this is very sharp, it also causes a higher noise arround. Actually it must be something which just lowers the strong signals a bit, maybe 25 dB but leaves the rest as it is. In a phone call with Markus we discussed about this and discovered the the frequence selective limiter and it's performance. It can be found in the options register card of the filter control window and must be enabled there. I've the configured a band pass filter including this limiter. After that filter and limiter, the NB is running in the blackbox between L4 and L5.

Now, when enabling the filter and defining a limit just about 10 dB above the average noise floor, the signal of DK2DB is reduced to a level which does not cause the NB to rise the noise floor! You can see it at 22:08 UTC. In the list you can see that the displayed SNR dropped from +3 to -15 dB at 22:16 UTC where is reduced the limiter threshold a bit more. So decodes of the strong local stations do still happen while the NB is not acting on the strong signal, and QRN is significantly blanked, allowing to decode weak signals! For example, see G3XIZ at 22:44 UTC, showing -17 dB instead of -25 dB, i.e. an improvement of 8 dB! DK2DB has been active to that time.

73, Stefan

--------------040602050108060307010705--