[Elecraft] K3 command mode default k30 k31

[Joe Subich, W4TV]

Don, 

> That sounds like a programing deficiency in the Microham MK2. 
> The fact that the K3 defaults to K30 on power on is documented 
> in the Programmer's Reference as default.

That's uncalled for.  

The K3 "RTTY" mode is ambiguous in its default configuration.  
There is no way for software to  distinguish among the four 
data sub-modes with the default "K30" response set.   

The hallmark of good software is that IT NEVER CHANGES THE STATE 
OF THE RADIO UNEXPECTEDLY.  This is particularly true for microHAM 
Router since it has to interoperate with a multitude of logging 
and data programs - some of which require K30 mode and some of 
which use the K31 configuration. 

The appropriate "fix" would be for the "data sub mode" report 
to be present in the IF (autoinformation) report at all times 
- but that's not the way the K3 currently operates - or for 
the K3 to add two "new" modes to indicate audio based data 
submodes (AFSK_A or DATA_A) like Yaesu did in their Kenwood 
like protocol for the FT-9000/2000/950/450.  

The lack of information on AFSK/PSK vs. FSK simply means that 
this one feature of the microHAM interfaces (DigiKeyer, 
microKEYER, microKEYER II) is not supported with the K3 
because the K3 fails to provide the necessary data.  

Except for the K2 and K3 (and Flex-Radio), the RTTY mode in 
every other transceiver manufactured in the last 20 years (and 
all Kenwood transceivers except the TS-440) is always FSK.  
With the K2 "RTTY" is AFSK and with the K3 "RTTY" is ambiguous.  

73, 

   ... Joe, W4TV 
 


> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net 
> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Don Wilhelm
> Sent: Thursday, October 01, 2009 7:48 PM
> To: Hugo pa4la
> Cc: elecraft at mailman.qth.net
> Subject: Re: [Elecraft] K3 command mode default k30 k31
> 
> 
> Hugo,
> 
> That sounds like a programing deficiency in the Microham MK2. 
>  The fact 
> that the K3 defaults to K30 on power on is documented in the 
> Programmer's Reference as default.
> If a device needs to use an extended mode command, it should 
> query the 
> state - the K3 command can be used as a GET or a SET, so the 
> programmer 
> can determine the state before issuing the command.
> 
> 73,
> Don W3FPR
> 
> Hugo pa4la wrote:
> > I am playing with my Microham MK2 and have learned that,
> >
> >  the K3 must be in extended (k31) command mode for the MK2 
> to switch 
> > correct between audio or fsk data modes
> >
> >  
> >
> > When the K3 is powered on, the mode setting is always standard k30.
> >
> > Putting the k31 command via a terminal is not a big issue 
> but it would 
> > save a couple of mouse clicks :)
> >
> >  
> >
> > Is there a way tot save the k31 setting or a way to make k31 the 
> > default setting?
> >
> >  
> >
> > Tnx in advance,
> >
> >  
> >
> > Hugo pa4la
> >   
> >
> ______________________________________________________________
> 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