Product definition
- Bike category and target market
- Target rider, route, gradient and total load
- Wheel, frame and packaging constraints
OEM Engineering Preparation
Prepare the eBike motor system before the first integration build
Align the bike requirements, motor, battery, controller, HMI, sensors, communication interfaces, engineering files and validation gates before moving from samples to production RFQ.
1. Freeze the bike-program inputs
System selection becomes reliable only when the intended product and use conditions are documented.
Performance definition
- Voltage and torque target
- Assist behavior and riding-mode expectations
- Representative duty cycle and service environment
Program definition
- Sample quantity and evaluation stage
- Expected annual volume
- Validation schedule and launch timeline
2. Control every system interface
Record the owner, input, output and acceptance method for each interface before the sample configuration is released.
Mechanical interface
- Motor mounting or wheel/axle interface
- Clearance, chain line, cable path and connector location
- Assembly and service access
Power interface
- Battery voltage and capacity target
- Controller and charger scope
- Protection, connector and cable requirements
Communication interface
- Required protocol and message ownership
- HMI, controls and sensor interaction
- Fault, diagnostic and update expectations
Configuration interface
- Hardware revision
- Firmware version and parameter set
- Approved sample bill of materials
3. Request the files needed for the current stage
Engineering information should match the selected system, sample configuration and evaluation scope.
Product references
- Applicable datasheet
- System and component scope
- Configuration identification
Mechanical references
- CAD or STEP request
- Mounting and envelope review
- Drawing revision and change notes
Integration references
- Interface and wiring questions
- Firmware and parameter questions
- Validation responsibility matrix
Datasheet, CAD, STEP and related engineering-file availability is confirmed through the OEM discussion for the target system. Public-page content does not replace controlled engineering documentation.
4. Use a stage-gate sample validation plan
Each gate should have a controlled configuration, expected result, evidence and named owner.
Gate A: document review
Confirm the product requirements, component scope, files, interfaces, responsibilities and sample configuration before assembly.
Gate B: fit and function
Verify mechanical fit, cable routing, connectors, power-up, communication, controls, sensors and basic fault behavior.
Gate C: bench and ride evaluation
Run the agreed operating checks, assist modes, starts and stops, representative loads and routes, thermal observations, noise review and service-access checks.
Gate D: issue closure and RFQ
Close findings against the recorded configuration, align firmware and parameter baselines, freeze the component scope and prepare annual volume and launch inputs.
Continue with the correct KingClean route
Use the comparison guide, product pages and RFQ page according to the current engineering question.
Mid-Drive vs Hub-Drive OEM Guide Select the drive architecture from platform requirements.
A80 Mid-Drive System Review the A80 product route and request engineering information.
W200B Hub-Drive System Review the W200B product route and request engineering information.
OEM Sample and RFQ Process Prepare sample quantity, requested files, annual volume and launch timing.
Send the controlled integration inputs
Email echo.li@kingclean.com with the bike requirements, preferred system, mechanical constraints, battery/controller/HMI/sensor scope, protocol, requested files, sample quantity, validation scope, annual volume and launch timeline.
Email the eBike Team