Joe, I beg to differ. The K3 does provide the information on the command state via the 'K2n;' command and the 'K3n;' command. The K30 state is clearly documented as the default.
I repeat, any software that needs to issue K31 commands must assure that the K3 is capable of accepting those commands. This is a task for the programmer who says they support the K3 command set. IT IS NOT A MATTER OF NOT CHANGING THE STATE OF THE RADIO - the situation is that the software is trying to issue a command that requires the K31 state. The command cannot be received if the radio is not in the K31 state - so either the software must use an alternative method or it must set the K31 state. If the software must restore the radio to the K30 state afterwards (to be "good programming") than by all means, issue the K30 command at the end of the process. That fact that other radios 'do it differently' is not a reason for software which supposedly supports the K3 command set to make assumptions about the state of the K3. I do come from a long background that says any software that makes assumptions (without checking) is faulty programming. 73, Don W3FPR Joe Subich, W4TV wrote: > 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: [email protected] >> [mailto:[email protected]] On Behalf Of Don Wilhelm >> Sent: Thursday, October 01, 2009 7:48 PM >> To: Hugo pa4la >> Cc: [email protected] >> 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:[email protected] >> >> 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:[email protected] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.14.1/2407 - Release Date: 10/01/09 > 06:34:00 > > ______________________________________________________________ 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
