Elecraft

[K2] Rig Control Error

Classic

List

Threaded

16 messages Options

Phil Kane-2

[K2] Rig Control 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 connected to the computer
are 9-pin "RS-232" wired ports and all drivers are current.

With PC running Windows 7, both MixW3 and WSJTX 2.0.0 using identical
CAT control and audio settings ran without problems.

After upgrading the computer to Win 10 with no other changes, MixW3 runs
properly but WSJTX 2.0.0 and 2.0.1 did not. The error messages from
Hamlib are:

(Tune) "IO error while opening connection to rig"
(Test CAT) "Communication timed out while opening connection to rig"

In additions, the frequency readout on the WSJTX UI has reverted to all
zeros.

Are there "permission" settings in Win 10 that didn't exist in Win 7?

Has anyone experienced this with Win 10 and found a solution?

73 de K2ASP - Phil Kane
Elecraft K2/100 s/n 5402

From a Clearing in the Silicon Forest
Beaverton (Washington County) Oregon
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

David Haines

Re: [K2] Rig Control Error

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 messages you show.

My conjecture is that is has something to do with the COM ports, or
shortage thereof. The KX3 utility lists only one, COM3, when I try to
download to the KX3. It appears the COM3 port was taken over by another
peripheral, maybe a printer? Sometimes a reboot of the PC fixes it, but
it would be nice to have a permanent solution.

Can you communicate to the K2 using the K2 Utility?

73 de david, KC1DNY, in the Maine woods.

elecraft KX3 s/n 8651

On 4/24/2019 11:02 PM, Phil Kane wrote:

> 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 connected to the computer
> are 9-pin "RS-232" wired ports and all drivers are current.
>
> With PC running Windows 7, both MixW3 and WSJTX 2.0.0 using identical
> CAT control and audio settings ran without problems.
>
> After upgrading the computer to Win 10 with no other changes, MixW3 runs
> properly but WSJTX 2.0.0 and 2.0.1 did not. The error messages from
> Hamlib are:
>
> (Tune) "IO error while opening connection to rig"
> (Test CAT) "Communication timed out while opening connection to rig"
>
> In additions, the frequency readout on the WSJTX UI has reverted to all
> zeros.
>
> Are there "permission" settings in Win 10 that didn't exist in Win 7?
>
> Has anyone experienced this with Win 10 and found a solution?
>
> 73 de K2ASP - Phil Kane
> Elecraft K2/100 s/n 5402
>
> From a Clearing in the Silicon Forest
> Beaverton (Washington County) Oregon
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> 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:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Jim KO5V

Re: [K2] Rig Control Error

In reply to this post by Phil Kane-2

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:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Bob McGraw - K4TAX

Re: [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 <[hidden email]> 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:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>

Jim KO5V

Re: [K2] Rig Control Error

In reply to this post by Phil Kane-2

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 <[hidden email]>
>Sent: Apr 25, 2019 11:26 AM
>To: Jim KO5V <[hidden email]>
>Cc: Elecraft List <[hidden email]>
>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 <[hidden email]> 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:[hidden email]
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>
>

Bob McGraw - K4TAX

Re: [K2] Rig Control Error

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 <[hidden email]> 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 <[hidden email]>
>> Sent: Apr 25, 2019 11:26 AM
>> To: Jim KO5V <[hidden email]>
>> Cc: Elecraft List <[hidden email]>
>> 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 <[hidden email]> 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:[hidden email]
>>>
>>> This list hosted by: http://www.qsl.net
>>> Please help support this email list: http://www.qsl.net/donate.html
>>>
>>
>>
>

David Haines

Re: [K2] Rig Control Error

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 <[hidden email]> 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 <[hidden email]>
>>> Sent: Apr 25, 2019 11:26 AM
>>> To: Jim KO5V <[hidden email]>
>>> Cc: Elecraft List <[hidden email]>
>>> 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 <[hidden email]> 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:[hidden email]
>>>>
>>>> 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:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

Don Wilhelm

Re: [K2] Rig Control Error

Windows will usually assign the same port number IF you plug it into the
same USB port.

You can go into Properties for each device and change the port number -
COM1 and COM2 are usually reserved for serial ports on the motherboard,
even if no RS-232 ports are present on the board.

73,
Don W3FPR

On 4/25/2019 4:14 PM, David Haines wrote:

> 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 <[hidden email]> 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 <[hidden email]>
>>>> Sent: Apr 25, 2019 11:26 AM
>>>> To: Jim KO5V <[hidden email]>
>>>> Cc: Elecraft List <[hidden email]>
>>>> 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 <[hidden email]> 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:[hidden email]
>>>>>
>>>>> 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:[hidden email]
>>
>> 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:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

Elecraft mailing list

Re: [K2] Rig Control Error

My Window10 computer has 4 USB C ports and a 7 port USB3 hub. I have 5 different Elecraft USB Serial ports connected and they always receive the same com port number regardless of which USB port or HUB port they are plugged into. K3s, KAT500, KPA500, KX3, SG3 and other non Elecraft devices.

I have never had them change as a result of a Windows upgrade.

73 - Mike - K9JRI

> On Apr 25, 2019, at 5:08 PM, Don Wilhelm <[hidden email]> wrote:
>
> Windows will usually assign the same port number IF you plug it into the same USB port.
>
> You can go into Properties for each device and change the port number - COM1 and COM2 are usually reserved for serial ports on the motherboard, even if no RS-232 ports are present on the board.
>
> 73,
> Don W3FPR
>
> On 4/25/2019 4:14 PM, David Haines wrote:
>> 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 <[hidden email]> 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 <[hidden email]>
>>>>> Sent: Apr 25, 2019 11:26 AM
>>>>> To: Jim KO5V <[hidden email]>
>>>>> Cc: Elecraft List <[hidden email]>
>>>>> 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 <[hidden email]> 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:[hidden email]
>>>>>>
>>>>>> 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:[hidden email]
>>>
>>> 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:[hidden email]
>> 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:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

Bob McGraw - K4TAX

Re: [K2] Rig Control Error

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
communicate with the radio. Then I look at Device Manager and find that
the port number has changed. I change the port number in the
application and all is well........until next time.

And with another radio {Elecraft K3S}, I do not find that changing the
physical USB connection on the computer will cause the communication
port number to change. Hence the port assignment is sticky.

This says to me all USB drivers are not created equal. And likewise,
I've experienced no issues being the result of Windows 10 updates.

73

Bob, K4TAX

On 4/25/2019 4:14 PM, Michael Blake via Elecraft wrote:
> My Window10 computer has 4 USB C ports and a 7 port USB3 hub. I have 5 different Elecraft USB Serial ports connected and they always receive the same com port number regardless of which USB port or HUB port they are plugged into. K3s, KAT500, KPA500, KX3, SG3 and other non Elecraft devices.
>
> I have never had them change as a result of a Windows upgrade.
>
> 73 - Mike - K9JRI
>
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Neil Zampella

Re: [K2] Rig Control Error

In reply to this post by Phil Kane-2

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 remotely using VNC.

Neil, KN3ILZ

On 4/24/2019 11:02 PM, Phil Kane wrote:

> 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 connected to the computer
> are 9-pin "RS-232" wired ports and all drivers are current.
>
> With PC running Windows 7, both MixW3 and WSJTX 2.0.0 using identical
> CAT control and audio settings ran without problems.
>
> After upgrading the computer to Win 10 with no other changes, MixW3 runs
> properly but WSJTX 2.0.0 and 2.0.1 did not. The error messages from
> Hamlib are:
>
> (Tune) "IO error while opening connection to rig"
> (Test CAT) "Communication timed out while opening connection to rig"
>
> In additions, the frequency readout on the WSJTX UI has reverted to all
> zeros.
>
> Are there "permission" settings in Win 10 that didn't exist in Win 7?
>
> Has anyone experienced this with Win 10 and found a solution?
>
> 73 de K2ASP - Phil Kane
> Elecraft K2/100 s/n 5402
>
> >From a Clearing in the Silicon Forest
> Beaverton (Washington County) Oregon
>

---
This email has been checked for viruses by AVG.
https://www.avg.com

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Phil Kane-2

Re: [K2] Rig Control Error

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 problem and I will respectfully continue with him
off-line as to the details.

Again, thanks for the assist.--

73 de K2ASP - Phil Kane
Elecraft K2/100 s/n 5402

From a Clearing in the Silicon Forest
Beaverton (Washington County) Oregon
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Phil Kane-2

Re: [K2] WSJTX -W10 Rig Control Error - PROBLEM SOLVED

On 4/26/2019 8:00 PM, Phil Kane wrote:

> 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 problem and I will respectfully continue with him
> off-line as to the details.

The solution was so simple that it hit me in the face when I tried it!

In WSJTX Configuration (F2) Radio tab - I set Rig to "None". This turns
off CAT control. Then I set PTT to RTS and the COM Port to the one that
controls the RigBlaster that is connected to the K2.

Lo and behold, the rig is recognized and operation is as expected.
Sure, there are no CAT control bells-and-whistles, but the program works
KISS. Now to make contacts again.....

73 de K2ASP - Phil Kane
Elecraft K2/100 s/n 5402

From a Clearing in the Silicon Forest
Beaverton (Washington County) Oregon
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Neil Zampella

Re: [K2] WSJTX -W10 Rig Control Error - PROBLEM SOLVED

FWIW ... I use DXLab's DX Commander with my K2, and have full CAT
control. Not using a Rigblaster, but connecting through the RS-232
cable, CAT works fine. I've worked a DXPedition using this setup, and
the Fox/Hound mode worked perfectly.

Neil, KN3ILZ

On 5/14/2019 1:39 PM, Phil Kane wrote:

> On 4/26/2019 8:00 PM, Phil Kane wrote:
>
>> 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 problem and I will respectfully continue with him
>> off-line as to the details.
> The solution was so simple that it hit me in the face when I tried it!
>
> In WSJTX Configuration (F2) Radio tab - I set Rig to "None". This turns
> off CAT control. Then I set PTT to RTS and the COM Port to the one that
> controls the RigBlaster that is connected to the K2.
>
> Lo and behold, the rig is recognized and operation is as expected.
> Sure, there are no CAT control bells-and-whistles, but the program works
> KISS. Now to make contacts again.....
>
> 73 de K2ASP - Phil Kane
> Elecraft K2/100 s/n 5402
>
> >From a Clearing in the Silicon Forest
> Beaverton (Washington County) Oregon
>

Frank Krozel

Alternate refletor for Collins?

Folks this group has many eyes and ears out with amazing resources.

I am looking for a similar reflector for a Collins KWM-380.

Once I have this up and running I will probably trade for a K3S, etc but in the meantime, does anyone know of the resource link (Google-Io, etc) for the KWM-380?

de Frank KG9H
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Elecraft mailing list

Re: Alternate refletor for Collins?

Frank

There is a Yahoo group called KWM-1 run by a WA5. Haven’t been there in years.

Regards,

Mark, K1RX

> On May 21, 2019, at 8:05 AM, Frank Krozel <[hidden email]> wrote:
>
>
> Folks this group has many eyes and ears out with amazing resources.
>
> I am looking for a similar reflector for a Collins KWM-380.
>
> Once I have this up and running I will probably trade for a K3S, etc but in the meantime, does anyone know of the resource link (Google-Io, etc) for the KWM-380?
>
> de Frank KG9H
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html