What Test Data Should a DC Motor Supplier Provide With Samples?

When an OEM receives DC motor samples, a standard datasheet is useful, but it's rarely enough for proper engineering approval

A datasheet describes the product family's design intent; a sample test report should describe the actual measured performance of the specific units you receive.

A datasheet defines a motor's nominal characteristics, but it doesn't tell you how the samples in your hand actually performed, how much variation exists between them, or the exact conditions under which they were tested. For any serious OEM project, the sample data package is a critical document. It creates a measurable baseline that can be referenced throughout the product lifecycle—from internal validation and pilot runs to mass-production quality control and future failure analysis. The real question is, what data should you be getting?

Product Datasheet vs Sample Test Report vs Test Method

In many projects, I see teams treating these documents as interchangeable, but they each serve a distinct engineering purpose.

A datasheet supports selection, a sample report supports approval, and a documented test method supports reproducibility and correlation.

Understanding their roles prevents confusion and closes data gaps during the approval process.

• Product Datasheet: This document describes the target characteristics of the motor platform. It's used for initial design work and selecting a potential motor candidate.
• Sample Test Report: This report contains the measured data from the actual physical samples that were delivered. It is used for sample approval and to confirm performance.
• Test Method & Conditions¹: This explains how the values in the test report were obtained. Without it, the data is not reproducible, making it difficult to correlate tests between the supplier and your own lab.

Document	Main Question It Answers	Primary Use
Datasheet	What is the product designed to do?	Selection
Sample Report	What did these actual samples do?	Approval
Test Method	How were these values measured?	Reproduction / Correlation

A complete sample package should ideally include all three. The datasheet sets the target, the report shows the result, and the method makes the measurement reproducible.

What Per-Unit Test Data Should Be Included?

For a sample submission to be useful, it should provide data for each individual unit, not just a summary of the batch. The specific tests, however, depend on the project's requirements.

Per-unit data is essential for identifying variation, but not every sample submission requires every possible test. The data should focus on the parameters critical to your application.

A practical approach is to separate tests into baseline checks and application-specific measurements.

Typical Baseline Measurements:

These are often included to confirm basic functionality.

• No-load speed
• No-load current
• Starting voltage or startup behavior
• Rotation direction

Application-Dependent or Critical-to-Quality (CTQ) Measurements²:

These should be selected based on project risk.

• Rated/load speed and current at a defined operating point
• Winding resistance
• Insulation resistance
• Audible noise or vibration
• Shaft runout or other critical mechanical dimensions
• Encoder / Hall signal verification

For each motor, the report should clearly link the data to the physical unit, often with a simple pass/fail summary.

Sample ID	No-Load Speed (rpm)	No-Load Current (mA)	Start Voltage (V)	Result
S01	10050	115	0.45	Pass
S02	9980	121	0.48	Pass
S03	10110	118	0.46	Pass

Why Batch Statistics Matter Even for Small Sample Quantities

Even if you only have a handful of samples, looking at the range of the data provides useful insight into the variation observed within the submitted sample set.

Sample approval should consider both conformity to the specification and the variation observed within the sample set. High variation can be a warning sign.

When multiple samples are submitted, simple statistics such as minimum, maximum, and average can help describe the observed spread. Imagine a motor is specified with a no-load speed of 10,000 ±10% rpm (9,000 to 11,000 rpm).

• Batch A: 9,950, 10,020, 10,050, 10,010, 9,980 rpm. This set shows tight unit-to-unit variation around the nominal target.
• Batch B: 9,050, 9,200, 10,700, 10,850, 9,100 rpm. All units are within spec, but the wide spread is worth investigating before production approval. This level of variation may justify additional sampling or a review of the supplier's process.

System-Level Observation:
Even with a small sample set, basic statistics help describe the observed variation. However, they should not be treated as proof of long-term process capability. A meaningful capability assessment, such as Cpk, requires sufficient representative production data and evidence of process stability. Wide variation in an early sample set is a flag for further discussion.

Which Curves and Raw Data Are Worth Requesting?

You don't need a full laboratory data package for every prototype. The key is to request the data that corresponds to your application's actual risks.

Request performance curves and raw data strategically, focusing on the information needed to validate the motor's behavior at your specific operating point.

Characteristic curves provide far more insight than single-point data for many applications.

• Speed–Torque Curve: Particularly useful for understanding how speed will drop under load and ensuring you have enough torque margin.
• Current–Torque Curve: Valuable for evaluating driver sizing, power supply requirements, and current draw at different load points.
• Efficiency Curve³: Particularly useful for estimating motor power losses and supporting runtime analysis in battery-powered devices, as well as applications with strict thermal constraints.
• Temperature-Rise Data: Often recommended for continuous-duty or high-duty-cycle applications, especially in enclosed or high-ambient-temperature environments.
• Noise/Vibration Spectrum⁴: Often worth requesting for medical devices, precision instruments, and high-end consumer products where user experience is paramount.

Requesting the raw data files (e.g., CSV) can also be valuable for your own analysis and for correlating the supplier's results with your internal tests.

Test Conditions Must Be Reported With the Results

A measured value is only half the story. Without the context of the test conditions, the data is difficult to interpret and cannot be reliably reproduced or correlated.

A test result is only meaningful when another engineer can understand how it was produced. The sample report must include the conditions under which the data was collected.

A report stating "No-load current = 120 mA" is incomplete. A complete entry would look more like: "No-load current: 120 mA @ 24.0 VDC, 25°C ambient, measured 30 seconds after startup." Alternatively, the report might state that the measurement was taken after a defined warm-up period or at thermal steady state. The key is to state the condition clearly.

The same applies to noise. "Noise = 35 dBA⁵" should be accompanied by:

• Measurement distance (e.g., 10 cm)
• Background noise level
• Motor operating speed
• Mounting fixture details

Key test conditions to document:

• Supply voltage and tolerance
• Load torque
• Ambient temperature
• Driver/controller model and settings (e.g., PWM frequency)
• Motor mounting method
• Warm-up or stabilization condition
• Measurement instrument details (when precision is critical)

What OEM Buyers Should Define Before Requesting a Sample Data Package

To get a useful data package, you can't just ask the supplier to "send the test report." You need to be specific about what you need for your approval process.

To get a relevant sample report, OEMs should proactively define their acceptance criteria, turning a generic request into a clear and actionable deliverable for the supplier.

A more useful request is: "For these five samples, please provide a report with individual data for no-load speed/current at 24V and loaded performance at 50 mN·m. Reference drawing revision 1.2."

Before requesting samples, your team should define:

• The project stage and sample quantity
• The critical-to-quality (CTQ) motor parameters
• The load points that need to be tested
• Any requirements for performance curves or raw data
• The drawing and specification revision to be used
• Sample identification requirements (e.g., serial numbers)

By providing this information upfront, you help the supplier focus on what truly matters for your project. BODENMOTION can work with your team to structure a sample test plan and report that aligns with your specific engineering and quality approval criteria.

Minimum DC Motor Sample Data Package for Engineering Approval

A complete sample submission provides a traceable link between the physical motor, its measured performance, and its design documentation.

A robust sample data package must answer three questions: Did the samples meet the spec? Were the results measured under reproducible conditions? And can future production be traced back to this baseline?

The data package can be tiered based on the project stage.

Minimum Package (For early evaluation)

• Product Datasheet (current applicable revision)
• Mechanical/Electrical Drawing
• Individual test data for a few key parameters
• Basic test conditions

Engineering Approval Package (For design validation)

• All of the above, plus:
• Comprehensive individual test data for all critical parameters
• Batch summary statistics (min, max, average)
• Performance curves relevant to the application risk
• Clear revision numbers for all controlled documents
• A list of any deviations or abnormal results

Pre-Production Baseline (Before mass production)

• All of the above, plus:
• Final, signed-off specification and drawings
• Reference to a "golden sample" if applicable
• A fully documented test method
• Defined mass-production inspection criteria and sampling plan (e.g., AQL where applicable)⁶

Data Category	Recommended Content	Why It Matters
Product Specification	Current applicable datasheet and drawing revisions	Defines the design target and interface
Sample Identification	Sample ID / serial number	Links data to physical units
Individual Test Data	Actual measured values for each unit	Confirms actual sample performance
Batch Summary	Min / max / average / range	Shows observed unit-to-unit variation
Test Conditions	Voltage, load, temperature, fixture	Makes data reproducible and meaningful
Performance Curves	Speed–torque, etc., where needed	Supports operating-point analysis
Revision Information	Drawing / spec / controlled-doc revisions	Prevents version confusion
Exceptions	Any abnormal result or deviation	Prevents hidden approval risks
Traceability	Test date / lot information	Supports traceability and analysis

Conclusion

A useful DC motor sample data package should clearly separate the intended motor specification from the measured performance of the delivered units, document the conditions under which those measurements were taken, and maintain traceability between the data and the physical samples. The required depth should then scale with the project stage, application risk, and critical-to-quality parameters.

If your OEM project requires defined sample test points, CTQ verification, or a traceable approval baseline, BODENMOTION can work with your team to structure the required sample test data before production validation. Contact our engineering team at info@bodenmotion.com.

FAQ

Q1: Is a motor datasheet enough for sample approval?

Usually not. A datasheet describes the product family's expected characteristics, while sample approval requires measured data from the actual units delivered to verify their performance and consistency.

Q2: Should a supplier provide individual test results for every motor sample?

For key engineering parameters, individual results are highly recommended. They reveal unit-to-unit variation and help identify outliers that might represent an integration risk.

Q3: What test conditions should be included in a motor sample report?

At a minimum, the report should specify the supply voltage, load conditions, ambient temperature, motor mounting, and any specific driver or control settings used during the test.

Q4: Are full torque-speed curves always necessary?

Not necessarily. Curves are most valuable for applications where the operating point is critical, or where efficiency, current draw, and thermal margin are significant design risks.

Q5: What information should OEM buyers provide when requesting sample test reports?

Define the sample quantity, the critical parameters for acceptance, any required curves or raw data, the exact drawing revision to be used, and your internal approval criteria. This helps the supplier provide relevant data.

---