From: "Clemens Paul" <cpaul@gmx.net>
To: <rsgb_lf_group@blacksheep.org>
References: <1115219056.3583883.1555284806139.ref@mail.yahoo.com> <1115219056.3583883.1555284806139@mail.yahoo.com> <5CB4404E.1070405@posteo.de> <9279541555322759@myt5-96980ae04900.qloud-c.yandex.net> <9058813427D24C038D3F134D7D17504F@Clemens0811> <5998878f-b85f-9390-2f9c-539eca7b41eb@gmx.net>
In-Reply-To: <5998878f-b85f-9390-2f9c-539eca7b41eb@gmx.net>
Date: Fri, 19 Apr 2019 17:16:36 +0200
Message-ID: <2F01FB78C6694AFA8BED6EFB22A81E44@Clemens0811>
MIME-Version: 1.0
Thread-Index: AdT1bErAqiaQk857Q4KPnqRKaLxalQBU+xrg
Subject: RE: LF: IW4DXW with bad signal on MW in WSPR
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Content-Transfer-Encoding: 8bit

Hi Tobias,

I believe it was rather a temporary SW or HW problem of Perseus which had been
started shortly before ,i.e. cold.
Also in the spectrum display (no soundcard involved) the signal looked strange which drew my attention first.
Then the multiple decodes showed up.
And I saw another double decode in the database by DK7FC/p.
Later transmissions decoded normally.
I've never have seen such a phenomen in my RX setup so far,
Only the QRO stations with real sidebands due to insufficient filtering of their power supply have
produced multiple decodes so far.
There have been three of them in the last years but two of them have managed to
produce a clean signal since a while. 

73
Clemens
DL4RAJ 


>-----Original Message-----
>From: owner-rsgb_lf_group@blacksheep.org 
>[mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Tobias DG3LV
>Sent: Thursday, April 18, 2019 12:19 AM
>To: rsgb_lf_group@blacksheep.org
>Subject: Re: LF: IW4DXW with bad signal on MW in WSPR
>
>Hi Clemens !
>
>Your soundcard has a temporary problem. When you see the signals on the
>waterfall, every signal is modulated by this. Restart the WSJT-X and/or
>the soundcard driver, and the problem vanishes. I have that 
>same problem
>from time to time, sometimes even a restart of windows was necessary.
>Yet no idea what causes this.
>
>73 de dg3lv Tobias
>
>Am 17.04.2019 um 22:11 schrieb Clemens Paul:
>> Hello,
>>
>> IW4DXW is booming in here but unfortunately his signal has a
>> very poor purity,hence the multiple deoces.
>>
>>   2019-04-17 20:02   IW4DXW   0.475802   -7   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475787   -7   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475794   0   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475775   -19   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475791   -6   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475772   -20   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8
>>   2019-04-17 20:02   IW4DXW   0.475760   -24   0   JN64bw   
>0.5   DL4RAJ   JN68kj   389   8  7
>>
>> 73
>> Clemens
>> DL4RAJ
>>
>>
>>
>
>
>---
>Diese E-Mail wurde von AVG auf Viren geprüft.
>http://www.avg.com
>