Thanks for the confirmation.  That's exactly consistent with my experience.  It's just too bad it has to be that way.

david, KC1DNY


n 4/25/2019 3:58 PM, Bob McGraw K4TAX wrote:
Sometimes you can disconnect the cable and then plug it back in and Windows 
will recognize the device. In other cases you will need to power down the 
device and back up in order for Windows to recognize the device.

Some assignments are sticky and will remain, while other cases it will be 
necessary to assign a port number every time.  That is controlled in the device 
driver code and the way Windows handles port assignments.

Bob, K4TAX


Sent from my iPhone

On Apr 25, 2019, at 12:53 PM, Jim KO5V <k...@earthlink.net> wrote:

Hi Bob,

I use Device Manager, and I've done what you described. However, it doesn't 
always seem to work. Sometimes the device ignores the COM port selected in its 
program and D.M, sometimes the settings won't stay selected after I close the 
program. Do I need to use Device Manager each time I start a device?

Thanks. 73, Jim  KO5V


-----Original Message-----
From: Bob McGraw K4TAX <rmcg...@blomand.net>
Sent: Apr 25, 2019 11:26 AM
To: Jim KO5V <k...@earthlink.net>
Cc: Elecraft List <elecraft@mailman.qth.net>
Subject: Re: [Elecraft] [K2] Rig Control Error

With Windows, DEVICE MANAGER is your friend.  Having it open and on screen, you 
can plug in devices or unplug devices and see, in real time, the port they are 
using.   This will then be the port to assign in an application.  Also check 
the parameters of the port to assure the device can communicate with the port.

Bob, K4TAX


Sent from my iPhone

On Apr 25, 2019, at 12:18 PM, Jim KO5V <k...@earthlink.net> wrote:

I have similar problems with my Win7 64 bit machines. It's tough to configure any additional COM 
ports, everything seems to eventually default to COM 3, and I can't make any changes 
"stick". Using only one "COM port"device, Sometimes just unplugging, and 
re-plugging that device, or stopping and restarting the desired program will make the computer see 
the connected device; sometimes,not.

I asked my brother-in-law, a Windows systems guy, what he would do, and his reply was 
that he basically does what I've been doing, but then explained about some "advanced 
stuff" that he would help me with, but that I shouldn't try them myself...

Make sure there's nothing else using the COM port, and see if the program will 
work (if you haven't already done that).

Good Luck. 73, Jim KO5V
______________________________________________________________
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



______________________________________________________________
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
______________________________________________________________
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

Reply via email to