Immediate termination and Device dropping

Submitted by Brassaxe on #1

I seem to be having two issues.

When I start the Server (Win 11) it sometimes starts, sometimes does not, and sometimes it will start then shutdown.

Second issue, (client side) I have one device (An RFExplorer 6G Combo+) that I can connect to and it seems to have the drives and gives it an appropriate Com port. But when I try to access the device with the software it immediately disconnects the device, windows will make the notification sound, the device manager list will refresh as if it was disconnected. But when the device manager list repopulates the device is still there with the same com port. Its as if accessing the device causes the connection to reset.

Thoughts?

Submitted by Brassaxe on Sat, 2022/12/10 - 11:15

#3

Is there any way around the Start/Not start issue?

Also, I am not at the server or client computers at the moment but I do think I just downloaded the newest client today. I will check on Monday. It's only one device that has the issue.

Submitted by Michael on Sat, 2022/12/10 - 22:05

#4

I found the bug in VirtualHere server for item 1 and fixed it. (It was'nt a bug in win11 after all)

So download the latest version 4.4.7 from this website and it will resolve that issue. https://www.virtualhere.com/windows_server_software

 

Submitted by Brassaxe on Tue, 2022/12/13 - 07:11

#5

So the server now works like normal but the client side, even with an up to date client still has disconnection issues with the one device. 

Submitted by Michael on Tue, 2022/12/13 - 07:45

#6

In the virtualhere client, right click on the problematic device and select Custom Event Handler... and paste in exactly this line:

onReset.$VENDOR_ID$.$PRODUCT_ID$=

then try use via virtualhere again

Submitted by Brassaxe on Sat, 2022/12/17 - 06:10

#7

Still not working. If it helps the Product is a CP2102N USB to UART Bridge.

Vendor ID-   0x10C4 

Product ID-   0xEA60

 

Submitted by Michael on Sat, 2022/12/17 - 07:25

#8

OK im not sure sorry. I dont know why its not passing through

You could try updating the firmware on the device https://j3.rf-explorer.com/upgrade or maybe ask rf-explorer to test it via virtualhere and see if they could tell me the issue since they know their firmware

I see they have a system check program that you could download and see what it says when you use it via virtualhere https://j3.rf-explorer.com/usb-troubleshoot

Submitted by Brassaxe on Fri, 2023/01/13 - 06:14

#10

Everything is updated.

Tried the system check program but it's not helpful because as soon as it tried to run the device disconnects. We have 6 laptops and the one main Desktop with the RFExplorer. The RFExplorer is the only device that does this. But it gets ever stranger. I noticed (maybe I didn't notice before) it restarts the desktop computer when I try to access the RFExplorer from the laptops. How is that possible? I tried to run Eventghost to record this but since the computer restarts all the log data is lost. This computer is only a month or so old.

I also got a response from the RFExplorer Support.

----------------------------------------------------------------------

Hi,

We had a chance to run some testing here and, using a laptop with a virtualhere server and a desktop with a virtualhere client, we could easily connect and run basic tests using RF Explorer for Windows tool

However, we did notice the sweep is sometimes broke and/or got corrupted data. It seems the virtualhere protocol may not be well protected against small network issues. We did not get any disconnect or serious event, but were using ethernet cable reliable connection, maybe with WiFi in an industrial noisy environment the nature of network events is more serious and therefore virtualhere does not handle them in the way you may expect.

If this cannot be resolved in the physical layer (i.e. virtualhere) we may be able to provide a specific retry+crc duplicated data communication for RF Explorer specific for your environment, but it will have a non trivial cost and we cannot guarantee it will work as we do not have access to the underlying technology used by virtualhere.

As an alternative approach, would be feasible for you to use some remote desk tool such as anydesk.com and run RF Explorer for Windows locally on each laptop but handle them remotely from a central desktop that way?
 

Submitted by Michael on Fri, 2023/01/13 - 08:26

#11

 The computer resetting almost seems like a BSOD which didnt show the BSOD screen.  Search google for "Enable Minidumps" and see if something is written to c:\windows\minidump

Every single packet sent from/to a USB device is guaranteed to be transmitted via virtualhere with no errors , and no dropped data. If there is any transmission problems (E.g if your network goes down.) the virtual usb device on the client side with "disconnect" and go back to the server. VirtualHere uses TCP (which is guaranteed to not corrupt data).

What it sounds like is happening is that the rfexplorer uses a Circular Buffer to store its radio sample data inside the device. If the usb signal takes a while to transmit via virtualhere then the data on the device is overwritten with the next sample because the buffer loops back around on itself. Hence it corrupts the data on the device itself. My suggestion is to increase the buffer size of the sample buffer inside the device firmware if possible and that will resolve the issue.

 

Submitted by Brassaxe on Sat, 2023/01/14 - 01:52

#12

Just did the minidump analysis from the latest crash. Its the hub causing the crash, but why... Hmmm.

FILE_IN_CAB:  011223-7562-01.dmp

 

DUMP_FILE_ATTRIBUTES: 0x1008

  Kernel Generated Triage Dump

 

BUGCHECK_CODE:  3b

 

BUGCHECK_P1: c0000005

 

BUGCHECK_P2: fffff80050af2760

 

BUGCHECK_P3: ffff9106fa34e580

 

BUGCHECK_P4: 0

 

CONTEXT:  ffff9106fa34e580 -- (.cxr 0xffff9106fa34e580)

rax=0000000000000001 rbx=0000000000000001 rcx=ffffe208f8a34370

rdx=ffffe208f7e2daa0 rsi=ffffe208f7e2daa0 rdi=ffffe208f55aee30

rip=fffff80050af2760 rsp=ffff9106fa34efa0 rbp=0000000000000000

 r8=ffffe208f7e2df18  r9=0000000000000000 r10=0000000000000000

r11=0000000000000082 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=ffffe208f8a34370

iopl=0         nv up ei pl nz na pe nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202

vhsd_USB+0x2760:

fffff800`50af2760 498b0a          mov     rcx,qword ptr [r10] ds:002b:00000000`00000000=????????????????

Resetting default scope

 

BLACKBOXBSD: 1 (!blackboxbsd)

 

 

BLACKBOXNTFS: 1 (!blackboxntfs)

 

 

BLACKBOXPNP: 1 (!blackboxpnp)

 

 

BLACKBOXWINLOGON: 1

 

CUSTOMER_CRASH_COUNT:  1

 

PROCESS_NAME:  vhusbdwin64.ex

 

STACK_TEXT: 

ffff9106`fa34efa0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000001 ffffe208`f55aee30 : vhsd_USB+0x2760

 

 

SYMBOL_NAME:  vhsd_USB+2760

 

MODULE_NAME: vhsd_USB

 

IMAGE_NAME:  vhsd_USB.sys

 

STACK_COMMAND:  .cxr 0xffff9106fa34e580 ; kb

 

BUCKET_ID_FUNC_OFFSET:  2760

 

FAILURE_BUCKET_ID:  AV_vhsd_USB!unknown_function

 

OSPLATFORM_TYPE:  x64

 

OSNAME:  Windows 10

 

FAILURE_ID_HASH:  {58cea6f1-ce58-a4fd-d12e-9c33bcb821c4}

Submitted by Brassaxe on Sat, 2023/01/14 - 02:26

#13

Also went through and checked all the updates were done on the main desktop computer (They were) and combed thorough every possible firewall or other issue on the network. Nothing helped.

Then I managed to get EventGhost to log something with no crashes. I had EG running on the main computer. On the laptop I selected the RFExplorer usb, and it went to (In Use by You). EG logged it on the main desktop computer as Device Removed, then another log as Attached. All looks good. But when trying to access the device via the RFExplorer software the laptop makes the sound as if the device was removed and nothing happens. EG on the Main desktop doesn't register anything happening, still says it's Attached.

The RF explorer support got back to me and requested I set the device baud rate to 2.4Kbps instead of 500kbps. Didn't help. Confusing how they can get it to work but it doesn't not work for myself. Going to try running the hum on another computer for troubleshooting.

 

Submitted by Brassaxe on Sat, 2023/01/14 - 03:31

#14

Tried some more troubleshooting. Connected the RF Explorer to a laptop on the network and tried to access it from another laptop. Same behavior, can put it (In use) but as soon as I try to use it the computer makes it sound like it disconnects and nothing happens. Also tried it with laptops on a completely other network. Same thing. Also tried two laptops connected directly with Cat6. Same.

Submitted by Michael on Sat, 2023/01/14 - 11:06

#15

Can you make sure the virtualhere server is not running then download the virtualhere server from the playstore and see if that helps https://www.microsoft.com/store/productId/9PK805V256R6  .This server uses a different way to redirect devices so that should fix that BSOD issue.

If that still doesnt work then its not going to work via virtualhere.