To: | [email protected] |
---|---|
Subject: | Re: LF: Re: QRSS / beacon test on 503.7kHz |
From: | Andy Talbot <[email protected]> |
Date: | Thu, 2 Apr 2009 21:20:56 +0100 |
Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wX3lvuBbjQhciYby4gyTqy9ARD1rokkgyv3MK8kc03s=; b=CB2pQIc3x4C6762evff+qof2VLK+a7b3OopjeYHoO/OYPrIOsRx7RQWzG5//pF3IyZ S8YPkI2Hw9kqpU85RKbCVM7DAjNvZhcTsiN9WDjS1nO22cVLG/x8r5Jh0qVzSQp9g8NX V9FQcO+E8EgIUHWOYTtHzpPOMqtqafbuIsYP4= |
Domainkey-signature: | a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=QRDAehXXK2yE66v84SNJ3bTMyMESS7Nvm0nLeAOleUGKxEGwR2PQTTyah67d0Rohpp gWe7A7AvrEhSUBYv9/EG3enDCJD1UpDYJxDWeSFm4bEGJXtbj/QhcZopxi9zKsQ/Qb5i pGeSml1AMQ6K795I/vfsMrimGp6SUbnCOxVUI= |
Domainkey-status: | good (testing) |
In-reply-to: | <008001c9b37b$29682450$6401a8c0@asus> |
References: | <0FD81C970D1F4740A80463DB2680F696@ns94d01ae4d850> <[email protected]> <[email protected]> <E321AF403CCD4A11AC93F651BA8D6D03@DR2> <[email protected]> <001901c9b307$f6e5ad40$6401a8c0@asus> <[email protected]> <008001c9b37b$29682450$6401a8c0@asus> |
Reply-to: | [email protected] |
Sender: | [email protected] |
There is not really any such thing as a hit with this "monitoring software" - it is not a logger as such, just an estimate of the frequency of a peak stable in a narrow bandwidth when measured over the critical five second period.
The left-hand plot you see on the screen covers a spectral plot +/-25Hz on the centre frequency, using an FFT with bins 0.2Hz wide. After windowing this gives an effective noise-bandwidth of 0.4Hz. A peak detector looks for the highest bin and plots the amplitude of this in the right hand window. If the detected peak is stable enough then the frequency is determined. If it isn't, or the peak varies due to noise hits, the frequency isn't logged.
What you are referring to as 'hits' are S/N ratio measurements (in a 0.4Hz bandwidth) at the frequency it 'thinks' the peak lies at, ie. at the highest peak detected anywhere in the total span, in the time interval 25 - 30 seconds for each of the three time slots, as defined by the PC's clock with the time offset applied.This corresponds to the third, most prominent, peak on the right hand plot which should hit its maximun at the 30 second marker.
Therefore, provided the signal hasn't drifted out of the +/-25Hz span range (and I doubt even a ceramic resonator will do that) and provided there is no QRM giving a higher false peak, it will be logged.
The noise part of the S/N is measured over the complete minute preceding the three slots. So if there is any signal in there it will distort the noise measurement, and hence the reported S/N
2009/4/2 Gary - G4WGT <[email protected]>
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: LF: 503.7kHz beacon , is anyone monitoring ??, Graham |
---|---|
Next by Date: | Re: LF: 503.7kHz beacon , is anyone monitoring ??, Andy Talbot |
Previous by Thread: | RE: LF: Re: QRSS / beacon test on 503.7kHz, Gary - G4WGT |
Next by Thread: | RE: LF: Re: QRSS / beacon test on 503.7kHz, Gary - G4WGT |
Indexes: | [Date] [Thread] [Top] [All Lists] |