Refine Your Search

Topic

Search Results

Standard

Pass-Thru Extended Features - Ethernet NDIS

2022-01-17
CURRENT
J2534-2/9_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement ethernet NDIS within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed.
Magazine

SAE Truck & Off-Highway Engineering: August 2021

2021-08-05
Accelerating truck autonomy Platform-agnostic interfaces, field data analytics and smart diagnostics will help the commercial-vehicle industry reach SAE Level 4 and 5 operations sooner. Upswing in outsourced EV testing As testing for electric commercial-vehicle propulsion systems surges, Drive System Design is rushing to expand its testing capabilities in the U.S. to keep up with the demand. Global emissions regs demand differing engine strategies The best choice in emissions-reducing technology varies for the U.S. versus Europe and elsewhere, a Jacobs expert details. Precision ag aids sustainability Deere expert Deanna Kovar, a 2021 SAE COMVEC keynoter, provides her thoughts on the future of autonomy, computer vision and machine learning, data management and more.
Standard

Vehicle OBD II Compliance Test Cases

2021-05-04
WIP
J1699/3
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.”
Standard

Vehicle OBD II Compliance Test Cases

2021-04-28
CURRENT
J1699/3_202104
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.
Standard

Serial Data Communication Interface

2021-01-27
CURRENT
J2610_202101
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.
Standard

Optional Pass-Thru Features

2020-12-14
CURRENT
J2534-2_202012
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to API version 04.04 of the SAE J2534-1 specification. It is not required for an interface to be fully compliant with API version 04.04 of the SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the vehicle OEMs and scan tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Standard

Keyword Protocol 1281

2019-05-20
CURRENT
J2818_201905
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 ECUs, in which a KWP1281 proprietary diagnostic communication protocol is implemented. ...The purpose of this document is to specify the KWP1281 protocol in enough detail to support the requirements necessary to implement the communication protocol in an SAE J2534 interface device.
Standard

General Motors UART Serial Data Communications

2019-05-20
CURRENT
J2740_201905
This document should be used in conjunction with SAE J2534-2 in order to enhance an SAE J2534 interface to also provide the capability to program ECUs with GM UART. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECUs) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. ...The purpose of this document is to specify the requirements necessary to implement GM UART in an enhanced SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
Standard

TP2.0 Vehicle Diagnostic Protocol

2019-05-20
CURRENT
J2819_201905
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 TP2.0 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.
Standard

Optional Pass-Thru Features

2019-01-16
HISTORICAL
J2534/2_201901
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Standard

Honda Diagnostic Serial Data Link Protocol - ABS/VSA System

2017-10-09
CURRENT
J2809_201710
This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an enhanced SAE J2534 interface. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface. ...The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface.
Standard

Vehicle OBD II Compliance Test Cases

2017-07-21
HISTORICAL
J1699/3_201707
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
Magazine

Automotive Engineering: March 3, 2016

2016-03-03
Multi-material structures move mpg upward The quest to improve fuel economy is not waning, nor is the desire to achieve higher mpg through the use of just the right lightweight material for the right vehicle application. Cars poised to become 'a thing' Making automobiles part of the Internet of Things brings both risks and rewards. Agility training for cars Chassis component suppliers refine vehicle dynamics at the high end and entry level with four-wheel steering and adaptive damping. SAE 2016 World Congress Preview Technology trends and exhibitor products are highlighted in this special section, which features Toyota's plans for the show floor, tech sessions, and more.
Magazine

MOBILITY ENGINEERING: March 2016

2016-03-01
Autonomous vehicles: impact on society Self-driving technology offers plenty of promise, but not everything about autonomous vehicles will be a panacea. Crankshaft reliability by integrated design, simulation, and testing This testing method is proven and beneficial for the design and development of the crankshaft and could be applied to other critical engine components, thereby extending to system reliability. New Engines 2016 Highlighting the design, engineering, and technologies inside some of the most competitive gasoline and light-duty diesel ICEs. Touch and go Avionics developments are changing life in the cockpit and at airborne work stations. Improving heavy-duty engine component efficiencies Cylinder deactivation can improve fuel economy by using a reduced number of cylinders that operate at higher loads and thermal efficiency, while other cylinders are turned off, when the engine operates at partial load conditions.
Article

OTA reflashing: the challenges and solutions

2016-01-21
Demand for a faster, secure approach to reprogramming on-board control modules, particularly for safety issues, is more urgent than ever. Over-the-air technologies bring a new set of issues, says an expert at Wind River.
X