|
And he got a good decode both those two times, with the frequency reported as 870 in each case (odd minutes listed in the database, coz of high Dsec setting). Surely not two oddities, exactly cancelling, on two completely different machines.
2009/1/31 James Moritz <[email protected]>
Dear Andy, LF Group,
Oddly enough, at the time your e-mail arrived, I noticed on the WSPR display that your signal frequency had jumped from 503869 to 503883 Hz. It stayed there for 2 frames (1838, 1840utc) and during that time it did not decode. After that, it reverted to normal frequency, and decoded normally. The other signals on the spectrogram behaved normally during this time, so I'm sure this was nothing to do with the receiver here.
Cheers, Jim Moritz
73 de M0BMU
----- Original Message ----- From: "Andy Talbot" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Saturday, January 31, 2009 6:02 PM
Subject: LF: Anoterh WSPR timing error
John, G0API, has been monitoring my QRP WSPR beacon most of the afternoon,
and getting the occasional decode at a S/N of -19dB, ie quite good.
However, he only manages a decode about one time in 10, randomly. The
frequency is usually reported as ....855 instead of the ...870 it should be,
although once in a while, it reports 870 and gives a proper decode. So it
looks as if he may have some sort of intermitetnt fault that affects
sampling rate.
|
