ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
This document specifies data link independent requirements of diagnostic services, which allow a diagnostic tester (client) to control diagnostic functions in an on-vehicle electronic control unit (ECU, server) such as an electronic fuel injection, automatic gearbox, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle.
It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission on the data link.
This document does not apply to non-diagnostic message transmission on the vehicle's communication data link between two electronic control units. However, this document does not restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange.
This document does not specify any implementation requirements.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$429.00 NZD
|
|
| HardCopy |
$473.00 NZD
|
|
| Networkable PDF |
Price varies
|
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
3 Terms and definitions
4 Symbols and abbreviated terms
5 Conventions
Figure 1 — The services and the protocol
6 Document overview
7 Application layer services
7.1 General
Figure 4 — Application layer service primitives – Unconfirmed service
Figure 4 — Application layer service primitives – Unconfirmed service
7.2 Format description of application layer services
7.3 Format description of service primitives
7.3.1 General definition
7.3.2 Service request and service indication primitives
7.3.3 Service response and service confirm primitives
7.3.3 Service response and service confirm primitives
7.3.4 Service request-confirm and service response-confirm primitives
7.4 Service data unit specification
7.4.1 Mandatory parameters
7.4.1.1 General definition
7.4.1.2 A_Mtype, application layer message type
7.4.1.3 A_SA, application layer source address
7.4.1.3 A_SA, application layer source address
7.4.1.4 A_TA, application layer target address
7.4.1.5 A_TA_Type, application layer target address type
7.4.1.5 A_TA_Type, application layer target address type
7.4.1.6 A_Result
7.4.1.7 A_Length
7.4.1.8 A_Data
7.4.2 Vehicle system requirements
7.4.3 Optional parameters - A_AE, application layer remote address
7.4.3 Optional parameters - A_AE, application layer remote address
8 Application layer protocol
8.1 General definition
8.2 A_PDU, application protocol data unit
8.2 A_PDU, application protocol data unit
8.3 A_PCI, application protocol control information
8.4 SI, service identifier
8.4 SI, service identifier
8.5 A_NR_SI, Negative response service identifier
8.6 Negative response/confirmation service primitive
8.6 Negative response/confirmation service primitive
8.7 Server response implementation rules
8.7.1 General definitions
8.7.2 General server response behaviour
8.7.3 Request message with SubFunction parameter and server response behaviour
8.7.3.1 General server response behaviour for request messages with SubFunction parameter
8.7.3 Request message with SubFunction parameter and server response behaviour
8.7.3.1 General server response behaviour for request messages with SubFunction parameter
8.7.3.2 Physically addressed client request message
8.7.3.2 Physically addressed client request message
8.7.3.3 Functionally addressed client request message
8.7.4 Request message without SubFunction parameter and server response behaviour
8.7.4.1 General server response behaviour for request messages without SubFunction parameter
8.7.4.2 Physically addressed client request message
8.7.4.3 Functionally addressed client request message
8.7.5 Pseudo code example of server response behaviour
8.7.6 Multiple concurrent request messages with physical and functional addressing
8.7.6 Multiple concurrent request messages with physical and functional addressing
9 Service description conventions
9.1 Service description
Table 8 — A_PDU parameter conventions
9.2 Request message
9.2.1 Request message definition
Table 10 — Request A_PDU definition without SubFunction
9.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 11 — SubFunction parameter structure
Table 12 — Request message SubFunction parameter definition
9.2.3 Request message data-parameter definition
9.3 Positive response message
9.3.1 Positive response message definition
9.3.2 Positive response message data-parameter definition
9.4 Supported negative response codes (NRC_)
Table 18 — Supported negative response codes
9.5 Message flow examples
Table 19 — Request message flow example
10 Diagnostic and communication management functional unit
10.1 Overview
Table 22 — Diagnostic and communication management functional unit
10.2 DiagnosticSessionControl (1016) service
10.2.1 Service description
10.2.2 Request message
10.2.2.1 Request message definition
10.2.2 Request message
10.2.2.1 Request message definition
10.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
10.2.2.3 Request message data-parameter definition
10.2.3 Positive response message
10.2.3.1 Positive response message definition
10.2.3.2 Positive response message data-parameter definition
Table 28 — sessionParameterRecord definition
10.2.4 Supported negative response codes (NRC_)
10.2.5 Message flow example(s) DiagnosticSessionControl – Start programmingSession
10.3 ECUReset (1116) service
10.3.1 Service description
10.3.2 Request message
10.3.2.1 Request message definition
10.3.2.2 Request message SubFunction Parameter $Level (LEV_) definition
Table 34 — Request message SubFunction parameter definition
10.3.2.3 Request message data-parameter definition
10.3.3 Positive response message
10.3.3.1 Positive response message definition
Table 35 — Positive response message definition
10.3.3.2 Positive response message data-parameter definition
Table 36 — Response message data-parameter definition
10.3.4 Supported negative response codes (NRC_)
Table 37 — Supported negative response codes
10.3.5 Message flow example ECUReset
10.3.5 Message flow example ECUReset
10.4 SecurityAccess (2716) service
10.4.1 Service description
10.4.2 Request message
10.4.2.1 Request message definition
10.4.2 Request message
10.4.2.1 Request message definition
Table 41 — Request message definition - SubFunction = sendKey
10.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 42 — Request message SubFunction parameter definition
Table 42 — Request message SubFunction parameter definition
10.4.2.3 Request message data-parameter definition
10.4.3 Positive response message
10.4.3.1 Positive response message definition
Table 44 — Positive response message definition
10.4.3 Positive response message
10.4.3.1 Positive response message definition
Table 44 — Positive response message definition
10.4.3.2 Positive response message data-parameter definition
Table 45 — Response message data-parameter definition
10.4.4 Supported negative response codes (NRC_)
10.4.5 Message flow example(s) SecurityAccess
10.4.5.1 Assumptions
10.4.5.2 Example #1 - server is in a “locked” state
10.4.5.2.1 Step #1: Request the Seed
10.4.5.2.2 Step #2: Send the Key
10.4.5.3 Example #2 - server is in an “unlocked” state
10.4.5.3.1 Step #1: Request the Seed
Table 52 — SecurityAccess positive response message flow example #2 – step #2
Table 52 — SecurityAccess positive response message flow example #2 – step #2
10.5 CommunicationControl (2816) service
10.5.1 Service description
10.5.2 Request message
10.5.2.1 Request message definition
Table 53 — Request message definition
10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 — Request message SubFunction parameter definition
10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 — Request message SubFunction parameter definition
10.5.2.3 Request message data-parameter definition
Table 55 — Request message data-parameter definition
10.5.3 Positive response message
10.5.3.1 Positive response message definition
Table 56 — Positive response message definition
10.5.3.2 Positive response message data-parameter definition
Table 57 — Response message data-parameter definition
10.5.4 Supported negative response codes (NRC_)
Table 58 — Supported negative response codes
10.5.5 Message flow example CommunicationControl (disable transmission of network management messages)
Table 60 — CommunicationControl positive response message flow example
10.5.6 Message flow example CommunicationControl (switch a remote network into the diagnostic-only scheduling mode where the node with address 000A16 is connected to)
Table 61 — CommunicationControl request message flow example
10.5.7 Message flow example CommunicationControl (switch to application scheduling mode with enhanced address information, the node 000A16, which is connected to a sub-network, is addressed)
Table 63 — CommunicationControl request message flow example
Table 64 — CommunicationControl positive response message flow example
10.6 Authentication (2916) service
10.6.1 Service overview
10.6.2 Authentication with PKI Certificate Exchange (APCE)
10.6.2 Authentication with PKI Certificate Exchange (APCE)
10.6.3 Authentication with Challenge-Response (ACR)
Figure 10 — Authentication sequence with Challenge-Response (ACR)
10.6.4 Common requirements
10.6.5 Request message
10.6.5.1 Request message definition
10.6.5 Request message
10.6.5.1 Request message definition
Table 67 — Request message definition - SubFunction = verifyCertificateBidirectional
Table 69 — Request message definition - SubFunction = transmitCertificate
Table 70 — Request message definition - SubFunction = requestChallengeForAuthentication
Table 71 — Request message definition - SubFunction = verifyProofOfOwnershipUnidirectional
Table 72 — Request message definition - SubFunction = verifyProofOfOwnershipBidirectional
Table 72 — Request message definition - SubFunction = verifyProofOfOwnershipBidirectional
Table 73 — Request message definition - SubFunction = authenticationConfiguration
10.6.5.2 Request message SubFunction parameter $Level (LEV_) definition
Table 74 — Request message SubFunction parameter definition
10.6.5.3 Request message data-parameter definition
10.6.6 Positive response message
10.6.6.1 Positive response message definition
10.6.6 Positive response message
10.6.6.1 Positive response message definition
Table 76 — Response message definition - SubFunction = deAuthenticate
Table 78 — Response message definition - SubFunction = verifyCertificateBidirectional
Table 78 — Response message definition - SubFunction = verifyCertificateBidirectional
Table 81 — Response message definition - SubFunction = requestChallengeForAuthentication
Table 83 — Response message definition - SubFunction = verifyProofOfOwnershipBidirectional
10.6.6.2 Positive response message data-parameter definition
10.6.7 Supported negative response codes (NRC_)
10.6.7 Supported negative response codes (NRC_)
10.6.8 Message flow example(s) Authentication
10.6.8.1 Example #1 - Unidirectional Authentication with PKI Certificate Exchange without session key establishment (happy path)
10.6.8.1.1 Assumptions
10.6.8.1.2 Step #1: Request Authentication Configuration
Table 88 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment positive response message flow example #1 - step #1
10.6.8.1.3 Step #2: Send Certificate Client
Table 89 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 – step #2
10.6.8.1.4 Step #3: Validate the Proof of Ownership
Table 91 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 - step #3
Table 92 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment positive response message flow example #1 - step #3
10.6.8.1.5 Step #4: Attempt to send a random secured service
Table 94 — ECUReset response message after successful Authentication request message attempt – example #1 - step #4
10.6.8.2 Example #2 - Unidirectional Authentication with PKI Certificate Exchange without session key establishment (failure path)
10.6.8.2.1 Assumptions
10.6.8.2.2 Step #1: Send Certificate Client
Table 95 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #2 – step #1
10.6.8.2.3 Step #2: Attempt to send a random secured service
Table 97 — ECUReset request message after failed Authentication request message attempt – example #2 - step #2
Table 98 — ECUReset response message after failed Authentication request message attempt – example #2 - step #2
10.6.8.3 Example #3 – Transmit Certificate after Authentication with PKI Certificate Exchange (happy path)
10.6.8.3.1 Assumptions
10.6.8.3.2 Step #1: Send Certificate
Table 99 — Transmit Certificate request message flow example #3 - step #1
Table 100 — Transmit Certificate positive response message flow example #3 - step #1
Table 100 — Transmit Certificate positive response message flow example #3 - step #1
10.6.8.4 Example #4 - Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment (happy path)
10.6.8.4.1 Assumptions
10.6.8.4.2 Step #1: Request Authentication Configuration
10.6.8.4.3 Step #2: Request the Challenge
10.6.8.4.4 Step #3: Validate the Proof of Ownership
Table 105 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #4 - step #3
10.6.8.5 Example #5 - Unidirectional Authentication using Challenge-Response (ACR) with asymmetric cryptography without session key establishment (failure path)
10.6.8.5.1 Assumptions
10.6.8.5.2 Step #1: Request the Challenge
Table 107 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 - step #1
10.6.8.5.3 Step #2: Validate the Proof of Ownership
Table 109 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 - step #2
Table 110 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment negative response message flow example #5 - step #2
10.6.8.6 Example #6 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment (happy path)
10.6.8.6.1 Assumptions
10.6.8.6.2 Step #1: Request challenge for Authentication
Table 111 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 - step #1
Table 112 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #6 - step #1
10.6.8.6.3 Step #2: Verify Proof of Ownership Unidirectional
Table 113 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 - step #2
Table 114 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #6 - step #2
10.6.8.7 Example #7 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment (failure path)
10.6.8.7.1 Assumptions
10.6.8.7.2 Step #1: Request challenge for Authentication
Table 115 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 - step #1
Table 115 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 - step #1
Table 116 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #7 - step #1
10.6.8.7.3 Step #2: Verify Proof of Ownership Unidirectional
Table 118 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment negative response message flow example #7 - step #2
10.7 TesterPresent (3E16) service
10.7.1 Service description
10.7 TesterPresent (3E16) service
10.7.1 Service description
10.7.2 Request message
10.7.2.1 Request message definition
Table 119 — Request message definition
10.7.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 120 — Request message SubFunction parameter definition
10.7.2.3 Request message data-parameter definition
10.7.3 Positive response message
10.7.3.1 Positive response message definition
Table 121 — Positive response message definition
10.7.3.2 Positive response message data-parameter definition
Table 121 — Positive response message definition
10.7.3.2 Positive response message data-parameter definition
Table 122 — Response message data-parameter definition
10.7.4 Supported negative response codes (NRC_)
Table 123 — Supported negative response codes
10.7.5 Message flow example(s) TesterPresent
10.7.5.1 Example #1 - TesterPresent (suppressPosRspMsgIndicationBit = FALSE)
Table 124 — TesterPresent request message flow example #1
Table 125 — TesterPresent positive response message flow example #1
10.7.5.2 Example #2 - TesterPresent (suppressPosRspMsgIndicationBit = TRUE)
Table 126 — TesterPresent request message flow example #2
10.8 ControlDTCSetting (8516) service
10.8.1 Service description
10.8.2 Request message
10.8.2.1 Request message definition
10.8.2 Request message
10.8.2.1 Request message definition
Table 127 — Request message definition
10.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 128 — Request message SubFunction parameter definition
10.8.2.3 Request message data-parameter definition
Table 129 — Request message data-parameter definition
Table 129 — Request message data-parameter definition
10.8.3 Positive response message
10.8.3.1 Positive response message definition
Table 130 — Positive response message definition
10.8.3.2 Positive response message data-parameter definition
Table 131 — Response message data-parameter definition
10.8.4 Supported negative response codes (NRC_)
Table 132 — Supported negative response codes
10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 - ControlDTCSetting (DTCSettingType = off)
Table 133 — ControlDTCSetting request message flow example #1
10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 - ControlDTCSetting (DTCSettingType = off)
Table 133 — ControlDTCSetting request message flow example #1
Table 134 — ControlDTCSetting positive response message flow example #1
10.8.5.2 Example #2 - ControlDTCSetting ( DTCSettingType = on)
Table 135 — ControlDTCSetting request message flow example #2
Table 136 — ControlDTCSetting positive response message flow example #2
10.9 ResponseOnEvent (8616) service
10.9.1 Service description
Figure 13 — Sampling of data identifiers
Table 137 — Recommended services to be used with the ResponseOnEvent service
10.9.2 Request message
10.9.2.1 Request message definition
10.9.2.2 Request message SubFunction Parameter $Level (LEV_) Definition
10.9.2.2.1 ResponseOnEvent request message SubFunction Parameter definition
10.9.2.2.2 Detailed request message SubFunction onDTCStatusChange parameters specification
10.9.2.2.3 Detailed request message SubFunction reportMostRecentDtcOnStatusChange parameters specification
10.9.2.2.4 Detailed request message SubFunction reportDTCRecordInformationOnDtcStatusChange parameters specification
10.9.2.2.5 Detailed request message SubFunction onChangeOfDataIdentifier parameters specification
10.9.2.2.6 Detailed request message SubFunction onComparisonOfValues parameters specification
Table 143 — Localization of value 16 bit bitfield parameter definition
10.9.2.3 Request message data-parameter definition
10.9.3 Positive response message
10.9.3.1 Positive response message definition
10.9.3.2 Positive response message data-parameter definition
Table 147 — Response message data-parameter definition
10.9.4 Supported negative response codes (NRC_)
Table 148 — Supported negative response codes
10.9.4 Supported negative response codes (NRC_)
Table 148 — Supported negative response codes
10.9.5 Message flow example(s) ResponseOnEvent
10.9.5.1 Assumptions
10.9.5.2 Example #1 - ResponseOnEvent (finite event window)
Table 150 — ResponseOnEvent initial positive response message flow example #1
Table 151 — Start of ResponseOnEvent request message flow example #1
Table 153 — ReadDTCInformation positive response message flow example #1
Table 156 — ResponseOnEvent final positive response message flow example #1
Figure 17 — Finite event window - multiple events during active event window
10.9.5.3 Example #2 - ResponseOnEvent (infinite event window)
Table 157 — ResponseOnEvent request message flow example #2
Table 157 — ResponseOnEvent request message flow example #2
Table 158 — ResponseOnEvent initial positive response message flow example #2
Table 159 — Start of ResponseOnEvent request message flow example #2
Table 160 — ResponseOnEvent positive response message flow example #2
Table 161 — ReadDTCInformation positive response message flow example #2
10.9.5.4 Example #3 - ResponseOnEvent (infinite event window) – SubFunction parameter “onComparisonOfValues”
10.9.5.4 Example #3 - ResponseOnEvent (infinite event window) – SubFunction parameter “onComparisonOfValues”
Table 162 — ResponseOnEvent request message example #3
Table 162 — ResponseOnEvent request message example #3
Table 163 — ReadDataByIdentifier positive response message example #3
10.9.5.5 Example #4 - ResponseOnEvent request message (reportMostRecentDtcOnStatusChange)
Table 164 — ResponseOnEvent request message flow example #4
Table 165 — ReadDTCInformation positive response message flow example #4
10.9.5.6 Example #5 - ResponseOnEvent request message (reportDTCRecordInformationOnDtcStatusChange)
Table 166 — ResponseOnEvent request message flow example #4
Table 167 — ReadDTCInformation positive response message flow example #1
Table 167 — ReadDTCInformation positive response message flow example #1
10.10 LinkControl (8716) service
10.10.1 Service description
10.10.2 Request message
10.10.2.1 Request message definition
Table 169 — Request message definition (linkControlType = verifyModeTransitionWithSpecificParameter)
Table 170 — Request message definition (linkControlType = transitionMode)
10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 — Request message SubFunction parameter definition
10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 — Request message SubFunction parameter definition
10.10.2.3 Request message data-parameter definition
10.10.3 Positive response message
10.10.3.1 Positive response message definition
10.10.3 Positive response message
10.10.3.1 Positive response message definition
10.10.3.2 Positive response message data-parameter definition
Table 174 — Response message data-parameter definition
10.10.4 Supported negative response codes (NRC_)
Table 175 — Supported negative response codes
10.10.5 Message flow example(s) LinkControl
10.10.5.1 Example #1 - Transition baudrate to fixed baudrate (PC baudrate 115,2 kBit/s)
10.10.5.1.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 176 — LinkControl request message flow example #1 - step #1
10.10.5 Message flow example(s) LinkControl
10.10.5.1 Example #1 - Transition baudrate to fixed baudrate (PC baudrate 115,2 kBit/s)
10.10.5.1.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 176 — LinkControl request message flow example #1 - step #1
Table 177 — LinkControl positive response message flow example #1 - step #1
10.10.5.1.2 Step#2: Transition the baudrate
Table 178 — LinkControl request message flow example #1 - step #2
10.10.5.2 Example #2 - Transition baudrate to specific baudrate (150 kBit/s)
10.10.5.2.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 179 — LinkControl request message flow example #2 - step #1
Table 180 — LinkControl positive response message flow example #2 - step #1
10.10.5.2.2 Step#2: Transition the baudrate
Table 181 — LinkControl request message flow example #2 - step #2
10.10.5.3 Example #3 - Transition FlexRay cycle design to 'programming'
10.10.5.3.1 Step#1: Verify if all criteria are met for a scheduler switch
Table 182 — LinkControl request message flow example #3 - step #1
Table 183 — LinkControl positive response message flow example #3 - step #1
10.10.5.3.2 Step#2: Transition to programming scheduler
Table 184 — LinkControl request message flow example #3 - step #2
11 Data transmission functional unit
11.1 Overview
Table 185 — Data Transmission functional unit
11.2 ReadDataByIdentifier (2216) service
11.2.1 Service description
11.2.2 Request message
11.2.2.1 Request message definition
Table 186 — Request message definition
11.2.2.2 Request message SubFunction parameter $Level (LEV_) Definition
11.2.2.3 Request message data-parameter definition
Table 187 — Request message data-parameter definition
11.2.2.2 Request message SubFunction parameter $Level (LEV_) Definition
11.2.2.3 Request message data-parameter definition
Table 187 — Request message data-parameter definition
11.2.3 Positive response message
11.2.3.1 Positive response message definition
Table 188 — Positive response message definition
11.2.3.2 Positive response message data-parameter definition
Table 189 — Response message data-parameter definition
11.2.4 Supported negative response codes (NRC_)
Table 190 — Supported negative response codes
Figure 20 — NRC handling for ReadDataByIdentifier service
11.2.5 Message flow example ReadDataByIdentifier
11.2.5.1 Assumptions
11.2.5 Message flow example ReadDataByIdentifier
11.2.5.1 Assumptions
11.2.5.2 Example #1: read single dataIdentifier F19016 (VIN number)
Table 192 — ReadDataByIdentifier positive response message flow example #1
11.2.5.3 Example #2: Read multiple dataIdentifiers 010A16 and 011016
Table 194 — ReadDataByIdentifier positive response message flow example #2
11.3 ReadMemoryByAddress (2316) service
11.3.1 Service description
11.3.2 Request message
11.3.2.1 Request message definition
11.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.3.2.3 Request message data-parameter definition
11.3.3 Positive response message
11.3.3.1 Positive response message definition
11.3.3 Positive response message
11.3.3.1 Positive response message definition
11.3.3.2 Positive response message data-parameter definition
Table 198 — Response message data-parameter definition
11.3.4 Supported negative response codes (NRC_)
Table 199 — Supported negative response codes
11.3.5 Message flow example ReadMemoryByAddress
11.3.5.1 Assumptions
11.3.5.2 Example #1: ReadMemoryByAddress - 4-byte (32-bit) addressing
Table 201 — ReadMemoryByAddress positive response message flow example #1
11.3.5.3 Example #2: ReadMemoryByAddress - 2-byte (16-bit) addressing.
11.3.5.4 Example #3: ReadMemoryByAddress, 3-byte (24-bit) addressing
11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description
11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description
11.4.2 Request message
11.4.2.1 Request message definition
Table 206 — Request message definition
11.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.4.2.3 Request message data-parameter definition
Table 207 — Request message data-parameter definition
11.4.3 Positive response message
11.4.3.1 Positive response message definition
Table 208 — Positive response message definition
11.4.3.2 Positive response message data-parameter definition
Table 209 — Response message data-parameter definition
11.4.4 Supported negative response codes (NRC_)
Table 210 — Supported negative response codes
11.4.5 Message flow example ReadScalingDataByIdentifier
11.4.5.1 Assumptions
11.4.5.2 Example #1: readScalingDataByIdentifier wth dataIdentifier F19016 (VIN number)
Table 211 — ReadScalingDataByIdentifier request message flow example #1
11.4.5.2 Example #1: readScalingDataByIdentifier wth dataIdentifier F19016 (VIN number)
Table 211 — ReadScalingDataByIdentifier request message flow example #1
Table 212 — ReadScalingDataByIdentifier positive response message flow example #1
11.4.5.3 Example #2: readScalingDataByIdentifier wth dataIdentifier 010516 (Vehicle Speed)
Table 214 — ReadScalingDataByIdentifier positive response message flow example #2
11.4.5.4 Example #3: readScalingDataByIdentifier wth dataIdentifier 096716
Table 215 — Example data definition
Table 216 — ReadScalingDataByIdentifier request message flow example #3
Table 216 — ReadScalingDataByIdentifier request message flow example #3
Table 217 — ReadScalingDataByIdentifier positive response message flow example #3
11.5 ReadDataByPeriodicIdentifier (2A16) service
11.5.1 Service description
11.5.2 Request message
11.5.2.1 Request message definition
11.5.2 Request message
11.5.2.1 Request message definition
11.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.5.2.3 Request message data-parameter definition
Table 219 — Request message data-parameter definition
11.5.3 Positive response message
11.5.3.1 Positive response message definition
Table 220 — Positive response message definition
Table 221 — Periodic data response message data definition
Table 221 — Periodic data response message data definition
11.5.3.2 Positive response message data-parameter definition
Table 222 — Periodic message data-parameter definition
11.5.4 Supported negative response codes (NRC_)
Table 223 — Supported negative response codes
Figure 23 — NRC handling for ReadDataByPeriodicIdentifier service
11.5.5 Message flow example ReadDataByPeriodicIdentifier
11.5.5.1 General assumptions
11.5.5 Message flow example ReadDataByPeriodicIdentifier
11.5.5.1 General assumptions
11.5.5.2 Example #1 - Read multiple periodicDataIdentifiers E316 and 2416 at medium rate
11.5.5.2.1 Assumptions
11.5.5.2.2 Step #1: Request periodic transmission of the periodicDataIdentifiers
Table 224 — ReadDataByPeriodicIdentifier request message flow example – step #1
Table 225 — ReadDataByPeriodicIdentifier initial positive response message flow example – step #1
Table 226 — ReadDataByPeriodicIdentifier subsequent positive response message #1 flows – step #1
Table 227 — ReadDataByPeriodicIdentifier subsequent positive response message #2 flows – step #1
11.5.5.2.3 Step #2: Stop the transmission of the periodicDataIdentifiers
Table 228 — ReadDataByIdentifier request message flow example – step #2
Table 229 — ReadDataByIdentifier positive response message flow example – step #2
11.5.5.3 Example #2 - Graphical and tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.3.1 ReadDataByPeriodicIdentifier example overview
11.5.5.3.2 Example #2 – Read multiple periodicDataIdentifiers E316 and 2416 at medium rate
Table 231 — Example #2: Periodic scheduler table for scheduler type 2
11.5.5.4 Example #3 - Graphical and tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.4.1 ReadDataByPeriodicIdentifier example overview
11.5.5.4.2 Read multiple periodicDataIdentifiers at different periodic rates
Table 232 — Example #3: Periodic scheduler table for scheduler type 1
Table 232 — Example #3: Periodic scheduler table for scheduler type 1
11.5.5.5 Example #4 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.5 Example #4 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.6 Example #5 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.6 Example #5 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
Table 235 — Example #5: Periodic scheduler table
11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description
11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description
11.6.2 Request message
11.6.2.1 Request message definition
Table 236 — Request message definition - SubFunction = defineByIdentifier
Table 237 — Request message definition - SubFunction = defineByMemoryAddress
Table 237 — Request message definition - SubFunction = defineByMemoryAddress
11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 — Request message SubFunction parameter definition
11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 — Request message SubFunction parameter definition
11.6.2.3 Request message data-parameter definition
11.6.3 Positive response message
11.6.3.1 Positive response message definition
Table 241 — Positive response message definition
11.6.3.2 Positive response message data-parameter definition
Table 242 — Response message data-parameter definition
11.6.4 Supported negative response codes (NRC_)
Table 243 — Supported negative response codes
11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions
11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions
Table 244 — Composite data blocks - DataIdentifier definitions
Table 245 — Elemental data records - DID definitions
Table 246 — Memory data records - Memory address definitions
11.6.5.2 Example #1: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 247 — DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #1
Table 248 — DynamicallyDefineDataIdentifier positive response DDDDI F30116 message flow example #1
Table 249 — ReadDataByIdentifier request DDDDI F30116 message flow example #1
11.6.5.3 Example #2: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 251 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #2
Table 253 — ReadDataByIdentifier request DDDDI F30216 message flow example #2
11.6.5.4 Example #3: DynamicallyDefineDataIdentifier, SubFunction = defineByMemoryAddress
Table 255 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3
Table 255 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3
Table 257 — ReadDataByIdentifier request DDDDI F30216 message flow example #3
Table 258 — ReadDataByIdentifier positive response DDDDI F30216 message flow example #3
11.6.5.5 Example #4: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 259 — DynamicallyDefineDataIdentifier request DDDDI F2E716 message flow example #4
Table 260 — DynamicallyDefineDataIdentifier positive response DDDDI F2E716 message flow example #4
Table 262 — ReadDataByPeriodicIdentifier initial positive message flow example #4
Table 263 — ReadDataByPeriodicIdentifier periodic data response #1 DDDDI F2E716 message flow example #4
Table 264 — ReadDataByPeriodicIdentifier periodic data response #n DDDDI F2E716 message flow example #4
11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 — DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5
11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 — DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5
Table 266 — DynamicallyDefineDataIdentifier positive response clear DDDDI F30316 message flow example #5
11.6.5.7 Example #6: DynamicallyDefineDataIdentifier, concatenation of definitions (defineByIdentifier/defineByAddress)
11.6.5.7.1 Step #1: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier (1 st portion)
Table 267 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier)
Table 267 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier)
Table 268 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6 definition of first portion (defineByIdentifier)
11.6.5.7.2 Step #2: DynamicallyDefineDataIdentifier, SubFunction = defineByMemoryAddress (2 nd portion)
Table 269 — DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #6 definition of 2nd portion (defineByMemoryAddress)
Table 270 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.3 Step #3: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier (3 rd portion)
Table 271 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 3rd portion (defineByIdentifier)
Table 272 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.4 Step #4: ReadDataByIdentifier - dataIdentifier = DDDDI F30116
Table 273 — ReadDataByIdentifier request DDDDI F30116 message flow example #6
Table 274 — ReadDataByIdentifier positive response DDDDI F30116 message flow example #6
11.6.5.7.5 Step #5: DynamicallyDefineDataIdentifier - clear definition of DDDDI F30116
Table 275 — DynamicallyDefineDataIdentifier request clear DDDDI F30116 message flow example #6
Table 276 — DynamicallyDefineDataIdentifier positive response clear DDDDI F30116 message flow example #6
11.7 WriteDataByIdentifier (2E16) service
11.7.1 Service description
11.7.2 Request message
11.7.2.1 Request message definition
Table 277 — Request message definition
11.7.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.7.2.3 Request message data-parameter definition
Table 278 — Request message data-parameter definition
11.7.3 Positive response message
11.7.3.1 Positive response message definition
Table 279 — Positive response message definition
11.7.3.2 Positive response message data-parameter definition
Table 280 — Response message data-parameter definition
11.7.4 Supported negative response codes (NRC_)
Table 281 — Supported negative response codes
11.7.4 Supported negative response codes (NRC_)
Table 281 — Supported negative response codes
Figure 26 — NRC handling for WriteDataByIdentifier service
11.7.5 Message flow example WriteDataByIdentifier
11.7.5.1 Assumptions
11.7.5.2 Example #1: write dataIdentifier F19016 (VIN)
11.8 WriteMemoryByAddress (3D16) service
11.8.1 Service description
11.8.2 Request message
11.8.2.1 Request message definition
Table 284 — Request message definition
11.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.8.2.3 Request message data-parameter definition
Table 285 — Request message data-parameter definition
11.8.3 Positive response message
11.8.3.1 Positive response message definition
Table 286 — Positive response message definition
11.8.3.2 Positive response message data-parameter definition
Table 287 — Response message data-parameter definition
11.8.3.2 Positive response message data-parameter definition
Table 287 — Response message data-parameter definition
11.8.4 Supported negative response codes (NRC_)
Table 288 — Supported negative response codes
Figure 27 — NRC handling for WriteMemoryByAddress service
11.8.5 Message flow example WriteMemoryByAddress
11.8.5.1 Assumptions
11.8.5.2 Example #1: WriteMemoryByAddress, 2-byte (16-bit) addressing
11.8.5 Message flow example WriteMemoryByAddress
11.8.5.1 Assumptions
11.8.5.2 Example #1: WriteMemoryByAddress, 2-byte (16-bit) addressing
Table 289 — WriteMemoryByAddress request message flow example #1
Table 290 — WriteMemoryByAddress positive response message flow example #1
11.8.5.3 Example #2: WriteMemoryByAddress, 3-byte (24-bit) addressing
Table 291 — WriteMemoryByAddress request message flow example #2
Table 292 — WriteMemoryByAddress positive response message flow example #2
11.8.5.4 Example #3: WriteMemoryByAddress, 4-byte (32-bit) addressing
Table 293 — WriteMemoryByAddress request message flow example #3
Table 294 — WriteMemoryByAddress positive response message flow example #3
12 Stored data transmission functional unit
12.1 Overview
Table 295 — Stored data transmission functional unit
12.2 ClearDiagnosticInformation (1416) service
12.2.1 Service description
12.2.2 Request message
12.2.2.1 Request message definition
12.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
12.2.2.3 Request message data-parameter definition
Table 297 — Request message data-parameter definition
12.2.3 Positive response message
12.2.3.1 Positive response message definition
12.2.3.2 Positive response message data-parameter definition
12.2.4 Supported negative response codes (NRC_)
Table 299 — Supported negative response codes
12.2.5 Message flow example ClearDiagnosticInformation
Table 301 — ClearDiagnosticInformation positive response message flow example #1
12.3 ReadDTCInformation (1916) service
12.3.1 Service description
12.3.1.1 General description
12.3.1.2 Retrieving the number of DTCs that match a client defined status mask (SubFunction = 0116 reportNumberOfDTCByStatusMask)
12.3.1.3 Retrieving the list of DTCs that match a client defined status mask (SubFunction = 0216 reportDTCByStatusMask)
12.3.1.4 Retrieving DTCSnapshot record identification (SubFunction = 0316 reportDTCSnapshotIdentification)
12.3.1.5 Retrieving DTCSnapshot record data for a client defined DTC mask (SubFunction = 0416 reportDTCSnapshotRecordByDTCNumber)
12.3.1.6 Retrieving DTCStoredData record data for a client defined record number (SubFunction = 0516 reportDTCStoredDataByRecordNumber)
12.3.1.7 Retrieving DTCExtendedData record data for a client defined DTC mask and a client defined DTCExtendedData record number (SubFunction = 0616 reportDTCExtDataRecordByDTCNumber)
12.3.1.8 Retrieving the number of DTCs that match a client defined severity mask record (SubFunction = 0716 reportNumberOfDTCBySeverityMaskRecord)
12.3.1.9 Retrieving severity and functional unit information that match a client defined severity mask record (SubFunction = 0816 reportDTCBySeverityMaskRecord)
12.3.1.10 Retrieving severity and functional unit information for a client defined DTC (SubFunction = 0916 reportSeverityInformationOfDTC)
12.3.1.10 Retrieving severity and functional unit information for a client defined DTC (SubFunction = 0916 reportSeverityInformationOfDTC)
12.3.1.11 Retrieving the status of all DTCs supported by the server (SubFunction = 0A16 reportSupportedDTC)
12.3.1.12 Retrieving the first/most recent failed DTC (SubFunction = 0B16 reportFirstTestFailedDTC, SubFunction = 0D16 reportMostRecentTestFailedDTC)
12.3.1.13 Retrieving the first/most recently detected confirmed DTC (SubFunction = 0C16 reportFirstConfirmedDTC,SubFunction = 0E16 reportMostRecentConfirmedDTC)
12.3.1.14 Retrieving a list of "prefailed" DTC status (SubFunction = 1416 reportDTCFaultDetection-Counter)
12.3.1.15 Retrieving a list of DTCs with "permanent DTC" status (SubFunction = 1516 reportDTCWithPermanentStatus)
12.3.1.16 Retrieving DTCExtendedData record data for a client defined DTCExtendedData record number (SubFunction = 1616 reportDTCExtDataRecordByRecordNumber)
12.3.1.17 Retrieving the list of DTCs out of the server's user defined DTC memory that match a client defined DTC status mask (SubFunction = 1716 reportUserDefMemoryDTCByStatusMask)
12.3.1.17 Retrieving the list of DTCs out of the server's user defined DTC memory that match a client defined DTC status mask (SubFunction = 1716 reportUserDefMemoryDTCByStatusMask)
12.3.1.18 Retrieving user defined memory DTCSnapshot record data for a client defined DTC mask and a client defined DTCSnapshotNumber out of the DTC user defined memory (SubFunction = 1816 reportUserDefMemoryDTCSnapshotRecordByDTCNumber)
12.3.1.19 Retrieving user defined memory DTCExtendedData record data for a client defined DTC mask and a client defined DTCExtendedData record number out of the DTC memory (SubFunction = 1916 reportUserDefMemoryDTCExtDataRecordByDTCNumber)
12.3.1.20 Retrieving the list of all DTCs that supports an specific DTCExtendedDataRecord (SubFunction = 1A16 reportSupportedDTCExtDataRecord)
12.3.1.21 Retrieving the list of VOBD DTCs from a functional group that match a client defined status mask (SubFunction = 4216 reportWWHOBDDTCByMaskRecord)
12.3.1.22 Retrieving a list of VOBD DTCs with "permanent DTC" status (SubFunction = 5516 reportWWHOBDDTCWithPermanentStatus)
12.3.1.23 Retrieve DTC information for a client defined DTCReadinessGroupIdentifier (SubFunction = 5616 reportDTCInformationByDTCReadinessGroupIdentifier)
12.3.2 Request message
12.3.2.1 Request message definition
Table 305 — Request message definition - SubFunction = reportDTCExtDataRecordByDTCNumber
Table 306 — Request message definition - SubFunction = reportNumberOfDTCBySeverityMaskRecord, reportDTCSeverityInformation
Table 307 — Request message definition - SubFunction = reportSeverityInformationOfDTC
Table 308 — Request message definition - SubFunction = reportSupportedDTC, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCFaultDetectionCounter, reportDTCWithPermanentStatus
Table 309 — Request message definition - SubFunction = reportDTCExtDataRecordByRecordNumber
Table 310 — Request message definition - SubFunction = reportUserDefMemoryDTCByStatusMask
Table 311 — Request message definition - SubFunction = reportUserDefMemoryDTCSnapshotRecordByDTCNumber
Table 313 — Request message definition - SubFunction = reportSupportedDTCExtDataRecord
Table 314 — Request message definition - SubFunction = reportWWHOBDDTCByMaskRecord
Table 315 — Request message definition - SubFunction = reportWWHOBDDTCWithPermanentStatus
Table 316 — Request message definition - SubFunction = reportDTCInformationByDTCReadinessGroupIdentifier
12.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 317 — Request message SubFunction definition
12.3.2.3 Request message data-parameter definition
Table 318 — Request data-parameter definition
12.3.3 Positive response message
12.3.3.1 Positive response message definition
12.3.3 Positive response message
12.3.3.1 Positive response message definition
Table 319 — Response message definition - SubFunction = reportNumberOfDTCByStatusMask, reportNumberOfDTCBySeverityMaskRecord
Table 320 — Response message definition - SubFunction = reportDTCByStatusMask, reportSupportedDTCs, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCWithPermanentStatus
Table 322 — Response message definition - SubFunction = reportDTCSnapshotRecordByDTCNumber
Table 322 — Response message definition - SubFunction = reportDTCSnapshotRecordByDTCNumber
Table 328 — Response message definition - SubFunction = reportUserDefMemoryDTCByStatusMask
Table 330 — Response message definition - SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber
Table 330 — Response message definition - SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber
Table 333 — Response message definition - SubFunction = reportWWHOBDDTCWithPermanentStatus
12.3.3.2 Positive response message data-parameter definition
12.3.4 Supported negative response codes (NRC_)
Table 336 — Supported negative response codes
12.3.5 Message flow examples – ReadDTCInformation
12.3.5.1 General asumption
12.3.5.2 Example #1 - ReadDTCInformation, SubFunction = reportNumberOfDTCByStatusMask
12.3.5.2.1 Example #1 overview
12.3.5.2.2 Example #1 assumptions
Table 337 — statusOfDTC = 2416 of DTC P0805-11
Table 337 — statusOfDTC = 2416 of DTC P0805-11
Table 338 — statusOfDTC = 2616 of DTC P0A9B-17
Table 339 — statusOfDTC = 2F16 of DTC P2522-1F
12.3.5.2.3 Example #1 message flow
12.3.5.2.3 Example #1 message flow
Table 341 — ReadDTCInformation, SubFunction = reportNumberOfDTCByStatusMask, positive response, example #1
12.3.5.3 Example #2 - ReadDTCInformation, SubFunction = reportDTCByStatusMask, matching DTCs returned
12.3.5.3.1 Example #2 overview
12.3.5.3.2 Example #2 assumptions
12.3.5.3.2 Example #2 assumptions
Table 342 — statusOfDTC= 2416 of DTC P0A9B-17
Table 343 — statusOfDTC = 0016 of DTC P2522-1F
Table 344 — statusOfDTC = 2F16 of DTC P0805-11
12.3.5.3.3 Example #2 message flow
Table 345 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #2
Table 346 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, positive response, example #2
12.3.5.4 Example #3 - ReadDTCInformation, SubFunction = reportDTCByStatusMask, no matching DTCs returned
12.3.5.4.1 Example #3 overview
12.3.5.4.2 Example #3 assumptions
Table 347 — statusOfDTC= 2416 of DTC P2522-1F
Table 348 — statusOfDTC = 0016 of DTC P0A9B-17
12.3.5.4.3 Example #3 message flow
Table 349 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #3
Table 350 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, positive response, example #3
12.3.5.5 Example #4 - ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification
12.3.5.5.1 Example #4 overview
12.3.5.5.2 Example #4 assumptions
12.3.5.5 Example #4 - ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification
12.3.5.5.1 Example #4 overview
12.3.5.5.2 Example #4 assumptions
12.3.5.5.3 Example #4 message flow
Table 351 — ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification, request message flow example #4
12.3.5.6 Example #5 - ReadDTCInformation, SubFunction = reportDTCSnapshotRecord-ByDTCNumber
12.3.5.6.1 Example #5 overview
12.3.5.6.2 Example #5 assumptions
Table 353 — DTCSnapshot record content
Table 353 — DTCSnapshot record content
12.3.5.6.3 Example #5 message flow
Table 354 — ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, request message flow example #5
Table 355 — ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, positive response, example #5
12.3.5.7 Example #6 - ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber
12.3.5.7.1 Example #6 overview
12.3.5.7.2 Example #6 assumptions
Table 356 — DTCStoredData record content
12.3.5.7.3 Example #6 message flow
Table 357 — ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber, request message flow example #6
12.3.5.7.3 Example #6 message flow
Table 357 — ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber, request message flow example #6
12.3.5.8 Example #7 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber
12.3.5.8.1 Example #7 overview
12.3.5.8.2 Example #7 assumptions
12.3.5.8 Example #7 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber
12.3.5.8.1 Example #7 overview
12.3.5.8.2 Example #7 assumptions
Table 359 — DTCExtDataRecordNumber 0516 content
Table 360 — DTCExtDataRecordNumber 1016 content
12.3.5.8.3 Example #7 message flow
Table 361 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber, request message flow example #7
Table 362 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber, positive response, example #7
12.3.5.9 Example #8 - ReadDTCInformation, SubFunction = reportNumberOfDTC-BySeverityMaskRecord
12.3.5.9.1 Example #8 overview
12.3.5.9.2 Example #8 assumptions
Table 363 — statusOfDTC = 2416 of DTC P0A9B-17
Table 363 — statusOfDTC = 2416 of DTC P0A9B-17
Table 364 — statusOfDTC = 0016 of DTC P2522-1F
Table 365 — statusOfDTC = 2F16 of DTC P0805-11
12.3.5.9.3 Example #8 message flow
Table 366 — ReadDTCInformation, SubFunction = reportNumberOfDTCBySeverityMaskRecord, request message flow example #8
Table 367 — ReadDTCInformation, SubFunction = reportNumberOfDTCBySeverityMaskRecord, positive response, example #8
12.3.5.10 Example #9 - ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord
12.3.5.10.1 Example #9 overview
12.3.5.10.2 Example #9 assumptions
12.3.5.10.3 Example #9 message flow
Table 368 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, request message flow example #9
Table 369 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, positive response, example #9
Table 369 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, positive response, example #9
12.3.5.11 Example #10 - ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC
12.3.5.11.1 Example #10 overview
12.3.5.11.2 Example #10 assumptions
12.3.5.11.3 Example #10 message flow
Table 370 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, request message flow example #10
Table 371 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10
Table 371 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10
12.3.5.12 Example #11 – ReadDTCInformation - SubFunction = reportSupportedDTCs
12.3.5.12.1 Example #11 overview
12.3.5.12.2 Example #11 assumptions
Table 372 — statusOfDTC = 2416
Table 373 — statusOfDTC = 0016
Table 374 — statusOfDTC = 2F16
12.3.5.12.3 Example #11 message flow
Table 375 — ReadDTCInformation, SubFunction = reportSupportedDTCs, request message flow example #11
Table 376 — ReadDTCInformation, SubFunction = readSupportedDTCs, positive response, example #11
Table 376 — ReadDTCInformation, SubFunction = readSupportedDTCs, positive response, example #11
12.3.5.13 Example #12 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, information available
12.3.5.13.1 Example #12 overview
12.3.5.13.2 Example #12 assumptions
Table 377 — statusOfDTC = 2616
Table 377 — statusOfDTC = 2616
12.3.5.13.3 Example #12 message flow
Table 378 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #12
Table 379 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #12
12.3.5.14 Example #13 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, no information available
12.3.5.14 Example #13 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, no information available
12.3.5.14.1 Example #13 overview
12.3.5.14.2 Example #13 assumptions
12.3.5.14.3 Example #13 message flow
Table 380 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #13
Table 381 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #13
12.3.5.15 Example #14 - ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter
12.3.5.15.1 Example #14 overview
12.3.5.15 Example #14 - ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter
12.3.5.15.1 Example #14 overview
12.3.5.15.2 Example #14 assumptions
12.3.5.15.3 Example #14 message flow
Table 382 — ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter, request message flow example #14
12.3.5.16 Example #15 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber
12.3.5.16.1 Example #15 overview
12.3.5.16 Example #15 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber
12.3.5.16.1 Example #15 overview
12.3.5.16.2 Example #15 assumptions
Table 384 — DTCExtDataRecordNumber 0516 content for DTC 12345616
Table 385 — DTCExtDataRecordNumber 0516 content for DTC 23456116
12.3.5.16.3 Example #15 message flow
Table 386 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15
12.3.5.16.3 Example #15 message flow
Table 386 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15
Table 387 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, positive response, example #15
12.3.5.17 Example #16 – ReadDTCInformation - SubFunction = reportDTCExtendedDataRecordIdentification
12.3.5.17.1 Example #16 overview
12.3.5.17.2 Example #16 assumptions
12.3.5.17.3 Example #16 message flow
Table 388 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16
Table 388 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16
Table 389 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, positive response, example #16
12.3.5.18 Example #17 - ReadDTCInformation, SubFunction = reportWWHOBDDTCByMaskRecord
12.3.5.18.1 Example #17 overview
12.3.5.18 Example #17 - ReadDTCInformation, SubFunction = reportWWHOBDDTCByMaskRecord
12.3.5.18.1 Example #17 overview
12.3.5.18.2 Example #17 assumptions
12.3.5.18.3 Example #17 message flow
Table 390 — ReadDTCInformation request, SubFunction = reportNumberOfDTCByStatusMask
Table 392 — ReadDTCInformation response, SubFunction = reportOBDDTCByStatusMask
12.3.5.19 Example #18 - ReadDTCInformation, SubFunction = reportOBDDTCWithPermanentStatus, matching DTCs returned
12.3.5.19.1 Example #18 overview
12.3.5.19.2 Example #18 assumptions
12.3.5.19 Example #18 - ReadDTCInformation, SubFunction = reportOBDDTCWithPermanentStatus, matching DTCs returned
12.3.5.19.1 Example #18 overview
12.3.5.19.2 Example #18 assumptions
12.3.5.19.3 Example #18 message flow
Table 394 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, request message flow example #2
Table 395 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18
Table 395 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18
12.3.5.20 Example #19 – ReadDTCInformation - SubFunction = reportDTCByReadinessGroupIdentifier
12.3.5.20.1 Example #19 overview
12.3.5.20.2 Example #19 assumptions
12.3.5.20.3 Example #19 message flow
Table 396 — ReadDTCInformation, SubFunction = reportDTCByReadinessGroupIdentifier, request message flow, example #19
13 InputOutput control functional unit
13.1 Overview
Table 398 — InputOutput Control functional unit
13.2 InputOutputControlByIdentifier (2F16) service
13 InputOutput control functional unit
13.1 Overview
Table 398 — InputOutput Control functional unit
13.2 InputOutputControlByIdentifier (2F16) service
13.2.1 Service description
13.2.2 Request message
13.2.2.1 Request message definition
13.2.2 Request message
13.2.2.1 Request message definition
13.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
13.2.2.3 Request message data-parameter definition
Table 400 — Request message data-parameter definition
13.2.3 Positive response message
13.2.3.1 Positive response message definition
Table 401 — Positive response message definition
13.2.3.2 Positive response message data-parameter definition
Table 402 — Response message data-parameter definition
13.2.4 Supported negative response codes (NRC_)
Table 403 — Supported negative response codes
Figure 29 — NRC handling for InputOutputControlByIdentifier service
13.2.5 Message flow example(s) InputOutputControlByIdentifier
13.2.5.1 Assumptions
13.2.5.2 Example #1 - "Air Inlet Door Position" shortTermAdjustment
13.2.5.2.1 Step #1: ReadDataByIdentifier
13.2.5.2 Example #1 - "Air Inlet Door Position" shortTermAdjustment
13.2.5.2.1 Step #1: ReadDataByIdentifier
13.2.5.2.2 Step #2: shortTermAdjustment
Table 407 — InputOutputControlByIdentifier positive response message flow example #1 - step #2
13.2.5.2.3 Step #3: ReadDataByIdentifier
Table 408 — ReadDataByIdentifier request message flow example #1 - step #3
Table 409 — ReadDataByIdentifier positive response message flow example #1 - step #3
13.2.5.2.4 Step #4: returnControlToECU
13.2.5.2.4 Step #4: returnControlToECU
13.2.5.2.5 Step #5: freezeCurrentState
Table 413 — InputOutputControlByIdentifier positive response message flow example #1 - step #5
13.2.5.3 Example #2 – EGR and IAC shortTermAdjustment
13.2.5.3.1 Assumptions
Table 414 — Composite data blocks – DataIdentifier definitions – Example #2
Table 415 — ControlEnableMaskRecord– Example #2
13.2.5.3.2 Case #1: Control IAC Pintle Position only
Table 416 — InputOutputControlByIdentifier request message flow example #2 – Case #1
Table 417 — InputOutputControlByIdentifier positive response message flow example #2 – Case #1
13.2.5.3.3 Case #2: Control RPM Only
Table 418 — InputOutputControlByIdentifier request message flow example #2 – Case #2
Table 419 — InputOutputControlByIdentifier positive response message flow example #2 – Case #2
Table 419 — InputOutputControlByIdentifier positive response message flow example #2 – Case #2
13.2.5.3.4 Case #3: Control both Pedal Position A and EGR Duty Cycle
Table 420 — InputOutputControlByIdentifier request message flow example #2 – Case #3
Table 421 — InputOutputControlByIdentifier positive response message flow example #2 – Case #3
13.2.5.3.5 Case #4: Return control of all parameters to the ECU
Table 422 — InputOutputControlByIdentifier request message flow example #2 – Case #4
14 Routine functional unit
14.1 Overview
Table 424 — Routine functional unit
14.2 RoutineControl (3116) service
14.2.1 Service description
14.2.1.1 Overview
14.2.1.1 Overview
14.2.1.2 Start a routine referenced by a routineIdentifier
14.2.1.3 Stop a routine referenced by a routineIdentifier
14.2.1.4 Request routine results referenced by a routineIdentifier
14.2.2 Request message
14.2.2.1 Request message definition
Table 425 — Request message definition
14.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 426 — Request message SubFunction definition
14.2.2.3 Request message data-parameter definition
Table 427 — Request message data-parameter definition
14.2.3 Positive response message
14.2.3.1 Positive response message definition
Table 428 — Positive response message definition
14.2.3.2 Positive response message data-parameter definition
Table 429 — Response message data-parameter definition
14.2.4 Supported negative response codes (NRC_)
Table 430 — Supported negative response codes
Figure 30 — NRC handling for RoutineControl service
14.2.5 Message flow example(s) RoutineControl
14.2.5.1 Example #1: SubFunction = startRoutine
Table 431 — RoutineControl request message flow - example #1
Table 431 — RoutineControl request message flow - example #1
Table 432 — positive response message flow - example #1
14.2.5.2 Example #2: SubFunction = stopRoutine
Table 433 — RoutineControl request message flow - example #2
Table 434 — RoutineControl positive response message flow - example #2
14.2.5.3 Example #3: SubFunction = requestRoutineResults
Table 435 — RequestRoutineResults request message flow – example #3
14.2.5.4 Example #4: SubFunction = startRoutine with routineControlOption
Table 437 — RoutineControl request message flow - example #4
Table 438 — RoutineControl positive response message flow - example #4
15 Upload download functional unit
15.1 Overview
Table 439 — Upload Download functional unit
15.2 RequestDownload (3416) service
15.2.1 Service description
15.2.2 Request message
15.2.2.1 Request message definition
Table 440 — Request message definition
15.2.2 Request message
15.2.2.1 Request message definition
Table 440 — Request message definition
15.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.2.2.3 Request message data-parameter definition
Table 441 — Request message data-parameter definition
15.2.3 Positive response message
15.2.3.1 Positive response message definition
Table 442 — Positive response message definition
15.2.3.2 Positive response message data-parameter definition
Table 443 — Response message data-parameter definition
15.2.4 Supported negative response codes (NRC_)
Figure 31 — NRC handling for RequestDownload service
15.2.5 Message flow example(s) RequestDownload
15.3 RequestUpload (3516) service
15.3.1 Service description
15.3.2 Request message
15.3.2.1 Request message definition
15.3.2 Request message
15.3.2.1 Request message definition
Table 445 — Request message definition
15.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.3.2.3 Request message data-parameter definition
15.3.3 Positive response message
15.3.3.1 Positive response message definition
Table 447 — Positive response message definition
15.3.3.2 Positive response message data-parameter definition
Table 448 — Response message data-parameter definition
15.3.4 Supported negative response codes (NRC_)
Table 449 — Supported negative response codes
Figure 32 — NRC handling for RequestUpload service
15.3.5 Message flow example(s) RequestUpload
15.4 TransferData (3616) service
15.4.1 Service description
15.4 TransferData (3616) service
15.4.1 Service description
15.4.2 Request message
15.4.2.1 Request message definition
Table 450 — Request message definition
15.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.4.2.3 Request message data-parameter definition
15.4.3 Positive response message
15.4.3.1 Positive response message definition
Table 452 — Positive response message definition
15.4.3.2 Positive response message data-parameter definition
Table 453 — Response message data-parameter definition
15.4.3.2 Positive response message data-parameter definition
Table 453 — Response message data-parameter definition
15.4.4 Supported negative response codes (NRC_)
Table 454 — Supported negative response codes
Figure 33 — NRC handling for TransferData service
15.4.5 Message flow example(s) TransferData
15.5 RequestTransferExit (3716) service
15.5.1 Service description
15.5.2 Request message
15.5.2.1 Request message definition
Table 455 — Request message definition
15.5.2 Request message
15.5.2.1 Request message definition
Table 455 — Request message definition
15.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.5.2.3 Request message data-parameter definition
Table 456 — Request message data-parameter definition
15.5.3 Positive response message
15.5.3.1 Positive response message definition
Table 457 — Positive response message definition
15.5.3.2 Positive response message data-parameter definition
15.5.4 Supported negative response codes (NRC_)
Table 459 — Supported negative response codes
15.5.5 Message flow example(s) for downloading/uploading data
15.5.5.1 Download data to a server
15.5.5.1.1 Assumptions
Table 460 — Definition of transferRequestParameter values
Table 461 — Definition of transferResponseParameter value
Table 461 — Definition of transferResponseParameter value
15.5.5.1.2 Step #1: Request for download
Table 462 — RequestDownload request message flow example
Table 463 — RequestDownload positive response message flow example
Table 463 — RequestDownload positive response message flow example
15.5.5.1.3 Step #2: Transfer data
Table 464 — TransferData request message flow example
Table 465 — TransferData positive response message flow example
Table 467 — TransferData positive response message flow example
Table 467 — TransferData positive response message flow example
15.5.5.1.4 Step #3: Request Transfer exit
Table 468 — RequestTransferExit request message flow example
Table 469 — RequestTransferExit positive response message flow example
15.5.5.2 Upload data from a server
15.5.5.2.1 Step #1: Request for upload
Table 472 — RequestUpload request message flow example
Table 473 — RequestUpload positive response message flow example
Table 473 — RequestUpload positive response message flow example
15.5.5.2.2 Step #2: Transfer data
Table 474 — TransferData request message flow example
Table 475 — TransferData positive response message flow example
Table 477 — TransferData positive response message flow example
15.5.5.2.3 Step #3: Request Transfer exit
Table 479 — RequestTransferExit positive response message flow example
Table 479 — RequestTransferExit positive response message flow example
15.6 RequestFileTransfer (3816) service
15.6.1 Service description
15.6.2 Request message
15.6.2.1 Request message definition
Table 480 — Request message definition
15.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.6.2.3 Request message data-parameter definition
15.6.3 Positive response message
15.6.3.1 Positive response message definition
Table 482 — Positive response message definition
15.6.3.2 Positive response message data-parameter definition
Table 483 — Response message data-parameter definition
15.6.4 Supported negative response codes (NRC_)
Table 484 — Supported negative response codes
Figure 35 — NRC handling for requestFileTransfer service
15.6.5 Message flow example(s) RequestFileTransfer
15.6.5.1 Assumptions
Table 485 — Definition RequestFileTransfer message parameter values
15.6.5.2 Request file transfer
Table 486 — RequestFileTransfer request message example
Table 487 — RequestFileTransfer positive response request message example
16 Security sub-layer definition
16.1 General
16.1.1 Purpose
16.1.2 Security sub-layer description
Figure 36 — Security sub-layer implementation
Figure 36 — Security sub-layer implementation
16.1.3 Security sub-layer access
Figure 37 — Physical communication during defaultSession - with SOM.ind and security sub-layer
Figure 38 — Physical communication during defaultSession - with enhanced response timing and security sub-layer
16.1.4 General server response behaviour
16.2 SecuredDataTransmission (8416) service
16.2.1 Service description
16.2 SecuredDataTransmission (8416) service
16.2.1 Service description
16.2.2 Request message
16.2.2.1 Request message definition
Table 488 — Request message definition
16.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
16.2.2.3 Request message data-parameter definition
Table 489 — Request message data-parameter definition
16.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
16.2.2.3 Request message data-parameter definition
Table 489 — Request message data-parameter definition
Table 490 — Definition of Administrative Parameter
16.2.3 Positive response message for successful internal message
16.2.3.1 Positive response message definition for successful internal message
Table 492 — Positive response message definition
16.2.3.2 Positive response message data-parameter definition
Table 493 — Response message data-parameter definition
16.2.3.2 Positive response message data-parameter definition
Table 493 — Response message data-parameter definition
16.2.3.3 Positive response message definition for unsuccessful internal message
Table 494 — Positive response message definition
16.2.3.4 Positive response message data-parameter definition
Table 495 — Response message data-parameter definition
16.2.4 Supported negative response codes (NRC_)
Table 496 — Supported negative response codes
16.2.5 Message flow example SecuredDataTransmission
16.2.5.1 Assumptions
16.2.5.2 Example #1: SecuredDataTransmission to Write DID
Table 497 — SecuredDataTransmission request message flow example #1
16.2.5.3 Example #2: SecuredDataTransmission to Write DID
Table 499 — SecuredDataTransmission request message flow example #2
Table 499 — SecuredDataTransmission request message flow example #2
Table 500 — SecuredDataTransmission response message flow example #2
17 Non-volatile server memory programming process
17.1 General information
17.2 Detailed programming sequence
17.2 Detailed programming sequence
17.2.1 Programming phase #1 — Download of application software and/or application data
17.2.1.1 Pre-Programming step of phase #1 — Setup of vehicle network for programming
17.2.1.2 Programming step of phase #1 — Download of application software and data
17.2.1.2 Programming step of phase #1 — Download of application software and data
17.2.1.3 Post-Programming step of phase #1 — Re-synchronisation of vehicle network
17.2.1.3 Post-Programming step of phase #1 — Re-synchronisation of vehicle network
Figure 43 — Post-programming step of phase 1 (STP3)
17.2.1.4 Preprogramming step of phase #2 — Server configuration
Figure 44 — Preprogramming step of phase 2 (STP4)
17.2.1.5 Programming step of phase #2 — Final server configuration
Figure 45 — Programming step of phase 2 (STP5)
17.2.1.6 Post-programming step of phase #2 — Re-synchronisation of vehicle network
17.3 Server reprogramming requirements
17.3 Server reprogramming requirements
17.3.1 Requirements for servers to support programming
17.3.1.1 Boot software description and requirements
17.3.1.1.1 Boot software general requirements
17.3.1.1.2 Boot software diagnostic service requirements
Table 503 — Boot software diagnostic service support during post-programming step of phase #1
17.3.1.2 Security requirements
17.3.2 Software, data identification and fingerprints
17.3.2.1 Software and data identification
17.3.2.2 Software and data fingerprints
17.3.2.2 Software and data fingerprints
17.3.3 Server routine access
Table 504 — routineIdentifiers for non-volatile memory access
17.4 Non-volatile server memory programming message flow examples
17.4.1 General information
17.4.2 Programming phase #1 — Pre-Programming step
Table 505 — StartDiagnosticSessionControl(extendedSession)
Table 506 — ControlDTCSetting(off)
Table 507 — CommunicationControl(disableRxAndTx in the application)
17.4.3 Programming phase #1 — Programming step
Table 508 — DiagnosticSessionControl(programmingSession)
Table 509 — SecurityAccess(requestSeed)
Table 510 — SecurityAccess(sendKey)
Table 511 — RoutineControl(eraseMemory)
Table 512 — RequestDownload — Module #1
Table 513 — TransferData — Module #1 (block #1)
Table 514 — TransferData — Module #1 (block #2)
Table 516 — RequestTransferExit — Module #1
Table 517 — RequestDownload — Module #2
Table 518 — TransferData — Module #2 (block #1)
Table 519 — TransferData — Module #2 (block #2)
Table 520 — TransferData — Module #2 (block #3)
Table 521 — RequestTransferExit — Module #2
Table 522 — RoutineControl(validate application)
Table 523 — WriteDataByIdentifier — dataIdentifier = VIN
17.4.4 Programming phase #1 — Post-Programming step
Annex A (normative) Global parameter definitions
A.1 Negative response codes
Annex B (normative) Diagnostic and communication management functional unit data-parameter definitions
B.1 communicationType parameter definition
Table B.1 — Definition of communicationType and subnetNumber byte
B.2 eventWindowTime parameter definition
B.3 linkControlModeIdentifier parameter definition
Table B.3 — Definition of linkControlModeIdentifier values
B.3 linkControlModeIdentifier parameter definition
Table B.3 — Definition of linkControlModeIdentifier values
B.4 nodeIdentificationNumber parameter definition
B.4 nodeIdentificationNumber parameter definition
B.5 AuthenticationReturnParameter definitions
Table B.5 — authenticationReturnParameter definitions
Annex C (normative) Data transmission functional unit data-parameter definitions
C.1 DID parameter definitions
Table C.1 — DID data-parameter definitions
C.2 scalingByte parameter definitions
Table C.3 — scalingByte (Low Nibble) parameter definition
C.3 scalingByteExtension parameter definitions
C.3.1 scalingByteExtension for scalingByte high nibble of bitMappedReportedWithOutMask
Table C.4 — scalingByteExtension for bitMappedReportedWithOutMask
C.3.2 scalingByteExtension for scalingByte high nibble of formula
Table C.5 — scalingByteExtension Bytes for formula
Table C.6 — formulaIdentifier encoding
Table C.7 — Two byte real number format
C.3.3 scalingByteExtension for scalingByte high nibble of unit/format
C.3.3 scalingByteExtension for scalingByte high nibble of unit/format
Table C.8 — Unit/format scalingByteExtension encoding
C.3.4 scalingByteExtension for scalingByte high nibble of stateAndConnectionType
Table C.9 — Encoding of scalingByte High Nibble of stateAndConnectionType
Table C.9 — Encoding of scalingByte High Nibble of stateAndConnectionType
C.4 transmissionMode parameter definitions
Table C.10 — transmissionMode parameter definitions
C.5 Coding of UDS edition version number
Table C.11 — Coding of UDS edition version number DID FF0016 – 4 bytes unsigned value
Table C.12 — DID FF0016 UDS edition version values of this document
Annex D (normative) Stored data transmission functional unit data-parameter definitions
D.1 groupOfDTC parameter definition
Table D.1 — Definition of groupOfDTC and range of DTC numbers
D.2 DTCStatusMask and statusOfDTC bit definitions
D.2.1 Convention and definition
D.2.2 Pseudocode data dictionary
Table D.2 — Pseudocode data dictionary
D.2.3 DTC status bit definitions
Table D.4 — DTC status bit 1 testFailedThisOperationCycle definitions
Table D.6 — DTC status bit 3 confirmedDTC definitions
Table D.7 — DTC status bit 4 testNotCompletedSinceLastClear definitions
Figure D.8 — DTC status bit 7 WarningIndicator requested logic
D.2.4 Example for operation of DTC Status Bits
D.3 DTC severity and class definition
D.3.1 DTC severity and class byte definition
Table D.11 — DTCSeverityMask/DTCSeverity byte definition
D.3.2 DTC severity bit definition
Table D.12 — DTC severity bit definitions (bit 7 to 5)
D.3.3 DTC class definition
Table D.13 — GTR DTC Class definition (bit 4 to 0)
D.4 DTCFormatIdentifier definition
Table D.14 — Definition of DTCFormatIdentifier (DTCFID_)
D.5 FunctionalGroupIdentifier definition
Table D.15 — Definition of FunctionalGroupIdentifiers (FGID_)
D.6 DTCFaultDetectionCounter operation implementation example
D.7 DTCAgingCounter example
D.7 DTCAgingCounter example
D.8 DTCExtendedDataRecordNumber value definition
Table D.16 — DTCExtendedDataRecordNumber value definition
Annex E (normative) Input output control functional unit data-parameter definitions
Annex F (normative) Routine functional unit data-parameter definitions
Annex G (normative) Upload and download functional unit data-parameter
Table G.1 — Definition of modeOfOperation values
Annex H (informative) Examples for addressAndLengthFormatIdentifier parameter values
Table H.1 — addressAndLengthFormatIdentifier example
Annex I (normative) Security access state chart
I.1 General
I.2 Disjunctive normal form based state transition definitions
Table I.1 — State transitions – parameters
Annex J (informative) Recommended implementation for multiple client environments
J.1 Introduction
J.2 Implementation specific limitations
J.3 Use cases relevant for system design
Figure J.1 — Example vehicle topology with onboard clients
Table J.1 — Use case (UC) matrix of multiple client scenarios to be addressed
J.4 Use case evaluation
J.4 Use case evaluation
Table J.2 — Evaluation of multiple client use cases
J.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol
J.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol
J.5.2 Assumptions
J.5.3 Multiple client handling flow
Bibliography
Blank Page
Previous versions
Keep me up-to-date
Sign up to receive updates when there are changes to this standard
Related Information
Similar Standards
-
AS/NZS 2538:2004
Vehicle support stands
-
AS/NZS 2550.9:1996
Cranes - Safe use - Vehicle hoists
-
AS/NZS 2615:2004
Hydraulic trolley jacks
-
AS/NZS 2640:1994
Portable ramps for vehicles
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
3 Terms and definitions
4 Symbols and abbreviated terms
5 Conventions
Figure 1 — The services and the protocol
6 Document overview
7 Application layer services
7.1 General
Figure 4 — Application layer service primitives – Unconfirmed service
Figure 4 — Application layer service primitives – Unconfirmed service
7.2 Format description of application layer services
7.3 Format description of service primitives
7.3.1 General definition
7.3.2 Service request and service indication primitives
7.3.3 Service response and service confirm primitives
7.3.3 Service response and service confirm primitives
7.3.4 Service request-confirm and service response-confirm primitives
7.4 Service data unit specification
7.4.1 Mandatory parameters
7.4.1.1 General definition
7.4.1.2 A_Mtype, application layer message type
7.4.1.3 A_SA, application layer source address
7.4.1.3 A_SA, application layer source address
7.4.1.4 A_TA, application layer target address
7.4.1.5 A_TA_Type, application layer target address type
7.4.1.5 A_TA_Type, application layer target address type
7.4.1.6 A_Result
7.4.1.7 A_Length
7.4.1.8 A_Data
7.4.2 Vehicle system requirements
7.4.3 Optional parameters - A_AE, application layer remote address
7.4.3 Optional parameters - A_AE, application layer remote address
8 Application layer protocol
8.1 General definition
8.2 A_PDU, application protocol data unit
8.2 A_PDU, application protocol data unit
8.3 A_PCI, application protocol control information
8.4 SI, service identifier
8.4 SI, service identifier
8.5 A_NR_SI, Negative response service identifier
8.6 Negative response/confirmation service primitive
8.6 Negative response/confirmation service primitive
8.7 Server response implementation rules
8.7.1 General definitions
8.7.2 General server response behaviour
8.7.3 Request message with SubFunction parameter and server response behaviour
8.7.3.1 General server response behaviour for request messages with SubFunction parameter
8.7.3 Request message with SubFunction parameter and server response behaviour
8.7.3.1 General server response behaviour for request messages with SubFunction parameter
8.7.3.2 Physically addressed client request message
8.7.3.2 Physically addressed client request message
8.7.3.3 Functionally addressed client request message
8.7.4 Request message without SubFunction parameter and server response behaviour
8.7.4.1 General server response behaviour for request messages without SubFunction parameter
8.7.4.2 Physically addressed client request message
8.7.4.3 Functionally addressed client request message
8.7.5 Pseudo code example of server response behaviour
8.7.6 Multiple concurrent request messages with physical and functional addressing
8.7.6 Multiple concurrent request messages with physical and functional addressing
9 Service description conventions
9.1 Service description
Table 8 — A_PDU parameter conventions
9.2 Request message
9.2.1 Request message definition
Table 10 — Request A_PDU definition without SubFunction
9.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 11 — SubFunction parameter structure
Table 12 — Request message SubFunction parameter definition
9.2.3 Request message data-parameter definition
9.3 Positive response message
9.3.1 Positive response message definition
9.3.2 Positive response message data-parameter definition
9.4 Supported negative response codes (NRC_)
Table 18 — Supported negative response codes
9.5 Message flow examples
Table 19 — Request message flow example
10 Diagnostic and communication management functional unit
10.1 Overview
Table 22 — Diagnostic and communication management functional unit
10.2 DiagnosticSessionControl (1016) service
10.2.1 Service description
10.2.2 Request message
10.2.2.1 Request message definition
10.2.2 Request message
10.2.2.1 Request message definition
10.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
10.2.2.3 Request message data-parameter definition
10.2.3 Positive response message
10.2.3.1 Positive response message definition
10.2.3.2 Positive response message data-parameter definition
Table 28 — sessionParameterRecord definition
10.2.4 Supported negative response codes (NRC_)
10.2.5 Message flow example(s) DiagnosticSessionControl – Start programmingSession
10.3 ECUReset (1116) service
10.3.1 Service description
10.3.2 Request message
10.3.2.1 Request message definition
10.3.2.2 Request message SubFunction Parameter $Level (LEV_) definition
Table 34 — Request message SubFunction parameter definition
10.3.2.3 Request message data-parameter definition
10.3.3 Positive response message
10.3.3.1 Positive response message definition
Table 35 — Positive response message definition
10.3.3.2 Positive response message data-parameter definition
Table 36 — Response message data-parameter definition
10.3.4 Supported negative response codes (NRC_)
Table 37 — Supported negative response codes
10.3.5 Message flow example ECUReset
10.3.5 Message flow example ECUReset
10.4 SecurityAccess (2716) service
10.4.1 Service description
10.4.2 Request message
10.4.2.1 Request message definition
10.4.2 Request message
10.4.2.1 Request message definition
Table 41 — Request message definition - SubFunction = sendKey
10.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 42 — Request message SubFunction parameter definition
Table 42 — Request message SubFunction parameter definition
10.4.2.3 Request message data-parameter definition
10.4.3 Positive response message
10.4.3.1 Positive response message definition
Table 44 — Positive response message definition
10.4.3 Positive response message
10.4.3.1 Positive response message definition
Table 44 — Positive response message definition
10.4.3.2 Positive response message data-parameter definition
Table 45 — Response message data-parameter definition
10.4.4 Supported negative response codes (NRC_)
10.4.5 Message flow example(s) SecurityAccess
10.4.5.1 Assumptions
10.4.5.2 Example #1 - server is in a “locked” state
10.4.5.2.1 Step #1: Request the Seed
10.4.5.2.2 Step #2: Send the Key
10.4.5.3 Example #2 - server is in an “unlocked” state
10.4.5.3.1 Step #1: Request the Seed
Table 52 — SecurityAccess positive response message flow example #2 – step #2
Table 52 — SecurityAccess positive response message flow example #2 – step #2
10.5 CommunicationControl (2816) service
10.5.1 Service description
10.5.2 Request message
10.5.2.1 Request message definition
Table 53 — Request message definition
10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 — Request message SubFunction parameter definition
10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 — Request message SubFunction parameter definition
10.5.2.3 Request message data-parameter definition
Table 55 — Request message data-parameter definition
10.5.3 Positive response message
10.5.3.1 Positive response message definition
Table 56 — Positive response message definition
10.5.3.2 Positive response message data-parameter definition
Table 57 — Response message data-parameter definition
10.5.4 Supported negative response codes (NRC_)
Table 58 — Supported negative response codes
10.5.5 Message flow example CommunicationControl (disable transmission of network management messages)
Table 60 — CommunicationControl positive response message flow example
10.5.6 Message flow example CommunicationControl (switch a remote network into the diagnostic-only scheduling mode where the node with address 000A16 is connected to)
Table 61 — CommunicationControl request message flow example
10.5.7 Message flow example CommunicationControl (switch to application scheduling mode with enhanced address information, the node 000A16, which is connected to a sub-network, is addressed)
Table 63 — CommunicationControl request message flow example
Table 64 — CommunicationControl positive response message flow example
10.6 Authentication (2916) service
10.6.1 Service overview
10.6.2 Authentication with PKI Certificate Exchange (APCE)
10.6.2 Authentication with PKI Certificate Exchange (APCE)
10.6.3 Authentication with Challenge-Response (ACR)
Figure 10 — Authentication sequence with Challenge-Response (ACR)
10.6.4 Common requirements
10.6.5 Request message
10.6.5.1 Request message definition
10.6.5 Request message
10.6.5.1 Request message definition
Table 67 — Request message definition - SubFunction = verifyCertificateBidirectional
Table 69 — Request message definition - SubFunction = transmitCertificate
Table 70 — Request message definition - SubFunction = requestChallengeForAuthentication
Table 71 — Request message definition - SubFunction = verifyProofOfOwnershipUnidirectional
Table 72 — Request message definition - SubFunction = verifyProofOfOwnershipBidirectional
Table 72 — Request message definition - SubFunction = verifyProofOfOwnershipBidirectional
Table 73 — Request message definition - SubFunction = authenticationConfiguration
10.6.5.2 Request message SubFunction parameter $Level (LEV_) definition
Table 74 — Request message SubFunction parameter definition
10.6.5.3 Request message data-parameter definition
10.6.6 Positive response message
10.6.6.1 Positive response message definition
10.6.6 Positive response message
10.6.6.1 Positive response message definition
Table 76 — Response message definition - SubFunction = deAuthenticate
Table 78 — Response message definition - SubFunction = verifyCertificateBidirectional
Table 78 — Response message definition - SubFunction = verifyCertificateBidirectional
Table 81 — Response message definition - SubFunction = requestChallengeForAuthentication
Table 83 — Response message definition - SubFunction = verifyProofOfOwnershipBidirectional
10.6.6.2 Positive response message data-parameter definition
10.6.7 Supported negative response codes (NRC_)
10.6.7 Supported negative response codes (NRC_)
10.6.8 Message flow example(s) Authentication
10.6.8.1 Example #1 - Unidirectional Authentication with PKI Certificate Exchange without session key establishment (happy path)
10.6.8.1.1 Assumptions
10.6.8.1.2 Step #1: Request Authentication Configuration
Table 88 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment positive response message flow example #1 - step #1
10.6.8.1.3 Step #2: Send Certificate Client
Table 89 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 – step #2
10.6.8.1.4 Step #3: Validate the Proof of Ownership
Table 91 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 - step #3
Table 92 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment positive response message flow example #1 - step #3
10.6.8.1.5 Step #4: Attempt to send a random secured service
Table 94 — ECUReset response message after successful Authentication request message attempt – example #1 - step #4
10.6.8.2 Example #2 - Unidirectional Authentication with PKI Certificate Exchange without session key establishment (failure path)
10.6.8.2.1 Assumptions
10.6.8.2.2 Step #1: Send Certificate Client
Table 95 — Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #2 – step #1
10.6.8.2.3 Step #2: Attempt to send a random secured service
Table 97 — ECUReset request message after failed Authentication request message attempt – example #2 - step #2
Table 98 — ECUReset response message after failed Authentication request message attempt – example #2 - step #2
10.6.8.3 Example #3 – Transmit Certificate after Authentication with PKI Certificate Exchange (happy path)
10.6.8.3.1 Assumptions
10.6.8.3.2 Step #1: Send Certificate
Table 99 — Transmit Certificate request message flow example #3 - step #1
Table 100 — Transmit Certificate positive response message flow example #3 - step #1
Table 100 — Transmit Certificate positive response message flow example #3 - step #1
10.6.8.4 Example #4 - Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment (happy path)
10.6.8.4.1 Assumptions
10.6.8.4.2 Step #1: Request Authentication Configuration
10.6.8.4.3 Step #2: Request the Challenge
10.6.8.4.4 Step #3: Validate the Proof of Ownership
Table 105 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #4 - step #3
10.6.8.5 Example #5 - Unidirectional Authentication using Challenge-Response (ACR) with asymmetric cryptography without session key establishment (failure path)
10.6.8.5.1 Assumptions
10.6.8.5.2 Step #1: Request the Challenge
Table 107 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 - step #1
10.6.8.5.3 Step #2: Validate the Proof of Ownership
Table 109 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 - step #2
Table 110 — Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment negative response message flow example #5 - step #2
10.6.8.6 Example #6 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment (happy path)
10.6.8.6.1 Assumptions
10.6.8.6.2 Step #1: Request challenge for Authentication
Table 111 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 - step #1
Table 112 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #6 - step #1
10.6.8.6.3 Step #2: Verify Proof of Ownership Unidirectional
Table 113 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 - step #2
Table 114 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #6 - step #2
10.6.8.7 Example #7 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment (failure path)
10.6.8.7.1 Assumptions
10.6.8.7.2 Step #1: Request challenge for Authentication
Table 115 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 - step #1
Table 115 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 - step #1
Table 116 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #7 - step #1
10.6.8.7.3 Step #2: Verify Proof of Ownership Unidirectional
Table 118 — Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment negative response message flow example #7 - step #2
10.7 TesterPresent (3E16) service
10.7.1 Service description
10.7 TesterPresent (3E16) service
10.7.1 Service description
10.7.2 Request message
10.7.2.1 Request message definition
Table 119 — Request message definition
10.7.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 120 — Request message SubFunction parameter definition
10.7.2.3 Request message data-parameter definition
10.7.3 Positive response message
10.7.3.1 Positive response message definition
Table 121 — Positive response message definition
10.7.3.2 Positive response message data-parameter definition
Table 121 — Positive response message definition
10.7.3.2 Positive response message data-parameter definition
Table 122 — Response message data-parameter definition
10.7.4 Supported negative response codes (NRC_)
Table 123 — Supported negative response codes
10.7.5 Message flow example(s) TesterPresent
10.7.5.1 Example #1 - TesterPresent (suppressPosRspMsgIndicationBit = FALSE)
Table 124 — TesterPresent request message flow example #1
Table 125 — TesterPresent positive response message flow example #1
10.7.5.2 Example #2 - TesterPresent (suppressPosRspMsgIndicationBit = TRUE)
Table 126 — TesterPresent request message flow example #2
10.8 ControlDTCSetting (8516) service
10.8.1 Service description
10.8.2 Request message
10.8.2.1 Request message definition
10.8.2 Request message
10.8.2.1 Request message definition
Table 127 — Request message definition
10.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 128 — Request message SubFunction parameter definition
10.8.2.3 Request message data-parameter definition
Table 129 — Request message data-parameter definition
Table 129 — Request message data-parameter definition
10.8.3 Positive response message
10.8.3.1 Positive response message definition
Table 130 — Positive response message definition
10.8.3.2 Positive response message data-parameter definition
Table 131 — Response message data-parameter definition
10.8.4 Supported negative response codes (NRC_)
Table 132 — Supported negative response codes
10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 - ControlDTCSetting (DTCSettingType = off)
Table 133 — ControlDTCSetting request message flow example #1
10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 - ControlDTCSetting (DTCSettingType = off)
Table 133 — ControlDTCSetting request message flow example #1
Table 134 — ControlDTCSetting positive response message flow example #1
10.8.5.2 Example #2 - ControlDTCSetting ( DTCSettingType = on)
Table 135 — ControlDTCSetting request message flow example #2
Table 136 — ControlDTCSetting positive response message flow example #2
10.9 ResponseOnEvent (8616) service
10.9.1 Service description
Figure 13 — Sampling of data identifiers
Table 137 — Recommended services to be used with the ResponseOnEvent service
10.9.2 Request message
10.9.2.1 Request message definition
10.9.2.2 Request message SubFunction Parameter $Level (LEV_) Definition
10.9.2.2.1 ResponseOnEvent request message SubFunction Parameter definition
10.9.2.2.2 Detailed request message SubFunction onDTCStatusChange parameters specification
10.9.2.2.3 Detailed request message SubFunction reportMostRecentDtcOnStatusChange parameters specification
10.9.2.2.4 Detailed request message SubFunction reportDTCRecordInformationOnDtcStatusChange parameters specification
10.9.2.2.5 Detailed request message SubFunction onChangeOfDataIdentifier parameters specification
10.9.2.2.6 Detailed request message SubFunction onComparisonOfValues parameters specification
Table 143 — Localization of value 16 bit bitfield parameter definition
10.9.2.3 Request message data-parameter definition
10.9.3 Positive response message
10.9.3.1 Positive response message definition
10.9.3.2 Positive response message data-parameter definition
Table 147 — Response message data-parameter definition
10.9.4 Supported negative response codes (NRC_)
Table 148 — Supported negative response codes
10.9.4 Supported negative response codes (NRC_)
Table 148 — Supported negative response codes
10.9.5 Message flow example(s) ResponseOnEvent
10.9.5.1 Assumptions
10.9.5.2 Example #1 - ResponseOnEvent (finite event window)
Table 150 — ResponseOnEvent initial positive response message flow example #1
Table 151 — Start of ResponseOnEvent request message flow example #1
Table 153 — ReadDTCInformation positive response message flow example #1
Table 156 — ResponseOnEvent final positive response message flow example #1
Figure 17 — Finite event window - multiple events during active event window
10.9.5.3 Example #2 - ResponseOnEvent (infinite event window)
Table 157 — ResponseOnEvent request message flow example #2
Table 157 — ResponseOnEvent request message flow example #2
Table 158 — ResponseOnEvent initial positive response message flow example #2
Table 159 — Start of ResponseOnEvent request message flow example #2
Table 160 — ResponseOnEvent positive response message flow example #2
Table 161 — ReadDTCInformation positive response message flow example #2
10.9.5.4 Example #3 - ResponseOnEvent (infinite event window) – SubFunction parameter “onComparisonOfValues”
10.9.5.4 Example #3 - ResponseOnEvent (infinite event window) – SubFunction parameter “onComparisonOfValues”
Table 162 — ResponseOnEvent request message example #3
Table 162 — ResponseOnEvent request message example #3
Table 163 — ReadDataByIdentifier positive response message example #3
10.9.5.5 Example #4 - ResponseOnEvent request message (reportMostRecentDtcOnStatusChange)
Table 164 — ResponseOnEvent request message flow example #4
Table 165 — ReadDTCInformation positive response message flow example #4
10.9.5.6 Example #5 - ResponseOnEvent request message (reportDTCRecordInformationOnDtcStatusChange)
Table 166 — ResponseOnEvent request message flow example #4
Table 167 — ReadDTCInformation positive response message flow example #1
Table 167 — ReadDTCInformation positive response message flow example #1
10.10 LinkControl (8716) service
10.10.1 Service description
10.10.2 Request message
10.10.2.1 Request message definition
Table 169 — Request message definition (linkControlType = verifyModeTransitionWithSpecificParameter)
Table 170 — Request message definition (linkControlType = transitionMode)
10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 — Request message SubFunction parameter definition
10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 — Request message SubFunction parameter definition
10.10.2.3 Request message data-parameter definition
10.10.3 Positive response message
10.10.3.1 Positive response message definition
10.10.3 Positive response message
10.10.3.1 Positive response message definition
10.10.3.2 Positive response message data-parameter definition
Table 174 — Response message data-parameter definition
10.10.4 Supported negative response codes (NRC_)
Table 175 — Supported negative response codes
10.10.5 Message flow example(s) LinkControl
10.10.5.1 Example #1 - Transition baudrate to fixed baudrate (PC baudrate 115,2 kBit/s)
10.10.5.1.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 176 — LinkControl request message flow example #1 - step #1
10.10.5 Message flow example(s) LinkControl
10.10.5.1 Example #1 - Transition baudrate to fixed baudrate (PC baudrate 115,2 kBit/s)
10.10.5.1.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 176 — LinkControl request message flow example #1 - step #1
Table 177 — LinkControl positive response message flow example #1 - step #1
10.10.5.1.2 Step#2: Transition the baudrate
Table 178 — LinkControl request message flow example #1 - step #2
10.10.5.2 Example #2 - Transition baudrate to specific baudrate (150 kBit/s)
10.10.5.2.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 179 — LinkControl request message flow example #2 - step #1
Table 180 — LinkControl positive response message flow example #2 - step #1
10.10.5.2.2 Step#2: Transition the baudrate
Table 181 — LinkControl request message flow example #2 - step #2
10.10.5.3 Example #3 - Transition FlexRay cycle design to 'programming'
10.10.5.3.1 Step#1: Verify if all criteria are met for a scheduler switch
Table 182 — LinkControl request message flow example #3 - step #1
Table 183 — LinkControl positive response message flow example #3 - step #1
10.10.5.3.2 Step#2: Transition to programming scheduler
Table 184 — LinkControl request message flow example #3 - step #2
11 Data transmission functional unit
11.1 Overview
Table 185 — Data Transmission functional unit
11.2 ReadDataByIdentifier (2216) service
11.2.1 Service description
11.2.2 Request message
11.2.2.1 Request message definition
Table 186 — Request message definition
11.2.2.2 Request message SubFunction parameter $Level (LEV_) Definition
11.2.2.3 Request message data-parameter definition
Table 187 — Request message data-parameter definition
11.2.2.2 Request message SubFunction parameter $Level (LEV_) Definition
11.2.2.3 Request message data-parameter definition
Table 187 — Request message data-parameter definition
11.2.3 Positive response message
11.2.3.1 Positive response message definition
Table 188 — Positive response message definition
11.2.3.2 Positive response message data-parameter definition
Table 189 — Response message data-parameter definition
11.2.4 Supported negative response codes (NRC_)
Table 190 — Supported negative response codes
Figure 20 — NRC handling for ReadDataByIdentifier service
11.2.5 Message flow example ReadDataByIdentifier
11.2.5.1 Assumptions
11.2.5 Message flow example ReadDataByIdentifier
11.2.5.1 Assumptions
11.2.5.2 Example #1: read single dataIdentifier F19016 (VIN number)
Table 192 — ReadDataByIdentifier positive response message flow example #1
11.2.5.3 Example #2: Read multiple dataIdentifiers 010A16 and 011016
Table 194 — ReadDataByIdentifier positive response message flow example #2
11.3 ReadMemoryByAddress (2316) service
11.3.1 Service description
11.3.2 Request message
11.3.2.1 Request message definition
11.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.3.2.3 Request message data-parameter definition
11.3.3 Positive response message
11.3.3.1 Positive response message definition
11.3.3 Positive response message
11.3.3.1 Positive response message definition
11.3.3.2 Positive response message data-parameter definition
Table 198 — Response message data-parameter definition
11.3.4 Supported negative response codes (NRC_)
Table 199 — Supported negative response codes
11.3.5 Message flow example ReadMemoryByAddress
11.3.5.1 Assumptions
11.3.5.2 Example #1: ReadMemoryByAddress - 4-byte (32-bit) addressing
Table 201 — ReadMemoryByAddress positive response message flow example #1
11.3.5.3 Example #2: ReadMemoryByAddress - 2-byte (16-bit) addressing.
11.3.5.4 Example #3: ReadMemoryByAddress, 3-byte (24-bit) addressing
11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description
11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description
11.4.2 Request message
11.4.2.1 Request message definition
Table 206 — Request message definition
11.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.4.2.3 Request message data-parameter definition
Table 207 — Request message data-parameter definition
11.4.3 Positive response message
11.4.3.1 Positive response message definition
Table 208 — Positive response message definition
11.4.3.2 Positive response message data-parameter definition
Table 209 — Response message data-parameter definition
11.4.4 Supported negative response codes (NRC_)
Table 210 — Supported negative response codes
11.4.5 Message flow example ReadScalingDataByIdentifier
11.4.5.1 Assumptions
11.4.5.2 Example #1: readScalingDataByIdentifier wth dataIdentifier F19016 (VIN number)
Table 211 — ReadScalingDataByIdentifier request message flow example #1
11.4.5.2 Example #1: readScalingDataByIdentifier wth dataIdentifier F19016 (VIN number)
Table 211 — ReadScalingDataByIdentifier request message flow example #1
Table 212 — ReadScalingDataByIdentifier positive response message flow example #1
11.4.5.3 Example #2: readScalingDataByIdentifier wth dataIdentifier 010516 (Vehicle Speed)
Table 214 — ReadScalingDataByIdentifier positive response message flow example #2
11.4.5.4 Example #3: readScalingDataByIdentifier wth dataIdentifier 096716
Table 215 — Example data definition
Table 216 — ReadScalingDataByIdentifier request message flow example #3
Table 216 — ReadScalingDataByIdentifier request message flow example #3
Table 217 — ReadScalingDataByIdentifier positive response message flow example #3
11.5 ReadDataByPeriodicIdentifier (2A16) service
11.5.1 Service description
11.5.2 Request message
11.5.2.1 Request message definition
11.5.2 Request message
11.5.2.1 Request message definition
11.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.5.2.3 Request message data-parameter definition
Table 219 — Request message data-parameter definition
11.5.3 Positive response message
11.5.3.1 Positive response message definition
Table 220 — Positive response message definition
Table 221 — Periodic data response message data definition
Table 221 — Periodic data response message data definition
11.5.3.2 Positive response message data-parameter definition
Table 222 — Periodic message data-parameter definition
11.5.4 Supported negative response codes (NRC_)
Table 223 — Supported negative response codes
Figure 23 — NRC handling for ReadDataByPeriodicIdentifier service
11.5.5 Message flow example ReadDataByPeriodicIdentifier
11.5.5.1 General assumptions
11.5.5 Message flow example ReadDataByPeriodicIdentifier
11.5.5.1 General assumptions
11.5.5.2 Example #1 - Read multiple periodicDataIdentifiers E316 and 2416 at medium rate
11.5.5.2.1 Assumptions
11.5.5.2.2 Step #1: Request periodic transmission of the periodicDataIdentifiers
Table 224 — ReadDataByPeriodicIdentifier request message flow example – step #1
Table 225 — ReadDataByPeriodicIdentifier initial positive response message flow example – step #1
Table 226 — ReadDataByPeriodicIdentifier subsequent positive response message #1 flows – step #1
Table 227 — ReadDataByPeriodicIdentifier subsequent positive response message #2 flows – step #1
11.5.5.2.3 Step #2: Stop the transmission of the periodicDataIdentifiers
Table 228 — ReadDataByIdentifier request message flow example – step #2
Table 229 — ReadDataByIdentifier positive response message flow example – step #2
11.5.5.3 Example #2 - Graphical and tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.3.1 ReadDataByPeriodicIdentifier example overview
11.5.5.3.2 Example #2 – Read multiple periodicDataIdentifiers E316 and 2416 at medium rate
Table 231 — Example #2: Periodic scheduler table for scheduler type 2
11.5.5.4 Example #3 - Graphical and tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.4.1 ReadDataByPeriodicIdentifier example overview
11.5.5.4.2 Read multiple periodicDataIdentifiers at different periodic rates
Table 232 — Example #3: Periodic scheduler table for scheduler type 1
Table 232 — Example #3: Periodic scheduler table for scheduler type 1
11.5.5.5 Example #4 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.5 Example #4 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.6 Example #5 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
11.5.5.6 Example #5 - Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
Table 235 — Example #5: Periodic scheduler table
11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description
11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description
11.6.2 Request message
11.6.2.1 Request message definition
Table 236 — Request message definition - SubFunction = defineByIdentifier
Table 237 — Request message definition - SubFunction = defineByMemoryAddress
Table 237 — Request message definition - SubFunction = defineByMemoryAddress
11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 — Request message SubFunction parameter definition
11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 — Request message SubFunction parameter definition
11.6.2.3 Request message data-parameter definition
11.6.3 Positive response message
11.6.3.1 Positive response message definition
Table 241 — Positive response message definition
11.6.3.2 Positive response message data-parameter definition
Table 242 — Response message data-parameter definition
11.6.4 Supported negative response codes (NRC_)
Table 243 — Supported negative response codes
11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions
11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions
Table 244 — Composite data blocks - DataIdentifier definitions
Table 245 — Elemental data records - DID definitions
Table 246 — Memory data records - Memory address definitions
11.6.5.2 Example #1: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 247 — DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #1
Table 248 — DynamicallyDefineDataIdentifier positive response DDDDI F30116 message flow example #1
Table 249 — ReadDataByIdentifier request DDDDI F30116 message flow example #1
11.6.5.3 Example #2: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 251 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #2
Table 253 — ReadDataByIdentifier request DDDDI F30216 message flow example #2
11.6.5.4 Example #3: DynamicallyDefineDataIdentifier, SubFunction = defineByMemoryAddress
Table 255 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3
Table 255 — DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3
Table 257 — ReadDataByIdentifier request DDDDI F30216 message flow example #3
Table 258 — ReadDataByIdentifier positive response DDDDI F30216 message flow example #3
11.6.5.5 Example #4: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 259 — DynamicallyDefineDataIdentifier request DDDDI F2E716 message flow example #4
Table 260 — DynamicallyDefineDataIdentifier positive response DDDDI F2E716 message flow example #4
Table 262 — ReadDataByPeriodicIdentifier initial positive message flow example #4
Table 263 — ReadDataByPeriodicIdentifier periodic data response #1 DDDDI F2E716 message flow example #4
Table 264 — ReadDataByPeriodicIdentifier periodic data response #n DDDDI F2E716 message flow example #4
11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 — DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5
11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 — DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5
Table 266 — DynamicallyDefineDataIdentifier positive response clear DDDDI F30316 message flow example #5
11.6.5.7 Example #6: DynamicallyDefineDataIdentifier, concatenation of definitions (defineByIdentifier/defineByAddress)
11.6.5.7.1 Step #1: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier (1 st portion)
Table 267 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier)
Table 267 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier)
Table 268 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6 definition of first portion (defineByIdentifier)
11.6.5.7.2 Step #2: DynamicallyDefineDataIdentifier, SubFunction = defineByMemoryAddress (2 nd portion)
Table 269 — DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #6 definition of 2nd portion (defineByMemoryAddress)
Table 270 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.3 Step #3: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier (3 rd portion)
Table 271 — DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 3rd portion (defineByIdentifier)
Table 272 — DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.4 Step #4: ReadDataByIdentifier - dataIdentifier = DDDDI F30116
Table 273 — ReadDataByIdentifier request DDDDI F30116 message flow example #6
Table 274 — ReadDataByIdentifier positive response DDDDI F30116 message flow example #6
11.6.5.7.5 Step #5: DynamicallyDefineDataIdentifier - clear definition of DDDDI F30116
Table 275 — DynamicallyDefineDataIdentifier request clear DDDDI F30116 message flow example #6
Table 276 — DynamicallyDefineDataIdentifier positive response clear DDDDI F30116 message flow example #6
11.7 WriteDataByIdentifier (2E16) service
11.7.1 Service description
11.7.2 Request message
11.7.2.1 Request message definition
Table 277 — Request message definition
11.7.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.7.2.3 Request message data-parameter definition
Table 278 — Request message data-parameter definition
11.7.3 Positive response message
11.7.3.1 Positive response message definition
Table 279 — Positive response message definition
11.7.3.2 Positive response message data-parameter definition
Table 280 — Response message data-parameter definition
11.7.4 Supported negative response codes (NRC_)
Table 281 — Supported negative response codes
11.7.4 Supported negative response codes (NRC_)
Table 281 — Supported negative response codes
Figure 26 — NRC handling for WriteDataByIdentifier service
11.7.5 Message flow example WriteDataByIdentifier
11.7.5.1 Assumptions
11.7.5.2 Example #1: write dataIdentifier F19016 (VIN)
11.8 WriteMemoryByAddress (3D16) service
11.8.1 Service description
11.8.2 Request message
11.8.2.1 Request message definition
Table 284 — Request message definition
11.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.8.2.3 Request message data-parameter definition
Table 285 — Request message data-parameter definition
11.8.3 Positive response message
11.8.3.1 Positive response message definition
Table 286 — Positive response message definition
11.8.3.2 Positive response message data-parameter definition
Table 287 — Response message data-parameter definition
11.8.3.2 Positive response message data-parameter definition
Table 287 — Response message data-parameter definition
11.8.4 Supported negative response codes (NRC_)
Table 288 — Supported negative response codes
Figure 27 — NRC handling for WriteMemoryByAddress service
11.8.5 Message flow example WriteMemoryByAddress
11.8.5.1 Assumptions
11.8.5.2 Example #1: WriteMemoryByAddress, 2-byte (16-bit) addressing
11.8.5 Message flow example WriteMemoryByAddress
11.8.5.1 Assumptions
11.8.5.2 Example #1: WriteMemoryByAddress, 2-byte (16-bit) addressing
Table 289 — WriteMemoryByAddress request message flow example #1
Table 290 — WriteMemoryByAddress positive response message flow example #1
11.8.5.3 Example #2: WriteMemoryByAddress, 3-byte (24-bit) addressing
Table 291 — WriteMemoryByAddress request message flow example #2
Table 292 — WriteMemoryByAddress positive response message flow example #2
11.8.5.4 Example #3: WriteMemoryByAddress, 4-byte (32-bit) addressing
Table 293 — WriteMemoryByAddress request message flow example #3
Table 294 — WriteMemoryByAddress positive response message flow example #3
12 Stored data transmission functional unit
12.1 Overview
Table 295 — Stored data transmission functional unit
12.2 ClearDiagnosticInformation (1416) service
12.2.1 Service description
12.2.2 Request message
12.2.2.1 Request message definition
12.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
12.2.2.3 Request message data-parameter definition
Table 297 — Request message data-parameter definition
12.2.3 Positive response message
12.2.3.1 Positive response message definition
12.2.3.2 Positive response message data-parameter definition
12.2.4 Supported negative response codes (NRC_)
Table 299 — Supported negative response codes
12.2.5 Message flow example ClearDiagnosticInformation
Table 301 — ClearDiagnosticInformation positive response message flow example #1
12.3 ReadDTCInformation (1916) service
12.3.1 Service description
12.3.1.1 General description
12.3.1.2 Retrieving the number of DTCs that match a client defined status mask (SubFunction = 0116 reportNumberOfDTCByStatusMask)
12.3.1.3 Retrieving the list of DTCs that match a client defined status mask (SubFunction = 0216 reportDTCByStatusMask)
12.3.1.4 Retrieving DTCSnapshot record identification (SubFunction = 0316 reportDTCSnapshotIdentification)
12.3.1.5 Retrieving DTCSnapshot record data for a client defined DTC mask (SubFunction = 0416 reportDTCSnapshotRecordByDTCNumber)
12.3.1.6 Retrieving DTCStoredData record data for a client defined record number (SubFunction = 0516 reportDTCStoredDataByRecordNumber)
12.3.1.7 Retrieving DTCExtendedData record data for a client defined DTC mask and a client defined DTCExtendedData record number (SubFunction = 0616 reportDTCExtDataRecordByDTCNumber)
12.3.1.8 Retrieving the number of DTCs that match a client defined severity mask record (SubFunction = 0716 reportNumberOfDTCBySeverityMaskRecord)
12.3.1.9 Retrieving severity and functional unit information that match a client defined severity mask record (SubFunction = 0816 reportDTCBySeverityMaskRecord)
12.3.1.10 Retrieving severity and functional unit information for a client defined DTC (SubFunction = 0916 reportSeverityInformationOfDTC)
12.3.1.10 Retrieving severity and functional unit information for a client defined DTC (SubFunction = 0916 reportSeverityInformationOfDTC)
12.3.1.11 Retrieving the status of all DTCs supported by the server (SubFunction = 0A16 reportSupportedDTC)
12.3.1.12 Retrieving the first/most recent failed DTC (SubFunction = 0B16 reportFirstTestFailedDTC, SubFunction = 0D16 reportMostRecentTestFailedDTC)
12.3.1.13 Retrieving the first/most recently detected confirmed DTC (SubFunction = 0C16 reportFirstConfirmedDTC,SubFunction = 0E16 reportMostRecentConfirmedDTC)
12.3.1.14 Retrieving a list of "prefailed" DTC status (SubFunction = 1416 reportDTCFaultDetection-Counter)
12.3.1.15 Retrieving a list of DTCs with "permanent DTC" status (SubFunction = 1516 reportDTCWithPermanentStatus)
12.3.1.16 Retrieving DTCExtendedData record data for a client defined DTCExtendedData record number (SubFunction = 1616 reportDTCExtDataRecordByRecordNumber)
12.3.1.17 Retrieving the list of DTCs out of the server's user defined DTC memory that match a client defined DTC status mask (SubFunction = 1716 reportUserDefMemoryDTCByStatusMask)
12.3.1.17 Retrieving the list of DTCs out of the server's user defined DTC memory that match a client defined DTC status mask (SubFunction = 1716 reportUserDefMemoryDTCByStatusMask)
12.3.1.18 Retrieving user defined memory DTCSnapshot record data for a client defined DTC mask and a client defined DTCSnapshotNumber out of the DTC user defined memory (SubFunction = 1816 reportUserDefMemoryDTCSnapshotRecordByDTCNumber)
12.3.1.19 Retrieving user defined memory DTCExtendedData record data for a client defined DTC mask and a client defined DTCExtendedData record number out of the DTC memory (SubFunction = 1916 reportUserDefMemoryDTCExtDataRecordByDTCNumber)
12.3.1.20 Retrieving the list of all DTCs that supports an specific DTCExtendedDataRecord (SubFunction = 1A16 reportSupportedDTCExtDataRecord)
12.3.1.21 Retrieving the list of VOBD DTCs from a functional group that match a client defined status mask (SubFunction = 4216 reportWWHOBDDTCByMaskRecord)
12.3.1.22 Retrieving a list of VOBD DTCs with "permanent DTC" status (SubFunction = 5516 reportWWHOBDDTCWithPermanentStatus)
12.3.1.23 Retrieve DTC information for a client defined DTCReadinessGroupIdentifier (SubFunction = 5616 reportDTCInformationByDTCReadinessGroupIdentifier)
12.3.2 Request message
12.3.2.1 Request message definition
Table 305 — Request message definition - SubFunction = reportDTCExtDataRecordByDTCNumber
Table 306 — Request message definition - SubFunction = reportNumberOfDTCBySeverityMaskRecord, reportDTCSeverityInformation
Table 307 — Request message definition - SubFunction = reportSeverityInformationOfDTC
Table 308 — Request message definition - SubFunction = reportSupportedDTC, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCFaultDetectionCounter, reportDTCWithPermanentStatus
Table 309 — Request message definition - SubFunction = reportDTCExtDataRecordByRecordNumber
Table 310 — Request message definition - SubFunction = reportUserDefMemoryDTCByStatusMask
Table 311 — Request message definition - SubFunction = reportUserDefMemoryDTCSnapshotRecordByDTCNumber
Table 313 — Request message definition - SubFunction = reportSupportedDTCExtDataRecord
Table 314 — Request message definition - SubFunction = reportWWHOBDDTCByMaskRecord
Table 315 — Request message definition - SubFunction = reportWWHOBDDTCWithPermanentStatus
Table 316 — Request message definition - SubFunction = reportDTCInformationByDTCReadinessGroupIdentifier
12.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 317 — Request message SubFunction definition
12.3.2.3 Request message data-parameter definition
Table 318 — Request data-parameter definition
12.3.3 Positive response message
12.3.3.1 Positive response message definition
12.3.3 Positive response message
12.3.3.1 Positive response message definition
Table 319 — Response message definition - SubFunction = reportNumberOfDTCByStatusMask, reportNumberOfDTCBySeverityMaskRecord
Table 320 — Response message definition - SubFunction = reportDTCByStatusMask, reportSupportedDTCs, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCWithPermanentStatus
Table 322 — Response message definition - SubFunction = reportDTCSnapshotRecordByDTCNumber
Table 322 — Response message definition - SubFunction = reportDTCSnapshotRecordByDTCNumber
Table 328 — Response message definition - SubFunction = reportUserDefMemoryDTCByStatusMask
Table 330 — Response message definition - SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber
Table 330 — Response message definition - SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber
Table 333 — Response message definition - SubFunction = reportWWHOBDDTCWithPermanentStatus
12.3.3.2 Positive response message data-parameter definition
12.3.4 Supported negative response codes (NRC_)
Table 336 — Supported negative response codes
12.3.5 Message flow examples – ReadDTCInformation
12.3.5.1 General asumption
12.3.5.2 Example #1 - ReadDTCInformation, SubFunction = reportNumberOfDTCByStatusMask
12.3.5.2.1 Example #1 overview
12.3.5.2.2 Example #1 assumptions
Table 337 — statusOfDTC = 2416 of DTC P0805-11
Table 337 — statusOfDTC = 2416 of DTC P0805-11
Table 338 — statusOfDTC = 2616 of DTC P0A9B-17
Table 339 — statusOfDTC = 2F16 of DTC P2522-1F
12.3.5.2.3 Example #1 message flow
12.3.5.2.3 Example #1 message flow
Table 341 — ReadDTCInformation, SubFunction = reportNumberOfDTCByStatusMask, positive response, example #1
12.3.5.3 Example #2 - ReadDTCInformation, SubFunction = reportDTCByStatusMask, matching DTCs returned
12.3.5.3.1 Example #2 overview
12.3.5.3.2 Example #2 assumptions
12.3.5.3.2 Example #2 assumptions
Table 342 — statusOfDTC= 2416 of DTC P0A9B-17
Table 343 — statusOfDTC = 0016 of DTC P2522-1F
Table 344 — statusOfDTC = 2F16 of DTC P0805-11
12.3.5.3.3 Example #2 message flow
Table 345 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #2
Table 346 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, positive response, example #2
12.3.5.4 Example #3 - ReadDTCInformation, SubFunction = reportDTCByStatusMask, no matching DTCs returned
12.3.5.4.1 Example #3 overview
12.3.5.4.2 Example #3 assumptions
Table 347 — statusOfDTC= 2416 of DTC P2522-1F
Table 348 — statusOfDTC = 0016 of DTC P0A9B-17
12.3.5.4.3 Example #3 message flow
Table 349 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #3
Table 350 — ReadDTCInformation, SubFunction = reportDTCByStatusMask, positive response, example #3
12.3.5.5 Example #4 - ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification
12.3.5.5.1 Example #4 overview
12.3.5.5.2 Example #4 assumptions
12.3.5.5 Example #4 - ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification
12.3.5.5.1 Example #4 overview
12.3.5.5.2 Example #4 assumptions
12.3.5.5.3 Example #4 message flow
Table 351 — ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification, request message flow example #4
12.3.5.6 Example #5 - ReadDTCInformation, SubFunction = reportDTCSnapshotRecord-ByDTCNumber
12.3.5.6.1 Example #5 overview
12.3.5.6.2 Example #5 assumptions
Table 353 — DTCSnapshot record content
Table 353 — DTCSnapshot record content
12.3.5.6.3 Example #5 message flow
Table 354 — ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, request message flow example #5
Table 355 — ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, positive response, example #5
12.3.5.7 Example #6 - ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber
12.3.5.7.1 Example #6 overview
12.3.5.7.2 Example #6 assumptions
Table 356 — DTCStoredData record content
12.3.5.7.3 Example #6 message flow
Table 357 — ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber, request message flow example #6
12.3.5.7.3 Example #6 message flow
Table 357 — ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber, request message flow example #6
12.3.5.8 Example #7 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber
12.3.5.8.1 Example #7 overview
12.3.5.8.2 Example #7 assumptions
12.3.5.8 Example #7 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber
12.3.5.8.1 Example #7 overview
12.3.5.8.2 Example #7 assumptions
Table 359 — DTCExtDataRecordNumber 0516 content
Table 360 — DTCExtDataRecordNumber 1016 content
12.3.5.8.3 Example #7 message flow
Table 361 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber, request message flow example #7
Table 362 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber, positive response, example #7
12.3.5.9 Example #8 - ReadDTCInformation, SubFunction = reportNumberOfDTC-BySeverityMaskRecord
12.3.5.9.1 Example #8 overview
12.3.5.9.2 Example #8 assumptions
Table 363 — statusOfDTC = 2416 of DTC P0A9B-17
Table 363 — statusOfDTC = 2416 of DTC P0A9B-17
Table 364 — statusOfDTC = 0016 of DTC P2522-1F
Table 365 — statusOfDTC = 2F16 of DTC P0805-11
12.3.5.9.3 Example #8 message flow
Table 366 — ReadDTCInformation, SubFunction = reportNumberOfDTCBySeverityMaskRecord, request message flow example #8
Table 367 — ReadDTCInformation, SubFunction = reportNumberOfDTCBySeverityMaskRecord, positive response, example #8
12.3.5.10 Example #9 - ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord
12.3.5.10.1 Example #9 overview
12.3.5.10.2 Example #9 assumptions
12.3.5.10.3 Example #9 message flow
Table 368 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, request message flow example #9
Table 369 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, positive response, example #9
Table 369 — ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, positive response, example #9
12.3.5.11 Example #10 - ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC
12.3.5.11.1 Example #10 overview
12.3.5.11.2 Example #10 assumptions
12.3.5.11.3 Example #10 message flow
Table 370 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, request message flow example #10
Table 371 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10
Table 371 — ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10
12.3.5.12 Example #11 – ReadDTCInformation - SubFunction = reportSupportedDTCs
12.3.5.12.1 Example #11 overview
12.3.5.12.2 Example #11 assumptions
Table 372 — statusOfDTC = 2416
Table 373 — statusOfDTC = 0016
Table 374 — statusOfDTC = 2F16
12.3.5.12.3 Example #11 message flow
Table 375 — ReadDTCInformation, SubFunction = reportSupportedDTCs, request message flow example #11
Table 376 — ReadDTCInformation, SubFunction = readSupportedDTCs, positive response, example #11
Table 376 — ReadDTCInformation, SubFunction = readSupportedDTCs, positive response, example #11
12.3.5.13 Example #12 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, information available
12.3.5.13.1 Example #12 overview
12.3.5.13.2 Example #12 assumptions
Table 377 — statusOfDTC = 2616
Table 377 — statusOfDTC = 2616
12.3.5.13.3 Example #12 message flow
Table 378 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #12
Table 379 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #12
12.3.5.14 Example #13 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, no information available
12.3.5.14 Example #13 - ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, no information available
12.3.5.14.1 Example #13 overview
12.3.5.14.2 Example #13 assumptions
12.3.5.14.3 Example #13 message flow
Table 380 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #13
Table 381 — ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #13
12.3.5.15 Example #14 - ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter
12.3.5.15.1 Example #14 overview
12.3.5.15 Example #14 - ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter
12.3.5.15.1 Example #14 overview
12.3.5.15.2 Example #14 assumptions
12.3.5.15.3 Example #14 message flow
Table 382 — ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter, request message flow example #14
12.3.5.16 Example #15 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber
12.3.5.16.1 Example #15 overview
12.3.5.16 Example #15 - ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber
12.3.5.16.1 Example #15 overview
12.3.5.16.2 Example #15 assumptions
Table 384 — DTCExtDataRecordNumber 0516 content for DTC 12345616
Table 385 — DTCExtDataRecordNumber 0516 content for DTC 23456116
12.3.5.16.3 Example #15 message flow
Table 386 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15
12.3.5.16.3 Example #15 message flow
Table 386 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15
Table 387 — ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, positive response, example #15
12.3.5.17 Example #16 – ReadDTCInformation - SubFunction = reportDTCExtendedDataRecordIdentification
12.3.5.17.1 Example #16 overview
12.3.5.17.2 Example #16 assumptions
12.3.5.17.3 Example #16 message flow
Table 388 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16
Table 388 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16
Table 389 — ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, positive response, example #16
12.3.5.18 Example #17 - ReadDTCInformation, SubFunction = reportWWHOBDDTCByMaskRecord
12.3.5.18.1 Example #17 overview
12.3.5.18 Example #17 - ReadDTCInformation, SubFunction = reportWWHOBDDTCByMaskRecord
12.3.5.18.1 Example #17 overview
12.3.5.18.2 Example #17 assumptions
12.3.5.18.3 Example #17 message flow
Table 390 — ReadDTCInformation request, SubFunction = reportNumberOfDTCByStatusMask
Table 392 — ReadDTCInformation response, SubFunction = reportOBDDTCByStatusMask
12.3.5.19 Example #18 - ReadDTCInformation, SubFunction = reportOBDDTCWithPermanentStatus, matching DTCs returned
12.3.5.19.1 Example #18 overview
12.3.5.19.2 Example #18 assumptions
12.3.5.19 Example #18 - ReadDTCInformation, SubFunction = reportOBDDTCWithPermanentStatus, matching DTCs returned
12.3.5.19.1 Example #18 overview
12.3.5.19.2 Example #18 assumptions
12.3.5.19.3 Example #18 message flow
Table 394 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, request message flow example #2
Table 395 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18
Table 395 — ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18
12.3.5.20 Example #19 – ReadDTCInformation - SubFunction = reportDTCByReadinessGroupIdentifier
12.3.5.20.1 Example #19 overview
12.3.5.20.2 Example #19 assumptions
12.3.5.20.3 Example #19 message flow
Table 396 — ReadDTCInformation, SubFunction = reportDTCByReadinessGroupIdentifier, request message flow, example #19
13 InputOutput control functional unit
13.1 Overview
Table 398 — InputOutput Control functional unit
13.2 InputOutputControlByIdentifier (2F16) service
13 InputOutput control functional unit
13.1 Overview
Table 398 — InputOutput Control functional unit
13.2 InputOutputControlByIdentifier (2F16) service
13.2.1 Service description
13.2.2 Request message
13.2.2.1 Request message definition
13.2.2 Request message
13.2.2.1 Request message definition
13.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
13.2.2.3 Request message data-parameter definition
Table 400 — Request message data-parameter definition
13.2.3 Positive response message
13.2.3.1 Positive response message definition
Table 401 — Positive response message definition
13.2.3.2 Positive response message data-parameter definition
Table 402 — Response message data-parameter definition
13.2.4 Supported negative response codes (NRC_)
Table 403 — Supported negative response codes
Figure 29 — NRC handling for InputOutputControlByIdentifier service
13.2.5 Message flow example(s) InputOutputControlByIdentifier
13.2.5.1 Assumptions
13.2.5.2 Example #1 - "Air Inlet Door Position" shortTermAdjustment
13.2.5.2.1 Step #1: ReadDataByIdentifier
13.2.5.2 Example #1 - "Air Inlet Door Position" shortTermAdjustment
13.2.5.2.1 Step #1: ReadDataByIdentifier
13.2.5.2.2 Step #2: shortTermAdjustment
Table 407 — InputOutputControlByIdentifier positive response message flow example #1 - step #2
13.2.5.2.3 Step #3: ReadDataByIdentifier
Table 408 — ReadDataByIdentifier request message flow example #1 - step #3
Table 409 — ReadDataByIdentifier positive response message flow example #1 - step #3
13.2.5.2.4 Step #4: returnControlToECU
13.2.5.2.4 Step #4: returnControlToECU
13.2.5.2.5 Step #5: freezeCurrentState
Table 413 — InputOutputControlByIdentifier positive response message flow example #1 - step #5
13.2.5.3 Example #2 – EGR and IAC shortTermAdjustment
13.2.5.3.1 Assumptions
Table 414 — Composite data blocks – DataIdentifier definitions – Example #2
Table 415 — ControlEnableMaskRecord– Example #2
13.2.5.3.2 Case #1: Control IAC Pintle Position only
Table 416 — InputOutputControlByIdentifier request message flow example #2 – Case #1
Table 417 — InputOutputControlByIdentifier positive response message flow example #2 – Case #1
13.2.5.3.3 Case #2: Control RPM Only
Table 418 — InputOutputControlByIdentifier request message flow example #2 – Case #2
Table 419 — InputOutputControlByIdentifier positive response message flow example #2 – Case #2
Table 419 — InputOutputControlByIdentifier positive response message flow example #2 – Case #2
13.2.5.3.4 Case #3: Control both Pedal Position A and EGR Duty Cycle
Table 420 — InputOutputControlByIdentifier request message flow example #2 – Case #3
Table 421 — InputOutputControlByIdentifier positive response message flow example #2 – Case #3
13.2.5.3.5 Case #4: Return control of all parameters to the ECU
Table 422 — InputOutputControlByIdentifier request message flow example #2 – Case #4
14 Routine functional unit
14.1 Overview
Table 424 — Routine functional unit
14.2 RoutineControl (3116) service
14.2.1 Service description
14.2.1.1 Overview
14.2.1.1 Overview
14.2.1.2 Start a routine referenced by a routineIdentifier
14.2.1.3 Stop a routine referenced by a routineIdentifier
14.2.1.4 Request routine results referenced by a routineIdentifier
14.2.2 Request message
14.2.2.1 Request message definition
Table 425 — Request message definition
14.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 426 — Request message SubFunction definition
14.2.2.3 Request message data-parameter definition
Table 427 — Request message data-parameter definition
14.2.3 Positive response message
14.2.3.1 Positive response message definition
Table 428 — Positive response message definition
14.2.3.2 Positive response message data-parameter definition
Table 429 — Response message data-parameter definition
14.2.4 Supported negative response codes (NRC_)
Table 430 — Supported negative response codes
Figure 30 — NRC handling for RoutineControl service
14.2.5 Message flow example(s) RoutineControl
14.2.5.1 Example #1: SubFunction = startRoutine
Table 431 — RoutineControl request message flow - example #1
Table 431 — RoutineControl request message flow - example #1
Table 432 — positive response message flow - example #1
14.2.5.2 Example #2: SubFunction = stopRoutine
Table 433 — RoutineControl request message flow - example #2
Table 434 — RoutineControl positive response message flow - example #2
14.2.5.3 Example #3: SubFunction = requestRoutineResults
Table 435 — RequestRoutineResults request message flow – example #3
14.2.5.4 Example #4: SubFunction = startRoutine with routineControlOption
Table 437 — RoutineControl request message flow - example #4
Table 438 — RoutineControl positive response message flow - example #4
15 Upload download functional unit
15.1 Overview
Table 439 — Upload Download functional unit
15.2 RequestDownload (3416) service
15.2.1 Service description
15.2.2 Request message
15.2.2.1 Request message definition
Table 440 — Request message definition
15.2.2 Request message
15.2.2.1 Request message definition
Table 440 — Request message definition
15.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.2.2.3 Request message data-parameter definition
Table 441 — Request message data-parameter definition
15.2.3 Positive response message
15.2.3.1 Positive response message definition
Table 442 — Positive response message definition
15.2.3.2 Positive response message data-parameter definition
Table 443 — Response message data-parameter definition
15.2.4 Supported negative response codes (NRC_)
Figure 31 — NRC handling for RequestDownload service
15.2.5 Message flow example(s) RequestDownload
15.3 RequestUpload (3516) service
15.3.1 Service description
15.3.2 Request message
15.3.2.1 Request message definition
15.3.2 Request message
15.3.2.1 Request message definition
Table 445 — Request message definition
15.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.3.2.3 Request message data-parameter definition
15.3.3 Positive response message
15.3.3.1 Positive response message definition
Table 447 — Positive response message definition
15.3.3.2 Positive response message data-parameter definition
Table 448 — Response message data-parameter definition
15.3.4 Supported negative response codes (NRC_)
Table 449 — Supported negative response codes
Figure 32 — NRC handling for RequestUpload service
15.3.5 Message flow example(s) RequestUpload
15.4 TransferData (3616) service
15.4.1 Service description
15.4 TransferData (3616) service
15.4.1 Service description
15.4.2 Request message
15.4.2.1 Request message definition
Table 450 — Request message definition
15.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.4.2.3 Request message data-parameter definition
15.4.3 Positive response message
15.4.3.1 Positive response message definition
Table 452 — Positive response message definition
15.4.3.2 Positive response message data-parameter definition
Table 453 — Response message data-parameter definition
15.4.3.2 Positive response message data-parameter definition
Table 453 — Response message data-parameter definition
15.4.4 Supported negative response codes (NRC_)
Table 454 — Supported negative response codes
Figure 33 — NRC handling for TransferData service
15.4.5 Message flow example(s) TransferData
15.5 RequestTransferExit (3716) service
15.5.1 Service description
15.5.2 Request message
15.5.2.1 Request message definition
Table 455 — Request message definition
15.5.2 Request message
15.5.2.1 Request message definition
Table 455 — Request message definition
15.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.5.2.3 Request message data-parameter definition
Table 456 — Request message data-parameter definition
15.5.3 Positive response message
15.5.3.1 Positive response message definition
Table 457 — Positive response message definition
15.5.3.2 Positive response message data-parameter definition
15.5.4 Supported negative response codes (NRC_)
Table 459 — Supported negative response codes
15.5.5 Message flow example(s) for downloading/uploading data
15.5.5.1 Download data to a server
15.5.5.1.1 Assumptions
Table 460 — Definition of transferRequestParameter values
Table 461 — Definition of transferResponseParameter value
Table 461 — Definition of transferResponseParameter value
15.5.5.1.2 Step #1: Request for download
Table 462 — RequestDownload request message flow example
Table 463 — RequestDownload positive response message flow example
Table 463 — RequestDownload positive response message flow example
15.5.5.1.3 Step #2: Transfer data
Table 464 — TransferData request message flow example
Table 465 — TransferData positive response message flow example
Table 467 — TransferData positive response message flow example
Table 467 — TransferData positive response message flow example
15.5.5.1.4 Step #3: Request Transfer exit
Table 468 — RequestTransferExit request message flow example
Table 469 — RequestTransferExit positive response message flow example
15.5.5.2 Upload data from a server
15.5.5.2.1 Step #1: Request for upload
Table 472 — RequestUpload request message flow example
Table 473 — RequestUpload positive response message flow example
Table 473 — RequestUpload positive response message flow example
15.5.5.2.2 Step #2: Transfer data
Table 474 — TransferData request message flow example
Table 475 — TransferData positive response message flow example
Table 477 — TransferData positive response message flow example
15.5.5.2.3 Step #3: Request Transfer exit
Table 479 — RequestTransferExit positive response message flow example
Table 479 — RequestTransferExit positive response message flow example
15.6 RequestFileTransfer (3816) service
15.6.1 Service description
15.6.2 Request message
15.6.2.1 Request message definition
Table 480 — Request message definition
15.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.6.2.3 Request message data-parameter definition
15.6.3 Positive response message
15.6.3.1 Positive response message definition
Table 482 — Positive response message definition
15.6.3.2 Positive response message data-parameter definition
Table 483 — Response message data-parameter definition
15.6.4 Supported negative response codes (NRC_)
Table 484 — Supported negative response codes
Figure 35 — NRC handling for requestFileTransfer service
15.6.5 Message flow example(s) RequestFileTransfer
15.6.5.1 Assumptions
Table 485 — Definition RequestFileTransfer message parameter values
15.6.5.2 Request file transfer
Table 486 — RequestFileTransfer request message example
Table 487 — RequestFileTransfer positive response request message example
16 Security sub-layer definition
16.1 General
16.1.1 Purpose
16.1.2 Security sub-layer description
Figure 36 — Security sub-layer implementation
Figure 36 — Security sub-layer implementation
16.1.3 Security sub-layer access
Figure 37 — Physical communication during defaultSession - with SOM.ind and security sub-layer
Figure 38 — Physical communication during defaultSession - with enhanced response timing and security sub-layer
16.1.4 General server response behaviour
16.2 SecuredDataTransmission (8416) service
16.2.1 Service description
16.2 SecuredDataTransmission (8416) service
16.2.1 Service description
16.2.2 Request message
16.2.2.1 Request message definition
Table 488 — Request message definition
16.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
16.2.2.3 Request message data-parameter definition
Table 489 — Request message data-parameter definition
16.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
16.2.2.3 Request message data-parameter definition
Table 489 — Request message data-parameter definition
Table 490 — Definition of Administrative Parameter
16.2.3 Positive response message for successful internal message
16.2.3.1 Positive response message definition for successful internal message
Table 492 — Positive response message definition
16.2.3.2 Positive response message data-parameter definition
Table 493 — Response message data-parameter definition
16.2.3.2 Positive response message data-parameter definition
Table 493 — Response message data-parameter definition
16.2.3.3 Positive response message definition for unsuccessful internal message
Table 494 — Positive response message definition
16.2.3.4 Positive response message data-parameter definition
Table 495 — Response message data-parameter definition
16.2.4 Supported negative response codes (NRC_)
Table 496 — Supported negative response codes
16.2.5 Message flow example SecuredDataTransmission
16.2.5.1 Assumptions
16.2.5.2 Example #1: SecuredDataTransmission to Write DID
Table 497 — SecuredDataTransmission request message flow example #1
16.2.5.3 Example #2: SecuredDataTransmission to Write DID
Table 499 — SecuredDataTransmission request message flow example #2
Table 499 — SecuredDataTransmission request message flow example #2
Table 500 — SecuredDataTransmission response message flow example #2
17 Non-volatile server memory programming process
17.1 General information
17.2 Detailed programming sequence
17.2 Detailed programming sequence
17.2.1 Programming phase #1 — Download of application software and/or application data
17.2.1.1 Pre-Programming step of phase #1 — Setup of vehicle network for programming
17.2.1.2 Programming step of phase #1 — Download of application software and data
17.2.1.2 Programming step of phase #1 — Download of application software and data
17.2.1.3 Post-Programming step of phase #1 — Re-synchronisation of vehicle network
17.2.1.3 Post-Programming step of phase #1 — Re-synchronisation of vehicle network
Figure 43 — Post-programming step of phase 1 (STP3)
17.2.1.4 Preprogramming step of phase #2 — Server configuration
Figure 44 — Preprogramming step of phase 2 (STP4)
17.2.1.5 Programming step of phase #2 — Final server configuration
Figure 45 — Programming step of phase 2 (STP5)
17.2.1.6 Post-programming step of phase #2 — Re-synchronisation of vehicle network
17.3 Server reprogramming requirements
17.3 Server reprogramming requirements
17.3.1 Requirements for servers to support programming
17.3.1.1 Boot software description and requirements
17.3.1.1.1 Boot software general requirements
17.3.1.1.2 Boot software diagnostic service requirements
Table 503 — Boot software diagnostic service support during post-programming step of phase #1
17.3.1.2 Security requirements
17.3.2 Software, data identification and fingerprints
17.3.2.1 Software and data identification
17.3.2.2 Software and data fingerprints
17.3.2.2 Software and data fingerprints
17.3.3 Server routine access
Table 504 — routineIdentifiers for non-volatile memory access
17.4 Non-volatile server memory programming message flow examples
17.4.1 General information
17.4.2 Programming phase #1 — Pre-Programming step
Table 505 — StartDiagnosticSessionControl(extendedSession)
Table 506 — ControlDTCSetting(off)
Table 507 — CommunicationControl(disableRxAndTx in the application)
17.4.3 Programming phase #1 — Programming step
Table 508 — DiagnosticSessionControl(programmingSession)
Table 509 — SecurityAccess(requestSeed)
Table 510 — SecurityAccess(sendKey)
Table 511 — RoutineControl(eraseMemory)
Table 512 — RequestDownload — Module #1
Table 513 — TransferData — Module #1 (block #1)
Table 514 — TransferData — Module #1 (block #2)
Table 516 — RequestTransferExit — Module #1
Table 517 — RequestDownload — Module #2
Table 518 — TransferData — Module #2 (block #1)
Table 519 — TransferData — Module #2 (block #2)
Table 520 — TransferData — Module #2 (block #3)
Table 521 — RequestTransferExit — Module #2
Table 522 — RoutineControl(validate application)
Table 523 — WriteDataByIdentifier — dataIdentifier = VIN
17.4.4 Programming phase #1 — Post-Programming step
Annex A (normative) Global parameter definitions
A.1 Negative response codes
Annex B (normative) Diagnostic and communication management functional unit data-parameter definitions
B.1 communicationType parameter definition
Table B.1 — Definition of communicationType and subnetNumber byte
B.2 eventWindowTime parameter definition
B.3 linkControlModeIdentifier parameter definition
Table B.3 — Definition of linkControlModeIdentifier values
B.3 linkControlModeIdentifier parameter definition
Table B.3 — Definition of linkControlModeIdentifier values
B.4 nodeIdentificationNumber parameter definition
B.4 nodeIdentificationNumber parameter definition
B.5 AuthenticationReturnParameter definitions
Table B.5 — authenticationReturnParameter definitions
Annex C (normative) Data transmission functional unit data-parameter definitions
C.1 DID parameter definitions
Table C.1 — DID data-parameter definitions
C.2 scalingByte parameter definitions
Table C.3 — scalingByte (Low Nibble) parameter definition
C.3 scalingByteExtension parameter definitions
C.3.1 scalingByteExtension for scalingByte high nibble of bitMappedReportedWithOutMask
Table C.4 — scalingByteExtension for bitMappedReportedWithOutMask
C.3.2 scalingByteExtension for scalingByte high nibble of formula
Table C.5 — scalingByteExtension Bytes for formula
Table C.6 — formulaIdentifier encoding
Table C.7 — Two byte real number format
C.3.3 scalingByteExtension for scalingByte high nibble of unit/format
C.3.3 scalingByteExtension for scalingByte high nibble of unit/format
Table C.8 — Unit/format scalingByteExtension encoding
C.3.4 scalingByteExtension for scalingByte high nibble of stateAndConnectionType
Table C.9 — Encoding of scalingByte High Nibble of stateAndConnectionType
Table C.9 — Encoding of scalingByte High Nibble of stateAndConnectionType
C.4 transmissionMode parameter definitions
Table C.10 — transmissionMode parameter definitions
C.5 Coding of UDS edition version number
Table C.11 — Coding of UDS edition version number DID FF0016 – 4 bytes unsigned value
Table C.12 — DID FF0016 UDS edition version values of this document
Annex D (normative) Stored data transmission functional unit data-parameter definitions
D.1 groupOfDTC parameter definition
Table D.1 — Definition of groupOfDTC and range of DTC numbers
D.2 DTCStatusMask and statusOfDTC bit definitions
D.2.1 Convention and definition
D.2.2 Pseudocode data dictionary
Table D.2 — Pseudocode data dictionary
D.2.3 DTC status bit definitions
Table D.4 — DTC status bit 1 testFailedThisOperationCycle definitions
Table D.6 — DTC status bit 3 confirmedDTC definitions
Table D.7 — DTC status bit 4 testNotCompletedSinceLastClear definitions
Figure D.8 — DTC status bit 7 WarningIndicator requested logic
D.2.4 Example for operation of DTC Status Bits
D.3 DTC severity and class definition
D.3.1 DTC severity and class byte definition
Table D.11 — DTCSeverityMask/DTCSeverity byte definition
D.3.2 DTC severity bit definition
Table D.12 — DTC severity bit definitions (bit 7 to 5)
D.3.3 DTC class definition
Table D.13 — GTR DTC Class definition (bit 4 to 0)
D.4 DTCFormatIdentifier definition
Table D.14 — Definition of DTCFormatIdentifier (DTCFID_)
D.5 FunctionalGroupIdentifier definition
Table D.15 — Definition of FunctionalGroupIdentifiers (FGID_)
D.6 DTCFaultDetectionCounter operation implementation example
D.7 DTCAgingCounter example
D.7 DTCAgingCounter example
D.8 DTCExtendedDataRecordNumber value definition
Table D.16 — DTCExtendedDataRecordNumber value definition
Annex E (normative) Input output control functional unit data-parameter definitions
Annex F (normative) Routine functional unit data-parameter definitions
Annex G (normative) Upload and download functional unit data-parameter
Table G.1 — Definition of modeOfOperation values
Annex H (informative) Examples for addressAndLengthFormatIdentifier parameter values
Table H.1 — addressAndLengthFormatIdentifier example
Annex I (normative) Security access state chart
I.1 General
I.2 Disjunctive normal form based state transition definitions
Table I.1 — State transitions – parameters
Annex J (informative) Recommended implementation for multiple client environments
J.1 Introduction
J.2 Implementation specific limitations
J.3 Use cases relevant for system design
Figure J.1 — Example vehicle topology with onboard clients
Table J.1 — Use case (UC) matrix of multiple client scenarios to be addressed
J.4 Use case evaluation
J.4 Use case evaluation
Table J.2 — Evaluation of multiple client use cases
J.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol
J.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol
J.5.2 Assumptions
J.5.3 Multiple client handling flow
Bibliography
Blank Page