As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

A wheelbase that goes dead mid-race is a nightmare: no warning, no gradual loss of force feedback, just an instant disconnection and a reset pop-up while the field piles past. A common culprit is USB power starvation from an unpowered hub with a button box plugged into it, sitting on the same power rail as the wheelbase connection.

USB dropout isn't random. It's physics. A direct-drive wheelbase like the R9 draws ~5 to 7 amps of current under heavy load. A peripheral like a button box draws 0.5 amps. An unpowered hub can starve the bus. A powered hub with an undersized power supply bottlenecks everything on it. A poorly shielded cable picks up electrical noise. Most troubleshooting guides skip the real why, so you end up guessing. Here's what actually happens and how to fix it.

How USB power and bandwidth share one cable

USB 2.0 and 3.0 cables carry both data and power in the same four to nine wires. Data flows one direction. Power flows the opposite way. A USB 3.0 bus-powered device can draw up to 900 milliamps (0.9 amps). A USB 3.0 self-powered device (one plugged into AC power) can draw 5 amps. Your R9 wheelbase is self-powered: it has its own PSU. But the data line back to your PC still shares the same physical cable as power for upstream devices.

When you chain devices via an unpowered hub, they all compete for power budget from the single port on your motherboard. If that port can only supply 500 milliamps and you plug in a wheel (6 amps self-powered), a button box (0.5 amps), and a shifter (0.3 amps), the math already exceeds what the hub can negotiate. The bus doesn't have enough reserve to handle a power spike from your wheelbase firmware polling or a sudden motor load. Something drops.

Why unpowered hubs cause mid-race disconnects

An unpowered hub (also called a bus-powered hub) has no AC adapter. It draws all its power from the USB port it plugs into. When multiple devices plug into an unpowered hub, the motherboard's USB controller has to allocate power to each one. If total draw exceeds the port's budget, the controller cuts power to the lowest-priority device. That's usually your peripheral, not your wheel, but the wheel can still reset if its data line gets starved.

Hub Type Matters

Check your hub's label. If it says 'bus-powered' or shows only a USB input (no AC barrel jack), it draws power from your PC. Toss it. A powered hub must have its own AC power supply rated for at least 2 amps total output to safely run your rig.

The real power budget of your rig

A direct-drive wheelbase like the R9 draws ~5 to 7 amps under heavy transient load (sudden FFB spike during a curb hit). A set of load-cell pedals can draw ~0.3 amps. A button box with 32 buttons and 2 encoders draws 0.5 to 1 amp depending on backlighting. A sequential shifter pulls 0.2 amps. A handbrake adds another 0.5 amps. That's 6.5 to 10 amps total during peak load on a single rig with all of these devices.

Your PC motherboard typically provides 500 mA per USB 2.0 port and 900 mA per USB 3.0 port. Most boards have 4 to 6 USB 3.0 ports sharing a single controller chip. If you plug the wheelbase into one port, the pedals into another, and a hub into a third, you're using three of your board's power budgets. The hub itself gets 900 mA, which it must divide among everything plugged into it. If a button box, shifter, and handbrake live on that hub, they're fighting for 900 mA total. It works until a 2000 Hz FFB update spike sucks current and the controller yanks power.

Cable quality and shielding amplify the problem

Poor shielding or long cable runs introduce capacitive and inductive coupling. Electrical noise from your PSU (especially under heavy load), your monitor refresh, your graphics card, and even your WiFi router can couple into USB data lines. A USB controller interprets this noise as signal corruption. Multiple bit errors in a row trigger a port reset. The port powers off and back on. Your device disconnects and reconnects.

Avoid running the wheelbase USB cable alongside an unshielded power strip, which is bad practice and can make dropouts far more frequent. Run the USB cable alone and separate it from power cables by 12 inches. Shielded USB cables and good cable routing aren't luxuries for race rigs; they're essentials.

Powered hub specifications and how to choose

A powered hub's AC supply must deliver enough current for all connected devices plus a safety margin. If your wheelbase and pedals draw 7.5 amps (self-powered, so they bypass hub power), but your button box, shifter, and handbrake draw 2 amps total, your hub's PSU needs to supply at least 3 amps at 5 volts. That's 15 watts. Most hub PSUs are rated in amps, not watts, so check both figures. A hub labeled '2A, 5V' is actually 10 watts, which works for a button box alone. A hub labeled '3A, 5V' is 15 watts, enough for a typical peripheral setup.

Look for hubs with per-port current limiting or switchable charging. Some hubs let you disable individual ports if a device is misbehaving. Avoid passive hub designs (metal boxes with no power management). A $40 powered hub from a reputable maker (Anker, Belkin, or Startech) beats a $15 no-name hub every time. If you have a multimeter or oscilloscope, check the hub's bus voltage under load: a proper hub PSU should hold 4.95 to 5.05 volts. A cheap PSU that sags to 4.7 volts can trigger dropout thresholds in sensitive devices.

Optimal cable architecture for your rig

Plug your wheelbase directly into a USB 3.0 port on your motherboard (not a hub). Plug your pedals directly into another USB 3.0 port. Both devices are self-powered, so they don't compete for hub power. A powered hub can then serve your button box, shifter, handbrake, and other accessories. This gives you 900 mA of hub power for peripherals and isolates your critical racing hardware from hub contention.

If your motherboard has only two USB 3.0 ports and you need more, buy a second powered hub for your wheel and pedals to share. Don't plug both into the same hub. Most boards have 2 to 4 physical USB 3.0 ports, each with independent power lanes inside the chipset. Use them. Reserve hub power for low-draw devices.

  1. Wheelbase to USB 3.0 port 1 (motherboard)
  2. Pedals to USB 3.0 port 2 (motherboard)
  3. Powered hub (rated 2+ amps) to USB 3.0 port 3 (motherboard)
  4. Button box, shifter, handbrake, and lower-priority devices to the powered hub
Port Hierarchy

Check your motherboard's USB block diagram in the manual. Most boards have at least one or two USB 3.0 ports that bypass the southbridge and connect directly to the CPU. Use those for your wheelbase and pedals. Lower-speed ports can handle hubs fine.

Firmware and driver updates mask the real issue

If you've experienced dropout, your instinct might be to update your wheel's firmware or install fresh drivers. Sometimes that helps, but often it just masks a power supply problem. Firmware updates can include improved power negotiation algorithms. Drivers can add retry logic. But if your hub PSU is undersized or your cable is poor, the problem will return under higher load or after a few hours of racing.

Before you waste time on driver loops, test your physical setup. Swap to a known-good powered hub. Swap to a new shielded cable. Plug directly into the motherboard. If dropout stops, your firmware was never the problem. If dropout persists after all hardware changes, then file a support ticket with MOZA or your wheelbase maker and include your USB configuration details.

From the RealiRacing shop

Before your next session, free up your rig. NWM PitStop is the clean-up + stream-priority script set we run before every session — our own product, not a third-party pick. See NWM PitStop →

The gear in this guide
PickWhy it made the listTested?
MOZA R9 Direct Drive Wheelbase9 N·m direct drive — the base bolted to my rig right nowRaced on
MOZA CRP2 Load Cell Pedalsload-cell brake, managed in the same Pit House softwareResearched pick

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links — I may earn a commission at no cost to you.

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

My wheelbase disconnects every 2 to 3 hours of racing, but not during short sessions. What's happening?

Prolonged racing generates heat inside your PC and in hub electronics. Thermal drift in PSU output voltage combined with increased current draw from longer sessions will reveal marginal power supplies. A hub PSU rated barely high enough at room temperature will sag when warm. Test with a higher-capacity powered hub (3+ amps rated) or plug your wheelbase directly into the motherboard to isolate hub involvement.

I have a Fanatec CSL DD, not a MOZA wheel. Does this apply to me?

Yes. Any direct-drive wheelbase draws 5 to 8 amps under load. Fanatec, SimXperience, Accuforce, and MOZA wheelbases all exhibit the same dropout pattern when powered through undersized hubs. The principle is universal: hub power budgets are small, and transient motor spikes exceed them quickly. Plug your wheelbase directly into the PC.

Can I use a USB extension cable to reach my motherboard without a hub?

Active (powered) extension cables work fine. Passive (unpowered) extension cables degrade signal and can introduce dropout, especially if longer than 10 feet. Passive cables are cheaper but they're a false economy. Buy a good powered hub or a powered extension cable if you need distance. Never daisy-chain unpowered hubs or extensions.

What's the difference between a 'powered hub' and a hub with 'pass-through charging'?

A powered hub has its own AC supply and powers its ports. Pass-through charging means the hub also charges a phone or tablet plugged into a dedicated port while forwarding power to other ports, but the AC supply is still shared. For sim racing, a simple powered hub without pass-through charging is cleaner. Fewer devices competing for power means more stable rail voltage.