Actions
Forum Thread Details
  • State Verified Answer
  • Replies 11 replies
  • Subscribers 384 subscribers
  • Views 3184 views
  • Users 0 members are here
Related

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 ?

robogary

Curious minds want to know 

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 ?

Is it related to he USB driver IC used on the Arduino board ? 

Parents
  • 0

    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.

  • 0 in reply to BigG

    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.

Reply
  • 0 in reply to BigG

    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.

Children
No Data