Selection Guide

Motor Controller Selection Guide

This guide helps teams choose motor controller models by voltage class, current demand, motor compatibility, and control-strategy requirements.

Best practice: lock motor map and duty-cycle envelope before selecting current tier.

Selection Workflow

Start with application boundaries, then narrow to a practical shortlist.

  1. Step 1

    Define traction and pump-drive boundary

    Lock motor type, voltage class, peak current target, and expected torque-response behavior.

  2. Step 2

    Select controller class

    Map standard 80V and 144V tiers to platform duty, then determine if custom strategy is required.

  3. Step 3

    Close calibration and interface plan

    Align CAN signals, protection logic, and pilot calibration checkpoints with BMS and telematics teams.

Key Selection Matrix

Use this matrix to screen options before requesting detailed proposal and datasheets.

Decision Factor How to Choose Quick Verification
Voltage and current envelope Use 80V tiers for common industrial drive systems and 144V tier for higher-voltage architecture. Validate peak-current demand and transient events against controller margin.
Motor compatibility Confirm PMSM or AC induction support and matching control strategy before model lock. Review motor map, target torque curve, and regenerative behavior requirements.
Duty intensity For continuous heavy load, prioritize higher current tier or custom control calibration. Run thermal and sustained-load simulation in representative duty cycle.
Software differentiation Use custom program when standard parameter range cannot satisfy platform-specific behavior goals. Compare required control features with standard firmware capability matrix.

Scenario-to-Model Mapping

Start from operating scenario and architecture targets to jump directly to a practical shortlist.

Standard traction platform

80V system with moderate-to-high current demand

Start from ZM-80V-350A and scale to 450A when torque reserve is tight.

80V tier covers broad industrial use while keeping integration straightforward.

Open ZM-80V-350A
High-voltage architecture

144V platform with stricter efficiency and response requirements

Use ZM-144V-200A as the baseline and verify thermal behavior under peak duty.

Higher-voltage control path improves fit for advanced platform layouts.

Open ZM-144V-200A
Differentiated drive strategy

Need custom control logic and AI-assisted optimization

Move to ZM-Custom track for staged hardware and software co-development.

Custom program enables platform-specific control behavior without forcing compromises.

Open ZM-Custom

Common Selection Mistakes to Avoid

These are high-frequency issues seen during integration and pilot validation.

  • Matching by nominal voltage only: Include peak current, thermal behavior, and duty-cycle stress before final model decision.
  • Ignoring motor-map alignment: Validate controller and motor map compatibility early to avoid calibration bottlenecks.
  • No regen strategy validation: Define regenerative braking boundaries and safety behavior before pilot field testing.
  • Late cross-domain signal mapping: Freeze BMS, controller, and telematics interface map at the architecture stage.

Selection FAQ

How do I decide between 350A and 450A quickly?

Start from peak torque and sustained load requirements. If operating envelope is near limit, move to 450A for practical margin.

When should I move from standard to ZM-Custom?

Move to custom when required voltage/current boundary or control behavior exceeds standard parameter range.

Can controller selection be linked with BMS and telematics planning?

Yes. CAN signal ownership, protection logic, and diagnostics pathways should be defined jointly.

What should be included in quote requests?

Provide motor type, voltage/current targets, duty profile, cooling constraints, and launch schedule.

Need a Controller Model Recommendation?

Share motor type, voltage/current targets, and duty-cycle profile. We will return a controller shortlist and pilot calibration plan.

Request Controller Recommendation