<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><tt>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.</tt></p>
<p><tt>For example, see the info here:-</tt></p>
<p><tt><a class="moz-txt-link-freetext" href="http://www.w1hkj.com/doku/doku.php?id=howto:taming_the_wild_comport_in_windows">http://www.w1hkj.com/doku/doku.php?id=howto:taming_the_wild_comport_in_windows</a></tt></p>
<p><tt>As well as telling Windows 10 (if that's what you use) to
allow applications to access to that port.</tt></p>
<p><tt>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.</tt></p>
<p><tt>Note too, that any USB hub's put in-between the PC and
device, makes it a whole new ball game.</tt></p>
<p><tt>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.</tt></p>
<p><tt>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.</tt></p>
<p><tt>At <a class="moz-txt-link-freetext" href="http://www.ftdichip.com/Support/Utilities.htm">http://www.ftdichip.com/Support/Utilities.htm</a> There are
two links of interest.</tt></p>
<table width="100%" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td>
<li>
<p><tt><font size="2"><a
href="http://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView"><font
color="#0000FF">Microsoft USBView</font></a></font></tt></p>
</li>
<p> </p>
<li>
<p><tt><font size="2"><a
href="http://www.ftdichip.com/Support/Utilities.htm#USBViewLinux"><font
color="#0000FF">Linux USBView</font></a></font></tt></p>
</li>
</td>
</tr>
</tbody>
</table>
<p><tt><br>
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.)</tt></p>
<p><tt>73.</tt></p>
<p><tt>Dave G0WBX</tt></p>
<br>
<div class="moz-cite-prefix">On 27/05/18 20:00,
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.danplanet.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.1.1527447602.12477.chirp_users@intrepid.danplanet.com">
<pre wrap="">Subject: Re: [chirp_users] UV-5R issue
To: Discussion of CHIRP <a class="moz-txt-link-rfc2396E" href="mailto:chirp_users@intrepid.danplanet.com" moz-do-not-send="true"><chirp_users@intrepid.danplanet.com></a>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:CAE1d062d_i4sm7ZtNFxqBzDx3Ybx8tVPXBE1UXHLwv9wXh=+Zg@mail.gmail.com" moz-do-not-send="true"><CAE1d062d_i4sm7ZtNFxqBzDx3Ybx8tVPXBE1UXHLwv9wXh=+Zg@mail.gmail.com></a>
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)</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Created on and sent from a Unix like PC running and using free and open source software:
</pre>
</body>
</html>