[Elecraft] K2 INFO 232 error with PLL
Dick Lamb
dick.judy.lamb at gmail.com
Mon Jun 29 14:09:18 EDT 2015
Don, I changed the setting to "Y," and it instantly jumped back on
frequency and everything is fine again. As always, I really appreciate
your expert and responsive help.
Dick, K0KK
On Mon, Jun 29, 2015 at 12:13 PM, Don Wilhelm <w3fpr at embarqmail.com> wrote:
> Dick,
>
> With the K60XV installed, do your have the menu for d10 set to "Y" - i
> needs to be that way or CAL PLL will fail as you stated.
> The initial frequency for CAL PLL is in the 12,960 to 12.990 range.
>
> Your TP1 reading also says that the frequency the K2 is trying to tune to
> is near 6350 kHz - again the problem is the d19 menu parameter.
>
> 73,
> Don W3FPR
>
>
> On 6/29/2015 11:46 AM, Dick Lamb wrote:
>
>> On a K2, the freq display is way, way off; e.g., on 40 meters it's really
>> receiving about 0.5 mHz lower. I tried to run CAL PLL but get INFO 232.
>> The PLL process appears to start, momentarily displaying 11,27164 mHZ,
>> then aborts in about a second with the INFO 232 error. I'm absolutely
>> positive before running PLL that the VFO shows a 40 meter freq and the
>> probe is plugged into TP1.
>>
>> The CAL FCTR readings for the TPs are: TP1 = 11271.8(4); TP2 = 4913.55;
>> TP3 = 12097.9(6) (Numbers in parentheses flicker between an adjacent
>> digit, but values are otherwise stable).
>>
>> Probably not relevant, but more background. This is my friends K2 for
>> which the KPA100 would not work. I traced problem to blown diode in swr
>> bridge, fixed it, and that problem was solved. Also, I Initially I made a
>> change in the set-up menu for the k60xv, not realizing it was installed.
>> Nothing else was touched--at least intentionally.
>>
>>
>>
>
More information about the Elecraft
mailing list