Refine Your Search

Topic

Search Results

Standard

Early Acquisition and Preservation of Information in a Motor Vehicle Crash

2018-07-12
CURRENT
J1674_201807
It is intended that these guidelines improve the effectiveness of data collection, which will assist subsequent analysis and reconstruction of a particular crash. This document is intended to guide early data collectors whose objectives include documenting information related to the crash.
Standard

Handbook for Robustness Validation of Automotive Electrical/Electronic Modules

2012-11-19
CURRENT
J1211_201211
This document addresses robustness of electrical/electronic modules for use in automotive applications. Where practical, methods of extrinsic reliability detection and prevention will also be addressed. This document primarily deals with electrical/electronic modules (EEMs), but can easily be adapted for use on mechatronics, sensors, actuators and switches. EEM qualification is the main scope of this document. Other procedures addressing random failures are specifically addressed in the CPI (Component Process Interaction) section 10. This document is to be used within the context of the Zero Defect concept for component manufacturing and product use. It is recommended that the robustness of semiconductor devices and other components used in the EEM be assured using SAE J1879 OCT2007, Handbook for Robustness Validation of Semiconductor Devices in Automotive Applications.
Standard

Operational Definitions of Driving Performance Measures and Statistics

2015-06-30
CURRENT
J2944_201506
This Recommended Practice, Operational Definitions of Driving Performance Measures and Statistics, provides functional definitions of and guidance for performance measures and statistics concerned with driving on roadways. As a consequence, measurements and statistics will be calculated and reported in a consistent manner in SAE and ISO standards, journal articles proceedings papers, technical reports, and presentations so that the procedures and results can be more readily compared. Only measures and statistics pertaining to driver/vehicle responses that affect the lateral and longitudinal positioning of a road vehicle are currently provided in this document. Measures and statistics covering other aspects of driving performance may be included in future editions. For eye glance-related measures and statistics, see SAE J2396 (Society of Automotive Engineers, 2007) and ISO 15007-1 (International Standards Organization, 2002).
Standard

Event Data Recorder - Output Data Definition

2018-05-24
CURRENT
J1698/1_201805
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions, to provide a minimum data element set,and to specify EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
Standard

Event Data Recorder - Output Data Definition

2013-04-29
HISTORICAL
J1698/1_201304
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions and EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
Standard

Product Development Process and Checklist for Vehicle Electronic Systems

2015-07-30
CURRENT
J1938_201507
Since it is impossible to be all inclusive and cover every aspect of the design/validation process, this document can be used as a basis for preparation of a more comprehensive and detailed plan that reflects the accumulated "lessons learned" at a particular company. The following areas are addressed in this document: 1 Contemporary perspective including common validation issues and flaws. 2 A Robustness Validation (RV) process based on SAE J1211 handbook and SAE J2628. 3 Design checklists to aid in such a RV process.
Standard

Selection of Transmission Media

2000-02-23
CURRENT
J2056/3_200002
This SAE Information Report studies the present transmission media axioms and takes a fresh look at the Class C transmission medium requirements and also the possibilities and limitations of using a twisted pair as the transmission medium. The choice of transmission medium is a large determining factor in choosing a Class C scheme.
Standard

Application Layer - Diagnostics

2019-01-31
CURRENT
J1939/73_201901
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.
Standard

Lessons Learned from Developing, Implementing, and Operating a Health Management System for Propulsion and Drive Train Systems

2011-01-03
CURRENT
AIR1871C
SAE Aerospace Information Report AIR1871 provides valuable insight into lessons learned in the development, implementation, and operation of various health monitoring systems for propulsion engines and drive train systems. This document provides an overview of the lessons learned for ground-based systems, oil debris monitoring systems, lubrication systems, and Health and Usage Monitoring Systems (HUMS) for military and commercial programs. For each case study, this document presents a brief technical description, the design requirements, accomplishments, lessons learned, and future recommendations. The lessons learned presented in this document represent a fragment of the knowledge gained through experience when developing and implementing a propulsion health management system. Previous versions of this document contain additional lessons learned during the 1980’s and 1990’s that may be of additional value to the reader.
Standard

Event Data Recorder - Output Data Definition

2017-02-24
HISTORICAL
J1698/1_201702
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions, to provide a minimum data element set, and to specify EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
Standard

Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms--Equivalent to ISO/TR 15031-2

1988-06-01
HISTORICAL
J1930_198806
This document is applicable to all light duty gasoline and diesel vehicles (LDV), light duty gasoline and diesel trucks (LDT), and heavy duty gasoline vehicles (HDGV). Specific applications of this document include service and repair manuals, training manuals, repair data bases, under-hood emission labels, and emission certification applications. Even though the use and appropriate updating of this document and its companion documents is strongly encouraged, nothing in these documents should be construed as prohibiting the introduction of a term or acronym not covered by these documents.
Standard

Active Safety System Sensors

2017-11-30
CURRENT
J3088_201711
The current document is a part of an effort of the Active Safety Systems Committee, Active Safety Systems Sensors Task Force whose objectives are to: a Identify the functionality and performance you could expect from active safety sensors b Establish a basic understanding of how sensors work c Establish a basic understanding of how sensors can be tested d Describe an exemplar set of acceptable requirements and tests associated with each technology e Describe the key requirements/functionality for the test targets f Describe the unique characteristics of the targets or tests This document will cover items (a) and (b).
Standard

Design/process Checklist for Vehicle Electronic Systems

1998-05-01
HISTORICAL
J1938_199805
The following subjects reflect the automotive environment and are based on good engineering practices and past ("lessons learned") experiences. Since it is impossible to be all inclusive and cover every aspect of quality and reliability, this document should be used as a basis for preparation of a more comprehensive and detailed checklist that reflects the accumulated "lessons learned" at a particular Company. It is not the intent of this document to give a lot of detail, only to point out the type of subjects that need to be investigated and acted upon.
Standard

Cybersecurity Guidebook for Cyber-Physical Vehicle Systems

2016-01-14
CURRENT
J3061_201601
This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc. This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems.
Standard

Application Layer - Diagnostics

2017-05-12
HISTORICAL
J1939/73_201705
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.
Standard

Application Layer - Diagnostics

2016-01-22
HISTORICAL
J1939/73_201601
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.
Standard

Application Layer - Diagnostics

2015-08-28
HISTORICAL
J1939/73_201508
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.
Standard

Application Layer - Diagnostics

2013-07-24
HISTORICAL
J1939/73_201307
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.
Standard

Application Layer--Diagnostics

2004-03-08
HISTORICAL
J1939/73_200403
The SAE J1939 series of recommended practices are intended for light- and heavy-duty vehicle uses on- or off-road as well as appropriate stationary applications which use vehicle-derived components (e.g. generator sets). Vehicles of interest include, but are not limited to: on- and off-highway trucks and their trailers, construction equipment, and agriculture equipment and implements. The purpose of these documents is to provide an open interconnect system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. J1939-73 identifies the diagnostic connector to be used for the vehicle service tool interface and defines messages to accomplish diagnostic services. California-regulated OBD II requirements are satisfied with a subset of the specified connector and the defined messages. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired.
X