Hello support,
my problem is on linux ubuntu virtual here server.
We use a spectrofotometer to read a color value.
This device is phisically connected on linux machine where running vh server.
Unfortunatly during color reading/analisys I got on vh server logs tons of " Error 22 discarding urb ....."
The device is identify itself as
|__ Port 10: Dev 9, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
ID 0765:3040 X-Rite, Inc.
/sys/bus/usb/devices/3-10 /dev/bus/usb/003/009
The device is costantly powered by a separated power supply.
The VH server is a vhusbdx86_64hw v4.5.6
VirtualHere USB Server for Linux Desktop (Optimized build)
The machien where VH server is installed is an Ubuntu is 20.04.5 LTS
and the kernel is 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:53:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
The vh client is 5.4.7 and running on windows 10 virtual machine
I running the server (licensed and as service) with these config:
● virtualhere.service - VirtualHere Server
Loaded: loaded (/etc/systemd/system/virtualhere.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-12 07:13:37 CEST; 5 days ago
Main PID: 936 (vhusbdx86_64hw)
Tasks: 22 (limit: 6931)
Memory: 24.9M
CGroup: /system.slice/virtualhere.service
└─936 /opt/virtualhere/vhusbdx86_64hw -b -c /opt/virtualhere/config.ini -r /var/log/virtualhere.log
the content of config.ini:
more /opt/virtualhere/config.ini
It=1611653426
EasyFindId=XpgHLFfSMZmTNq6vNWwbgm
EasyFindPin=2nTdb2
Servername=$HOSTNAME$
ClaimPorts=1
#Con AutoAttachToKernel=1 la tastiera funziona...
AutoAttachToKernel=1
#AutoAttachToKernel=0
AllowedDevices=471/485e,765/3040,529/0001
License=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CompressionLimit=768
#onReset.0765.3040=
I need to solve this frustrating problem!
Any ideas??
Thank you!
.
Can you tell me the exact model of the https://www.xrite.com/page/color-spectrophotometer
Can you also run the virtualhere client on windows and see if that works (instead of the linux client) if possible. Keep linux as the server
.
Hello Michael,
this is our device:
https://www.xrite.com/it-it/categories/portable-spectrophotometers/exact
Vh client is running on windows 10 so is the windows client; Only it run on virtualized win10.
Only the server is running on Linux ubuntu.
.
Sorry i misread, i see you are using the windows client already.
I dont think its going to be compatible because usually when that sort of error occurs it means the device cannot upload its data quick enough (i.e the network latency is too high)
Is the virtualhere client <-> Server connected via wifi or ethernet?
.
>>Is the virtualhere client <-> Server connected via wifi or ethernet?
Is an ethernet connection.
I'll try to check the latency and in my samples I noted peak about 54msec.
The standard is about 30msec...
These values are evidence for your guess?
.
30ms! For ethernet, that is really bad. Is this over a VPN? I think that is your issue. I suspect it needs to be < 5ms
.
Unfortunatly is passing trougth old devices and cables.
I'll try to move in other location to get better result and I'll let you know...
.
Hello,
today I have dose some iperf test and latency I measured are in range from 0.5 to 1.5 msec.
What I mesasured was the jitter so it was the udp traffic.
These values sound strange for you if compared to your latency graph?
.
The latency graph shows what the latency actually is between virtualhere server and client. This uses TCP
Right click USB Hubs->About->Statistics and watch that graph. Is that the graph you are looking at?
.
Yes correct, but if your graph is in tcp, my values are incomparable 'cause are in udp.
.
Im confused, so the virtualhere client is showing 30-54ms or 0.5 to 1ms?
>>>30-54ms This is what I…
>>>30-54ms
This is what I see in your graph ( as you explain, you use a TCP)
>>>0.5 to 1ms
This is what I measured by iperf tool using UDP.