Introduction
Launching an ONYX is the most demanding moment the system will experience. It is where electrical load, torque delivery, traction, and rider input all converge at once. What happens in the first few seconds determines not only performance, but also efficiency, heat generation, and consistency across runs.
This post focuses on how launch behavior actually works. Not just what to do, but why it works. The goal is to understand how to control a high-output system under load, and how to translate that control into repeatable, predictable performance.
ONYX platforms operate in a high-torque category. They can be ridden casually, but they are capable of delivering substantial power instantly. That capability makes technique critical. The difference between a clean launch and a poor one is not subtle. It shows up in speed, stability, and system stress.
Summary
- Launch is the highest load event in the system
- Acceleration from rest produces maximum current draw
- Traction, not power, is the primary limiting factor at low speed
- Smooth throttle input improves efficiency and control
- Structured runs improve consistency and performance
- Rider input directly determines how energy is converted into motion or heat
Launch Dynamics
Launch is not just about throttle. It is about managing the relationship between torque and traction.
Throttle input is not power output. It is a request that the system attempts to fulfill within traction and electrical limits.
At low speed:
- Available torque exceeds available traction
- Full throttle does not translate directly into forward motion
- Excess demand results in instability and energy loss
An object at rest requires more energy to begin moving than to continue moving. This is where the system experiences its highest electrical demand.
Key characteristics of launch:
- Peak current draw occurs at initial movement
- Motor operates in its least efficient region at low speed under high load
- Energy losses are highest during uncontrolled acceleration
- These losses occur when demanded torque exceeds available traction
- Heat is generated rapidly when demand exceeds usable output
A launch is traction-limited, not power-limited.
These constraints define how the system must be ridden during launch.
The goal is not maximum input. The goal is controlled application of available power within the limits of traction.
Launch Technique
Rolling Start vs Dead Stop
- Entering the launch at 7-10 mph before full throttle:
- Reduces initial current spike
- Moves the motor into a more efficient operating range
- Improves traction consistency
- Creates a pre-loaded system instead of a dead-start system
Throttle Application
- Initial throttle: ~¾ input
- At 5-10 mph: transition to full throttle
This approach:
- Reduces peak electrical demand
- Prevents unnecessary torque spikes
- Improves forward energy conversion
- Limits early heat buildup
Push-Off Mechanics
- Push off with the left foot during initial throttle
- Place foot on peg once stable
This acts as:
- Mechanical assistance during zero-speed load
- Reduction in initial electrical demand on the motor
- Stabilization of balance and direction
Body Position
- Lean forward before and during launch
- Maintain alignment through acceleration
This helps:
- Counter rearward weight transfer
- Maintain front-end stability
- Keep directional control consistent
Clean Launch Definition
A clean launch is:
- Straight
- Progressive
- Traction-aligned
- Thermally controlled
- Repeatable
Acceleration From a Stop
Every stop resets the system to its highest demand state.
At 0 mph:
- The system must overcome inertia
- Torque demand spikes immediately
- Electrical load peaks instantly
Two Different Starts
| Behavior | Energy Use | Heat Generation | Result |
|---|---|---|---|
| Aggressive launch | High | High | Unstable, inefficient |
| Smooth roll-on throttle | Moderate | Lower | Controlled, efficient |
What Is Happening
Aggressive input:
- Maximum current draw immediately
- Energy converted into heat instead of motion
- Reduced efficiency and stability
Controlled input:
- Gradual load increase
- Better traction utilization
- More effective energy conversion
The first few seconds of movement determine overall efficiency.
Consistency at launch requires consistency in how runs are executed.
Run Structure and Coordination
Without structure, performance cannot be measured or repeated.
Unstructured runs introduce variables. Variables reduce both performance and control.
Reduced control at launch directly reduces usable performance.
A structured approach improves consistency, safety, and repeatability.
Core Roles
Starter
- Confirms line is clear
- Provides a clear, singular launch signal
- Removes ambiguity
Spotter
- Observes surroundings before launch
- Identifies unexpected variables
- Communicates only before the run begins
Rider
- Focuses entirely on execution
- No decision-making during launch beyond control inputs
Observer / Data Tracker (Optional)
- Records results
- Tracks consistency between runs
- Monitors performance changes
Communication
- Use one clear signal for launch
- Avoid overlapping instructions
- No mid-launch communication
Environment Characteristics
- Predictable surface
- Clear line of sight
- Minimal unexpected variables
- Consistent conditions between runs
Run Flow
- Minimize idle time between runs
- Keep setup consistent
- Avoid unnecessary changes between attempts
- Maintain rhythm and repeatability
Structured runs reduce variables. Fewer variables improve performance.
Race Preparation
Thermal Management
- Begin runs with a cool system
- Elevated temperatures reduce efficiency and available output
- Allow cooldown between repeated runs
Where heat builds:
- Motor: sustained load and low-speed inefficiency
- Controller: high current spikes during launch
- Battery: high discharge under load
When heat becomes a problem:
- Repeated launches with minimal cooldown
- Aggressive riding in high-output modes
- Continuous operation without recovery time
Practical guidance:
- Space out runs to allow temperature stabilization
- Monitor for changes in response or consistency
- If throttle response feels softer or less immediate, treat it as a sign of accumulated heat
- If performance begins to drop or feel inconsistent, stop and allow the system to cool
- Avoid stacking multiple high-load runs without recovery
Heat is cumulative. Performance loss is not always immediate. Heat also reduces consistency of output, not just peak performance.
Battery State
- Start with a fully charged battery
- Higher voltage improves performance consistency
Weight Considerations
- Total system weight affects acceleration
- Reduced weight improves responsiveness and efficiency
Tire Pressure and Setup
- Set tire pressure consistently (e.g. ~33 psi)
- Ensure spokes and components are properly tensioned
Cooling Considerations
- Increased airflow improves thermal stability
- Any modifications should balance cooling with protection and reliability
Track Familiarity
- Ride the surface before running
- Identify irregularities, traction changes, and surface conditions
- Memorize the feel of the path
Predictability improves control and repeatability.
Diagnostics
Poor launches can be identified through consistent system behavior patterns.
Signs of Inefficient Launch
- Sudden jerk at initial movement
- Front-end instability or drift
- Excessive heat after short runs
- Inconsistent acceleration between attempts
- Gradual reduction in acceleration across repeated runs (under similar conditions)
What This Indicates
- Excessive initial current demand
- Poor traction management
- Inefficient energy conversion
- Thermal saturation
- Lack of repeatability
Consistent input, consistent conditions, and a stable system produce consistent results.
Common Mistakes
- Immediate full-throttle input from 0 mph
- Inconsistent throttle application
- Ignoring system temperature
- Changing conditions between runs
- Relying on random starts instead of structured execution
Regen Drop
- Engaging throttle while holding brake, then releasing:
- Creates uncontrolled torque engagement
- Disrupts timing
- Reduces launch consistency
Range and Efficiency Connection
Launch behavior directly impacts range.
- High current spikes reduce overall efficiency
- Energy lost during poor launches becomes heat
- Repeated inefficient launches compound range loss
Efficient launches:
- Reduce thermal load
- Improve energy utilization
- Extend usable range
Platform Modes and Output Behavior
Controller behavior defines how power is delivered. Delivery defines how the bike behaves under load.
These configurations represent increasing levels of output and responsiveness, and decreasing tolerance for error.
Higher output modes do not increase traction. They increase how quickly you reach the limit of traction.
As output increases, the system becomes less forgiving, not more capable.
Controller and Platform Context
- 72V platforms use a Kelly controller in their base configuration
- 80V platforms use a different controller architecture
- JAWS Mode configurations are associated with Fardriver systems
- Different controllers change how input is interpreted and delivered, not just total output
- Controller architecture determines how throttle input is translated into current and torque
80V Hyper Mode
- Increases rate of torque delivery
- Reaches traction limits faster
- Amplifies throttle sensitivity at low speed
Implications:
- Requires smoother initial throttle input
- Small input errors become more pronounced
- Thermal buildup occurs faster under aggressive launches
Hyper mode does not change traction limits. It reaches them faster.
72V Sicko Mode
- Tuned Kelly controller configuration specific to the 72V platform
- Alters response curve and torque delivery characteristics
- Reduces margin for error during launch
Implications:
- Requires disciplined throttle control
- Launch inconsistencies become more visible
- Efficiency losses occur faster with poor input
Sicko Mode compresses the margin for error.
JAWS Mode (72V and 80V)
- Associated with Fardriver-based configurations
- Applies to both 72V and 80V platforms
- Represents a different controller architecture, not just a higher output setting
Implications:
- Maximum available output
- Fastest response to throttle input
- Least forgiving configuration
- Immediate exposure of poor technique
- Highest potential for thermal buildup during repeated runs
JAWS Mode exposes every weakness in technique immediately.
Higher output modes amplify both correct and incorrect input.
Configuration Discipline
- Follow all setup instructions exactly as defined
- Do not mix partial configurations or unsupported combinations
- Do not substitute components or settings outside intended design
- Do not assume similar behavior across different battery or controller setups
The best results come from exact adherence.
Not close. Not approximate. Exact.
Small deviations produce disproportionately large changes in behavior.
This becomes more pronounced in higher output configurations.
Reference
These resources define the intended configuration, behavior, and expectations for each setup.
Stock vs Modified Perspective
It is equally valuable to ride these bikes in stock form and in modified configurations.
- Stock setups provide consistency and a clear performance baseline
- Modified setups introduce higher output and increased variability
Both are useful.
- Comparing setups builds understanding
- Observing different builds reveals how changes affect behavior
- Sharing results and experiences improves collective knowledge
Different setups change behavior, but the underlying physics does not.
Understanding how each configuration behaves is more valuable than simply increasing output.
Failure Patterns and Misconceptions
Most performance issues are not caused by lack of power. They are caused by lack of control or consistency.
Common Misconceptions
More throttle equals faster launch
- Exceeds traction limits
- Reduces stability and efficiency
Higher modes guarantee better performance
- Increase demand, not control
- Amplify poor technique
One strong run represents true performance
- Without repeatability, results are unreliable
The bike feels fine, so it is operating optimally
- Heat buildup may not be immediately noticeable
- Performance degradation can be delayed
Common Failure Patterns
- Inconsistent throttle input between runs
- Repeated launches without adequate cooldown
- Poor traction management at low speed
- Partial or incorrect configuration setups
- Ignoring environmental and surface variability
- Chasing output instead of improving control
- Expecting consistency without controlling variables
Resulting Outcomes
- Reduced acceleration efficiency
- Increased thermal load
- Inconsistent performance
- Lower overall system reliability
If results are inconsistent, the input is inconsistent.
Final Advice
- Control matters more than input
- Smooth application outperforms aggressive spikes
- Structure improves consistency
- Consistency improves results
- Power is only useful when it can be applied effectively
Throttle input is not power output. It is a request that the system attempts to fulfill within physical limits.
The system does exactly what it is asked to do. The outcome depends on how precise that request is.
Performance is repeatable control, not isolated results.
Performance is not just about how much power is available.
It is about how controlled the system is under load.