I found a 16.9xx crystal on an old computer board and swapped it out.
Now the birdie has moved somewhere else.
My other choice was 16.670 but I figured that would wind up in the 6
meter band...
Thanks everyone for the help.
Sam N4MAP
___
Elecraft maili
On Jun 29, 2005, at 5:13 AM, Sam Smith wrote:
Thanks, Lyle,
Yes, I have K2 #1013 - lucky 13. I'm sure I bought the KIO2 as soon as
it came out. I'll check the crystal fequency tonight.
The KIO2 uses a crystal frequency of 16.289 MHz. It has NOT been
changed since the unit's inception. The K
Thanks, Lyle,
Yes, I have K2 #1013 - lucky 13. I'm sure I bought the KIO2 as soon as
it came out. I'll check the crystal fequency tonight.
Isn't there also a KIO2 in my remote PA? That one is probably the newer crystal?
Sam N4MAP
___
Elecraft mailing li
Sam,
Funny you should mention that. In my shack, I have the K2 with a KIO2
and also a 2 meter rig nearby. Whenever the K2 is on, the 2 meter rig
stops scanning and hangs on 146.625 and just breaks the squelch. As soon
as I shut the K2, scanning resumes.
Sam Smith wrote:
I noticed this at F
I noticed this at Field Day. The club was using a repeater with output
on 146.625. As soon as I turned on the K2 we got hash on that
frequency.
Any suggestions for tracking this down?
You must have an older KIO2 with the 16.289 MHz oscillator. The 9th
harmonic is 146.60 MHz.
You can change th
I noticed this at Field Day. The club was using a repeater with output
on 146.625. As soon as I turned on the K2 we got hash on that
frequency. Since then I have checked it at home with no computers
anywhere around and confirmed the problem.
I have the PA and the KAT100 in the EC2. A short cable c
6 matches
Mail list logo