Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: IW4DXW with bad signal on MW in WSPR

To: [email protected]
Subject: Re: LF: IW4DXW with bad signal on MW in WSPR
From: DK7FC <[email protected]>
Date: Fri, 19 Apr 2019 18:25:10 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1555691111; bh=TES/r1xWwI8nyarMNU9bLtV2ALnnEWWAp24ORNvup1M=; h=Date:From:To:Subject:From; b=bmzIAZO3luhpbZSol5a/XlcZajGGJ/Z6pFZWfW8MIKiQD2Wk2/ESLD6aBYfVxpw+v QQIs/DZR62ovf2CupBqhff3tm8Dm7W05dmKxPKtT7VIzcDon9cgG9wm7AhdIjTp2pp XyqQqMagqlZxVEG5UkequiPleEVCM7Er+VH2JTxNncmNTIcchTFT21MUdqZCGBqgRa 7FsZXB8UO/04HIRjRVADRmLhZFcjYXFaeNY2e8XiG1WfLdEJNIkPdrj0flKP1Z6WtI JGuqHyqcSOUX4jMaz1EtRFU64j/X9ffVw5UlrGDkZNlAIP1jNoyCoKZqJw7QkU8sbq jeaAX9keCkq6w==
In-reply-to: <559808A0C84F4073A94E20E3FE0F6863@Clemens0811>
References: <[email protected]> <[email protected]> <[email protected]> <559808A0C84F4073A94E20E3FE0F6863@Clemens0811>
Reply-to: [email protected]
Sender: [email protected]
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
Hi Clemens,

Yes, indeed. This is because i am running two identical receivers (using the same LO) with two orthogonal loops into my tree (/p) and then two WSPR instances using the same callsign (DK7FC/p). Sometimes WSPR uploads all two spots and sometimes just one of them (of course sometimes there is a decode at one antenna only). So this is not an anormality.

73, Stefan


Am 19.04.2019 17:16, schrieb Clemens Paul:
Hi Stefan,

A quick look to the database shows that the signal from Rik
looks clean at any RX site, except at DL4RAJ.
You know, the complainers ;-)
There was indeed another multiple decode,albeit on the same frequency.

2019-04-17 20:02         IW4DXW          0.475797        -3      0       JN64bw 
         0.5     DK7FC/P         JN49ik          563
334
  2019-04-17 20:02       IW4DXW          0.475797        +1      0       JN64bw 
         0.5     DK7FC/P         JN49ik          563
334


73
Clemens
DL4RAJ




-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of DK7FC
Sent: Wednesday, April 17, 2019 10:46 PM
To: [email protected]
Subject: Re: LF: IW4DXW with bad signal on MW in WSPR

Hi Markus,

A quick look to the database shows that the signal from Rik
looks clean at any RX site, except at DL4RAJ.
You know, the complainers ;-)

73, Stefan



Am 17.04.2019 22:29, schrieb Markus Vester:

        Hi Clemens,

        the signal from Ric looks perfectly clean at DL0AO,
indeed a strong signal but no multiple decodes.

        73, Markus
        
        
        
        -----Ursprüngliche Mitteilung-----
        Von: Clemens Paul<[email protected]>  <mailto:[email protected]>
        An: rsgb_lf_group<[email protected]>
<mailto:[email protected]>
        Cc: rsgb-lf-group<[email protected]>
<mailto:[email protected]>
        Verschickt: Mi, 17. Apr. 2019 22:13
        Betreff: LF: IW4DXW with bad signal on MW in WSPR
        
        
        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





<http://www.avg.com/email-signature?utm_medium=email&utm_source
=link&utm_campaign=sig-email&utm_content=emailclient>        
Virenfrei.>www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source
=link&utm_campaign=sig-email&utm_content=emailclient>        



<Prev in Thread] Current Thread [Next in Thread>