Ed Muns, W0YK wrote: > >> I would vote not to make Test mode persistent. While I find >> it very useful, it can be a trap for an inexperienced K3 >> user, to whom it might look like the radio simply isn't >> working. There is no indication that the radio is in Test >> mode, other than the failure to transmit. > > Actually, there is a (subtle) indication ... the TX icon blinks when in TX > TEST mode. >
I don't think this would help. You'd still have to remember to put it into TEST mode before switching it off. There is perhaps a case for having an option for the radio to come up in TEST mode and stay in that mode until it received a valid command over the RS-232. This could be useful for those who rarely if ever use the radio *without* a computer connected. Even if you don't have a serial port that asserts key down when no logger is active, many PCs do toggle the serial port control lines during the power-on tests at boot-up, causing the rig to transmit a series of dashes. I've had this happen a few times, when I switched on the radio before the computer. Partly because I'm also developing software and prone to accidentally transmitting test messages, I have got into the habit of always switching to TEST whenever I turn on the radio. Except when I forget to, of course. ----- Julian, G4ILO K3 s/n: 222 K2 s/n: 392 G4ILO's Shack: www.g4ilo.com KComm for K2/K3: www.g4ilo.com/kcomm.html -- View this message in context: http://www.nabble.com/K3-Key-down-on-power-up-tp18158201p18159592.html Sent from the Elecraft mailing list archive at Nabble.com. _______________________________________________ Elecraft mailing list Post to: [email protected] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com
