[Elecraft] K3<-->KPA500 Request

N2BC n2bc at stny.rr.com
Thu Mar 1 10:43:01 EST 2012


"when transmitting" is the problem... key the mic and say nothing:  the
program could determing the TX mode but the output is zero.      I suppose
the KPA500 could simulate a peak-hold  power function, but the
implementation would have to be in the KPA firmware, the K3 firmware and
probably in the application program.  I just write "500" in my log.

-----Original Message-----
From: Phil Hystad [mailto:phystad at mac.com] 
Sent: Thursday, March 01, 2012 9:58 AM
To: n2bc at stny.rr.com
Cc: 'Jack Brindle'; 'Elecraft Reflector'
Subject: Re: [Elecraft] K3<-->KPA500 Request

It still seems to be a useful feature.   I mean, you usually only "read" the
power level when transmitting anyway, at least that is what I do.  So, this
is how it could work that would satisfy me.  Given a K3 power setting, the
output power of the KPA500 is read when transmitting which can be saved in
memory on the K3 and thus available via the programming interface.  If the
K3 power setting is changed, or other changes such as band changes and so on
occur, then this KPA500 power setting can be cleared to zero until the K3
transmits again using the KPA500 and thus getting a new value.  Not a
perfect solution but it seems to be able to work in most situations.

phil, K7PEH


On Mar 1, 2012, at 6:41 AM, N2BC wrote:

> The program is reading the power SETTING on the K3 - not the K3 output 
> power
> - is available regardless of mode or if the K3 is transmitting or
receiving.
> The KPA500's "power" data is essentially RF forward power and would be 
> an instantaneous reading... so if the data is requested while in RX 
> the result is zero...
> 
> Bill N2BC
> 
> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net 
> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Phil Hystad
> Sent: Thursday, March 01, 2012 9:21 AM
> To: Jack Brindle
> Cc: Elecraft Reflector
> Subject: Re: [Elecraft] K3<-->KPA500 Request
> 
> I am also a MacLoggerDX user...
> 
> If the KPA500 knows the output power well enough to make it available 
> on its own serial port then why can't it send that info back to the K3 
> through the
> K3-KPA500 interface.  I think the original request is a one with good 
> technical merit that could be implemented -- maybe without too much 
> hassle by the Elecraft programmer(s).
> 
> 73, phil, K7PEH
> 
> 
> On Feb 29, 2012, at 11:04 PM, Jack Brindle wrote:
> 
>> Jim;
>> 
>> The KPA does not send its output power information to the K3, so the 
>> K3
> would just be guessing. The measured output power _is_ available from 
> the KPA500's serial port, so it would be much better if MacLoggerDX 
> were to get this information directly from the amplifier. Make a 
> request to the author to get him to add KPA500 control to the program. 
> I'll even volunteer to help Don if he needs it (doubtful - he is good).
>> 
>> Jack Brindle, W6FB
>> 
>> 
>> On Feb 29, 2012, at 10:17 PM, Jim Bennett wrote:
>> 
>>> I use MacLoggerDX (MLDX) for QSO logging, among other tasks. It
> interfaces very nicely between my K3 and the MacBook Air laptop. The 
> K3 passes a lot of data (including power output level) to MLDX and it 
> winds up in my log. However, when I'm using the KPA500, the K3 only 
> sends the driving power that it outputs to the amp. What I wind up 
> with in my log is incorrect. For example, if the KPA500 is in OPERATE 
> mode and I log a QSO, it'll get reported as a QSO made using 25 watts 
> or power, instead of the 450
> - 500 that the amp is putting out. Since the K3 and the KPA500 "speak 
> the same language" and talk to each other, can the firmware be changed 
> so that the K3 sends corrected Power Out level to the output data port 
> when the
> KPA500 is engaged? As it is now, I have to go back into MLDX after 
> every QRO contact and change the power field to reflect the actual 
> power and not the K3's driving power.
>>> 
>>> Regards, Jim / W6JHB
>>> Folsom, CA
>>> ______________________________________________________________
>>> Elecraft mailing list
>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>>> Help: http://mailman.qth.net/mmfaq.htm
>>> Post: mailto:Elecraft at mailman.qth.net
>>> 
>>> This list hosted by: http://www.qsl.net Please help support this 
>>> email list: http://www.qsl.net/donate.html
>> 
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:Elecraft at mailman.qth.net
>> 
>> This list hosted by: http://www.qsl.net Please help support this 
>> email
>> list: http://www.qsl.net/donate.html
> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net Please help support this email 
> list: http://www.qsl.net/donate.html
> 



More information about the Elecraft mailing list