There are ways in Windows to fix a USB/Serial device's identity, so that it always shows up at the same COM number each time, or at known different (but predictable) ones depending on which USB hole you connect it to.
For example, see the info here:-
http://www.w1hkj.com/doku/doku.php?id=howto:taming_the_wild_comport_in_windo...
As well as telling Windows 10 (if that's what you use) to allow applications to access to that port.
Take care, ANY USB system re-enumeration (that happens when you plug in / power up an attached device, or unplug / power down a device) can cause a COM port to be re-assigned.
Note too, that any USB hub's put in-between the PC and device, makes it a whole new ball game.
Under Linux, look up how to use "udev rules", where so long as the USB device has something unique about it's identity (a serial number for example) a similar trick can be done.
Note though, many Prolific (and clone) devices do not have any unique identity compared to many of their brethren! FTDI devices usually have a unique per-device serial number string somewhere. I only have one SiLab's device, so can't say about them.
At http://www.ftdichip.com/Support/Utilities.htm%C2%A0%C2%A0 There are two links of interest.
#
Microsoft USBView http://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
#
Linux USBView http://www.ftdichip.com/Support/Utilities.htm#USBViewLinux
Follow the one for your type of OS and you'll be able to see the device information to understand what's going on. The linux version will need compiling, but is well worth having, though you do also need to run it via sudo so it has the rights to read the needed info from the system. (I believe it can be built on MAC's too, but have no first hand knowledge re that OS.)
73.
Dave G0WBX
On 27/05/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
Subject: Re: [chirp_users] UV-5R issue To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Message-ID: CAE1d062d_i4sm7ZtNFxqBzDx3Ybx8tVPXBE1UXHLwv9wXh=+Zg@mail.gmail.com Content-Type: text/plain; charset="utf-8"
Sometimes I have to simply unplug and plug back in the USB cable.
That is really the only issue I have with Chirp and that's not on Chirp but Windows OS and/or the cable driver.
Dennis M. Wage (W9BOQ)