I agree. There are only two valid reasons for a transceiver refusing to obey a direct operator command: to avoid physical damage, or to avoid transmitting illegally out-of-band.
So when the operator presses the SPLIT button, the transceiver should do as it's told! Every other make of transceiver will do that, and will automatically reset the second VFO (or second RX) to the same band and mode as the main. Most will also allow the operator to program an automatic frequency offset to eliminate any possibility of transmitting on top of the DX station. Those "Smart Split" options have evolved into an industry standard for a very good reason: it is what users need and expect. The K3 is not being uniquely smart in behaving differently... just uniquely ignorant of the way that SPLIT is used in real life. Please don't anybody say "Use a macro" - I wrote my own Smart Split macro on the first day that facility was released. But the point is: I shouldn't have needed to do that. Industry-standard options like Smart Split should have been part of the K3's core firmware since version 1.0.0.0. Sigh... seven years down the line, I can't believe we're still needing to beg for something that is so industry-standard and so obvious. 73 from Ian GM3SEK >-----Original Message----- >From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >Frank Westphal >Sent: 02 October 2014 07:03 >To: Elecraft@mailman.qth.net >Subject: [Elecraft] Split N/A > >Every time I change modes from CW to RTTY or RTTY to CW I get the Split >N/A error message. I do not get this message when changing modes from >CW to SSB or SSB to CW. Since I am primarily a DXer who works split >having to change from split operation before mode change and then change >back to split operation requires a whole lot of button pushing. This is >extremely annoying almost to he point of considering selling the K3. >Elecraft told me this was for my own protection. I don't need a company >to tell me this is for my own protection and not willing to make a >product easy to operate. I hope someone out there is radio land has a >firmware fix for this annoying issue. Otherwise I have enjoyed >operating the K3 for the last year. > >Thanks in advance. > >Frank >K6FW ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
