Lyn, Can you share your source that COM port reassignment is a deliberate security feature? I'm curious what vulnerability it's mitigating.
Thanks, Julie On Thu, Jun 30, 2022 at 3:25 PM Lyn Norstad <[email protected]> wrote: > Are you running Windows 10 by any chance? > > As a security measure, Win 10 automatic updates often reassign COM port > numbers. > > If you know how to do it, you can rename and reassign port numbers. If you > give them a number of 20 or higher, Win 10 update will leave them alone. > > Hint: Control Panel>Device Manager>Ports>(Elecraft connection > port)>General>Advanced>COM Port Number > > Be sure to make the corresponding port number change in the software. > > 73 > Lyn, W0LEN > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Peter Dougherty > (W2IRT) > Sent: Thursday, June 30, 2022 12:28 AM > To: 'George Thornton'; [email protected] > Subject: Re: [Elecraft] COM port problems > > It's possible (and I'm guessing somehow likely), but darned if I know what > to even look for. These are things that were set when the computer was > built > from scratch last year, they have worked 100% reliably over thousands of > QSOs in both Commander and N1MM+ ever since, and absolutely nothing was > changed in terms of configuration or even a Windows Update in at least two > weeks. I just needed to restart the computer after moving it from a wall > outlet to a UPS, and it started going crazy from that point on. > > Whatever the issue is, it seems to affect ALL the COM ports in the system > the same; neither Commander nor N1MM can open the radio port, or either of > the two rotor ports. > > I did somehow manage to get Commander working (don't aske me how, it just > started), but the rotors are still no-go (and not critical at the moment). > > > > - pjd > > > > From: George Thornton <[email protected]> > Sent: Wednesday, June 29, 2022 10:23 PM > To: Peter Dougherty (W2IRT) <[email protected]>; [email protected] > Subject: RE: [Elecraft] COM port problems > > > > It is possible the parameters set in the computer after reboot don't match > those set in the program. Check the port and baud settings. > > > > Generally xom port settings need to match for communication to occur. > > > > > > > > Sent from my Galaxy > > > > > > > > -------- Original message -------- > > From: "Peter Dougherty (W2IRT)" <[email protected] <mailto:[email protected]> > > > > Date: 6/29/22 6:59 PM (GMT-08:00) > > To: [email protected] <mailto:[email protected]> > > Subject: [Elecraft] COM port problems > > > > OK, got a massive problem that just cropped up this evening that is far > beyond my understanding that has completely killed my ability to use my K3 > with my computer. > > > > After restarting the PC, suddenly I cannot communicate with the radio using > DX Lab Suite or N1MM+ on the assigned COM port. I have downloaded the K3 > Utility software and it is able to connect to the radio on COM5, its usual > port, and invoke macros via the Utility. So I know there's proper > communication between the radio and the PC. But once I close down the K3 > Utility program I get the first major problem. The radio goes into transmit > for 10 seconds, releases for about 4 or 5 second, and goes back in to > transmit. Only powering the radio off and back on again stops this > behavior. > > The main issue is that no CAT control software seems to be able to connect > to the radio at all. The radio is on COM5, and has been for at least the > last 4 or 5 years, and until today it has just worked, even after building > a > new computer last November. I just rebooted today and everything went to > heck. > > The kicker is that's it's not a K3 hardware problem, and since it works > with > neither N1MM nor DX Lab software any more it's apparently not those > programs > either, and quite frankly I just don't know where to look next. Compounding > the issue, and likely related to it, the N1MM Rotor control cannot find > either COM port assigned to the rotors (COM1 and COM3). I have tried > removing the ports and re-adding them in Device Manager but the problem > still persists. I am absolutely prepared to pay a certified systems > professional to diagnose and fix this, but with ultra-specialized radio > gear > I doubt they'd be able to figure it out either. Any suggestions? I'm > basically QRT until I can fix this. > > > > > ---------------------------------------------------- > > Regards, > Peter Dougherty, W2IRT > > DXCC Card Checker/CQ-WAZ Checkpoint > > www.facebook.com/W2IRT <http://www.facebook.com/W2IRT> > > > > ______________________________________________________________ > 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] > <mailto:[email protected]> > > ______________________________________________________________ > 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] > > ______________________________________________________________ > 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] > ______________________________________________________________ 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]
