K3 utility and new computer don't get along

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

K3 utility and new computer don't get along

W8JH
I have built a new NUC computer for the shack and Windows 10 is on it.  Let's take that as a given and not debate the merits of the computer or OS please.

I am trying to get the computer to talk with the K3 (serial number 1713) as I had set up in the past.  The K3 utility and N3FJP's AC log both worked with the old system.

I was unable to get this working with my old USB to DB9 cables I used so I bought a new USB to DB9 cable with the FTDI chipset in it.  Looking in Win10 Device Manager I can see that the FTDI driver is dated 3/9/2016.  The parameters I have set are 38,400, 8, N, 1 and the flow control is set to none.

K3 utility is unable to find the K3 at any baud rate.  N3FJP's AClog is also unable to find the K3.  The real oddity is that when I have the AC log program send a frequency change to the K3 the change goes through.  This also works when I click on a DX spot and AC log changes the K3 to the appropriate mode and frequency.  

So it seems that information is flowing from the computer to the K3 but AC log does not seem to recognize any data coming back as the frequency does not change on the computer screen when I spin the K3 dial (as it previously did with the old system).  Also the K3 Utility does not seem to get info from the K3.

Any suggestions how to proceed with diagnosis/treatment are appreciated as I do not see how to proceed from here.

Thanks in advance for any help on or off list, your choice.

73,

Joe, W8JH
73,

Joe, W8JH

K3s, KPA 500, KAT 500 and  KX3 happy user.