Problems on raspberry pi 4

Hi, i'm an usual user of virtual here in the windows version, and now i'm trying to switch part of the setup to a raspberry.

My setup is a windows 10 computer with the client and then a raspberry pi 4 connected on lan for game streaming using moonlight. This setup is used for simracing so I need virtual here for connecting my steering wheel to the windows computer.

My problem is that, despite the fact that everything connects and works fine, after some seconds of gaming the steering wheel stops working, and it is a very strange situation. Some times I lose the force feedback (The feedback of the steering wheel) and sometimes I lose the input to the steering. It seems like it loses conectivity only for one side of the connection. I have tried too to connect only the steering and disable the streaming and that works fine, and if I use the streaming with the lowest resolution it works fine too.

Any idea of what is happening? Is there any log I can read?

Thanks in advance

#2

Oct 5 22:59:59 raspberrypi vhusbdarm[915]: Unmanaging device 111 [046d:c260]
Oct 5 22:59:59 raspberrypi kernel: [ 1436.767196] usb 1-1.1: USB disconnect, device number 10
Oct 5 23:00:00 raspberrypi kernel: [ 1437.573065] usb 1-1.1: new full-speed USB device number 11 using xhci_hcd
Oct 5 23:00:00 raspberrypi kernel: [ 1437.709855] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c24f, bcdDevice=89.00
Oct 5 23:00:00 raspberrypi kernel: [ 1437.709868] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 5 23:00:00 raspberrypi kernel: [ 1437.709877] usb 1-1.1: Product: G29 Driving Force Racing Wheel
Oct 5 23:00:00 raspberrypi kernel: [ 1437.709887] usb 1-1.1: Manufacturer: Logitech
Oct 5 23:00:00 raspberrypi vhusbdarm[915]: Found Full speed device [046d:c24f] "Logitech, G29 Driving Force Racing Wheel" at address 111
Oct 5 23:00:00 raspberrypi mtp-probe: checking bus 1, device 11: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Oct 5 23:00:00 raspberrypi mtp-probe: bus: 1, device: 11 was not an MTP device
Oct 5 23:00:00 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c24f
Oct 5 23:00:00 raspberrypi vhusbdarm[915]: Device 111 [046d:c24f] BOUND to connection 1
Oct 5 23:00:01 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c24f
Oct 5 23:01:45 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c24f
Oct 5 23:01:45 raspberrypi kernel: [ 1542.767701] usb 1-1.1: USB disconnect, device number 11
Oct 5 23:01:45 raspberrypi vhusbdarm[915]: Device 111 [046d:c24f] SURPRISE UNBOUND from connection 1
Oct 5 23:01:45 raspberrypi vhusbdarm[915]: Unmanaging device 111 [046d:c24f]
Oct 5 23:01:54 raspberrypi kernel: [ 1551.765278] usb 1-1.1: new full-speed USB device number 12 using xhci_hcd
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Found Full speed device [046d:c260] "Logitech, G29 Driving Force Racing Wheel" at address 111
Oct 5 23:01:55 raspberrypi kernel: [ 1551.899676] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c260, bcdDevice=89.00
Oct 5 23:01:55 raspberrypi kernel: [ 1551.899692] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 5 23:01:55 raspberrypi kernel: [ 1551.899698] usb 1-1.1: Product: G29 Driving Force Racing Wheel
Oct 5 23:01:55 raspberrypi kernel: [ 1551.899706] usb 1-1.1: Manufacturer: Logitech
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c260
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Device 111 [046d:c260] BOUND to connection 1
Oct 5 23:01:55 raspberrypi mtp-probe: checking bus 1, device 12: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Oct 5 23:01:55 raspberrypi mtp-probe: bus: 1, device: 12 was not an MTP device
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c260
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Device 111 [046d:c260] SURPRISE UNBOUND from connection 1
Oct 5 23:01:55 raspberrypi vhusbdarm[915]: Unmanaging device 111 [046d:c260]
Oct 5 23:01:55 raspberrypi kernel: [ 1552.241206] usb 1-1.1: USB disconnect, device number 12
Oct 5 23:01:56 raspberrypi kernel: [ 1553.045290] usb 1-1.1: new full-speed USB device number 13 using xhci_hcd
Oct 5 23:01:56 raspberrypi kernel: [ 1553.182382] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c24f, bcdDevice=89.00
Oct 5 23:01:56 raspberrypi kernel: [ 1553.182395] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 5 23:01:56 raspberrypi kernel: [ 1553.182405] usb 1-1.1: Product: G29 Driving Force Racing Wheel
Oct 5 23:01:56 raspberrypi kernel: [ 1553.182414] usb 1-1.1: Manufacturer: Logitech
Oct 5 23:01:56 raspberrypi vhusbdarm[915]: Found Full speed device [046d:c24f] "Logitech, G29 Driving Force Racing Wheel" at address 111
Oct 5 23:01:56 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c24f
Oct 5 23:01:56 raspberrypi vhusbdarm[915]: Device 111 [046d:c24f] BOUND to connection 1
Oct 5 23:01:56 raspberrypi mtp-probe: checking bus 1, device 13: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Oct 5 23:01:56 raspberrypi mtp-probe: bus: 1, device: 13 was not an MTP device
Oct 5 23:01:56 raspberrypi vhusbdarm[915]: Executed "" for onReset.046d.c24f

#3

I think you need to put a separately powered usb hub between the wheel and the pi because i suspect its a power issue

#4

I have bought a powered USB hub, the problem is exactly the same. Same log. Is there any configuration I can try for virtual here server that could help?

#6

Tried 5 times in a row, nothing new. I´ve been looking on dmesg too, but doesn´t show any log in the moment of desconection.

#7

Could it be caused by connection? The device only disconnects when I start moving in game. Or maybe it is when the CPU is stressed. There is no warning of undervolt.

#8

In the log of virtual here I can see that it is sending on reset and then the surprise unbound happens, can I disable that reset?

#9

Actually it is skipping resets automatically for the G29.

For example in the log it shows its skipping them

Executed "" for onReset.046d.c24f

You could try this

1. Stop the virtualhere server (sudo pkill vhusbdarm)
2. Edit the config.ini file and add the line
3. ClaimPorts=1
4. Save the config.ini file and then start the server again
5. Unplug and replug the wheel
6. Try to use it again now via virtualhere

#10

Didn't work, same problem. This is a little bit stressful. I can see other people using the same configuration and working properly. :(

#11

What is your latency like? In the virtualhere client right click USB Hubs->About->Statistics.

#12

I don't know how to post images, is more o less constant in 1 ms with some peaks to 3 ms

#13

OK that should be totally fine. Do you have any other pi or something you can test with?

#14

I don't have any other pi but now I am trying a laptop with the exact same setup, disconnect from the pi and connect to the laptop directly and it works perfectly fine, without any lag. But I don't think it's a performance issue, the pi gets about 40% of CPU usage when it fails.

#15

Ok im not sure sorry, im out of ideas for this one

#16

No problem, thank you for your time. If I have something new I will tell you.