SAE J2534 Pass-Thru API

 

 

Connects to the OBDII J1962 DLC and supports the following protocols.

1 CAN2 Single Wire
2 J1850PWM+ , J1850VPW
3 CAN2+
6 CAN+ (CAN-C only), SCI A Engine, 5v-20v out
7 ISO-9141 K-line, SCI A Engine, SCI A Trans, SCI B Engine
9 SCI B Trans, 5v-20v out or short-to-ground
10 J1850PWM-
11 CAN2- 5v-20v out
12 SCI B Engine 5v-20v out or short-to-ground
14 CAN- (CAN-C only), SCI A Trans 5v-20v out
15 ISO L Line, SCI B Trans, Short-to-ground

 

The PassThru device manufacturer supplies the hardware appliance and cable that connects to and communicates with the vehicle network.

The physical interface to the vehicle network is the SAE J1962 connector, which supports the various vehicle serial data protocols.

The following network layer protocols are supported:

ISO 9141
ISO 14230-4(KWP2000, Keyword Protocol)
SAE J1850 41.6 KBPS PWM(Pulse Width Modulation)
SAE J1850 10.4 KBPS VPW(Variable Pulse Width)
CAN(Controller Area Network, ISO 11898)
ISO 15765-4(CAN)
SAE J2610 DaimlerChrysler SCI(Serial Communications Interface)

 

J2534-1: Recommended Practice for Pass-Thru Vehicle Programming Last published version 12/2004

J2534-2: Optional Pass-Thru Features Last published version 04/2010

J2534-3: Conformance Test Cases for an SAE J2534-1 Device No published document

 

SAE J2534-1

defines an Application Program Interface (API) that can be used by Vehicle Manufacturers for reprogramming emission related modules.
This interface also includes some capabilities that may not be required for reprogramming,
but allows the interface to be used for other purposes without placing a significant burden on the interface manufacturers.

SAE J2534-2

defines optional features that takes advantage of the J2534-1 framework.
It allows the interface (J2534) to be used for other purposes and includes features that are above and beyond emission related reprogramming needs.
Many OEM’s wanted a standard for reprogramming other modules not “Emission Related”.
Those instructions were added into -2. It also expands the scope of what a J2534 device can do. (ie: Diagnostics)

SAE J2534-3

defines a set of conformance test cases, which can be used to check an interface’s compliance with SAE J2534-1 Conformance test cases are planned for J2534-2 features
also Some preliminary work has been done on the J2534-1 conformance test cases.
No work has been initiated for the J2534-2 conformance test cases.
There is no published standard yet.

J2534 framework includes application interfaces for the following functionality:

Network Initialization
Basic Send and Receive
Periodic Transmission Capability
Message Filters
Generic IO Control
Protocol Specific IO Control
Programming Voltage Supply
Other Utility Functions

Protocols Supported by a fully compliant SAE J2534-1 Device

J1850 VPW (GM Class2, Chrysler OBD)
J1850 PWM (Ford SCP)
High Speed CAN ISO 15765-4 (Diag. On CAN)
ISO 14230 (KWP)
ISO 9141-2
Chrysler SCI

Additional Protocols Currently Supported by the SAE J2534-2 Specifications

SAE J1939
SAE J1708
Single Wire CAN
GM UART
UART Echo Byte
Ford MS-CAN
Honda Diag-H
TP 2.0
Fault Tolerant CAN

 

6.5.1 ISO 9141

The following specifications clarify and, if in conflict with ISO 9141, override any related specifications in ISO 9141: 

a. The maximum sink current to be supported by the interface is 100 mA. 
b. The range for all tests performed relative to ISO 7637-1 is –1.0 to +40.0 V. 
c. The default bus idle period before the interface shall transmit an address, shall be 300 ms. 
d. Support following baud rate with ±0.5% tolerance: 10400. 
e. Support following baud rate with ±1% tolerance: 10000. 
f. Support following baud rates with ±2% tolerance: 4800, 9600, 9615, 9800, 10870, 11905, 12500, 13158, 13889, 14706, 15625, and 19200. 
g. Support other baud rates if the interface is capable of supporting the requested value within ±2%. 
h. The baud rate shall be set by the application, not determined by the SAE J2534 interface. The interface is not required to support baud rate detection based on the synchronization byte. 
i. Support odd and even parity in addition to the default of no parity, with seven or eight data bits. Always one start bit and one stop bit.

j. Support for timer values that are less than or greater than those specified in ISO 9141 (see Figure 30 in Section 7.3.2). 
k. Support ability to disable automatic ISO 9141-2 / ISO 14230 checksum verification by the interface to allow vehicle manufacturer specific error detection. 
l. If the ISO 9141 checksum is verified by the interface, and the checksum is incorrect, the message will be discarded. 
m. Support both ISO 9141 5-baud initialization and ISO 14230 fast initialization. 
n. Interface shall not adjust timer parameters based on keyword values.

6.5.2 ISO 14230-4 (KWP