I wish to thank all the folks here who offered helpful comments on the
problem. Yes, I did all the checking of ports and drivers and
connections - I've been dealing with those sort of things for years so
I've been there, but with no resolution this time. Neil did relate his
solution to the
Phil,
I've got my K2/100 running under Win10 using DXLabs Commander. I
could never get WSJT-X running the K2 directly using the built in Hamlib
settings, or with Omnirig or Flrig. It works fine, and I was able
to create custom controls for Commander to adjust the power if I'm
running
Interesting.
Using Windows 10 Pro I have one radio {model/brand} if I plug it in, set
the application to communicate with the port as defined in Device
Manager, all is well. I can then turn the radio off and then back on,
changing no cables or ports, and find the same application will not
> 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
List
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 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
Sent: Apr 25, 2019 11:26 AM
To: Jim KO5V
Cc: Elecraft List
Subject: Re: [Elecraft] [K2] Rig Control Error
im KO5V
>
>
> -Original Message-
>> From: Bob McGraw K4TAX
>> Sent: Apr 25, 2019 11:26 AM
>> To: Jim KO5V
>> Cc: Elecraft List
>> Subject: Re: [Elecraft] [K2] Rig Control Error
>>
>> With Windows, DEVICE MANAGER is your friend. Ha
start a device?
Thanks. 73, Jim KO5V
-Original Message-
>From: Bob McGraw K4TAX
>Sent: Apr 25, 2019 11:26 AM
>To: Jim KO5V
>Cc: Elecraft List
>Subject: Re: [Elecraft] [K2] Rig Control Error
>
>With Windows, DEVICE MANAGER is your friend. Having it open and on s
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
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
I'm having similar problems after going from Windows 7 to Windows 10.
I'm using a KX3 on FT8 with WSJT-X, cheap $10 Sabrent USB Soundcard,
nothing in the 9-pin RS-232 wired port of a Dell Inspiron 3670. It all
works well most of the time, but ... .
Occasionally I get one of the two error
Problem (described below) with the WSJTX program (the "home" of FT8)
trying to access K2. I didn't get an answer on the WSJTX Yahoo group so
I'll try here.
Configuration:
Dell Laptop PC with iMic and RigBlaster Plus connected to Elecraft K2.
Both the Elecraft and RigBlaster serial ports
12 matches
Mail list logo
