Thrustmaseter T150 Pro

Submitted by xtentor on #1

Hello.

I've tried to use your software in multiple different scenarios. 

  1. Android server (Nvidia Shield TV)
  2. Linux server(Synology)

Also for these servers, I've tried to use 2 different clients, both on Windows 11. 

 T150 was tested in 2 different modes, PS3 and PS4.

In all situations and all servers on PS3 mode, I'm getting the device name "Thrustmaster FFB Wheel (USB)" which can't start with error code 10.

With PS4 mode I can get 3 devices, one USB input device, and 2 HID devices, but I can get only buttons working with these drivers. 

Is there anyone who has had a successful experience establishing a connection with this wheel by using Virtualhere? 

 

In the server log, I have:

Sat Aug 17 21:10:24 2024 LOG_INFO    Unmanaging device 13 [044f:b65d]
Sat Aug 17 21:10:26 2024 LOG_INFO    Found Full speed device [044f:b65d] "Thrustmaster, Thrustmaster FFB Wheel" at address 13
Sat Aug 17 21:11:05 2024 LOG_INFO    Executed "" for onReset.044f.b65d
Sat Aug 17 21:11:05 2024 LOG_INFO    Device 13 [044f:b65d] BOUND to connection 1
Sat Aug 17 21:11:06 2024 LOG_INFO    Executed "" for onReset.044f.b65d
 

Please advise how to fix this.

Submitted by Michael on Mon, 2024/08/19 - 11:13

#2

I have a T150 (not the PRO) that i test with, and tested then by plugging it into my Pixel 8 android phone running virtualhere server.

It did work but you need to be aware that when the wheel is used via virtualhere it begins showing Thrustmaster FFB Wheel,  and then Android will show a popup and you need to give permission to allow access via virtualhere

Then once you use the wheel via virtualhere it will reboot and switch modes and come back as T150RS (or similar) you need to give Android permission to access this new "device" because it appears to android as a different device (even though its the same physical device) and then use that via virtualhere.

Once you do that it should work ok. You can use the checkboxes in the popups to remember these settings so you dont have to click them all the time.

Submitted by xtentor on Tue, 2024/08/20 - 04:28

#3

Hello Michael,

Thanks for your reply, but please check my post closely, the problem is not only with Android, I have Linux as a host, and the problem is the same there. So I think it's something different.

Submitted by Michael on Tue, 2024/08/20 - 05:45

#4

Im assuming you have the thrustmaster drivers installed where the virtualhere client is running? If so then i dont know the problem

Submitted by xtentor on Wed, 2024/08/21 - 07:04

#5

Michael,

Thanks for your reply, Do you have any suggestions for diagnosing this issue?

Submitted by Michael on Wed, 2024/08/21 - 07:46

#6

Do you have the thrustmaster drivers installed on the client?

Submitted by xtentor on Wed, 2024/08/21 - 10:39

#7

Michael,

Sure I have, I've tried to use Virtualhere without drivers, on the android server and I had only one HID device which threw error 10. But on Linux, I had 3 HID devices without issues and when I installed the driver it still threw error 10.  Let's leave Android, as it's useless. I'm trying to pass this device via Linux, so I can provide logs, I have root access. Please help me.

Regards,

Submitted by Michael on Wed, 2024/08/21 - 10:52

#8

Stop the virtualhere server process on linux. Then edit the config.ini file and add the line

ClaimPorts=1

Then start the server again and then unplug/replug the wheel and let me know if that helps

Submitted by xtentor on Thu, 2024/08/22 - 05:22

#9

Michael, 

Thanks a lot for your suggestion!!! This fixed the issue and I can use Thrustmaster T150 Pro !!! Running to buy the license of your perfect software!!!

Just a small comment to someone who needs something similar, to what I did on Synology NAS:

  1. Checked service status and config file location:
    root@NAS:~# systemctl status pkgctl-VirtualHere
    ● pkgctl-VirtualHere.service - VirtualHere's service unit
      Loaded: loaded (/usr/local/lib/systemd/system/pkgctl-VirtualHere.service; enabled; vendor preset: disabled)
      Active: active (exited) since Wed 2024-08-21 21:08:00 CEST; 9min ago
     Process: 22288 ExecStop=/bin/bash -c /usr/syno/sbin/synopkgctl stop $SELF && /bin/rm -f /var/packages/$SELF/enabled (code=exited, status=0/SUCCESS)
     Process: 22920 ExecStart=/bin/bash -c /usr/syno/sbin/synopkgctl start $SELF && /bin/touch /var/packages/$SELF/enabled (code=exited, status=0/SUCCESS)
    Main PID: 22920 (code=exited, status=0/SUCCESS)
      CGroup: /VirtualHere.slice/pkgctl-VirtualHere.service
              └─22962 /volume1/@appstore/VirtualHere/vhusbdx86_64 -b -r /var/log/virtualhere.log -c /volume1/@appstore/VirtualHere/config.ini
     

  2. Changed config file as suggested:

    root@NAS:~# grep Claim /volume1/@appstore/VirtualHere/config.ini
    ClaimPorts=1

  3. Restarted service:

    root@NAS:~# systemctl restart pkgctl-VirtualHere

 

A small part from the log file:

Wed Aug 21 21:08:00 2024 LOG_INFO    >>> Starting VirtualHere USB Server v4.3.2 (Built: Jun 22 2021, 13:06:30)<<<
Wed Aug 21 21:08:00 2024 LOG_INFO    Using configuration /volume1/@appstore/VirtualHere/config.ini
Wed Aug 21 21:08:00 CEST 2024 Started successfully
Wed Aug 21 21:08:00 2024 LOG_INFO    Server licensed to=unlicensed max_devices=1
Wed Aug 21 21:08:00 2024 LOG_INFO    Using large URB's
Wed Aug 21 21:08:00 2024 LOG_INFO    Listening on all network interfaces at TCP port 17570
Wed Aug 21 21:08:00 2024 LOG_INFO    Claiming 8 ports on hub /proc/bus/usb/001/001
Wed Aug 21 21:08:00 2024 LOG_INFO    Claiming 7 ports on hub /proc/bus/usb/002/001
Wed Aug 21 21:10:24 2024 LOG_INFO    Found Full speed device [044f:b65d] "Thrustmaster, Thrustmaster FFB Wheel" at address 13
Wed Aug 21 21:11:32 2024 LOG_INFO    192.168.0.40 connected as connection 1
Wed Aug 21 21:11:44 2024 LOG_INFO    Executed "" for onReset.044f.b65d
Wed Aug 21 21:11:44 2024 LOG_INFO    Device 13 [044f:b65d] BOUND to connection 1
Wed Aug 21 21:11:45 2024 LOG_INFO    Executed "" for onReset.044f.b65d
Wed Aug 21 21:11:47 2024 LOG_INFO    Device 13 [044f:b65d] SURPRISE UNBOUND from connection 1
Wed Aug 21 21:11:47 2024 LOG_INFO    Unmanaging device 13 [044f:b65d]
Wed Aug 21 21:11:48 2024 LOG_INFO    Found Full speed device [044f:b677] "Thrustmaster, Thrustmaster T150RS" at address 13
Wed Aug 21 21:13:22 2024 LOG_INFO    Executed "" for onReset.044f
Wed Aug 21 21:13:22 2024 LOG_INFO    Device 13 [044f:b677] BOUND to connection 1
Wed Aug 21 21:13:22 2024 LOG_INFO    Executed "" for onReset.044f
Wed Aug 21 21:14:12 2024 LOG_INFO    Device 13 [044f:b677] UNBOUND from connection 1
Wed Aug 21 21:14:15 2024 LOG_INFO    Executed "" for onReset.044f
Wed Aug 21 21:14:15 2024 LOG_INFO    Device 13 [044f:b677] BOUND to connection 1
Wed Aug 21 21:14:15 2024 LOG_INFO    Executed "" for onReset.044f
 

Many thanks again to Michael!

Submitted by Michael on Thu, 2024/08/22 - 08:25

#10

Excellent, thats great news, and helpful for others too