This article explains how to compare ONYX RCR performance changes using repeatable measured runs. It applies to the described testing method, not a promised result for stock, SICKO, or Jaws builds.

Readiness Before Measurement

For a FarDriver build, complete Jaws Mode Calibration and Validation through stable Passes 1-3 before measured performance runs. For any build, verify safe mechanical condition, battery/current compatibility, and stable operation first. Use a suitable closed testing area, keep mechanical brakes functional, and stop after a fault, unexpected cutoff, unstable response, or excessive heat. The GPS meter article covers equipment and mounting; this article owns measurement and comparison.

Equivalent runs support comparison, but do not prove the cause of a change by themselves. No sample measured results have been invented for this article.

Test Environment Standardization

For reliable calibration, control the environment as much as possible.

Use the same test road when possible.

Keep comparisons inside a defined battery state band such as 60 to 80 percent.

Keep these conditions as consistent as possible:

  • flat road or known grade
  • same direction or two-direction average
  • minimal wind
  • repeatable start and end points
  • similar ambient temperature
  • similar thermal state of the bike

Do not compare cold runs to heat-soaked runs as if they are equivalent.

Start Method Standard

For timed or measured testing, define the start method before comparing runs.

Keep the following consistent:

  • from stop or rolling start
  • throttle snap or smooth roll-on
  • same gear
  • same rider posture

Inconsistent rider input can make a good setup look worse than it is, or make a worse setup appear faster.

Test Invalidation Rules

Discard a run if any of the following occurs:

  • inconsistent throttle input
  • wheelspin or obvious traction loss
  • different gear than the comparison runs
  • materially different battery state of charge
  • materially different thermal state
  • wind, slope, traffic, or interruption changes the run
  • rider position is noticeably different
  • fault behavior appears during the run

Bad runs should still be logged, but they should not be used as proof of improvement.

Calibration Record Sheet

For each important test run, log:

  • run name
  • battery voltage before run
  • battery voltage during peak load
  • battery percentage or state of charge
  • ambient conditions
  • motor temperature
  • controller temperature
  • line current
  • phase current
  • RPM
  • gear used
  • start method
  • symptom observed
  • parameter changed
  • result after re-test

Calibration becomes much more repeatable when runs are logged instead of remembered.

Rider Input Variability

Measured performance is affected by more than controller settings.

Also account for:

  • throttle consistency
  • body position
  • traction management
  • rider timing during launch

Inconsistent rider input creates inconsistent data.

Cold vs Warm Baseline Awareness

The first run often feels strongest.

Later runs usually reveal the true sustained capability of the bike.

This is normal.

A setup should be judged by how consistently it behaves after the system is no longer cold.

Pass 4 Measured Validation

Pass 4 should only begin after Pass 1 through Pass 3 are stable.

This is the measured validation layer.

It converts rider feel into repeatable evidence.

It does not turn the guide into a benchmark page.

Split Metrics Model

Treat the measured tests differently.

  • 0 to 30 MPH = launch, throttle, traction, and early torque signal
  • 30 to 60 MPH = sustained power, line current, battery support, and upper-speed transition
  • 0 to 60 MPH = overall system validation

This matters because 0 to 60 MPH is one of the most misunderstood metrics in ONYX tuning.

It is useful for validation, but it is not a primary calibration tool.

0 to 30 MPH Validation

This is the most useful measured acceleration check for calibration.

What it reveals:

  • launch tuning quality
  • throttle ramp behavior
  • early torque delivery
  • traction control quality
  • low-speed rideability

Use it as the primary measured calibration signal.

A cleaner and more repeatable 0 to 30 MPH result is usually more valuable than a single dramatic 0 to 60 MPH number.

30 to 60 MPH Validation

This test removes launch variables and helps isolate the rest of the system.

What it reveals:

  • battery support under load
  • line current limitation
  • mid-range to high-speed continuation
  • field weakening transition behavior
  • sustained power delivery

If the bike launches hard but feels flat later, this test is often more useful than 0 to 60 MPH.

0 to 60 MPH Validation

Keep this as a secondary validation metric.

It combines:

  • launch behavior
  • sustained power
  • battery sag
  • rider position effects
  • thermal influence
  • top-end continuation

Use 0 to 60 MPH to confirm overall system consistency.

Do not use it as the first or only tuning metric.

1/8 Mile Validation

Use the 1/8 mile as a sustained acceleration check.

What it reveals:

  • launch quality
  • torque delivery through the run
  • mid-range pull
  • battery sag under continuous load
  • repeatability across multiple runs

If available, record trap speed as well.

Treat this as measured validation, not drag-race bragging.

High-Speed Stability Validation

This is not a top-speed challenge.

Use it to confirm that the bike remains stable, predictable, and thermally manageable near the upper operating range.

Observe:

  • smoothness near top speed
  • oscillation or surging
  • small-throttle stability at high speed
  • approach to speed plateau
  • temperature rise rate
  • repeatability across runs

Speed Plateau Behavior

How the bike approaches top speed matters more than the number itself.

Typical patterns:

  • smooth taper -> healthy system
  • oscillation -> weakening or PID issue
  • abrupt wall -> LimitSpeed or current limitation
  • fade after peak -> thermal or battery limitation

Higher speed does not automatically mean better calibration.

Dragy-Based Performance Validation

Dragy or a similar GPS-based tool is preferred for precision, but it is not required.

Use it for:

  • 0 to 30 MPH
  • 30 to 60 MPH
  • 0 to 60 MPH
  • 1/8 mile ET
  • trap speed
  • repeatability across runs

Rules:

  • compare averages, not one best run
  • repeat runs in a similar battery state band
  • repeat runs in a similar thermal state
  • keep gear and rider posture consistent

Partner-Assisted Calibration

This is optional.

A second person can improve measurement quality, but is not required for correct calibration.

Useful assisted tasks:

  • stopwatch timing from fixed landmarks
  • video capture for review
  • observing launch behavior
  • observing traction loss
  • noting chassis response
  • comparing runs visually

Safety rules:

  • observer must stay clear of the run path
  • rider should never watch a timer while riding

Stopwatch timing is less precise than GPS tools, but it can still be useful if the method is consistent.

Load and Grade Validation

These tests reveal system behavior under real torque demand.

Use them to evaluate:

  • hill climb performance
  • passenger or extra load performance
  • uphill restart behavior
  • loaded regen on descent
  • battery sag under sustained load
  • heating under continuous stress

This layer often exposes issues that flat-road testing hides.

Measured Test Rules

For all measured testing:

  • use the same gear every run
  • use the same start method every run
  • use the same rider posture every run
  • compare runs within a defined battery state band
  • repeat the run at least 2 to 3 times
  • compare averages, not hero runs

Two-Direction Test Rule

When safe and practical, perform the same test in both directions and average the results.

This helps reduce error from:

  • wind
  • slight grade change
  • road bias

Throttle Consistency Rule

Do not stab the throttle in one run and roll on gently in another.

Define the input method first and keep it consistent.

Inconsistent throttle input creates inconsistent data.

Single Run Fallacy

One fast run means very little by itself.

A valid result should repeat.

Require at least 2 to 3 reasonably consistent runs before drawing conclusions.

Run Spacing Rule

Do not mix cold runs and hot runs in the same comparison group unless the point of the test is heat-soak behavior.

Either:

  • allow consistent cooldown between runs
  • or intentionally test heat-stacked behavior

Do not compare them as if they are the same.

Structured Run Naming

Name the runs clearly.

Examples:

  • Baseline_A1
  • Baseline_A2
  • Test_LineCurrent_B1
  • Test_LineCurrent_B2
  • Test_WeakCoeff_C1

Keep failed or invalidated runs in the log. Just mark them clearly.

Comparing Results Between ONYX Builds

Comparison can be useful, but only when context is preserved.

Do not compare raw settings in isolation.

Always compare with context:

  • controller model
  • battery voltage
  • battery current capability
  • motor
  • wheel or tire size
  • rider weight
  • state of charge
  • ambient conditions
  • measured results
  • temperatures
  • throttle feel or stability notes

Recommended comparison fields:

  • Controller
  • Battery voltage
  • Battery current capability
  • Motor
  • Wheel size
  • Rider weight
  • Gear used
  • MaxLineCurr
  • MaxPhaseCurr
  • WeakCurrCoeff
  • LimitSpeed
  • 0 to 30 time
  • 0 to 60 time
  • 1/8 mile ET
  • trap speed
  • peak voltage sag
  • peak controller temp
  • peak motor temp
  • notes on throttle feel and stability

Shared results are useful.

Settings-only comparison is not.

Common False Improvements

Some changes feel better without actually improving the system.

Watch for these traps:

  • feels faster but gives worse 0 to 60 MPH = throttle ramp illusion
  • higher no-load RPM but worse road speed = field weakening misuse
  • stronger launch but worse full-run result = phase-only gain without sustained power
  • one great run with poor repeatability = thermal or battery effect
  • sharper response but worse control = throttle aggressiveness mistaken for performance

Repeatable improvement matters more than dramatic first impression.