Why Your Wheel Isn't Being Detected
GSI wheels expose two interfaces over a single USB connection: a HID interface (buttons, paddles, encoders) and a serial interface (screen and LEDs). Either or both can fail to enumerate if USB power, drivers, or software aren't set up correctly.
Work through the sections below in order. Most issues are resolved in the first two.
⚠️ Firmware update stuck? If your wheel was detected and you started a firmware update that is now frozen on "Preparing Device… Wait for DFU", stop here and follow this article instead: Wheel Firmware Update stalls on "Preparing Device… Wait for DFU".
Step 1 — USB Basics
These fix the majority of detection failures.
- Restart SimOS or SimHub with the wheel already plugged in. Both apps enumerate devices at launch — plugging in after the app is open can cause the wheel to be missed.
- Unplug and re-plug the USB cable. Listen for the Windows device-connect chime. If you hear it, the wheel is visible to Windows and the issue is software-side. No chime = USB or hardware problem.
- Plug directly into a rear motherboard USB port — no hubs, no extension cables, no front-panel ports — just for this test.
- Update SimOS. Open SimOS → click the version number → check for updates. Older versions may not recognise newer wheel firmware.
Step 2 — USB Power & Port
Use a powered USB hub
GSI wheels are high-bandwidth devices. The screen, LEDs, and HID data all share a single connection and require more power than many motherboard ports deliver reliably. A powered (self-powered) USB hub is required for consistent detection.
💡 Use a 4-port or fewer powered hub connected to a dedicated USB 3.0 rear motherboard port. Connect only the GSI wheel to it — don't share it with pedals or other peripherals.
⚠️ Never use USB extension cables. Even short ones degrade signal integrity enough to cause detection failures. Extend the hub's upstream cable if you need reach, not the wheel's cable.
Disable USB power management
Windows can silently power down USB devices, causing them to vanish from SimOS and SimHub.
- Open Device Manager → expand Universal Serial Bus controllers.
- Right-click each USB Root Hub → Properties → Power Management tab.
- Uncheck "Allow the computer to turn off this device to save power." Repeat for all root hubs.
- Unplug and re-plug the wheel, then relaunch SimOS.
Step 3 — SimOS Not Finding the Wheel
"No devices to display"
- Close SimOS. Plug the wheel in and wait 10 seconds. Then open SimOS.
- Open Device Manager — the wheel should appear without a warning icon under Human Interface Devices or Universal Serial Bus controllers. If it's not there at all, return to Step 1.
- Right-click the SimOS shortcut → Run as administrator. Some Windows configurations restrict USB device access for non-elevated processes.
Step 4 — SimHub Not Communicating with Wheel
Wheel found but LEDs or screen don't respond
- In SimHub → Dash Studio, confirm a dash is deployed to the wheel — not just open in the editor. Hit Deploy and select your wheel.
- For RPM LEDs: go to LED Manager → Rev Lights and confirm the correct device is selected as the LED target.
Step 5 — Stopped Working After a Change
- New quick-release installed
- Some pass-through QRs carry button data only — the screen requires a data-capable QR or the USB cable plugged in directly. Check your QR manufacturer's docs.
- SimHub or SimOS updated
- Re-enable the GSI device in SimHub → Controllers and Inputs. Re-deploy your dash.
- Thrustmaster or Fanatec drivers installed
- Toggle Third Party Driver Mitigation in SimOS Settings, or disable those drivers' background services.
- More USB devices added to setup
- Move the GSI wheel to a port on a different USB controller. Use USB Device Tree Viewer (free) to find an uncrowded port.
- Moved the PC or changed cable routing
- Test with a different cable. If detection returns, the coiled cable is faulty — open a ticket.
Partial Detection — Some Features Work, Others Don't
- Buttons work but screen / LEDs are dead
- The USB port is likely marginal on power. Switch to a powered hub. Also confirm a dash is deployed in SimHub, not just open.
- Screen shows splash logo but buttons aren't recognized in-game
- Press Win + R, type joy.cpl, and check that the wheel appears and responds to button presses. If it does, the issue is the game's controller binding — rebind inputs in the game settings.
- Interlock or GTMax32 — LED matrix not showing
- The matrix is a separate SimHub device. Add it independently in Dash Studio and deploy a layout specifically to it.
Still Not Working?
Open a support ticket and include the following:
- Wheel model and serial number (printed on the back of the wheel)
- SimOS version and SimHub version
- Wheel base and whether you're using a pass-through QR
- Screenshot of Device Manager (USB Controllers and HID sections) with the wheel plugged in
- Screenshot of what SimOS shows in its device list
- What changed before the issue started, if anything
ℹ️ Related articles:
Steering Clear of Disconnects — wheel drops out mid-session
Firmware Update stalls on "Preparing Device… Wait for DFU" — update is stuck