Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+IW4DXW\s+with\s+bad\s+signal\s+on\s+MW\s+in\s+WSPR\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+IW4DXW\s+with\s+bad\s+signal\s+on\s+MW\s+in\s+WSPR\s*$/: 9 ]

Total 9 documents matching your query.

1. LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: "Clemens Paul" <[email protected]>; Date: Wed, 17 Apr 2019 22:11:37 +0200; 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 I; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00117.html (11,170 bytes)
2. Re: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: Markus Vester <[email protected]>; Date: Wed, 17 Apr 2019 20:29:49 +0000 (UTC); /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00118.html (11,881 bytes)
3. Re: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: DK7FC <[email protected]>; Date: Wed, 17 Apr 2019 22:45:39 +0200; 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 Veste; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00119.html (13,024 bytes)
4. Re: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: DK7FC <[email protected]>; Date: Wed, 17 Apr 2019 22:50:05 +0200; PS: This specific transmission (20:02 UTC) is still visible at http://www.iup.uni-heidelberg.de/schaefer_vlf/DK7FC_remote_Grabber.html, on both loops, E-W and N-S. Am 17.04.2019 22:45, schrieb DK7FC:; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00120.html (13,192 bytes)
5. Re: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: Tobias DG3LV <[email protected]>; Date: Thu, 18 Apr 2019 00:19:06 +0200; 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 vani; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00121.html (11,625 bytes)
6. RE: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: "Clemens Paul" <[email protected]>; Date: Fri, 19 Apr 2019 17:16:36 +0200; Hi Stefan, 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; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00133.html (13,226 bytes)
7. RE: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: "Clemens Paul" <[email protected]>; Date: Fri, 19 Apr 2019 17:16:36 +0200; 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 str; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00134.html (13,954 bytes)
8. Re: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: DK7FC <[email protected]>; Date: Fri, 19 Apr 2019 18:25:10 +0200; 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 (DK7F; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00137.html (14,019 bytes)
9. RE: LF: IW4DXW with bad signal on MW in WSPR (score: 1): Author: "Clemens Paul" <[email protected]>; Date: Fri, 19 Apr 2019 18:52:41 +0200; Hi Stefan, thanks for the explanation. 73 Clemens DL4RAJ; /rsgb_lf_group-archives/html/rsgb_lf_group/2019-04/msg00139.html (15,822 bytes)

Current List: 1 - 9
Page: [1]