Hi Token
On the '2 second' beep... sorry about calling it that it was a guess of mine and no equipment was used to determine the timing... <heh>
No reason to be sorry, your “2 second” was fine, I was just giving you the rough measured number if you were interested for your notes. And my measured number is probably not dead on the money, but should be within 0.005 sec.
A decent free program that will display spectrograms and allow such measurements would be Spectrogram (there are several others also). I find having at least a rough idea of the actual numbers can sometimes help ID things a little better.
As for the frequency... well the specs for the rig I was using on that intercept are as follows:
+- 4 ppm from 1 min. to 60 min after power on... and the rig was on for about 4 hours... Not lab standards for sure but fair to good for hobby purposes :-) reads out to 0.01 khz btw
Sorry for any confusion :-)
Again, no reason to be sorry, it was not a criticism. I was only telling you the actual center freq assuming your freq readout was correct. Some people like to log that, others could care less, it is all good either way. For CW signals it is preferable to log center freq if possible. Some tune CW in SSB, others in CW mode, and it can lead to confusion of the “real” freq unless you know the mode used and in the case of CW mode the CW offset of the receiver. This confusion can be a problem on some beacons (and other CW signals) that are tight packed in freq and similar in sound. Sometimes knowing the real freq can help determine which one you are hearing.
As before, a program like Spectrogram, Audacity, FLDigi, Argo, etc can be used to determine the center frequency form knowing your tuned freq and mode. Then you add (or subtract if in LSB) the offset to your tuned freq and you have the center freq.
T!