GUIDE · Clear Up Confusion

Motor Wash vs Motor Break-in: What's the Difference?

"Motor wash" and "motor break-in" are entirely different procedures, often confused. This article clarifies when, how, and why for each.

The fundamental difference

AspectBreak-in (Run-in)Wash
WhenBefore first use of new motorAfter accumulated carbon residue
PurposeOptimize brush-commutator contactClean internal carbon dust & old lube
ToolsBreak-in station (controlled supply)Stoddard solvent / Zippo fluid
Duration30-60 min10-15 min
AfterInstall in car directlyMust re-lubricate (WURTH HP-2040 etc.)

When to wash a motor?

  • Motor feels "gritty" when running
  • Current noticeably increased at the same voltage (more internal friction)
  • RPM dropped >5% compared to post-break-in baseline
  • Audible irregular noise or vibration
  • Factory anti-rust oil needs removal (also applies to brand new)

Standard wash procedure

  • Prepare Stoddard solvent (green bottle, ~NT$45/0.5L) or Zippo fluid
  • Submerge motor in solvent, rotate shaft gently to let solvent penetrate
  • Run briefly at low voltage (<1V) to flush out carbon dust
  • Remove and thoroughly air-dry (oil-free compressed air), ensure no residue
  • Re-apply lubricant (WURTH HP-2040 or equivalent), or the motor will feel even draggier

Important: Washing does NOT necessarily make the motor faster! If break-in was inadequate, washing only removes carbon — slow stays slow. Speed comes from break-in. Washing is maintenance.

Maintenance schedule recommendation

Based on real-world experience, lifecycle of a Hyper Dash 2 motor:

  • New unit — complete 10-stage break-in (MotorLab M1/PRO automated)
  • After 5-10 races — first wash + re-lubricate
  • Every 5 races — quick re-lubricate
  • Every 15-20 races — full wash + health fingerprint re-test
  • When metrics drop >10% — consider retirement

This schedule is precisely trackable via MotorLab PRO's history feature (stores 50 measurements), so you know exactly "how many races and how much degradation" for each motor — no more guess-based maintenance.