> ... So perhaps it was reset to "Not inst" > after loading the new firmware, but why would loading the new firmware > cause such a change?
I can't explain why it might happen, but on occasion after a firmware load, especially one that is moving up several generations, it is possible a config parameter might be altered. I suspect if you reloaded the new firmware, and experienced the same unexpected status of the ATU, it could be remedied through the CONFIG menu. Also, after a major upgrade, and once you see all is working properly, I recommend doing a configuration save using K3 Utility. 73, Lyle KK7P ______________________________________________________________ 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
