Sae J1699-2
Sae J1699-2
J1699®-2 SEP2017
SURFACE VEHICLE
RECOMMENDED PRACTICE Issued 1998-01
Revised 2017-09
(R) Test Cases for OBD-II Scan Tools and I/M Test Equipment
RATIONALE
The test cases have been updated to support the most recent requirements included in SAE J1979, SAE 2284-3, and
ISO 15765-4. Also, compliance test cases previously listed in SAE J1978/ISO 15031-4, have been added.
TABLE OF CONTENTS
1. SCOPE .......................................................................................................................................................... 7
1.1 Purpose ......................................................................................................................................................... 7
2. REFERENCES .............................................................................................................................................. 7
2.1 Applicable Documents .................................................................................................................................. 7
2.1.1 SAE Publications ........................................................................................................................................... 7
2.1.2 ISO Publications ............................................................................................................................................ 7
2.2 Related Publications ..................................................................................................................................... 8
2.2.1 SAE Publications ........................................................................................................................................... 8
2.2.2 ISO Publications ............................................................................................................................................ 8
2.2.3 Other Publications ......................................................................................................................................... 8
3. DEFINITIONS ............................................................................................................................................... 8
3.1 Definition of Terms ........................................................................................................................................ 8
3.2 Acronyms ...................................................................................................................................................... 9
4. OVERVIEW ................................................................................................................................................... 9
4.1 Documentation Conventions ....................................................................................................................... 10
__________________________________________________________________________________________________________________________________________
SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely
voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.”
SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and
suggestions.
Copyright © 2017 SAE International
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying,
recording, or otherwise, without the prior written permission of SAE.
TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) SAE values your input. To provide feedback
Tel: +1 724-776-4970 (outside USA) on this Technical Report, please visit
Fax: 724-776-0790 http://standards.sae.org/J1699/2_201709
Email: [email protected]
SAE WEB ADDRESS: http://www.sae.org
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
To define test cases for the OBD-II interface on external test equipment (such as an OBD-II Scan Tool,
Inspection/Maintenance Tester, etc.) which can be used to verify compliance with the applicable standards such as
SAE J1978 and SAE J1979 for Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II).
1.1 Purpose
To provide guidance to Scan Tool Manufacturers, Vehicle OEMs, and Regulators (CARB, EPA, etc.) for qualifying the
OBD-II interface on external test equipment that is used for vehicle diagnostics and/or I/M testing.
2. REFERENCES
This specification takes precedence over all conflicts in the documents cited in this section.
The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the
latest issue of SAE publications shall apply.
Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA
and Canada) or +1 724-776-4970 (outside USA), www.sae.org.
SAE J1930 Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms. This is
equivalent to ISO/DIS 15031-2 - Communication Between Vehicle and External Equipment for Emissions-
Related Diagnostics - Part 2: Terms, definitions, abbreviations and acronyms.
SAE J1978 OBD II Scan Tool. This is equivalent to ISO/DIS 15031-4 - Communication Between Vehicle and External
Equipment for Emissions-Related Diagnostics - Part 4: External test equipment.
SAE J1979 E/E Diagnostic Test Modes. This is equivalent to ISO/DIS 15031-5 (April 30, 2002) - Communication
Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part 5: Emissions-related
diagnostic services.
SAE J2012 Diagnostic Trouble Code Definitions. This is equivalent to ISO/DIS 15031-6 (April 30, 2002) -
Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part 6:
Diagnostic trouble code definitions.
SAE J2284/3 High-Speed CAN (HSC) for Vehicle Applications at 500 KBPS
ISO 9141-2 Road vehicles - Diagnostic systems - Part 2: CARB requirements for interchange of digital information
ISO 14230-4 Road vehicles - Diagnostic systems - Part 4: KWP 2000 requirements for emission related systems
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
ISO/DIS 15031-3 Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part
3: Diagnostic connector and related electrical circuits, specification and use (equivalent to SAE J1962)
ISO/DIS 15031-4 Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics
(equivalent to SAE J1978)
ISO/DIS 15031-5 Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part
5: Emissions-related diagnostic services (equivalent to SAE J1979)
ISO/DIS 15031-6 Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part
6: Diagnostic trouble code definitions (equivalent to SAE J2012)
ISO 15765-4 Road vehicles - Diagnostics on Controller Area Network (CAN) - Part 4: Requirements for emissions-
related systems
The following publications are for information purposes only and are not a required part of this document.
Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA
and Canada) or +1 724-776-4970 (outside USA), www.sae.org.
ISO 11898 Road vehicles, Interchange of Digital information, Controller Area Network (CAN) for High Speed
Communication
CARB RegulationTitle 13, California Code Regulations, Section 1968.2, Malfunction and Diagnostic System Requirements
for 2004 and Subsequent Model-Year Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD
II). Web address: https://www.arb.ca.gov/msprog/obdprog/obdregs.htm.
3. DEFINITIONS
The definitions of terms that are related to the use of this document may be found in the publications listed under 2.1,
Applicable Documents.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
4. OVERVIEW
This document defines a set of compliance tests for OBD II Scan Tools and I/M Test Equipment. The test cases are designed
to gain confidence that communications can be established and maintained with the vehicle. These tests will evaluate of a
variety of characteristics including mechanical attributes, electrical attributes, adherence to required protocol standards,
support for required network services, and presentation of vehicle data. The requirements for these test cases are drawn
from a variety of documents, but mainly focus on OBD II communication for light and medium duty vehicles as specified in
SAE J1979 (ISO 15031-5).
Since OBD II Scan Tools and I/M Test Equipment have a variety of different requirements, the specific set of test cases
required to verify compliance will also need to vary. For example, I/M Test Equipment may have no need to make any SID
$06 requests and therefore the test cases for SID $06 would not be applicable (and would not be part of that device’s
compliance test). This document contains a super-set of test cases, from which product specific test case subsets can be
selected to verify compliance.
While this document only defines the test cases, it is expected that some level of automation will need to exist to perform
the test cases as described. It is envisioned that this would consist of a PC, some instrumentation, a SAE J2534-2 Interface,
and some custom software.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
This document details a number of test cases, which have been divided into sections for ease of testing. The test cases
that have an expected positive (or successful) result start with the phrase “Verify”. Test cases that expect a failure (or result
in something other than successful) start with the phrase “Test”. Each test case consists of one or more steps. Each step
(labeled “ACTION”) has and an associated evaluation criteria (labeled “EVALUATION:”).
The phrase “ACTION” shall be followed by the specific device to be used. “ECUSIM” indicates that the associated action
must be applied to the ECU Simulation Device. The ECU Simulation Device provides the network messages that would
typically come from a vehicle. It is envisioned that this would consist of a PC, a SAE J2534-2 Interface, and some software
to operate in the manner described in the test cases. “INST” indicates that the associated action must be applied to some
piece of Instrumentation (like the Power Supply, Scope, DVOM, etc.). The Instrumentation hardware could also be part of
the ECU Simulation Device. “DUT” indicates that the associated action must be applied to the Device Under Test.
The evaluation criteria (“EVALUATION:”) shall identify the expected results. In some instances, it is easier to identify the
criteria for passing (for example, “Pass if ...”). In these cases, any result not listed as a pass shall be considered a failure.
However, in some cases it will be easier to identify the criteria for failing (for example, “Fail if …”). In these cases, any result
not listed as a failure shall be considered a pass. A test case failure is defined as the results of an individual action that
does not meet the associated evaluation criteria. If a test case has failed, any remaining actions for that test case need not
be executed as continuing on may produce unpredictable results.
Each test case shall have an associated Test ID. This number shall be unique and shall not change. The Test ID shall be
used when referencing a test case, as section numbers in the document may change in subsequent revisions. The Test IDs
have been structured to aid in automation. The Test ID is a hexadecimal number that shall have the following format with
each letter representing a single hex digit:
$GRTFFCCC
where:
G indicates the test Group (a total of 16):
0 for Mechanical
1 for Electrical
2 for Protocol
3 for Network
4 for Presentation
R is RESERVED and must be 0
T indicates the Type of test (a total of 16):
0 for General Tests
1 for ISO 15765-4 Tests
2 for ISO 14230-4 Tests
3 for ISO 9141-2Tests
4 for SAE J1850 VPW Tests
5 for SAE J1850 PWM Tests
FF indicates the Feature to be tested (a total of 256):
When G = 0 (Mechanical)
00 for General
01 for Connector
02 for Cable
When G = 1 (Electrical)
00 for General
01 for Voltage
02 for Current
03 for Capacitance
04 for Impedance/Resistance
05 for Wave Shaping
When G = 2 (Protocol)
00 for General
01 for Bit Times
02 for Transport Protocol
03 for Initialization
10 for ETI Anomalies
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
In the body of the Test Cases, specific messages and timing parameters will be referred to by an alpha-numeric text in bold
(for example, SID$01_PID$00). These references correspond to specific messages and parameter values are listed in
various tables throughout Section 5.
All numbers are in decimal unless otherwise indicated. (Hexadecimal values shall have a leading ‘$’; for example, $7AF or
$800 are hexadecimal values.)
All references to protocol specific parameters that are specified in other documents will be in italics (for example, W0).
This section provides an overview of how the test equipment and the DUT should be setup. The ‘Setup’ section of each test
case will describe the exact state of each piece of test equipment. Please note that not every piece of test equipment will
be used in every test case. All testing shall be conducted at a temperature of 23 °C (5 °C) and between 25 and 95%
relative humidity.
The DUT shall include all equipment required to operate in the manner described in the test cases. This shall include the
mechanism used to attach to the vehicle’s SAE J1962 connector.
The following list of test equipment is suggested when executing the tests contained in this document. The suggested
equipment will also aid in test automation. Please note that not every piece of test equipment will be required for every test.
• A generic PC running a WindowsTM operating system and capable of executing WIN32 function calls
• Software that can run on the PC and interact with the SAE J2534-2 Interface in the manner described in the test cases
(e.g., simulate the network messages that would typically come from a vehicle, etc.)
• A +20 V DC (5 A) Variable Power Supply - This will provide power the ECUSIM and DUT during the tests. Additionally,
this power supply shall provide power for a variety of electrical tests.
Oscilloscope
Optional
Bus
Analyzer
Simulated
Vehicle
Network
Power Supply PC
5.4.1.1 Power On
The Power On state is immediately after power up when the device is connected, but there is no active OBD communication.
5.4.2 CAN
CAN High
GND (-)
Power Simulated
Supply Vehicle
Network
POS (+)
CAN Low PC
The following messages have been pre-defined for 11-bit CAN. For convenience, the test cases in this document will use
the text in the ‘Message Reference’ column when referring to the specific set of message bytes, detailed in the ‘Message
Bytes’ column of the table below.
The device shall initially be in the ‘Power On’ state, connected to the CAN network with the appropriate termination (as
depicted in 5.4.3.1), then configured for 11-bit CAN Identifiers at a baud rate of 500000.
Optional
Bus
Analyzer
CAN High
CAN High
GND (-)
Power Simulated
Supply Vehicle
Network
POS (+)
CAN Low PC
The following address bytes have been pre-defined for 11-bit ISO 15765-4. For convenience, the test cases in this document
will use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
Figure 5 - ECU reference and associated addresses for ISO 15765-4 (11-bit)
The following address bytes have been pre-defined for 29-bit ISO 15765-4. For convenience, the test cases in this document
will use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
Figure 6 - ECU reference and associated addresses for ISO 15765-4 (29-bit)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The following messages have been pre-defined for 11-bit ISO 15765-4. These messages represent the fully assembled
message and do not include any transport layer mechanisms that appear in the individual CAN Frames (like the PCI byte,
Flow Control messages, etc.). For convenience, the test cases in this document will use the text in the ‘Message Reference’
column when referring to the specific set of message bytes, detailed in the ‘Message Bytes’ column of the table below.
For convenience, the test cases in this document will use the text in the ‘Parameter Reference’ column when referring to
the specific value, detailed in the ‘Value’ column of the table below. Unless otherwise specified, the following timing values
shall be used:
The device shall initially be in the ‘Power On’ state, connected to the CAN network with the appropriate termination (as
depicted in 5.4.3.1), and configured for 11-bit CAN Identifiers at a baud rate of 500000. The device shall not generate any
In-Frame Acknowledgements on the CAN network, but shall interpret messages according to the ISO 15765-2 format (that
is, verify and remove the PCI byte).
The device shall initially be in the ‘Power On’ state, connected to the CAN network with the appropriate termination (as
depicted in 5.4.3.1), and configured for 11-bit CAN Identifiers at a baud rate of 250000.
The device shall initially be in the ‘Power On’ state, connected to the CAN network with the appropriate termination (as
depicted in 5.4.3.1), and configured for 11-bit CAN Identifiers at a baud rate of 500000.
The device shall initially be in the ‘Power On’ state, connected to the CAN network with the appropriate termination (as
depicted in 5.4.3.1), and configured for 29-bit CAN Identifiers at a baud rate of 500000.
The OBD network shall have determined to be ISO 15765-4 with 11-bit CAN Identifiers at a baud rate of 500000 with two
OBD II ECUs having been identified. The DUT may produce a periodic message transmission to keep the network alive. A
successful completion of 8.2.2 shall define this state.
The OBD network shall have determined to be ISO 15765-4 with 29-bit CAN Identifiers at a baud rate of 500000 with two
OBD II ECUs having been identified. The DUT may produce a periodic message transmission to keep the network alive. A
successful completion of 8.2.3 shall define this state.
The OBD network shall have determined to be ISO 15765-4 with 11-bit CAN Identifiers at a baud rate of 500000 with eight
OBD II ECUs having been identified. The DUT may produce a periodic message transmission to keep the network alive. A
successful completion of 8.2.4 shall define this state.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The OBD network shall have determined to be ISO 15765-4 with 29-bit CAN Identifiers at a baud rate of 500000 with eight
OBD II ECUs having been identified. The DUT may produce a periodic message transmission to keep the network alive. A
successful completion of 8.2.5 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 0 shall define this state.
5.4.3.14 ISO 15765-4 (11-bit, 500K, 2 ECUs) SID9 Diesel Ready State
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.2.38 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.2.39 shall define this state.
5.4.3.16 ISO 15765-4 (29-bit, 500K, 2 ECUs) SID9 Diesel Ready State
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.2.40 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 9.2.41 shall define this state.
5.4.3.18 ISO 15765-4 (11-bit, 500K, 8 ECUs) SID9 Diesel Ready State
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 0 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 0 shall define this state.
5.4.3.20 ISO 15765-4 (29-bit, 500K, 8 ECUs) SID9 Diesel Ready State
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 0 shall define this state.
K-Line
GND (-)
Power Simulated
Supply Vehicle
Network
POS (+)
L-Line
Device PC
Under
Test
The following address bytes have been pre-defined for ISO 14230-4. For convenience, the test cases in this document will
use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
The following messages have been pre-defined for ISO 14230-4. For convenience, the test cases in this document will use
the text in the ‘Message Reference’ column when referring to the specific set of message bytes, detailed in the ‘Message
Bytes’ column of the table below.
For convenience, the test cases in this document will use the text in the ‘Parameter Reference’ column when referring to
the specific value, detailed in the ‘Value’ column of the table below. Unless otherwise specified, the following timing values
shall be used:
The device shall initially be in the ‘Power On’ state with the K and L Lines connected and the appropriate pull-up applied
(as depicted in 5.4.4.1).
The OBD network shall have determined to be ISO 14230-4 at a baud rate of 10400 with two OBD II ECUs shall have been
identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion of
any Section from 8.3.2 to 8.3.9 shall define this state.
The OBD network shall have determined to be ISO 14230-4 at a baud rate of 10400 with eight OBD II ECUs having been
identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion of
8.3.10 shall define this state.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.3.17 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 0 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 9.3.19 shall define this state.
Ground
Optional
Bus
Analyzer
K-Line
K-Line
GND (-)
Power Simulated
Supply Vehicle
Network
POS (+)
L-Line
Device PC
Under
Test
The following address bytes have been pre-defined for ISO 9141-2. For convenience, the test cases in this document will
use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
The following messages have been pre-defined for ISO 9141-2. For convenience, the test cases in this document will use
the text in the ‘Message Reference’ column when referring to the specific set of message bytes, detailed in the ‘Message
Bytes’ column of the table below.
For convenience, the test cases in this document will use the text in the ‘Parameter Reference’ column when referring to
the specific value, detailed in the ‘Value’ column of the table below. Unless otherwise specified, the following timing values
shall be used:
The device shall initially be in the ‘Power On’ state with the K and L Lines connected and the appropriate pull-up applied
(as depicted in 5.4.5.1).
The OBD network shall have determined to be ISO 9141-2 at a baud rate of 10400 with two OBD II ECUs having been
identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion of
any section from 8.4.2 to 8.4.3 shall define this state.
The OBD network shall have determined to be ISO 9141-2 at a baud rate of 10400 with eight OBD II ECUs having been
identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion of
8.4.3 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.4.17 shall define this state.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 0 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 9.4.19 shall define this state.
Figure 18 outlines the typical set-up for SAE J1850 VPW testing.
Bus (+)
Optional
Bus (+) Bus
Analyzer
GND (-)
Power
Supply Simulated
Vehicle
Network
POS (+)
PC
Device
Under
Test
The following address bytes have been pre-defined for SAE J1850 VPW. For convenience, the test cases in this document
will use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
The following messages have been pre-defined for SAE J1850 VPW. For convenience, the test cases in this document will
use the text in the ‘Message Reference’ column when referring to the specific set of message bytes, detailed in the ‘Message
Bytes’ column of the table below.
For convenience, the test cases in this document will use the text in the ‘Parameter Reference’ column when referring to
the specific value, detailed in the ‘Value’ column of the table below. Unless otherwise specified, the following timing values
shall be used:
The device shall initially be in the ‘Power On’ state, connected to the SAE J1850 network with the appropriate termination
applied (as depicted in 5.4.6.1).
The OBD network shall have determined to be SAE J1850 VPW at a baud rate of 10400 with two OBD II ECUs having been
identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion of
8.5.1 shall define this state.
The OBD network shall have determined to be SAE J1850 VPW at a baud rate of 10400 with eight OBD II ECUs having
been identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion
of 8.5.2 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two simulated OBD II ECUs on the network. The DUT may produce
a periodic message transmission to keep the network alive. A successful completion of 9.5.17 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two simulated OBD II ECUs on the network. The DUT may produce
a periodic message transmission to keep the network alive. A successful completion of 0 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight simulated OBD II ECUs on the network. The DUT may
produce a periodic message transmission to keep the network alive. A successful completion of 9.5.19 shall define this
state.
Figure 22 outlines the typical set-up for SAE J1850 PWM testing.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Optional
Bus (+) Bus
Analyzer
GND (-)
Power
Supply Simulated
Vehicle
Network
POS (+)
Bus (-) PC
Device
Under Bus (-)
Test
The following address bytes have been pre-defined for SAE J1850 PWM. For convenience, the test cases in this document
will use the text in the ‘ECU Reference’ column when referring to the specific set of address bytes, detailed in the ‘Address
Bytes’ column of the table below.
The following messages have been pre-defined for SAE J1850 PWM. For convenience, the test cases in this document will
use the text in the ‘Message Reference’ column when referring to the specific set of message bytes, detailed in the ‘Message
Bytes’ column of the table below.
For convenience, the test cases in this document will use the text in the ‘Parameter Reference’ column when referring to
the specific value, detailed in the ‘Value’ column of the table below. Unless otherwise specified, the following timing values
shall be used:
The device shall initially be in the ‘Power On’ state, connected to the SAE J1850 network with the appropriate termination
applied (as depicted in 5.4.7.1).
The OBD network shall have determined to be SAE J1850 PWM at a baud rate of 41600 with two OBD II ECUs having
been identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion
of 0 shall define this state.
The OBD network shall have determined to be SAE J1850 PWM at a baud rate of 41600 with eight OBD II ECUs having
been identified. The DUT may produce a periodic message transmission to keep the network alive. A successful completion
of 8.6.2 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 9.6.17 shall define this state.
The SID $09 INFOTYPES shall be known for each of the two OBD II ECUs on the network. The DUT may produce a periodic
message transmission to keep the network alive. A successful completion of 1.1.1 shall define this state.
The SID $09 INFOTYPES shall be known for each of the eight OBD II ECUs on the network. The DUT may produce a
periodic message transmission to keep the network alive. A successful completion of 0 shall define this state.
6. MECHANICAL EVALUATION
This section details test cases that will verify the mechanical attributes of the DUT.
These are general mechanical tests, which are not specific to any OBD II network.
This section details test cases that will verify the electrical attributes of the DUT.
These are general electrical tests, which are not specific to any OBD II protocol.
Purpose: The purpose of this test is to verify that the DUT will not exceed the maximum 4.0 A current
limit over the 8.0 to 18.0 voltage range.
Rationale: This test will confirm that the DUT never draws too much power.
Set Up: Connect the DUT to the variable power supply (PS #1) as outlined in Figure 26. The positive
terminal of PS #1 shall be connected to pin 16 on the DUT’s SAE J1962 connector. The
negative terminal of PS #1 shall be connected to pins 4 and 5 on the DUT’s SAE J1962
connector. If the DUT requires an external power source (other than the SAE J1962 connector),
be sure to connect it and verify that it is providing power to the DUT.
Procedure:
ACTION- INST
Set the PS #1 to 8 V DC, then measure the voltage V1 and V2 as well as current A1, A2, and
A3.
EVALUATION
Pass if all of the following conditions are true:
8.0 V DC <= V1 <= 18.0 V DC, 8.0 V DC <= V2 <= 18.0 V DC, A1 <= 4.0 A, A2 <= 1.5 A, A3
<= 4.0 A.
ACTION- INST
Set the PS #1 to 12.5 V DC, then measure the voltage V1 and V2 as well as current A1, A2,
and A3.
EVALUATION
Pass if all of the following conditions are true:
8.0 V DC <= V1 <= 18.0 V DC, 8.0 V DC <= V2 <= 18.0 V DC, A1 <= 4.0 A, A2 <= 1.5 A, A3
<= 4.0 A.
ACTION- INST
Set the PS #1 to 18 V DC, then measure the voltage V1 and V2 as well as current A1, A2,
and A3.
EVALUATION
Pass if all of the following conditions are true:
8.0 V DC <= V1 <= 18.0 V DC, 8.0 V DC <= V2 <= 18.0 V DC, A1 <= 4.0 A, A2 <= 1.5 A, A3
<= 4.0 A.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to determine if the network has the specified termination.
Rationale: This test will confirm that there is no termination being applied by the DUT.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Connected State” as defined in 5.4.3.7.
Procedure:
ACTION- INST
Measure the resistance between pin 6 (CAN H) and pin 14 (CAN L) on the DUT’s SAE J1962
connector.
EVALUATION
Pass if the resistance measurement is 500K Ohm or greater.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to determine the capacitance applied by the DUT.
Rationale: This test will confirm that the DUT is providing the correct amount of capacitance
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Connected State” as defined in 5.4.3.7.
Procedure:
ACTION- INST
Measure the capacitance between pin 5 (Signal Ground) and pin 6 (CAN H) on the DUT’s
SAE J1962 connector.
EVALUATION
Pass if the value is less than 100pF.
ACTION- INST
Measure the capacitance between pin 5 (Signal Ground) and pin 14 (CAN L) on the DUT’s
SAE J1962 connector.
EVALUATION
Pass if the value is less than 100pF.
ACTION- INST
Measure the capacitance between pin 6 (CAN H) and pin 14 (CAN L) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the value is less than 50pF.
Purpose: The purpose of this test is to determine if the network has the specified termination.
Rationale: This test will confirm that the DUT is providing a pull-up to vehicle battery.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- INST
Measure the voltage between pin 7 (K Line) and pin 4 (chassis ground) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the voltage is greater than 90% of vehicle battery.
ACTION- INST
Measure the voltage between pin 15 (K Line) and pin 4 (chassis ground) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the voltage is greater than 90% of vehicle battery.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to determine the capacitance applied by the DUT.
Rationale: This test will confirm that the DUT is providing the correct amount of capacitance
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- INST
Measure the capacitance between pin 5 (Signal Ground) and pin 7 (K Line) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the value is less than 2nF.
ACTION- INST
Measure the capacitance between pin 5 (Signal Ground) and pin 15 (L Line) on the DUT’s
SAE J1962 connector.
EVALUATION
Pass if the value is less than 2nF.
Purpose: The purpose of this test is to determine if the network has the specified termination.
Rationale: This test will confirm that the DUT is providing a pull-up to vehicle battery.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- INST
Measure the voltage between pin 7 (K Line) and pin 4 (chassis ground) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the voltage is greater than 90% of vehicle battery.
ACTION- INST
Measure the voltage between pin 15 (K Line) and pin 4 (chassis ground) on the DUT’s SAE
J1962 connector.
EVALUATION
Pass if the voltage is greater than 90% of vehicle battery.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to determine the capacitance applied by the DUT.
Rationale: This test will confirm that the DUT is providing the correct amount of capacitance
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- INST
Measure capacitance on the DUT’s SAE J1962 connector.
EVALUATION
Pass if the value is less than 2nF
These electrical tests are specific to SAE J1850 VPW and are specified in SAE J1699-1.
These electrical tests are specific to SAE J1850 PWM and are specified in SAE J1699-1.
8. PROTOCOL EVALUATION
This section details test cases that will verify the protocol attributes (such as, correct signal timing, transport layer
implementation, etc.) of the DUT.
These are general protocol tests, which are not specific to any OBD II protocol.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to determine if the DUT is attempting to establish communications
on ISO 9141-2, ISO 14230-4, J1850 PWM, J1850 VPW, ISO 15765-4 (11-bit, 500K), and ISO
15765-4 (29-bit, 500K). Where applicable, the appropriate delays shall be checked between
attempts for protocols that use the same physical layers.
Rationale: This test will confirm that all OBD interfaces are checked once per scan and that the polling
rates do not exceed those specified ISO 15031-5.
Set Up: The DUT shall be in the “Power On” state as defined in 5.4.1.1.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan and allow the DUT to make two passes through the protocol
scan process.
EVALUATION
Pass if the following is true:
There was an attempt to do a K-Line 5-Baud Initialization (Verify that both K and L Lines at
idle [logic ‘1’] for the time specified in W5. Then both K and L Lines transmit the byte $33 at
5-bits per second ±0.5%.), ISO 14230-4 Fast Initialization (Verify that the K Line was at logic
‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning to a logic ‘1’ for the
remainder of Twup. Then verify that the message 14230_START_COMM was transmitted.) at
10.4k baud, J1850 PWM 1850PWM_SID$01_PID$00 message was transmitted at 41.6k
baud, J1850 VPW 1850VPW_SID$01_PID$00 message was transmitted at 10.4k baud, ISO
15765-4 (11-bit) 15765_11_SID$01_PID$00 message was transmitted at 500K baud, and
ISO 15765-4 (29-bit) 15765_29_SID$01_PID$00 message was transmitted at 500K baud - at
least twice for each protocol, in no specific order, without user intervention.
There was at least a 2.6 second delay (2 seconds for the address at 5 baud + W1 + W5)
between start of ISO 14230-4 Fast Initialization and the start of K-Line 5-Baud Initialization.
These protocol tests are specific to ISO 15765-4. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.
Purpose: The purpose of this test is to verify that the DUT issues the correct flow control message in
response to a previous request.
Rationale: This test will use positive responses from a single ECU.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “CAN (11-bit,
500K) Connected State” as defined in 5.4.2.4.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the CAN_11_SID$09_INF$04 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the message CAN_11_ECU1_SID$09_INF$04_FF.
EVALUATION
Pass if the transmission is successful.
ACTION- DUT
In response to the ECUSIM First Frame message, the DUT should automatically issue an ISO
15765 Flow Control frame.
EVALUATION
Pass if the following is true:
The DUT recognizes that the message transmission was aborted and automatically recovers.
Figure 28 - Test ISO 15765-4 protocol BS and STMIN are 0 (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the ISO 15765-4 network with 11-bit CAN Identifiers.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Connected State” as defined in 5.4.3.7.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 15765_11_SID$01_PID$00 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the message ISO15765_11_ECU1_SID$01_PID$00, delay P2,
then transmit the message15765_11_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as ISO 15765-4
with 2 ECUs.
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the ISO 15765-4 network with 29-bit CAN Identifiers.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT shall be in the “ISO 15765 (29-bit, 500K) Connected State” as defined in 5.4.3.8 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(29-bit, 500K) Connected State” as defined in 5.4.3.8.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 15765_29_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 15765_29_ECU1_SID$01_PID$00, delay P2, then
transmit the message 15765_29_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as ISO 15765-4
with 2 ECUs.
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the ISO 15765-4 network with 11-bit CAN Identifiers when 8 ECUs are present.
Rationale: This test will use positive responses from eight different ECUs with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Connected State” as defined in 5.4.3.7.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 15765_11_SID$01_PID$00 message was transmitted
ACTION- ECUSIM
Delay P2_MIN, then transmit the message 15765_11_ECU1_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU2_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU3_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU4_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU5_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU6_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU7_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_11_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as ISO 15765-4
with 8 ECUs.
Figure 31 - Verify ISO 15765-4 protocol initialization with 8 ECUs (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the ISO 15765-4 network with 29-bit CAN Identifiers when 8 ECUs are present.
Rationale: This test will use positive responses from eight different ECUs with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “ISO 15765 (29-bit, 500K) Connected State” as defined in 5.4.3.8 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(29-bit, 500K) Connected State” as defined in 5.4.3.8.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 15765_29_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN, then transmit the message 15765_29_ECU1_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU2_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU3_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU4_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU5_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU6_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU7_SID$01_PID$00.
Delay P2_MIN, then transmit the message 15765_29_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as ISO 15765-4
with 8 ECUs.
Figure 32 - Verify ISO 15765-4 protocol initialization with 8 ECUs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT will retry transmission for at least 25 ms, the
time needed to wake up a deactivated/sleeping module or win the arbitration, when a CAN
frame is unacknowledged.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Monitor State” as defined in 5.4.3.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the following is true:
Figure 33 - Test ISO 15765-4 protocol initialization with no acknowledgement (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT will successfully initialize even when there are
unacknowledged CAN frames.
Rationale: This test will delay (with no In-Frame Acknowledgements) before using positive responses from
two different ECUs.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Monitor State” as defined in 5.4.3.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the following is true:
Figure 34 - Verify ISO 15765-4 protocol initialization with delayed acknowledgement (11-bit, 500K)
8.2.8 Test Protocol Initialization with Error Frame Detected (11-bit, 500K)
Purpose: The purpose of this test is to verify that the DUT will detect an error during transmission of a
CAN frame and disconnect itself from the bus.
Rationale: This test will generate an error condition on the ISO 15765-4 network.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 250K) Monitor State” as defined in 5.4.3.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the following is true:
Figure 35 - Test ISO 15765-4 protocol initialization with error frame detected (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT will successfully initialize when there are 5 NRC
of $21 in a row.
Rationale: This test will use a positive response from the first ECU and a negative ‘busy’ response from a
second ECU; five times in a row.
Set Up: The DUT shall be in the “ISO 15765 (11-bit, 500K) Connected State” as defined in 5.4.3.7 with
the ISO 15765-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 15765
(11-bit, 500K) Connected State” as defined in 5.4.3.7.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 15765_11_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the ISO15765_11_ECU2_SID$01_PID$00 message, delay P2, then
transmit the ISO15765_11_ECU1_SID$01_NRC$21 message.
EVALUATION
Pass if the messages were successfully transmitted.
ACTION- DUT
The DUT re-transmits the 15765_11_SID$01_PID$00 message.
EVALUATION
Pass if the message was transmitted >= 200 ms after the previous response.
ACTION- ECUSIM
Delay P2, then transmit the 15765_11_ECU2_SID$01_PID$00 message, delay P2, then
transmit the 15765_11_ECU1_SID$01_NRC$21 message.
EVALUATION
Pass if the messages were successfully transmitted.
ACTION- DUT
The DUT re-transmits the 15765_11_SID$01_PID$00 message.
EVALUATION
Pass if the message was transmitted >= 200 ms after the previous response.
ACTION- ECUSIM
Delay P2, then transmit the 15765_11_ECU2_SID$01_PID$00 message, delay P2, then
transmit the 15765_11_ECU1_SID$01_NRC$21 message.
EVALUATION
Pass if the messages were successfully transmitted.
ACTION- DUT
The DUT re-transmits the 15765_11_SID$01_PID$00 message.
EVALUATION
Pass if the message was transmitted >= 200 ms after the previous response.
ACTION- ECUSIM
Delay P2, then transmit the 15765_11_ECU2_SID$01_PID$00 message, delay P2, then
transmit the 15765_11_ECU1_SID$01_NRC$21 message.
EVALUATION
Pass if the messages were successfully transmitted.
ACTION- DUT
The DUT re-transmits the 15765_11_SID$01_PID$00 message.
EVALUATION
Pass if the message was transmitted >= 200 ms after the previous response.
ACTION- ECUSIM
Delay P2, then transmit the 15765_11_ECU2_SID$01_PID$00 message, delay P2, then
transmit the 15765_11_ECU1_SID$01_NRC$21 message.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 36 - Test ISO 15765-4 protocol initialization with NRC=$21 (11-bit, 500K)
These protocol tests are specific to ISO 14230-4. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.13.
Purpose: The purpose of this test is to verify that the bit times on the ISO 14230-4 network when the DUT
is transmitting at 10400 baud meet the signal and communication specification set forth in
ISO 14230-1.
Figure 37 - Verify ISO 14230-4 bit times for 10400 baud communications
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$E9 $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $E9 $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $E9,
delay W3, transmit $8F.
EVALUATION
Pass if $70 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO
14230-4 with 2 ECUs.
Figure 38 - Verify ISO 14230-4 5-baud initialization with key bytes $E9 $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$6B $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $6B $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 14230-4 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $6B,
delay W3, transmit $8F.
EVALUATION
Pass if $70 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO
14230-4 with 2 ECUs.
Figure 39 - Verify ISO 14230-4 5-baud initialization with key bytes $6B $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$6D $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $6D $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the
ISO 14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 14230-4 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $6D,
delay W3, transmit $8F.
EVALUATION
Pass if $70 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as
ISO 14230-4 with 2 ECUs.
Figure 40 - Verify ISO 14230-4 5-baud initialization with key bytes $6D $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$EF $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $EF $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $EF,
delay W3, transmit $8F.
EVALUATION
Pass if $70 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO
14230-4 with 2 ECUs.
Figure 41 - Verify ISO 14230-4 fast initialization with key bytes $EF $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a fast OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$E9 $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $E9 $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the
ISO 14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 fast initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_E98F.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 2 ECUs.
Figure 42 - Verify ISO 14230-4 fast initialization with key bytes $E9 $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a fast OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$6B $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $6B $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 fast initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_6B8F.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 2 ECUs.
Figure 43 - Verify ISO 14230-4 fast initialization with key bytes $6B $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a fast OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$6D $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $6D $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 fast initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_6D8F.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 2 ECUs.
Figure 44 - Verify ISO 14230-4 fast initialization with key bytes $6D $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a fast OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$EF $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $EF $8F, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 fast initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_EF8F.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$01_PID$00, delay P2, then
transmit the message 14230_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 2 ECUs.
Figure 45 - Verify ISO 14230-4 Fast initialization with Key Bytes $EF $8F and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a fast OBD II
initialization on the ISO 14230-4 network and communicate at 10400 baud when the Key Bytes
$EF $8F are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $EF $8F, then 8
ECUs will respond positively to the SID $01 PID $00 request with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “ISO 14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO 14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 142320-4 fast initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_EF8F.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU2_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU3_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU4_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU5_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU6_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU7_SID$01_PID$00.
Delay P2, then transmit the message 14230_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 8 ECUs.
Figure 46 - Verify ISO 14230-4 fast initialization with key bytes $EF $8F and 8 ECUS
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT will accept specific non-OBD II key bytes as
as valid on the ISO 14230-4 protocol. (This anomaly is detailed in SAE J1699-4.)
Set Up: The DUT shall be in the “ISO14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 14230-4 Fast Initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_NO_KB.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU18_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 1 ECU.
Figure 47 - Test ISO 14230-4 fast initialization with no OBD II key bytes and 1 ECU
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT will accept specific non-OBD II key bytes as
valid on the ISO 14230-4 protocol. (This anomaly is detailed in SAE J1699-4.)
Set Up: The DUT shall be in the “ISO14230-4 Connected State” as defined in 5.4.4.5 with the ISO
14230-4 network connected to the ECUSIM. The ECUSIM shall be in the “ISO14230-4
Connected State” as defined in 5.4.4.5.
An oscilloscope shall be connected to the ISO 14230-4 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 14230-4 Fast Initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
The K Line was at logic ‘1’ for at least W5 before changing to logic ‘0’ for TiniL then returning
to a logic ‘1’ for the remainder of Twup.
The message 14230_START_COMM was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU1_START_COMM_0000.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 14230_SID$01_PID$00 was transmitted over the K Line with inter-byte
times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
Delay P2, then transmit the message 14230_ECU18_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as 14230-4
with 1 ECU.
Figure 48 - Test ISO 14230-4 fast initialization with non-OBD II key bytes $00 $00 and 1 ECU
These protocol tests are specific to ISO 9141-2. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.4.7.
Purpose: The purpose of this test is to verify that the bit times on the ISO 9141-2 network when the DUT
is transmitting at 10400 baud meet the signal and communication specification set forth in ISO
9141-2.
Figure 49 - Verify ISO 9141-2 bit times for 10400 baud communications
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 9141-2 network and communicate at 10400 baud when the Key Bytes
$08 $08 are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $08 $08, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO9141-2 Connected State” as defined in 5.4.5.5 with the ISO 9141-2
network connected to the ECUSIM. The ECUSIM shall be in the “ISO9141-2 Connected State”
as defined in 5.4.5.5.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $08,
delay W3, transmit $08.
EVALUATION
Pass if $F7 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 9141_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$01_PID$00, delay P2, then
transmit the message 9141_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO 9141-2
with 2 ECUs.
Figure 50 - Verify ISO 9141-2 5-baud initialization with key bytes $08 $08 and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 9141-2 network and communicate at 10400 baud when the Key Bytes
$08 $08 are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $08 $08, then 8
ECUs will respond positively to the SID $01 PID $00 request with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “ISO9141-2 Connected State” as defined in 5.4.5.5 with the ISO 9141-2
network connected to the ECUSIM. The ECUSIM shall be in the “ISO9141-2 Connected State”
as defined in 5.4.5.5.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $08,
delay W3, transmit $08.
EVALUATION
Pass if $F7 is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 9141_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
Delay P2, then transmit the message 9141_ECU1_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU2_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU3_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU4_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU5_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU6_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU7_SID$01_PID$00.
Delay P2, then transmit the message 9141_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO 9141-2
with 8 ECUs.
Figure 51 - Verify ISO 9141-2 5-baud initialization with key bytes $08 $08 and 8 ECUS
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 9141-2 network and communicate at 10400 baud when the Key Bytes
$94 $94 are returned.
Rationale: This test will use a positive response from the first ECU with the Key Bytes $94 $94, then two
ECUs will respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO9141-2 Connected State” as defined in 5.4.5.5 with the ISO 9141-2
network connected to the ECUSIM. The ECUSIM shall be in the “ISO9141-2 Connected State”
as defined in 5.4.5.5.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $94,
delay W3, transmit $94.
EVALUATION
Pass if $6B is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 9141_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$01_PID$00, delay P2, then
transmit the message 9141_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO 9141-2
with 2 ECUs.
Figure 52 - Verify ISO 9141-2 5-baud initialization with key bytes $94 $94 and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform a 5-baud OBD II
initialization on the ISO 9141-2 network and communicate at 10400 baud when the Key Bytes
$94 $94 are returned after receiving no response to the first attempt at 5-baud initialization.
Rationale: This test will have the no response to the first attempt to initialize, but the second attempt will
use a positive response from the first ECU with the Key Bytes $94 $94, then two ECUs will
respond positively to the SID $01 PID $00 request.
Set Up: The DUT shall be in the “ISO9141-2 Connected State” as defined in 5.4.5.5 with the ISO 9141-2
network connected to the ECUSIM. The ECUSIM shall be in the “ISO9141-2 Connected State”
as defined in 5.4.5.5.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
The ECUSIM shall take no action in response to the first attempt at initialization. The ECUSIM
shall wait for the second attempt at initialization.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $94,
delay W3, transmit $94.
EVALUATION
Pass if $6B is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 9141_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$01_PID$00, delay P2, then
transmit the message 9141_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission was successful and the DUT identifies the OBD II protocol as ISO 9141-2
with 2 ECUs.
Figure 53 - Verify ISO 9141-2 second attempt at 5-baud initialization with key bytes $94 $94 and 2 ECUs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that after the 5-baud initialization, the DUT will re-transmit a
request when the first response is corrupted (and there are no subsequent responses) to the
SID $01 PID $00 request.
Rationale: This test will have a successful 5-baud initialization, but the first (and only) response to SID $01
PID $00 will be corrupted.
Set Up: The DUT shall be in the “ISO9141-2 Connected State” as defined in 5.4.5.5 with the ISO 9141-2
network connected to the ECUSIM. The ECUSIM shall be in the “ISO9141-2 Connected State”
as defined in 5.4.5.5.
An oscilloscope shall be connected to the ISO 9141-2 network to measure the timing of voltage
transitions during the initialization process.
Procedure:
ACTION- DUT
The DUT starts the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $94,
delay W3, transmit $94.
EVALUATION
Pass if $6B is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
ACTION- DUT
The DUT issues the Service $01 PID $00 request.
EVALUATION
Pass if the message 9141_SID$01_PID$00 was transmitted (at 10400 baud) over the K Line
with inter-byte times of at least P4_MIN and no greater than P4_MAX.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$01_PID$00_BAD.
EVALUATION
Pass if transmission was successful.
ACTION- DUT
Without user intervention, the DUT must redo the ISO 9141-2 5-baud initialization sequence.
EVALUATION
Pass if the following events occurred in this order:
Verify that both K and L Lines at idle (logic ‘1’) for the time specified in W5.
Verify that both K and L Lines transmit the byte $33 at 5-bits per second ±0.5%.
ACTION- ECUSIM
Using 10400 baud from now on, delay W1, transmit the byte $55, delay W2, transmit $94,
delay W3, transmit $94.
EVALUATION
Pass if $6B is received in no less than W4_MIN and no greater than W4_MAX.
ACTION- ECUSIM
After the W4 delay, transmit the byte $CC.
EVALUATION
Pass if transmission is successful.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 54 - Verify ISO 9141-2 request re-transmission when SID $01 PID $00 first response is corrupted
These protocol tests are specific to SAE J1850 VPW. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.5.7.
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the SAE J1850 VPW network.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT shall be in the “SAE J1850 VPW Connected State” as defined in 5.4.6.5 with the SAE
J1850 VPW network connected to the ECUSIM. The ECUSIM shall be in the “SAE J1850 VPW
Connected State” as defined in 5.4.6.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 1850VPW_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$01_PID$00, delay P2, then
transmit the message 1850VPW_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as SAE J1850
with 2 ECUs.
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the SAE J1850 VPW network.
Rationale: This test will use positive responses from eight different ECUs with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “SAE J1850 VPW Connected State” as defined in 5.4.6.5 with the SAE
J1850 VPW network connected to the ECUSIM. The ECUSIM shall be in the “SAE J1850 VPW
Connected State” as defined in 5.4.6.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 1850VPW_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 1850VPW_ECU1_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU2_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU3_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU4_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU5_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU6_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU7_SID$01_PID$00.
Delay P2, then transmit the message 1850VPW_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as SAE J1850
with 8 ECUs.
These protocol tests are specific to SAE J1850 PWM. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.6.7.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the SAE J1850 PWM network.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT shall be in the “SAE J1850 PWM Connected State” as defined in 5.4.6.5 with the SAE
J1850 PWM network connected to the ECUSIM. The ECUSIM shall be in the “SAE J1850 PWM
Connected State” as defined in 5.4.6.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 1850PWM_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$01_PID$00, delay P2, then
transmit the message 1850PWM_ECU2_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as SAE J1850
with 2 ECUs.
Purpose: The purpose of this test is to verify that the DUT can successfully perform an OBD II initialization
on the SAE J1850 PWM network.
Rationale: This test will use positive responses from eight different ECUs with ECU3 through ECU8
indicating that no SID $01 PIDs are supported.
Set Up: The DUT shall be in the “SAE J1850 PWM Connected State” as defined in 5.4.6.5 with the SAE
J1850 PWM network connected to the ECUSIM. The ECUSIM shall be in the “SAE J1850 PWM
Connected State” as defined in 5.4.6.5.
Procedure:
ACTION- DUT
Initiate the OBD II protocol scan.
EVALUATION
Pass if the 1850PWM_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2, then transmit the message 1850PWM_ECU1_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU2_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU3_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU4_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU5_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU6_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU7_SID$01_PID$00.
Delay P2, then transmit the message 1850PWM_ECU8_SID$01_PID$00.
EVALUATION
Pass if transmission is successful and the DUT identifies the OBD II protocol as SAE J1850
with 8 ECUs.
This section details test cases that will verify the network attributes (such as, message format, responses to incorrect/invalid
messages, etc.) of the DUT.
These are general network tests, which are not specific to any OBD II protocol.
These network tests are specific to ISO 15765-4. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.
9.2.1 Verify a SID $01 PID Supported PID Requests (11-bit, 500K; 1 ECU)
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
EVALUATION
Pass if the 15765_11_SID$01_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$01_PID$00_20.
EVALUATION
Pass if transmission is successful and the DUT transmits the message
15765_11_SID$01_PID$20.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$01_PID$20.
EVALUATION
Pass if transmission is successful and the DUT transmits the message
15765_11_SID$01_PID$40.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$01_PID$40.
EVALUATION
Pass if transmission is successful and the DUT indicates that PIDs $01, $0C, and $41 are
supported for ECU #1.
Figure 59 - Verify an ISO 15765-4 SID $01 PID supported PID request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
EVALUATION
Pass if the 15765_29_SID$01_PID$00 message was transmitted
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$01_PID$00_20.
EVALUATION
Pass if transmission is successful and the DUT transmits the message
15765_29_SID$01_PID$20.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$01_PID$20.
EVALUATION
Pass if transmission is successful and the DUT transmits the message
15765_29_SID$01_PID$40.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$01_PID$40.
EVALUATION
Pass if transmission is successful and the DUT indicates that PIDs $01, $0C, and $41 are
supported for ECU #1.
Figure 60 - Verify an ISO 15765-4 SID $01 PID supported PID request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs as a group.
Rationale: This test will use positive responses from a single different ECU using a group
request/response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs as a group request.
EVALUATION
Pass if the 15765_11_SID$01_PID$00-$E0 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$01_PID$00-$E0.
EVALUATION
Pass if transmission is successful and the DUT indicates that PIDs $01, $0C, and $41 are
supported for ECU #1.
Figure 61 - Verify an ISO 15765-4 SID $01 PID supported PID request - group (11-bit, 500K)
9.2.4 Verify a SID $01 PID Supported PID Requests - Group (29-bit, 500K; 1 ECU)
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs as a group.
Rationale: This test will use positive responses from a single different ECU using a group
request/response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs as a group request.
EVALUATION
Pass if the 15765_29_SID$01_PID$00-$E0 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$01_PID$00-$E0.
EVALUATION
Pass if transmission is successful and the DUT indicates that PIDs $01, $0C, and $41 are
supported for ECU #1.
Figure 62 - Verify an ISO 15765-4 SID $01 PID supported PID request - group (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmits the message 15765_11_SID$01_PID$0C, then after the delay P2_MIN
and transmit the message 15765_11_ECU1_SID$01_PID$0C. Wait for the remaining
message transactions in this ACTION to be completed.
If the DUT transmits the message 15765_11_SID$01_PID$41, then after the delay P2_MIN
and transmit the message 15765_11_ECU1_SID$01_PID$41. Wait for the remaining
message transactions in this ACTION to be completed.
EVALUATION
Pass if the following is true:
All three messages were successfully received and the corresponding responses were
successfully transmitted.
The DUT indicates that PIDs $01, $0C, and $41 are supported for ECU #1.
PID $01 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
PID $0C for ECU #1 indicates that engine RPM is 0.
PID $41 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY.
Figure 63 - Verify an ISO 15765-4 SID $01 PID request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Procedure:
ACTION- DUT
Initiate the request for SID $01 PIDs $01, $0C, and $41 from ECU #1.
ACTION- ECUSIM
If the DUT transmits the message 15765_29_SID$01_PID$01, then after the delay P2_MIN
and transmit the message 15765_29_ECU1_SID$01_PID$01_SPARK. Wait for the
remaining message transactions in this ACTION to be completed.
If the DUT transmits the message 15765_29_SID$01_PID$0C, then after the delay P2_MIN
and transmit the message 15765_29_ECU1_SID$01_PID$0C. Wait for the remaining
message transactions in this ACTION to be completed.
If the DUT transmits the message 15765_29_SID$01_PID$41, then after the delay P2_MIN
and transmit the message 15765_29_ECU1_SID$01_PID$41.
EVALUATION
Pass if the following is true:
All three messages were successfully received and the corresponding responses were
successfully transmitted.
The DUT indicates that PIDs $01, $0C, and $41 are supported for ECU #1.
PID $01 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
PID $0C for ECU #1 indicates that engine RPM is 0.
PID $41 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY.
Figure 64 - Verify an ISO 15765-4 SID $01 PID request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request several SID $01 PIDs as
a group.
Rationale: This test will use positive responses from a single different ECU using a group
request/response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PIDs $01, $0C, and $41 from ECU #1 as a group request.
EVALUATION
Pass if the DUT transmits the message 15765_11_SID$01_PID$01-$0C-$41.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$01_PID$01-$0C-$41.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that PIDs $01, $0C, and $41 are supported for ECU #1.
PID $01 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
PID $0C for ECU #1 indicates that engine RPM is 0.
PID $41 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY.
Figure 65 - Verify an ISO 15765-4 SID $01 PID request - group (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request several SID $01 PIDs as
a group.
Rationale: This test will use positive responses from a single different ECU using a group
request/response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PIDs $01, $0C, and $41 from ECU #1 as a group request.
EVALUATION
Pass if the DUT transmits the message 15765_29_SID$01_PID$01-$0C-$41.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$01_PID$01-$0C-$41.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that PIDs $01, $0C, and $41 are supported for ECU #1.
PID $01 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
PID $0C for ECU #1 indicates that engine RPM is 0.
PID $41 for ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY.
Figure 66 - Verify an ISO 15765-4 SID $01 PID request - group (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 15765_11_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$01_PID$01_SPARK,
delay P2_MIN, then transmit the message 15765_11_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 67 - Verify an ISO 15765-4 SID $01 PID $01 request for spark ignition (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 15765_29_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$01_PID$01_SPARK,
delay P2_MIN, then transmit the message 15765_29_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 68 - Verify an ISO 15765-4 SID $01 PID $01 request for spark ignition (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 15765_11_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$01_PID$01_COMP,
delay P2_MIN, then transmit the message 15765_11_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 69 - Verify an ISO 15765-4 SID $01 PID $01 request for compression ignition (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 15765_29_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$01_PID$01_COMP,
delay P2_MIN, then transmit the message 15765_29_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 70 - Verify an ISO 15765-4 SID $01 PID $01 request for compression ignition (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 15765_11_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$01_PID$0C_KOEO,
delay P2_MIN, then transmit the message 15765_11_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 71 - Verify an ISO 15765-4 SID $01 PID $0C request (11-bit, 500K)
9.2.14 Verify a SID $01 PID $0C Request (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 15765_29_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$01_PID$0C_KOEO,
delay P2_MIN, then transmit the message 15765_29_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 72 - Verify an ISO 15765-4 SID $01 PID $0C request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 15765_11_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$02_PID$02_NoDTC,
delay P2_MIN, then transmit the message 15765_11_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 73 - Verify an ISO 15765-4 SID $02 PID freeze frame DTC request with no DTCs (11-bit, 500K)
9.2.16 Verify a SID $02 PID Freeze Frame DTC Request with No DTCs (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 15765_29_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$02_PID$02_NoDTC,
delay P2_MIN, then transmit the message 15765_29_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 74 - Verify an ISO 15765-4 SID $02 PID freeze frame DTC request with no DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 15765_11_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$02_PID$02_DTC,
delay P2_MIN, then transmit the message 15765_11_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 75 - Verify an ISO 15765-4 SID $02 PID freeze frame DTC request with DTCs (11-bit, 500K)
9.2.18 Verify a SID $02 PID Freeze Frame DTC Request with DTCs (29-bit, 500K; 2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 15765_29_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$02_PID$02_DTC,
delay P2_MIN, then transmit the message 15765_29_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 76 - Verify an ISO 15765-4 SID $02 PID freeze frame DTC request with DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 15765_11_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$03_NoDTC, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 77 - Verify an ISO 15765-4 SID $03 confirmed DTC request with no DTCs (11-bit, 500K)
9.2.20 Verify a SID $03 Confirmed DTC Request with No DTCs (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 15765_29_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$03_NoDTC, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 78 - Verify an ISO 15765-4 SID $03 confirmed DTC request with no DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 15765_11_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$03_DTC, delay
P2_MIN, then transmit the message 15765_11_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 79 - Verify an ISO 15765-4 SID $03 confirmed DTC request with DTCs (11-bit, 500K)
9.2.22 Verify a SID $03 Confirmed DTC Request with DTCs (29-bit, 500K; 2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 15765_29_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$03_DTC, delay
P2_MIN, then transmit the message 15765_29_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 80 - Verify an ISO 15765-4 SID $03 confirmed DTC request with DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_11_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$04_DONE, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 81 - Verify an ISO 15765-4 SID $04 clear codes request (11-bit, 500K)
9.2.24 Verify a SID $04 Clear Codes Request (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_29_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$04_DONE, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 82 - Verify an ISO 15765-4 SID $04 clear codes request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_11_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$04_NRC22, delay
P2_MIN, then transmit the message 15765_11_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 83 - Test an ISO 15765-4 SID $04 clear codes request with NRC=$22 (11-bit, 500K)
9.2.26 Test a SID $04 Clear Codes Request with NRC=$22 (29-bit, 500K; 2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_29_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$04_NRC22, delay
P2_MIN, then transmit the message 15765_29_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 84 - Test an ISO 15765-4 SID $04 clear codes request with NRC=$22 (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that it is busy then eventually competes.
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_11_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$04_NRC78, delay
P2_MIN, then transmit the message 15765_11_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 15765_11_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 85 - Verify an ISO 15765-4 SID $04 clear codes request with NRC=$78 (11-bit, 500K)
9.2.28 Verify a SID $04 Clear Codes Request with NRC=$78 (29-bit, 500K; 2 ECUs)
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 15765_29_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$04_NRC78, delay
P2_MIN, then transmit the message 15765_29_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 15765_29_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 86 - Verify an ISO 15765-4 SID $04 clear codes request with NRC=$78 (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 15765_11_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 87 - Verify an ISO 15765-4 SID $06 MID supported MID request (11-bit, 500K)
9.2.30 Verify a SID $06 MID Supported MID Request (29-bit, 500K; 1 ECU)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 15765_29_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 88 - Verify an ISO 15765-4 SID $06 MID supported MID request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 15765_11_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$07_NoDTC, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 89 - Verify an ISO 15765-4 SID $07 pending DTC request with no DTCs (11-bit, 500K)
9.2.32 Verify a SID $07 Pending DTC Request with No DTCs (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 15765_29_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$07_NoDTC, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 90 - Verify an ISO 15765-4 SID $07 pending DTC request with no DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 15765_11_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$07_DTC, delay
P2_MIN, then transmit the message 15765_11_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 91 - Verify an ISO 15765-4 SID $07 pending DTC request with DTCs (11-bit, 500K)
9.2.34 Verify a SID $07 Pending DTC Request with DTCs (29-bit, 500K; 2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 15765_29_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$07_DTC, delay
P2_MIN, then transmit the message 15765_29_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 92 - Verify an ISO 15765-4 SID $07 pending DTC request with DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 15765_11_SID$08_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 93 - Verify an ISO 15765-4 SID $08 TID supported TID request (11-bit, 500K)
9.2.36 Verify a SID $08 TID Supported TID Request (29-bit, 500K; 1 ECU)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 15765_29_SID$08_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 94 - Verify an ISO 15765-4 SID $08 TID supported TID request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_11_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$00, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports INF $02
(VIN), INF $04 (CALID), INF $06 (CVN), INF $08 (IPT), and INF $0A (ECU Name) while ECU
#2 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
Figure 95 - Verify an ISO 15765-4 SID $09 INF supported INF request (11-bit, 500K)
9.2.38 Verify a SID $09 INF Supported INF Request Diesel (11-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_11_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$00_DIESEL,
delay P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports INF $02
(VIN), INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT), INF $0D
(ESN), and INF $0F (EROTAN) while ECU #2 supports INF $04 (CALID), INF $06 (CVN), INF
$0A (ECU Name), INF $0B (IPT), INF $0D (ESN), and INF $0F (EROTAN).
Figure 96 - Verify an ISO 15765-4 SID $09 INF supported INF request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_29_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$00, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $08 (IPT), and INF
$0A (ECU Name)
ECU #2 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
Figure 97 - Verify an ISO 15765-4 SID $09 INF supported INF request (29-bit, 500K)
9.2.40 Verify a SID $09 INF Supported INF Request Diesel (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_29_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$00_DIESEL,
delay P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name),
INF $0B (IPT), INF $0D (ESN), and INF $0F (EROTAN)
ECU #2 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
Figure 98 - Verify an ISO 15765-4 SID $09 INF supported INF request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) Initialized State”,
which is detailed in 5.4.3.11.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_11_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU5_SID$09_INF$00, 15765_11_ECU2_SID$09_INF$00,
15765_11_ECU6_SID$09_INF$00, 15765_11_ECU3_SID$09_INF$00,
15765_11_ECU7_SID$09_INF$00, 15765_11_ECU4_SID$09_INF$00,
15765_11_ECU1_SID$09_INF$00 and 15765_11_ECU8_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $08 (IPT), and INF
$0A (ECU Name).
ECU #2 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #3 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #4 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #5 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #6 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #7 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #8 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
Figure 99 - Verify an ISO 15765-4 SID $09 INF supported INF request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) Initialized State”,
which is detailed in 5.4.3.11.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_11_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU5_SID$09_INF$00_DIESEL, 15765_11_ECU2_SID$09_INF$00_DIESEL,
15765_11_ECU6_SID$09_INF$00_DIESEL, 15765_11_ECU3_SID$09_INF$00_DIESEL,
15765_11_ECU7_SID$09_INF$00_DIESEL, 15765_11_ECU4_SID$09_INF$00_DIESEL,
15765_11_ECU1_SID$09_INF$00_DIESEL and
15765_11_ECU8_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name),
INF $0B (IPT), INF $0D (ESN), and INF $0F (EROTAN).
ECU #2 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #3 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #4 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #5 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #6 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #7 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #8 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
Figure 100 - Verify an ISO 15765-4 SID $09 INF supported INF request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) Initialized State”,
which is detailed in 5.4.3.12.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_29_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU5_SID$09_INF$00, 15765_29_ECU2_SID$09_INF$00,
15765_29_ECU6_SID$09_INF$00, 15765_29_ECU3_SID$09_INF$00,
15765_29_ECU7_SID$09_INF$00, 15765_29_ECU4_SID$09_INF$00,
15765_29_ECU1_SID$09_INF$00 and 15765_29_ECU8_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $08 (IPT), and INF
$0A (ECU Name).
ECU #2 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #3 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #4 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #5 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #6 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #7 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
ECU #8 supports INF $04 (CALID), INF $06 (CVN), and INF $0A (ECU Name).
Figure 101 - Verify an ISO 15765-4 SID $09 INF supported INF request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) Initialized State”,
which is detailed in 5.4.3.12.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 15765_29_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU5_SID$09_INF$00_DIESEL, 15765_29_ECU2_SID$09_INF$00_DIESEL,
15765_29_ECU6_SID$09_INF$00_DIESEL, 15765_29_ECU3_SID$09_INF$00_DIESEL,
15765_29_ECU7_SID$09_INF$00_DIESEL, 15765_29_ECU4_SID$09_INF$00_DIESEL,
15765_29_ECU1_SID$09_INF$00_DIESEL and
15765_29_ECU8_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $02 (VIN), INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name),
INF $0B (IPT), INF $0D (ESN), and INF $0F (EROTAN).
ECU #2 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #3 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #4 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #5 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #6 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #7 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
ECU #8 supports INF $04 (CALID), INF $06 (CVN), INF $0A (ECU Name), INF $0B (IPT),
INF $0D (ESN), and INF $0F (EROTAN).
Figure 102 - Verify an ISO 15765-4 SID $09 INF supported INF request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.13.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 15765_11_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$09_INF$02.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 103 - Verify an ISO 15765-4 SID $09 VIN request (11-bit, 500K)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.15.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 15765_29_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$09_INF$02.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 104 - Verify an ISO 15765-4 SID $09 VIN request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.13.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 15765_11_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$09_NRC78.
EVALUATION
Pass if the 15765_11_ECU1_SID$09_NRC78 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$09_INF$02.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 105 - Verify an ISO 15765-4 SID $09 VIN request with NRC=$78 (11-bit, 500K)
9.2.48 Verify a SID $09 VIN Request with NRC=$78 (29-bit, 500K; 1 ECU)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.15.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 15765_29_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$09_NRC78.
EVALUATION
Pass if the 15765_29_ECU1_SID$09_NRC78 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$09_INF$02.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 106 - Verify an ISO 15765-4 SID $09 VIN request with NRC=$78 (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.13.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 15765_11_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$04, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$04.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
Figure 107 - Verify an ISO 15765-4 SID $09 CALID request (11-bit, 500K)
9.2.50 Verify a SID $09 CALID Request (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.15.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 15765_29_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$04, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$04.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
Figure 108 - Verify an ISO 15765-4 SID $09 CALID request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs respond with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.17.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 15765_11_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU5_SID$09_INF$04_9, 15765_11_ECU2_SID$09_INF$04_9,
15765_11_ECU6_SID$09_INF$04_9, 15765_11_ECU3_SID$09_INF$04_9,
15765_11_ECU7_SID$09_INF$04_9, 15765_11_ECU4_SID$09_INF$04_9,
15765_11_ECU1_SID$09_INF$04_9, 15765_11_ECU8_SID$09_INF$04_9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CALID for ECU #1 are: “11589778”, “21589777”, “31589776”,
“41589775”, “51589774”, “61589773”, “71589772”, “81589771”, “91589770”.
The DUT indicates that the CALID for ECU #2 are: “12589778”, “22589777”, “32589776”,
“42589775”, “52589774”, “62589773”, “72589772”, “82589771”, “92589770”.
The DUT indicates that the CALID for ECU #3 are: “13589778”, “23589777”, “33589776”,
“43589775”, “53589774”, “63589773”, “73589772”, “83589771”, “93589770”.
The DUT indicates that the CALID for ECU #4 are: “14589778”, “24589777”, “34589776”,
“44589775”, “54589774”, “64589773”, “74589772”, “84589771”, “94589770”.
The DUT indicates that the CALID for ECU #5 are: “15589778”, “25589777”, “35589776”,
“45589775”, “55589774”, “65589773”, “75589772”, “85589771”, “95589770”.
The DUT indicates that the CALID for ECU #6 are: “16589778”, “26589777”, “36589776”,
“46589775”, “56589774”, “66589773”, “76589772”, “86589771”, “96589770”.
The DUT indicates that the CALID for ECU #7 are: “17589778”, “27589777”, “37589776”,
“47589775”, “57589774”, “67589773”, “77589772”, “87589771”, “97589770”.
The DUT indicates that the CALID for ECU #8 are: “18589778”, “28589777”, “38589776”,
“48589775”, “58589774”, “68589773”, “78589772”, “88589771”, “98589770”.
Figure 109 - Verify an ISO 15765-4 SID $09 CALID request with 9 CALIDs on an ECU (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs responds with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.19.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 15765_29_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU5_SID$09_INF$04_9, 15765_29_ECU2_SID$09_INF$04_9,
15765_29_ECU6_SID$09_INF$04_9, 15765_29_ECU3_SID$09_INF$04_9,
15765_29_ECU7_SID$09_INF$04_9, 15765_29_ECU4_SID$09_INF$04_9,
15765_29_ECU1_SID$09_INF$04_9, 15765_29_ECU8_SID$09_INF$04_9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CALID for ECU #1 are: “11589778”, “21589777”, “31589776”,
“41589775”, “51589774”, “61589773”, “71589772”, “81589771”, “91589770”.
The DUT indicates that the CALID for ECU #2 are: “12589778”, “22589777”, “32589776”,
“42589775”, “52589774”, “62589773”, “72589772”, “82589771”, “92589770”.
The DUT indicates that the CALID for ECU #3 are: “13589778”, “23589777”, “33589776”,
“43589775”, “53589774”, “63589773”, “73589772”, “83589771”, “93589770”.
The DUT indicates that the CALID for ECU #4 are: “14589778”, “24589777”, “34589776”,
“44589775”, “54589774”, “64589773”, “74589772”, “84589771”, “94589770”.
The DUT indicates that the CALID for ECU #5 are: “15589778”, “25589777”, “35589776”,
“45589775”, “55589774”, “65589773”, “75589772”, “85589771”, “95589770”.
The DUT indicates that the CALID for ECU #6 are: “16589778”, “26589777”, “36589776”,
“46589775”, “56589774”, “66589773”, “76589772”, “86589771”, “96589770”.
The DUT indicates that the CALID for ECU #7 are: “17589778”, “27589777”, “37589776”,
“47589775”, “57589774”, “67589773”, “77589772”, “87589771”, “97589770”.
The DUT indicates that the CALID for ECU #8 are: “18589778”, “28589777”, “38589776”,
“48589775”, “58589774”, “68589773”, “78589772”, “88589771”, “98589770”.
Figure 110 - Verify an ISO 15765-4 SID $09 CALID request with 9 CALIDs on an ECU (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
2 ECUs responds with 1 CVN each.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.13.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 15765_11_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$06, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and the CVN for ECU #2 is $2791BC88.
Figure 111 - Verify an ISO 15765-4 SID $09 CVN request (11-bit, 500K)
9.2.54 Verify a SID $09 CVN Request (29-bit, 500K; 2 ECU w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
2 ECUs responds with 1 CVN each.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.15.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 15765_29_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$06, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and the CVN for ECU #2 is $2791BC88.
Figure 112 - Verify an ISO 15765-4 SID $09 CVN request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs responds with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.17.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 15765_11_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU8_SID$09_INF$06_9, 15765_11_ECU1_SID$09_INF$06_9,
15765_11_ECU7_SID$09_INF$06_9, 15765_11_ECU2_SID$09_INF$06_9,
15765_11_ECU6_SID$09_INF$06_9, 15765_11_ECU3_SID$09_INF$06_9,
15765_11_ECU5_SID$09_INF$06_9, 15765_11_ECU4_SID$09_INF$06_9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Figure 113 - Verify an ISO 15765-4 SID $09 CVN request with 9 CVNs on an ECU (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs responds with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.19.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 15765_29_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU8_SID$09_INF$06_9, 15765_29_ECU1_SID$09_INF$06_9,
15765_29_ECU7_SID$09_INF$06_9, 15765_29_ECU2_SID$09_INF$06_9,
15765_29_ECU6_SID$09_INF$06_9, 15765_29_ECU3_SID$09_INF$06_9,
15765_29_ECU5_SID$09_INF$06_9, 15765_29_ECU4_SID$09_INF$06_9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Figure 114 - Verify an ISO 15765-4 SID $09 CVN request with 9 CVNs on an ECU (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 15765_11_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$08_32, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$08_32.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
Figure 115 - Verify an ISO 15765-4 SID $09 IPT (INF$08, 32 bytes) request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 15765_29_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$08_32, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$08_32.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
Figure 116 - Verify an ISO 15765-4 SID $09 IPT (INF$08, 32 bytes) request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.13.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 15765_11_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$08_40, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$08_40.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
SO2SCOMP1 = 90
SO2SCOND1 = 95
SO2SCOMP2 = 00
SO2SCOND2 = 00
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 117 - Verify an ISO 15765-4 SID $09 IPT (INF$08, 40 bytes) request (11-bit, 500K)
9.2.60 Verify a SID $09 IPT (INF$08, 40 bytes) Request (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.15.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 15765_29_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$08_40, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$08_40.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
SO2SCOMP1 = 90
SO2SCOND1 = 95
SO2SCOMP2 = 00
SO2SCOND2 = 00
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 118 - Verify an ISO 15765-4 SID $09 IPT (INF$08, 40 bytes) request (29-bit, 500K)
9.2.61 Verify a SID $09 ECU Name Request (11-bit, 500K; 8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0A.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.17.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0A (ECU Name).
EVALUATION
Pass if the 15765_11_SID$09_INF$0A message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU4_SID$09_INF$0A, 15765_11_ECU5_SID$09_INF$0A,
15765_11_ECU6_SID$09_INF$0A, 15765_11_ECU3_SID$09_INF$0A,
15765_11_ECU2_SID$09_INF$0A, 15765_11_ECU7_SID$09_INF$0A,
15765_11_ECU1_SID$09_INF$0A, 15765_11_ECU8_SID$09_INF$0A.
EVALUATION
Pass if the following are true:
Transmission is successful.
The DUT indicates that the ECU Name for ECU #1 is “ECM1-EngineControl1”.
The DUT indicates that the ECU Name for ECU #2 is “ECM2-EngineControl2”.
The DUT indicates that the ECU Name for ECU #3 is “TCM1-TransmisCtrl1”.
The DUT indicates that the ECU Name for ECU #4 is “ECC1-EmisCritInfo1”.
The DUT indicates that the ECU Name for ECU #5 is “ECC2-EmisCritInfo2”.
The DUT indicates that the ECU Name for ECU #6 is “TCM2-TransmisCtrl2”.
The DUT indicates that the ECU Name for ECU #7 is “TCC1-TransfCaseCtrl1”.
The DUT indicates that the ECU Name for ECU #8 is “TCC2-TransfCaseCtrl2”.
Figure 119 - Verify an ISO 15765-4 SID $09 ECU name request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0A.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) SID9 Ready State”,
which is detailed in 5.4.3.19.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0A (ECU Name).
EVALUATION
Pass if the 15765_29_SID$09_INF$0A message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU4_SID$09_INF$0A, 15765_29_ECU5_SID$09_INF$0A,
15765_29_ECU6_SID$09_INF$0A, 15765_29_ECU3_SID$09_INF$0A,
15765_29_ECU2_SID$09_INF$0A, 15765_29_ECU7_SID$09_INF$0A,
15765_29_ECU1_SID$09_INF$0A, 15765_29_ECU8_SID$09_INF$0A.
EVALUATION
Pass if the following are true:
Transmission is successful.
The DUT indicates that the ECU Name for ECU #1 is “ECM1-EngineControl1”.
The DUT indicates that the ECU Name for ECU #2 is “ECM2-EngineControl2”.
The DUT indicates that the ECU Name for ECU #3 is “TCM1-TransmisCtrl1”.
The DUT indicates that the ECU Name for ECU #4 is “ECC1-EmisCritInfo1”.
The DUT indicates that the ECU Name for ECU #5 is “ECC2-EmisCritInfo2”.
The DUT indicates that the ECU Name for ECU #6 is “TCM2-TransmisCtrl2”.
The DUT indicates that the ECU Name for ECU #7 is “TCC1-TransfCaseCtrl1”.
The DUT indicates that the ECU Name for ECU #8 is “TCC2-TransfCaseCtrl2”.
Figure 120 - Verify an ISO 15765-4 SID $09 ECU name request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 15765_11_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$0B_32, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$0B_32.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
EGSCOND = 55
EGRCOMP = 60
EGRCOND = 65
BPCOND = 70
BPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
Figure 121 - Verify an ISO 15765-4 SID $09 IPT (INF$0B, 32 bytes) request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 15765_29_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$0B_32, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$0B_32.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
EGSCOND = 55
EGRCOMP = 60
EGRCOND = 65
BPCOND = 70
BPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
Figure 122 - Verify an ISO 15765-4 SID $09 IPT (INF$0B, 32 bytes) request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (36
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) SID9 Diesel Ready
State”, which is detailed in 5.4.3.14.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 15765_11_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$09_INF$0B_36, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$09_INF$0B_36.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
EGSCOND = 55
EGRCOMP = 60
EGRCOND = 65
BPCOND = 70
BPCOND = 75
FUELCOND = 80
FUELCOND = 85
The DUT indicates that the IPT for ECU #2 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 123 - Verify an ISO 15765-4 SID $09 IPT (INF$0B, 36 bytes) request (11-bit, 500K)
9.2.66 Verify a SID $09 IPT (INF$0B, 36 bytes) Request (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (36
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) SID9 Diesel Ready
State”, which is detailed in 5.4.3.16.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 15765_29_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$09_INF$0B_36, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$09_INF$0B_36.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
EGSCOND = 55
EGRCOMP = 60
EGRCOND = 65
BPCOND = 70
BPCOND = 75
FUELCOND = 80
FUELCOND = 85
The DUT indicates that the IPT for ECU #2 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 124 - Verify an ISO 15765-4 SID $09 IPT (INF$0B, 36 bytes) request (29-bit, 500K)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0D.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be the same as that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) SID9 Diesel Ready
State”, which is detailed in 5.4.3.18.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0D (ESN).
EVALUATION
Pass if the 15765_11_SID$09_INF$0D message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU1_SID$09_INF$0D, 15765_11_ECU2_SID$09_INF$0D,
15765_11_ECU3_SID$09_INF$0D, 15765_11_ECU4_SID$09_INF$0D,
15765_11_ECU5_SID$09_INF$0D, 15765_11_ECU6_SID$09_INF$0D,
15765_11_ECU7_SID$09_INF$0D, 15765_11_ECU8_SID$09_INF$0D.
EVALUATION
Pass if the following are true:
Transmission is successful
The DUT indicates that the ESN for ECU #1 is “VALESN987651”.
The DUT indicates that the ESN for ECU #2 is “VALESN987652”.
The DUT indicates that the ESN for ECU #3 is “VALESN987653”.
The DUT indicates that the ESN for ECU #4 is “VALESN987654”.
The DUT indicates that the ESN for ECU #5 is “VALESN987655”.
The DUT indicates that the ESN for ECU #6 is “VALESN987656”.
The DUT indicates that the ESN for ECU #7 is “VALESN987657”.
The DUT indicates that the ESN for ECU #8 is “VALESN987658”.
Figure 125 - Verify an ISO 15765-4 SID $09 ESN request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0D.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be the same as that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) SID9 Diesel Ready
State”, which is detailed in 5.4.3.20.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0D (ESN).
EVALUATION
Pass if the 15765_29_SID$09_INF$0D message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU1_SID$09_INF$0D, 15765_29_ECU2_SID$09_INF$0D,
15765_29_ECU3_SID$09_INF$0D, 15765_29_ECU4_SID$09_INF$0D,
15765_29_ECU5_SID$09_INF$0D, 15765_29_ECU6_SID$09_INF$0D,
15765_29_ECU7_SID$09_INF$0D, 15765_29_ECU8_SID$09_INF$0D.
EVALUATION
Pass if the following are true:
Transmission is successful
The DUT indicates that the ESN for ECU #1 is “VALESN987651”.
The DUT indicates that the ESN for ECU #2 is “VALESN987652”.
The DUT indicates that the ESN for ECU #3 is “VALESN987653”.
The DUT indicates that the ESN for ECU #4 is “VALESN987654”.
The DUT indicates that the ESN for ECU #5 is “VALESN987655”.
The DUT indicates that the ESN for ECU #6 is “VALESN987656”.
The DUT indicates that the ESN for ECU #7 is “VALESN987657”.
The DUT indicates that the ESN for ECU #8 is “VALESN987658”.
Figure 126 - Verify an ISO 15765-4 SID $09 ESN request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0F.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 8 ECUs) SID9 Diesel Ready
State”, wich is detailed in 5.4.3.18.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0F (EROTAN).
EVALUATION
Pass if the 15765_11_SID$09_INF$0F message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_11_ECU8_SID$09_INF$0F, 15765_11_ECU7_SID$09_INF$0F,
15765_11_ECU6_SID$09_INF$0F, 15765_11_ECU5_SID$09_INF$0F,
15765_11_ECU4_SID$09_INF$0F, 15765_11_ECU3_SID$09_INF$0F,
15765_11_ECU2_SID$09_INF$0F, 15765_11_ECU1_SID$09_INF$0F.
EVALUATION
Pass if the following are true:
Transmission is successful.
The DUT indicates that the EROTAN for ECU #1 is “VALERTAN1”.
The DUT indicates that the EROTAN for ECU #2 is “VALERTAN2”.
The DUT indicates that the EROTAN for ECU #3 is “VALERTAN3”.
The DUT indicates that the EROTAN for ECU #4 is “VALERTAN4”.
The DUT indicates that the EROTAN for ECU #5 is “VALERTAN5”.
The DUT indicates that the EROTAN for ECU #6 is “VALERTAN6”.
The DUT indicates that the EROTAN for ECU #7 is “VALERTAN7”.
The DUT indicates that the EROTAN for ECU #8 is “VALERTAN8”.
Figure 127 - Verify an ISO 15765-4 SID $09 EROTAN request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0F.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 8 ECUs) SID9 Diesel Ready
State”, which is detailed in 5.4.3.20.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0F (EROTAN).
EVALUATION
Pass if the 15765_29_SID$09_INF$0F message was transmitted.
ACTION- ECUSIM
Delay P2_MIN before transmitting each of the following messages
15765_29_ECU8_SID$09_INF$0F, 15765_29_ECU7_SID$09_INF$0F,
15765_29_ECU6_SID$09_INF$0F, 15765_29_ECU5_SID$09_INF$0F,
15765_29_ECU4_SID$09_INF$0F, 15765_29_ECU3_SID$09_INF$0F,
15765_29_ECU2_SID$09_INF$0F, 15765_29_ECU1_SID$09_INF$0F.
EVALUATION
Pass if the following are true:
Transmission is successful.
The DUT indicates that the EROTAN for ECU #1 is “VALERTAN1”.
The DUT indicates that the EROTAN for ECU #2 is “VALERTAN2”.
The DUT indicates that the EROTAN for ECU #3 is “VALERTAN3”.
The DUT indicates that the EROTAN for ECU #4 is “VALERTAN4”.
The DUT indicates that the EROTAN for ECU #5 is “VALERTAN5”.
The DUT indicates that the EROTAN for ECU #6 is “VALERTAN6”.
The DUT indicates that the EROTAN for ECU #7 is “VALERTAN7”.
The DUT indicates that the EROTAN for ECU #8 is “VALERTAN8”.
Figure 128 - Verify an ISO 15765-4 SID $09 EROTAN request (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $0A and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $0A (Permanent DTCs).
EVALUATION
Pass if the 15765_11_SID$0A message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU2_SID$0A_NoDTC, delay
P2_MIN, then transmit the message 15765_11_ECU1_SID$0A_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no permanent DTCs in
either ECU.
Figure 129 - Verify an ISO 15765-4 SID $0A permanent DTC request with no DTCs (11-bit, 500K)
9.2.72 Verify a SID $0A Permanent DTC Request with No DTCs (29-bit, 500K; 2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $0A and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $0A (Permanent DTCs).
EVALUATION
Pass if the 15765_29_SID$0A message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU2_SID$0A_NoDTC, delay
P2_MIN, then transmit the message 15765_29_ECU1_SID$0A_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no permanent DTCs in
either ECU.
Figure 130 - Verify an ISO 15765-4 SID $0A permanent DTC request with no DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $0A and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (11-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.9.
Procedure:
ACTION- DUT
Initiate the request for SID $0A (Permanent DTCs).
EVALUATION
Pass if the 15765_11_SID$0A message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_11_ECU1_SID$0A_DTC, delay
P2_MIN, then transmit the message 15765_11_ECU2_SID$0A_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following permanent DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no permanent DTCs.
Figure 131 - Verify an ISO 15765-4 SID $0A permanent DTC request with DTCs (11-bit, 500K)
9.2.74 Verify a SID $0A Permanent DTC Request with DTCs (29-bit, 500K; 2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $0A and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 15765 (29-bit, 500K, 2 ECUs) Initialized State”,
which is detailed in 5.4.3.10.
Procedure:
ACTION- DUT
Initiate the request for SID $0A (Permanent DTCs).
EVALUATION
Pass if the 15765_29_SID$0A message was transmitted.
ACTION- ECUSIM
After the P2_MIN delay, transmit the message 15765_29_ECU1_SID$0A_DTC, delay
P2_MIN, then transmit the message 15765_29_ECU2_SID$0A_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following permanent DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no permanent DTCs.
Figure 132 - Verify an ISO 15765-4 SID $0A permanent DTC request with DTCs (29-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
These network tests are specific to ISO 14230-4. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.13.
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
EVALUATION
Pass if the 14230_SID$01_PID$00 or 14230_SID$01_PID$20 or 14230_SID$01_PID$40
message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$01_PID$00 then after the P2 delay, transmit
14230_ECU1_SID$01_PID$00_20, delay P2 and transmit 14230_ECU2_SID$01_PID$00.
Wait for the remaining message transactions in this ACTION to be completed.
Figure 133 - Verify an ISO 14230-4 SID $01 PID supported PID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6 with the ISO 14230-4 network connected to the ECUSIM. The ECUSIM shall be in
the “ISO 14230-4 (2 ECUs) Initialized State” as defined in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 14230_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$01_PID$01_SPARK, delay P2,
then transmit the message 14230_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 134 - Verify an ISO 14230-4 SID $01 PID $01 request for spark ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 14230_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$01_PID$01_COMP, delay P2,
then transmit the message 14230_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 135 - Verify an ISO 14230-4 SID $01 PID $01 request for compression ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 14230_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$01_PID$0C_KOEO, delay P2,
then transmit the message 14230_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 136 - Verify an ISO 14230-4 SID $01 PID $0C request
9.3.5 Verify a SID $02 PID Freeze Frame DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 14230_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$02_PID$02_NoDTC, delay P2,
then transmit the message 14230_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 137 - Verify an ISO 14230-4 SID $02 PID freeze frame DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 14230_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$02_PID$02_DTC, delay P2,
then transmit the message 14230_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 138 - Verify an ISO 14230-4 SID $02 PID freeze frame DTC request with DTCs
9.3.7 Verify a SID $03 Confirmed DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 14230_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$03_NoDTC, delay P2, then
transmit the message 14230_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 139 - Verify an ISO 14230-4 SID $03 confirmed DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 14230_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
14230_ECU1_SID$03_DTC_M1, 14230_ECU1_SID$03_DTC_M2,
14230_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 140 - Verify an ISO 14230-4 SID $03 confirmed DTC request with DTCs
9.3.9 Verify a SID $04 Clear Codes Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 14230_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$04_DONE, delay P2, then
transmit the message 14230_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 141 - Verify an ISO 14230-4 SID $04 clear codes request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 14230_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$04_NRC22, delay P2, then
transmit the message 14230_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 142 - Test an ISO 14230-4 SID $04 clear codes request with NRC=$22
9.3.11 Verify a SID $04 Clear Codes Request with NRC=$78 (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that it is busy then eventually competes.
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 14230_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$04_NRC78, delay P2, then
transmit the message 14230_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 14230_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 143 - Verify an ISO 14230-4 SID $04 clear codes request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $05 TID $01.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $05 TID $01.
EVALUATION
Pass if the 14230_SID$05_TID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$05_TID$01.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 O2 Bank 1 Sensor
2 has a test limit of 450 mV.
Figure 144 - Verify an ISO 14230-4 SID $05 TID $01 request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 14230_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 145 - Verify an ISO 14230-4 SID $06 MID supported MID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 14230_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$07_NoDTC, delay P2, then
transmit the message 14230_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 146 - Verify an ISO 14230-4 SID $07 pending DTC request with no DTCs
9.3.15 Verify a SID $07 Pending DTC Request with DTCs (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 14230_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
14230_ECU1_SID$07_DTC_M1, 14230_ECU1_SID$07_DTC_M2,
14230_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 147 - Verify an ISO 14230-4 SID $07 pending DTC request with DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 14230_SID$08_PID$00 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 148 - Verify an ISO 14230-4 SID $08 TID supported TID request
9.3.17 Verify a SID $09 INF Supported INF Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 14230_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$09_INF$00, delay P2, then
transmit the message 14230_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $08 (IPT)
Figure 149 - Verify an ISO 14230-4 SID $09 INF supported INF request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) Initialized State”, which is detailed
in 5.4.4.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 14230_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 14230_ECU2_SID$09_INF$00_DIESEL, delay P2,
then transmit the message 14230_ECU1_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $0B (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $0B (IPT)
Figure 150 - Verify an ISO 14230-4 SID $09 INF supported INF request
9.3.19 Verify a SID $09 INF Supported INF Request (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (8 ECUs) Initialized State”, which is detailed
in 5.4.4.7.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 14230_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
14230_ECU2_SID$09_INF$00, 14230_ECU1_SID$09_INF$00,
14230_ECU4_SID$09_INF$00, 14230_ECU3_SID$09_INF$00,
14230_ECU6_SID$09_INF$00, 14230_ECU5_SID$09_INF$00,
14230_ECU8_SID$09_INF$00, and 14230_ECU7_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 151 - Verify an ISO 14230-4 SID $09 INF supported INF request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 14230_SID$09_INF$01 or 14230_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$01 then after the P2 delay, transmit the message
14230_ECU1_SID$09_INF$01 and wait for the DUT to transmit 14230_SID$09_INF$02.
If the DUT transmitted 14230_SID$09_INF$02 then after the P2 delay, transmit the messages
(with a P2 delay between each message): 14230_ECU1_SID$09_INF$02_M1,
14230_ECU1_SID$09_INF$02_M2, 14230_ECU1_SID$09_INF$02_M3,
14230_ECU1_SID$09_INF$02_M4, 14230_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 14230_SID$09_INF$01 or 14230_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
If the DUT transmits the message 14230_SID$09_INF$01, then after the delay P2, transmit
the message 14230_ECU1_SID$09_INF$01. Wait for the remaining message transactions in
this ACTION to be completed.
If the DUT transmits the message 14230_SID$09_INF$02, then after the delay P2_MIN and transmit the
message 14230_ECU1_SID$09_NRC78..EVALUATION
Pass if the 14230_ECU1_SID$09_NRC78 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
14230_ECU1_SID$09_INF$02_M1, 14230_ECU1_SID$09_INF$02_M2,
14230_ECU1_SID$09_INF$02_M3, 14230_ECU1_SID$09_INF$02_M4,
14230_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 153 - Verify an ISO 14230-4 SID $09 VIN request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 14230_SID$09_INF$03 or 14230_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$03 then after the P2 delay, transmit the message
14230_ECU1_SID$09_INF$03 and wait for the DUT to transmit 14230_SID$09_INF$04.
If the DUT transmitted 14230_SID$09_INF$04 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$04_M1,
14230_ECU1_SID$09_INF$04_M1, 14230_ECU2_SID$09_INF$04_M2,
14230_ECU1_SID$09_INF$04_M2, 14230_ECU2_SID$09_INF$04_M3,
14230_ECU1_SID$09_INF$04_M3, 14230_ECU2_SID$09_INF$04_M4,
14230_ECU1_SID$09_INF$04_M4.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
9.3.23 Verify a SID $09 CALID Request with 9 CALIDs from Each of 8 ECUs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs respond with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 14230_SID$09_INF$03 or 14230_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$03 then after the P2 delay, transmit the following
messages (with a P2 delay between each message):
14230_ECU5_SID$09_INF$03, 14230_ECU2_SID$09_INF$03,
14230_ECU6_SID$09_INF$03, 14230_ECU3_SID$09_INF$03,
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 14230_SID$09_INF$04 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU5_SID$09_INF$04_9_M1
thru 14230_ECU5_SID$09_INF$04_9_M35, 14230_ECU2_SID$09_INF$04_9_M1 thru
14230_ECU2_SID$09_INF$04_9_M35, 14230_ECU6_SID$09_INF$04_9_M1 thru
14230_ECU6_SID$09_INF$04_9_M35, 14230_ECU3_SID$09_INF$04_9_M1 thru
14230_ECU3_SID$09_INF$04_9_M35, 14230_ECU7_SID$09_INF$04_9_M1 thru
14230_ECU7_SID$09_INF$04_9_M35, 14230_ECU4_SID$09_INF$04_9_M1 thru
14230_ECU4_SID$09_INF$04_9_M35, 14230_ECU1_SID$09_INF$04_9_M1 thru
14230_ECU1_SID$09_INF$04_9_M35, 14230_ECU8_SID$09_INF$04_9_M1 thru
14230_ECU8_SID$09_INF$04_9_M35.
EVALUATION
Pass if the following is true:
All Transmissions are successful.
The DUT indicates that the CALID for ECU #1 are: “11589778”, “21589777”, “31589776”,
“41589775”, “51589774”, “61589773”, “71589772”, “81589771”, “91589770”.
The DUT indicates that the CALID for ECU #2 are: “12589778”, “22589777”, “32589776”,
“42589775”, “52589774”, “62589773”, “72589772”, “82589771”, “92589770”.
The DUT indicates that the CALID for ECU #3 are: “13589778”, “23589777”, “33589776”,
“43589775”, “53589774”, “63589773”, “73589772”, “83589771”, “93589770”.
The DUT indicates that the CALID for ECU #4 are: “14589778”, “24589777”, “34589776”,
“44589775”, “54589774”, “64589773”, “74589772”, “84589771”, “94589770”.
The DUT indicates that the CALID for ECU #5 are: “15589778”, “25589777”, “35589776”,
“45589775”, “55589774”, “65589773”, “75589772”, “85589771”, “95589770”.
The DUT indicates that the CALID for ECU #6 are: “16589778”, “26589777”, “36589776”,
“46589775”, “56589774”, “66589773”, “76589772”, “86589771”, “96589770”.
The DUT indicates that the CALID for ECU #7 are: “17589778”, “27589777”, “37589776”,
“47589775”, “57589774”, “67589773”, “77589772”, “87589771”, “97589770”.
The DUT indicates that the CALID for ECU #8 are: “18589778”, “28589777”, “38589776”,
“48589775”, “58589774”, “68589773”, “78589772”, “88589771”, “98589770”.
Figure 155 - Verify an ISO 14230-4 SID $09 CALID request with 9 CALIDs on an ECU
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06.
Rationale: This test will use positive responses from a two ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 14230_SID$09_INF$05 or 14230_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$05 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU1_SID$09_INF$05,
14230_ECU2_SID$09_INF$05 and wait for the DUT to transmit 14230_SID$09_INF$06.
If the DUT transmitted 14230_SID$09_INF$06 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU1_SID$09_INF$06 and
14230_ECU2_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and ECU #2 is $2791BC88.
9.3.25 Verify a SID $09 CVN Request with 9 CVNs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs responds with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and the ECUSIM shall be in the “ISO 14230-4 (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 14230_SID$09_INF$05 or 14230_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$05 then after the P2 delay, transmit the following
messages (with a P2 delay between each message):
14230_ECU5_SID$09_INF$05, 14230_ECU2_SID$09_INF$05,
14230_ECU6_SID$09_INF$05, 14230_ECU3_SID$09_INF$05,
14230_ECU7_SID$09_INF$05, 14230_ECU4_SID$09_INF$05,
14230_ECU1_SID$09_INF$05, 14230_ECU8_SID$09_INF$05 and wait for the DUT to
transmit 14230_SID$09_INF$06.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 14230_SID$09_INF$06 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU8_SID$09_INF$06_9_M1 to
14230_ECU8_SID$09_INF$06_9_M9, 14230_ECU1_SID$09_INF$06_9_M1 to
14230_ECU1_SID$09_INF$06_9_M9, 14230_ECU7_SID$09_INF$06_9_M1 to
14230_ECU7_SID$09_INF$06_9_M9, 14230_ECU2_SID$09_INF$06_9_M1 to
14230_ECU2_SID$09_INF$06_9_M9, 14230_ECU6_SID$09_INF$06_9_M1 to
14230_ECU6_SID$09_INF$06_9_M9, 14230_ECU3_SID$09_INF$06_9_M1 to
14230_ECU3_SID$09_INF$06_9_M9, 14230_ECU5_SID$09_INF$06_9_M1 to
14230_ECU5_SID$09_INF$06_9_M9, 14230_ECU4_SID$09_INF$06_9_M1 to
14230_ECU4_SID$09_INF$06_9_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Figure 157 - Verify an ISO 14230-4 SID $09 CVN request with 9 CVNs on an ECU
9.3.26 Verify a SID $09 IPT (INF$08, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 14230_SID$09_INF$07 or 14230_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$07_832,
14230_ECU1_SID$09_INF$07_832 and wait for the DUT to transmit 14230_SID$09_INF$08.
If the DUT transmitted 14230_SID$09_INF$08 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$08_32_M1
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
Figure 158 - Verify an ISO 14230-4 SID $09 IPT (INF$08, 32 bytes) request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.4.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 14230_SID$09_INF$07 or 14230_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$07_840,
14230_ECU1_SID$09_INF$07_840 and wait for the DUT to transmit 14230_SID$09_INF$08.
If the DUT transmitted 14230_SID$09_INF$08 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$08_40_M1
thru 14230_ECU2_SID$09_INF$08_40_M10, 14230_ECU1_SID$09_INF$08_40_M1 thru
14230_ECU1_SID$09_INF$08_40_M10.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
SO2SCOMP1 = 90
SO2SCOND1 = 95
SO2SCOMP2 = 00
SO2SCOND2 = 00
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 159 - Verify an ISO 14230-4 SID $09 IPT (INF$08, 40 bytes) request
9.3.28 Verify a SID $09 IPT (INF$0B, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Diesel Ready State”, which
is detailed in 5.4.4.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 14230_SID$09_INF$07 or 14230_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$07_B32,
14230_ECU1_SID$09_INF$07_B32 and wait for the DUT to transmit 14230_SID$09_INF$08.
If the DUT transmitted 14230_SID$09_INF$0B then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$0B_32_M1
thru 14230_ECU2_SID$09_INF$0B_32_M8, 14230_ECU1_SID$09_INF$0B_32_M1 thru
14230_ECU1_SID$09_INF$0B_32_M8.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
Figure 160 - Verify an ISO 14230-4 SID $09 IPT (INF$0B, 32 bytes) request
9.3.29 Verify a SID $09 IPT (INF$0B, 36 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (36
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 14230-4 (2 ECUs) SID9 Diesel Ready State”, which
is detailed in 5.4.4.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 14230_SID$09_INF$07 or 14230_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 14230_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$07_B36,
14230_ECU1_SID$09_INF$07_B36 and wait for the DUT to transmit 14230_SID$09_INF$08.
If the DUT transmitted 14230_SID$09_INF$0B then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 14230_ECU2_SID$09_INF$0B_36_M1
thru 14230_ECU2_SID$09_INF$0B_36_M9, 14230_ECU1_SID$09_INF$0B_36_M1 thru
14230_ECU1_SID$09_INF$0B_36_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
FUELCOND = 00
FUELCOND = 00
Figure 161 - Verify an ISO 14230-4 SID $09 IPT (INF$0B, 36 bytes) request
These network tests are specific to ISO 9141-2. Unless otherwise specified, all references to Electrical Connections, ECU
Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.4.7.
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
EVALUATION
Pass if all transmissions by the DUT and ECUSIM were successful and the DUT indicates
that:
ECU #1 supports PIDs $01(Readiness Bits), $0C (RPM), and $41 (Monitor Status this drive
cycle) are supported.
ECU #2 supports PIDs $01(Readiness Bits) and $0C (RPM) are supported.
Figure 162 - Verify an ISO 9141-2 SID $01 PID supported PID request
9.4.2 Verify a SID $01 PID $01 Request for Spark Ignition (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 9141_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$01_PID$01_SPARK, delay P2,
then transmit the message 9141_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 163 - Verify an ISO 9141-2 SID $01 PID $01 request for spark ignition
9.4.3 Verify a SID $01 PID $01 Request for Compression Ignition (2 ECUs w/ Order Swap)
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 9141_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$01_PID$01_COMP, delay P2,
then transmit the message 9141_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 164 - Verify an ISO 9141-2 SID $01 PID $01 request for compression ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 9141_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$01_PID$0C_KOEO, delay P2,
then transmit the message 9141_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 165 - Verify an ISO 9141-2 SID $01 PID $0C request
9.4.5 Verify a SID $02 PID Freeze Frame DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 9141_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$02_PID$02_NoDTC, delay P2,
then transmit the message 9141_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 166 - Verify an ISO 9141-2 SID $02 PID freeze frame DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 9141_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$02_PID$02_DTC, delay P2, then
transmit the message 9141_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 167 - Verify an ISO 9141-2 SID $02 PID freeze frame DTC request with DTCs
9.4.7 Verify a SID $03 Confirmed DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 9141_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$03_NoDTC, delay P2, then
transmit the message 9141_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 168 - Verify an ISO 9141-2 SID $03 confirmed DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 9141_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
9141_ECU1_SID$03_DTC_M1, 9141_ECU1_SID$03_DTC_M2,
9141_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 169 - Verify an ISO 9141-2 SID $03 confirmed DTC request with DTCs
9.4.9 Verify a SID $04 Clear Codes Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 9141_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$04_DONE, delay P2, then
transmit the message 9141_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 170 - Verify an ISO 9141-2 SID $04 clear codes request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 9141_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$04_NRC22, delay P2, then
transmit the message 9141_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 171 - Test an ISO 9141-2 SID $04 clear codes request with NRC=$22
9.4.11 Verify a SID $04 Clear Codes Request with NRC=$78 (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that it is busy then eventually competes.
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 9141_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$04_NRC78, delay P2, then
transmit the message 9141_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 9141_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 172 - Verify an ISO 9141-2 SID $04 clear codes request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $05 TID $01.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $05 TID $01.
EVALUATION
Pass if the 9141_SID$05_TID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$05_MID$01.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 ECU #1 O2 Bank 1
Sensor 2 has a test limit of 450 mV.
Figure 173 - Verify an ISO 9141-2 SID $05 TID $01 request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 9141_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 174 - Verify an ISO 9141-2 SID $06 MID supported MID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 9141_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$07_NoDTC, delay P2, then
transmit the message 9141_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 175 - Verify an ISO 9141-2 SID $07 pending DTC request with no DTCs
9.4.15 Verify a SID $07 Pending DTC Request with DTCs (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 9141_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
9141_ECU1_SID$07_DTC_M1, 9141_ECU1_SID$07_DTC_M2,
9141_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 176 - Verify an ISO 9141-2 SID $07 pending DTC request with DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 9141_SID$08_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 177 - Verify an ISO 9141-2 SID $08 TID supported TID request
9.4.17 Verify a SID $09 INF Supported INF Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 9141_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$09_INF$00, delay P2, then
transmit the message 9141_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $08 (IPT)
Figure 178 - Verify an ISO 9141-2 SID $09 INF supported INF request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 9141_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 9141_ECU2_SID$09_INF$00_DIESEL, delay P2,
then transmit the message 9141_ECU1_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $0B (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $0B (IPT)
Figure 179 - Verify an ISO 9141-2 SID $09 INF supported INF request
9.4.19 Verify a SID $09 INF Supported INF Request (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) Initialized State”, which is detailed
in 5.4.5.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 9141_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
9141_ECU2_SID$09_INF$00, 9141_ECU1_SID$09_INF$00, 9141_ECU4_SID$09_INF$00,
9141_ECU3_SID$09_INF$00, 9141_ECU6_SID$09_INF$00, 9141_ECU5_SID$09_INF$00,
9141_ECU8_SID$09_INF$00, 9141_ECU7_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 180 - Verify an ISO 9141-2 SID $09 INF supported INF request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 9141_SID$09_INF$01 or 9141_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$01 then after the P2 delay, transmit the message
9141_ECU1_SID$09_INF$01 and wait for the DUT to transmit 9141_SID$09_INF$02.
If the DUT transmitted 9141_SID$09_INF$02 then after the P2 delay, transmit the messages
(with a P2 delay between each message): 9141_ECU1_SID$09_INF$02_M1,
9141_ECU1_SID$09_INF$02_M2, 9141_ECU1_SID$09_INF$02_M3,
9141_ECU1_SID$09_INF$02_M4, 9141_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 9141_SID$09_INF$01 or 9141_SID$09_INF$02 message was transmitted.
ACTION- ECUSIM
If the DUT transmits the message 9141_SID$09_INF$01, then after the delay P2, transmit the
message 9141_ECU1_SID$09_INF$01. Wait for the remaining message transactions in this
ACTION to be completed.
If the DUT transmits the message 9141_SID$09_INF$02, then after the delay P2_MIN and
transmit the message 9141_ECU1_SID$09_NRC78.
EVALUATION
Pass if the 9141_ECU1_SID$09_NRC78 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
9141_ECU1_SID$09_INF$02_M1, 9141_ECU1_SID$09_INF$02_M2,
9141_ECU1_SID$09_INF$02_M3, 9141_ECU1_SID$09_INF$02_M4,
9141_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 182 - Verify an ISO 9141-2 SID $09 VIN request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 9141_SID$09_INF$03 or 9141_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$03 then after the P2 delay, transmit the message
9141_ECU1_SID$09_INF$03 and wait for the DUT to transmit 9141_SID$09_INF$04.
If the DUT transmitted 9141_SID$09_INF$04 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$04_M1,
9141_ECU1_SID$09_INF$04_M1, 9141_ECU2_SID$09_INF$04_M2,
9141_ECU1_SID$09_INF$04_M2, 9141_ECU2_SID$09_INF$04_M3,
9141_ECU1_SID$09_INF$04_M3, 9141_ECU2_SID$09_INF$04_M4,
9141_ECU1_SID$09_INF$04_M4.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
9.4.23 Verify a SID $09 CALID Request with 9 CALIDs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs respond with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 9141_SID$09_INF$03 or 9141_SID$09_INF$04 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$03 then after the P2 delay, transmit the following
messages (with a P2 delay between each message):
9141_ECU5_SID$09_INF$03, 9141_ECU2_SID$09_INF$03, 9141_ECU6_SID$09_INF$03,
9141_ECU3_SID$09_INF$03, 9141_ECU7_SID$09_INF$03, 9141_ECU4_SID$09_INF$03,
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 9141_SID$09_INF$04 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU5_SID$09_INF$04_9_M1
thru 9141_ECU5_SID$09_INF$04_9_M35, 9141_ECU2_SID$09_INF$04_9_M1 thru
9141_ECU2_SID$09_INF$04_9_M35, 9141_ECU6_SID$09_INF$04_9_M1 thru
9141_ECU6_SID$09_INF$04_9_M35, 9141_ECU3_SID$09_INF$04_9_M1 thru
9141_ECU3_SID$09_INF$04_9_M35, 9141_ECU7_SID$09_INF$04_9_M1 thru
9141_ECU7_SID$09_INF$04_9_M35, 9141_ECU4_SID$09_INF$04_9_M1 thru
9141_ECU4_SID$09_INF$04_9_M35, 9141_ECU1_SID$09_INF$04_9_M1 thru
9141_ECU1_SID$09_INF$04_9_M35, 9141_ECU8_SID$09_INF$04_9_M1 thru
9141_ECU8_SID$09_INF$04_9_M35.
EVALUATION
Pass if the following is true:
All Transmissions are successful.
The DUT indicates that the CALID for ECU #1 are: “11589778”, “21589777”, “31589776”,
“41589775”, “51589774”, “61589773”, “71589772”, “81589771”, “91589770”.
The DUT indicates that the CALID for ECU #2 are: “12589778”, “22589777”, “32589776”,
“42589775”, “52589774”, “62589773”, “72589772”, “82589771”, “92589770”.
The DUT indicates that the CALID for ECU #3 are: “13589778”, “23589777”, “33589776”,
“43589775”, “53589774”, “63589773”, “73589772”, “83589771”, “93589770”.
The DUT indicates that the CALID for ECU #4 are: “14589778”, “24589777”, “34589776”,
“44589775”, “54589774”, “64589773”, “74589772”, “84589771”, “94589770”.
The DUT indicates that the CALID for ECU #5 are: “15589778”, “25589777”, “35589776”,
“45589775”, “55589774”, “65589773”, “75589772”, “85589771”, “95589770”.
The DUT indicates that the CALID for ECU #6 are: “16589778”, “26589777”, “36589776”,
“46589775”, “56589774”, “66589773”, “76589772”, “86589771”, “96589770”.
The DUT indicates that the CALID for ECU #7 are: “17589778”, “27589777”, “37589776”,
“47589775”, “57589774”, “67589773”, “77589772”, “87589771”, “97589770”.
The DUT indicates that the CALID for ECU #8 are: “18589778”, “28589777”, “38589776”,
“48589775”, “58589774”, “68589773”, “78589772”, “88589771”, “98589770”.
Figure 184 - Verify an ISO 9141-2 SID $09 CALID request with 9 CALIDs on an ECU
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06.
Rationale: This test will use positive responses from a two ECUs.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 9141_SID$09_INF$05 or 9141_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$05 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU1_SID$09_INF$05,
9141_ECU2_SID$09_INF$05 and wait for the DUT to transmit 9141_SID$09_INF$06.
If the DUT transmitted 9141_SID$09_INF$06 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU1_SID$09_INF$06 and
9141_ECU2_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and ECU #2 is $2791BC88.
9.4.25 Verify a SID $09 CVN Request with 9 CVNs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs responds with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 9141_SID$09_INF$05 or 9141_SID$09_INF$06 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$05 then after the P2 delay, transmit the following
messages (with a P2 delay between each message):
9141_ECU5_SID$09_INF$05, 9141_ECU2_SID$09_INF$05, 9141_ECU6_SID$09_INF$05,
9141_ECU3_SID$09_INF$05, 9141_ECU7_SID$09_INF$05, 9141_ECU4_SID$09_INF$05,
9141_ECU1_SID$09_INF$05, 9141_ECU8_SID$09_INF$05 and wait for the DUT to transmit
9141_SID$09_INF$06.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 9141_SID$09_INF$06 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU8_SID$09_INF$06_9_M1 to
9141_ECU8_SID$09_INF$06_9_M9, 9141_ECU1_SID$09_INF$06_9_M1 to
9141_ECU1_SID$09_INF$06_9_M9, 9141_ECU7_SID$09_INF$06_9_M1 to
9141_ECU7_SID$09_INF$06_9_M9, 9141_ECU2_SID$09_INF$06_9_M1 to
9141_ECU2_SID$09_INF$06_9_M9, 9141_ECU6_SID$09_INF$06_9_M1 to
9141_ECU6_SID$09_INF$06_9_M9, 9141_ECU3_SID$09_INF$06_9_M1 to
9141_ECU3_SID$09_INF$06_9_M9, 9141_ECU5_SID$09_INF$06_9_M1 to
9141_ECU5_SID$09_INF$06_9_M9, 9141_ECU4_SID$09_INF$06_9_M1 to
9141_ECU4_SID$09_INF$06_9_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Figure 186 - Verify an ISO 9141-2 SID $09 CVN request with 9 CVNs on an ECU
9.4.26 Verify a SID $09 IPT (INF$08, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID( Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 9141_SID$09_INF$07 or 9141_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$07_832,
9141_ECU1_SID$09_INF$07_832 and wait for the DUT to transmit 9141_SID$09_INF$08.
If the DUT transmitted 9141_SID$09_INF$08 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$08_32_M1
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
Figure 187 - Verify an ISO 9141-2 SID $09 IPT (INF$08, 32 bytes) request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.5.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 9141_SID$09_INF$07 or9141_SID$09_INF$08 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$07_840,
9141_ECU1_SID$09_INF$07_840 and wait for the DUT to transmit 9141_SID$09_INF$08.
If the DUT transmitted 9141_SID$09_INF$08 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$08_40_M1
thru 9141_ECU2_SID$09_INF$08_40_M10, 9141_ECU1_SID$09_INF$08_40_M1 thru
9141_ECU1_SID$09_INF$08_40_M10.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
SO2SCOMP1 = 90
SO2SCOND1 = 95
SO2SCOMP2 = 00
SO2SCOND2 = 00
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 188 - Verify an ISO 9141-2 SID $09 IPT (INF$08, 40 bytes) request
9.4.28 Verify a SID $09 IPT (INF$0B, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Diesel Ready State”, which
is detailed in 5.4.5.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 9141_SID$09_INF$07 or 9141_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$07_B32,
9141_ECU1_SID$09_INF$07_B32 and wait for the DUT to transmit 9141_SID$09_INF$08.
If the DUT transmitted 9141_SID$09_INF$0B then After the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$0B_32_M1
thru 9141_ECU2_SID$09_INF$0B_32_M8, 9141_ECU1_SID$09_INF$0B_32_M1 thru
9141_ECU1_SID$09_INF$0B_32_M8.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 00
PMCOND2 = 00
EGSCOMP = 50
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
Figure 189 - Verify an ISO 9141-2 SID $09 IPT (INF$0B, 32 bytes) request
9.4.29 Verify a SID $09 IPT (INF$0B, 36 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (36
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “ISO 9141-2 (2 ECUs) SID9 Diesel Ready State”, which
is detailed in 5.4.5.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 9141_SID$09_INF$07 or9141_SID$09_INF$0B message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 9141_SID$09_INF$07 then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$07_B36,
9141_ECU1_SID$09_INF$07_B36 and wait for the DUT to transmit 9141_SID$09_INF$08.
If the DUT transmitted 9141_SID$09_INF$0B then after the P2 delay, transmit the following
messages (with a P2 delay between each message): 9141_ECU2_SID$09_INF$0B_36_M1
thru 9141_ECU2_SID$09_INF$0B_36_M9, 9141_ECU1_SID$09_INF$0B_36_M1 thru
9141_ECU1_SID$09_INF$0B_36_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
FUELCOND = 00
FUELCOND = 00
Figure 190 - Verify an ISO 9141-2 SID $09 IPT (INF$0B, 36 bytes) request
These network tests are specific to SAE J1850 VPW. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.5.7.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
EVALUATION
Pass if the 1850VPW_SID$01_PID$00 or 1850VPW_SID$01_PID$20 or
1850VPW_SID$01_PID$40 message was transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$01_PID$00 then after the P2 delay, transmit
1850VPW_ECU1_SID$01_PID$00_20, delay P2 and transmit
1850VPW_ECU2_SID$01_PID$00. Wait for the remaining message transactions in this
ACTION to be completed.
Figure 191 - Verify an SAE J1850 VPW SID $01 PID Supported PID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 1850VPW_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$01_PID$01_SPARK, delay
P2, then transmit the message 1850VPW_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 192 - Verify an SAE J1850 VPW SID $01 PID $01 request for spark ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 1850VPW_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$01_PID$01_COMP, delay
P2, then transmit the message 1850VPW_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 193 - Verify an SAE J1850 VPW SID $01 PID $01 request for compression ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 1850VPW_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$01_PID$0C_KOEO, delay
P2, then transmit the message 1850VPW_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 194 - Verify an SAE J1850 VPW SID $01 PID $0C request
9.5.5 Verify a SID $02 PID Freeze Frame DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 1850VPW_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$02_PID$02_NoDTC, delay
P2, then transmit the message 1850VPW_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 195 - Verify an SAE J1850 VPW SID $02 PID freeze frame DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 1850VPW_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$02_PID$02_DTC, delay P2,
then transmit the message 1850VPW_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 196 - Verify an SAE J1850 VPW SID $02 PID freeze frame DTC request with DTCs
9.5.7 Verify a SID $03 Confirmed DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 1850VPW_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$03_NoDTC, delay P2, then
transmit the message 1850VPW_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 197 - Verify an SAE J1850 VPW SID $03 confirmed DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 1850VPW_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850VPW_ECU1_SID$03_DTC_M1, 1850VPW_ECU1_SID$03_DTC_M2,
1850VPW_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 198 - Verify an SAE J1850 VPW SID $03 confirmed DTC request with DTCs
9.5.9 Verify a SID $04 Clear Codes Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850VPW_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$04_DONE, delay P2, then
transmit the message 1850VPW_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 199 - Verify an SAE J1850 VPW SID $04 clear codes request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850VPW_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$04_NRC22, delay P2, then
transmit the message 1850VPW_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 200 - Test an SAE J1850 VPW SID $04 clear codes request with NRC=$22
9.5.11 Verify a SID $04 Clear Codes Request with NRC=$78 (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that it is busy then eventually competes.
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850VPW_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$04_NRC78, delay P2, then
transmit the message 1850VPW_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 1850VPW_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 201 - Verify an SAE J1850 VPW SID $04 clear codes request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $05 TID $01.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $05 TID $01.
EVALUATION
Pass if the 1850VPW_SID$01_TID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$05_MID$01.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 O2 Bank 1 Sensor
2 has a test limit of 450 mV.
Figure 202 - Verify an SAE J1850 VPW SID $05 TID $01 request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 1850VPW_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 203 - Verify an SAE J1850 VPW SID $06 MID supported MID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 1850VPW_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$07_NoDTC, delay P2, then
transmit the message 1850VPW_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 204 - Verify an SAE J1850 VPW SID $07 pending DTC request with no DTCs
9.5.15 Verify a SID $07 Pending DTC Request with DTCs (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 1850VPW_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850VPW_ECU1_SID$07_DTC_M1, 1850VPW_ECU1_SID$07_DTC_M2,
1850VPW_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 205 - Verify an SAE J1850 VPW SID $07 pending DTC request with DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 1850VPW_SID$08_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 206 - Verify an SAE J1850 VPW SID $08 TID supported TID request
9.5.17 Verify a SID $09 INF Supported INF Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 1850VPW_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$09_INF$00, delay P2, then
transmit the message 1850VPW_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $08 (IPT)
Figure 207 - Verify an SAE J1850 VPW SID $09 INF supported INF request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) Initialized State”, which is
detailed in 5.4.6.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 1850VPW_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850VPW_ECU2_SID$09_INF$00_DIESEL, delay
P2, then transmit the message 1850VPW_ECU1_SID$09_INF$00_DIESEL.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $0B (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $0B (IPT)
Figure 208 - Verify an SAE J1850 VPW SID $09 INF supported INF request
9.5.19 Verify a SID $09 INF Supported INF Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (8 ECUs) Initialized State”, which is
detailed in 5.4.6.7.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 1850VPW_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$00, 1850VPW_ECU1_SID$09_INF$00,
1850VPW_ECU4_SID$09_INF$00, 1850VPW_ECU3_SID$09_INF$00,
1850VPW_ECU6_SID$09_INF$00, 1850VPW_ECU5_SID$09_INF$00,
1850VPW_ECU8_SID$09_INF$00, and 1850VPW_ECU7_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 209 - Verify an SAE J1850 VPW SID $09 INF supported INF request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 1850VPW_SID$09_INF$01 or 1850VPW_SID$09_INF$02 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$01 then after the P2 delay, transmit the
message 1850VPW_ECU1_SID$09_INF$01 and wait for the DUT to transmit
1850VPW_SID$09_INF$02.
If the DUT transmitted 1850VPW_SID$09_INF$02 then after the P2 delay, transmit the
messages (with a P2 delay between each message): 1850VPW_ECU1_SID$09_INF$02_M1,
1850VPW_ECU1_SID$09_INF$02_M2, 1850VPW_ECU1_SID$09_INF$02_M3,
1850VPW_ECU1_SID$09_INF$02_M4, 1850VPW_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 210 - Verify an SAE J1850 VPW SID $09 VIN request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 1850VPW_SID$09_INF$01 or 1850VPW_SID$09_INF$02 message was
transmitted.
ACTION- ECUSIM
If the DUT transmits the message 1850VPW_SID$09_INF$01, then after the delay P2,
transmit the message 1850VPW_ECU1_SID$09_INF$01. Wait for the remaining message
transactions in this ACTION to be completed.
If the DUT transmits the message 1850VPW_SID$09_INF$02, then after the delay P2_MIN
and transmit the message 1850VPW_ECU1_SID$09_NRC78.
EVALUATION
Pass if the 1850VPW_ECU1_SID$09_NRC78 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850VPW_ECU1_SID$09_INF$02_M1, 1850VPW_ECU1_SID$09_INF$02_M2,
1850VPW_ECU1_SID$09_INF$02_M3, 1850VPW_ECU1_SID$09_INF$02_M4,
1850VPW_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 211 - Verify an SAE J1850 VPW SID $09 VIN request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 1850VPW_SID$09_INF$03 or 1850VPW_SID$09_INF$04 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$03 then after the P2 delay, transmit the
message 1850VPW_ECU1_SID$09_INF$03 and wait for the DUT to transmit
1850VPW_SID$09_INF$04.
If the DUT transmitted 1850VPW_SID$09_INF$04 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$04_M1, 1850VPW_ECU1_SID$09_INF$04_M1,
1850VPW_ECU2_SID$09_INF$04_M2, 1850VPW_ECU1_SID$09_INF$04_M2,
1850VPW_ECU2_SID$09_INF$04_M3, 1850VPW_ECU1_SID$09_INF$04_M3,
1850VPW_ECU2_SID$09_INF$04_M4, 1850VPW_ECU1_SID$09_INF$04_M4.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
Figure 212 - Verify an SAE J1850 VPW SID $09 CALID request
9.5.23 Verify a SID $09 CALID Request with 9 CALIDs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs respond with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 1850VPW_SID$09_INF$04 or1850VPW_SID$09_INF$04 message was
transmitted.
ACTION- ECUSIM
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 1850VPW_SID$09_INF$04 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU5_SID$09_INF$04_9_M1 thru 1850VPW_ECU5_SID$09_INF$04_9_M35,
1850VPW_ECU2_SID$09_INF$04_9_M1 thru 1850VPW_ECU2_SID$09_INF$04_9_M35,
1850VPW_ECU6_SID$09_INF$04_9_M1 thru 1850VPW_ECU6_SID$09_INF$04_9_M35,
1850VPW_ECU3_SID$09_INF$04_9_M1 thru 1850VPW_ECU3_SID$09_INF$04_9_M35,
1850VPW_ECU7_SID$09_INF$04_9_M1 thru 1850VPW_ECU7_SID$09_INF$04_9_M35,
1850VPW_ECU4_SID$09_INF$04_9_M1 thru 1850VPW_ECU4_SID$09_INF$04_9_M35,
1850VPW_ECU1_SID$09_INF$04_9_M1 thru 1850VPW_ECU1_SID$09_INF$04_9_M35,
1850VPW_ECU8_SID$09_INF$04_9_M1 thru 1850VPW_ECU8_SID$09_INF$04_9_M35.
EVALUATION
Pass if the following is true:
All Transmissions are successful.
The DUT indicates that the CALID for ECU #1 are: “11589778”, “21589777”, “31589776”,
“41589775”, “51589774”, “61589773”, “71589772”, “81589771”, “91589770”.
The DUT indicates that the CALID for ECU #2 are: “12589778”, “22589777”, “32589776”,
“42589775”, “52589774”, “62589773”, “72589772”, “82589771”, “92589770”.
The DUT indicates that the CALID for ECU #3 are: “13589778”, “23589777”, “33589776”,
“43589775”, “53589774”, “63589773”, “73589772”, “83589771”, “93589770”.
The DUT indicates that the CALID for ECU #4 are: “14589778”, “24589777”, “34589776”,
“44589775”, “54589774”, “64589773”, “74589772”, “84589771”, “94589770”.
The DUT indicates that the CALID for ECU #5 are: “15589778”, “25589777”, “35589776”,
“45589775”, “55589774”, “65589773”, “75589772”, “85589771”, “95589770”.
The DUT indicates that the CALID for ECU #6 are: “16589778”, “26589777”, “36589776”,
“46589775”, “56589774”, “66589773”, “76589772”, “86589771”, “96589770”.
The DUT indicates that the CALID for ECU #7 are: “17589778”, “27589777”, “37589776”,
“47589775”, “57589774”, “67589773”, “77589772”, “87589771”, “97589770”.
The DUT indicates that the CALID for ECU #8 are: “18589778”, “28589777”, “38589776”,
“48589775”, “58589774”, “68589773”, “78589772”, “88589771”, “98589770”.
Figure 213 - Verify an SAE J1850 VPW SID $09 CALID request with 9 CALIDs on an ECU
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 1850VPW_SID$09_INF$05 or1850VPW_SID$09_INF$06 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$05 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU1_SID$09_INF$05, 1850VPW_ECU2_SID$09_INF$05 and wait for the DUT
to transmit 1850VPW_SID$09_INF$06.
If the DUT transmitted 1850VPW_SID$09_INF$06 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU1_SID$09_INF$06 and 1850VPW_ECU2_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and ECU #2 is $2791BC88.
Figure 214 - Verify an SAE J1850 VPW SID $09 CVN request
9.5.25 Verify a SID $09 CVN Request with 9 CVNs from Each of ECUs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs responds with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (8 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 1850VPW_SID$09_INF$05 or 1850VPW_SID$09_INF$06 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$05 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU5_SID$09_INF$05, 1850VPW_ECU2_SID$09_INF$05,
1850VPW_ECU6_SID$09_INF$05, 1850VPW_ECU3_SID$09_INF$05,
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 1850VPW_SID$09_INF$06 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU8_SID$09_INF$06_9_M1 to 1850VPW_ECU8_SID$09_INF$06_9_M9,
1850VPW_ECU1_SID$09_INF$06_9_M1 to 1850VPW_ECU1_SID$09_INF$06_9_M9,
1850VPW_ECU7_SID$09_INF$06_9_M1 to 1850VPW_ECU7_SID$09_INF$06_9_M9,
1850VPW_ECU2_SID$09_INF$06_9_M1 to 1850VPW_ECU2_SID$09_INF$06_9_M9,
1850VPW_ECU6_SID$09_INF$06_9_M1 to 1850VPW_ECU6_SID$09_INF$06_9_M9,
1850VPW_ECU3_SID$09_INF$06_9_M1 to 1850VPW_ECU3_SID$09_INF$06_9_M9,
1850VPW_ECU5_SID$09_INF$06_9_M1 to 1850VPW_ECU5_SID$09_INF$06_9_M9,
1850VPW_ECU4_SID$09_INF$06_9_M1 to 1850VPW_ECU4_SID$09_INF$06_9_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Figure 215 - Verify an SAE J1850 VPW SID $09 CVN Request with 9 CVNs on an ECU
9.5.26 Verify a SID $09 IPT (INF$08, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 1850VPW_SID$09_INF$07 or 1850VPW_SID$09_INF$08 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 1850VPW_SID$09_INF$08 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$08_32_M1 thru 1850VPW_ECU2_SID$09_INF$08_32_M8,
1850VPW_ECU1_SID$09_INF$08_32_M1 thru 1850VPW_ECU1_SID$09_INF$08_32_M8.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
Figure 216 - Verify an SAE J1850 VPW SID $09 IPT (INF$08, 32 bytes) request (11-bit, 500K)
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Ready State”, which is
detailed in 5.4.6.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 1850VPW_SID$09_INF$08 or 1850VPW_SID$09_INF$08 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$07_840, 1850VPW_ECU1_SID$09_INF$07_840 and wait for
the DUT to transmit 1850VPW_SID$09_INF$08.
If the DUT transmitted 1850VPW_SID$09_INF$08 then After the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$08_40_M1 thru 1850VPW_ECU2_SID$09_INF$08_40_M10,
1850VPW_ECU1_SID$09_INF$08_40_M1 thru 1850VPW_ECU1_SID$09_INF$08_40_M10.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
SO2SCOMP1 = 90
SO2SCOND1 = 95
SO2SCOMP2 = 00
SO2SCOND2 = 00
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 217 - Verify an SAE J1850 VPW SID $09 IPT (INF$08, 40 bytes) request
9.5.28 Verify a SID $09 IPT (INF$0B, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Diesel Ready State”,
which is detailed in 5.4.6.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 1850VPW_SID$09_INF$07 or 1850VPW_SID$09_INF$0B message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$07_B32, 1850VPW_ECU1_SID$09_INF$07_B32 and wait
for the DUT to transmit 1850VPW_SID$09_INF$08.
If the DUT transmitted 1850VPW_SID$09_INF$0B then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$0B_32_M1 thru 1850VPW_ECU2_SID$09_INF$0B_32_M8,
1850VPW_ECU1_SID$09_INF$0B_32_M1 thru 1850VPW_ECU1_SID$09_INF$0B_32_M8.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 10
HCCATCOND1 = 15
NCATCOMP2 = 00
NCATCOND2 = 00
NADSCOMP1 = 00
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
Figure 218 - Verify an SAE J1850 VPW SID $09 IPT (INF$0B, 32 bytes) request
9.5.29 Verify a SID $09 IPT (INF$0B, 36 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $0B (36
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 VPW (2 ECUs) SID9 Diesel Ready State”,
which is detailed in 5.4.6.9.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $0B (IPT).
EVALUATION
Pass if the 1850VPW_SID$09_INF$07 or 1850VPW_SID$09_INF$0B message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850VPW_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$07_B36, 1850VPW_ECU1_SID$09_INF$07_B36 and wait
for the DUT to transmit 1850VPW_SID$09_INF$08.
If the DUT transmitted 1850VPW_SID$09_INF$0B then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850VPW_ECU2_SID$09_INF$0B_36_M1 thru 1850VPW_ECU2_SID$09_INF$0B_36_M9,
1850VPW_ECU1_SID$09_INF$0B_36_M1 thru 1850VPW_ECU1_SID$09_INF$0B_36_M9.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 36 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
HCCATCOMP1 = 00
HCCATCOND1 = 00
NCATCOMP2 = 20
NCATCOND2 = 25
NADSCOMP1 = 00
NADSCOND1 = 00
PMCOMP2 = 40
PMCOND2 = 45
EGSCOMP = 00
EGSCOND = 00
EGRCOMP = 00
EGRCOND = 00
BPCOND = 00
BPCOND = 00
FUELCOND = 00
FUELCOND = 00
Figure 219 - Verify an SAE J1850 VPW SID $09 IPT (INF$0B, 36 bytes) request
These network tests are specific to SAE J1850 PWM. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.6.7.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID Supported
PIDs.
Rationale: This test will use positive responses from a single different ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID Supported PIDs.
EVALUATION
Pass if the 1850PWM_SID$01_PID$00 or 1850PWM_SID$01_PID$20 or
1850PWM_SID$01_PID$40 message was transmitted
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$01_PID$00 then after the P2 delay, transmit
1850PWM_ECU1_SID$01_PID$00_20, delay P2 and transmit
1850PWM_ECU2_SID$01_PID$00. Wait for the remaining message transactions in this
ACTION to be completed.
Figure 220 - Verify an SAE J1850 PWM SID $01 PID supported PID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 1850PWM_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$01_PID$01_SPARK, delay
P2, then transmit the message 1850PWM_ECU1_SID$01_PID$01_SPARK.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
SPARK IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
CATALYST MONITORING is SUPPORTED and NOT READY
HEATED CATALYST MONITORING is SUPPORTED and NOT READY
EVAPORATIVE SYSTEM MONITORING is SUPPORTED and NOT READY
SECONDARY AIR SYSTEM MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR MONITORING is SUPPORTED and NOT READY
OXYGEN SENSOR HEATER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 221 - Verify an SAE J1850 PWM SID $01 PID $01 request for spark ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order. This test will also verify that the DUT can
differentiate a spark ignition response from a compression ignition response.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $01 (I/M Readiness Bits).
EVALUATION
Pass if the 1850PWM_SID$01_PID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$01_PID$01_COMP, delay
P2, then transmit the message 1850PWM_ECU1_SID$01_PID$01_COMP.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that ECU #1 has the following values:
MIL is OFF
DCT COUNT is 0
COMPRESSION IGNITION MONITORS are SUPPORTED
MISFIRE is SUPPORTED and READY
FUEL SYSTEM MONITORING is SUPPORTED and READY
COMPREHENSIVE COMPONENT MONITORING is SUPPORTED and READY
NMHC MONITORING is SUPPORTED and NOT READY
NOX AFTERTREATMENT MONITORING is SUPPORTED and NOT READY
BOOST PRESSURE SYSTEM MONITORING is SUPPORTED and NOT READY
EXHAUST GAS SENSOR MONITORING is SUPPORTED and NOT READY
PM FILTER MONITORING is SUPPORTED and NOT READY
EGR/VVT SYSTEM MONITORING is SUPPORTED and NOT READY
Figure 222 - Verify an SAE J1850 PWM SID $01 PID $01 request for compression ignition
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request a SID $01 PID, which the
ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $01 PID $0C (RPM).
EVALUATION
Pass if the 1850PWM_SID$01_PID$0C message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$01_PID$0C_KOEO, delay
P2, then transmit the message 1850PWM_ECU1_SID$01_PID$0C_KOEO.
EVALUATION
Pass if transmission is successful and the DUT indicates that engine RPM is 0.
Figure 223 - Verify an SAE J1850 PWM SID $01 PID $0C request
9.6.5 Verify a SID $02 PID Freeze Frame DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is no Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 1850PWM_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$02_PID$02_NoDTC, delay
P2, then transmit the message 1850PWM_ECU1_SID$02_PID$02_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there is no Freeze Frame DTC
in either ECU.
Figure 224 - Verify an SAE J1850 PWM SID $02 PID freeze frame DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $02 PID $02
(indicating that there is a Freeze Frame DTC), which the ECUSIM indicates is supported.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $02 PID $02 (the Freeze Frame DTC).
EVALUATION
Pass if the 1850PWM_SID$02_PID$02 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$02_PID$02_DTC, delay P2,
then transmit the message 1850PWM_ECU2_SID$02_PID$02_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has a Freeze Frame DTC of P0107 and ECU #2 has no
Freeze Frame DTC.
Figure 225 - Verify an SAE J1850 PWM SID $02 PID freeze frame DTC request with DTCs
9.6.7 Verify a SID $03 Confirmed DTC Request with No DTCs (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 1850PWM_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$03_NoDTC, delay P2, then
transmit the message 1850PWM_ECU1_SID$03_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no confirmed DTCs in
either ECU.
Figure 226 - Verify an SAE J1850 PWM SID $03 confirmed DTC request with no DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $03 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $03 (Confirmed DTCs).
EVALUATION
Pass if the 1850PWM_SID$03 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850PWM_ECU1_SID$03_DTC_M1, 1850PWM_ECU1_SID$03_DTC_M2,
1850PWM_ECU2_SID$03_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following confirmed DTCs: P0107, P0110, P0115,
and P0124.
The DUT indicates that ECU #2 has no confirmed DTCs.
Figure 227 - Verify an SAE J1850 PWM SID $03 confirmed DTC request with DTCs
9.6.9 Verify a SID $04 Clear Codes Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850PWM_SID$04 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$04_DONE, delay P2, then
transmit the message 1850PWM_ECU1_SID$04_DONE.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 228 - Verify an SAE J1850 PWM SID $04 clear codes request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that conditions are not correct.
Rationale: This test will use negative responses (NRC $22) from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850PWM_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$04_NRC22, delay P2, then
transmit the message 1850PWM_ECU2_SID$04_NRC22.
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have NOT been
cleared.
Figure 229 - Test an SAE J1850 PWM SID $04 clear codes request with NRC=$22
9.6.11 Verify a SID $04 Clear Codes Request with NRC=$78 (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $04 when an ECU
indicates that it is busy then eventually competes.
Rationale: This test will use positive responses from the first ECU and a response pending (NRC $78)
from a second ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $04 (Clear DTCs).
EVALUATION
Pass if the 1850PWM_SID$04 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$04_NRC78, delay P2, then
transmit the message 1850PWM_ECU2_SID$04_DONE.
EVALUATION
Pass if the transmission is successful.
ACTION- ECUSIM
After the P2_78 delay, transmit the message 1850PWM_ECU1_SID$04_DONE
EVALUATION
Pass if the transmission is successful and the DUT indicates that DTCs have been cleared.
Figure 230 - Verify an SAE J1850 PWM SID $04 clear codes request with NRC=$78
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $05 TID $01.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $05 TID $01.
EVALUATION
Pass if the 1850PWM_SID$05_TID$01 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$05_TID$01.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 O2 Bank 1 Sensor
2 has a test limit of 450 mV.
Figure 231 - Verify an SAE J1850 PWM SID $05 TID $01 request
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $06 MID Supported
MIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $06 MID $00 (MID Supported MIDs).
EVALUATION
Pass if the 1850PWM_SID$06_MID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$06_MID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports MIDs $01,
$02, $05, and $06.
Figure 232 - Verify an SAE J1850 PWM SID $06 MID supported MID request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘no DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 1850PWM_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$07_NoDTC, delay P2, then
transmit the message 1850PWM_ECU1_SID$07_NoDTC.
EVALUATION
Pass if transmission is successful and the DUT indicates that there are no pending DTCs in
either ECU.
Figure 233 - Verify an SAE J1850 PWM SID $07 pending DTC request with no DTCs
9.6.15 Verify a SID $07 Pending DTC Request with DTCs (2 ECUs)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $07 and process a
‘DTCs present’ response.
Rationale: This test will use positive responses from two different ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $07 (Pending DTCs).
EVALUATION
Pass if the 1850PWM_SID$07 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850PWM_ECU1_SID$07_DTC_M1, 1850PWM_ECU1_SID$07_DTC_M2,
1850PWM_ECU2_SID$07_NoDTC.
EVALUATION
Pass if the following is true:
The transmission is successful.
The DUT indicates that ECU #1 has the following pending DTCs: P0107, P0110, P0115, and
P0124.
The DUT indicates that ECU #2 has no pending DTCs.
Figure 234 - Verify an SAE J1850 PWM SID $07 pending DTC request with DTCs
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $08 TID Supported
TIDs.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $08 TID $00 (TID Supported TIDs).
EVALUATION
Pass if the 1850PWM_SID$08_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU1_SID$08_PID$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that ECU #1 supports TID $01
(the leak test).
Figure 235 - Verify an SAE J1850 PWM SID $08 TID supported TID request
9.6.17 Verify a SID $09 INF Supported INF Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) Initialized State”, which is
detailed in 5.4.7.6.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 1850PWM_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the message 1850PWM_ECU2_SID$09_INF$00, delay P2, then
transmit the message 1850PWM_ECU1_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $08 (IPT)
Figure 236 - Verify an SAE J1850 PWM SID $09 INF supported INF request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF Supported
INFs.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (8 ECUs) Initialized State”, which is
detailed in 5.4.7.7.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $00 (INF Supported INFs).
EVALUATION
Pass if the 1850PWM_SID$09_PID$00 message was transmitted.
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$00, 1850PWM_ECU1_SID$09_INF$00,
1850PWM_ECU4_SID$09_INF$00, 1850PWM_ECU3_SID$09_INF$00,
1850PWM_ECU6_SID$09_INF$00, 1850PWM_ECU5_SID$09_INF$00,
1850PWM_ECU8_SID$09_INF$00, and 1850PWM_ECU7_SID$09_INF$00.
EVALUATION
Pass if the transmission is successful and the DUT indicates that:
ECU #1 supports INF $01 (MC_VIN), INF $02 (VIN), INF $03 (MC_CALID), INF $04 (CALID),
INF $05 (MC_CVN), INF $06 (CVN), INF $07 (MC_IPT), INF $08 (IPT)
ECU #2 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN), INF $07 (MC_IPT), INF $08 (IPT)
ECU #3 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
ECU #4 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
ECU #5 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
ECU #6 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
ECU #7 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
ECU #8 supports INF $03 (MC_CALID), INF $04 (CALID), INF $05 (MC_CVN), INF $06
(CVN)
Figure 237 - Verify an SAE J1850 PWM SID $09 INF supported INF request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02.
Rationale: This test will use a positive response from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 1850PWM_SID$09_INF$01 or 1850PWM_SID$09_INF$02 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$01 then after the P2 delay, transmit the
message 1850PWM_ECU1_SID$09_INF$01 and wait for the DUT to transmit
1850PWM_SID$09_INF$02.
If the DUT transmitted 1850PWM_SID$09_INF$02 then after the P2 delay, transmit the
messages (with a P2 delay between each message): 1850PWM_ECU1_SID$09_INF$02_M1,
1850PWM_ECU1_SID$09_INF$02_M2, 1850PWM_ECU1_SID$09_INF$02_M3,
1850PWM_ECU1_SID$09_INF$02_M4, 1850PWM_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 238 - Verify an SAE J1850 PWM SID $09 VIN request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $02 when
the ECU has an initial NRC = $78.
Rationale: This test will use a response pending (NRC $78) from a single ECU.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $02 (VIN).
EVALUATION
Pass if the 1850PWM_SID$09_INF$01 or 1850PWM_SID$09_INF$02 message was
transmitted.
ACTION- ECUSIM
If the DUT transmits the message 1850PWM_SID$09_INF$01, then after the delay P2,
transmit the message 1850PWM_ECU1_SID$09_INF$01. Wait for the remaining message
transactions in this ACTION to be completed.
If the DUT transmits the message 1850PWM_SID$09_INF$02, then after the delay P2_MIN
and transmit the message 1850PWM_ECU1_SID$09_NRC78.
EVALUATION
Pass if the 1850PWM_ECU1_SID$09_NRC78 message was transmitted
ACTION- ECUSIM
After the P2 delay, transmit the following messages (with a P2 delay between each message):
1850PWM_ECU1_SID$09_INF$02_M1, 1850PWM_ECU1_SID$09_INF$02_M2,
1850PWM_ECU1_SID$09_INF$02_M3, 1850PWM_ECU1_SID$09_INF$02_M4,
1850PWM_ECU1_SID$09_INF$02_M5.
EVALUATION
Pass if the transmission is successful and the DUT indicates that VIN is
1GYDE63A7A0000000.
Figure 239 - Verify an SAE J1850 PWM SID $09 VIN request with NRC=$78
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04.
Rationale: This test will use positive responses from two different ECUs. The order of ECU responses will
be different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 1850PWM_SID$09_INF$03 or1850PWM_SID$09_INF$04 message was
transmitted.
ACTION- ECUSIM
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
If the DUT transmitted 1850PWM_SID$09_INF$04 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$04_M1, 1850PWM_ECU1_SID$09_INF$04_M1,
1850PWM_ECU2_SID$09_INF$04_M2, 1850PWM_ECU1_SID$09_INF$04_M2,
1850PWM_ECU2_SID$09_INF$04_M3, 1850PWM_ECU1_SID$09_INF$04_M3,
1850PWM_ECU2_SID$09_INF$04_M4, 1850PWM_ECU1_SID$09_INF$04_M4.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CALID for ECU #1 is
12589772 while CALID for ECU #2 is 24221419.
Figure 240 - Verify an SAE J1850 PWM SID $09 CALID request
9.6.22 Verify a SID $09 CALID Request with 9 CALIDs (8 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $04 when
8 ECUs respond with 9 CALIDs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (8 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $04 (CALID).
EVALUATION
Pass if the 1850PWM_SID$09_INF$03 or 1850PWM_SID$09_INF$04 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$03 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU5_SID$09_INF$03, 1850PWM_ECU2_SID$09_INF$03,
1850PWM_ECU6_SID$09_INF$03, 1850PWM_ECU3_SID$09_INF$03,
1850PWM_ECU7_SID$09_INF$03, 1850PWM_ECU4_SID$09_INF$03,
1850PWM_ECU1_SID$09_INF$03, 1850PWM_ECU8_SID$09_INF$03 and wait for the DUT
to transmit 1850PWM_SID$09_INF$04.
If the DUT transmitted 1850PWM_SID$09_INF$04 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU5_SID$09_INF$04_9_M1 thru 1850PWM_ECU5_SID$09_INF$04_9_M35,
1850PWM_ECU2_SID$09_INF$04_9_M1 thru 1850PWM_ECU2_SID$09_INF$04_9_M35,
1850PWM_ECU6_SID$09_INF$04_9_M1 thru 1850PWM_ECU6_SID$09_INF$04_9_M35,
1850PWM_ECU3_SID$09_INF$04_9_M1 thru 1850PWM_ECU3_SID$09_INF$04_9_M35,
1850PWM_ECU7_SID$09_INF$04_9_M1 thru 1850PWM_ECU7_SID$09_INF$04_9_M35,
1850PWM_ECU4_SID$09_INF$04_9_M1 thru 1850PWM_ECU4_SID$09_INF$04_9_M35,
1850PWM_ECU1_SID$09_INF$04_9_M1 thru 1850PWM_ECU1_SID$09_INF$04_9_M35,
1850PWM_ECU8_SID$09_INF$04_9_M1 thru 1850PWM_ECU8_SID$09_INF$04_9_M35.
EVALUATION
Pass if the following is true:
All Transmissions are successful.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 241 - Verify an SAE J1850 PWM SID $09 CALID request with 9 CALIDs on an ECU
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06.
Rationale: This test will use positive responses from a two ECUs.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 1850PWM_SID$09_INF$05 or 1850PWM_SID$09_INF$06 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$05 then after the P2 delay, transmit the
following messages (with a P2 delay between each
message):1850PWM_ECU1_SID$09_INF$05, 1850PWM_ECU2_SID$09_INF$05 and wait
for the DUT to transmit 1850PWM_SID$09_INF$06.
If the DUT transmitted 1850PWM_SID$09_INF$06 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU1_SID$09_INF$06 and 1850PWM_ECU2_SID$09_INF$06.
EVALUATION
Pass if the transmission is successful and the DUT indicates that the CVN for ECU #1 is
$1791BC88 and ECU #2 is $2791BC88.
Figure 242 - Verify an SAE J1850 PWM SID $09 CVN request
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $06 when
8 ECUs respond with 9 CVNs each.
Rationale: This test will use positive responses from eight different ECUs. The order of ECU responses
will be different than that of the original connection order with ECU3 through ECU8 indicating
that no SID $01 PIDs are supported.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (8 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.10.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $06 (CVN).
EVALUATION
Pass if the 1850PWM_SID$09_INF$05 or 1850PWM_SID$09_INF$06 message was
transmitted
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$05 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU5_SID$09_INF$05, 1850PWM_ECU2_SID$09_INF$05,
1850PWM_ECU6_SID$09_INF$05, 1850PWM_ECU3_SID$09_INF$05,
1850PWM_ECU7_SID$09_INF$05, 1850PWM_ECU4_SID$09_INF$05,
1850PWM_ECU1_SID$09_INF$05, 1850PWM_ECU8_SID$09_INF$05 and wait for the DUT
to transmit 1850PWM_SID$09_INF$06.
If the DUT transmitted 1850PWM_SID$09_INF$06 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU8_SID$09_INF$06_9_M1 to 1850PWM_ECU8_SID$09_INF$06_9_M9,
1850PWM_ECU1_SID$09_INF$06_9_M1 to 1850PWM_ECU1_SID$09_INF$06_9_M9,
1850PWM_ECU7_SID$09_INF$06_9_M1 to 1850PWM_ECU7_SID$09_INF$06_9_M9,
1850PWM_ECU2_SID$09_INF$06_9_M1 to 1850PWM_ECU2_SID$09_INF$06_9_M9,
1850PWM_ECU6_SID$09_INF$06_9_M1 to 1850PWM_ECU6_SID$09_INF$06_9_M9,
1850PWM_ECU3_SID$09_INF$06_9_M1 to 1850PWM_ECU3_SID$09_INF$06_9_M9,
1850PWM_ECU5_SID$09_INF$06_9_M1 to 1850PWM_ECU5_SID$09_INF$06_9_M9,
1850PWM_ECU4_SID$09_INF$06_9_M1 to 1850PWM_ECU4_SID$09_INF$06_9_M9.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the CVN for ECU #1 is $1791BC88, $1891BC87, $1991BC86,
$1A91BC85, $1B91BC84, $1C91BC83, $1D91BC82, $1E55AA81, $1FFF0080.
The DUT indicates that the CVN for ECU #2 is $2791BC88, $2891BC87, $2991BC86,
$2A91BC85, $2B91BC84, $2C91BC83, $2D91BC82, $2E55AA81, $2FFF0080.
The DUT indicates that the CVN for ECU #3 is $3791BC88, $3891BC87, $3991BC86,
$3A91BC85, $3B91BC84, $3C91BC83, $3D91BC82, $3E55AA81, $3FFF0080.
The DUT indicates that the CVN for ECU #4 is $4791BC88, $4891BC87, $4991BC86,
$4A91BC85, $4B91BC84, $4C91BC83, $4D91BC82, $4E55AA81, $4FFF0080.
The DUT indicates that the CVN for ECU #5 is $5791BC88, $5891BC87, $5991BC86,
$5A91BC85, $5B91BC84, $5C91BC83, $5D91BC82, $5E55AA81, $5FFF0080.
The DUT indicates that the CVN for ECU #6 is $6791BC88, $6891BC87, $6991BC86,
$6A91BC85, $6B91BC84, $6C91BC83, $6D91BC82, $6E55AA81, $6FFF0080.
The DUT indicates that the CVN for ECU #7 is $7791BC88, $7891BC87, $7991BC86,
$7A91BC85, $7B91BC84, $7C91BC83, $7D91BC82, $7E55AA81, $7FFF0080.
The DUT indicates that the CVN for ECU #8 is $8791BC88, $8891BC87, $8991BC86,
$8A91BC85, $8B91BC84, $8C91BC83, $8D91BC82, $8E55AA81, $8FFF0080.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
9.6.25 Verify a SID $09 IPT (INF$08, 32 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (32
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 1850PWM_SID$09_INF$07 or 1850PWM_SID$09_INF$08 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$07_832, 1850PWM_ECU1_SID$09_INF$07_832 and wait
for the DUT to transmit 1850PWM_SID$09_INF$08.
If the DUT transmitted 1850PWM_SID$09_INF$08 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$08_32_M1 thru 1850PWM_ECU2_SID$09_INF$08_32_M8,
1850PWM_ECU1_SID$09_INF$08_32_M1 thru 1850PWM_ECU1_SID$09_INF$08_32_M8.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
AIRCOND = 65
EVAPCOND = 70
EVAPCOND = 75
The DUT indicates that the IPT for ECU #2 is 32 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Figure 244 - Verify an SAE J1850 PWM SID $09 IPT (INF$08, 32 bytes) request (11-bit, 500K)
9.6.26 Verify a SID $09 IPT (INF$08, 40 bytes) Request (2 ECUs w/ Order Swap)
Purpose: The purpose of this test is to verify that the DUT can correctly request SID $09 INF $08 (40
bytes).
Rationale: This test will use positive responses from two ECUs. The order of ECU responses will be
different than that of the original connection order.
Set Up: The DUT and ECUSIM shall be in the “SAE J1850 PWM (2 ECUs) SID9 Ready State”, which
is detailed in 5.4.7.8.
Procedure:
ACTION- DUT
Initiate the request for SID $09 INF $08 (IPT).
EVALUATION
Pass if the 1850PWM_SID$09_INF$07 or 1850PWM_SID$09_INF$08 message was
transmitted.
ACTION- ECUSIM
If the DUT transmitted 1850PWM_SID$09_INF$07 then after the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$07_840, 1850PWM_ECU1_SID$09_INF$07_840 and wait
for the DUT to transmit 1850PWM_SID$09_INF$08.
If the DUT transmitted 1850PWM_SID$09_INF$08 then After the P2 delay, transmit the
following messages (with a P2 delay between each message):
1850PWM_ECU2_SID$09_INF$08_40_M1 thru 1850PWM_ECU2_SID$09_INF$08_40_M10,
1850PWM_ECU1_SID$09_INF$08_40_M1 thru 1850PWM_ECU1_SID$09_INF$08_40_M10.
EVALUATION
Pass if the following is true:
Transmission is successful.
The DUT indicates that the IPT for ECU #1 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 10
CATCOND1 = 15
CATCOMP2 = 00
CATCOND2 = 00
O2COMP1 = 30
O2COND1 = 35
O2COMP2 = 00
O2COND2 = 00
EGRCOMP = 50
EGRCOND = 55
AIRCOMP = 60
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The DUT indicates that the IPT for ECU #2 is 40 bytes and has the following values:
OBDCOND = 100
IGNCNTR = 105
CATCOMP1 = 00
CATCOND1 = 00
CATCOMP2 = 20
CATCOND2 = 25
O2COMP1 = 00
O2COND1 = 00
O2COMP2 = 40
O2COND2 = 45
EGRCOMP = 00
EGRCOND = 00
AIRCOMP = 00
AIRCOND = 00
EVAPCOND = 00
EVAPCOND = 00
SO2SCOMP1 = 00
SO2SCOND1 = 00
SO2SCOMP2 = 90
SO2SCOND2 = 95
Figure 245 - Verify an SAE J1850 PWM SID $09 IPT (INF$08, 40 bytes) request
This section details test cases that will verify the presentation attributes of the DUT.
These are general presentation tests, which are not specific to any OBD II protocol.
These presentation tests are specific to ISO 15765-4. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.
These presentation tests are specific to ISO 14230-4. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.3.13.
These presentation tests are specific to ISO 9141-2. Unless otherwise specified, all references to Electrical Connections,
ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.4.7.
These presentation tests are specific to SAE J1850 VPW. Unless otherwise specified, all references to Electrical
Connections, ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.5.7.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
These presentation tests are specific to SAE J1850 PWM. Unless otherwise specified, all references to Electrical
Connections, ECU Addresses, Messages, Message Timing, and pre-defined states will be as described in 5.4.6.7.
11. NOTES
A change bar (l) located in the left margin is for the convenience of the user in locating areas where technical revisions, not
editorial changes, have been made to the previous issue of this document. An (R) symbol to the left of the document title
indicates a complete revision of the document, including technical revisions. Change bars and (R) are not used in original
publications, nor in documents that contain editorial changes only.
A.1.1 General
Conformance testing specifies the tests required to be passed in order for external test equipment to be type approved as
“conforms to SAE J1978”. Only external test equipment that pass all these tests may be so labeled. External test equipment
shall support all the listed protocols (specified in ’Communication Protocols’ Clause of ISO 15031-4) as allowed by legislation
of the country where the equipment will be offered to the market. Equipment that pass all tests shall be labeled “Conforms
to SAE J1978” and shall list the protocols supported as shown in ‘Communication Protocols’ Clause of ISO 15031-4.
The external test equipment manufacturer may optimize the automatic determination of communication interface sequence
to only test for those protocols allowed by the legislation of the country (see ‘Automatic determination of communication
interface’ Clause of ISO 15031-4).
EXAMPLE: North American legislation only allows 500 Kbps data rate of ISO 15765-4 (CAN) although the standard also
specifies 250 Kbps. External test equipment manufacturers are allowed to only support 500 Kbps in the
software if the equipment with this software is offered to the North American market.
Validation of the conformance test is the responsibility of the equipment manufacturer and the equipment manufacturer may
elect to self-certify.
The tests in this clause, shall be performed successfully five (5) consecutive times, on each sample unit to be considered
passed.
Three (3) examples of at least production intent level external test equipment shall pass all these tests in order for a given
version of external test equipment hardware and software to be considered passed, and that the equipment manufacturer
shall ensure consistent quality of manufacture to meet the requirements of this document, to ensure consistent compatibility
between external test equipment and vehicle.
Any changes to the hardware or software used in an external test equipment for the functions described in this document
shall require a retest of these tests or an explanation from the external test equipment manufacturer as to why the change
shall not require a retest. Where an explanation is submitted in lieu of a retest due to a change, the organization originally
performing these tests shall determine whether the explanation is acceptable or whether a retest is required. Reasonable
normal engineering criteria shall be used when determining whether to accept an explanation.
For every product type which is labeled as conforming to, or compatible with the requirements of SAE J1978 OBD access
facilities, or other labeling to that effect, the manufacturer shall record:
a. clear indication of the versions of product hardware, software and protocols supported,
Both proper and improper response messages will be employed during these tests. Improper responses are those that have
incorrect header information, an incorrect Service Identifier, an incorrect PID, an incorrect length of the response message,
or an incorrect CRC or checksum. The external test equipment must ignore all improper response messages and perform
as if no response was received.
Situations involving multiple ECUs responding to a single request message, single ECUs responding with multiple response
messages to a single request message and multiple ECUs responding with multiple response messages to a single request
message will be tested.
The interval between the end of the request message and the beginning of the response message(s) will be varied from
0 ms up to the delay required to show a no response message indication on the external test equipment. This delay that
causes the no response message indication will be compared to the value defined in SAE J1979.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
The ability to obtain and report the results of the on-board system readiness tests shall be verified. The ability to report
which tests the vehicle supports and which have been completed shall be verified.
The requirements described in A.1.3 through A.1.7 (inclusive) shall be verified on each protocol specified in
’Communication Protocols’ Clause of ISO 15031-4.
When performing these tests, observation of the indications and displays provided to the user and the signals of each
protocol specified in ‘Communication Protocols’ Clause of ISO 15031-4 (bus + and bus -, K and L lines, if applicable) will
be the criteria for proper performance.
Testing shall be conducted at a temperature of 23 °C ± 5 °C and between 25 and 95% relative humidity.
Testing information and results must be made available to the buying public.
Items to be tested:
— automatic determination of interface and protocol type when the SAE J1962 connector is plugged into its mating
connector in the vehicle and/or OBD support is selected, where such a selection is necessary,
— that a test of all supported OBD communication interfaces is performed at least once per scan,
— that the interface contacts related to protocols not supported by the external test equipment are not activated during the
test cycle,
— that the scan of all interfaces continues until successful or until terminated by the user,
— that some indication is provided to the user that the scan of interfaces is being performed,
— that a failure to successfully find an OBD interface during a scan of all the possible interfaces is indicated to the user at
the completion of each and every scan,
— that when an OBD interface is successfully found, the external test equipment automatically prompts the user for
function selection,
— that the external test equipment provides and uses the facilities and/or messages specified in SAE J1979, ISO 9141-2,
SAE J1850, ISO 14230-4, ISO 15765-4, and SAE J2012,
— that the external test equipment does not exceed the polling rates specified in SAE J1979,
— that the external test equipment provides the proper bias for the K and L lines as specified in ISO 9141-2 and
ISO 14230-4,
— that the external test equipment performs the initialization tests according to ‘Automatic determination of communication
interface’ subclause of ISO 15031-4 such that the external test equipment supports the use of an idle message when
ISO 9141-2 and ISO 14230-4 are used.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
For unsupported interfaces it is only necessary to ensure that the specific contacts related to that protocol remain open
circuit and that no damage occurs to either the external test equipment or vehicle.
Confirm, using each supported protocol specified in ’Communication Protocols’ Clause of ISO 15031-4, that the external
test equipment automatically requests and correctly reports the results of the supported on-board system readiness tests.
Confirm, using each supported protocol specified in ’Communication Protocols’ Clause of ISO 15031-4:
— at the external test equipment offers all of the diagnostic facilities described in ’Required functions of external test
equipment’ Clause of ISO 15031-4,
Confirm, using each supported protocol specified in ’Communication Protocols’ Clause of ISO 15031-4:
a. That the user is able to select and display simultaneously at least two items from any one of:
1. available DTC's,
b. That the module ID's and the PID's or parameter names associated with all the items mentioned above can also be
displayed either (a) simultaneously with the displayed items, or (b) in some alternate method.
c. That the units-of-measurement information associated with all the possible current data items and freeze frame data
items are easily available either as a part of the data display, displayed separately, or otherwise available on or with the
external test equipment body itself.
d. That the external test equipment is able to handle multiple responses from the same module due to one request.
e. That the external test equipment is able to handle responses from multiple modules due to one request.
f. That the external test equipment is able to handle multiple responses from multiple modules due to one request.
g. That the external test equipment informs the user whenever multiple modules respond to a particular request.
Responses from multiple modules to a request are to be made available to the user as separate items for display.
h. That the external test equipment informs the user whenever multiple modules produce differing responses to a single
request.
The criteria for successfully passing this test is to navigate between all the items and observe the results.
Confirm, using each supported protocol specified in ’Communication Protocols’ Clause of ISO 15031-4:
— that the selection of the Clear Codes function incorporates a request to the user for confirmation,
— that both yes and no responses to the request to the user to confirm the selection of the clear codes function are
processed appropriately.
When performing this test, the presence or absence of DTCs shall be verified both before and after the clear codes function
is selected.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
When performing tests involving diagnostic messages, tests are to be made of the external test equipment's ability to handle
an immediate response, a slow response and a response delayed longer than the maximum allowed by each of the
protocols.
The external test equipment shall be able to process all responses that are received within the maximum time allowed by
each protocol and indicate a no response condition to the user when the response is delayed longer than the maximum
allowed by each protocol.
The external test equipment shall support the transmission of its node address as an in-frame-response during the
transmission of any response messages from modules on an SAE J1850 bus and shall be able to handle both the presence
and the absence of an in-frame-response during the external test equipment's transmission of request messages.
Confirm, using each supported protocol specified in ’Communication Protocols’ Clause of ISO 15031-4, that the capacitance
and impedance of the external test equipment, its connecting data cables and the diagnostic connector are within the limits
specified in SAE J1850, ISO 9141-2, ISO 14230-4, ISO 15765-4 and SAE J1962. Measurement of these parameters shall
be performed by a testing agency at their discretion following generally acceptable engineering standards.
Confirm, using each supported protocol specified in ‘Communication Protocols’ Clause of ISO 15031-4:
— that the external test equipment shall correctly operate throughout the voltage range specified in the ‘Vehicle battery
voltage support’ Clause of ISO 15031-4 and shall not require more than the maximum current specified in the ‘Vehicle
battery current consumption’ Clause of ISO 15031-4,
— that the external test equipment shall accept without causing damage the use of supply voltages of up to the maximum
survival voltage and survive reverse voltage specified in ‘Vehicle battery voltage support’ Clause of ISO 15031-4.
During other conformance tests, the voltage supplied to the external test equipment is to be varied throughout the specified
range and a check for continuous operation performed. Also, the supply current is to be compared with the limit specified.
Confirm, using each supported protocol specified in ‘Communication Protocols’ Clause of ISO 15031-4, that all the request
and response messages, as specified in ‘Network Access’ Clause of ISO 15031-4 are properly and appropriately used by
the external test equipment.
Verify that the external test equipment is able to display alphanumeric characters.
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
Verify that:
a. A user manual and/or HELP facility is available with the external test equipment;
5. how to determine the PID, item name and module ID of data returned for display,
7. how to obtain and display OBD emissions related test parameters and results as described in related documentation
for each protocol,
10. what current and freeze frame data items are available through OBD.
The external test equipment shall be tested for a HELP facility and/or the availability and coverage of a user manual.
The following table is intended to aid in the readers understanding of how the ISO 15031-4 Conformance Testing
requirements map onto SAE J1699-2 test cases. Please note that at the present time, SAE J1699-2 does not include test
cases for every requirement previously specified in ISO 15031-4 Conformance Testing. It is expected that this will be
corrected in subsequent publications of this document.
SAE INTERNATIONAL J1699®-2 SEP2017 Page 254 of 255
NO a) Verify that the user can select and display two items from any one of the following: DTCs, Current PIDs, Freeze Frame
PIDs, Test parameters and results
NO b) Modules ID's can also be displayed
NO c) Units of measure are available for PIDs
NO d) Handle multiple responses from the same module for a single request
NO e) Handle responses from multiple modules for a single request
NO f) Handle multiple responses from multiple modules for a single request
NO g) Informs user when multiple modules respond with each module response being a separate display item
A.1.5 NO h) Informs user when multiple modules produce differing responses to a single request
For each protocol:
NO Verify that clear codes include a user confirmation
NO Verify that a YES and NO confirmation are processed correctly
A.1.6 NO Verify that the presence or absence of DTC's shall be verified before and after the code clear function
For each protocol:
NO Verify the DUT can process Immediate, slow responses (< max.), and > max.
NO Verify that DUT transmits its node address as an IFR for response messages from vehicle on J1850
A.1.7 NO Verify that DUT can handle both the presence and absence of IFR from vehicle during request messages
SAE INTERNATIONAL J1699®-2 SEP2017 Page 255 of 255
ISO 15765-4: 7.2.2-7.2.3
ISO 14230-4: 7.3.2-7.3.3
ISO 9141-2: 7.4.2-7.4.3
J1850 VPW: 7.5.2-7.5.3
A.1.8 YES Verify the capacitance and impedance for DUT at diagnostic connector for all protocols J1850 PWM: 7.6.2-7.6.3
NO Verify DUT operation through specified voltage range
NO Verify DUT current draw through the specified voltage range
NO Verify DUT can survive maximum voltage
NO Verify DUT can survive reverse voltage
A.1.9 NO Check voltage and current draw during other tests
YES 9.1) Verify DUT correctly initializes the network 8.1.1
NO 9.2) Verify the DUT correctly handles no response
YES 9.3) Verify the DUT correctly handles multiple responses; LATER->inform user when multiple modules respond to same All tests that validate >2 ECUs
request; inform user when multiple module have different values for same data item; User allow to separately display
responses from multiple modules for same data item
YES 9.4) Verify DUT message structure is correct Throughout all tests
NO 9.5) Verify the DUT can continuously monitor and display DTCs (including the case where no DTCs are present)
YES 9.6[a]) Verify that DUT can obtain, convert, and display all ISO 15031-5 data. Throughout all tests
NO 9.6[b]) When current data is displayed, the DUT will continually request and display data. Where applicable, DUT will
indicate whether a test limit is a high limit or low limit and show test ID and component ID. The DUT shall allow user to
request services/parameters/Test IDs/etc. irrespective of whether the vehicle has indicated support for such items.
NO 9.7) Verify code clear with user confirmation before action is taken
NO 9.8.1) Verify display of readiness status immediately after connection
NO 9.8.2) Verify DUT indicates which readiness bits are supported and which have been completed.
NO 9.8.3) Verify DUT indicates MIL status and identifies which module(s) are commanding it on.
A.1.10 NO 9.9) Verify DUT support of StopCommunications service for ISO 14230-4 (Optional)
A.1.11 NO Verify DUT can display alphanumeric characters
Verify that there is a User Manual and/or HELP facility available with DUT that includes the following:
NO a) Parameter ID and Sevice IDs as described in ISO 15031-5
NO b) All abbreviations used by the DUT
NO c) How to select functions
NO d) How to select items for simultaneous display
NO e) How to determine the PID, item name and module ID of data returned for display
NO f) How to confirm the selection of the clear codes function
NO g) How to obtain and display OBD emissions-related test parameters and results for each protocol
NO h) How multiple responses from one request are indicated
NO i) How different responses to the same request are indicated
Downloaded from SAE International by Cummins Inc, Tuesday, June 27, 2023
A.1.12 NO j) What current and freeze frame data items are available through OBD