Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Acoustical test results for standardized SAE and ASTM test procedures, as well as non-standardized vehicle test procedures, can be presented in a number of formats and scalings, making comparison(s) of results difficult in many cases. This article examines SAE J2629-2015, a recommended practice that addresses the need for a consistent format for the presentation of various acoustical material, part, and vehicle interior noise test data.
🛠️ Engineering Insight: Standard formats reduce ambiguity and enable cross-test comparison. Consistent presentation helps avoid misinterpretation by engineers and analysts. Including metadata (test conditions, samples, facilities) is essential for reproducibility. The standard recommends specific graph types and axis scaling for different test types.
The SAE J2629-2015 standard provides a framework to ensure consistency and facilitate comparison of results across various test procedures. Whether you are testing materials in the laboratory or evaluating vehicle interior noise on the road or a chassis dynamometer, following a uniform format helps stakeholders interpret data correctly and make informed decisions.
The following table summarizes key data elements recommended by the standard for inclusion in acoustical test reports:
| Data Element | Description |
|---|---|
| Test Procedure | Identify whether the test follows SAE, ASTM, or a non-standardized procedure. |
| Test Conditions | Record temperature, humidity, and any other environmental factors. |
| Sample Description | Describe material type, dimensions, mounting method, and preconditioning. |
| Test Facility | Note the location, instrumentation, and calibration details. |
| Data Format | Specify if data is presented as A-weighted sound pressure level vs. engine speed, 1/3 octave band spectra, or other formats. |
| Graph Scaling | Use recommended axis scaling for clarity (e.g., logarithmic frequency, linear sound pressure level). |
The standard covers both vehicle-level testing (e.g., road data, chassis dynamometer) and laboratory testing of materials and components. For vehicle tests, common formats include A-weighted sound pressure level versus engine speed or versus 1/3 octave frequency. The standard also accommodates metrics like the Modified Articulation Index.
⚠️ Note: SAE J2629-2015 has been stabilized and will no longer be subjected to periodic reviews for currency. Users are responsible for verifying references and continued suitability of technical requirements. Newer technology may exist.
The standard recommends a consistent format for both standardized (SAE, ASTM) and non-standardized vehicle test procedures. Formats include A-weighted sound pressure level vs. engine speed, sound pressure level vs. 1/3 octave frequency, and Modified Articulation Index vs. engine speed. All formats must include clear labeling, scaling, and supporting metadata.
By following the format guidelines in SAE J2629-2015, data can be normalized and presented on common scales, enabling direct comparison. Including full test conditions and sample information allows analysts to account for differences in testing environment and setup.
For frequency-domain data, use a logarithmic frequency axis and a linear sound pressure level axis (in decibels). For engine speed data, use a linear RPM axis. Graphs should be uncluttered with adequate axis labels, gridlines, and legends. The standard provides example templates in its appendix.
Data should be organized by test type (vehicle, component, material) and follow the same formatting principles. For vehicle-level tests, separate graphs for road and dynamometer data are recommended. Key parameters (e.g., engine speed, microphone location) must be noted. The standard’s appendix includes spreadsheet templates to assist with consistent reporting.
🔍 Remember: The goal of the standard is to make acoustical data transparent, comparable, and actionable. Adopting these formats helps ensure that your results are understood across engineering teams and stakeholders.