Re: [Elecraft] COM port problems

[Walter Underwood]

Finally, a sensible post about this.

It is funny that we argue about the purpose of amateur radio, because (for US 
amateurs) it is spelled out in FCC regulations. There are five purposes, two 
technical, one about technical and communication education, one about public 
service, and one about international goodwill. An amateur doing any one of 
those is solidly within the purposes of their license. An amateur following the 
regs and good practice and having fun on the air is also doing just fine in my 
book, even if they don’t know Amps from Volts.

https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97

Heartily agree about RS-232. When I got back into the hobby, I was appalled at 
all the serial control. The very last time that I used RS-232 with a computer 
was in 2001, rebuilding the kernel on an HP-UX server at Inktomi. I threw away 
my collection of RS-232 connector shells and crimp pins not long after that. 
Imagine my surprise when I was looking at rigs in 2009.

Anybody who’d like to learn more is welcome in the Amateur Radio Elmers group 
on Facebook. We welcome your questions and have zero tolerance for bad behavior.

https://www.facebook.com/groups/483873128439168

wunder
K6WRU
Walter Underwood
CM87wj
http://observer.wunderwood.org/ (my blog)

> On Jul 7, 2022, at 4:03 AM, Gerry Hull  wrote:
> 
> LOL!
> 
> Jim and Dave,
> 
> You both have made great contribution to the hobby.
> 
> I am an ex ARRL Assistant Technical Editor, working with  Doug DeMaw,
> W1FB,  and Jerry Hall,  K1TD in the Tech Department of ARRL, and  was a
> contributor to the ARRL Handbook  and  QST editor.  Oh, and 47 years in the
> hobby now:  I think i know a thing or two about radio, but, am always
> learning -- that's what keeps it interesting.
> 
> Other than that,  I've spent 35+ years as a software engineer.
> 
> Measuring a ham's worth by what they know technically is, sad to say, a
> very myopic view of the world.   Many hams are non-technical, especially
> new ones.  Many come to the hobby from non-technical backgrounds, and are
> usually excellent communicators. They enrich our hobby tremendously,
> never the less.
> 
> From my experience, RS-232  and CAT in general is one of the most difficult
> issues hams deal with.  "Plug and Play" and the details of the intricacies
> of the USB bus and different Windows device driver models are not on any
> ham exam, nor should an end user ever have to mess with them.It is a
> difficult challenge to solve for end uses due to the incredible complexity
> of the Windows PC ecosystem.
> 
> As a contester, I know messing with interfacing CAT, Sound and Networking
> are the bain of many, and consume the most time in prep for any event.
> This is the nature of our hobby today.  However, there is no need to get a
> CS degree to have fun.
> Please keep contributing, but remember not everyone has your skills.
> 
> Judging from the number of private emails I've received, I know I'm helping
> people solve their issues.
> 
> We are on the Elecraft reflector.
> 
> Bravo to the Elecraft team.  They build radios for communicators, not
> computer geeks.  IMHO, the only company that really gets that.
> 
> Peace.
> 
> 73,
> 
> Gerry W1VE
> 
> 
> 
> 
> 
> 
> 
> 
> On Thu, Jul 7, 2022, 4:58 AM Jim Brown  wrote:
> 
>> On 7/7/2022 12:58 AM, Dave B via Elecraft wrote:
>>> Well, this is a "technical" hobby, and such technicalities are not going
>>> to go away anytime soon I suspect.  Especially in regards to the use of
>>> computers in the shack.
>> 
>> Yep. Traditionally, ham radio has been a hobby for those who what to
>> LEARN stuff. The guys who put us in space and on the moon started out
>> with ham radio and the ARRL Handbook. I'm of that generation, worked in
>> other fields, but that's how I started out!
>> 
>> 73, Jim K9YC
>> 
>> 
>> __
>> 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
>> Message delivered to ge...@w1ve.com
> __
> 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
> Message delivered to wun...@wunderwood.org 

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Wes]

Interesting discussion.  With respect to what a ham should or should not know 
about technical stuff let me say this. I spent 30 years in various positions at 
Hughes Aircraft Company. 
(https://www.hughesscgheritage.com/hughes-aircraft-history-1932-1986-transcribed-by-faith-macpherson/) 
*


We had experts on everything, however, none one of them knew everything.  There 
was a saying: "Somewhere at Hughes Aircraft there is a guy who can solve your 
problem.  Your job is to find him."


Forums such as this one are where we find the guy we need.  There should be no 
shame for looking for him.


Wes  N7WS

* If you explore this document, you can find the name Dave Evans. Dave was a ham 
and the "Around-the-world-flight" network used 7.000 and 14.000 MHz.  Ham radio 
helped start the company and it started my career at the company.



__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Gerry Hull]

LOL!

Jim and Dave,

You both have made great contribution to the hobby.

I am an ex ARRL Assistant Technical Editor, working with  Doug DeMaw,
W1FB,  and Jerry Hall,  K1TD in the Tech Department of ARRL, and  was a
contributor to the ARRL Handbook  and  QST editor.  Oh, and 47 years in the
hobby now:  I think i know a thing or two about radio, but, am always
learning -- that's what keeps it interesting.

Other than that,  I've spent 35+ years as a software engineer.

Measuring a ham's worth by what they know technically is, sad to say, a
very myopic view of the world.   Many hams are non-technical, especially
new ones.  Many come to the hobby from non-technical backgrounds, and are
usually excellent communicators. They enrich our hobby tremendously,
never the less.

>From my experience, RS-232  and CAT in general is one of the most difficult
issues hams deal with.  "Plug and Play" and the details of the intricacies
of the USB bus and different Windows device driver models are not on any
ham exam, nor should an end user ever have to mess with them.It is a
difficult challenge to solve for end uses due to the incredible complexity
of the Windows PC ecosystem.

As a contester, I know messing with interfacing CAT, Sound and Networking
are the bain of many, and consume the most time in prep for any event.
This is the nature of our hobby today.  However, there is no need to get a
CS degree to have fun.
Please keep contributing, but remember not everyone has your skills.

Judging from the number of private emails I've received, I know I'm helping
people solve their issues.

We are on the Elecraft reflector.

Bravo to the Elecraft team.  They build radios for communicators, not
computer geeks.  IMHO, the only company that really gets that.

Peace.

73,

Gerry W1VE








On Thu, Jul 7, 2022, 4:58 AM Jim Brown  wrote:

> On 7/7/2022 12:58 AM, Dave B via Elecraft wrote:
> > Well, this is a "technical" hobby, and such technicalities are not going
> > to go away anytime soon I suspect.  Especially in regards to the use of
> > computers in the shack.
>
> Yep. Traditionally, ham radio has been a hobby for those who what to
> LEARN stuff. The guys who put us in space and on the moon started out
> with ham radio and the ARRL Handbook. I'm of that generation, worked in
> other fields, but that's how I started out!
>
> 73, Jim K9YC
>
>
> __
> 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
> Message delivered to ge...@w1ve.com
__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Jim Brown]

On 7/7/2022 12:58 AM, Dave B via Elecraft wrote:
Well, this is a "technical" hobby, and such technicalities are not going 
to go away anytime soon I suspect.  Especially in regards to the use of 
computers in the shack.


Yep. Traditionally, ham radio has been a hobby for those who what to 
LEARN stuff. The guys who put us in space and on the moon started out 
with ham radio and the ARRL Handbook. I'm of that generation, worked in 
other fields, but that's how I started out!


73, Jim K9YC


__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Dave B via Elecraft]

On 06/07/2022 16:46, Gerry Hull wrote:

Great info, Dave.

    Thanks...


Might be a little technical for some users.
    Well, this is a "technical" hobby, and such technicalities are not 
going to go away anytime soon I suspect.  Especially in regards to the 
use of computers in the shack.


The #1 problem most hams have is they plug their USB-To-Serial 
adapters into different USB ports, and the COM port number changes.
    That is well known, and can be managed, especially with devices 
that have a unique "identifying feature" in their USB descriptor that 
the OS sees.   (FTDI rule the roost in that matter!)
Not only that, Windows leaves the old port number reserved much of the 
time.

    Yep, but again, that can be managed, using USBDview if nothing else.


I have an in-depth blog post which talks about this in layman's terms 
on my blog.  See 
https://blog.remote.radio/2020/11/automation-in-amateur-radio-rs-232-for.html
    Good info, but many of the hardware solutions (that do work well) 
edgeport etc are beyond the purchasing ability of many Hams. Plus, they 
rarely show up surplus or at ham-flea markets (here in the UK at least...)


    Lantronix are more well known for their LANPort devices.  Very 
good, but needs a certain level of knowledge to use, plus application 
software needs to be able to use TCP/IP connections to other devices.   
(Or tunnel a VCP over a network link.)


As explained in that blog article, there is a way to solve this 
problem.   Digi, a company who has been in the business for many 
decades, has a series of USB-to-Serial adapters
called Edgeport, from 1 to 16 ports.   The great thing about Edgeport 
devices is they have a driver and utility.  If you use that, the COM 
port number is associated with

the BOX, not where it is plugged in.

Edgeport devices are quite expensive when new, but can often be found 
on the surplus market (ebay, etc).  They have been used to do baudot 
by hams for decades.  I use them all over the place.
I have 4,8, and 16-port USB-to-serials that are surplus to my needs if 
anyone is interested.


They solve the RS-232 port issue every time!


    The simplest solution, is to (sorry) learn and understand the 
issue, then use stable and easy to uniquely enumerate devices, (FTDI is 
the only vendor that shows unique serial numbers AFIK.)


    As before, Ham Radio is a Technical Hobby by it's nature, it 
worries me sometimes when even highly respected Hams who can and have 
worked the world (i.e. are Superb operators with worked all continents 
on many bands and modes etc) seem to know very little about the 
technical aspects of the kit they own and use.


73,

Gerry Hull, *W1VE *Hancock, NH USA
CWOps #191 | YCCC | CanAm Contest Coalition | Maritime Contest Club
RadioSport Manitoba | ARRL | RAC | QCWA
ARCluster dxc.w1ve.com  | Telnet or telnet:7373 
access | RBN direct feeds


    73.
    Dave G0WBX(G8KBV)   A "no one" in Ham terms.  No awards, no WAC, 
WAB, or whatever.  But I can diagnose faults, fix and adapt stuff.






On Sun, Jul 3, 2022 at 7:04 AM Dave B via Elecraft 
 wrote:


FYI...

Windows users, can use these utilities to find out what is/was
connected
to their PC's by USB etc...

USBview:  A Microsoft (was System Internals who MS bought) tool.
The easiest way to find it is here:- https://ftdichip.com/utilities/
"Microsoft USBView - USB Connection Viewer"
There is a link to download a zipfile that contains it:-
https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
That contains a single stand-alone exe file that is the utility.
Put it
in a folder of it's own, and create a shortcut to it for your desktop.

(Also a link to a Linux version, that does work, but needs compiling
from source, and running using sudo as it needs elevated rights to
read
the running configuration files to get the information to display.)


Another similar tool is USBDview
https://www.nirsoft.net/utils/usb_devices_view.html
That shows a much more detailed list of what Windows knows about,
that
is, any USB device that was ever connected since windows was
initially
installed, regardless of if it was ever used!

You can also delete instances of old / defunct devices easily with
this
very useful tool.
(Some AV tools say it's suspect or malicious.  Use VirusTotal.com to
verify if it (or anything else) is bad, on a file by file, or webpage
basis. )


Note that if for whatever reason Windows (or Linux) re-enumerates
things, the linkage between a physical device and it's COM port
number
can (and often does!) change.  Seemingly at the will of some minor
deity
somewhere...   That of course, will break any software that
expects some
specific device to be at a specific COM port.

Windows has the means to "Fix" that.  (Known to work up to Win10,
that I
have personally tested it on.)

Re: [Elecraft] COM port problems

[Jim Rhodes]

Back when I needed a lot of serial ports I used those USB to RS232 by Digi
and they solved a lot of problems. Now most of my rigs have USB interfaces,
if not ethernet, and those issues are in the past. And the rigs have the
sound card built in and it gets more simple. Used to have 2 or 3 rigs,
several FSK interfaces, rotors and I don't remember what all run in through
RS232 ports. But the main thing was you could go in and assign any port
number available to any port. When you had  dozen or more active at once it
was a lot to keep track of.

On Wed, Jul 6, 2022, 10:48 Gerry Hull  wrote:

> Great info, Dave.   Might be a little technical for some users.
>
> The #1 problem most hams have is they plug their USB-To-Serial
> adapters into different USB ports, and the COM port number changes.
> Not only that, Windows leaves the old port number reserved much of the
> time.
>
> I have an in-depth blog post which talks about this in layman's terms on my
> blog.  See
>
> https://blog.remote.radio/2020/11/automation-in-amateur-radio-rs-232-for.html
>
> As explained in that blog article, there is a way to solve this problem.
>  Digi, a company who has been in the business for many decades, has a
> series of USB-to-Serial adapters
> called Edgeport, from 1 to 16 ports.   The great thing about Edgeport
> devices is they have a driver and utility.  If you use that, the COM port
> number is associated with
> the BOX, not where it is plugged in.
>
> Edgeport devices are quite expensive when new, but can often be found on
> the surplus market (ebay, etc).   They have been used to do baudot by hams
> for decades.  I use them all over the place.
> I have 4,8, and 16-port USB-to-serials that are surplus to my needs if
> anyone is interested.
>
> They solve the RS-232 port issue every time!
>
> 73,
>
> Gerry Hull, *W1VE  *Hancock, NH USA
> CWOps #191 | YCCC | CanAm Contest Coalition | Maritime Contest Club
> RadioSport Manitoba | ARRL | RAC | QCWA
> ARCluster dxc.w1ve.com | Telnet or telnet:7373 access | RBN direct feeds
>
>
>
> On Sun, Jul 3, 2022 at 7:04 AM Dave B via Elecraft <
> elecraft@mailman.qth.net>
> wrote:
>
> > FYI...
> >
> > Windows users, can use these utilities to find out what is/was connected
> > to their PC's by USB etc...
> >
> > USBview:  A Microsoft (was System Internals who MS bought) tool.
> > The easiest way to find it is here:- https://ftdichip.com/utilities/
> > "Microsoft USBView - USB Connection Viewer"
> > There is a link to download a zipfile that contains it:-
> > https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
> > That contains a single stand-alone exe file that is the utility. Put it
> > in a folder of it's own, and create a shortcut to it for your desktop.
> >
> > (Also a link to a Linux version, that does work, but needs compiling
> > from source, and running using sudo as it needs elevated rights to read
> > the running configuration files to get the information to display.)
> >
> >
> > Another similar tool is USBDview
> > https://www.nirsoft.net/utils/usb_devices_view.html
> > That shows a much more detailed list of what Windows knows about, that
> > is, any USB device that was ever connected since windows was initially
> > installed, regardless of if it was ever used!
> >
> > You can also delete instances of old / defunct devices easily with this
> > very useful tool.
> > (Some AV tools say it's suspect or malicious.  Use VirusTotal.com to
> > verify if it (or anything else) is bad, on a file by file, or webpage
> > basis. )
> >
> >
> > Note that if for whatever reason Windows (or Linux) re-enumerates
> > things, the linkage between a physical device and it's COM port number
> > can (and often does!) change.  Seemingly at the will of some minor deity
> > somewhere...   That of course, will break any software that expects some
> > specific device to be at a specific COM port.
> >
> > Windows has the means to "Fix" that.  (Known to work up to Win10, that I
> > have personally tested it on.)
> > Find those details here:-
> > https://sourceforge.net/p/fldigi/wiki/windows_com_howto/
> > I wrote much of that after hours of "fun" some years ago...   As above,
> > it works well with Win-10.
> >
> >
> > For Linux users, look up and explore the world of "udev rules". But...
> > They are only really easy to setup, if a USB device has a unique
> > "something" in it's USB descriptor, that the OS uses to identify it.
> > Such as a Serial Number.   FTDI devices have unique sn's, but Prolific,
> > SiLabs and others sadly do not.  So, it gets funky if you have several
> > of the same type of device that all "look the same" to the OS.
> >
> > (Newer genuine FTDI devices also have the ability to have that serial
> > number (and some other settings) re-programmed!   Fakes seem to take the
> > reprogramming, but the new data does not "stick".  Don't ask how I found
> > that out!)
> >
> > However, you can use the "connection path" between the OS and the
> > Device, as a deciding factor, but then you 

Re: [Elecraft] COM port problems

[Randy Farmer]

I've used a few of the Gearmo USB to RS-232 adapters, and they also seem 
to hold their COM port assignments constant (on any one given machine, 
of course). They just use the standard FTDI chipset with no special 
drivers. Not sure how they do it, but it works.


73...
Randy, W8FN

On 7/6/2022 11:46 AM, Gerry Hull wrote:

As explained in that blog article, there is a way to solve this problem.
  Digi, a company who has been in the business for many decades, has a
series of USB-to-Serial adapters
called Edgeport, from 1 to 16 ports.   The great thing about Edgeport
devices is they have a driver and utility.  If you use that, the COM port
number is associated with
the BOX, not where it is plugged in

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Gerry Hull]

Great info, Dave.   Might be a little technical for some users.

The #1 problem most hams have is they plug their USB-To-Serial
adapters into different USB ports, and the COM port number changes.
Not only that, Windows leaves the old port number reserved much of the time.

I have an in-depth blog post which talks about this in layman's terms on my
blog.  See
https://blog.remote.radio/2020/11/automation-in-amateur-radio-rs-232-for.html

As explained in that blog article, there is a way to solve this problem.
 Digi, a company who has been in the business for many decades, has a
series of USB-to-Serial adapters
called Edgeport, from 1 to 16 ports.   The great thing about Edgeport
devices is they have a driver and utility.  If you use that, the COM port
number is associated with
the BOX, not where it is plugged in.

Edgeport devices are quite expensive when new, but can often be found on
the surplus market (ebay, etc).   They have been used to do baudot by hams
for decades.  I use them all over the place.
I have 4,8, and 16-port USB-to-serials that are surplus to my needs if
anyone is interested.

They solve the RS-232 port issue every time!

73,

Gerry Hull, *W1VE  *Hancock, NH USA
CWOps #191 | YCCC | CanAm Contest Coalition | Maritime Contest Club
RadioSport Manitoba | ARRL | RAC | QCWA
ARCluster dxc.w1ve.com | Telnet or telnet:7373 access | RBN direct feeds



On Sun, Jul 3, 2022 at 7:04 AM Dave B via Elecraft 
wrote:

> FYI...
>
> Windows users, can use these utilities to find out what is/was connected
> to their PC's by USB etc...
>
> USBview:  A Microsoft (was System Internals who MS bought) tool.
> The easiest way to find it is here:- https://ftdichip.com/utilities/
> "Microsoft USBView - USB Connection Viewer"
> There is a link to download a zipfile that contains it:-
> https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
> That contains a single stand-alone exe file that is the utility. Put it
> in a folder of it's own, and create a shortcut to it for your desktop.
>
> (Also a link to a Linux version, that does work, but needs compiling
> from source, and running using sudo as it needs elevated rights to read
> the running configuration files to get the information to display.)
>
>
> Another similar tool is USBDview
> https://www.nirsoft.net/utils/usb_devices_view.html
> That shows a much more detailed list of what Windows knows about, that
> is, any USB device that was ever connected since windows was initially
> installed, regardless of if it was ever used!
>
> You can also delete instances of old / defunct devices easily with this
> very useful tool.
> (Some AV tools say it's suspect or malicious.  Use VirusTotal.com to
> verify if it (or anything else) is bad, on a file by file, or webpage
> basis. )
>
>
> Note that if for whatever reason Windows (or Linux) re-enumerates
> things, the linkage between a physical device and it's COM port number
> can (and often does!) change.  Seemingly at the will of some minor deity
> somewhere...   That of course, will break any software that expects some
> specific device to be at a specific COM port.
>
> Windows has the means to "Fix" that.  (Known to work up to Win10, that I
> have personally tested it on.)
> Find those details here:-
> https://sourceforge.net/p/fldigi/wiki/windows_com_howto/
> I wrote much of that after hours of "fun" some years ago...   As above,
> it works well with Win-10.
>
>
> For Linux users, look up and explore the world of "udev rules". But...
> They are only really easy to setup, if a USB device has a unique
> "something" in it's USB descriptor, that the OS uses to identify it.
> Such as a Serial Number.   FTDI devices have unique sn's, but Prolific,
> SiLabs and others sadly do not.  So, it gets funky if you have several
> of the same type of device that all "look the same" to the OS.
>
> (Newer genuine FTDI devices also have the ability to have that serial
> number (and some other settings) re-programmed!   Fakes seem to take the
> reprogramming, but the new data does not "stick".  Don't ask how I found
> that out!)
>
> However, you can use the "connection path" between the OS and the
> Device, as a deciding factor, but then you are forced into hooking
> everything up "EXACTLY" the same each time.  (Hub's and all...) But it
> does work.
>
> Using them, you create "symbolic links" to the actual port used, so for
> example my VHF radio appears as /dev/ttyFT736  Regardless of which hole
> I connect it's associated FTDI serial adapter to on the PC (or via any
> hubs!)  Or what /dev/ttyUSB* the OS re-assigns it to if things are
> re-enumerated for whatever reason.)
>
> For example, this is the rule for my ancient FT-736
>
> #FT-736r
> SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"
>
> Flrig and most other software both accept symlinks and work well.
>
> (For the odd software title that insists on using the full /dev/ttyUSBx
> for example, they often store their settings in a file that can often be
> edited with 

Re: [Elecraft] COM port problems

[Bill Frantz]

I have not had the problem of devices “moving” on the Mac. I think the Mac uses 
the FDTI serial number to keep them straight. When I was using a RS-232 
protocol analyzer on to chase a problem, I had 4 Elecraft FTDI RS-232 <—> USB 
cables hooked up. Two for the two directions of the analyzer, one for the K3 
acting as test machine, and 1 for a KX3 acting as the other end of the RF link. 
The Mac always seemed to keep them straight, even when I plugged them into 
different USB sockets on hubs etc.

I’ve always wondered why Microsoft hasn’t fixed this problem. And I sympathize 
with my friends who use Windows.

73 Bill AE6JV

> On Jul 3, 2022, at 06:59:59, Dave B via Elecraft  
> wrote:
> 
> I have zero experience of Apple Mac's.  But they use a custom version of BSD 
> as their OS, that is more like Unix than Linux.  So it is likely some if not 
> all of the above could work on them too. If Apple let you dig that deep and 
> meddle…



__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Peter Dougherty (W2IRT)]

Thanks for this. I will try to see what the COM devices are supposedly 
connected to when it's in failure mode but it's all very cryptic.

I have already deleted old phantom devices during the first phase of 
troubleshooting, as well as deleted all unnecessary software from the system. 
The problem of *ALL* COM ports being shown as busy upon reboot persists.

 - pjd

-Original Message-
From: elecraft-boun...@mailman.qth.net  On 
Behalf Of Dave B via Elecraft
Sent: Sunday, July 3, 2022 7:00 AM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] COM port problems

FYI...

Windows users, can use these utilities to find out what is/was connected to 
their PC's by USB etc...

USBview:  A Microsoft (was System Internals who MS bought) tool.
The easiest way to find it is here:- https://ftdichip.com/utilities/ "Microsoft 
USBView - USB Connection Viewer"
There is a link to download a zipfile that contains it:- 
https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
That contains a single stand-alone exe file that is the utility. Put it in a 
folder of it's own, and create a shortcut to it for your desktop.

(Also a link to a Linux version, that does work, but needs compiling from 
source, and running using sudo as it needs elevated rights to read the running 
configuration files to get the information to display.)


Another similar tool is USBDview
https://www.nirsoft.net/utils/usb_devices_view.html
That shows a much more detailed list of what Windows knows about, that is, any 
USB device that was ever connected since windows was initially installed, 
regardless of if it was ever used!

You can also delete instances of old / defunct devices easily with this very 
useful tool.
(Some AV tools say it's suspect or malicious.  Use VirusTotal.com to verify if 
it (or anything else) is bad, on a file by file, or webpage basis. )


Note that if for whatever reason Windows (or Linux) re-enumerates things, the 
linkage between a physical device and it's COM port number can (and often 
does!) change.  Seemingly at the will of some minor deity somewhere...   That 
of course, will break any software that expects some specific device to be at a 
specific COM port.

Windows has the means to "Fix" that.  (Known to work up to Win10, that I have 
personally tested it on.) Find those details here:- 
https://sourceforge.net/p/fldigi/wiki/windows_com_howto/
I wrote much of that after hours of "fun" some years ago...   As above, it 
works well with Win-10.


For Linux users, look up and explore the world of "udev rules". But...
They are only really easy to setup, if a USB device has a unique "something" in 
it's USB descriptor, that the OS uses to identify it. Such as a Serial Number.  
 FTDI devices have unique sn's, but Prolific, SiLabs and others sadly do not.  
So, it gets funky if you have several of the same type of device that all "look 
the same" to the OS.

(Newer genuine FTDI devices also have the ability to have that serial number 
(and some other settings) re-programmed!   Fakes seem to take the 
reprogramming, but the new data does not "stick".  Don't ask how I found that 
out!)

However, you can use the "connection path" between the OS and the Device, as a 
deciding factor, but then you are forced into hooking everything up "EXACTLY" 
the same each time.  (Hub's and all...) But it does work.

Using them, you create "symbolic links" to the actual port used, so for example 
my VHF radio appears as /dev/ttyFT736  Regardless of which hole I connect it's 
associated FTDI serial adapter to on the PC (or via any
hubs!)  Or what /dev/ttyUSB* the OS re-assigns it to if things are 
re-enumerated for whatever reason.)

For example, this is the rule for my ancient FT-736

#FT-736r
SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"

Flrig and most other software both accept symlinks and work well.

(For the odd software title that insists on using the full /dev/ttyUSBx for 
example, they often store their settings in a file that can often be edited 
with a text editor, where you can in effect force-feed it the symlink.   The 
fun part is finding where that is stored!)

The exact details of how to use udev rules are way to much for this list, but 
as usual, there are many websites that can furnish such info, plus some 
examples.   Has to be said though, different "flavors" of Linux, often store 
such rules in subtly different places to others.


I have zero experience of Apple Mac's.  But they use a custom version of BSD as 
their OS, that is more like Unix than Linux.  So it is likely some if not all 
of the above could work on them too. If Apple let you dig that deep and 
meddle...


Hope some of the above helps, and or gives people some ideas how to tame things.

73.
Dave G0WBX(G8KBV)

--
Created on and sent from a Unix like PC running and using free and open

Re: [Elecraft] COM port problems

[Dave B via Elecraft]

FYI...

Windows users, can use these utilities to find out what is/was connected 
to their PC's by USB etc...


USBview:  A Microsoft (was System Internals who MS bought) tool.
The easiest way to find it is here:- https://ftdichip.com/utilities/  
"Microsoft USBView - USB Connection Viewer"
There is a link to download a zipfile that contains it:- 
https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
That contains a single stand-alone exe file that is the utility. Put it 
in a folder of it's own, and create a shortcut to it for your desktop.


(Also a link to a Linux version, that does work, but needs compiling 
from source, and running using sudo as it needs elevated rights to read 
the running configuration files to get the information to display.)



Another similar tool is USBDview 
https://www.nirsoft.net/utils/usb_devices_view.html
That shows a much more detailed list of what Windows knows about, that 
is, any USB device that was ever connected since windows was initially 
installed, regardless of if it was ever used!


You can also delete instances of old / defunct devices easily with this 
very useful tool.
(Some AV tools say it's suspect or malicious.  Use VirusTotal.com to 
verify if it (or anything else) is bad, on a file by file, or webpage 
basis. )



Note that if for whatever reason Windows (or Linux) re-enumerates 
things, the linkage between a physical device and it's COM port number 
can (and often does!) change.  Seemingly at the will of some minor deity 
somewhere...   That of course, will break any software that expects some 
specific device to be at a specific COM port.


Windows has the means to "Fix" that.  (Known to work up to Win10, that I 
have personally tested it on.)
Find those details here:- 
https://sourceforge.net/p/fldigi/wiki/windows_com_howto/
I wrote much of that after hours of "fun" some years ago...   As above, 
it works well with Win-10.



For Linux users, look up and explore the world of "udev rules". But...
They are only really easy to setup, if a USB device has a unique 
"something" in it's USB descriptor, that the OS uses to identify it.  
Such as a Serial Number.   FTDI devices have unique sn's, but Prolific, 
SiLabs and others sadly do not.  So, it gets funky if you have several 
of the same type of device that all "look the same" to the OS.


(Newer genuine FTDI devices also have the ability to have that serial 
number (and some other settings) re-programmed!   Fakes seem to take the 
reprogramming, but the new data does not "stick".  Don't ask how I found 
that out!)


However, you can use the "connection path" between the OS and the 
Device, as a deciding factor, but then you are forced into hooking 
everything up "EXACTLY" the same each time.  (Hub's and all...) But it 
does work.


Using them, you create "symbolic links" to the actual port used, so for 
example my VHF radio appears as /dev/ttyFT736  Regardless of which hole 
I connect it's associated FTDI serial adapter to on the PC (or via any 
hubs!)  Or what /dev/ttyUSB* the OS re-assigns it to if things are 
re-enumerated for whatever reason.)


For example, this is the rule for my ancient FT-736

#FT-736r
SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"

Flrig and most other software both accept symlinks and work well.

(For the odd software title that insists on using the full /dev/ttyUSBx 
for example, they often store their settings in a file that can often be 
edited with a text editor, where you can in effect force-feed it the 
symlink.   The fun part is finding where that is stored!)


The exact details of how to use udev rules are way to much for this 
list, but as usual, there are many websites that can furnish such info, 
plus some examples.   Has to be said though, different "flavors" of 
Linux, often store such rules in subtly different places to others.



I have zero experience of Apple Mac's.  But they use a custom version of 
BSD as their OS, that is more like Unix than Linux.  So it is likely 
some if not all of the above could work on them too. If Apple let you 
dig that deep and meddle...



Hope some of the above helps, and or gives people some ideas how to tame 
things.


73.
Dave G0WBX(G8KBV)

--
Created on and sent from a Unix like PC running and using free and open source 
software:
__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] Com Port Problems

[Peter Dougherty (W2IRT)]

Yes, that is likely my next step, an in-place reinstall. I do not have the time 
to fully reconfigure the system so I can't do a bare metal install job. It's my 
work computer as well as my ham computer, and work MUST take precedence on it. 

 - pjd

-Original Message-
From: Lyn Norstad  
Sent: Saturday, July 2, 2022 3:01 PM
To: 'Peter Dougherty (W2IRT)' ; 'Wilson Lamb' 
; 'elecraft' 
Subject: RE: [Elecraft] Com Port Problems

Peter -

If you're sure that the problem is not what we addressed, then I suggest you 
reinstall Windows 11.  Presumably you're using the " Pro " edition.  If not, 
switch to that one.  The latest build is # 22000.778 released on 06/23/2022 
(last week).

Instructions here:

https://support.microsoft.com/en-us/topic/june-23-2022-kb5014668-os-build-22000-778-preview-2b5f1da6-d602-48b4-b443-96b460e3c38d

73
Lyn, W0LEN

-Original Message-
From: elecraft-boun...@mailman.qth.net 
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty (W2IRT)
Sent: Friday, July 01, 2022 5:22 PM
To: 'Wilson Lamb'; 'elecraft'
Subject: Re: [Elecraft] Com Port Problems

The problem isn't the Elecraft radio, or the COM ports, it's a defect of some 
nature within Windows 11 that has suddenly manifested itself. I've tried all 
the usual troubleshooting problems and no-go, and even a Microsoft 2nd Level 
guy spent three hours with me on the phone and did it all again and still 
couldn’t' find it. Making things work "once" isnt' too difficult. Making 
everything work 100% reliably *repeatedly*, as it has been for years, is the 
problem.

I really hate the fact that it took SO long for ham radio manufacturers to move 
away from RS-232 to pure USB, and only recently to TCP/IP, which is the correct 
way of doing things in my opinion.

 - pjd

-Original Message-
From: elecraft-boun...@mailman.qth.net  On 
Behalf Of Wilson Lamb via Elecraft
Sent: Friday, July 1, 2022 2:18 PM
To: elecraft 
Subject: [Elecraft] Com Port Problems


Please read my rant about Ham Qualifications and Technology. 
We are at the mercy of MANY programmers and "software engineers." 
The operating system people have no resistance to making things steadily more 
obscure and complicated. 
They don't know or care what the programmers of our many programs are doing and 
have little incentive to find out. 
The programmers typically have only a nodding acquaintance with what the 
Operating System really does and don't have time/ability to find out. 
WE are way out on a thin limb that gets more and more likely to break or sag 
down to the ground. 
All the people mentioned above are whittling away at the limb, each 
contributing to its weakness/impending breakage, and none have much incentive 
to help US. 
I really hope you find it and I guarantee, if you do, there will be a gotcha 
that someone will tell you should have seen and that will make you feel 
inadequate!  In this area, we are all inadequate! 
I know this doesn't help.  It's meant as sympathy. 
I have been building and using computers since the 50s, when I helped build one 
that used relays and I still have NO interest in software except to say what it 
should do, at which I've been pretty successful. 
Good luck and remember, there are knobs on the radio and they will probably 
work for you, since the software in the radio has likely had a few years to get 
sorted out and the worst bugs found. 
WL
__
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 Message 
delivered to li...@w2irt.net 

__
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 Message 
delivered to l...@lnainc.com 


__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] Com Port Problems

[Lyn Norstad]

Peter -

If you're sure that the problem is not what we addressed, then I suggest you 
reinstall Windows 11.  Presumably you're using the " Pro " edition.  If not, 
switch to that one.  The latest build is # 22000.778 released on 06/23/2022 
(last week).

Instructions here:

https://support.microsoft.com/en-us/topic/june-23-2022-kb5014668-os-build-22000-778-preview-2b5f1da6-d602-48b4-b443-96b460e3c38d

73
Lyn, W0LEN

-Original Message-
From: elecraft-boun...@mailman.qth.net 
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty (W2IRT)
Sent: Friday, July 01, 2022 5:22 PM
To: 'Wilson Lamb'; 'elecraft'
Subject: Re: [Elecraft] Com Port Problems

The problem isn't the Elecraft radio, or the COM ports, it's a defect of some 
nature within Windows 11 that has suddenly manifested itself. I've tried all 
the usual troubleshooting problems and no-go, and even a Microsoft 2nd Level 
guy spent three hours with me on the phone and did it all again and still 
couldn’t' find it. Making things work "once" isnt' too difficult. Making 
everything work 100% reliably *repeatedly*, as it has been for years, is the 
problem.

I really hate the fact that it took SO long for ham radio manufacturers to move 
away from RS-232 to pure USB, and only recently to TCP/IP, which is the correct 
way of doing things in my opinion.

 - pjd

-Original Message-
From: elecraft-boun...@mailman.qth.net  On 
Behalf Of Wilson Lamb via Elecraft
Sent: Friday, July 1, 2022 2:18 PM
To: elecraft 
Subject: [Elecraft] Com Port Problems


Please read my rant about Ham Qualifications and Technology. 
We are at the mercy of MANY programmers and "software engineers." 
The operating system people have no resistance to making things steadily more 
obscure and complicated. 
They don't know or care what the programmers of our many programs are doing and 
have little incentive to find out. 
The programmers typically have only a nodding acquaintance with what the 
Operating System really does and don't have time/ability to find out. 
WE are way out on a thin limb that gets more and more likely to break or sag 
down to the ground. 
All the people mentioned above are whittling away at the limb, each 
contributing to its weakness/impending breakage, and none have much incentive 
to help US. 
I really hope you find it and I guarantee, if you do, there will be a gotcha 
that someone will tell you should have seen and that will make you feel 
inadequate!  In this area, we are all inadequate! 
I know this doesn't help.  It's meant as sympathy. 
I have been building and using computers since the 50s, when I helped build one 
that used relays and I still have NO interest in software except to say what it 
should do, at which I've been pretty successful. 
Good luck and remember, there are knobs on the radio and they will probably 
work for you, since the software in the radio has likely had a few years to get 
sorted out and the worst bugs found. 
WL
__
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 Message 
delivered to li...@w2irt.net 

__
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
Message delivered to l...@lnainc.com 

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Fred Jensen]

Thank you Mitch!!  The procedure I have been using and wrote about seems 
to work roughly 50% of the time.  Now I think I know why [:=)


73,

Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

Mitch Wolfson wrote on 7/1/2022 9:23 PM:

Peter,

Skip is on to what you need to do, but that method won't show
everything. What you need to do is the following:

- Open up a DOS command window by clicking on the start button, then on
"run" and enter "cmd" and hit the enter button
- Copy and paste the following into the command line:  set
devmgr_show_nonpresent_devices=1
- Then copy and paste the following, or manually start Device Manager
like Skip says:  \windows\system32\devmgmt.msc
- Now go to the view menu and click on show hidden devices and you will
see everything that you ever installed
- Now you can delete everything that is in conflict and follow Skip's
instructions

I also have a nifty script that nukes all installed COM port drivers at
once as a worst case scenario. If you need that, send me a direct mail.
I don't read these postings all the time.

73,
Mitch  DJ0QN / K7DX

--
Mitch Wolfson DJ0QN / K7DX
1494 Serrano Cir, Naples, FL 34105
USA: Home: +1-239-221-9600 - Mobile: +1-424-288-9171
Germany: Home: +49 89 32152700 - Mobile/WhatsApp: +49 172 8374436

On 01.07.2022 19:07, Fred Jensen wrote:

Peter:

1.  Open Control Panel and click on Hardware/Sound-->Device
Mangler-->Ports

2.  In the View menu, click on Show Hidden Devices

If there are any, they will appear in the Ports display but grayed
out.  Delete them, close everything, reboot, and try again. Windows
will occasionally, and without notice, leave a previous device
enumerated even after it is removed.  It shows up as unavailable, or
in-use to a real device.

May not be your problem, but an easy fix.  Best to remove all USB
cables before the reboot, then insert them one at a time while
watching the Ports display


73,

Fred ["Skip"] K6DGW #142
Sparks NV DM09dn
Washoe County

Peter Dougherty (W2IRT) wrote on 7/1/2022 3:17 PM:

The issue is far deeper than this. None of the COM ports work
normally after
starting the system. Occasionally the radio connects to the software
normally, other times it doesn't. If I have it working with N1MM,
close down
N1MM and try to start Commander (DX Labs) it won't work initially,
but if I
try it 3 or 4 times in a row it will connect normally.

Ditto with my two rotors. Those are the only serial ports in my
system. The
K3s, my 6m rotor (Rotor-EZ board in the controller box) and a Green
Heron
RT-20 (serial-to-USB, not pure USB like the newer RT-21). For whatever
reason, there is *something* holding all the installed/configured COM
ports
open and unavailable. I cannot find that "something."

  - pjd












--
This email has been checked for viruses by AVG.
https://www.avg.com
__
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
Message delivered to arch...@mail-archive.com 

[Elecraft] COM port problems

[Bob McGraw]

I suggest you perform a RESTORE function from a previous file dated 
before the problem occurred.   Or if you have a back-up system, go back 
to a known working configuration.   (You have regular computer back ups 
don't you?)


Using the K3 Utility, if communicates correctly with the radio, then 
start with a single application such as WSJT-X or FLDIGI. Don't use or 
launch  any other control or logging applications. Just run WSJT-X or 
FLDIGI direct and stand-a-lone.   If that works then you perhaps would 
be lead to believe that the configuration between the control 
application and logging application are suspect.


The approach is to launch and run only one application at a time.  If it 
doesn't work, then debug and find out why and get it working before 
moving on.  Too many variables may take eons to sort out.


73

Bob, K4TAX


On 7/1/2022 5:27 PM, elecraft-requ...@mailman.qth.net wrote:

-Original Message-
From:elecraft-boun...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty
(W2IRT)
Sent: Thursday, June 30, 2022 12:28 AM
To: 'George Thornton';Elecraft@mailman.qth.net
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



--
IF ONE EXPECTS COMPUTERS AND TECHNOLOGY TO SOLVE THEIR PROBLEMS,
ONE DOESN'T UNDERSTAND COMPUTERS AND TECHNOLOGY
AND ONE DOESN'T UNDERSTAND THEIR PROBLEMS."


__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Fred Jensen]

Peter:

1.  Open Control Panel and click on Hardware/Sound-->Device Mangler-->Ports

2.  In the View menu, click on Show Hidden Devices

If there are any, they will appear in the Ports display but grayed out.  
Delete them, close everything, reboot, and try again.  Windows will 
occasionally, and without notice, leave a previous device enumerated 
even after it is removed.  It shows up as unavailable, or in-use to a 
real device.


May not be your problem, but an easy fix.  Best to remove all USB cables 
before the reboot, then insert them one at a time while watching the 
Ports display



73,

Fred ["Skip"] K6DGW #142
Sparks NV DM09dn
Washoe County

Peter Dougherty (W2IRT) wrote on 7/1/2022 3:17 PM:

The issue is far deeper than this. None of the COM ports work normally after
starting the system. Occasionally the radio connects to the software
normally, other times it doesn't. If I have it working with N1MM, close down
N1MM and try to start Commander (DX Labs) it won't work initially, but if I
try it 3 or 4 times in a row it will connect normally.

Ditto with my two rotors. Those are the only serial ports in my system. The
K3s, my 6m rotor (Rotor-EZ board in the controller box) and a Green Heron
RT-20 (serial-to-USB, not pure USB like the newer RT-21). For whatever
reason, there is *something* holding all the installed/configured COM ports
open and unavailable. I cannot find that "something."

  - pjd






--
This email has been checked for viruses by AVG.
https://www.avg.com
__
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
Message delivered to arch...@mail-archive.com 

[Elecraft] COM port problems

[Andy Durbin]

"I cannot find that "something.""

That something is likely Microsoft Windows.  I declined Win 10 and never 
regretted that decision.  It seems Win 11 is even worse than Win 10.

My station computer in Win 8.1 64 bit.  It never changes COM port assignments.  
I have other XP Sp3 computers that perform useful functions but I keep them off 
the internet.

Andy, k3wyc
__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] Com Port Problems

[Peter Dougherty (W2IRT)]

The problem isn't the Elecraft radio, or the COM ports, it's a defect of some 
nature within Windows 11 that has suddenly manifested itself. I've tried all 
the usual troubleshooting problems and no-go, and even a Microsoft 2nd Level 
guy spent three hours with me on the phone and did it all again and still 
couldn’t' find it. Making things work "once" isnt' too difficult. Making 
everything work 100% reliably *repeatedly*, as it has been for years, is the 
problem.

I really hate the fact that it took SO long for ham radio manufacturers to move 
away from RS-232 to pure USB, and only recently to TCP/IP, which is the correct 
way of doing things in my opinion.

 - pjd

-Original Message-
From: elecraft-boun...@mailman.qth.net  On 
Behalf Of Wilson Lamb via Elecraft
Sent: Friday, July 1, 2022 2:18 PM
To: elecraft 
Subject: [Elecraft] Com Port Problems


Please read my rant about Ham Qualifications and Technology. 
We are at the mercy of MANY programmers and "software engineers." 
The operating system people have no resistance to making things steadily more 
obscure and complicated. 
They don't know or care what the programmers of our many programs are doing and 
have little incentive to find out. 
The programmers typically have only a nodding acquaintance with what the 
Operating System really does and don't have time/ability to find out. 
WE are way out on a thin limb that gets more and more likely to break or sag 
down to the ground. 
All the people mentioned above are whittling away at the limb, each 
contributing to its weakness/impending breakage, and none have much incentive 
to help US. 
I really hope you find it and I guarantee, if you do, there will be a gotcha 
that someone will tell you should have seen and that will make you feel 
inadequate!  In this area, we are all inadequate! 
I know this doesn't help.  It's meant as sympathy. 
I have been building and using computers since the 50s, when I helped build one 
that used relays and I still have NO interest in software except to say what it 
should do, at which I've been pretty successful. 
Good luck and remember, there are knobs on the radio and they will probably 
work for you, since the software in the radio has likely had a few years to get 
sorted out and the worst bugs found. 
WL
__
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 Message 
delivered to li...@w2irt.net 

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Peter Dougherty (W2IRT)]

The issue is far deeper than this. None of the COM ports work normally after
starting the system. Occasionally the radio connects to the software
normally, other times it doesn't. If I have it working with N1MM, close down
N1MM and try to start Commander (DX Labs) it won't work initially, but if I
try it 3 or 4 times in a row it will connect normally.

Ditto with my two rotors. Those are the only serial ports in my system. The
K3s, my 6m rotor (Rotor-EZ board in the controller box) and a Green Heron
RT-20 (serial-to-USB, not pure USB like the newer RT-21). For whatever
reason, there is *something* holding all the installed/configured COM ports
open and unavailable. I cannot find that "something."

 - pjd

-Original Message-
From: elecraft-boun...@mailman.qth.net  On
Behalf Of Geoffrey Feldman
Sent: Friday, July 1, 2022 1:23 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] COM port problems

These is nothing unique about the Elecraft serial cable except possibly the
radio side connector.  Basically it's a USB to RS232 Ground/transmit/Receive
cable. Anyone who understands USB com ports can help you.  They don't need
to know radio.  They should understand what I wrote here.

For USB COM port problems (with anything, including these).
Run DEVMGR (I do this by entering that in the search bar) In Devmgr "View"
menu , click / check "Show Hidden Devices"
Look in the list for "Ports(COM & LPT) Expand that to the sub list You will
see a list of ports there in the sub list.  Some are grayed out, those are
not connected.
Plug in your Elecraft serial cable. Is there a change?  You should see  a
grayed out one now dark (enabled) (as COM 1 is)  That is the number of the
Elecraft port.
OR ... a new one just appears. This sometimes happens. That is the new
number of the Elecraft port. (This is a likely outcome).

Make a note of anything in devmgr list, this may help Elecraft help you but
I expect you will have figured it out with the above steps.

If this does not work, try other USB ports on your computer with the above
procedure.

If this does not work, try the Elecraft cable on a friends computer (the
driver for Elecraft is pretty standard you don't need the radio to check the
cable).  If this does not work, you need a Elecraft serial cable.  You can
also look in the cable and make one.  There are USB to RS232 cables you can
change the connector to match the cable description in the manual.  Others
available may have the same connector but TX and RX are reversed.  Some are
already the same as elecraft.

W1GCF
Geoff

__
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 Message
delivered to li...@w2irt.net 

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Lyn Norstad]

Peter –

 

From what you’re saying, it doesn’t sound like the COM ports were properly 
reassigned.

 

You need to change them ALL to a number starting with 21 and going UP.

 

Then make sure that the software that is accessing the device connected to that 
port is properly reconfigured to look for the NEW port number.

 

The cold reboot(s) likely would actually cause the problem to manifest itself, 
again and again – just as stopping and restarting the affected apps is doing.

 

Lyn

 

From: Peter Dougherty (W2IRT) [mailto:li...@w2irt.net] 
Sent: Thursday, June 30, 2022 8:31 PM
To: l...@lnainc.com; 'Julia Tuttle'
Cc: 'George Thornton'; 'Elecraft'
Subject: RE: [Elecraft] COM port problems

 

Reassigning port numbers did not solve the problem, and I did try that as one 
of the first steps in troubleshooting.

With one day’s work under my belt here’s where the situation lies as of tonight.

 

1.  After a cold reboot, the first attempt to launch either CI-V Commander 
(DX Labs rig interface) or N1MM Logger + may or may not capture the COM5 port 
used for CAT control (which was briefly changed to COM8 then changed back after 
finding no change).
2.  Launching either the old version of N1MM Rotor (v12.11) or the current 
.NET version, there’s about a very slim chance that it will work, but the usual 
result is that on attempting to start the rotor software it indicates both 
rotor com ports (COM1 and COM3) are already in use, and any attempt to invoke a 
direction command generates an error message (8018, IIRC) stating the function 
can only work if a port is open.
3.  Using the DX Lab “DX View” software, which interfaces with the rotor 
control software, if I repeatedly enable/disable the rotor control tick box, it 
**MAY** come back, and will keep working until the program is closed.
4.  If CAT control is in fact established, whether through N1MM or 
Commander, it will remain active until the program is closed. Once closed, 
either reopening it or opening the other control software will result in either 
program not being able to see the radio (i.e. the port remains locked out). 
Note than if it is Commander that is closed and N1MM does not see the radio at 
first, if I hit the “Reset Radio” bar in the bandmap several times it does seem 
to come back and start working again.
5.  Every other function of the PC is working the same as it always has, 
and once a COM port feature is working it remains working flawlessly.
6.  Troubleshooting has involved using Process Explorer to see if any 
devices are holding a port open when the problem is occurring, and none appear 
to be doing so. Phantom COM ports were removed, all USB devices were set to fix 
the issue of stopping the device for power saving (I hoped that one would work, 
but it didn’t), and all USB Serial drivers were deleted and allowed to 
reinstall themselves upon reboot. The results were identical.

 

In short, it appears to me that there is SOMETHING within Windows 11 that has 
changed somehow, and is locking serial ports on its own, with no easy way to 
release them.

 

- pjd

 

From: Lyn Norstad  
Sent: Thursday, June 30, 2022 8:46 PM
To: 'Julia Tuttle' 
Cc: 'Peter Dougherty (W2IRT)' ; 'George Thornton' 
; 'Elecraft' 
Subject: RE: [Elecraft] COM port problems

 

Julie –

 

I can look for it … but I don’t believe it was in an official MSFT document.  
Nevertheless, it has been going on for a couple years.  It seems to affect 
almost every ham using Win 10 sooner or later.

 

My understanding is that one or more specific Windows 10 Pro 64 updates 
reassigned COM ports in order to prevent a potential hacker from accessing the 
system.  It may have been related to the presence of specific software 
installed on the system.

 

In any event, the fix I mentioned does indeed work and ends the problem.

 

George may have other issues, since he’s already tried this

 

73

Lyn, W0LEN

 

 

From: Julia Tuttle [mailto:ju...@juliatuttle.net] 
Sent: Thursday, June 30, 2022 2:47 PM
To: l...@lnainc.com
Cc: Peter Dougherty (W2IRT); George Thornton; Elecraft
Subject: Re: [Elecraft] COM port problems

 

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  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: elecraft-boun...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Doug

[Elecraft] COM port problems

[Andy Durbin]

"These is nothing unique about the Elecraft serial cable except possibly the 
radio side connector.  Basically it's a USB to RS232 Ground/transmit/Receive 
cable."

I think you may find that some Elecraft serial cables use TTL levels and are 
not RS-232 compliant.  Doesn't matter if used for intended purpose.

Andy, k3wyc
__
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
Message delivered to arch...@mail-archive.com 

[Elecraft] Com Port Problems

[Wilson Lamb via Elecraft]

Please read my rant about Ham Qualifications and Technology. 
We are at the mercy of MANY programmers and "software engineers." 
The operating system people have no resistance to making things steadily more 
obscure and complicated. 
They don't know or care what the programmers of our many programs are doing and 
have little incentive to find out. 
The programmers typically have only a nodding acquaintance with what the 
Operating System really does and don't have time/ability to find out. 
WE are way out on a thin limb that gets more and more likely to break or sag 
down to the ground. 
All the people mentioned above are whittling away at the limb, each 
contributing to its weakness/impending breakage, and none have much incentive 
to help US. 
I really hope you find it and I guarantee, if you do, there will be a gotcha 
that someone will tell you should have seen and that will make you feel 
inadequate!  In this area, we are all inadequate! 
I know this doesn't help.  It's meant as sympathy. 
I have been building and using computers since the 50s, when I helped build one 
that used relays and I still have NO interest in software except to say what it 
should do, at which I've been pretty successful. 
Good luck and remember, there are knobs on the radio and they will probably 
work for you, since the software in the radio has likely had a few years to get 
sorted out and the worst bugs found. 
WL
__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Geoffrey Feldman]

These is nothing unique about the Elecraft serial cable except possibly the
radio side connector.  Basically it's a USB to RS232 Ground/transmit/Receive
cable. Anyone who understands USB com ports can help you.  They don't need
to know radio.  They should understand what I wrote here.

For USB COM port problems (with anything, including these).
Run DEVMGR (I do this by entering that in the search bar)
In Devmgr "View" menu , click / check "Show Hidden Devices"
Look in the list for "Ports(COM & LPT) Expand that to the sub list
You will see a list of ports there in the sub list.  Some are grayed out,
those are not connected.
Plug in your Elecraft serial cable. Is there a change?  You should see  a
grayed out one now dark (enabled) (as COM 1 is)  That is the number of the
Elecraft port.
OR ... a new one just appears. This sometimes happens. That is the new
number of the Elecraft port. (This is a likely outcome).

Make a note of anything in devmgr list, this may help Elecraft help you but
I expect you will have figured it out with the above steps.

If this does not work, try other USB ports on your computer with the above
procedure.

If this does not work, try the Elecraft cable on a friends computer (the
driver for Elecraft is pretty standard you don't need the radio to check the
cable).  If this does not work, you need a Elecraft serial cable.  You can
also look in the cable and make one.  There are USB to RS232 cables you can
change the connector to match the cable description in the manual.  Others
available may have the same connector but TX and RX are reversed.  Some are
already the same as elecraft.

W1GCF
Geoff

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[Peter Dougherty (W2IRT)]

Reassigning port numbers did not solve the problem, and I did try that as one 
of the first steps in troubleshooting.

With one day’s work under my belt here’s where the situation lies as of tonight.

 

1.  After a cold reboot, the first attempt to launch either CI-V Commander 
(DX Labs rig interface) or N1MM Logger + may or may not capture the COM5 port 
used for CAT control (which was briefly changed to COM8 then changed back after 
finding no change).
2.  Launching either the old version of N1MM Rotor (v12.11) or the current 
.NET version, there’s about a very slim chance that it will work, but the usual 
result is that on attempting to start the rotor software it indicates both 
rotor com ports (COM1 and COM3) are already in use, and any attempt to invoke a 
direction command generates an error message (8018, IIRC) stating the function 
can only work if a port is open.
3.  Using the DX Lab “DX View” software, which interfaces with the rotor 
control software, if I repeatedly enable/disable the rotor control tick box, it 
**MAY** come back, and will keep working until the program is closed.
4.  If CAT control is in fact established, whether through N1MM or 
Commander, it will remain active until the program is closed. Once closed, 
either reopening it or opening the other control software will result in either 
program not being able to see the radio (i.e. the port remains locked out). 
Note than if it is Commander that is closed and N1MM does not see the radio at 
first, if I hit the “Reset Radio” bar in the bandmap several times it does seem 
to come back and start working again.
5.  Every other function of the PC is working the same as it always has, 
and once a COM port feature is working it remains working flawlessly.
6.  Troubleshooting has involved using Process Explorer to see if any 
devices are holding a port open when the problem is occurring, and none appear 
to be doing so. Phantom COM ports were removed, all USB devices were set to fix 
the issue of stopping the device for power saving (I hoped that one would work, 
but it didn’t), and all USB Serial drivers were deleted and allowed to 
reinstall themselves upon reboot. The results were identical.

 

In short, it appears to me that there is SOMETHING within Windows 11 that has 
changed somehow, and is locking serial ports on its own, with no easy way to 
release them.

 

- pjd

 

From: Lyn Norstad  
Sent: Thursday, June 30, 2022 8:46 PM
To: 'Julia Tuttle' 
Cc: 'Peter Dougherty (W2IRT)' ; 'George Thornton' 
; 'Elecraft' 
Subject: RE: [Elecraft] COM port problems

 

Julie –

 

I can look for it … but I don’t believe it was in an official MSFT document.  
Nevertheless, it has been going on for a couple years.  It seems to affect 
almost every ham using Win 10 sooner or later.

 

My understanding is that one or more specific Windows 10 Pro 64 updates 
reassigned COM ports in order to prevent a potential hacker from accessing the 
system.  It may have been related to the presence of specific software 
installed on the system.

 

In any event, the fix I mentioned does indeed work and ends the problem.

 

George may have other issues, since he’s already tried this

 

73

Lyn, W0LEN

 

 

From: Julia Tuttle [mailto:ju...@juliatuttle.net] 
Sent: Thursday, June 30, 2022 2:47 PM
To: l...@lnainc.com <mailto:l...@lnainc.com> 
Cc: Peter Dougherty (W2IRT); George Thornton; Elecraft
Subject: Re: [Elecraft] COM port problems

 

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 mailto:l...@lnainc.com> > 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: elecraft-boun...@mailman.qth.net 
<mailto:elecraft-boun...@mailman.qth.net> 
[mailto:elecraft-boun...@mailman.qth.net 
<mailto:elecraft-boun...@mailman.qth.net> ] On Behalf Of Peter Dougherty
(W2IRT)
Sent: Thursday, June 30, 2022 12:28 AM
To: 'George Thornton'; Elecraft@mailman.qth.net 
<mailto:Elecraft@mailman.qth.net> 
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

Re: [Elecraft] COM port problems

[Lyn Norstad]

Julie –

 

I can look for it … but I don’t believe it was in an official MSFT document.  
Nevertheless, it has been going on for a couple years.  It seems to affect 
almost every ham using Win 10 sooner or later.

 

My understanding is that one or more specific Windows 10 Pro 64 updates 
reassigned COM ports in order to prevent a potential hacker from accessing the 
system.  It may have been related to the presence of specific software 
installed on the system.

 

In any event, the fix I mentioned does indeed work and ends the problem.

 

George may have other issues, since he’s already tried this

 

73

Lyn, W0LEN

 

 

From: Julia Tuttle [mailto:ju...@juliatuttle.net] 
Sent: Thursday, June 30, 2022 2:47 PM
To: l...@lnainc.com
Cc: Peter Dougherty (W2IRT); George Thornton; Elecraft
Subject: Re: [Elecraft] COM port problems

 

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  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: elecraft-boun...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty
(W2IRT)
Sent: Thursday, June 30, 2022 12:28 AM
To: 'George Thornton'; Elecraft@mailman.qth.net
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  
Sent: Wednesday, June 29, 2022 10:23 PM
To: Peter Dougherty (W2IRT) ; Elecraft@mailman.qth.net
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)" mailto:li...@w2irt.net> > 

Date: 6/29/22 6:59 PM (GMT-08:00) 

To: Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net>  

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 doub

Re: [Elecraft] COM port problems

[Julia Tuttle]

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  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: elecraft-boun...@mailman.qth.net
> [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty
> (W2IRT)
> Sent: Thursday, June 30, 2022 12:28 AM
> To: 'George Thornton'; Elecraft@mailman.qth.net
> 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 
> Sent: Wednesday, June 29, 2022 10:23 PM
> To: Peter Dougherty (W2IRT) ; Elecraft@mailman.qth.net
> 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)" mailto:li...@w2irt.net>
> >
>
> Date: 6/29/22 6:59 PM (GMT-08:00)
>
> To: Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net>
>
> 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.face

Re: [Elecraft] COM port problems

[Lyn Norstad]

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: elecraft-boun...@mailman.qth.net
[mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty
(W2IRT)
Sent: Thursday, June 30, 2022 12:28 AM
To: 'George Thornton'; Elecraft@mailman.qth.net
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  
Sent: Wednesday, June 29, 2022 10:23 PM
To: Peter Dougherty (W2IRT) ; Elecraft@mailman.qth.net
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)" mailto:li...@w2irt.net> > 

Date: 6/29/22 6:59 PM (GMT-08:00) 

To: Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net>  

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:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to gthorn...@thorntonmostullaw.com
<mailto:gthorn...@thorntonmostullaw.com>  

__
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.

Re: [Elecraft] COM port problems

[Peter Dougherty (W2IRT)]

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  
Sent: Wednesday, June 29, 2022 10:23 PM
To: Peter Dougherty (W2IRT) ; Elecraft@mailman.qth.net
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)" mailto:li...@w2irt.net> > 

Date: 6/29/22 6:59 PM (GMT-08:00) 

To: Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net>  

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:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to gthorn...@thorntonmostullaw.com
<mailto:gthorn...@thorntonmostullaw.com>  

__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[David Decoons]

Hi Peter,

I am pretty sure I know the answer. I was sleeping when you called earlier 
having been in Frantic City for a couple of days. 

I should be up by 8 a.m. tomorrow. Give me a call and I will walk you through 
checking some settings.

73
Dave wo2x

Sent from my iPad

> On Jun 29, 2022, at 10:25 PM, George Thornton 
>  wrote:
> 
> 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)" 
> Date: 6/29/22 6:59 PM (GMT-08:00)
> To: Elecraft@mailman.qth.net
> 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:Elecraft@mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to gthorn...@thorntonmostullaw.com
> __
> 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
> Message delivered to rocke...@gmail.com 
__
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
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] COM port problems

[George Thornton]

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)" 
Date: 6/29/22 6:59 PM (GMT-08:00)
To: Elecraft@mailman.qth.net
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:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to gthorn...@thorntonmostullaw.com
__
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
Message delivered to arch...@mail-archive.com 

[Elecraft] COM port problems

[Peter Dougherty (W2IRT)]

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

 

__
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
Message delivered to arch...@mail-archive.com