Recommended Practice for Pass-Thru Vehicle Programming
- Ground Vehicle Standard
- J2534/1_201510
- Revised
Scope
Rationale
-
Ensure that all compliant devices can be validated
-
Ensure that all compliant devices act the same
-
Concerns/issues from Vehicle OEMs and Device manufacturers
-
Add new functionality to meet the needs of Vehicle OEMs that are improving the reprogramming process
-
1
To ensure testability and consistency among compliant devices
-
APIs have been clarified to eliminate ambiguities
-
Error case handling has been added/extended
-
Optional Content has been eliminated
-
Prohibit pop-ups or other types of user interaction from within the DLL
-
Specify behavior when a device disconnect occurs
-
-
2
To address Vehicle OEMs and Device manufacturers concerns
-
Interleave ISO 15765 messages
-
Individual timing/control settings for each ISO 15765 logical communication channel
-
Support ISO 15765 full and half-duplex
-
-
3
To meet new OEM requirements
-
The API now supports raw CAN frames and ISO 15765 messages on the same physical link
-
A Pass-Thru Device discovery mechanism has been added
-
New device details to specifically support wireless Pass-Thru Devices
-
Provided the ability to send and receive larger messages
-
Provide a framework that is extendable with future protocols
-
Topic
Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Unnamed Dataset 1 | ||
Unnamed Dataset 2 | ||
Unnamed Dataset 3 | ||
Unnamed Dataset 4 | ||
Unnamed Dataset 5 | ||
Unnamed Dataset 6 | ||
Unnamed Dataset 7 | ||
Unnamed Dataset 8 | ||
Unnamed Dataset 9 | ||
Unnamed Dataset 10 | ||
Unnamed Dataset 11 | ||
Unnamed Dataset 12 | ||
Unnamed Dataset 13 | ||
Unnamed Dataset 14 | ||
Unnamed Dataset 15 | ||
Unnamed Dataset 16 | ||
Unnamed Dataset 17 | ||
Unnamed Dataset 18 | ||
Unnamed Dataset 19 | ||
Unnamed Dataset 20 | ||
Unnamed Dataset 21 | ||
Unnamed Dataset 22 | ||
Unnamed Dataset 23 | ||
Unnamed Dataset 24 | ||
Unnamed Dataset 25 |
Issuing Committee
Vehicle E E System Diagnostic Standards Committee
The committee shall increase customer satisfaction and lower product life cycle costs by investigating and recommending standards that will promote more effective diagnosis of vehicle electrical and electronic system problems. The resulting recommended practices will focus on model year 1992 and beyond. However, they may be useful for prior vehicle diagnosis/repair and may serve as a basis for additional recommended practices and pre-model year 1992 vehicles.Vision Statement: A standard disgnostic connector (in a standard location) will be in all vehicles. Pin assignments for a portion of the connector will also be standardized.All vehicles will implement a set of industry standard diagnostic test modes that can be executed over a standard communication data line (i.e., SAE J1850, ISO 9141-2). Industry standard test information will be associated with some of these diagnostic test modes.An OBD II scan tool will be able to utilize a minimum set of standardized diagnostic test modes and test information.A system will be in place that will allow standard electronic access of all E/E diagnostic service information. Future diagnostic legislation will be in harmony with this vision and the resulting SAE Recommended Practices.
Reference
Number | Title |
---|---|
ISO 7637-1 | This document is not part of the subscrption. |
ISO 9141-2 | This document is not part of the subscrption. |
ISO/FDIS 15765-2 | This document is not part of the subscrption. |
ISO/FDIS 15765-4 | This document is not part of the subscrption. |
ISO11898 | This document is not part of the subscrption. |
ISO14230-4 | This document is not part of the subscrption. |
ISO9141 | This document is not part of the subscrption. |
J1850_201510 | Class B Data Communications Network Interface |
J1939_201104 | Serial Control and Communications Heavy Duty Vehicle Network - Top Level Document |
J1962_201207 | Diagnostic Connector Equivalent to ISO/DIS 15031-3: December 14, 2001 |
J2610_201501 | Serial Data Communication Interface |