72V ONYX Kelly Problems (Diagnosis and Fixes)

This page is part of the ONYX Performance Guide

This post defines how to diagnose and troubleshoot the Kelly KLS7230S controller on the 72V ONYX.

It combines controller behavior, calibration, fault detection, and real-world failure patterns into a usable diagnostic system.

• verify hardware before adjusting parameters
• diagnose behavior before tuning
• fix root causes before changing settings

Controller Diagnostics

Safe Diagnostic Setup

Before performing any calibration or testing:

• lift the rear wheel at least 6 inches off the ground
• remove the pedal chain to prevent drivetrain movement
• ensure the bike is stable and cannot move
• keep hands and tools clear of the motor
• do not connect or disconnect components while powered
• do not run calibration with load on the wheel

During calibration:

• the motor can spin unexpectedly or reach high speed
• treat the system as live and uncontrolled

Normal controller state:

• green LED = steady ON
• red LED = OFF

If faults are present, the red LED will flash codes on startup.

Motor Calibration

Verification:

• confirm Motor Identify EN returns to 85 (required)
• if the value remains at 170, calibration did not execute

If the value does not return to 85, calibration did not complete successfully.

Calibration Behavior and Failure

During calibration:

• motor may spin or jerk unpredictably
• rapid acceleration or full-speed spin can occur
• do not apply throttle during calibration
• this is normal behavior

If calibration fails or behaves incorrectly:

• motor stutters or fails to rotate
• controller returns errors
• value does not return to 85

Check:

• hall sensor wiring
• phase wiring
• battery voltage
• throttle connection
• motor connection

Bad calibration results in:

• weak acceleration
• excessive heat
• noise or rough operation
• poor efficiency

Calibration is not optional. Incorrect identification directly affects performance.

Hall Sensor Quick Test

Signals toggle between:

0V ↔ 5V

If signals do not toggle:

• hall sensor or wiring is faulty
• controller cannot determine motor position

Controller Behavior Under Load

Most real-world performance issues should be diagnosed here before assuming a hardware failure.

The controller does not immediately shut down under stress. It reduces output first.

Current Limiting

• battery current and phase current are independently limited
• controller reduces power before cutting output

Symptoms:

• weak acceleration
• reduced top speed
• “battery feels weak”

Cause may be:

• current limits
• thermal limiting
• voltage sag protection

Voltage Protection

• low voltage → controller cuts output
• high voltage → controller limits or shuts down
• regen can push voltage too high

Real-world behavior:

• cuts out under throttle → low voltage protection
• cuts out downhill → regen over-voltage
• cuts out near full charge → high voltage condition

Thermal Limiting

• controller reduces current as temperature rises
• shutdown occurs only at higher thresholds

Symptoms:

• performance fades after hard riding
• power returns after cooling
• no fault code until extreme temperature

This is normal protection behavior.

Controller Thermal Behavior and Cooling

The controller is a sealed thermal system.

• internal components are embedded in thermal compound
• this compound transfers heat to the outer case
• the housing acts as a heat sink with cooling fins

The controller depends on:

• mounting surface contact
• airflow
• ambient temperature

Critical Cooling Reality

If the controller overheats:

• the internal system is already transferring heat correctly
• the limitation is external to the controller

Common causes:

• poor mounting contact
• restricted airflow
• enclosed mounting location
• repeated high-load riding

Do Not Open the Controller

• the controller is weather sealed
• opening it breaks the seal
• internal thermal compound is disturbed
• heat transfer performance is permanently reduced

Opening the controller introduces:

• moisture risk
• contamination
• long-term reliability issues

Internal repair is not practical. Treat the controller as a sealed unit.

Kelly Controller LED Fault Codes

Fault codes should always be interpreted with behavior, not in isolation.

Throttle Optimization and Fault Behavior

Default throttle uses limited range.

TPS Dead Low and TPS Dead High define how much of the throttle signal is ignored at the beginning and end of the twist.

• Lowering TPS Dead Low makes throttle engagement begin earlier.
• Raising TPS Dead High allows more of the upper throttle range to be used.
• Together, these settings increase usable throttle travel and reduce the compressed feel of the stock setup.

This changes throttle feel more than peak power.

On stock throttles, setting TPS Dead Low too low can make initial response too abrupt or inconsistent. If the bike feels overly sensitive right off idle, add some dead zone back.

TPS Forw MAP changes how response is distributed across the throttle sweep.

Typical behavior:

• Around 30 gives a more logarithmic feel, with stronger response earlier in the twist.
• Around 50 feels more linear and predictable.
• Around 70 gives a more exponential feel, with softer early response and more output later in the twist.

This is mainly a ride-feel adjustment, not a fix for hardware problems.

Throttle Fault Logic

The controller expects a valid throttle range.

Fault conditions:

• throttle active at startup → no output
• voltage outside expected range → fault
• inconsistent signal → intermittent cutoff

Symptoms:

• bike powers on but does not move
• throttle cuts in and out
• delayed throttle response

Domino Throttle Wiring

• 72V Domino Full Throttle

Use crimp connectors instead of solder for vibration resistance.

Regen and Over-Voltage Behavior

Regen is not always stable under all conditions.

• braking or downhill riding increases pack voltage
• near full charge, regen can trigger over-voltage protection

This condition is more likely when the battery is fully charged and descending hills with sustained braking.

Symptoms:

• bike cuts out while braking downhill
• regen suddenly stops working
• intermittent braking behavior

Regen modes may conflict with other inputs depending on configuration.

Input Conflicts and Configuration Traps

Some controller inputs share functionality.

• boost and analog regen can share the same input
• incorrect configuration disables one or the other

Other input behavior:

• switch inputs require 12V signal
• incorrect wiring leads to non-functional features

Symptoms:

• boost not working
• regen not working
• switches behaving inconsistently

Startup Protection Behavior

Controller includes protection logic at startup.

• throttle must be at zero
• brake state may affect enable
• switch states must be valid

Symptoms:

• bike powers on but does not respond
• requires releasing the throttle to restore function

This is normal protection behavior, not a fault.

Controller Failure vs System Failure

Controller failure is less common than system issues.

Most problems are:

• battery-related
• wiring-related
• sensor-related
• configuration-related

Do not assume the controller is the problem first.

When Not To Adjust Settings

Do not change parameters before verifying:

• hall sensor signals
• throttle signal
• battery condition
• wiring integrity

Tuning a faulty system creates more problems.

Intermittent Problems

Intermittent issues are usually physical.

Common causes:

• loose connections
• vibration
• heat expansion
• wiring faults

Symptoms:

• works sometimes
• cuts out randomly
• returns after restart

Power Problems vs Battery Problems

Weak performance is not always the battery.

Possible causes:

• current limiting
• thermal limiting
• voltage protection

All can feel like battery degradation.

Maintenance and Inspection

Before assuming failure:

• inspect all connectors
• check for corrosion
• verify tight connections
• ensure clean contact surfaces

When working on the system:

• disconnect battery
• allow system to discharge
• use insulated tools

Do not open the controller housing.

Final Advice

Diagnose behavior before adjusting settings.

For the 72V ONYX:

• use calibration correctly and confirm Motor Identify EN returns to 85
• interpret fault codes with real behavior
• understand thermal and voltage protection
• treat the controller as a sealed thermal system
• verify hardware before tuning

Most issues are not the controller itself.

Controller behavior should always be interpreted as a response to system conditions, not as an isolated failure.

And when they are, the correct path is replacement, not internal repair.