This article distinguishes measured throttle voltage, configured thresholds, throttle-type examples, and battery-related power loss on FarDriver-equipped ONYX RCR builds.
Applicability and Immediate Stop Check
Stop if the throttle signal is unstable, the wheel moves unexpectedly, or power drops at a repeatable throttle position. Verify wiring and controller input mode before further riding tests. A position-dependent symptom can suggest an input problem, but does not prove the cause without signal and fault evidence. High-load sag, BMS protection, loose wiring, and thermal protection still need their own checks.
The source’s 0.6V/4.35V and 1.1V/4.3V examples belong to different described ranges/configurations. The approximately 0.8V-1.0V idle and 4.1V-4.3V full-signal observations are measurements/reference ranges, not a universal threshold pair. Measure the installed throttle and confirm the exact mode and firmware before programming. FarDriver’s control-parameter instructions distinguish idle/full signals from configured low/high thresholds and explain input-fault detection; their examples also vary by throttle type.
Do not use a temporary workaround described below to ride around an unresolved fault. Restore the verified configuration and complete a stable no-load sweep before load testing. The source procedure remains intact below with its stop conditions.
Throttle Voltage Reference
Typical hall throttle behavior is usually observed in these ranges:
- idle: approximately 0.8V to 1.0V
- full throttle: approximately 4.1V to 4.3V
Typical setup logic:
- Throttle Low should usually sit slightly above idle voltage
- Throttle High should usually sit slightly below true full-throttle voltage
- sudden jumps, unstable readings, or clipped range should be treated as signal or calibration issues before riding tests continue
Use these numbers as reference points only. Always confirm the actual signal on the bike you are tuning.
Throttle Miscalibration Cutout Behavior (Critical Early Failure Mode)
Throttle miscalibration is one of the most common causes of early failure during initial setup.
It often appears immediately after AutoLearn and before proper calibration is completed.
Why This Happens
If Throttle Low and Throttle High do not correctly match the actual throttle signal:
- part of the throttle range becomes invalid
- the signal can fall outside the controller’s valid input window
- the controller misinterprets input position
- internal limits or protections may be triggered
This creates unstable or inconsistent behavior under load.
Real-World Symptoms
Throttle miscalibration commonly appears as:
- bike cuts out at specific throttle positions
- power drops suddenly under load
- inconsistent or jerky acceleration
- works at low throttle but fails at higher input
- no clear or persistent fault codes
Common Misdiagnosis
This behavior is frequently mistaken for:
- battery or BMS limitations
- controller faults
- wiring issues
Key Difference vs Battery Limitation
- Throttle issue -> happens at specific throttle positions
- Battery issue -> happens under high load regardless of position
Root Cause
Incorrect configuration of:
- Throttle Low
- Throttle High
These values must match the real voltage range of the throttle.
They are not tuning parameters.
Correct Approach
- measure or observe actual throttle voltage
- set Throttle Low slightly above idle voltage
- set Throttle High slightly below max voltage
- verify smooth response across full range
Calibration Rule
If throttle behavior is inconsistent:
- fix throttle scaling first
- do not adjust current, PID, or weakening parameters
Priority
This is a Critical Early Failure Mode.
It must be resolved before:
- load testing
- current tuning
- performance evaluation
Link to Detailed Setup
-> See ONYX Jaws Mode Calibration -> Throttle Setup and Validation
Throttle Voltage and AutoLearn Errors
Throttle voltage must be within a valid range before running AutoLearn.
If the controller detects an abnormal throttle signal, AutoLearn may fail or throw a throttle-related error.
Throttle Voltage Ranges
Typical ONYX / FarDriver throttle values:
| State | Voltage Range |
|---|---|
| Low (Idle) | ~0.8V - 1.0V |
| High (Full Throttle) | ~3.6V - 4.35V |
Notes:
- some systems reach up to ~4.35V at full throttle
- this is acceptable if the signal is stable and linear
- values above this may indicate 5V rail or sensor issues
Why This Matters
During AutoLearn:
- the controller expects zero throttle input
- any voltage outside the idle range may be interpreted as throttle engagement
- this can prevent AutoLearn from starting or completing
Common Throttle Errors During AutoLearn
| Issue | Cause |
|---|---|
| AutoLearn will not start | Idle voltage too high |
| Immediate error on start | Throttle not at zero |
| Motor does not spin | Controller blocking input |
| Inconsistent behavior | Noisy or unstable signal |
Diagnosis
Check throttle signal before AutoLearn:
- confirm throttle is not being touched
- verify voltage at idle
- ensure stable reading (no fluctuation)
If using app data:
- observe live throttle percentage or voltage
- confirm it reads near 0% at rest
Correction Methods
If idle voltage is too high:
- adjust throttle baseline (if configurable in controller)
- inspect wiring:
- 5V supply (Red)
- ground (Black)
- signal (Green/White)
- check for:
- partial shorts
- pin misalignment
- damaged connectors
Temporary Workarounds
If AutoLearn must be completed:
- ensure throttle fully returns to rest position
- cycle power and retry with no input
- avoid any mechanical preload on the throttle
When to Stop
Do not continue if:
- idle voltage is unstable
- throttle reads above zero at rest
- controller repeatedly throws throttle errors
Fix the signal issue before proceeding.
Post-AutoLearn Throttle Cutout Warning
AutoLearn completing successfully does not confirm that throttle calibration is correct.
After AutoLearn, if the bike:
- cuts out when applying throttle
- hesitates or drops power under load
- behaves inconsistently with no active faults
- works at low throttle but fails at higher input
one of the most common causes is incorrect Throttle Low / Throttle High configuration.
This condition often appears on the first ride after setup and is frequently misdiagnosed as:
- wiring issues
- battery or BMS limitations
- controller faults
Do not attempt to tune around this behavior.
-> See ONYX Jaws Mode Calibration -> Throttle Miscalibration Cutout Behavior before continuing.
Parameter-Reference Throttle Clarification
Throttle Low and Throttle High are calibration values, not tuning values.
If these do not match the actual throttle voltage correctly:
- part of the throttle range can become invalid
- the controller can misread throttle position
- the bike can cut out or drop power at specific throttle positions
This is often misdiagnosed as:
- battery limitation
- controller fault
- wiring problems
If the bike works at low throttle but cuts out at higher input, verify Throttle Low / Throttle High before changing power, weakening, or PID settings.
-> See ONYX Jaws Mode Calibration -> Throttle Miscalibration Cutout Behavior
