Jaws Mode FarDriver Parameters and Behavior for ONYX RCR

Reference Values vs the Settings Profile

Values in this article explain parameter behavior. They include a different Ratio In Speed curve and LowSpeedPhaseRatio from the Jaws Mode Settings profile. At 500 RPM the reference uses 100% versus 98% in the settings; at 2250 RPM it uses 80% versus 58%; LowSpeedPhaseRatio is 65% versus 60%. The dataset revision or hardware basis for these differences is not recorded. These are distinct records, not interchangeable confirmed defaults. Preserve motor-specific learned/calibration values and verify applicability before writing settings.

ONYX FarDriver JAWS MODE Controller Reference

This reference explains the core controller behavior of the ONYX-focused FarDriver JAWS MODE configuration.

It covers Simple Mode and Pro NBLE, motor/current relationships, input functions, protection, PID, and firmware features. Detailed gear/RPM ratios, regenerative braking, display/calibration measurements, and throttle-cutout diagnosis have their own linked articles.

Every section explains:

• what the parameter or system does
• how it behaves under load
• what it interacts with
• what it feels like when changed
• where it reaches diminishing returns
• what fails when pushed too far
• how it should be tuned in real ONYX QS motor setups

This is not generic FarDriver documentation. It is written specifically around ONYX builds using ND-series controllers, QS motors, and real-world riding behavior.

JAWS MODE Workflow

Performance Build -> Wiring -> AutoLearn -> Tuning -> Parameters -> Calibration

SYSTEM OVERVIEW

This defines the electrical and hardware boundaries that all controller behavior operates within. Power delivery, thermal limits, and control stability are all constrained by the combination of controller capability, system voltage, and motor characteristics.

• Controllers -> define current ceiling and thermal handling
• Voltage -> sets power potential and protection scaling
• Motors -> determine torque response, efficiency, and heat behavior
• PolePairs (16) -> required for correct RPM calculation and stable commutation
• JAWS MODE -> prioritizes fast current delivery and minimal filtering

All tuning and parameter behavior in later sections operate inside these limits.

CORE SYSTEM RELATIONSHIPS

Power = Voltage × Current
Heat ≈ Current² × Time
Voltage Sag ≈ Current × Internal Resistance

These systems are directly coupled. Increasing one always shifts load into another.

• Increasing MaxPhaseCurr (Torque) increases acceleration, but heat rises exponentially and quickly becomes the limiting factor
• Increasing MaxLineCurr (Power) improves high-speed pull, but increases voltage sag, reducing effective power under load
• Increasing Weakening (Speed) raises top speed, but reduces efficiency and torque while increasing instability at high RPM
• Increasing Throttle Acc Step (Control) makes response feel faster, but creates current spikes that add heat and stress without increasing sustained torque

Real-world behavior:

• High torque + high power -> fastest acceleration, but maximum thermal load
• High power + low voltage -> severe sag, weak top-end performance
• High weakening + high current -> unstable high-speed behavior
• High throttle response + high phase current -> sharp feel, but inefficient and heat-heavy

Limits follow a consistent pattern:

Increase -> Gain -> Tradeoff -> Limitation

Tuning Guidance (ONYX-Specific)

• Do not increase MaxPhaseCurr and MaxLineCurr simultaneously without monitoring motor and controller temperature
• If acceleration is strong but weakens at speed, increase MaxLineCurr before increasing MaxPhaseCurr
• If the system becomes unstable at high RPM, reduce WeakCurrCoeff or weakening response before adjusting current limits
• If throttle feels aggressive but inefficient, reduce Throttle Acc Step before lowering current values
• On QS motors, excessive phase current produces diminishing returns quickly and converts directly into heat rather than usable torque

SIMPLE MODE SCREEN

Core behavior:

• SIMPLE MODE provides high-level control over system behavior without modifying deep controller logic
• It defines how the system behaves at a functional level: direction, low-speed response, gear scaling, and feature control
• It does not directly define peak performance limits, but it strongly influences usability and ride feel

Interaction layer:

• Base Parameters set foundational behavior that all other systems depend on
• Three Speed settings scale the output defined in PRO NBLE (current and speed limits)
• Functions modify how and when systems activate, including regen, safety, and external inputs
• All SIMPLE MODE parameters act as modifiers on the deeper PRO NBLE configuration

Real-world behavior:

• Proper configuration -> predictable throttle, stable braking, and controllable power delivery
• Gear system -> allows quick adjustment between low, mid, and high performance modes
• Functions -> enable or disable features depending on riding conditions and preferences
• Misconfiguration -> noticeable immediately in throttle feel, braking, or system behavior

Limits and failure modes:

• SIMPLE MODE cannot override incorrect PRO NBLE configuration
• Incorrect base parameters -> unstable or unusable system behavior
• Improper gear scaling -> inefficient performance or excessive heat
• Disabled or misused functions -> reduced safety or unexpected behavior

Tuning Guidance (ONYX-Specific)

• Configure SIMPLE MODE first to establish stable baseline behavior before tuning PRO NBLE
• Use gear scaling to manage usable performance without changing core current limits
• Keep base parameters aligned with actual hardware (voltage, direction) at all times
• Enable only necessary functions - avoid unnecessary system complexity
• Treat SIMPLE MODE as the user-facing control layer and PRO NBLE as the performance layer

BASE PARAMETERS

Core behavior:

• These parameters define baseline system behavior before any high-power tuning is applied
• They do not directly increase performance, but they control how the system responds at low load and during transitions

Interaction layer:

• Motor Reverse Direction must match Motor Direction or throttle behavior becomes inverted
• Rated Voltage directly affects all protection thresholds and voltage-based calculations
• Low Power Control Mode shapes how throttle inputs translate into current at low speed
• Energy Feedback interacts with MaxBackCurr and regen tables to define total braking force

Real-world behavior:

• Incorrect direction settings -> immediate unusable throttle behavior
• Incorrect voltage -> random cutouts or battery stress under load
• Poor low power mode tuning -> jerky launches or overly soft response
• Aggressive regen -> strong braking but increased risk of rear wheel slip

Limits and failure modes:

• Motor Reverse Direction has no performance gain, only correct/incorrect states
• Rated Voltage outside actual pack voltage -> protection system failure
• Low Power Control Mode too low -> unresponsive throttle
• Energy Feedback too high -> instability under braking

Tuning Guidance (ONYX-Specific)

• Set Motor Reverse Direction correctly first before any other tuning
• Always match Rated Voltage to actual system voltage to avoid protection errors
• Use 11-SOP for balanced ONYX behavior; adjust only if low-speed control is problematic
• Increase Energy Feedback gradually and validate stability under braking, especially on QS motors
• Do not attempt to compensate poor throttle behavior with high current - fix Low Power Control Mode first

CONFIGURATION VALUES

Core behavior:

• These values define the baseline operating state of the controller before load or tuning changes are applied
• They establish how the system behaves at startup, low throttle, and during braking

Interaction layer:

• Motor Reverse Direction must align with Motor Direction to maintain correct throttle orientation
• Rated Voltage determines how all voltage-based protections behave under load and regen
• Low Power Control Mode directly influences how throttle input converts into current at low speed
• Energy Feedback sets the baseline regen level, which is then scaled by MaxBackCurr and regen mapping

Real-world behavior:

• Correct configuration -> predictable throttle, stable braking, and consistent protection behavior
• Incorrect direction -> immediate throttle inversion
• Incorrect voltage -> unstable cutoffs or battery stress under acceleration or regen
• Medium EABS -> controlled braking suitable for street riding without excessive slip

Limits and failure modes:

• Direction mismatch -> unusable throttle control
• Voltage mismatch -> protection system malfunction
• Low Power Mode too aggressive -> jerky launches
• High regen settings -> rear wheel instability under braking

Tuning Guidance (ONYX-Specific)

• Verify Motor Reverse Direction and Motor Direction alignment before any tuning
• Always match Rated Voltage to the actual battery (72V system) to ensure correct protection behavior
• Use 11-SOP as a stable baseline for QS motor control; only adjust if low-speed response is problematic
• Keep EABS at Medium for balanced ONYX street riding; increase only if additional braking force is required and traction allows
• Do not attempt to fix low-speed behavior with current or throttle tuning - correct Low Power Control Mode first

Motor Reverse Direction

Core behavior:

• This parameter strictly controls motor rotation direction and does not influence torque, power, or efficiency
• It operates at the control logic level, flipping phase sequence electronically

Interaction layer:

• Directly linked to Motor Direction in Pro NBLE settings
• Both parameters must align to ensure correct rotational output
• Does not interact with current, voltage, or performance tuning systems

Real-world behavior:

• Correct setting -> normal throttle response and expected forward motion
• Incorrect setting -> throttle input results in reversed wheel direction
• No change in acceleration, speed, or thermal behavior

Limits and failure modes:

• No performance benefit from adjustment
• Only valid states are correct or incorrect
• Misconfiguration results in unusable throttle behavior

Tuning Guidance (ONYX-Specific)

• Set Motor Reverse Direction correctly before any other configuration or tuning
• If throttle direction is reversed, correct this parameter instead of adjusting wiring or other settings
• Always verify alignment with Motor Direction after controller or firmware changes
• Do not attempt to compensate for incorrect direction using any performance parameters

Rated Voltage

Core behavior:

• Rated Voltage defines how the controller interprets battery voltage across all systems
• It does not change actual power, but it scales protection thresholds and internal calculations

Interaction layer:

• Directly linked to LowVolProtect and OverVolProtect thresholds
• Affects how the controller reacts to voltage sag under load and voltage rise during regen
• Influences battery protection behavior across all operating conditions

Real-world behavior:

• Correct value -> predictable cutoff behavior and stable operation under load
• Too low -> premature low-voltage cutoffs during acceleration
• Too high -> battery over-discharge risk and delayed protection response
• Under regen -> incorrect value can trigger unexpected over-voltage cutouts

Limits and failure modes:

• Does not increase performance when raised or lowered
• Incorrect value leads to protection system misbehavior
• Mismatch between actual battery voltage and Rated Voltage causes instability under load and braking

Tuning Guidance (ONYX-Specific)

• Always match Rated Voltage to the actual battery system (72V, 84V, or 96V)
• Do not use Rated Voltage as a tuning parameter - it is a system definition value
• If experiencing random cutouts under load, verify Rated Voltage before adjusting current limits
• If regen causes unexpected shutdowns, confirm Rated Voltage alignment with OverVolProtect settings

Low Power Control Mode

Core behavior:

• This parameter controls how throttle input is translated into current at low speeds and low load conditions
• It shapes the initial response curve before high-current systems dominate behavior

Interaction layer:

• Works with ThrottleResponse to define overall throttle feel
• Interacts with ECOAccCoeff to scale acceleration in low-power or ECO conditions
• Influences how quickly phase current begins ramping from zero

Real-world behavior:

• Proper setting -> smooth launches, predictable throttle, easy low-speed control
• Too aggressive -> jerky starts, difficult modulation in traffic or tight maneuvers
• Too soft -> delayed response, weak initial acceleration feel

Limits and failure modes:

• Does not increase peak power or torque
• Only affects low-speed and low-throttle behavior
• Incorrect configuration leads to poor rideability, not performance gain or loss

Tuning Guidance (ONYX-Specific)

• Use 11-SOP as the baseline for QS motor setups on ONYX builds
• If launches feel jerky, reduce aggressiveness here before adjusting Throttle Acc Step
• If throttle feels unresponsive at low speed, adjust this before increasing current limits
• Do not attempt to fix low-speed behavior with MaxPhaseCurr - correct this parameter first
• Fine-tune in combination with ThrottleResponse for balanced control

Energy Feedback (EABS)

Energy Feedback, MaxBackCurr, brake-input logic, and battery charge acceptance govern electrical deceleration. Mechanical brakes remain necessary. See FarDriver Regenerative Braking and Full-Battery Cutouts for the complete EABS explanation and reference tables.

Riding Modes and RPM Scaling

MaxPhaseCurr sets the phase-current ceiling; MaxLineCurr sets the battery-current ceiling. Riding-mode ratios and RPM-dependent scaling modify those limits together with speed and weakening behavior. For the complete tables, mode interactions, and thermal/traction tradeoffs, see FarDriver Ratio In Speed and Gear Ratios.

FUNCTIONS (SIMPLE)

Core behavior:

• These functions do not increase performance, but control system behavior, safety, and ride stability
• They operate as logic-level features that modify how and when current is applied or restricted

Interaction layer:

• Cruise holds throttle output, interacting directly with throttle mapping and current delivery
• P Function overrides motor output entirely, locking rotation regardless of throttle input
• Auto Return P depends on P Function timing and system idle detection
• RE Function enables regen behavior, interacting with Energy Feedback and MaxBackCurr
• TCS Function limits rapid torque spikes by controlling how quickly current is applied

Real-world behavior:

• Cruise -> maintains speed but removes active throttle control
• P Function -> prevents rolling on inclines or during parking
• Auto Return P -> adds safety but may engage unexpectedly if timing is too short
• RE Function -> allows regenerative braking, reducing reliance on mechanical brakes
• TCS Function -> improves traction, especially on high-power QS setups

Limits and failure modes:

• Cruise misuse -> unsafe if road conditions change
• P Function engaged while moving -> abrupt stop or system conflict
• Auto Return P misconfigured -> unexpected lock behavior
• High regen with RE -> potential over-voltage cutout
• TCS too aggressive -> reduced performance and delayed response

Tuning Guidance (ONYX-Specific)

• Leave Cruise disabled unless specifically needed for steady-speed riding
• Use P Function for parking stability, especially on inclines
• Disable Auto Return P unless required - can interfere with normal operation
• Keep RE enabled for normal ONYX setups, but balance with regen limits to avoid cutouts
• Use TCS on high-power builds (QS260/QS273) to reduce wheel spin; disable for maximum raw performance

CONFIGURATION VALUES

Core behavior:

• These values define how auxiliary systems, safety logic, and external inputs behave in the controller
• They do not directly increase performance, but significantly affect usability, safety, and ride control

Interaction layer:

• Cruise, ACC, and DEC inputs interact with throttle and current delivery systems
• RE Function enables regen, interacting with Energy Feedback and MaxBackCurr
• P Function and Park logic override motor output regardless of throttle
• TCS modifies how quickly torque is applied, interacting with phase current and throttle response
• Safety-related functions (Seat, Side Stand) can interrupt motor operation based on external conditions

Real-world behavior:

• Most functions disabled -> direct, manual control with minimal interference
• RE enabled -> predictable regenerative braking
• TCS (Asphalt) -> improved traction on high-power setups
• Disabled safety features -> fewer interruptions, but increased rider responsibility

Limits and failure modes:

• Disabled safety systems -> increased risk during operation (stand down, no seat detection)
• Incorrect pin mapping -> unintended acceleration or braking inputs
• Regen enabled with high settings -> possible over-voltage cutouts
• TCS active -> smoother output but reduced aggressive response

Tuning Guidance (ONYX-Specific)

• Keep RE Function enabled for standard ONYX riding; tune regen strength separately
• Use TCS (Asphalt) on high-power QS builds to manage traction; disable only for maximum raw output
• Leave Cruise, Auto Return P, and Park disabled unless specifically required
• Verify all external pin mappings (ACC/DEC) before enabling to avoid unintended inputs
• Only disable safety features (Side Stand, Seat) if fully understood - these remove protection layers

PRO NBLE SCREEN

Core behavior:

• PRO NBLE defines the full control system of the controller, including motor definition, current delivery, throttle behavior, and protection logic
• Unlike Simple Mode, these parameters directly control how the system behaves under load and determine overall performance

Interaction layer:

• Motor definition parameters (AngleDetect, PolePairs, PhaseOffset) determine whether the system operates correctly at all
• Power system (MaxPhaseCurr / MaxLineCurr) defines torque and total power, interacting with thermal limits
• Throttle system controls how quickly current is applied, interacting with both torque and heat generation
• Speed and weakening systems extend RPM but reduce efficiency and stability
• Protection systems override all others when limits are exceeded

Real-world behavior:

• Correct configuration -> smooth, powerful, and stable operation across all speeds
• High current + aggressive throttle -> strong performance but rapid heat buildup
• High weakening -> increased top speed with reduced pull and stability
• Protection triggers -> sudden power reduction or shutdown under extreme conditions

Limits and failure modes:

• Incorrect motor definition -> no operation or severe instability
• Excessive current -> heat saturation and motor/controller damage
• Aggressive throttle + high current -> inefficient, high-stress system
• Weakening pushed too far -> oscillation and loss of control at speed
• Protection thresholds reached -> cutouts or forced power reduction

Tuning Guidance (ONYX-Specific)

• Verify motor definition parameters first - incorrect values will invalidate all other tuning
• Set MaxPhaseCurr and MaxLineCurr within safe thermal limits for QS motors before adjusting throttle or speed
• Tune throttle response after current limits are stable to avoid unnecessary heat
• Use weakening conservatively - ONYX builds prioritize usable power over peak speed
• Do not bypass or ignore protection systems - frequent triggering indicates improper tuning

PARAMETERS (FULL LIST)

Core behavior:

• These parameters define the complete controller behavior including motor definition, current limits, throttle response, speed limits, and weakening
• They operate together as a unified control system where each parameter influences overall performance, efficiency, and stability
• The RatedPower value does not limit real output. It tells the controller how to interpret motor strength, torque modeling, and thermal assumptions. It affects internal calculations, not power caps.

Throttle Voltage Cutout Check

Throttle Low and Throttle High are calibration values. If power drops at a specific throttle position, stop and verify the measured signal against the configured bounds before changing current, weakening, or PID. See FarDriver Throttle Calibration and Cutout Diagnostics.

The following relationships continue the full parameter-list discussion.

Interaction layer:

• Motor definition parameters (AngleDetect, PolePairs, PhaseOffset) must be correct for any operation to function properly
• Current system (MaxPhaseCurr / MaxLineCurr) defines torque and power, interacting with heat and voltage sag
• Throttle system (Response, Acc/Dec Step) controls how quickly current is applied and removed
• Weakening system extends speed but reduces efficiency and increases instability
• Protection and calibration parameters ensure safe and accurate operation

Real-world behavior:

• Correct configuration -> smooth, powerful, predictable performance
• High phase current -> strong acceleration but rapid heat buildup
• High line current -> better high-speed pull but increased voltage sag
• Aggressive throttle settings -> sharp response but inefficient and heat-heavy
• Weakening -> increased top speed but reduced torque and stability

Limits and failure modes:

• Incorrect motor definition -> no operation or unstable behavior
• Excessive current -> thermal overload and component stress
• Aggressive throttle + high current -> inefficient system with high heat
• Weakening pushed too far -> instability at speed
• Incorrect calibration -> poor throttle response or dead zones

Tuning Guidance (ONYX-Specific)

• Verify motor definition parameters first - these are non-negotiable for stable operation
• Set MaxPhaseCurr based on QS motor thermal limits before increasing MaxLineCurr
• Increase MaxLineCurr only after phase current is stable to improve high-speed performance
• Keep Throttle Acc Step below aggressive thresholds (~140) to avoid unnecessary heat
• Use weakening conservatively - ONYX builds favor usable power over peak speed
• Always validate throttle calibration (0.6V-4.35V) before tuning response parameters

Regen and Battery Protection

Regen returns energy to the battery and can cause a voltage-protection event near full charge. Confirm battery charge acceptance and mechanical braking before testing. The detailed current and RPM reference is in FarDriver Regenerative Braking and Full-Battery Cutouts.

FUNCTIONS (ADVANCED)

Core behavior:

• Advanced Functions define hardware-level control logic and input mapping
• These parameters determine how external signals (pins) interact with controller behavior
• They act as the bridge between physical inputs and internal control systems

Core principle:

Physical Input -> Logic Mapping -> System Behavior

Interaction layer:

• Pin mappings directly control:
  • Gear selection (High/Low speed pins)
  • Direction (Forward/Backward)
  • Safety systems (Seat, SideStand, Anti-theft)
• Boost system interacts with BoostLineCurr and BoostPhaseCurr
• Brake and Follow interact with regen system (EABS, MaxBackCurr)
• Gear logic ties into Ratio In Gears and overall power scaling

Real-world behavior:

• Proper configuration -> predictable control and safe operation

• Gear pins -> instant switching between performance modes

• Boost -> temporary high power when triggered

• Safety pins -> prevent unsafe operation (stand, seat, theft)

• Misconfiguration results in:

  • Unexpected behavior (reverse, throttle lock, no response)
  • Disabled safety systems
  • Incorrect gear or boost activation

Limits and failure modes:

• Incorrect pin mapping -> non-functional or dangerous behavior
• Disabled safety inputs -> increased risk during operation
• Boost misuse -> thermal overload
• Brake misconfiguration -> harsh cutoff or lack of regen

Tuning Guidance (ONYX-Specific)

• Only enable pins that are physically wired and verified
• Keep unused pins set to Invalid to avoid unintended behavior
• Verify gear pins match actual switch wiring before riding
• Use Boost conservatively - ONYX setups already run high current
• Ensure brake + regen (Follow = EABSWhenBrake) is properly configured for smooth deceleration
• Do not disable safety-related pins unless intentionally modifying system behavior

Measurement and Display Accuracy

Display scaling changes reported speed or distance; fixed calibration constants also affect measurements used by protection and control. These are separate from performance tuning. Preserve hardware calibration and use FarDriver Display Settings and Telemetry Accuracy when investigating a mismatch.

PROTECT

Core behavior:

• Protection system defines hard safety limits for voltage, temperature, current behavior, and system faults
• These parameters override all performance settings when thresholds are exceeded
• The system continuously monitors conditions and intervenes to prevent damage

Core principle:

If Limit Exceeded -> Reduce Power or Shutdown

Interaction layer:

• Voltage protection interacts heavily with regen (OverVolProtect) and load (LowVolProtect)
• Temperature protection interacts with MaxPhaseCurr and sustained load
• IntRes influences voltage sag modeling, affecting low-voltage cutoffs under load
• Throttle and safety inputs prevent unintended acceleration or faults
• Turtle mode reduces current when faults or limits are approached

Real-world behavior:

• High load -> voltage sag -> potential low-voltage cutoff

• Strong regen -> voltage spike -> possible over-voltage cutout

• Sustained acceleration -> heat buildup -> thermal limiting

• Fault conditions -> system enters reduced power (turtle mode) or shuts down

• Riders experience:

  • Sudden power loss under extreme load
  • Reduced performance when hot
  • Cutouts during aggressive regen on full battery

Limits and failure modes:

• Overly aggressive limits -> frequent cutouts and poor usability
• Too loose limits -> risk of motor, controller, or battery damage
• Incorrect IntRes -> inaccurate sag prediction -> unexpected cutoffs
• Disabled safety (ThrottleLost, etc.) -> unsafe operation

Tuning Guidance (ONYX-Specific)

• Set voltage limits based on actual battery pack (72V nominal -> align cutoffs accordingly)
• Ensure OverVolProtect accounts for regen spikes on full charge
• Keep thermal limits conservative - QS motors generate high heat under load
• Adjust IntRes to match real battery behavior for accurate sag modeling
• Do not disable safety features unless fully understood
• If experiencing cutouts:
  • Check voltage sag (LowVolProtect)
  • Check regen spikes (OverVolProtect)
  • Check thermal limits before increasing current

PID PARAS

Core behavior:

• PID parameters define how the controller responds to error between target and actual motor behavior
• They control stability, smoothness, and responsiveness across different operating regions
• The system uses multiple PID layers:
  • Start (low speed)
  • Mid (normal operation)
  • Max (high load/high speed)
  • Speed loop (RPM control)

Core principle:

Error -> PID Correction -> Adjust Current

Interaction layer:

• PID directly controls how MaxPhaseCurr is applied over time
• Interacts with:
  • Throttle system (input demand)
  • Ratio In Speed (available torque)
  • Motor definition (stability baseline)
• Poor PID tuning amplifies instability from aggressive current or weakening settings

Real-world behavior:

• Low gains -> smooth but sluggish response

• Balanced gains -> stable, responsive acceleration

• High gains -> aggressive response but risk of oscillation

• Riders experience:

  • Proper tuning -> smooth, controlled power delivery
  • Poor tuning -> jerky throttle, surging, or unstable speed holding

Limits and failure modes:

• Too high KP -> oscillation, vibration, unstable throttle
• Too high KI -> slow drift or overshoot
• Too low values -> weak response, delayed acceleration
• Mismatched PID zones -> inconsistent feel across speed ranges

Tuning Guidance (ONYX-Specific)

• Leave PID close to known stable values unless necessary - this is not a primary tuning layer
• Adjust only after current, throttle, and ratio systems are correctly configured
• Focus on:
  • StartKl / StartKP -> launch feel
  • MidKP -> main riding response
  • MaxKP -> high-speed stability
• Avoid increasing gains to compensate for weak torque - fix current settings instead
• If experiencing oscillation, reduce KP values before changing other systems

PRODUCT

Core behavior:

• Product parameters define firmware-level features, toggles, and secondary behaviors
• They act as a feature control layer, enabling or disabling subsystems and fine-tuning non-core behavior
• These do not define primary performance, but they modify how systems behave and interact

Core principle:

Feature Enabled -> System Behavior Modified

Interaction layer:

• Directly interacts with:
  • Regen system (EABSEnable, ReCurrRatio, Fast RE)
  • Weakening system (WeakCurrCoeff, DeepWeak)
  • Safety systems (SeatEnable, Anti-theft, Park)
  • Throttle system (LearnThrottle, StartIs)
• Works alongside:
  • PROTECT (safety overrides)
  • FUNCTIONS (input control)
  • CURRENT system (performance base)

Real-world behavior:

• Proper configuration -> clean, predictable system behavior with correct features enabled

• Disabled features -> simpler system, fewer variables

• Enabled features -> more functionality but increased complexity

• Riders experience:

  • Regen behavior changes (EABS, Fast RE)
  • Launch feel differences (StartIs)
  • Feature availability (cruise, reverse, anti-theft)

Limits and failure modes:

• Enabling unnecessary features -> unpredictable interactions
• Incorrect calibration (throttle learn values) -> poor throttle response
• Aggressive weakening (DeepWeak) -> instability at speed
• Misconfigured safety features -> unsafe operation

Tuning Guidance (ONYX-Specific)

• Keep non-essential features disabled for stability (Seat, Push, Anti-theft unless used)
• Ensure EABSEnable = 1 for consistent regen behavior
• Avoid enabling DeepWeak unless specifically tuning for high-speed builds
• Verify throttle learning values before tuning throttle response
• Use StartIs to fine-tune launch feel only after current settings are correct
• Treat PRODUCT as a feature layer, not a primary performance tuning layer

FINAL INSIGHT

Core behavior:

• All FarDriver systems follow a non-linear performance curve
• Initial increases in parameters produce strong gains, but this quickly transitions into diminishing returns
• Beyond the optimal range, additional input results in heat, stress, and instability instead of usable performance

Core principle:

Increase -> Gain -> Plateau -> Heat -> Failure

Interaction layer:

• This pattern applies universally across:
  • MaxPhaseCurr (torque)
  • MaxLineCurr (power)
  • Weakening (speed)
  • Throttle Acc Step (response)
• All systems are thermally coupled:
  • Increasing one parameter increases total system load
  • Combined increases accelerate heat buildup exponentially

Real-world behavior:

• Low settings -> predictable, safe, but underpowered

• Mid settings -> best balance of acceleration, speed, and thermal stability

• High settings -> feels faster initially, but performance becomes inconsistent

• Extreme settings -> bike feels aggressive but quickly loses efficiency and stability

• Riders experience:

  • Strong gains early in tuning
  • Then “fake performance” (more noise, heat, and harshness without real speed gains)

Limits and failure modes:

• Chasing peak numbers -> reduced real-world performance
• Excessive current -> motor and controller overheating
• Excessive weakening -> instability at speed
• Excessive throttle aggression -> stress without torque gain

Tuning Guidance (ONYX-Specific)

• Always tune for the mid (optimal) zone, not the maximum possible value
• Use temperature and consistency as your primary indicators, not peak output
• If a change increases heat more than performance, it is past the optimal point
• Balance torque, power, and speed instead of maximizing a single parameter
• The fastest and most reliable setups operate below the system’s maximum limits

Final takeaway:

Performance is limited by heat and system balance, not by how high you can set a value

Where To Go Next

• Wiring Harness
• AutoLearn
• Calibration

Related Articles

• Riding modes and RPM ratios
• Regenerative braking
• Display and telemetry accuracy
• Throttle cutout diagnostics