Login  Register

RE: K2 Calibration using WWV

Posted by Don Wilhelm-3 on Apr 24, 2006; 3:01pm
URL: http://elecraft.85.s1.nabble.com/Need-help-for-sick-K1-tp389102p389113.html

Thanks for posting this Tom.  It has since been written as an application
note and is available on the Elecraft website in .pdf format - see
http://www.elecraft.com/Apps/K2%20C22%20Adjust%20App%20Note.pdf

I have only one thing to add and that is for us 'tone-deaf' folks tuning WWV
precisely may be difficult (and the procedure does depend on precisely
tuning WWV or other reference frequency) - I can get close by listening to
the voice, but I may be as much as 100 Hz off.

I connect the computer running Spectrogram and listen to the transmitted
tones - WWV transmits 500 and 600 Hz tones on alternate minutes, and I look
for these tones displayed on the Spectrogram screen - I set markers at 500
Hz and 600 Hz - then adjust the tuning until the tones line up with the
markers.  It is easy to get within 10 Hz this way.

Another way is to use the SPOT to provide a reference tone - set the
sidetone pitch at 500 or 600 Hz and tune the WWV tone for zero-beat with the
SPOT tone.  Of course, if you zero with the 500 Hz tone thinking it was the
600 Hz one, you will be 100 Hz off, but listening for a short while will
quickly indicate this error.

There are other accurate ways of setting the 4 MHz master oscillator, and
some are contained in the K2 Dial Calibration article on my website
http://w3fpr.qrprqdio.com

73,
Don W3FPR


> -----Original Message-----
>
> Here's an 'improved' method for zeroing the MCU master Oscillator.
> Comes directly from the designer, N6KR:
>
>    Subject: 4 MHz oscillator cal method for the K2
>    Date: Wed, 20 Aug 2003 13:57:44 -0700
>    From: Wayne Burdick <[hidden email]>
>
>    All of the methods that have been described for
>    calibrating the K2's 4-MHz oscillator will work. But I use
>    a different technique that allows C22 on the Control board
>    to be set to precisely to the correct position, with no
>    guesswork.
>
>    This method relies on the following simple observation. If
>    you tune in an on-air signal at a known frequency, the
>    difference between the *measured* VCO and BFO (using CAL
>    FCTR) *must* equal that frequency, or C22 is not set
>    correctly. (Actually, this holds for 160-17 m; on 15-10 m
>    it's the sum, or VCO + BFO, that must equal the signal's
>    frequency. But it's easier to do the adjustment of C22 on
>    17 m or lower because you don't have to do any math at
>    all, as I'll explain below.)
>
>    Here's the procedure. It requires revision 2.XX firmware,
>    and assumes you have already done Alignment and Test, Part
>    II, at some point. The K2 should also be allowed to come
>    up to room temperature.
>
>    1. Tune in a signal at a known frequency. Use one that's
>       at an *exact* kHz boundary, so you can easily see when
>       the VCO and BFO readings match in step 2. (I use WWV at
>       10, 15, or 20 MHz.) Use USB or LSB mode rather than CW,
>       so that there will be no CW receive offset. In the case
>       of a K2 I was calibrating, the VFO read 10000.17 when
>       the signal was tuned in perfectly. If it had read
>       10000.00, no further improvement would have been
>       possible.
>
>       TIP: Zero-beat the carrier precisely, or listen to a
>       voice signal and adjust the VFO for the best quality.
>       The more accurately you tune in the signal, the more
>       accurately you'll be able to set C22, below.
>
>    2. Run CAL FCTR. Now alternately move the K2's internal
>       counter probe between TP1 (VCO) and TP2 (BFO),
>       adjusting C22 in small increments until the kHz and Hz
>       digits at the two test points match as closely as
>       possible. In my case, the two readings matched at
>       14913.60 and 4913.60. The difference is exactly
>       10000.00--the frequency of the on-air signal.
>
>    3. Put the counter probe on TP1 (VCO), switch to 40
>       meters, and run CAL PLL.
>
>    4. Put the probe on TP2 (BFO) and run CAL FIL. For each
>       operating mode, vary each filter (or BFO) setting up 1
>       count, then back down, to force the K2 to take a new
>       BFO measurement for each and store it in EEPROM.
>
>    The VFO dial should now be very well calibrated.
>
>    If we get a lot of positive feedback on this method, we'll
>    post it as an application note.
>
>    73,
>    Wayne
>    N6KR
>
> You might want to hold up on dong anything at this juncture, until
> you get everything assembled and tested. It won't HURT to perform it
> now, but you might need to re-do it at the end as wel..
>
> 73,
>
> Tom Hammond    N0SS
>
>
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
>  http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.4.5/322 - Release Date: 4/22/2006
>
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com