So why does the Arduino IDE connect to an Arduino using a different COM port each time a different one is plugged in, even tho each Arduino is plugged into the same USB connector to the PC ?

This is the case with most USB devices.  The USB transceivers are coded with unique serial numbers, and because of that, the drivers caused them to be assigned a unique COM id.  On my development system at home, I am currently well over COM100.  I have a client that wants to have the USB device enumerate to the same COM number on a system, so I program a fixed Serial Number on the devices, so that any adapter that is connected on a give computer will enumerate to the same COM number.

Having switched over to Linux OS on my computer years ago, I no longer have to experience this Windows COM port comedy.

On the Arduino side, there is a core header file "usbconfig.h" which contains the USB configuration parameters.

I think it only gets interesting when you hit COM256. Might need to consider a bit of housekeeping and clear out unused assignments at that point.

Can I get some clarification. I find the Windows COM port comedy frustrating. Knowing the cause doesn't solve the problems but at least I have some understanding.

USB transceivers have unique serial numbers S/N. USB COM drivers assign each S/N a COM ID. When a  USB device is detected, the driver deals out COM id's. Each time a new USB device is detected, the assignment begins again and may not remain consistent?

If the device vendor ID, product ID and serial number match then it should in theory get the same virtual COM  port assignment each time, assuming it isn't currently active.

If you type:

   set devmgr_show_nonpresent_devices=1 

from a command prompt before starting Device Manager, then select 'Show hidden devices' 

you should be able to see the virtual COM port assignments for both present and non present USB serial devices.

Some issues may start to appear if you start using multiple devices with the same serial numbers at the same time (or perhaps if the device was still in use by an application when it was removed) as when the device is next plugged in, a new virtual COM port assignment may end up being created. The next time round then you now have two virtual COM port assignments allocated to the same VID/PID/serial number and it will depend on the enumeration order as to which virtual COM port you will be allocated for that device.

A bit of 'housekeeping' in Device Manager can help keep things in order.

Just to add... a useful tool for viewing USB related information all in the one place is 'USBDeview' by NirSoft. It lists all the USB devices and displays extended information including VID PID, serial No, COM port allocation and so on for current and past devices. It might be a rather long list if you are above COM100 though.

https://www.nirsoft.net/utils/usb_devices_view.html

I find this happens with the Arduino Leonardo, the Uno doesn't suffer from this problem.

In part of the programming procedure, Windows see the device do this:

- Hi, I'm a serial device, upload code to me!

- I'm no longer a serial device, I'm in programming mode, but you don't have a driver for me

- Hi, I'm back to being a serial device, upload code to me!

And it's this process which unhinges the COM port allocation. If you can manage to hold the Arduino Leonardo in its 'programmer' phase which Windows doesn't have a driver installed for (yet) then I found it doesn't suffer COM port hopping as badly. I can't remember how to get the Arduino Leonardo to stay in this mode.

Not specifically related to the Arduino, but I know that is the same for USB printers. The same printer, connected to a different USB port, Windows installs a new printer. The old one stays offline.

If you switch back to the old USB port, the old printer (still installed) comes to life and the new printer stays offline... It's a mess.

Double tap the reset button to force it into bootloader. LED will "breathe" in this mode. Good to recover a ATmega32u4 based board that has a faulty sketch interfering with USB loaded.

- Gough

I agree... Switched to Kubuntu 5 years ago... there are actually 2 addressing modes:

First depends on the USB driver, so the device might be: /dev/ttyUSBx, where x is 0 to [no idea what the limit is], but x is assigned always from the lowest number. This kind of addressing also tells you what kind of drive was used. USB to serial devices typically have /dev/ttyUSBx , modem drivers /dev/ttyACMx etc.

Second is something I use when repeatability is needed. The address is like /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0 and reflects the physical topology of the USB hub ports. Anything that is plugged through the USB gets the same address when connected to the same port (either directly to PC or through one of more USB hubs). I use this for manufacturing terminals that have many devices connected and I need to be sure I am talking to an instrument of device under test. I have no idea whether Windows have something like this.