Back to Home

Tuning Guides & Methodology

Everything you need to know about capturing perfect datalogs and understanding our engine analytics.

1. Datalogging Best Practices
How to configure VersaTuner for maximum resolution and accuracy.

CRITICAL: The 16-Parameter Limit

VersaTuner places a strict hard limit of exactly 16 selectable logging parameters to ensure the OBD2 bus maintains a fast 10-20 Hz sampling resolution. Because you cannot log any more than 16, every single slot is critical. You must log the exact parameters required by our math engine, otherwise your datalog will be rejected during upload.

The Required Parameters

Since VersaTuner limits you to 16 parameters, trying to configure this manually often leads to missing data or exceeding the limit. To prevent any issues, we have created a pre-configured VersaTuner logging preset that contains exactly the 16 parameters needed for our math engine.

Instructions: Download this file, open VersaTuner, go to the Datalogging tab, click "Import Preset", and select this file. This guarantees your log will upload perfectly to the dashboard.

2. The WOT Pull Procedure
How to record a clean Wide-Open Throttle log for analysis.

To accurately calibrate your MAF sensor and verify Ignition/Fueling safety, we need clean, uninterrupted data sweeps. Follow these exact steps on a closed course or safe stretch of road:

WARNING: Safe Basemap Required!

Never perform a Wide-Open Throttle (WOT) pull on an untested or completely stock tune if you have made major modifications-especially for Forced Induction setups.You must ensure your engine is running a mechanically safe basemap (with sufficiently retarded timing and enriched fueling) before attempting a full WOT pull, otherwise you risk catastrophic engine failure.

  1. Get into 3rd or 4th gear: Start cruising steadily around 3,000 RPM.
  2. Start the Log: Hit the log button in VersaTuner and wait 1-2 seconds for it to register.
  3. Go Wide Open Throttle: Push the accelerator pedal 100% to the floor immediately.If you roll into the throttle slowly or don't push it all the way, the data will be filtered out as part-throttle cruising.
  4. Hold until Redline: Continue accelerating at WOT through 8,500+ RPM.
  5. Lift and Stop: Completely lift off the accelerator, let the engine brake for a moment, and then stop the log.
3. Our Math Engine & Methodology
Understanding how RenesisLab crunches your data behind the scenes.

MAF Scaling Logic

The Mass Airflow (MAF) scaling engine works by analyzing your Short Term (STFT) and Long Term (LTFT) fuel trims during closed-loop operation. It strictly filters out any rows where the engine is cold (ECT < 80°C) or where you are rapidly moving the throttle (transient enrichment), ensuring the correction factors it generates are based on pure, steady-state airflow readings.

Safety Engine & "Shift Knock"

Rotary engines frequently register false "shift knock" or part-throttle drivetrain noise. To prevent the dashboard from throwing false alarms, our Safety Engine intentionally ignores all knock retard data when the engine load is below 0.25 or the throttle is below 5%. It only flags Knock Retard that occurs under medium-to-high load conditions where detonation is genuinely harmful.

Naturally Aspirated vs. Forced Induction

The platform handles NA and Turbocharged/Supercharged (FI) tunes entirely differently. When you upload an NA log, the math engine caps the load bins at 1.155. Any data exceeding this is mathematically impossible for an NA rotary and is discarded to prevent sensor glitches from corrupting your heatmaps. When you check the Forced Induction toggle during upload, the engine expands the grids all the way up to 2.10+ Load to accommodate high boost pressures.

Duty Cycle Calculations

VersaTuner does not export Injector Duty Cycle as a percentage. Instead, it logs the physical time the injector is open (Pulse Width in milliseconds). Our math engine calculates the dynamic duty cycle using the formula: (Pulse Width * RPM) / 600. This is why you will see Duty Cycle percentages in your dashboard even though they aren't in your raw CSV file.