Start with COTS
Use a catalog drive when its published electrical, mechanical, communication, environmental, and safety characteristics meet the application.
Screen whether a standard drive, integration support, custom PCBA, or joint design is the right starting route. Then review the technical and commercial details a supplier needs to confirm.
An ODM project is useful when a specific requirement cannot be met by a suitable catalog drive or a limited integration change. The choice depends on verified motor, battery, enclosure, and interface requirements—not payload class or annual volume alone.
Use a catalog drive when its published electrical, mechanical, communication, environmental, and safety characteristics meet the application.
Consider firmware, connector, cable, or configuration changes when the base drive fits but integration details do not.
Request custom development when board layout, form factor, interfaces, or design ownership need project-specific work.
These diagrams show example topologies only. Axis count, communication links, isolation, and power distribution depend on the selected motors and system safety design.
Separate units can simplify replacement, but require product-specific wiring and configuration.
Integration can be tailored to the chassis; validate thermal, electrical, service, and safety trade-offs.
| Route | Consider when | Main trade-off | Confirm with supplier |
|---|---|---|---|
| COTS | A catalog unit meets the project envelope. | Less freedom to change hardware or interfaces. | Exact configuration, stock, warranty, and product life. |
| Integration support | The base drive fits with limited firmware, connector, cable, or parameter changes. | Modified configurations may need regression testing and support agreements. | Change scope, ownership, validation, price, and schedule. |
| Custom ODM | Board layout, power stage, or form factor needs custom engineering. | More control brings design, validation, and lifecycle responsibilities. | NRE, MOQ, unit pricing, test plan, deliverables, and lead time. |
| Joint design (JDM) | Both parties need to shape the requirements or product architecture. | Requires clear decision rights and contractual IP boundaries. | Background and project IP, exclusivity, support, and change control. |
NRE, MOQ, pricing, and schedule are project-specific. Public evidence is not sufficient to give a dependable universal range for these items; ask suppliers to quote against the same written requirements and validation scope.
Request a scope review using the same engineering and validation assumptions.
Record battery minimum under load, maximum at full charge, peak and continuous current, motor speed and torque, and regenerative braking behavior. Check them against the exact drive limits.
Share duty cycle, ambient temperature, enclosure, mounting surface, and available airflow. Ask how losses and temperature rise will be verified in the intended assembly.
Describe the vehicle route, mounting points, expected shocks, and vibration exposure. Agree the fixture, axes, test profile, duration, operating state, and pass criteria.
Document motor feedback, fieldbus, safety functions, service access, drawings, firmware responsibilities, and the evidence each party must deliver.
IEC 60068-2-6 describes a sinusoidal-vibration test method for assessing specimens against specified severities. It does not provide one universal AMR pass level. Select the profile from the vehicle environment and product requirements, then review the actual test report and mounting setup.
IEC 60068-2-6:2007 official catalog descriptionSource and page scope reviewed 29 September 2026. The catalog entry describes the method and specified test severities; the project must still define its own acceptance criteria.
A nominal battery label is not the full operating range. Compare the battery and drive limits at charge, under load, and during regeneration before choosing a bus voltage.
Compact packaging can constrain heat removal. Validate the assembled drive at the application duty cycle and ambient range; do not assume that a different MOSFET or cooling method alone resolves it.
A proposal can omit fixtures, lab tests, redesign loops, or production acceptance. Request a deliverable-by- deliverable quotation and define who owns each test and corrective action.
No. Payload and application class are not sufficient for electrical sizing. Provide the motor speed and torque envelope, battery minimum and maximum voltage, peak current, and braking behavior for an engineering review.
These depend on design changes, validation, sourcing, and production scope. Ask each supplier for separate engineering, tooling, test, sample, and recurring production costs with the assumptions stated.
It is a sinusoidal-vibration test method, not a universal AMR product certificate. Request the report, test severity, fixture and mounting details, operating state, and acceptance criteria for the actual assembly.
Define background IP, project-specific deliverables, source or object-code access, modification rights, exclusivity, maintenance, and end-of-life support in the contract before development begins.
Review supplier capability and AMR drive selection criteria.
Check the published product scope for 24V systems.
Compare the catalog path for a 48V class project.
Prepare a project scope and technical RFQ before requesting quotes.
Explore the broader custom drive service scope.