I think the current firmware implementation for this (non-sticky) is OK. But, I sympathize with your concern.
In my use of the K3 (SN-11, SN-17 and SN-4959, with all the possible K3S upgrades), I sometimes wish TX TEST were sticky through a power cycle, but most times am glad it is not sticky. Even though I'm a long-time K3 user, I'm still sometimes baffled when transmit doesn't work due to the rig being in TX TEST mode. I've lost count of how many contests I've started with no one coming back to me when I eventually discover I was still in TX TEST mode from testing before the contest. Thus, the argument for non-sticky. OTOH, lately I've been spending a lot of time with CSS (the Contest Super Simulator) and I'm having the opposite issue. I fire up the simulator, WriteLog and the K3, only to realize (long into my simulation session) that I am transmitting rather than being in TX TEST mode. This is due to the non-sticky aspect through a power cycle. So, I can see both sides, but on balance I believe the current non-sticky implementation is best. BTW, one could argue for a user-configuration parameter in CONFIG to choose between sticky and non-sticky, but I still think that is a waste of Wayne's valuable firmware time for little benefit. Ed W0YK ____________________________________________________________________ Brian K3KO wrote: Recently I was doing something requiring that K3 not transmit power. TX test was selected. I expected that it would retain this setting after shutdown and subsequent restart. It does NOT stick with a K3 S/N 8XXX and FW 5.38. Is this the way it is supposed to work? Fortunately we didn't transmit into anything and destroy it. ______________________________________________________________ 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 Message delivered to [email protected]
