Moza R5 + Assetto Corsa Competizione = Freeze

Submitted by sieskei on #1

Hello,

First, I want to congratulate you on the amazing work! The software you offer is fantastic!

The issue is that when I use the Moza R5 through VirtualHere, the game freezes at the start of a race. When it’s connected via cable (20 meters), this problem doesn’t occur. Other games like Forza Motorsport 8, Dirt Rally 2.0, etc works perfectly.

I'm using a Pi Zero 2W with a wired connection. The latency is between 1 and 2 milliseconds.

Settings I’ve tried without success include CompressionLimit and ClaimPorts.

The logs look normal; nothing unusual appears.

I would be very grateful if you could guide me on what I could test.
Best Regards,
Miro!

Submitted by Michael on Sat, 2024/11/09 - 15:38

#2

My guess is that its probably the USB hub actually. Im assuming you are using one of those hubs with the built-in ethernet port? They have only "1 TT" which can cause issues with wheels etc. Do you have any other hub you can try?

Submitted by sieskei on Sat, 2024/11/09 - 18:44

#3

Hello, thanks for the response.

Yes, I am using this type of USB hub (usb hat with pogo pins) where the LAN adapter is connected via USB. You’re right—using lsusb -v | grep -i tt shows only 1 TT.

I have two more hubs, also with LAN, but they are quite budget-friendly as well. I don’t expect them to support multi-TT.

Could I test it by using WiFi and connecting only the Moza to the micro-USB port? The performance might be poor, but at least for testing?

Submitted by Michael on Sat, 2024/11/09 - 19:33

#4

You could test via wifi if the pi is really close to the router it might be ok

Submitted by sieskei on Sat, 2024/11/09 - 20:38

#5

I tried without the USB hub (via WiFi) and it still doesn't work.

Dump without device.
Does this mean that the built-in controller does not support MTT?
In that case, does it matter what USB hub I use?

/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M

admin@pi0:~ $ sudo lsusb -s 1:1 -v

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
 bLength                18
 bDescriptorType         1
 bcdUSB               2.00
 bDeviceClass            9 Hub
 bDeviceSubClass         0
 bDeviceProtocol         1 Single TT
 bMaxPacketSize0        64
 idVendor           0x1d6b Linux Foundation
 idProduct          0x0002 2.0 root hub
 bcdDevice            6.06
 iManufacturer           3 Linux 6.6.51+rpt-rpi-v8 dwc_otg_hcd
 iProduct                2 DWC OTG Controller
 iSerial                 1 3f980000.usb
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength       0x0019
   bNumInterfaces          1
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0xe0
     Self Powered
     Remote Wakeup
   MaxPower                0mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           1
     bInterfaceClass         9 Hub
     bInterfaceSubClass      0
     bInterfaceProtocol      0 Full speed (or root) hub
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            3
         Transfer Type            Interrupt
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0004  1x 4 bytes
       bInterval              12

Submitted by Michael on Sat, 2024/11/09 - 20:42

#6

Yes that looks to be the case. From searching this forum, the pi5 is a good platform as a usb server for the moza

Submitted by sieskei on Sat, 2024/11/09 - 21:43

#7

Lol, very strange.
I have a Pi 5 (which I use for different purposes), and lsusb shows the same results, again 1 TT, BUT IT WORKS.
I tested it on both USB 2.0 and 3.0 ports, and it works on both.

Do you have any idea why?

 Is there anything that can be done to make it work on the Pi Zero, or is the issue entirely hardware-related?
Thank you in advance!

Submitted by Michael on Sat, 2024/11/09 - 21:48

#8

That is surprising, i dont know how the USB dwc IP (Intellectual Property) exactly is implemented in the broadcom chip maybe it really is multi-TT

Submitted by sieskei on Sun, 2024/11/10 - 01:11

#9

Very strange indeed. I just checked and even this 20-meter USB extender has a hub with 1 TT. I even tested the Pi 5 with this extender to make sure it goes through a 1 TT hub, and it still works.

I’d be happy to help if there’s any way to debug/log the situation further.

Submitted by Michael on Sun, 2024/11/10 - 08:29

#10

Maybe its just the slow cpu in the pi02w.

normally the single TT causes issue when at least two full speed (or low speed) USB devices are plugged into the same hub. Does that wheel setup have more than one usb cable you need to plug in?