VNM DIRECT DRIVE CONFIGURATION MANUAL

The Configuration Window is the primary interface used to configure connected VNM devices.

A device list is displayed on the left sidebar, showing all supported device categories in the VNM ecosystem.

Device categories include:

Selecting a device from the sidebar opens its configuration page, where users can adjust parameters specific to that device.

Detailed configuration instructions for each device are provided in the relevant sections of this manual.

The System Log Window displays real-time system messages and device event logs generated by VNM SimCenter.

This window can be opened using the keyboard shortcut:

Ctrl + F9

The log window provides useful information for monitoring system activity, including:

The System Log Window is primarily used for system monitoring and troubleshooting.

Purpose

Sets the current steering wheel position as the center position.

Explanation

If the steering wheel is not perfectly aligned after installation, the Center function allows the current wheel position to be defined as the neutral steering position.

This ensures that the physical wheel center matches the steering center used by the wheelbase.

Usage

The wheelbase will store its current position as the steering center.

Purpose
Performs an automatic calibration procedure to measure and initialize internal wheelbase parameters.

Explanation
During calibration, the wheelbase automatically rotates the steering shaft through a predefined movement sequence:

After the calibration sequence is completed, the wheel will automatically return to its original position and stop.

This process allows the wheelbase to initialize internal control parameters required for normal operation.

Important

Do not touch the steering wheel during calibration, as this may interfere with the calibration process and lead to incorrect measurements.

Usage

The steering wheel will automatically return to its original position.

Purpose

Defines the total steering rotation of the wheel from lock to lock.

Explanation

This setting determines how far the steering wheel can rotate between the left and right steering limits.

Different types of race cars use different steering ranges. Adjusting this value allows the wheelbase to match the steering behavior of the simulated vehicle.

Recommended Settings

The default value is 900°.

Purpose

Allows the wheelbase to operate at its full torque capability.

Explanation

By default, the wheelbase operates at 50% of its maximum torque output in order to provide a safer and more comfortable experience, particularly for new users.

When Max Torque Mode is enabled, the wheelbase can generate its full torque output. This provides stronger and more detailed force feedback but may require greater physical effort to control the steering wheel.

Important

High torque levels can generate strong steering forces.

Before enabling this mode, ensure that:

Usage

Purpose
Adjusts the overall torque output level of the wheelbase.

Explanation
This parameter controls how much torque the wheelbase motor produces.

Higher values result in stronger steering forces, while lower values produce lighter steering forces.

Overall Gain does not modify the force feedback signal generated by the sim racing game. Instead, it determines how strongly the wheelbase reproduces that force through the motor.

This setting allows users to adjust the steering force to match:

Recommended Usage

For high-torque Direct Drive wheelbases, it is recommended to start with a lower gain value and gradually increase it until the desired steering force is reached.

Purpose

Applies filtering to the incoming force feedback signal.

Explanation

The filter smooths rapid changes in the force feedback signal.

Lower filter values allow more detailed and responsive force feedback but may introduce additional vibration.

Higher filter values reduce high-frequency noise and produce smoother steering behavior.

Recommended Range

300 – 470

Lower values provide more detail.
Higher values produce smoother steering forces.

User Effects generate additional steering forces within the wheelbase.

These effects are applied on top of the force feedback signal received from the sim racing game and are used to simulate the mechanical characteristics of a real steering mechanism.

User effects are generated inside the wheelbase and are independent from the force feedback signal produced by the game.

2.7.1 Damper Gain

Purpose
Adds resistance proportional to the steering speed.

Explanation

Damping stabilizes the steering wheel and helps reduce oscillation, especially when driving at high speeds.

Recommended Range
0 – 20 %

2.7.2 Friction Gain

Purpose
Adds constant resistance to wheel rotation.

Explanation
Friction simulates mechanical resistance within the steering mechanism and increases the perceived weight of the steering wheel.

Recommended Range
0 – 10 %

2.7.3 Inertia Gain

Purpose
Simulates rotational inertia in the steering system.

Explanation
Increasing inertia makes the steering feel heavier and smoother, but may slightly reduce steering responsiveness.

Recommended Range
0 – 10 %

2.7.4 Spring Gain

Purpose
Applies a centering force toward the neutral steering position.

Explanation
Spring effects simulate the behavior of a mechanical centering spring.

For most modern sim racing games that provide native force feedback, this setting should remain disabled or set to a very low value.

These effects are optional and are typically used to fine-tune the steering feel according to personal preference.

The System Info panel displays the current operating status of the wheelbase.

Displayed information typically includes:

This information can be used for system monitoring and quick diagnostics.

The Game & Car section allows configuration profiles to be assigned to specific sim racing games and vehicles.

This feature enables the wheelbase to automatically load different settings depending on the active game or selected vehicle.

Profiles can be customized to match the handling characteristics of different racing disciplines.

Note
This feature may not be available in all software versions.

Purpose

Limits extremely strong force spikes generated during crashes or abrupt physics events.

Explanation

Some sim racing games may generate very large force spikes during collisions. These spikes can result in sudden high torque output from the wheelbase.

Crash Effect Reduction helps limit these spikes to improve user safety and reduce excessive steering shocks.

Recommended Usage

Enable this option if the wheel produces very strong impacts during crashes.

Disabling this option allows the wheelbase to reproduce the full force feedback signal generated by the game.

Purpose

Controls the contribution of the DirectInput force feedback signal when combining multiple force sources.

Explanation

In certain modes, such as TIC (Telemetry + DirectInput Combine), the wheelbase may receive force feedback from multiple sources, including DirectInput signals from the game and internally generated forces based on telemetry data.

The DI Ratio determines how much influence the DirectInput signal has compared to these internally generated forces.

Higher values prioritize the DirectInput force feedback signal from the game.

Lower values increase the influence of internally generated forces, such as telemetry-based effects.

Typical Range

30 – 70

Purpose

Controls the response speed of the damping effect.

Explanation

The damper filter determines how quickly the damping force reacts to changes in steering speed.

Lower values produce faster and more responsive damping behavior.

Higher values smooth the damping response and create more stable steering behavior.

Recommended Range

0 – 300

Purpose

Controls the response speed of the simulated rotational inertia.

Explanation

This filter determines how quickly the inertia effect reacts to changes in steering acceleration.

Lower values allow the inertia effect to respond more quickly.

Higher values produce smoother inertia behavior but may slightly reduce steering responsiveness.

Recommended Range

0 – 300

Purpose

Controls the response speed of the friction effect.

Explanation

This filter stabilizes the constant resistance generated by the friction simulation.

Lower values produce a faster response to steering input.

Higher values smooth the friction behavior and reduce rapid changes in steering resistance.

Recommended Range

0 – 300

Purpose

Defines the steering angle at which the maximum bumpstop force is reached.

Explanation

The bumpstop effect simulates the mechanical steering limit of a real vehicle.

When the steering angle reaches the configured Steering Range, the bumpstop force begins to increase.

As the wheel continues to rotate beyond this point, the bumpstop force gradually increases until it reaches maximum strength at the Bumpstop Range.

This progressive force prevents the wheel from rotating beyond the configured steering limits while maintaining a natural steering feel.

Recommended Setting

The Bumpstop Range should typically be set slightly beyond the configured Steering Range (approximately +5° to +15°).

Purpose

Controls the maximum strength of the bumpstop force.

Explanation

Lock Strength defines the maximum force applied when the steering angle reaches the Bumpstop Range.

Higher values create a stronger steering stop and make the steering limit more noticeable.

Lower values produce a softer steering stop.

Recommended Range

5000 – 10000

Higher values create a stronger steering stop. Lower values produce a softer steering limit.

The FFB Mode setting defines how the wheelbase receives and processes force feedback signals from sim racing games.

Different games support different force feedback interfaces. Selecting the appropriate mode ensures correct force feedback behavior and compatibility.

DirectInput

DirectInput is the standard force feedback interface used by most Windows sim racing games.

In this mode, the wheelbase receives force feedback signals directly from the game through the DirectInput API.

This mode provides the best compatibility with most sim racing titles and is recommended for general use.

Telemetry

In Telemetry mode, the wheelbase generates force feedback using vehicle telemetry data received from supported games.

Telemetry mode requires the VNM Telemetry plugin to be enabled and supported by the selected game.

This allows additional force effects and more detailed vehicle dynamics to be reproduced.

Supported games include:

Telemetry mode may require the VNM Telemetry Plugin to be enabled in VNM SimCenter.

iRacing 360

This mode is designed for full steering range support in iRacing.

It allows the wheelbase to operate with a 360 Hz force feedback update rate, providing faster and smoother force feedback response compared to standard DirectInput operation.

This mode is intended to support high-frequency force feedback updates in iRacing.
Availability depends on future updates to the iRacing software.

Note
This mode may not function in current versions of the game.

TIC (Telemetry + DirectInput Combine)

TIC mode combines Telemetry-based force feedback with DirectInput force feedback signals.

This hybrid approach can provide more detailed steering feedback while maintaining compatibility with the game’s native force feedback system.

The parameters in the Game Settings tab correspond to the different Force Feedback effect types defined by the Microsoft DirectInput Force Feedback API.

When a sim racing game sends Force Feedback signals to the wheelbase, those signals are represented using standardized effect types. Each effect type describes how the force behaves over time or how it reacts to steering movement.

VNM SimCenter allows users to adjust the gain (strength) of each effect type. This makes it possible to fine-tune how strongly the wheelbase reproduces specific DirectInput force effects generated by the game.

In most cases, it is recommended to keep all values at 100% to ensure accurate reproduction of the Force Feedback signal from the game.

DirectInput defines several categories of force effects, described below.

Here are some waveforms to understand how each effect works

4.1.1. Constant Force

Constant Force represents a steady force that does not change over time.

This type of effect is commonly used by sim racing games to represent continuous steering forces generated by the vehicle physics engine, such as:

For most modern sim racing games, Constant Force is the primary component of the Force Feedback signal.

4.1.2. Ramp Force

Ramp Force represents a force that gradually increases or decreases over time.

This type of effect may be used by some games to simulate smooth transitions in steering force, for example when steering load progressively increases as the car enters a corner.

Ramp forces are less commonly used than constant forces in modern physics-based simulators.

4.1.3. Condition Effects

Condition effects simulate mechanical characteristics of a steering system.
Unlike constant or ramp forces, condition effects generate forces dynamically based on the movement of the steering wheel.

These effects may depend on parameters such as:

DirectInput defines several types of condition effects.

Spring

The Spring effect applies a centering force that pulls the steering wheel toward the neutral position.

Some games use spring forces to simulate the natural centering behavior of a steering system.

In modern physics-based racing simulators, spring forces are often unnecessary because the self-aligning torque of the tires is already calculated by the physics engine.

Damper

The Damper effect generates resistance proportional to the speed of the steering movement.

This effect simulates damping in the steering system and helps stabilize steering motion.

Increasing damper gain increases resistance when the wheel is turned quickly.

Friction

The Friction effect applies a constant resistance to steering movement regardless of steering speed.

This effect may be used to simulate mechanical friction within the steering system.

Inertia

The Inertia effect simulates the rotational mass of the steering system.

This effect causes the wheel to resist changes in rotational acceleration, similar to the behavior of a physical steering assembly.

4.1.3. Periodic Effects

Periodic effects generate oscillating forces based on mathematical waveforms.

These effects are commonly used to simulate vibration or repeating force patterns.

DirectInput defines several waveform types.

Sine Wave

A sine wave produces a smooth and continuous oscillating force.

This effect may be used to simulate road surface vibration or other periodic oscillation effects.

Triangle Wave

A triangle wave generates a force that changes linearly between two values over time.

Some games may use triangle waves for vibration effects or testing signals.

Square Wave

A square wave alternates abruptly between two force levels.

This waveform can create strong vibration effects or distinct feedback patterns.

Sawtooth Wave

A sawtooth waveform gradually increases or decreases before changing abruptly.

DirectInput defines two variants:

These waveforms may be used by certain games to generate specific vibration patterns.

In most cases, users should keep all DirectInput effect gain values at 100%.

This ensures that the wheelbase reproduces the Force Feedback signal generated by the game as accurately as possible.

Adjust these values only if you want to modify how strongly the wheelbase responds to a specific type of DirectInput force effect.

These are the games and its effects. Users can adjust the gain to meet personal liking

The profile management controls are located in the Profile section of the wheelbase configuration page.

Users can perform the following actions:

create new profiles

load existing profiles

save changes to the current profile

import profiles from external files

share profiles with other users

To create a new wheelbase profile:

Step 1
Click Add Profile.

Step 2
Enter a name for the new profile.

Step 3
Adjust the wheelbase settings as desired.

Step 4
Click Save to store the profile.

The new profile will now appear in the profile list.

To switch to a different profile:

Step 1
Open the Profile list.

Step 2
Select the desired profile.

Step 3
Click Apply.

The wheelbase will immediately load the settings stored in that profile.

If you modify any wheelbase settings, the profile can be updated to store the new configuration.

Step 1
Adjust the desired parameters.

Step 2
Click Save to store the changes in the current profile.

If the changes should not be saved, click Revert to restore the previous settings.

Profiles can be imported from external files.

Step 1
Click Import.

Step 2
Select the profile file.

Step 3
The profile will be added to the profile list.

This feature allows users to load profiles shared by other users or provided by VNM.

Profiles can also be exported and shared with other users.

Sharing profiles is useful when:

exchanging Force Feedback setups with other sim racers

distributing recommended settings for specific games

backing up personal configurations

Recommended Usage

It is recommended to create separate profiles for each sim racing game.

Different games use different Force Feedback models, and separate profiles help maintain consistent steering behavior across titles.

Purpose

The Automatically Change Profile feature automatically switches the wheelbase profile based on the car you are using in-game.
This eliminates the need for manual profile changes and ensures optimal Force Feedback for each vehicle.

Requirements

How It Works

Important Note:

Setup (for new car)

When using a new car (not yet learned by the plugin), follow these steps:

Step 1
Open VNM SimCenter

Step 2
Navigate to Automatically Change Profile

Step 3
Enable the Automatically Change Profile feature

Step 4
Click Refresh to update the car list from the plugin

Step 5
Select game and car from the drop lists

Step 6
Configure Force Feedback settings as desired (Overall gain, user effects..)

Step 7
Click Save

What Happens Next

Notes

Best Practices

Purpose

This section allows you to quickly adjust wheelbase settings and switch profiles without going to Windows.

Access

Step 1
Open VNM SimCenter

Step 2
Go to:
Settings → Wheelbase

Hotkey Configuration

Hotkey step

Purpose:
Defines how much the value changes with each key press

Explanation:
Each press will increase/decrease the value based on this step

Recommended:

Hotkey sensitivity

Purpose:
Controls how fast values change when holding a key

Explanation:
Higher value → slower change when holding the key

Notification position

Purpose:
Defines where notifications appear on screen

Options:

Device selection

Purpose:
Select which device receives the hotkey input

Explanation:
Dropdown shows the currently controlled device

Example:

Hotkey Mapping

You can assign keys to control functions directly.

How to assign keys (important)

For Overall Gain, DI Ratio, Overall Filter:

Step 1
Click the REC button

Step 2
Press the key you want to assign

Step 3
The key will be saved to that function

For Centerize and Profile switching:

Step 1
Click on the input field

Step 2
Press the key or key combination you want to assign

Centerize

Purpose:
Return the wheel to center position (0°)

Overall Gain (+ / -)

Purpose:
Increase / decrease overall FFB strength

Use case:

DI Ratio (+ / -)

Purpose:
Adjust DirectInput scaling ratio in TIC mode

Explanation:
Affects how force from the game is scaled

Overall Filter (+ / -)

Purpose:
Adjust FFB smoothness

Explanation:

Profile switching

Purpose:
Quickly switch between profiles

Example:

Click Save in the bottom-right corner to apply all changes

This section controls how the wheelbase is displayed and how certain UI-related behaviors function. These settings do not directly affect Force Feedback, but help with monitoring and usability.

Wheel max angle

Purpose:
Defines the maximum steering angle displayed in the software

Explanation:
This value is used for UI visualization and wheel animation, not the physical steering limit of the wheelbase

Recommended:

Wheel angle step

Purpose:
Defines how much the steering angle changes when adjusted via hotkeys

Explanation:
Each hotkey press will increase or decrease the wheel angle by this value using the arrow keys (after clicking on the slider handle).

Recommended:

Show current torque in percentage

Purpose:
Displays current Force Feedback output as a percentage

Explanation:
Shows torque as a percentage instead of Nm, making it easier to monitor overall usage and detect limits

Enable circle animation

Purpose:
Displays a circular visualization for base status

Explanation:
Provides a visual indicator for:

Telemetry Force Feedback in VNM SimCenter consists of two components:

Telemetry Core Forces represent the continuous forces generated from vehicle telemetry data, such as steering load or vehicle dynamics.

Telemetry Effects are short-duration signals generated from specific vehicle events, for example:

To ensure that event-based effects remain clearly perceptible without overwhelming the main steering forces, VNM SimCenter automatically manages the distribution of force output between these two components.

Force Allocation Behavior

When no telemetry effects are enabled

Telemetry Core Forces = 100%
Telemetry Effects = 0%

The wheelbase reproduces the full telemetry-based force feedback signal.

When one or more telemetry effects are enabled. A portion of the available torque output is reserved for telemetry effects so that event-based feedback remains clearly perceptible

By default, approximately 70% of the force output is allocated to telemetry forces and 30% to telemetry effects.

This automatic distribution helps maintain a balance between:

Recommended Usage

Telemetry effects are designed to complement the main steering forces generated from telemetry data.

Enabling too many telemetry effects simultaneously may too much information (could cause noise) of the continuous telemetry force.

For the best driving experience, enable only the effects that provide user liking meaningful feedback for the selected sim racing game.

Telemetry data is provided through a plugin system.

The plugin receives telemetry data from supported games and sends it to VNM SimCenter, where the data is processed to generate additional Force Feedback effects.

The plugin system supports two types of plugins:

Native Plugins

Native plugins are distributed as DLL files and are loaded directly by VNM SimCenter.

Python Plugins (deprecated)

Python plugins consist of two files:

These plugins allow users or developers to create custom telemetry processing logic.

Python plugins are deprecated and may be removed in future versions of VNM SimCenter.

Plugins can be installed using the Plugin Store or by manually copying plugin files into the plugins folder.

To install a plugin:

Step 1
Open the Plugin Store.

Step 2
Select the desired plugin.

Step 3
Click Install.

Step 4

Reload plugin after installing a new plugin to ensure it is properly loaded

Alternatively, plugin files can be manually copied into the plugins directory located in the same folder as the VNM SimCenter application.

Each telemetry effect can be configured using several parameters that control how the effect is generated.

Typical configuration parameters include the following.

Enable

Enables or disables the selected telemetry effect.

If disabled, the effect will not be generated even if the telemetry event occurs.

Waveform

Defines the waveform used to generate the vibration or force signal.

Available waveform types include:

Different waveforms produce different vibration characteristics.

Gain

Controls the overall gain applied to the effect signal.

Increasing this value increases the amplitude of the generated force.

Frequency

Defines the oscillation frequency of the generated signal.

Higher frequency values produce faster vibration patterns.

Duration

Defines how long the effect lasts after the telemetry event is triggered.

This parameter is typically used for short events such as gear shifts.

A value of -1 disables the duration limit

6.5.1. Gear Shift

Purpose

The Gear Shift effect generates a short vibration or force pulse when the vehicle changes gear.

This effect simulates the mechanical sensation that occurs during a gear shift, helping the driver perceive gear changes more clearly through the steering wheel.

Gear shift feedback can be especially useful in vehicles with sequential gearboxes or paddle shifters, where the driver may rely on tactile feedback rather than visual cues.

Explanation

When a gear change event is detected from telemetry data, VNM SimCenter generates a short force signal based on the selected waveform and parameters.

The strength and character of the effect can be adjusted using several parameters, allowing users to customize how the gear shift feedback feels.

The generated signal is mixed with the telemetry core force output according to the Telemetry Force Distribution described earlier.

Parameters

Enable

Enables or disables the Gear Shift telemetry effect.

When disabled, no gear shift feedback will be generated.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

Different waveforms produce different vibration characteristics.

For example:

Gain

Controls the overall amplitude of the gear shift signal.

Higher gain values produce stronger gear shift feedback.

Frequency

Defines the oscillation frequency of the vibration signal.

Higher frequencies produce faster vibration patterns, while lower frequencies create slower pulses.

Typical gear shift effects use relatively high frequencies to simulate a short mechanical impact.

Duration

Defines how long the gear shift effect lasts after the shift event is detected.

Short durations create a quick mechanical "kick", while longer durations produce a more sustained vibration.

Typical values are 10–40 ms depending on user preference.

Recommended Usage

For realistic gear shift feedback:

Gear shift feedback should remain subtle and should not overpower the primary steering forces.

6.5.2 EngineVibe

Purpose
The Engine Vibration effect generates continuous vibration based on the engine speed (RPM) of the vehicle.

This effect simulates the vibration produced by the engine and drivetrain, providing additional feedback about engine operation and RPM levels through the steering wheel.

Engine vibration can help drivers perceive engine load and speed without relying solely on visual indicators.

Explanation
When telemetry data reports the current engine RPM, VNM SimCenter generates a vibration signal based on the configured parameters.

The vibration characteristics vary with engine speed:

The final vibration frequency is limited within a defined range to prevent excessive vibration and to avoid masking important Force Feedback details such as tire grip and road surface information.

This ensures that engine vibration provides useful feedback while remaining subtle and non-intrusive.

Parameters

Enable

Enables or disables the Engine Vibration telemetry effect.

When disabled, no engine vibration feedback will be generated.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

A sine waveform is typically recommended for engine vibration because it produces smooth oscillations.

Gain

Controls the overall amplitude of the engine vibration signal.

Higher gain values produce stronger vibration.

Frequency

Defines the base oscillation frequency of the vibration signal.

This value acts as the base frequency, which is dynamically adjusted according to engine RPM.

Higher values produce faster vibration patterns, while lower values result in slower oscillations.

Recommended Usage

Engine vibration should remain subtle so that it does not interfere with the main steering forces.

For most vehicles:

This ensures that engine vibration provides additional feedback without masking the core Force Feedback signal.

Example Settings

Example baseline configuration:

Waveform : Sine
Gain : 20 – 40
Frequency : 40 – 80 Hz

These values produce a subtle vibration that varies with engine speed while maintaining clear steering feedback.

6.5.3. RoadTexture

Purpose

The Road Texture effect generates subtle vibrations based on road surface telemetry data.

This effect simulates small surface irregularities of the track, allowing the driver to feel the texture of the road through the steering wheel.

Road Texture helps improve immersion by providing additional tactile feedback from the driving surface.

Explanation

When telemetry data indicates variations in the road surface or tire contact forces, VNM SimCenter generates a vibration signal that reflects the texture of the track.

Unlike large steering forces generated by vehicle dynamics, road texture feedback consists of small high-frequency vibrations designed to reproduce the fine details of the road surface.

The resulting signal is mixed with the telemetry core force output according to the Telemetry Force Distribution described earlier.

Parameters

Enable

Enables or disables the Road Texture telemetry effect.

When disabled, no road surface vibration will be generated.

Waveform

Road texture is generated from real-time telemetry data. Therefore this effect typically uses a constant force signal rather than a predefined waveform.

Gain

Controls the overall amplitude of the road texture signal.

Higher values increase the strength of road surface vibrations.

Excessive gain may produce unrealistic steering vibration.

Recommended Usage

Road texture effects should remain subtle and should not overpower the primary Force Feedback generated by the vehicle physics.

For realistic results:

Too much road texture feedback may mask important steering forces such as tire grip or weight transfer.

6.5.4. ABS

Purpose

The ABS effect generates vibration feedback when the vehicle’s Anti-lock Braking System (ABS) is activated.

This effect helps the driver detect when the braking system is approaching the traction limit and the ABS system begins to modulate brake pressure.

Providing tactile feedback for ABS activation can help drivers better control braking force during heavy braking situations.

Explanation

When telemetry data indicates that the ABS system is active, VNM SimCenter generates a vibration signal through the wheelbase.

The vibration typically consists of rapid pulses that simulate the sensation of brake modulation occurring during ABS operation.

This feedback helps inform the driver that the wheels are near the limit of grip and that braking pressure may need to be adjusted.

The generated signal is mixed with the telemetry force output according to the Telemetry Force Distribution described earlier.

Parameters

Enable

Enables or disables the ABS telemetry effect.

When disabled, no ABS vibration feedback will be generated.

Waveform

Defines the waveform used to generate the ABS vibration signal.

Available waveform types may include:

For ABS simulation, Sine or Triangle waveforms often provide clearer pulse feedback.

Gain

Controls the overall amplitude of the ABS vibration signal.

Higher values produce stronger vibration when ABS activates.

Frequency

Defines the oscillation frequency of the vibration signal.

Short durations are typically recommended to simulate rapid brake pressure modulation.

Brake Input ABS Trigger

Purpose

Defines the brake pedal input level required before the ABS vibration effect can be activated.

Explanation

Brake Input ABS Trigger acts as a minimum brake pedal threshold.
The ABS telemetry effect will only be allowed to activate when the brake pedal input exceeds this value.

This prevents the ABS vibration from being triggered during light braking situations where ABS is unlikely to occur.

For example, if Brake Input ABS Trigger is set to 5000, the ABS vibration effect will only activate when the brake pedal input exceeds this threshold and an ABS event is detected.

Using a brake input threshold helps ensure that ABS feedback is generated only during heavy braking conditions where the Anti-lock Braking System is likely to engage.

Recommended Usage

Use a moderate threshold value to avoid unnecessary vibration during normal braking.

Higher values require stronger brake input before the ABS effect can activate.
Lower values allow ABS feedback to trigger earlier.

ABS Trigger

Purpose

Defines the telemetry threshold used to detect ABS activity.

Explanation

ABS Trigger determines the sensitivity of the ABS telemetry signal required to activate the ABS vibration effect.

When the telemetry data indicates that the ABS system is active and exceeds the configured ABS Trigger level, the wheelbase generates the configured ABS vibration signal.

Lower values make the ABS effect more sensitive and allow it to trigger more easily.
Higher values require stronger ABS activity before the vibration effect is generated.

This parameter allows users to adjust how early or aggressively the ABS feedback is felt through the steering wheel.

Recommended Usage

Lower values produce earlier ABS feedback and may generate more frequent vibration.

Higher values reduce sensitivity and ensure that ABS vibration is generated only during strong ABS activation.

Users should adjust this value according to the behavior of the specific racing simulator and vehicle.

Note: Only iRacing uses ABS flag to generate ABS signal, other games use other telemetries to calculate.

6.5.5. Brake Lock Up

Purpose

The Brake Lockup effect generates vibration feedback when one or more wheels begin to lock during braking.

This effect helps the driver detect loss of tire rotation caused by excessive braking force.
Feeling this feedback through the steering wheel allows the driver to reduce brake pressure and regain traction more quickly.

Brake lockup feedback is especially useful in racing simulators where vehicles may not use ABS or when ABS is disabled.

Explanation

When telemetry data indicates that a wheel has stopped rotating relative to the vehicle speed (wheel lock condition), VNM SimCenter generates a vibration signal through the wheelbase.

This vibration simulates the harsh mechanical sensation associated with a tire sliding on the track surface during heavy braking.

The generated signal is mixed with the telemetry force output according to the Telemetry Force Distribution described earlier.

Brake Lockup feedback typically appears as a short, sharp vibration that alerts the driver that the braking force has exceeded the available tire grip.

Parameters

Enable

Enables or disables the Brake Lockup telemetry effect.

When disabled, no vibration feedback will be generated during wheel lock events.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

Square or Triangle waveforms are typically recommended for Brake Lockup feedback because they produce sharper pulses that are easier to perceive.

Frequency

Defines the oscillation frequency of the vibration signal.

Higher frequencies produce faster vibration pulses, while lower frequencies generate slower feedback patterns.

Typical lockup feedback uses medium to high frequencies to simulate tire sliding vibration.

Brake Input BLU Trigger

Defines the minimum brake pedal input required before the Brake Lockup effect can activate.

This prevents the effect from triggering during light braking situations.

Higher values require stronger brake pedal input before lockup feedback is allowed.

BLU Trigger

Defines the telemetry threshold used to detect a wheel lock condition.

Lower values make the effect more sensitive and allow earlier detection of wheel lock.

Higher values require more severe wheel lock conditions before the vibration effect is triggered.

Recommended Usage

Brake Lockup feedback should remain noticeable but not overpower the primary steering forces.

For realistic results:

This effect is particularly useful in racing games where precise brake modulation is required to prevent wheel lock.

6.5.6. Wheel Spin

Purpose

The Wheel Spin effect generates vibration feedback when the driven wheels begin to spin faster than the available tire grip during acceleration.

This effect helps the driver detect loss of traction caused by excessive throttle input. Feeling this feedback through the steering wheel allows the driver to reduce throttle and regain traction more effectively.

Wheel spin feedback is especially useful in high-power vehicles where throttle control is critical.

Explanation

When telemetry data indicates that the driven wheels are rotating faster than the vehicle speed (wheel slip condition), VNM SimCenter generates a vibration signal through the wheelbase.

This vibration simulates the sensation of tire slip that occurs when traction is lost under acceleration.

The generated signal is mixed with the telemetry force output according to the Telemetry Force Distribution described earlier.

Wheel spin feedback typically appears as a vibration that increases when throttle input exceeds the available grip.

Parameters

Enable

Enables or disables the Wheel Spin telemetry effect.

When disabled, no vibration feedback will be generated during wheel spin events.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

Sine waveforms are commonly used for wheel spin feedback because they produce smooth vibration patterns.

Strength

Controls the intensity of the vibration generated during a wheel spin event.

Higher values produce stronger feedback.

Excessive values may interfere with the main steering forces.

Frequency

Defines the oscillation frequency of the vibration signal.

Higher frequency values produce faster vibration patterns, while lower values generate slower oscillations.

Wheel spin feedback typically uses medium to high frequencies to simulate tire slip vibration.

Throttle Trigger

Defines the minimum throttle input required before the Wheel Spin effect can activate.

This prevents the effect from triggering during very light throttle input.

Higher values require stronger throttle input before wheel spin feedback is allowed.

Wheel Spin Trigger

Defines the telemetry threshold used to detect wheel slip.

Lower values make the effect more sensitive and allow earlier detection of wheel spin.

Higher values require more severe wheel slip before the vibration effect is generated.

Recommended Usage

Wheel spin feedback should remain noticeable but not overpower the primary steering forces.

For realistic results:

Proper tuning allows the driver to feel traction loss during acceleration without masking important steering information such as tire grip or vehicle balance.

6.5.7. Understeer

Purpose

The Understeer effect generates vibration feedback when the front tires begin to lose grip during cornering.

This effect helps the driver detect understeer conditions where the vehicle turns less than expected despite steering input.

Feeling this feedback through the steering wheel allows the driver to adjust steering angle or reduce throttle in order to regain front tire grip.

Explanation

When telemetry data indicates that the front tires have exceeded their optimal slip angle and begin to slide, VNM SimCenter generates a vibration signal through the wheelbase.

This feedback represents the reduction in front tire grip that occurs during understeer.

The vibration is designed to alert the driver that the front tires are approaching or exceeding their traction limit.

The generated signal is mixed with the telemetry force output according to the Telemetry Force Distribution described earlier.

Understeer feedback typically appears as a subtle vibration that increases as the front tires lose grip.

Parameters

Enable

Enables or disables the Understeer telemetry effect.

When disabled, no feedback will be generated when the vehicle experiences understeer.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

A sine waveform is commonly used because it produces smooth vibration patterns.

Gain

Controls how strongly the understeer telemetry signal contributes to the generated vibration.

Higher values increase the sensitivity of the effect to understeer telemetry data.

Frequency

Defines the oscillation frequency of the vibration signal.

Lower frequencies produce slower oscillations, while higher frequencies produce faster vibration patterns.

Understeer feedback typically uses lower to medium frequencies so that the vibration remains noticeable but not distracting.

Understeer Trigger

Defines the telemetry threshold required before the Understeer effect activates.

Lower values make the effect more sensitive and allow earlier detection of understeer.

Higher values require stronger front tire slip before the vibration is generated.

Recommended Usage

Understeer feedback should remain subtle and should not overpower the main steering forces generated by the vehicle physics.

For realistic results:

Proper tuning allows the driver to detect front tire grip loss without masking important steering feedback such as tire load or weight transfer.

6.5.8. Oversteer

The Oversteer effect generates vibration feedback when the rear tires begin to lose grip during cornering.

This effect helps the driver detect oversteer conditions where the rear of the vehicle begins to slide outward due to loss of traction.

Feeling this feedback through the steering wheel allows the driver to react quickly by adjusting steering input or throttle to regain rear tire grip and stabilize the vehicle.

When telemetry data indicates that the rear tires exceed their optimal slip angle and begin to slide, VNM SimCenter generates a vibration signal through the wheelbase.

This vibration represents the loss of rear traction that occurs during oversteer.

The feedback is designed to alert the driver that the rear tires are approaching or exceeding their grip limit.

The generated signal is mixed with the telemetry force output according to the Telemetry Force Distribution described earlier.

Oversteer feedback typically appears as a noticeable vibration that increases as the rear tires lose traction.

Parameters

Enable

Enables or disables the Oversteer telemetry effect.

When disabled, no feedback will be generated when the vehicle experiences oversteer.

Waveform

Defines the waveform used to generate the vibration signal.

Available waveform types may include:

Square or Triangle waveforms are often used because they produce clearer vibration pulses that are easier to detect during rapid rear traction loss.

Gain

Controls how strongly the oversteer telemetry signal contributes to the generated vibration.

Higher values increase the sensitivity of the effect to rear tire slip telemetry data.

Frequency

Defines the oscillation frequency of the vibration signal.

Lower frequencies produce slower oscillations, while higher frequencies generate faster vibration patterns.

Oversteer feedback typically uses low to medium frequencies so the vibration remains clearly perceptible during rear traction loss.

Oversteer Trigger

Defines the telemetry threshold required before the Oversteer effect activates.

Lower values make the effect more sensitive and allow earlier detection of rear tire slip.

Recommended Usage

Higher values require stronger oversteer conditions before the vibration is generated.

Oversteer feedback should remain noticeable but should not overpower the primary steering forces.

For realistic results:

Proper tuning allows the driver to detect rear traction loss early without masking important steering feedback such as tire grip and vehicle balance.

6.5.9. General

The General section contains global parameters that affect how telemetry-based force feedback signals are processed before being sent to the wheelbase.

These settings help control the overall behavior of telemetry forces, prevent excessive force spikes, and allow additional steering effects to be applied to telemetry-generated feedback.

Haptic Only

Purpose

Determines whether telemetry effects are applied only to haptic-style vibration signals.

Explanation

When Haptic Only is enabled, telemetry effects generate vibration feedback without modifying the main steering torque produced by the wheelbase.

This mode is useful when telemetry effects are intended to provide additional tactile cues without interfering with the primary steering forces generated by the simulator physics.

When disabled, telemetry effects may also influence the main force feedback signal.

This feature is used to test each effect with its settings.

Haptic Headroom

Purpose
Reserves a portion of torque for telemetry effects.

Explanation
Under high steering load, most torque may be used for steering force, making telemetry effects less noticeable.
Haptic Headroom ensures telemetry feedback remains perceptible.

Behavior

Recommended Usage
Increase if telemetry effects are too weak. Decrease if steering feels too light.

Default value is 30%

Force Spike Reduction Enable

Purpose

Enable or disable the limits extremely large force spikes generated by telemetry signals.

Explanation

Certain telemetry events can generate very sharp force spikes that may feel unrealistic or uncomfortable.

The Force Spike Reduction feature detects sudden increases in force magnitude and limits them to a safer and smoother level.

This helps maintain a more natural steering feel while protecting the driver from abrupt force changes.

Force Spike Trigger

Purpose

Defines the threshold at which force spike reduction begins to activate.

Explanation

When the magnitude of the telemetry force exceeds this threshold, the system identifies the signal as a potential force spike.

Once this threshold is exceeded, the Force Spike Reduction system begins limiting the force output.

Lower values make the system more sensitive and activate spike reduction earlier.

Higher values allow stronger force peaks before limiting occurs.

Force Spike Limit

Purpose

Defines the maximum allowed magnitude of telemetry force when spike reduction is active.

Explanation

When Force Spike Reduction is triggered, the telemetry force output will be clamped to this limit.

This prevents extremely large or unrealistic force spikes from reaching the wheelbase.

Telemetry Condition Force

In certain situations, steering oscillation may occur when telemetry-based force feedback is active.

Although User Effects such as Damper, Friction, and Inertia are generated directly by the wheelbase, increasing damping in the User Effects section may not always eliminate oscillation caused by telemetry-generated forces.

This occurs because telemetry forces are generated dynamically by the telemetry engine before being combined with other force feedback signals. If oscillation originates from the telemetry signal itself, applying condition force at the telemetry stage is more effective.

Friction Gain

Purpose

Adds simulated friction resistance to telemetry-based steering forces.

Explanation

Friction simulates constant resistance in the steering system.

Increasing this value adds a small amount of resistance to wheel rotation, which can help stabilize steering feel when telemetry forces are active.

Damper Gain

Purpose

Adds damping to telemetry-generated steering forces.

Explanation

Damping produces resistance proportional to steering speed.

Increasing Damper Gain can help reduce oscillations and stabilize the wheel when telemetry forces are strong or highly dynamic.

Inertia Gain

Purpose

Adds simulated rotational inertia to telemetry-generated forces.

Explanation

Inertia simulates the rotational mass of a steering system.

Increasing this value makes the steering feel heavier and smoother but may slightly reduce responsiveness.

6.5.10. Static force reduction

Not yet implemented

Telemetry Activation Guide

iRacing

To enable full telemetry support (including high-frequency FFB data), you need to modify the app.ini file.

Step 1
Go to the following folder:
C:/Users/<your account>/Documents/iRacing

Step 2
Open the file app.ini

Step 3
Find and set the following parameters:

irsdkLog360Hz=1
enableFFB360HzInterpolated=1

Explanation:

Result:
Improves telemetry resolution and provides smoother, more detailed Force Feedback.

rFactor 2 / Le Mans Ultimate (LMU)

Telemetry requires an external plugin. Use Simhub to config telemetry for RF2/LMU or use following steps:

Step 1
Download the plugin:
https://github.com/TheIronWolfModding/rF2SharedMemoryMapPlugin/releases/tag/3.7.14.2

Step 2
Extract the plugin files

Step 3
Copy the plugin to the game plugin folder:

Step 4
Launch the game and ensure the plugin is loaded

Notes

GameS and Effects support

Firmware Update allows you to update the internal software of the wheelbase to:

When to Update

You should update the firmware when a new version is released by the manufacturer

Important Notes

How to Access

Step 1 + Open VNM SimCenter

Step 2 + From the top menu, select: + Device → Update Firmware

Firmware update panel will be displayed and detect [DFU] VNM Direct Driver.

Components Description

Device (DFU Mode)

Purpose:
Select the device in DFU (Device Firmware Update) mode

Explanation:

Firmware Version

Purpose:
Select the firmware version to install

Explanation:

Refresh Button

Purpose: Rescan and refresh connected DFU devices

Use case:

File Selection (…)

Purpose: Manually select firmware file

Use case: Beta firmware

Full erase

Purpose:
Erase all existing firmware before flashing

Explanation:

Recommended:

Flash

Purpose:
Start the firmware update process

Abort

Purpose:
Cancel the update process

Log Window

Purpose:
Displays update progress and status

Explanation:

Step 1
Put the wheelbase into DFU mode
(automatic via UI or using reset button if required)

Step 2
Open Firmware Update window

Step 3
Select:

Step 4 (Optional)
Enable Full erase if needed

Step 5 + Click Flash

Step 6
Wait until the process completes
(Check log window for status)

Problem: Device not detected after update
Solution:

Problem: Update stuck or not completing + Solution:

Notes

If your wheelbase occasionally disconnects from the PC during use, this is usually related to USB signal instability, electrical noise (EMI), or system power quality.

9.1.1. Quick check (important)

Before trying all steps, identify your situation:

Testing

Case 1: Disconnect under force (driving)

If yes → indicates a load-dependent issue

Further check:

If no → less likely related to load; may indicate general USB stability or hardware-related issue

Case 2: Random disconnect

Test 1: EMC Stop

If stable → strongly suggests EMI or load-related interference

Test 2: DFU Mode

If yes → USB cable / hardware issue

Test 3: Different PC

Test on another PC or laptop. If it works normally → likely PC USB environment issue

9.1.2. Step-by-step solution

(For EMI / grounding issues and PC USB environment issues)

Step 1: Use a direct motherboard USB connection

Connect the wheelbase directly to a rear USB port on the motherboard.

Avoid:

Step 2: Keep USB cable away from power cables

Ensure the USB cable is not routed alongside

Keep at least 20–30 cm distance if possible.

Step 3. Ground the rig to the PC case

If you are using a metal rig, connect it to the PC case using a wire (or grounding cable):

Rig / Wheelbase → a wire (or grounding cable)→ PC Case

This helps reduce electrical noise and improves stability.

Step 4: Ensure proper grounding of the PC

For best results, the PC should be connected to a properly grounded power outlet (3-pin with earth).

In advanced setups, a dedicated grounding connection (earth-only plug or grounding wire) can be used to connect the rig or PC case to a verified earth ground.

⚠️ Only perform this if you are familiar with proper electrical grounding and safety.

Step 5: Try a different USB port

Step 6: Try a shorter USB cable

If available, use a cable shorter than 1.5 m. Shorter cables are less sensitive to interference.

Step 7: Add ferrite clamps

Attach ferrite clamps to the USB cable, preferably near the device side (e.g., wheelbase).

If multiple USB devices are connected (pedals, shifters, button boxes, etc.), consider adding ferrite clamps to those cables as well.

Electrical noise can travel through USB connections between devices and the PC. In some cases, noise generated by one device may affect others through the shared USB system.

Using ferrite clamps on multiple devices can help reduce overall system noise and improve stability.

Step 8: Check power stability

Step 9: Check power stability

In high electrical noise environments, a USB isolator with isolated power may help improve stability. This is not required in most setups.

If the issue still occurs, please provide the following information:

A. Basic Information

B. When does the issue occur?

C. Additional details (if possible)