Problem solved.

Turned out failure of the 1 mW test was caused by a defective dummy load used 
at the XVTR-OUT connector for the test.

Thanks for the many quick/detailed/in-depth responses (some by off-list 
responses); fortunately this was a self-inflicted issue, unrelated to the K3 at 
all.

73 Dave WB0GAZ [email protected]

> Message: 13
> Date: Tue, 23 Mar 2010 17:12:29 -0600
> From: david feldman <[email protected]>
> Subject: Re: [Elecraft] New K144XV/KXV3A - problems on 2M - 1
>       milliwatt calibration ERR TXG and 'Unexpected response "DB 0.56 MW; "
>       to "DB; " State 153'
> To: <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="Windows-1252"
> 
> 
> Partially fixed - I had set XV1 ADR to TRN1 instead of INT TRN1.
> 
> Once I changed that, I found many problems corrected - I was able to set the 
> two offset frequencies, I hear the relay switching between band segments, and 
> I am now able to receive on 2M.
> 
> However, I repeated the calibration using the K3 utility and I still get this 
> message:
> 
> 5 watt calibration succeeded
> IsSamplingComplete: Unexpected response "DB 0.52 MW;" to "DB;" State 153
> 1 milliwatt calibration failed
> 
> and after the calibration is done, I see the following on the display.
> 
> ERR TXG
> 
> How do I interpret this message?
> 
> I'm much closer now thanks to the quick help!
> 
> 73 Dave WB0GAZ [email protected]                                       
> ****************************************
                                          
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/210850553/direct/01/
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Reply via email to