Connecting to Virtual Here with my own software

Hello,

I am trying VirtualHere for the first time.

It is installed on a RasPi on my local network.

The USB device connected receives and transmits serial strings at 115200BAUD

I also have a laptop running Windows 10 and my own software developped with Delphi.

I use a Indy TUDPServer that Broadcast and listens on a UDP port presently set at 1241.

Which port does VirtualHere use for serial passthrough?

Many thanks,
E.

#2

I think you are confusing things.

1. Plug your USB device into the pi

2. Use the USB device from the VirtualHere client by right clicking on it and select Use

3. VirtualHere passes through USB data and recreates the USB device remotely on the client

4. You don't parse any VirtualHere protocol. You simply open the serial port on your client pc and use the serial port with your software just as if the serial device was directly plugged into your client.

#3

Is it possible not to use virtualHere client and use my software instead is what I am after.

#4

No that is not possible. I dont think you realize how complicated this software is. The USB spec is very complicated and that needs to be combined with the OS stack and plus the virtualhere software is proprietary.

#5

I tried to install vhusbdarm on the rapberry pi 3B+ and followed the instruction on the website but it is not working

vhusbdarm is downloaded and installed
I see the file on the Rpi
I run: chmod +x ./vhusbdarm
I run sudo ./vhusbdarm -b
I check the running processes using the ps a command
vhusbdarm is not amongst the other processes

I start the vhui64.exe (on windows 10 64-bit computer on the same network)

No devise appear in the list.

Sometime the USB Hubs has a Connecting to USB hubs... coming but nothing shows up.

I tried to plug:
arduino nano
USB dongle
USB-Serial adaptor

nothing shows up

I'd still like to get it working to try it out but so far no luck.

Cheers,
e.

#6

"vhusbdarm is not amongst the other processes"

On the pi, try ps -ef | grep vh does anything show?

#7

something weird just happened

I have had the Pi on for a while and out of nowhere, the com port connected and installed the drivers and it worked .. for about 30 seconds until it disappeared again.

I typed ps -ef | grep vh
I got
root 573 1 0 07:02 ? 00:00:00 /home/pi/vhusbdarm -b
pi 1929 1707 0 07:04 pts/0 00:00:00 grep --color=auto vh

#8

In the virtualhere client right click USB Hubs->System Messages

Let that run for a while, then copy and paste it into here

#9

2021-03-04 11:14:55 INFO :VirtualHere Client 5.1.5 starting (Compiled: Feb 5 2021 11:26:16)
2021-03-04 11:14:55 INFO :Client OS is Windows 10 (build 18363), 64-bit edition
2021-03-04 11:14:55 INFO :Using config at C:\Users\etien\AppData\Roaming\vhui.ini
2021-03-04 11:14:55 INFO :IPC available at \\.\pipe\vhclient
2021-03-04 11:14:55 INFO :Auto-find (Bonjour) on
2021-03-04 11:14:55 INFO :Auto-find (Bonjour SSL) on
2021-03-04 11:15:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:16:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:17:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:17:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:18:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:18:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:19:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:19:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:20:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:20:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:21:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:21:32 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:22:02 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:32:33 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 11:33:03 INFO :Could not connect to 169.254.144.82:7575
2021-03-04 15:38:51 INFO :Could not connect to 169.254.144.82:7575

#10

Looks like it connected for 4 minutes:
2021-03-04 14:56:44 INFO :Connected to the VirtualHere Client Driver (Version 2)

#11

169... is not a proper address, it means your raspberry pi does not have a allocated IP address.

You need to use dhcp on your pi and let that allocate an address and then it will work

#12

Hello not sure why its showing that address.

My Pi is configured with a static IP address 192.168.2.2

I ran ifconfig to check. There is nothing with the address 169.254.144.82

#13

OK i dont know your setup but usually that means its not right.

Anyway in the virtualhere client right click USB Hubs->Specify Hubs and put in the ip address you think the pi is at

#14

sorted.

Thank you for your help