Remote Rig

Webswitch 1216H Support in English => Configuration, Webswitch 1216H => Topic started by: DL5CW on 2015-08-06, 19:07:52

Title: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: DL5CW on 2015-08-06, 19:07:52
Hi,

I installed the Windows 10 update today. After that, my system got problems with the virtual
COM Port 4 (generated like described in the RC-1216H manual with the Microbit Setup Manager).

Windows 10 saw the COM4 as virtual port, but it doesn't work (in the Win 10 device manager you see
COM4 with an exclamation mark). So I can't use the original Expert Software - need for remote tuning the amplifier.

I was falling back to Windows 8.1 now and everything is fine again.

Is this only my problem? Or has anyone the same problem? Is this a Win 10 proplem or a problem of Microbit Setup Manager with Win 10?

73! Andy, DL5CW
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-08-07, 16:47:48
Hi,
We will try to reproduce the issue you have experienced. We will also release new Com port drivers which hopefully will fix problems like this.
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: KX7M on 2015-09-28, 17:04:30
Any updates for the Windows 10 drivers for 1258 virtual COM ports?
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-09-29, 08:54:28
Any updates for the Windows 10 drivers for 1258 virtual COM ports?
Sorry, but no, the new driver is not available yet.
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-09-30, 08:55:41
Any updates for the Windows 10 drivers for 1258 virtual COM ports?
Sometimes things happen faster than expected! Give version 1.28 a try! Find it here:  http://www.remoterig.com/wp/?page_id=88 (http://www.remoterig.com/wp/?page_id=88)

(And just to be clear, the updated drivers are for the virtual com ports created on the "Serial Port" tab in Setup Manager, not the USB virtual com ports)
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: KX7M on 2015-10-26, 19:28:42
Unfortunately, the virtual USB com ports are not working yet.
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-10-27, 08:58:29
Unfortunately, the virtual USB com ports are not working yet.
After installing version 1.28?
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: KX7M on 2015-10-31, 05:39:06
On Win 10 64bit, after I install both Setup Manager 1.28 and allow virtual COM ports installation, I can only see 4 instances of generic USB Serial Device (COM3-6). In the driver details, the provider is Microsoft, so I guess the driver installation does not make the USB COM ports the RRC 1258 COM0-2,and Ext.

and btw, the version number is still 1.27 (when uninstalling programs)
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-10-31, 08:12:25
I use Win 10 64bit myself and it works ok. You could try running the installation as 'Admin'.

Where do you see version number 1.27?
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: KX7M on 2015-11-01, 05:57:21
I did run all attempts as Admin. I figured it out. After generic USB ports show up, I had to force driver update by clicking on each of the 4 virtual USB ports Properties \ Update Driver. After that they showed up as RRC 1258 instances with Microbit 2.0 AB as provider (usbser.sys 10.0.10240.16401)
There is still a problem using the COM port with logging software, but OmniRig seems to have no problem with the same Elecraft K3.

Oh well, it is better than it was :)
Thanks!

BTW, when you go to uninstall programs (Programs and Features),  under the listing of programs to uninstal, Microbit Setup Manager version 1.27 is displayed.
Title: Re: RC-1216H with Expert1K and Windows 10 - virtual COM Port
Post by: Jan (Microbit) on 2015-11-01, 06:47:35
Glad to hear you worked it out! But strange you had to force driver update for it to work.

OK, seems we forgot to change version number in the uninstall script. Thanks for pointing that out! :)