Search Results

The scope of this document focuses on the setup and use of solid particle number (SPN) counting devices in both engine development and certification environments. The document reviews best practices for collecting and measuring samples from both raw and diluted exhaust gas streams across several sample probe insertion locations relative to installed aftertreatment devices. Appropriate dilution techniques, sample transfer processes, and temperature management techniques are included. Finally, performance and validation checks are covered to ensure that long-term degradation and instrument failures can be identified quickly. The particle size range targeted in this document is >23 nm, which aligns with the present EU SPN regulations and targets only solid particles. Current commonly available measurement devices are designed for counting efficiencies of 50% at 23 nm and 90% counting efficiencies at 40 nm so the contents of this document primarily address these particle sizes.

This SAE Information Report lists engine and laboratory tests for service fill engine oils which are associated with specifications and classifications established outside of SAE J304 and SAE J183. These specifications and classifications include those developed prior to April 1, 2017, by international technical societies, as well as individual original equipment manufacturers. The information contained within this report applies to engine oils utilized in gasoline- and diesel-powered automotive vehicles.

This SAE Information Report lists engine and laboratory tests for service fill engine oils which are associated with specifications and classifications established outside of North America. These specifications and classifications include those developed prior to January 1, 2010 by international technical societies as well as individual original equipment manufacturers. The information contained within this report applies to engine oils utilized in gasoline and diesel powered automotive vehicles.

This SAE Information Report lists engine and laboratory tests for service fill engine oils which are associated with specifications and classifications established outside of North America. These specifications and classifications include those developed prior to June 1, 2006 by International Technical Societies as well as individual original equipment manufacturers. The information contained within this report applies to engine oils utilized in gasoline and diesel powered automotive vehicles.

This document describes particulate filter weigh-room recommended practices to provide guidance in the procedures and processes associated with gravimetric filter weighing of engine or vehicle particulate matter (PM) emissions. This recommended practice provides proper procedures to build and maintain a particulate filter weigh room or enclosure to meet the requirements of EPA's 40 CFR Part 1065 and ISO 14065 for obtaining low measurement uncertainty. The content of this recommended practice addresses the following areas: a Particulate Filter Weigh Room b Microbalance Requirements c Filter Conditioning and Handling Requirements d Weighing Process e Equipment Calibration and Maintenance

This SAE Information Report provides SAE’s recommendations for meeting the requirements for REAL NOx accuracy demonstration and for the implementation of REAL NOx binning requirements as defined in OBD regulations 13 CCR 1971.1 and 13 CCR 1968.2.

This document describes a rigorous-engineering fuel-consumption test procedure that utilizes industry accepted data collection and statistical analysis methods to determine the change in fuel consumption for trucks and buses with GVWR of more than 10,000 pounds. The test procedure may be conducted on a test track or on a public road under controlled conditions and supported by extensive data collection and data analysis constraints. The on-road test procedure is offered as a lower cost alternative to on-track testing but the user is cautioned that on-road test may result in lower resolution (or precision) data due to a lack of control over the test environment. Test results that do not rigorously follow the method described herein are not intended for public use and dissemination and shall not be represented as a J1321-Type II test result.

This document describes a rigorous-engineering fuel-consumption test procedure that utilizes industry accepted data collection and statistical analysis methods to determine the change in fuel consumption for individual trucks and buses with GVWR of more than 10000 pounds. The test procedure may be conducted on a test track or on a public road under controlled conditions and supported by extensive data collection and data analysis constraints. The on-road test procedure is offered as a lower cost alternative to on-track testing, but the user is cautioned that on-road test may result in lower resolution (or precision) data due to a lack of control over the test environment. Test results that do not rigorously follow the method described herein are not intended for public use and dissemination and shall not be represented as an SAE J1321-Type II test result.

This SAE Information Report reviews the various physical and chemical properties of engine oils and provides references to test methods and standards used to measure these properties. It also includes general references on the subject of engine oils, base stocks, and additives.

This SAE Information Report reviews the various physical and chemical properties of engine oils and provides references to test methods and standards used to measure these properties. It also includes general references on the subject of engine oils, base stocks, and additives.

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/EDiagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534 2 feature “Mixed Format Frames on a CAN Network.”

The SAE J1939 communications network is developed for use in heavy-duty environments and suitable for horizontally integrated vehicle industries. The SAE J1939 communications network is applicable for light-duty, medium-duty, and heavy- duty vehicles used on-road or off-road, and for appropriate stationary applications which use vehicle derived components (e.g. generator sets). Vehicles of interest include, but are not limited to, on-highway and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. SAE J1939-71 Vehicle Application Layer is the SAE J1939 reference document for the conventions and notations that specify parameter placement in PGN data fields, the conventions for ASCII parameters, and conventions for PGN transmission rates. This document previously contained the majority of the SAE J1939 data parameters and messages for information exchange between the ECU applications connected to the SAE J1939 communications network.

SAE J1939-73 defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc. California-, EPA-, or EU-regulated OBD requirements are satisfied with a subset of the specified connector and the defined messages.

SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.

SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.