Criteria

Text:
Sector:
Display:

Results

Viewing 1 to 30 of 109
CURRENT
2015-01-15
Standard
J2610_201501
The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU.
HISTORICAL
2002-04-30
Standard
J2610_200204
The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding "pass-thru programming" of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU.
CURRENT
2008-10-02
Standard
J2190_200810
This SAE Recommended Practice describes the implementation of Enhanced Diagnostic Test Modes, which are intended to supplement the legislated Diagnostic Test Modes defined in SAE J1979. Modes are defined for access to emission related test data beyond what is included in SAE J1979, and for non-emission related data. This document describes the data byte values for diagnostic messages transmitted between diagnostic test equipment, either on-vehicle or off-vehicle, and vehicle electronic control modules. No distinction is made between test modes for emission related and non-emission related diagnostics. These messages can be used with a diagnostic serial data link such as described in SAE J1850 or ISO 9141-2. For each test mode, this document includes a functional description of the test mode, request and report message data byte content, and an example if useful for clarification.
HISTORICAL
1993-06-01
Standard
J2190_199306
This SAE Recommended Practice describes the implementation of Enhanced Diagnostic Test Modes, which are intended to supplement the legislated Diagnostic Test Modes defined in SAE J1979. Modes are defined for access to emission related test data beyond what is included in SAE J1979, and for non-emission related data. This document describes the data byte values for diagnostic messages transmitted between diagnostic test equipment, either on-vehicle or off-vehicle, and vehicle electronic control modules. No distinction is made between test modes for emission related and non-emission related diagnostics. These messages can be used with a diagnostic serial data link such as described in SAE J1850 or ISO 9141-2. For each test mode, this document includes a functional description of the test mode, request and report message data byte content, and an example if useful for clarification.
HISTORICAL
1994-06-01
Standard
J2205_199406
This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.
HISTORICAL
1995-12-01
Standard
J2205_199512
This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.
HISTORICAL
1990-11-01
Standard
J2037_199011
This SAE Information Report is an example of how J1850 might be used to implement diagnostics in a vehicle. The utilities defined for J2037 are designed to facilitate manufacturing and service diagnosis requirements. Definition of the capability includes definition of standard messages and the dialogue necessary to provide the capability. the standard messages will be distinguished by the contents of the first data byte which specifies the diagnostic operation. Note that some vehicle applications will not require the implementation of all the defined diagnostic capabilities, and consequently, these applications will not support all message modes.
CURRENT
2001-06-21
Standard
J2037_200106
The utilities defined for J2037 are designed to facilitate manufacturing and service diagnosis requirements. Definition of the capability includes definition of standard messages and the dialogue necessary to provide the capability. The standard messages will be distinguished by the contents of the first data byte which specifies the diagnostic operation. Note that some vehicle applications will not require the implementation of all the defined diagnostic capabilities, and consequently, these applications will not support all message modes.
HISTORICAL
1990-11-01
Standard
J2054_199011
This SAE Information Report describes the diagnostic data communications required for implementation of a set of diagnostic test modes for all electronic systems on the vehicle's serial data link. These test modes can be used by off-board test equipment for both service and assembly plant testing. The goal of this document is to provide standard methods to perform common functions for all electronic systems. This standard set of procedures will aid development, production, and field service of those systems.
CURRENT
2001-06-21
Standard
J2054_200106
This SAE Information Report describes the diagnostic data communications required for implementation of a set of diagnostic test modes for all electronic systems on the vehicle's serial data link. These test modes can be used by off-board test equipment for both service and assembly plant testing. The goal of this document is to provide standard methods to perform common functions for all electronic systems. This standard set of procedures will aid development, production, and field service of those systems.
CURRENT
1989-08-01
Standard
J2062_198908
CURRENT
1999-07-22
Standard
J2205_199907
This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.
CURRENT
1999-07-20
Standard
J2201_199907
SAE J1978 defines the requirements of the OBD II scan tool. SAE J2201 defines the minimum requirements of the vehicle communications interface for the SAE J1978 OBD II scan tool. This interface connects the SAE J1962 test requirement connector to the hardware/software of the SAE J1978 OBD II scan tool that will use this interface to communicate with vehicles for thr pupose of accessing required OBD II functions. Included in this SAE Recommended Practice are several definitions relating to the interface, and interafce functionality evaluation. Appendix A—Examples include several example interface circuit implementation, which are believed to meet the requirements of this document and of SAE J1978. These examples are NOT requirements of this document. They are provided to assist circuit designers in developing interface circuits. Appenidx B—Supporting Documents includes a list of supporting documents for the examples shown in Appendix A.
HISTORICAL
1993-06-01
Standard
J2201_199306
SAE J1978 defines the requirements of the OBD II scan tool. SAE J2201 defines the minimum requirements of the vehicle communications interface for the SAE J1978 OBD II scan tool. This interface connects the SAE J1962 test requirement connector to the hardware/software of the SAE J1978 OBD II scan tool that will use this interface to communicate with vehicles for thr pupose of accessing required OBD II functions. Included in this SAE Recommended Practice are several definitions relating to the interface, and interafce functionality evaluation. Appendix A—Examples include several example interface circuit implementation, which are believed to meet the requirements of this document and of SAE J1978. These examples are NOT requirements of this document. They are provided to assist circuit designers in developing interface circuits. Appenidx B—Supporting Documents includes a list of supporting documents for the examples shown in Appendix A.
2008-08-04
WIP Standard
J2534/3
The purpose of this document is to define tests necessary to verify that an SAE J2534-1 interface device meets all the requirements specified in SAE J2534-1: Recommended Practice for Pass-Thru Vehicle Programming. Recent Activity Date Type
2013-08-07
WIP Standard
J2534/4
This document will define the P1.6 Diagnostics Message Transport Protocol and its application with SAE J2534.
CURRENT
2002-07-23
Standard
J1724_200207
CURRENT
2015-01-15
Standard
J3054_201501
This Technical Information Report defines the diagnostic communication protocol TP1.6. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP1.6 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface. This Technical Information Report describes how a tester can be connected to a vehicle to perform diagnostics using the TP1.6 protocol. Details regarding ECU to ECU communication have been left out.
2016-09-07
WIP Standard
J3005-1
SAE J3005-1 is being published as a new document which replaces J3005:20140602 ( Guidance for Remote I/M programs, Portable Emission Measurement Systems (PEMS), GPS, Wireless-LAN or Bluetooth interfaces and insurance devices.) The SAE J3005-1 devices are not intended to be used for SAE J1699-3 vehicle validation testing. The document focuses on OBD mandated communication protocols defined in SAE J1979.
2016-10-13
WIP Standard
J3005-2
SAE J3005-2 describes OBD interface security guidelines for J1979 communications and best practices for telematic devices connected with the SAE J1962 OBD vehicle connector.
CURRENT
2011-06-30
Standard
J2901_201106
The intent of the specification is to present a functional set of requirements which define the user and hardware interfaces while providing sufficient capability to meet the misfire patterns for compliance demonstration and engineering development. The misfire generator behaves as a spark-defeat device which induces misfires by inhibiting normal ignition coil discharge. It does so by monitoring the vehicle’s ignition timing signals and suspends ignition coil saturation for selected cylinder firing events. The misfire generator will thereby induce engine misfire in spark ignited gasoline internal combustion engines; including rotary engines. This requirement assumes that the user has a fundamental understanding of misfire diagnostics as well as ignition controls. This requirement is not intended to be an introductory misfire guideline or interpretation of regulatory requirements.
2016-05-17
WIP Standard
J2901
The intent of the specification is to present a functional set of requirements which define the user and hardware interfaces while providing sufficient capability to meet the misfire patterns for compliance demonstration and engineering development. The misfire generator behaves as a spark-defeat device which induces misfires by inhibiting normal ignition coil discharge. It does so by monitoring the vehicle’s ignition timing signals and suspends ignition coil saturation for selected cylinder firing events. The misfire generator will thereby induce engine misfire in spark ignited gasoline internal combustion engines; including rotary engines. This requirement assumes that the user has a fundamental understanding of misfire diagnostics as well as ignition controls. This requirement is not intended to be an introductory misfire guideline or interpretation of regulatory requirements.
HISTORICAL
1991-09-16
Standard
J2186_199109
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
HISTORICAL
1996-10-01
Standard
J2186_199610
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
CURRENT
2005-06-27
Standard
J2186_200506
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
2015-04-19
WIP Standard
J1115
Historically SAE has been concerned with nomenclature as an integral part of the standards development process. Guidelines for automotive nomenclature were written in 1916, were last revised in 1941, and were included in the SAE Handbook until 1962. The present diversity of groups working on nomenclature in the various ground vehicle committees led to the organization of the Nomenclature Advisory Committee under SAE Automotive Council.
CURRENT
2008-05-13
Standard
J2450/1_200805
This supplement, which is a living document, is meant to provide both clients and translation suppliers with some suggestions for integrating SAE J2450 into their business practices. It is intended for the use of clients, trainers who wish to develop new evaluators, and those who wish to self-train.
CURRENT
2016-08-17
Standard
J2450_201608
This SAE Standard is applicable to translations of automotive service information into any target language. The metric may be applied regardless of the source language or the method of translation (i.e., human translation, computer assisted translation or machine translation). Note that the current version of the metric does not measure errors in style, making it unsuitable for evaluations of material in which style is important (e.g., owner's manuals or marketing literature). The metric can be expanded to accommodate style and other requirements of particular new media.
HISTORICAL
2005-08-22
Standard
J2450_200508
This SAE Standard is applicable to translations of automotive service information into any target language. The metric may be applied regardless of the source language or the method of translation (i.e., human translation, computer assisted translation or machine translation). Note that the current version of the metric does not measure errors in style, making it unsuitable for evaluations of material in which style is important (e.g., owner's manuals or marketing literature). The metric can be expanded to accommodate style and other requirements of particular new media.
Viewing 1 to 30 of 109