Begin ride validation only after wiring, AutoLearn, throttle signals, and basic protections have been checked. Keep a baseline, change one setting at a time, and use repeatable tests to decide whether the change actually helped.

Calibration Loop

Every calibration change should follow the same sequence:

  1. perform a controlled test
  2. observe behavior and live data
  3. identify the likely parameter group
  4. make a small adjustment
  5. repeat the same test
  6. compare result against the previous run

This loop is the foundation of all calibration work.

Change Isolation Rule

Only adjust one parameter group at a time.

Do not modify:

  • current limits
  • throttle response
  • PID values

in the same pass.

Do not change:

  • current and throttle together
  • PID and throttle together
  • field weakening and LimitSpeed together
  • line current and phase current together unless you are intentionally reverting to a known baseline

If multiple systems are changed together, the result is not diagnosable.

Adjustment Increment Guidelines

Small changes preserve cause and effect.

Use minimal step sizes:

  • current limits -> small percentage changes
  • throttle steps -> small step changes
  • PID values -> very small increments only
  • field weakening -> minimal changes per test

Large changes make the system harder to read.

Baseline Snapshot Rule

Before major changes:

  • save the current parameter set
  • record the current behavior
  • note battery voltage, ambient conditions, and temperatures

This gives you a stable return point if a later change makes the system worse.

Regression Recovery Rule

If a change makes the bike worse:

  1. revert to the last known stable setup
  2. confirm the old behavior returns
  3. re-test the failed change in isolation
  4. reduce the size of the change

Do not keep layering new changes on top of a bad result.

Data vs Feel Conflict Rule

If data and rider impression disagree:

  1. verify the data first
  2. repeat the test
  3. compare against multiple runs
  4. trust repeatable measured behavior over a single subjective impression

Feel still matters, but one strong impression is not enough to override repeatable evidence.

Parameter Interaction Overview

These systems overlap. Do not treat individual parameters as isolated power sliders.

Throttle Behavior

Throttle feel is affected by:

  • Throttle Low / Throttle High
  • ThrottleResponse
  • Throttle Acc Step / Dec Step
  • StartKI / StartKP
  • SpeedKI / SpeedKP

Launch and Low-Speed Torque

Launch behavior is affected by:

  • MaxPhaseCurr
  • Throttle Acc Step
  • StartKI / StartKP
  • SlowDown / SlowDownCoeff

Mid-Range Pull

Mid-range behavior is affected by:

  • MidKI / MidKP
  • MaxLineCurr / MaxPhaseCurr
  • ECOAccCoeff

High-Speed Behavior

High-speed behavior is affected by:

  • LimitSpeed
  • WeakCurrCoeff
  • WeakResponse
  • RPM / Field Weakening Map

Regen and Deceleration Feel

Regen and off-throttle feel are affected by:

  • MaxBackCurr
  • StopBackCurr
  • RPM Regen Table
  • Throttle Dec Step
  • EABSEnable
  • Brake Voltage (if present)

Performance Tradeoffs

More output usually comes with a cost.

  • more MaxPhaseCurr = more torque and more motor heat
  • more MaxLineCurr = more power and more battery and controller stress
  • more field weakening = more top speed potential and more instability and less efficiency
  • faster throttle response = sharper reaction and less controllability

A change that improves one area while worsening another does not automatically mean the parameter is wrong. It means the system is interacting as expected.

Battery Reality Check

Do not diagnose every power problem as a tuning problem.

Typical patterns:

  • strong launch but weak mid-range often indicates line current limit or battery sag
  • high no-load RPM but weak real-world speed often indicates battery limitation
  • large performance changes across battery state of charge often indicate battery dominance
  • weak low-speed torque with acceptable battery behavior often points to phase current or start tuning

Calibration cannot tune around battery limitations.

Heat Source Identification

Thermal problems are easier to fix when you know where the heat is coming from.

  • phase current mainly drives motor heat
  • line current mainly stresses battery and controller
  • field weakening adds controller heat and instability risk

Reduce the parameter that matches the heat source instead of reducing random values.

Thermal Saturation Behavior

A tune that only works cold is not a valid tune.

The first run is often not representative.

The second and third runs usually reveal the real thermal limit.

Heat changes:

  • efficiency
  • current behavior
  • throttle feel
  • rollback behavior

Always validate sustained behavior, not just the first clean pull.

Controller Feedback Awareness

Do not rely on app numbers alone.

Also watch for:

  • audible changes
  • vibration changes
  • unexpected tonal shifts

These can indicate:

  • phase issues
  • angle problems
  • field weakening instability
  • emerging thermal stress

Calibration Testing

This section defines how to validate and refine a completed JAWS MODE tune using real-world riding data.

After applying the full configuration, controlled test riding is used to evaluate how the bike behaves under load and across different operating conditions.

Each test below is tied directly to specific controller parameters, allowing targeted adjustments based on observed behavior.

  • validate performance under real load conditions
  • identify instability, inefficiency, or imbalance
  • apply controlled parameter adjustments based on measured results

Most Important Calibration Tests

If you do not want to work through every calibration test immediately, start with the tests below first.

Prioritize these in order:

  1. Determining True LimitSpeed
  2. Throttle Calibration Validation
  3. Launch / Low-Speed Response Test
  4. Full Throttle Load Test
  5. Field Weakening / High-Speed Stability Test
  6. Regenerative Braking Test
  7. Thermal Behavior Test

If the bike feels mostly correct after these tests, move on to:

  • Part-Throttle Modulation Test
  • Gear Behavior Test
  • Battery Sag / Voltage Drop Test
  • Extended Ride Consistency Test

Calibration Pass System

Calibration should be approached in structured passes. Each pass builds on the previous one, moving from safe baseline validation to full performance refinement.

Do not proceed to the next pass until the current pass is acceptably stable.

Pass 1 - Baseline

Goal:

  • verify correct setup
  • eliminate major configuration errors
  • establish stable baseline behavior

Tests:

  • no-load throttle sweep
  • WO_MaxRPM / LimitSpeed validation
  • low-speed launch test
  • basic throttle validation

Focus Parameters:

  • Throttle Low / High
  • Throttle Acc Step
  • StartKI / StartKP
  • LimitSpeed

Success Criteria:

  • smooth throttle from 0 to 100 percent
  • no error codes
  • stable RPM with no oscillation
  • predictable low-speed control

Pass 2 - Load Testing

Goal:

  • validate performance under rider load
  • identify thermal, current, and stability limits

Tests:

  • full throttle pulls
  • mid-range acceleration
  • hill climb test
  • regen braking test

Focus Parameters:

  • MaxLineCurr / MaxPhaseCurr
  • MidKI / MidKP
  • MaxBackCurr / StopBackCurr
  • WeakCurrCoeff

Success Criteria:

  • strong and consistent acceleration
  • no unexpected cutbacks
  • controlled regen behavior
  • manageable temperatures

Pass 3 - Refinement

Goal:

  • optimize ride feel and smoothness
  • eliminate edge-case issues
  • balance performance vs stability

Tests:

  • part-throttle modulation
  • gear transitions
  • stop-and-go riding
  • extended ride consistency

Focus Parameters:

  • ThrottleResponse
  • SpeedKI / SpeedKP
  • gear ratios and percentages
  • RPM / Field Weakening Map

Success Criteria:

  • smooth, predictable throttle at all speeds
  • no surging or dead zones
  • consistent behavior over time
  • stable high-speed operation

Pass 4 - Performance Validation

Goal:

  • convert rider feel into repeatable measured validation
  • confirm that the tune stays consistent under controlled test conditions
  • validate the whole system without turning the process into speed chasing

This pass is used after Pass 1 through Pass 3 are stable.

Measured testing is used to validate the tune, not to replace the tune.

Tuning Order Lock

Do not move into advanced changes until the lower-level systems are stable.

Do not meaningfully adjust:

  • field weakening
  • advanced PID behavior
  • aggressive regen behavior

until:

  • throttle calibration is correct
  • AutoLearn is valid
  • current limits are realistic
  • launch behavior is under control
  • no-load and load behavior are both stable

Determining True LimitSpeed

After applying the JAWS MODE configuration, this step establishes a stable and usable LimitSpeed based on the actual unloaded capability of the system.

WO_MaxRPM is the highest stable motor speed observed with the rear wheel off the ground, in High gear, at full throttle, with zero rider or road load.

Steps:

  1. place the bike securely on a stand so the rear wheel is completely unloaded
  2. select High gear
  3. apply full throttle and allow RPM to climb until it stabilizes
  4. hold steady throttle for 2 to 3 seconds once peak RPM is reached
  5. ignore brief spikes and record the highest stable RPM value shown
  6. set LimitSpeed to WO_MaxRPM minus 200 RPM

Example:

If WO_MaxRPM = 3000 RPM, then:

  • LimitSpeed = 2800 RPM

This buffer helps prevent:

  • abrupt limiter cutoffs
  • oscillation near max speed
  • unnecessary controller stress at high RPM

Only use stabilized RPM for this method. Do not use brief spikes.

Core Riding Tests

All road tests should be repeatable. When possible, repeat important tests at least 2 to 3 times before changing settings.

Launch / Low-Speed Response Test

Ride from a complete stop on flat ground and apply smooth throttle.

Observe:

  • initial hesitation or delay
  • jerkiness or aggressive hit
  • smoothness of power delivery

Adjust:

  • Throttle Acc Step
  • StartKI / StartKP

Direction:

  • hesitation -> increase Throttle Acc Step slightly
  • too aggressive or jerky -> decrease Throttle Acc Step
  • weak initial torque -> increase StartKI
  • harsh engagement -> reduce StartKP

Mid-Range Acceleration Test

Roll from approximately 20 to 40 MPH and apply throttle in High gear.

Observe:

  • smooth pull vs surging
  • flat spots in acceleration
  • excessive heat buildup

Adjust:

  • MidKI / MidKP
  • ECOAccCoeff

Direction:

  • surging -> reduce MidKP
  • sluggish response -> increase MidKI
  • too aggressive -> increase ECOAccCoeff slightly
  • too soft -> decrease ECOAccCoeff

Full Throttle Load Test

Perform a full throttle pull under rider load.

Observe:

  • sustained acceleration
  • controller or battery cutbacks
  • instability at higher RPM

Adjust:

  • MaxLineCurr
  • MaxPhaseCurr
  • BoostLineCurr / BoostPhaseCurr

Direction:

  • early power drop -> increase MaxLineCurr within system limits
  • weak torque under load -> increase MaxPhaseCurr
  • overheating or instability -> reduce both currents slightly

Field Weakening / High-Speed Stability Test

Ride near the upper RPM range.

Observe:

  • smoothness near top speed
  • oscillation or surging
  • heat buildup

Adjust:

  • WeakCurrCoeff
  • WeakResponse
  • RPM / Field Weakening Map

Direction:

  • instability at high RPM -> reduce WeakCurrCoeff
  • poor top speed -> increase WeakCurrCoeff slightly
  • abrupt transition into high speed -> smooth RPM table percentages

Field Weakening Reality Check

Field weakening should be treated as a late-stage refinement tool, not an early-stage shortcut for speed.

Use caution because excessive weakening can cause:

  • instability near top speed
  • more heat
  • rough transitions
  • fault or protection behavior

If increasing field weakening improves RPM but worsens measured acceleration, it is not a valid gain.

LimitSpeed Validation Test

Use the previously defined WO_MaxRPM method.

Observe:

  • whether the bike hits limiter harshly
  • whether RPM stabilizes cleanly near max

Adjust:

  • LimitSpeed

Direction:

  • hard cutoff -> reduce LimitSpeed further
  • not reaching expected speed -> verify WO_MaxRPM and increase cautiously

Regenerative Braking Test

Ride and apply brakes across multiple speeds.

Observe:

  • regen strength consistency
  • rear wheel instability
  • weak or delayed regen

Adjust:

  • MaxBackCurr
  • StopBackCurr
  • RPM Regen Table

Direction:

  • too aggressive -> reduce MaxBackCurr
  • too weak -> increase MaxBackCurr
  • jerky low-speed regen -> reduce StopBackCurr
  • inconsistent feel -> smooth RPM regen percentages

Thermal Behavior Test

Ride under sustained load such as long pulls or hills.

Observe:

  • motor temperature rise
  • controller temperature rise
  • thermal rollback behavior

Adjust:

  • MaxLineCurr / MaxPhaseCurr
  • MotorTempProtect / ControllerTempProtect

Direction:

  • fast overheating -> reduce current limits
  • no thermal headroom -> improve cooling or reduce load
  • premature limiting -> verify temperature sensor configuration

Post-Run Observation Rule

After each important run, also observe:

  • how quickly temperatures continue rising
  • how the bike behaves immediately after load
  • voltage recovery after throttle release

Heat lag and voltage recovery often reveal problems that do not show up during the pull itself.

Throttle Calibration Validation

Perform slow roll-on and fine throttle inputs.

Observe:

  • dead zone at start
  • non-linear response
  • throttle-related errors

Adjust:

  • Throttle Low / Throttle High
  • ThrottleResponse

Direction:

  • dead zone -> increase Throttle Low slightly
  • early jump -> decrease Throttle Low
  • limited top-end input -> increase Throttle High
  • errors during auto learn -> verify correct throttle type and voltage range

Gear Behavior Test

Switch between Low, Mid, and High gears while riding.

Observe:

  • expected power separation
  • smooth transitions
  • RPM alignment

Adjust:

  • Gear Power Output (%)
  • Gear Speed (%)
  • Ratio In Gears (RPM values)

Direction:

  • gears feel identical -> widen percentage differences
  • low gear too fast -> reduce LowSpeed RPM
  • mid gear weak -> increase MidSpeedLineRatio

Battery Sag / Voltage Drop Test

Perform a full throttle pull from mid-speed and monitor voltage in the app.

Observe:

  • voltage sag under load
  • sudden drops triggering protection
  • inconsistent power delivery at lower charge

Adjust:

  • MaxLineCurr
  • LowVolProtect / LowVolRestore
  • BattSignal / IntRes

Direction:

  • excessive sag -> reduce MaxLineCurr
  • early low-voltage cut -> lower LowVolProtect slightly
  • inconsistent behavior -> verify BattSignal and internal resistance values

Record:

  • battery voltage before the run
  • lowest observed voltage during load
  • voltage recovery after throttle release

Part-Throttle Modulation Test

Ride at steady low and mid speeds while holding partial throttle.

Observe:

  • smoothness at constant speed
  • surging or pulsing
  • difficulty holding steady speed

Adjust:

  • ThrottleResponse
  • Throttle Acc Step / Dec Step
  • SpeedKP / SpeedKI

Direction:

  • surging at steady throttle -> reduce SpeedKP
  • too sensitive input -> reduce Throttle Acc Step
  • sluggish modulation -> increase ThrottleResponse

Deceleration / Coast Behavior Test

Release throttle at different speeds without braking.

Observe:

  • how quickly the bike slows down
  • abrupt vs smooth deceleration
  • unwanted drag

Adjust:

  • Throttle Dec Step
  • Release Throttle
  • RPM Regen Table

Direction:

  • abrupt slowdown -> reduce Throttle Dec Step
  • too much drag -> reduce low-RPM regen values
  • coasting too freely -> increase regen slightly

Low-Speed Maneuvering Test

Ride slowly in tight areas such as parking lots, turns, or stop-and-go traffic.

Observe:

  • controllability at very low speed
  • jerky engagement
  • difficulty balancing throttle

Adjust:

  • StartKI / StartKP
  • Throttle Acc Step
  • SlowDown / SlowDownCoeff

Direction:

  • jerky low-speed control -> reduce StartKP
  • too jumpy -> reduce Throttle Acc Step
  • poor control when rolling -> increase SlowDownCoeff slightly

Reverse / Backward Function Test

Engage reverse and apply throttle gently.

Observe:

  • smoothness in reverse
  • excessive speed or torque
  • delay in engagement

Adjust:

  • BackSpeed
  • RE Function behavior
  • ThrottleResponse

Direction:

  • reverse too fast -> reduce BackSpeed
  • jerky engagement -> soften ThrottleResponse
  • delay -> verify RE configuration

Extended Ride Consistency Test

Ride for 10 to 20 minutes across mixed conditions.

Observe:

  • consistency of power delivery over time
  • thermal derating behavior
  • changes in throttle feel

Adjust:

  • Thermal limits
  • Current limits
  • RPM / Field Weakening Map

Direction:

  • performance drop over time -> reduce current or improve cooling
  • changing throttle feel -> check thermal rollback and compensation
  • instability after heat soak -> reduce WeakCurrCoeff

Pass 4 Measured Validation

Begin measured runs only after Passes 1-3 are stable and the readiness, fault, temperature, and stop checks in this article pass. Log voltage under load, temperatures, gear, start method, and the changed parameter; compare repeat runs under equivalent conditions. One faster run is insufficient. Stop if faults or unstable behavior appear. For the full split-metric method, see Dragy Performance Testing for ONYX RCR .

Read JAWS MODE: Troubleshooting for this subject.

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.

Common Calibration Mistakes

  • increasing current before validating baseline
  • skipping AutoLearn validation
  • adjusting multiple parameter groups at once
  • tuning based on feel without checking data
  • setting LimitSpeed too close to true no-load max RPM
  • using field weakening to cover up poor baseline tuning
  • diagnosing battery sag as a controller problem
  • diagnosing controller limiting as a battery problem
  • making large changes instead of incremental ones
  • comparing mixed-SOC runs
  • comparing mixed-gear runs
  • trusting one good run too much

Hardware Limit Reminder

Calibration cannot fix:

  • weak batteries
  • bad connectors
  • wiring faults
  • inaccurate sensors
  • failing cooling systems

Do not tune around hardware problems.

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.

When to Stop Tuning

Stop tuning when:

  • gains become inconsistent
  • heat or stress rises faster than performance improves
  • the bike becomes less predictable
  • performance varies more than it improves
  • behavior is stable across battery state, temperature, and ride duration

A slightly slower but more stable tune is usually the better calibration.

Final Calibration State

A correctly calibrated system should:

  • deliver smooth and predictable throttle from 0 to 100 percent
  • maintain stable RPM behavior with no abnormal oscillation
  • produce consistent acceleration without dead zones or random cutback
  • approach top speed cleanly without harsh limiter contact
  • remain thermally manageable under repeated real-world load
  • feel consistent across battery state and ride duration

A properly calibrated JAWS MODE setup should feel:

  • smooth off the line
  • strong through mid-range
  • stable at top speed
  • predictable under braking
  • thermally stable under sustained load

A correct calibration is defined by consistency across conditions, not peak performance in a single run.

Calibration Drift

A stable tune can change over time.

Reasons include:

  • connector aging
  • resistance change
  • battery aging
  • temperature and seasonal changes
  • cooling changes
  • hardware wear

Re-validate the tune periodically, especially after hardware changes or when behavior starts to drift.

Test Setup and Safety

Before performing AutoLearn, static testing, or LimitSpeed validation, the bike must be placed in a controlled and safe test condition.

These procedures involve spinning the motor at high speed without load and must be treated as active mechanical operations.

Required Setup

  • rear wheel lifted completely off the ground
  • bike stabilized on a secure stand
  • clear space around the wheel and drivetrain
  • no rider load

Chain / Drivetrain Considerations

For highest safety and cleanest results:

  • removing the chain is recommended during AutoLearn and no-load testing
  • this isolates the motor from drivetrain resistance
  • prevents unintended torque transfer
  • reduces risk of mechanical injury

If the chain is left installed:

  • ensure full clearance
  • do not stand near rotating components
  • avoid loose clothing or contact points

Safety Notes

  • never perform AutoLearn with the bike under load
  • never apply throttle while the bike is unstable
  • always verify rotation direction before full throttle
  • always perform a brief low-throttle spin before high-RPM testing
  • stop immediately if vibration, noise, or instability occurs

Data Monitoring During Calibration

During all calibration tests, monitor live data in the FarDriver app.

Minimum required metrics:

  • Battery Voltage (V)
  • Line Current (A)
  • Phase Current (A)
  • Motor RPM
  • Motor Temperature
  • Controller Temperature
  • Throttle Input (%)

Where available, also watch:

  • gear state
  • brake state
  • error status
  • thermal rollback behavior
  • battery voltage before the test and during peak load

Safe Operating Guidelines

  • Motor temperature: keep below 120C
  • Controller temperature: keep below 90C
  • sustained Line Current should remain within battery capability
  • Phase Current should not exceed motor thermal limits

Exceeding these values may result in:

  • thermal rollback
  • component damage
  • reduced system lifespan