Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+Re\:\s+RE\:\s+WSPR\s+beacon\s+on\s+136kHz\s+\-\s+QRT\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+Re\:\s+RE\:\s+WSPR\s+beacon\s+on\s+136kHz\s+\-\s+QRT\s*$/: 4 ]

Total 4 documents matching your query.

1. LF: Re: RE: WSPR beacon on 136kHz - QRT (score: 1): Author: <[email protected]>; Date: Sun, 11 Jan 2009 21:31:09 -0500; Jim Looked...but no joy. Jay W1VD WD2XNS WE2XGR/2 Dear LF Group, The WSPR beacon is now QRT at 0206utc - I was worried about falling asleep with 900W going up the antenna, which is now waving around; /rsgb_lf_group-archives/html/rsgb_lf_group/2009-01/msg00388.html (11,847 bytes)
2. LF: RE: RE: WSPR beacon on 136kHz - QRT (score: 1): Author: "Dave G3WCB" <[email protected]>; Date: Mon, 12 Jan 2009 20:16:12 +0100; Hi Jim, LF. Sadly no decodes from M0BMU or DF6NM on 136 last night. M0BMU was clearly audible and was showing on the waterfall display. I'm using WSPR 1.01_r1023, and it worked fine on 500kHz the oth; /rsgb_lf_group-archives/html/rsgb_lf_group/2009-01/msg00690.html (12,105 bytes)
3. Re: LF: RE: RE: WSPR beacon on 136kHz - QRT (score: 1): Author: Wolfgang Büscher <[email protected]>; Date: Mon, 12 Jan 2009 20:44:08 +0100; Hi Dave, Except from trying WSPR (the standalone GUI version) a few times on shortwave and LF, I can only tell you that.. - it's very important to sync the local PC time accurately - but sure that's; /rsgb_lf_group-archives/html/rsgb_lf_group/2009-01/msg00872.html (12,379 bytes)
4. Re: LF: RE: RE: WSPR beacon on 136kHz - QRT (score: 1): Author: Piotr Mynarski <[email protected]>; Date: Mon, 12 Jan 2009 21:50:19 +0100; Hi Jim, LF. Sadly no decodes from M0BMU or DF6NM on 136 last night. M0BMU was clearly audible and was showing on the waterfall display. I'm using WSPR 1.01_r1023, and it worked fine on 500kHz the oth; /rsgb_lf_group-archives/html/rsgb_lf_group/2009-01/msg00922.html (13,747 bytes)

Current List: 1 - 4
Page: [1]