Return to KLUBNL.PL main page
| To: | <[email protected]> |
|---|---|
| Subject: | LF: Re: WSPR Timing issue - odd minute spots |
| From: | "Markus Vester" <[email protected]> |
| Date: | Sat, 31 Jan 2009 01:23:53 +0100 |
| In-reply-to: | <20090129204114.01d053e8@lurcher> |
| References: | <00f801c98235$a558af20$a402a8c0@Inspiron><FAEE5C1C09A4415EBB6C38E663C4EEDC@JimPC> <20090129204114.01d053e8@lurcher> |
| Reply-to: | [email protected] |
| Sender: | [email protected] |
Hi John, when I used a positive Dsec setting (eg. +1.5) in WSPR 1.01 to compensate for a PC clock running slightly behind UT, the reports came up with a timestamp from the past minute. This evening I could make out all five traces in the spectrogram, but only the stronger ones (BMU, JNT, NBD) were decoded. Markus, DF6NM ----- Original Message ----- From: "John P-G" <[email protected]> To: <[email protected]> Sent: Thursday, January 29, 2009 9:41 PM Subject: Re: LF: Re: WSPR Timing issue And occasionally one sees spots reported at WSPRnet with an ODD minute timestamp - how's that done? John |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | LF: Now running -10dBm 100uW WSPR, Lee Hudson |
|---|---|
| Next by Date: | LF: xgj, victor13 |
| Previous by Thread: | Re: LF: Re: WSPR Timing issue, John P-G |
| Next by Thread: | Re: LF: Re: WSPR Timing issue, Andy Talbot |
| Indexes: | [Date] [Thread] [Top] [All Lists] |