Elecraft

Remote computer won't communicate with K3 after re-installing Windows 10

Classic

List

Threaded

8 messages Options

Jim Reisert AD1C

Remote computer won't communicate with K3 after re-installing Windows 10

I need some help from the reflector. First of all, I am NOT a K3
owner. I am helping a friend remotely who is 2000 miles away.

His computer was running Windows 10 and was previously working with
the K3, both with the K3 Utility as well as DX4WIN. I had to rebuild
the computer from scratch after a number of software problems
developed. His microHAM device with several virtual COM ports is
working fine (it's interfaced to a Ten-Tec Orion). It's only the K3
that we're having problems with.

I have been referring to this page:

http://www.elecraft.com/K3/k3_software.htm

First of all, regarding this statement, "Elecraft offers the KUSB
serial-to-USB cable for USB only computers etc. Our cable was
originally provided using a Prolific chip set but since approximately
July of 2010 we have been shipping KUSB cables which use the FTDI chip
set."

How do I determine which chipset he has? Other than the virtual COM
ports for the microHAM device, I see two other ports:

One that says simply, "USB Com Port 3"

Another port mentions a Silicon Labs driver, and it shows up on COM10.

There is no overlap of any COM port numbers.

I have tried both DX4WIN and the K3 utility with both COM ports (3 and
10). While there are no "unknown port" errors, neither program can
communicate with the K3 on either port. So something is missing and I
do not know what that is.

Again, I am trying to do this remotely, so it's hard for me to pull
cables, etc. to try to figure out what's going on.

Can someone please suggest a course of action for me to try to debug
this problem? Mainly, I don't know which of the two COM devices above
*may* be for the K3, and whether the correct driver is installed.

Thanks & 73 - Jim AD1C

--
Jim Reisert AD1C, <[hidden email]>, http://www.ad1c.us
______________________________________________________________
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
Message delivered to [hidden email]

Bill Rogers W3UL

Re: Remote computer won't communicate with K3 after re-installing Windows 10

Jim

On my Win 10 machine I can tell by going to *Device Manager*,* Ports*,
selecting the specific port in question, then right clicking and going to
*Properties*. There, on all of my USB connections, it says "*Manufacturer:
FTDI*". Hope that will help.

73, Bill W3UL

On Mon, Aug 14, 2017 at 12:27 PM, Jim Reisert AD1C <[hidden email]>
wrote:

> I need some help from the reflector. First of all, I am NOT a K3
> owner. I am helping a friend remotely who is 2000 miles away.
>
> His computer was running Windows 10 and was previously working with
> the K3, both with the K3 Utility as well as DX4WIN. I had to rebuild
> the computer from scratch after a number of software problems
> developed. His microHAM device with several virtual COM ports is
> working fine (it's interfaced to a Ten-Tec Orion). It's only the K3
> that we're having problems with.
>
> I have been referring to this page:
>
> http://www.elecraft.com/K3/k3_software.htm
>
> First of all, regarding this statement, "Elecraft offers the KUSB
> serial-to-USB cable for USB only computers etc. Our cable was
> originally provided using a Prolific chip set but since approximately
> July of 2010 we have been shipping KUSB cables which use the FTDI chip
> set."
>
> How do I determine which chipset he has? Other than the virtual COM
> ports for the microHAM device, I see two other ports:
>
> One that says simply, "USB Com Port 3"
>
> Another port mentions a Silicon Labs driver, and it shows up on COM10.
>
> There is no overlap of any COM port numbers.
>
> I have tried both DX4WIN and the K3 utility with both COM ports (3 and
> 10). While there are no "unknown port" errors, neither program can
> communicate with the K3 on either port. So something is missing and I
> do not know what that is.
>
> Again, I am trying to do this remotely, so it's hard for me to pull
> cables, etc. to try to figure out what's going on.
>
> Can someone please suggest a course of action for me to try to debug
> this problem? Mainly, I don't know which of the two COM devices above
> *may* be for the K3, and whether the correct driver is installed.
>
> Thanks & 73 - Jim AD1C
>
> --
> Jim Reisert AD1C, <[hidden email]>, http://www.ad1c.us
> ______________________________________________________________
> 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
> Message delivered to [hidden email]
>

--
73,
William (Bill) Rogers / W3UL
Annapolis, Maryland U.S.A.
______________________________________________________________
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
Message delivered to [hidden email]

Jim Reisert AD1C

Re: Remote computer won't communicate with K3 after re-installing Windows 10

> On my Win 10 machine I can tell by going to Device Manager, Ports, selecting
> the specific port in question, then right clicking and going to Properties.
> There, on all of my USB connections, it says "Manufacturer: FTDI". Hope
> that will help.

Thanks, Bill, but I don't know which interface cable he has - it could
be Prolific or FTDI, depending on how old it is. Because there are
two COM ports not associated with the microHAM device (the generic
"USB" and the one that has a Silicon Labs driver), I guess I have to
assume that the generic USB COM port is the one that the K3 needs.
I'll see what type of device it is, and if I can find the right driver
for it.

- Jim

--
Jim Reisert AD1C, <[hidden email]>, http://www.ad1c.us
______________________________________________________________
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
Message delivered to [hidden email]

Clay Autery-2

Re: Remote computer won't communicate with K3 after re-installing Windows 10

In reply to this post by Bill Rogers W3UL

There's your issue.... Either he has a counterfeit FTDI chip/unit, OR
simply haven't gotten the FTDI drivers all updated.

I JUST used an older Elecraft supplied FTDI cable the other day to
update an Elmer's KPA500 or KAT500, I forget which.... and it took some
doing to finally get the latest FTDI drivers on ALL the ports used for
K3s, XG3, KAT500, KPA500, P3, etc...

Latest driver is dated: 09/28/2016 v.2.12.24.0 according to my
machine... Maybe an even newer one for Win10.

______________________
Clay Autery, KY5G
MONTAC Enterprises
(318) 518-1389

On 8/14/2017 12:15 PM, Bill Rogers W3UL wrote:

> Jim
>
> On my Win 10 machine I can tell by going to *Device Manager*,* Ports*,
> selecting the specific port in question, then right clicking and going to
> *Properties*. There, on all of my USB connections, it says "*Manufacturer:
> FTDI*". Hope that will help.
>
> 73, Bill W3UL
>
> On Mon, Aug 14, 2017 at 12:27 PM, Jim Reisert AD1C <[hidden email]>
> wrote:
>
>> I need some help from the reflector. First of all, I am NOT a K3
>> owner. I am helping a friend remotely who is 2000 miles away.
>>
>> His computer was running Windows 10 and was previously working with
>> the K3, both with the K3 Utility as well as DX4WIN. I had to rebuild
>> the computer from scratch after a number of software problems
>> developed. His microHAM device with several virtual COM ports is
>> working fine (it's interfaced to a Ten-Tec Orion). It's only the K3
>> that we're having problems with.
>>
>> I have been referring to this page:
>>
>> http://www.elecraft.com/K3/k3_software.htm
>>
>> First of all, regarding this statement, "Elecraft offers the KUSB
>> serial-to-USB cable for USB only computers etc. Our cable was
>> originally provided using a Prolific chip set but since approximately
>> July of 2010 we have been shipping KUSB cables which use the FTDI chip
>> set."
>>
>> How do I determine which chipset he has? Other than the virtual COM
>> ports for the microHAM device, I see two other ports:
>>
>> One that says simply, "USB Com Port 3"
>>
>> Another port mentions a Silicon Labs driver, and it shows up on COM10.
>>
>> There is no overlap of any COM port numbers.
>>
>> I have tried both DX4WIN and the K3 utility with both COM ports (3 and
>> 10). While there are no "unknown port" errors, neither program can
>> communicate with the K3 on either port. So something is missing and I
>> do not know what that is.
>>
>> Again, I am trying to do this remotely, so it's hard for me to pull
>> cables, etc. to try to figure out what's going on.
>>
>> Can someone please suggest a course of action for me to try to debug
>> this problem? Mainly, I don't know which of the two COM devices above
>> *may* be for the K3, and whether the correct driver is installed.
>>
>> Thanks & 73 - Jim AD1C
>>
>> --
>> Jim Reisert AD1C, <[hidden email]>, http://www.ad1c.us
>> ______________________________________________________________
>> 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
>> Message delivered to [hidden email]
>>
>
>

______________________________________________________________
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
Message delivered to [hidden email]

Clay Autery-2

Re: Remote computer won't communicate with K3 after re-installing Windows 10

In reply to this post by Jim Reisert AD1C

My K3s is using an FTDI driver right this minute for BOTH Win4K3Suite
and/or Elecraft K3s Config software... COM7 by the way... not that that
really matters.

______________________
Clay Autery, KY5G
MONTAC Enterprises
(318) 518-1389

On 8/14/2017 12:27 PM, Jim Reisert AD1C wrote:

>> On my Win 10 machine I can tell by going to Device Manager, Ports, selecting
>> the specific port in question, then right clicking and going to Properties.
>> There, on all of my USB connections, it says "Manufacturer: FTDI". Hope
>> that will help.
> Thanks, Bill, but I don't know which interface cable he has - it could
> be Prolific or FTDI, depending on how old it is. Because there are
> two COM ports not associated with the microHAM device (the generic
> "USB" and the one that has a Silicon Labs driver), I guess I have to
> assume that the generic USB COM port is the one that the K3 needs.
> I'll see what type of device it is, and if I can find the right driver
> for it.
>
> - Jim
>

Jim Brown-10

Re: Remote computer won't communicate with K3 after re-installing Windows 10

In reply to this post by Jim Reisert AD1C

On 8/14/2017 10:27 AM, Jim Reisert AD1C wrote:
> Thanks, Bill, but I don't know which interface cable he has - it could
> be Prolific or FTDI, depending on how old it is.

This vendor, a ham in San Jose, sells a wide range of genuine FTDI USB
adapter cables, including this one that's USB to DB9.

http://www.ebay.com/itm/FTDI-USB-2-0-Converter-Adapter-Cable-to-RS-232-9-Pin-RS232-Serial-Port-STM-DB-9M-/151566371748?hash=item234a0f4ba4:g:dYUAAOSwbApZc97o

I bought a couple of cables from him and was pleased with what I got.

73, Jim K9YC

______________________________________________________________
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
Message delivered to [hidden email]

k6dgw

Re: Remote computer won't communicate with K3 after re-installing Windows 10

In reply to this post by Jim Reisert AD1C

Jim, just disconnect and reconnect each USB cable while watching the COM
ports in Device Mangler. You'll see the port disappear and then reappear.

FWIW: I never had any problems with Prolific USB-Serial chipsets until
Win10 graciously installed itself in the middle of the night without
asking. Turns out, there are several generations of Prolific chipsets,
and there are no Win10 drivers for a couple of the oldest ones. I found
an adapter with one of the more recent chipsets and it works fine.

73,

Fred ("Skip") K6DGW
Sparks NV USA
Washoe County DM09dn

On 8/14/2017 10:27 AM, Jim Reisert AD1C wrote:

Jim Reisert AD1C

Re: Remote computer won't communicate with K3 after re-installing Windows 10

In reply to this post by Clay Autery-2

Problem solved!

Apparently, the default FTDI driver that Windows 10 installs is from
2013 and just isn't good enough for this application.
I installed the latest FTDI driver that the K3 web site pointed to and
all is well now.

--
Jim Reisert AD1C, <[hidden email]>, http://www.ad1c.us
______________________________________________________________
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
Message delivered to [hidden email]