Thanks to all of the responses. "Dual RX always on" helps with the sub-rx being generally left on. However, the VFO-B window was still 'popping' at each CQ, and with dual-rx-always-on, a noticable 'chunk' is heard in the audio at the tx-to-rx transition. Oh, and the VFO-B window was still being displayed with buttons having no legends on them.
With so many configurable features between the K3, N1MM, microham router, etc. I can understand the assumption of "pebkac" on the part of responders, so I continued to try to solve this. I've been using N1MM for a very long time, and can usually diagnose it pretty well. What I did find that solved the 'VFO-B' window popping with no labels issue was changing (in the configurer tab) from SO2V to SO1V, saving, sending CQ, then immediately switching back to SO2V. Let me repeat that: Changing from SO2V to SO1V, then back to SO2V, should (in theory) produce no different results. However, it did/does. And for now, it solves my issue. If someone else encounters this issue, perhaps this benign suggestion of changing from SO2V to SO1V and back again will help. Brian N9ADG ________________________________ From: Guy Olinger K2AV <[email protected]> To: Arie Kleingeld PA3A <[email protected]> Cc: [email protected]; Brian Moran <[email protected]> Sent: Sat, January 29, 2011 11:21:05 AM Subject: Re: [Elecraft] Elecraft Firmware 4.25 / MicroHAM / N1MM 11.1.4 Exactly, if "Dual Rx always on" is not set, MM will kill the sub RX AND turn off diversity every time you click on a spot to QSY. 73, Guy. On Sat, Jan 29, 2011 at 11:22 AM, Arie Kleingeld PA3A <[email protected]> wrote: Brian, > >In N1MM - Config - Dual RX always on > > >73 >Arie PA3A > >Op 29-1-2011 17:14, Brian Moran schreef: > >> I'm participating in the cq160 contest, and am having some difficulty w/the >>4.25 >> firmware, thought I'm not sure it's particular to this version. >> >> When I'm using the sub-rx, the setup gets 'into this mode' where where the >> sub-rx is switched OFF when I stop CQing. Turning on and off the radio >>sometimes >> (2 out of 3?) cures it. Stopping N1MM does NOT cure it. Stopping the Microham >> driver (7.7.1) does NOT cure it every time. >> >> I captured the serial comms in the Microham utility -- it's at >> https://bmoran.onehub.com/d/1xu7/k3_vfo_weirdness.log (or also >>https://bmoran.onehub.com/n9adg/pages/home/content_items/show/7e6c4002f30b31f260a223059206a88df93e9f5c/k3_vfo_weirdness.log) >>) >> >> >> Has anyone else seen this? >> >> Any pointers on what other information to gather to troubleshoot this? >> ______________________________________________________________ >> 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 > ______________________________________________________________ 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
