Refine Your Search

Topic

Search Results

Standard

Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide

2020-06-30
CURRENT
J1939-5_202006
This document describes the application of the SAE J1939 recommended practices for compliance with on-board diagnostic malfunction detection system requirements for marine sterndrive and inboard spark ignition engines, as mandated by the California Air Resources Board (CARB). These Otto-cycle engines are not derived from automotive diesel-cycle engines.
Standard

Heavy Duty OBD IUMPR Data Collection Tool Process

2018-09-04
CURRENT
J3162_201809
This document describes the collection of IUMPR data required by the Heavy Duty On-Board Diagnostic regulation 13 CCR 1971.1 (l)(2.3.3), using SAE J1939-defined messages incorporated in a suite of software functions.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2017-10-18
CURRENT
J1939/84_201710
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2016-01-14
HISTORICAL
J1939/84_201601
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2015-02-18
HISTORICAL
J1939/84_201502
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2012-06-11
HISTORICAL
J1939/84_201206
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic test messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, test methods, and results for verifying diagnostics communication from an off board diagnostic tool (i.e. scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles.
Standard

Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide

2012-04-13
HISTORICAL
J1939/5_201204
This document describes the application of the SAE J1939 recommended practices for compliance with on-board diagnostic malfunction detection system requirements for marine sterndrive and inboard spark ignition engines, as mandated by the California Air Resources Board (CARB). These Otto-cycle engines are not derived from automotive diesel-cycle engines.
Standard

Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide

2017-10-13
CURRENT
J1939/5_201710
This document describes the application of the SAE J1939 recommended practices for compliance with on-board diagnostic malfunction detection system requirements for marine sterndrive and inboard spark ignition engines, as mandated by the California Air Resources Board (CARB). These Otto-cycle engines are not derived from automotive diesel-cycle engines.
Standard

Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide

2008-02-21
HISTORICAL
J1939/5_200802
This document describes the application of the SAE J1939 recommended practices for compliance with on-board diagnostic malfunction detection system requirements for marine sterndrive and inboard spark ignition engines, as mandated by the California Air Resources Board (CARB). These Otto-cycle engines are not derived from automotive diesel-cycle engines.
Standard

Medium/Heavy-Duty E/E Systems Diagnosis Nomenclature

2020-08-03
CURRENT
J2403_202008
This SAE Recommended Practice is applicable to all E/E systems on MD and HD vehicles. The terms defined are largely focused on compression-ignited and spark-ignited engines. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, under-hood emission labels, and emission certification applications. This document focuses on diagnostic terms, definitions, abbreviations, and acronyms applicable to E/E systems. It also covers mechanical systems which require definition. Nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. The use and appropriate updating of this document is strongly encouraged. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
Standard

Medium/Heavy-Duty E/E Systems Diagnosis Nomenclature

2018-12-19
HISTORICAL
J2403_201812
This SAE Recommended Practice is applicable to all E/E systems on MD and HD vehicles. The terms defined are largely focused on compression-ignited and spark-ignited engines. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, under-hood emission labels, and emission certification applications. This document focuses on diagnostic terms, definitions, abbreviations, and acronyms applicable to E/E systems. It also covers mechanical systems which require definition. Nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. The use and appropriate updating of this document is strongly encouraged. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
Standard

Medium/Heavy-Duty E/E Systems Diagnosis Nomenclature

2014-02-26
HISTORICAL
J2403_201402
This SAE Recommended Practice is applicable to all E/E systems on MD and HD vehicles. The terms defined are largely focused on compression-ignited and spark-ignited engines. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, under-hood emission labels, and emission certification applications. This document focuses on diagnostic terms, definitions, abbreviations, and acronyms applicable to E/E systems. It also covers mechanical systems which require definition. Nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. The use and appropriate updating of this document is strongly encouraged. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
Standard

Application Layer—Generator Sets and Industrial

2011-05-16
HISTORICAL
J1939/75_201105
SAE J1939-75 Generator Sets and Industrial Applications defines the set of data parameters (SPNs) and messages (PGNs) for information predominantly associated with monitoring and control generators and driven equipment in electric power generation and industrial applications. Applications using the SAE J1939-75 document may need to reference SAE J1939-71 for the SAE J1939 parameters and messages for monitoring and controlling the power units, e.g. engines and turbines, that power the generators and driven industrial equipment.
Standard

Compliance—Truck and Bus

2008-08-11
HISTORICAL
J1939/82_200808
The purpose of these compliance procedures is to generate one or more test documents that outline the tests needed to assure that an ECU that is designed to operate as a node on a SAE J1939 network would do so correctly. SAE does not certify devices and these tests and their results do not constitute endorsement by SAE of any particular device. These tests are presented to allow testing of a Device to determine self-compliance by the manufacturer of a device. The manufacturer can use its record of what procedures were run successfully to show the level of compliance with SAE J1939.
Standard

Application Layer - Diagnostics

2016-01-22
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

2017-05-12
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

2019-01-31
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

Application Layer - Diagnostics

2013-07-24
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

2015-08-28
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

2020-06-09
CURRENT
J1939-73_202006
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.
X