5. Troubleshooting¶

5.1 General Troubleshooting Steps¶

Before diving into specific issues, try these general troubleshooting steps that resolve many common problems:

5.1.1 Reset to Factory Defaults¶

If you’re experiencing unexpected behavior, instability, or effects issues, resetting to factory defaults is an excellent first troubleshooting step:

1. Open VPforce Configurator
2. Click “Factory Reset” button
3. Click “Import Rhino Defaults” button
4. Click “Store Settings” to save

This ensures you’re working with known-good baseline settings and eliminates configuration issues as a potential cause.

5.2 Power Issues¶

5.2.1 Base Does Not Power On At All¶

Issue:
The Rhino base shows no signs of life - no LED indicators, no response when connected, and does not appear in Windows Device Manager or VPforce Configurator.

Understanding Rhino’s Power System:

The Rhino has two separate power systems:

1. USB Power (5V): Powers the control electronics, USB communication, and status LEDs
2. DC Power (20V): Powers the motors and drive electronics

If the base does not power on at all, the USB power path is the most likely culprit.

5.2.1.1 Quick Troubleshooting Checklist¶

Before diving into detailed diagnostics, try these essential steps:

1. Verify USB connection - Ensure the USB cable is firmly seated and try a different USB cable if available
2. Try different USB ports - Test multiple USB ports (rear panel preferred over front panel)
3. Eliminate USB hubs - Disconnect any USB hubs and connect the Rhino directly to a motherboard USB port
4. Check Device Manager - Press Win + X and open Device Manager to verify Windows detects the device
5. Test DC power connection - Verify the DC barrel jack is firmly seated on the back of the Rhino

5.2.1.2 Common Causes and Solutions¶

1. Faulty USB Cable

USB cables are a frequent point of failure, particularly if subjected to repeated bending or tension:

• Verification: Test the cable with another USB device (mouse, keyboard, etc.)
• Solution: Replace with a high-quality USB cable (USB 2.0 is sufficient; keep cable under 3 meters)

2. USB Port Issues

Some motherboard USB ports have poor power delivery or signal integrity:

• Solution: Test multiple USB ports systematically and prefer motherboard rear-panel USB ports over front-panel ports
• Front-panel ports often have longer internal cables and higher insertion losses

3. USB Hub Power Delivery

USB hubs, especially unpowered hubs, can fail to provide adequate power:

• Solution: Always connect the Rhino directly to a motherboard USB port
• If a hub is absolutely necessary, use a powered USB hub with external power supply

4. Electrical Noise or Ground Loops

Electrical noise from the PC’s USB bus can prevent proper device recognition:

• Solution: Use a USB isolator to eliminate noise (see 5.3.4 USB Isolator Recommendation section)
• This is particularly effective in systems with many high-power devices

5. DC Power Connection Issue

Even with USB detection, a loose DC connection can prevent the device from initializing:

• Solution: Firmly reseat the DC barrel jack connector on the back of the Rhino
• Ensure DC power is being supplied to the board (the board should initialize after USB detection)

6. Mainboard Damage (Rare)

In rare circumstances, the Rhino mainboard can be damaged by:

• Electrostatic discharge (ESD) during handling
• Ground loops between PC and power supply — especially when reconnecting power or if the DC ground connection is unstable (see 5.3.4 USB Isolator Recommendation)

• Voltage transients on the USB bus

• Solution: If all troubleshooting steps fail and you’ve verified the USB cable, ports, and DC connection are good, the mainboard may be damaged

• Contact VPforce support for further diagnostics and potential RMA

5.2.2 Device Powers On But Motors Have No Power¶

Issue:
The Rhino appears in Windows and VPforce Configurator shows the device connected, but the motors remain unpowered. The stick feels completely limp, and FFB effects have no effect. Motor status may show OFFLINE or FAULT_UNDERVOLTAGE.

Understanding the Problem:

This scenario indicates the USB power path is working (electronics are powered), but the DC power path (20V) is faulty. The motors require 20V DC to operate, supplied by an external power supply.

5.2.2.1 Quick Troubleshooting Checklist¶

1. Check power supply LED - Verify the PSU is powered and LED is illuminated
2. Measure PSU output - Using a multimeter (if available), measure ~20V at the PSU DC connector
3. Inspect DC connections - Ensure the DC barrel jack on the Rhino is firmly seated
4. Check DC cable - Look for visible damage, kinks, or loose connectors
5. Test with known-good PSU - If available, try a different 20V power supply to isolate the problem

5.2.2.2 Common Causes and Solutions¶

1. Faulty Power Supply

Power supplies can fail over time, particularly under sustained high-current loads:

• Symptoms: No voltage output, voltage significantly below 20V, or voltage drops dramatically under load
• Verification: Measure PSU output with multimeter (should read ~20V DC)
• Solution: Replace with a known-good 20V power supply (6-8A minimum capacity recommended)

2. Poor DC Connector Contact

The DC barrel jack can become loose or develop poor contact over time:

• Symptoms: Intermittent motor power, motors work sometimes but not others, vibrations cause power loss
• Verification: Ensure connector is firmly seated; wiggle it gently to check for play
• Solution: Reseat the DC connector firmly; if problem persists, replace the DC cable or jack

3. Faulty DC Cable

DC cables can develop internal breaks or high resistance:

• Symptoms: Voltage present at PSU but not at Rhino, intermittent operation depending on cable position
• Verification: Measure voltage at both PSU output and Rhino DC input to compare
• Solution: Replace DC cable with a known-good cable (18AWG or heavier recommended)

4. Failing E-Stop Switch

E-Stop switches can develop high internal resistance or fail to make contact:

• Symptoms: FAULT_UNDERVOLTAGE errors, motors intermittently lose power, voltage sag under load
• Verification: Check if E-Stop is engaged or bypass it temporarily to test
• Solution: Replace E-Stop switch if bypassing resolves the issue

5. Insufficient PSU Capacity

Power supply may not provide sufficient current for high-torque FFB operation:

• Symptoms: Voltage correct at idle but drops under load, motors work at low forces but fault at high forces, FAULT_UNDERVOLTAGE during intense FFB
• Verification: Measure voltage while activating test FFB effects in Configurator
• Solution: Upgrade to higher-capacity power supply (8A or higher recommended)

5.2.2.3 Verification After Repairs¶

After applying a fix, verify the solution:

1. Measure DC voltage - Should read ~20V with no load, remain above 18V under typical FFB load
2. Check motor status in Configurator - Should show RUNNING, not OFFLINE or FAULT_UNDERVOLTAGE
3. Test FFB effects - Activate test effects and verify motors respond consistently with appropriate force

5.3 USB Connection Issues¶

Issue:

The Rhino exhibits intermittent connection problems, instability, or appears to disconnect and reconnect frequently. This typically manifests as effects stuttering, dropping out momentarily, or the device appearing offline in VPforce Configurator.

Why USB Communication Matters for FFB:

The Rhino FFB joystick communicates using high-frequency bidirectional data. Unlike a standard joystick that just sends “X and Y” coordinates, an FFB stick is constantly receiving “Force” instructions from the sim while sending “Position” data back. Any interruption in this communication—even brief pauses from USB throttling or power management—can cause jerky motion, lag, freezing, or complete sim lockup. This is why USB connection quality is critical for smooth FFB operation.

5.3.1 Common Causes & Solutions¶

Check the following items in order:

1. USB Hub

   • If you are currently using a USB hub, disconnect it and connect the Rhino directly to your PC
   • USB hubs can introduce latency, power delivery issues, and signal integrity problems — see 5.3.2 Why USB Hubs Cause Problems with FFB Devices below for a technical explanation
   • Test the direct connection for stability

2. USB Port

   • Try a different USB port on your PC
   • Some USB ports have better power delivery or less electrical noise than others
   • Test multiple ports to identify if the issue is port-specific
   • If available, try USB 3.0/3.1 ports (blue ports) rather than USB 2.0 (black ports)

3. USB Cable

   • Try a different USB cable if possible
   • USB cables can degrade over time or have internal damage
   • A faulty cable is a common cause of intermittent connection issues

4. DC Power Plug

   • Inspect the DC power connector on the back of the Rhino
   • If the DC power plug pulls out easily or feels loose, vibrations during operation might be causing intermittent power connection loss
   • Poor DC connections can also introduce ground loops, causing electrical noise and instability
   • Ensure the power plug is firmly seated and making good contact
   • This is a frequent cause of instability during intense FFB effects

5.3.2 Why USB Hubs Cause Problems with FFB Devices¶

The standard advice is “never plug your FFB joystick into a USB hub” — but rarely does anyone explain why. When you push heavy HID input/output traffic, especially the kind required by a high-refresh-rate FFB device, you start hitting the physical and architectural limits of how USB hubs manage data.

5.3.2.1 The Transaction Translator (TT) Bottleneck¶

This is the most common culprit. Many FFB devices operate at USB Full-Speed (12 Mbps) rather than High-Speed (480 Mbps), because 12 Mbps is generally plenty of bandwidth for HID data.

When a 12 Mbps device is plugged into a High-Speed USB 2.0 or 3.0 hub, the hub must translate that traffic using a hardware component called a Transaction Translator (TT):

• Single-TT (STT) hubs — Most cheap hubs are Single-TT. One 12 Mbps translator is shared across all ports. If you plug in your FFB joystick, a mouse, a keyboard, and a button box, they all fight for that same narrow pipe. FFB data gets delayed or dropped.
• Multi-TT (MTT) hubs — High-end hubs have a dedicated TT per port. Each Full-Speed device gets its own 12 Mbps lane up to the hub’s High-Speed uplink. FFB devices perform significantly better on MTT hubs.

5.3.2.2 HID Interrupt Transfers Under Load¶

USB HID devices use Interrupt Transfers — they guarantee a specific polling rate (for example, every 1 ms). When you introduce a hub, scheduling complexity increases. Cheap hub silicon may miss polling windows.

FFB devices are particularly demanding because they rely heavily on Interrupt OUT transfers (data from PC to device) to command the motors. Continuous Interrupt OUT traffic at high rates is notoriously hard on cheap hub controllers, causing micro-stutters or completely dropped FFB commands.

5.3.2.3 Buffer Overflows and Dropped Packets¶

FFB generates bursty traffic. When you hit turbulence or a surface in a sim, the PC sends a rapid sequence of OUT reports while the joystick simultaneously sends back rapid position data.

Cheap hubs have very little internal buffer RAM. If the hub is waiting to send data upstream, packets that overflow the buffer are simply discarded. Unlike bulk transfers (used for storage), HID Interrupt transfers have no guaranteed retry mechanism — dropped packets are gone forever. The result is a dead spot or micro-freeze in your FFB.

5.3.2.4 Power Fluctuations and Micro-Disconnects¶

Even if your FFB joystick has its own external power supply for the motors, the USB logic board still relies on the 5V line from the USB cable to maintain its data connection. An unpowered or poorly powered hub can sag the 5V line under combined load, causing the USB logic to brownout and trigger a re-enumeration. Windows will silently recover, but you will experience a momentary FFB freeze while the device reconnects.

5.3.2.5 Recommendations if You Must Use a Hub¶

If direct connection to a motherboard port is not possible:

• Use a Multi-TT (MTT) hub — This is the single most important factor. Some manufacturers (such as StarTech) and industrial USB hub brands explicitly advertise MTT support.
• Use an externally powered hub — never rely on bus power (from the PC) to run a hub that handles an FFB device.
• Isolate high-bandwidth devices — Put your FFB joystick on a separate physical USB root hub on your motherboard from VR headsets or webcams. VR headsets and cameras use Isochronous transfers, which reserve large, non-negotiable blocks of USB bandwidth and can crowd out FFB data.

5.3.3 Disable USB Selective Suspend¶

Issue:

Windows can automatically suspend USB ports to save power, causing the USB port to be “throttled” and resulting in system performance issues. Symptoms include jerky motion in VPforce Configurator, sim freezes or lockups, and system sluggishness when the Rhino is connected.

Solution:

Windows USB Selective Suspend can be disabled through Power Options. Follow these steps:

1. Open Power Options:

   • Right-click the battery/power icon in the taskbar
   • Select Power settings or go to Settings → System → Power & battery

2. Click Advanced power settings (or Power Options if in classic settings)

3. Click Change plan settings for your current power plan

4. Click Change advanced power settings

5. Expand USB settings in the list

6. Expand USB selective suspend setting

7. Set the value to Disabled for both “On battery” and “Plugged in”

8. Click Apply → OK

9. Restart your PC for the change to take effect

10. Reconnect the Rhino and verify the issue is resolved

5.3.4 USB Isolator Recommendation¶

A USB isolator is strongly recommended for all RHINO setups. It sits between the PC and the RHINO, physically breaking the electrical ground path between them. This eliminates ground loop noise, reduces EMI, and — critically — prevents hardware damage from ground faults.

Benefits of a USB isolator:

• Prevents hardware damage from ground faults and power surges through the USB path
• Eliminates ground loops between the PC and the RHINO
• Protects electronics from voltage spikes and transient faults on the USB bus
• Resolves connection instability in systems with high electrical noise

Where to Find USB Isolators:

Search for AduM3160 isolator boards on AliExpress, Amazon, or other electronics retailers. The AduM3160 is a popular, affordable USB 2.0 isolator IC commonly available on ready-made isolator boards. When searching, look for:

• “AduM3160 isolator board” or “USB isolator AduM3160”
• Pre-assembled USB isolator modules (no soldering required)
• Boards with both USB-A connectors or USB-A to USB-C options

Cost is typically low (under $10-20 USD), making it a worthwhile investment to protect your hardware.

5.4 WinUSB / WebUSB Firmware Update Issues¶

5.4.1 Legacy Firmware WebUSB Issue (1.0.16 and older)¶

Issue:

On Windows 10/11 with firmware 1.0.16 and older, the Rhino may appear correctly in Windows, but WinUSB fails to operate, preventing firmware updates through WebUSB. Users may see network errors in the WebUSB tool. This problem is fixed in newer firmwares.

You can apply a simple registry fix to restore WebUSB functionality. This requires administrative privileges.

Steps:

• Press Start, type PowerShell, right-click Windows PowerShell, and select Run as administrator.

• Paste the following command and press Enter:

  Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Enum\USB\VID_FFFF&PID_2055&MI_03\*\Device Parameters" -Name "DeviceInterfaceGUID" -Value "{DA10CDEF-26A6-47D9-970E-B3D561A277FA}"
  

  - Unplug the Rhino from the USB port and plug it back in. - Test the connection in the WebUSB tool - firmware updates should now work as expected.

5.4.2 WinUSB Driver Conflicts and Cleanup¶

Many Windows systems handle Rhino’s WebUSB interface without any special setup. Others don’t. The difference usually comes down to what Windows has stored from past hardware or software. Windows keeps old USB drivers in its internal driver store, and sometimes it silently reuses those drivers for new devices. If one of those older drivers isn’t compatible with WebUSB, Rhino may get matched to the wrong driver and the browser will show connection or “network” errors even though the device is working correctly in Configurator or game itself. The steps below clear out these leftover drivers so Windows can load the correct Microsoft WinUSB driver that WebUSB needs.

If you encounter WebUSB connection issues, driver conflicts from previous installations (particularly from Zadig or other USB tools) may be preventing proper WinUSB operation. Follow these steps to clean up conflicting drivers and restore proper WebUSB functionality.

5.4.2.1 Quick Reset (try this first)¶

1. Disconnect Rhino from the PC
2. Reboot Windows
3. Connect Rhino directly to a USB port on the PC (not a hub)
4. Test WebUSB connection

If errors persist, continue with the full driver cleanup procedure below.

5.4.2.2 Full Driver Cleanup Procedure¶

Step 1: Remove old Rhino drivers from Device Manager

1. Open Device Manager (Win + X)
2. View → Show hidden devices
3. Expand “Universal Serial Bus devices”, “USB devices”, “Other devices”, and “LibUSB” (if present)
4. Right-click every entry related to “Rhino DFU” or showing your device’s VID/PID → Uninstall device
5. If Windows shows a checkbox “Delete the driver software for this device”, enable it before uninstalling

Leave Device Manager open for now.

Step 2: Clean driver packages from Windows driver store (optional)

1. Open Start → type “cmd” → right-click → Run as administrator
2. List all driver packages:

pnputil /enum-drivers > %temp%\drivers.txt

3. Open the file:

notepad %temp%\drivers.txt

4. In the list, look for driver entries that mention:
   • Rhino
   • Your device VID_FFFF / PID_205x
   • WinUSB
   • libusb
   • libusbK
   • libwdi

Each entry shows something like Published name: oem47.inf.

5. For each matching driver, run:

pnputil /delete-driver oem47.inf /force /uninstall

Replace oem47.inf with the actual name. If Windows says “driver is in use”, unplug the device and run the command again.

Step 3: Remove ghost interfaces

Back in Device Manager:

1. View → Show hidden devices
2. Remove any greyed-out duplicates of “Rhino DFU” or anything matching VID/PID
3. Unplug the device after cleaning

Step 4: Reboot Windows

A clean reboot ensures Windows forgets cached bindings.

Step 5: Reconnect Rhino and verify WinUSB installation

Plug in Rhino. Windows should now load Microsoft’s built-in WinUSB (winusb.sys) automatically.

Verify correct driver:

1. Device Manager → open “Rhino DFU” device → Properties
2. Driver tab should show:
   • Provider: Microsoft
   • Driver file: winusb.sys

5.4.2.3 Forcing Windows to Use WinUSB (if automatic installation fails)¶

If Windows picks the wrong driver, manually bind WinUSB:

1. Right-click “Rhino DFU” in Device Manager → Update driver
2. Choose “Browse my computer for drivers”
3. Choose “Let me pick from a list of available drivers”
4. Select “Universal Serial Bus devices”
5. Pick “WinUSB Device” or “USB Device (WinUSB)” depending on Windows version
6. Install

This uses Microsoft’s own signed WinUSB and does not require Zadig or third-party tools.

5.4.2.4 Browser Cleanup¶

After correcting the driver:

1. Chrome/Edge → Settings → Privacy → Site settings → USB devices → Clear permissions for WebUSB tool
2. Clear site data for the WebUSB domain
3. Test connection in a fresh tab or Incognito window

5.5 Motor LED Indicators¶

Each motor has an integrated driver with a status LED that provides diagnostic information through flash patterns:

• Green flashes — indicate the assigned motor ID:

  • 1 flash = Motor ID 0 (pitch / Y-axis)
  • 2 flashes = Motor ID 1 (roll / X-axis)

• Red flashes — indicate a fault condition. Check the Configurator status bar for the specific fault code (see 5.6 Motor Faults below).

• LED normally OFF, brief blink every few seconds — the motor has power but is not actively communicating with the Rhino main board.

5.6 Motor faults¶

5.6.1 FAULT_UNSTABLE¶

Issue:

The Rhino reports a FAULT_UNSTABLE error. This fault typically occurs suddenly, often preceded by an audible thump or impact sensation from the device.

Cause:

This fault is most commonly caused by belt slippage on either the X-axis or Y-axis. When the belt connecting a motor to its pulley loses tension or alignment, the motor and pulley can slip relative to each other. The sudden slip causes the Rhino to detect an unexpected position change that doesn’t match the expected motor command, triggering the stability check and generating the fault. The audible thump is often the moment when slippage occurs.

Resolution:

1. Check belt tension: Inspect the axis belt which produced the fault. The belts should be firm but not over-tightened.

2. Re-tighten if necessary: If either belt is loose, carefully tighten it to restore proper tension. See the Belt Tensioning Guide for detailed instructions.

3. Run Auto Calibration: After adjusting tension and alignment, launch the VPforce FFB Configurator and run Auto Calibration from the Settings tab.

4. Verify calibration values: Once calibration completes, check the calibration values. You should see values around C:~2000 for both axes. If the values are significantly different, the belts may need further adjustment.

5.6.2 FAULT_UNDERVOLTAGE¶

Issue:
The Rhino reports a FAULT_UNDERVOLTAGE error when supply voltage drops below 8 volts.

Cause:
This fault protects motor drivers by halting operation when voltage is insufficient. The 8V threshold ensures reliable operation and prevents damage.

Under load (during active force feedback or high-torque movements):

• Poor electrical connection (loose or corroded power connector, high resistance in power path)
• Failing power supply (unable to maintain voltage during peak current draw)
• Insufficient PSU capacity (power supply rated below recommended specifications)
• Failing E-Stop switch (high internal resistance or intermittent disconnection)

At idle (no force feedback active):

• E-Stop pressed (normal behavior: motor power cut momentarily shows fault until capacitors discharge, then motor status shows OFFLINE)
• Faulty PSU (unable to maintain stable output without load)

Resolution:

1. Check power connections: Inspect PSU cables and connectors. Ensure tight, clean, corrosion-free connections.

2. Verify PSU output voltage: Measure PSU output voltage with multimeter under no load. Should match rated voltage.

3. Test under load: Monitor PSU voltage during typical Rhino operation. Significant voltage sag indicates insufficient PSU capacity or poor connections.

4. Replace or upgrade PSU: If power supply cannot maintain adequate voltage under load, replace with higher-capacity unit.

5.7 How to Get Effective Support¶

Providing complete information up front dramatically speeds up diagnosis and resolution. Follow this guide to get help as quickly as possible.

5.7.1 Required Screenshots¶

Always include screenshots of your VPforce Configurator:

1. Effects Tab — shows current FFB effect settings and active effects
2. Settings Tab — shows global gain multipliers and force settings
3. Debug Tab — if any errors or warnings are visible
4. Button Mapping Tab — if your issue involves buttons or inputs

5.7.2 Describe the Problem Clearly¶

Include the following in your support request:

• What exactly happens? — describe the specific behavior (e.g. “stick goes limp with no centering force” rather than “FFB doesn’t work”)
• When does it occur? — specific simulator, aircraft, action, or situation
• Is it consistent or intermittent? — every time, or only sometimes?
• When did it start? — new issue, or always been this way?
• What have you tried? — prevents suggesting steps you’ve already completed

5.7.3 System Information¶

• Rhino firmware version (visible in Configurator)
• Simulator name and version (e.g. DCS World 2.9.8, IL-2 v5.201)
• Grip type and extensions (e.g. VKB, Virpil, extension length)
• Recent changes (firmware updates, new hardware, configuration changes)

5.7.4 Real-Time Troubleshooting¶

While the issue is occurring:

1. Watch the Effects Tab — game-created effects appear in real-time and force values change dynamically while flying
2. Check the Debug Tab — look for error messages, connection issues, or motor faults

3. TelemFFB Users (if applicable):

   • Check TelemFFB log window for connection errors or warnings
   • Verify TelemFFB is connected to simulator
   • Post or screenshot TelemFFB log output when reporting issues
   • Check telemetry window to verify data reception

5.7.5 Common Pitfalls to Avoid¶

1. “It doesn’t work” without details - Define exactly what doesn’t work
2. Missing screenshots - Without Configurator screenshots, diagnosis is guesswork
3. No troubleshooting steps - Mention what you’ve already tried
4. Incomplete system info - Firmware version and simulator details are essential
5. Vague timing - “Sometimes” isn’t helpful - describe exact conditions
6. Assuming others know your setup - Describe your full configuration

5.7.6 Where to Get Support¶

VPforce Discord Community:

• Most active support channel
• Community and developers respond quickly
• Real-time troubleshooting assistance
• Type !support in Discord for quick reminder of required info

Documentation Resources:

• VPforce Documentation
• Troubleshooting Guide
• Firmware Updates

Before Asking:

1. Check this troubleshooting guide for your specific issue
2. Try factory reset and verify problem persists
3. Gather all required screenshots and information
4. Prepare clear problem description