[Elecraft] [K3] Logging programs and internal keyer

[Joe Subich, W4TV]

> I'm surprised 2) is a big deal for 
> contesting, when you are only sending very short "overs". 

Calls are corrected on a regular basis and many of the contest 
software authors are adamant about the ability to change anything 
that has not yet been sent, 

> In 
> the K2, it is possible to abort the unsent text by sending a 
> "KY @;" command. I'm not sure if Wayne has implenented this 
> in the K3 yet.

That works only on the K2 - at least according to the TS-2000 
manual.  In addition it involves a complete buffer flush and 
resend of any unsent information.  Since the KY command does 
not update the controlling program when each character is sent, 
it becomes impossible for the application to know what has been 
sent and is thus no longer available for editing ... or what 
must be resent in event of the buffer dump. 

> 3) is completely incorrect as far as the K2 and K3 goes. It 
> is possible to poll the radio and find out if the buffer is 
> full, part full or empty

First, this involves polling which increases programming overhead. 
Second, according to the TS-480, 570 and 2000 manuals the Kenwood 
implementation does not indicate when the buffer is empty - only 
if the buffer is full. 

The whole point is that the cost to implement KY support is much 
greater that the benefit given its limited capability and support. 

73, 

   ... Joe, W4TV 
 



> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net 
> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of G4ILO
> Sent: Sunday, May 25, 2008 11:05 AM
> To: elecraft at mailman.qth.net
> Subject: RE: [Elecraft] [K3] Logging programs and internal keyer
> 
> 
> 
> 
> Joe Subich, W4TV-3 wrote:
> > 
> > 
> > None of the three most commonly used contest logging programs
> > support the KY command.  All three authors/developer groups 
> > have investigated the KY command and rejected supporting it. 
> > The issues are: 1) KY is not universally supported - it is 
> > only useful with K2, K3 and some Kenwood transceivers.  2) 
> > once a message has been sent to the radio it is not possible 
> > to edit it (call corrections).  3) buffer management is very 
> > difficult - it is not possible for the logging program to know 
> > when a message has completed in order to implement timed delays 
> > (or repeating messages) with a known time between the end of the 
> > message and start of the repeat. 
> > 
> > 
> Although 1) is true, I'm surprised 2) is a big deal for 
> contesting, when you are only sending very short "overs". In 
> the K2, it is possible to abort the unsent text by sending a 
> "KY @;" command. I'm not sure if Wayne has implenented this 
> in the K3 yet.
> 
> 3) is completely incorrect as far as the K2 and K3 goes. It 
> is possible to poll the radio and find out if the buffer is 
> full, part full or empty. In fact it is essential to do this 
> as the K2 doesn't like being sent text its buffer doesn't 
> have room for.
> 
> -----
> Julian, G4ILO  K3 s/n: 222 K2 s/n: 392
> G4ILO's Shack: www.g4ilo.com
> Zerobeat Ham Forums: www.zerobeat.net/smf
> --