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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
