{"id":258556,"date":"2024-10-19T17:07:03","date_gmt":"2024-10-19T17:07:03","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-14229-12020\/"},"modified":"2024-10-25T12:44:46","modified_gmt":"2024-10-25T12:44:46","slug":"bs-iso-14229-12020","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-14229-12020\/","title":{"rendered":"BS ISO 14229-1:2020"},"content":{"rendered":"

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
2<\/td>\nundefined <\/td>\n<\/tr>\n
11<\/td>\nForeword <\/td>\n<\/tr>\n
12<\/td>\nIntroduction <\/td>\n<\/tr>\n
15<\/td>\n1 Scope
2 Normative references
3 Terms and definitions <\/td>\n<\/tr>\n
16<\/td>\n3 Terms and definitions <\/td>\n<\/tr>\n
19<\/td>\n4 Symbols and abbreviated terms
5 Conventions <\/td>\n<\/tr>\n
20<\/td>\nFigure 1 \u2014 The services and the protocol
6 Document overview <\/td>\n<\/tr>\n
21<\/td>\n7 Application layer services
7.1 General <\/td>\n<\/tr>\n
22<\/td>\nFigure 4 \u2014 Application layer service primitives \u2013 Unconfirmed service <\/td>\n<\/tr>\n
23<\/td>\nFigure 4 \u2014 Application layer service primitives \u2013 Unconfirmed service
7.2 Format description of application layer services
7.3 Format description of service primitives
7.3.1 General definition <\/td>\n<\/tr>\n
24<\/td>\n7.3.2 Service request and service indication primitives
7.3.3 Service response and service confirm primitives <\/td>\n<\/tr>\n
25<\/td>\n7.3.3 Service response and service confirm primitives
7.3.4 Service request-confirm and service response-confirm primitives <\/td>\n<\/tr>\n
26<\/td>\n7.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 <\/td>\n<\/tr>\n
27<\/td>\n7.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 <\/td>\n<\/tr>\n
28<\/td>\n7.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 <\/td>\n<\/tr>\n
29<\/td>\n7.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 <\/td>\n<\/tr>\n
30<\/td>\n8.2 A_PDU, application protocol data unit
8.3 A_PCI, application protocol control information
8.4 SI, service identifier <\/td>\n<\/tr>\n
31<\/td>\n8.4 SI, service identifier
8.5 A_NR_SI, Negative response service identifier
8.6 Negative response\/confirmation service primitive <\/td>\n<\/tr>\n
32<\/td>\n8.6 Negative response\/confirmation service primitive
8.7 Server response implementation rules
8.7.1 General definitions <\/td>\n<\/tr>\n
33<\/td>\n8.7.2 General server response behaviour <\/td>\n<\/tr>\n
34<\/td>\n8.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 <\/td>\n<\/tr>\n
35<\/td>\n8.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 <\/td>\n<\/tr>\n
36<\/td>\n8.7.3.2 Physically addressed client request message <\/td>\n<\/tr>\n
37<\/td>\n8.7.3.3 Functionally addressed client request message <\/td>\n<\/tr>\n
39<\/td>\n8.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 <\/td>\n<\/tr>\n
40<\/td>\n8.7.4.3 Functionally addressed client request message <\/td>\n<\/tr>\n
41<\/td>\n8.7.5 Pseudo code example of server response behaviour <\/td>\n<\/tr>\n
42<\/td>\n8.7.6 Multiple concurrent request messages with physical and functional addressing <\/td>\n<\/tr>\n
43<\/td>\n8.7.6 Multiple concurrent request messages with physical and functional addressing
9 Service description conventions
9.1 Service description <\/td>\n<\/tr>\n
44<\/td>\nTable 8 \u2014 A_PDU parameter conventions
9.2 Request message
9.2.1 Request message definition <\/td>\n<\/tr>\n
45<\/td>\nTable 10 \u2014 Request A_PDU definition without SubFunction
9.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 11 \u2014 SubFunction parameter structure <\/td>\n<\/tr>\n
46<\/td>\nTable 12 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
47<\/td>\n9.2.3 Request message data-parameter definition
9.3 Positive response message
9.3.1 Positive response message definition <\/td>\n<\/tr>\n
48<\/td>\n9.3.2 Positive response message data-parameter definition
9.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
49<\/td>\nTable 18 \u2014 Supported negative response codes
9.5 Message flow examples
Table 19 \u2014 Request message flow example <\/td>\n<\/tr>\n
50<\/td>\n10 Diagnostic and communication management functional unit
10.1 Overview
Table 22 \u2014 Diagnostic and communication management functional unit
10.2 DiagnosticSessionControl (1016) service
10.2.1 Service description <\/td>\n<\/tr>\n
53<\/td>\n10.2.2 Request message
10.2.2.1 Request message definition <\/td>\n<\/tr>\n
54<\/td>\n10.2.2 Request message
10.2.2.1 Request message definition
10.2.2.2 Request message SubFunction parameter $Level (LEV_) definition <\/td>\n<\/tr>\n
55<\/td>\n10.2.2.3 Request message data-parameter definition
10.2.3 Positive response message
10.2.3.1 Positive response message definition <\/td>\n<\/tr>\n
56<\/td>\n10.2.3.2 Positive response message data-parameter definition
Table 28 \u2014 sessionParameterRecord definition
10.2.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
57<\/td>\n10.2.5 Message flow example(s) DiagnosticSessionControl \u2013 Start programmingSession
10.3 ECUReset (1116) service
10.3.1 Service description <\/td>\n<\/tr>\n
58<\/td>\n10.3.2 Request message
10.3.2.1 Request message definition
10.3.2.2 Request message SubFunction Parameter $Level (LEV_) definition
Table 34 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
59<\/td>\n10.3.2.3 Request message data-parameter definition
10.3.3 Positive response message
10.3.3.1 Positive response message definition <\/td>\n<\/tr>\n
60<\/td>\nTable 35 \u2014 Positive response message definition
10.3.3.2 Positive response message data-parameter definition
Table 36 \u2014 Response message data-parameter definition
10.3.4 Supported negative response codes (NRC_)
Table 37 \u2014 Supported negative response codes
10.3.5 Message flow example ECUReset <\/td>\n<\/tr>\n
61<\/td>\n10.3.5 Message flow example ECUReset
10.4 SecurityAccess (2716) service
10.4.1 Service description <\/td>\n<\/tr>\n
62<\/td>\n10.4.2 Request message
10.4.2.1 Request message definition <\/td>\n<\/tr>\n
63<\/td>\n10.4.2 Request message
10.4.2.1 Request message definition
Table 41 \u2014 Request message definition – SubFunction = sendKey
10.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 42 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
64<\/td>\nTable 42 \u2014 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 \u2014 Positive response message definition <\/td>\n<\/tr>\n
65<\/td>\n10.4.3 Positive response message
10.4.3.1 Positive response message definition
Table 44 \u2014 Positive response message definition
10.4.3.2 Positive response message data-parameter definition
Table 45 \u2014 Response message data-parameter definition
10.4.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
66<\/td>\n10.4.5 Message flow example(s) SecurityAccess
10.4.5.1 Assumptions
10.4.5.2 Example #1 – server is in a \u201clocked\u201d state
10.4.5.2.1 Step #1: Request the Seed <\/td>\n<\/tr>\n
67<\/td>\n10.4.5.2.2 Step #2: Send the Key
10.4.5.3 Example #2 – server is in an \u201cunlocked\u201d state
10.4.5.3.1 Step #1: Request the Seed
Table 52 \u2014 SecurityAccess positive response message flow example #2 \u2013 step #2 <\/td>\n<\/tr>\n
68<\/td>\nTable 52 \u2014 SecurityAccess positive response message flow example #2 \u2013 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 \u2014 Request message definition
10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
69<\/td>\n10.5.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 54 \u2014 Request message SubFunction parameter definition
10.5.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
70<\/td>\nTable 55 \u2014 Request message data-parameter definition
10.5.3 Positive response message
10.5.3.1 Positive response message definition
Table 56 \u2014 Positive response message definition
10.5.3.2 Positive response message data-parameter definition
Table 57 \u2014 Response message data-parameter definition
10.5.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
71<\/td>\nTable 58 \u2014 Supported negative response codes
10.5.5 Message flow example CommunicationControl (disable transmission of network management messages)
Table 60 \u2014 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) <\/td>\n<\/tr>\n
72<\/td>\nTable 61 \u2014 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 \u2014 CommunicationControl request message flow example <\/td>\n<\/tr>\n
73<\/td>\nTable 64 \u2014 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) <\/td>\n<\/tr>\n
74<\/td>\n10.6.2 Authentication with PKI Certificate Exchange (APCE) <\/td>\n<\/tr>\n
79<\/td>\n10.6.3 Authentication with Challenge-Response (ACR) <\/td>\n<\/tr>\n
83<\/td>\nFigure 10 \u2014 Authentication sequence with Challenge-Response (ACR)
10.6.4 Common requirements <\/td>\n<\/tr>\n
84<\/td>\n10.6.5 Request message
10.6.5.1 Request message definition <\/td>\n<\/tr>\n
85<\/td>\n10.6.5 Request message
10.6.5.1 Request message definition <\/td>\n<\/tr>\n
86<\/td>\nTable 67 \u2014 Request message definition – SubFunction = verifyCertificateBidirectional <\/td>\n<\/tr>\n
87<\/td>\nTable 69 \u2014 Request message definition – SubFunction = transmitCertificate
Table 70 \u2014 Request message definition – SubFunction = requestChallengeForAuthentication <\/td>\n<\/tr>\n
88<\/td>\nTable 71 \u2014 Request message definition – SubFunction = verifyProofOfOwnershipUnidirectional
Table 72 \u2014 Request message definition – SubFunction = verifyProofOfOwnershipBidirectional <\/td>\n<\/tr>\n
89<\/td>\nTable 72 \u2014 Request message definition – SubFunction = verifyProofOfOwnershipBidirectional <\/td>\n<\/tr>\n
90<\/td>\nTable 73 \u2014 Request message definition – SubFunction = authenticationConfiguration
10.6.5.2 Request message SubFunction parameter $Level (LEV_) definition
Table 74 \u2014 Request message SubFunction parameter definition
10.6.5.3 Request message data-parameter definition <\/td>\n<\/tr>\n
91<\/td>\n10.6.6 Positive response message
10.6.6.1 Positive response message definition <\/td>\n<\/tr>\n
92<\/td>\n10.6.6 Positive response message
10.6.6.1 Positive response message definition
Table 76 \u2014 Response message definition – SubFunction = deAuthenticate
Table 78 \u2014 Response message definition – SubFunction = verifyCertificateBidirectional <\/td>\n<\/tr>\n
93<\/td>\nTable 78 \u2014 Response message definition – SubFunction = verifyCertificateBidirectional <\/td>\n<\/tr>\n
95<\/td>\nTable 81 \u2014 Response message definition – SubFunction = requestChallengeForAuthentication <\/td>\n<\/tr>\n
96<\/td>\nTable 83 \u2014 Response message definition – SubFunction = verifyProofOfOwnershipBidirectional <\/td>\n<\/tr>\n
97<\/td>\n10.6.6.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
98<\/td>\n10.6.7 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
99<\/td>\n10.6.7 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
100<\/td>\n10.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 <\/td>\n<\/tr>\n
101<\/td>\n10.6.8.1.2 Step #1: Request Authentication Configuration
Table 88 \u2014 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 <\/td>\n<\/tr>\n
102<\/td>\nTable 89 \u2014 Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 \u2013 step #2
10.6.8.1.4 Step #3: Validate the Proof of Ownership <\/td>\n<\/tr>\n
103<\/td>\nTable 91 \u2014 Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #1 – step #3
Table 92 \u2014 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 <\/td>\n<\/tr>\n
104<\/td>\nTable 94 \u2014 ECUReset response message after successful Authentication request message attempt \u2013 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 \u2014 Unidirectional Authentication with PKI Certificate Exchange without session key establishment request message flow example #2 \u2013 step #1 <\/td>\n<\/tr>\n
105<\/td>\n10.6.8.2.3 Step #2: Attempt to send a random secured service
Table 97 \u2014 ECUReset request message after failed Authentication request message attempt \u2013 example #2 – step #2 <\/td>\n<\/tr>\n
106<\/td>\nTable 98 \u2014 ECUReset response message after failed Authentication request message attempt \u2013 example #2 – step #2
10.6.8.3 Example #3 \u2013 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 \u2014 Transmit Certificate request message flow example #3 – step #1
Table 100 \u2014 Transmit Certificate positive response message flow example #3 – step #1 <\/td>\n<\/tr>\n
107<\/td>\nTable 100 \u2014 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 <\/td>\n<\/tr>\n
108<\/td>\n10.6.8.4.3 Step #2: Request the Challenge <\/td>\n<\/tr>\n
109<\/td>\n10.6.8.4.4 Step #3: Validate the Proof of Ownership
Table 105 \u2014 Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #4 – step #3 <\/td>\n<\/tr>\n
111<\/td>\n10.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 <\/td>\n<\/tr>\n
112<\/td>\n10.6.8.5.2 Step #1: Request the Challenge
Table 107 \u2014 Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 – step #1 <\/td>\n<\/tr>\n
113<\/td>\n10.6.8.5.3 Step #2: Validate the Proof of Ownership
Table 109 \u2014 Unidirectional Authentication using Challenge-Response with asymmetric cryptography without session key establishment request message flow example #5 – step #2 <\/td>\n<\/tr>\n
114<\/td>\nTable 110 \u2014 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 <\/td>\n<\/tr>\n
115<\/td>\n10.6.8.6.2 Step #1: Request challenge for Authentication
Table 111 \u2014 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 – step #1 <\/td>\n<\/tr>\n
116<\/td>\nTable 112 \u2014 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 <\/td>\n<\/tr>\n
117<\/td>\nTable 113 \u2014 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #6 – step #2 <\/td>\n<\/tr>\n
118<\/td>\nTable 114 \u2014 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 \u2014 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 – step #1 <\/td>\n<\/tr>\n
119<\/td>\nTable 115 \u2014 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment request message flow example #7 – step #1
Table 116 \u2014 Unidirectional Authentication using Challenge-Response (ACR) with symmetric cryptography without session key establishment positive response message flow example #7 – step #1 <\/td>\n<\/tr>\n
120<\/td>\n10.6.8.7.3 Step #2: Verify Proof of Ownership Unidirectional <\/td>\n<\/tr>\n
121<\/td>\nTable 118 \u2014 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 <\/td>\n<\/tr>\n
122<\/td>\n10.7 TesterPresent (3E16) service
10.7.1 Service description
10.7.2 Request message
10.7.2.1 Request message definition
Table 119 \u2014 Request message definition
10.7.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 120 \u2014 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 \u2014 Positive response message definition
10.7.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
123<\/td>\nTable 121 \u2014 Positive response message definition
10.7.3.2 Positive response message data-parameter definition
Table 122 \u2014 Response message data-parameter definition
10.7.4 Supported negative response codes (NRC_)
Table 123 \u2014 Supported negative response codes
10.7.5 Message flow example(s) TesterPresent
10.7.5.1 Example #1 – TesterPresent (suppressPosRspMsgIndicationBit = FALSE)
Table 124 \u2014 TesterPresent request message flow example #1 <\/td>\n<\/tr>\n
124<\/td>\nTable 125 \u2014 TesterPresent positive response message flow example #1
10.7.5.2 Example #2 – TesterPresent (suppressPosRspMsgIndicationBit = TRUE)
Table 126 \u2014 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 <\/td>\n<\/tr>\n
125<\/td>\n10.8.2 Request message
10.8.2.1 Request message definition
Table 127 \u2014 Request message definition
10.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 128 \u2014 Request message SubFunction parameter definition
10.8.2.3 Request message data-parameter definition
Table 129 \u2014 Request message data-parameter definition <\/td>\n<\/tr>\n
126<\/td>\nTable 129 \u2014 Request message data-parameter definition
10.8.3 Positive response message
10.8.3.1 Positive response message definition
Table 130 \u2014 Positive response message definition
10.8.3.2 Positive response message data-parameter definition
Table 131 \u2014 Response message data-parameter definition
10.8.4 Supported negative response codes (NRC_)
Table 132 \u2014 Supported negative response codes
10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 – ControlDTCSetting (DTCSettingType = off)
Table 133 \u2014 ControlDTCSetting request message flow example #1 <\/td>\n<\/tr>\n
127<\/td>\n10.8.5 Message flow example(s) ControlDTCSetting
10.8.5.1 Example #1 – ControlDTCSetting (DTCSettingType = off)
Table 133 \u2014 ControlDTCSetting request message flow example #1
Table 134 \u2014 ControlDTCSetting positive response message flow example #1
10.8.5.2 Example #2 – ControlDTCSetting ( DTCSettingType = on)
Table 135 \u2014 ControlDTCSetting request message flow example #2 <\/td>\n<\/tr>\n
128<\/td>\nTable 136 \u2014 ControlDTCSetting positive response message flow example #2
10.9 ResponseOnEvent (8616) service
10.9.1 Service description <\/td>\n<\/tr>\n
130<\/td>\nFigure 13 \u2014 Sampling of data identifiers <\/td>\n<\/tr>\n
134<\/td>\nTable 137 \u2014 Recommended services to be used with the ResponseOnEvent service <\/td>\n<\/tr>\n
135<\/td>\n10.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 <\/td>\n<\/tr>\n
138<\/td>\n10.9.2.2.2 Detailed request message SubFunction onDTCStatusChange parameters specification
10.9.2.2.3 Detailed request message SubFunction reportMostRecentDtcOnStatusChange parameters specification <\/td>\n<\/tr>\n
139<\/td>\n10.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 <\/td>\n<\/tr>\n
141<\/td>\nTable 143 \u2014 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 <\/td>\n<\/tr>\n
143<\/td>\n10.9.3.2 Positive response message data-parameter definition
Table 147 \u2014 Response message data-parameter definition
10.9.4 Supported negative response codes (NRC_)
Table 148 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
144<\/td>\n10.9.4 Supported negative response codes (NRC_)
Table 148 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
145<\/td>\n10.9.5 Message flow example(s) ResponseOnEvent
10.9.5.1 Assumptions
10.9.5.2 Example #1 – ResponseOnEvent (finite event window) <\/td>\n<\/tr>\n
146<\/td>\nTable 150 \u2014 ResponseOnEvent initial positive response message flow example #1 <\/td>\n<\/tr>\n
147<\/td>\nTable 151 \u2014 Start of ResponseOnEvent request message flow example #1
Table 153 \u2014 ReadDTCInformation positive response message flow example #1 <\/td>\n<\/tr>\n
149<\/td>\nTable 156 \u2014 ResponseOnEvent final positive response message flow example #1 <\/td>\n<\/tr>\n
151<\/td>\nFigure 17 \u2014 Finite event window – multiple events during active event window
10.9.5.3 Example #2 – ResponseOnEvent (infinite event window)
Table 157 \u2014 ResponseOnEvent request message flow example #2 <\/td>\n<\/tr>\n
152<\/td>\nTable 157 \u2014 ResponseOnEvent request message flow example #2
Table 158 \u2014 ResponseOnEvent initial positive response message flow example #2 <\/td>\n<\/tr>\n
153<\/td>\nTable 159 \u2014 Start of ResponseOnEvent request message flow example #2
Table 160 \u2014 ResponseOnEvent positive response message flow example #2
Table 161 \u2014 ReadDTCInformation positive response message flow example #2 <\/td>\n<\/tr>\n
155<\/td>\n10.9.5.4 Example #3 – ResponseOnEvent (infinite event window) \u2013 SubFunction parameter \u201conComparisonOfValues\u201d <\/td>\n<\/tr>\n
156<\/td>\n10.9.5.4 Example #3 – ResponseOnEvent (infinite event window) \u2013 SubFunction parameter \u201conComparisonOfValues\u201d
Table 162 \u2014 ResponseOnEvent request message example #3 <\/td>\n<\/tr>\n
157<\/td>\nTable 162 \u2014 ResponseOnEvent request message example #3 <\/td>\n<\/tr>\n
158<\/td>\nTable 163 \u2014 ReadDataByIdentifier positive response message example #3
10.9.5.5 Example #4 – ResponseOnEvent request message (reportMostRecentDtcOnStatusChange)
Table 164 \u2014 ResponseOnEvent request message flow example #4 <\/td>\n<\/tr>\n
159<\/td>\nTable 165 \u2014 ReadDTCInformation positive response message flow example #4
10.9.5.6 Example #5 – ResponseOnEvent request message (reportDTCRecordInformationOnDtcStatusChange)
Table 166 \u2014 ResponseOnEvent request message flow example #4
Table 167 \u2014 ReadDTCInformation positive response message flow example #1 <\/td>\n<\/tr>\n
160<\/td>\nTable 167 \u2014 ReadDTCInformation positive response message flow example #1
10.10 LinkControl (8716) service
10.10.1 Service description <\/td>\n<\/tr>\n
161<\/td>\n10.10.2 Request message
10.10.2.1 Request message definition
Table 169 \u2014 Request message definition (linkControlType = verifyModeTransitionWithSpecificParameter)
Table 170 \u2014 Request message definition (linkControlType = transitionMode)
10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
162<\/td>\n10.10.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 171 \u2014 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 <\/td>\n<\/tr>\n
163<\/td>\n10.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 \u2014 Response message data-parameter definition
10.10.4 Supported negative response codes (NRC_)
Table 175 \u2014 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 \u2014 LinkControl request message flow example #1 – step #1 <\/td>\n<\/tr>\n
164<\/td>\n10.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 \u2014 LinkControl request message flow example #1 – step #1
Table 177 \u2014 LinkControl positive response message flow example #1 – step #1
10.10.5.1.2 Step#2: Transition the baudrate
Table 178 \u2014 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 <\/td>\n<\/tr>\n
165<\/td>\nTable 179 \u2014 LinkControl request message flow example #2 – step #1
Table 180 \u2014 LinkControl positive response message flow example #2 – step #1
10.10.5.2.2 Step#2: Transition the baudrate
Table 181 \u2014 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 <\/td>\n<\/tr>\n
166<\/td>\nTable 182 \u2014 LinkControl request message flow example #3 – step #1
Table 183 \u2014 LinkControl positive response message flow example #3 – step #1
10.10.5.3.2 Step#2: Transition to programming scheduler
Table 184 \u2014 LinkControl request message flow example #3 – step #2
11 Data transmission functional unit
11.1 Overview
Table 185 \u2014 Data Transmission functional unit <\/td>\n<\/tr>\n
167<\/td>\n11.2 ReadDataByIdentifier (2216) service
11.2.1 Service description
11.2.2 Request message
11.2.2.1 Request message definition
Table 186 \u2014 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 \u2014 Request message data-parameter definition <\/td>\n<\/tr>\n
168<\/td>\n11.2.2.2 Request message SubFunction parameter $Level (LEV_) Definition
11.2.2.3 Request message data-parameter definition
Table 187 \u2014 Request message data-parameter definition
11.2.3 Positive response message
11.2.3.1 Positive response message definition
Table 188 \u2014 Positive response message definition
11.2.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
169<\/td>\nTable 189 \u2014 Response message data-parameter definition
11.2.4 Supported negative response codes (NRC_)
Table 190 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
170<\/td>\nFigure 20 \u2014 NRC handling for ReadDataByIdentifier service
11.2.5 Message flow example ReadDataByIdentifier
11.2.5.1 Assumptions <\/td>\n<\/tr>\n
171<\/td>\n11.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 \u2014 ReadDataByIdentifier positive response message flow example #1 <\/td>\n<\/tr>\n
172<\/td>\n11.2.5.3 Example #2: Read multiple dataIdentifiers 010A16 and 011016
Table 194 \u2014 ReadDataByIdentifier positive response message flow example #2 <\/td>\n<\/tr>\n
173<\/td>\n11.3 ReadMemoryByAddress (2316) service
11.3.1 Service description
11.3.2 Request message
11.3.2.1 Request message definition <\/td>\n<\/tr>\n
174<\/td>\n11.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 <\/td>\n<\/tr>\n
175<\/td>\n11.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 \u2014 Response message data-parameter definition
11.3.4 Supported negative response codes (NRC_)
Table 199 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
177<\/td>\n11.3.5 Message flow example ReadMemoryByAddress
11.3.5.1 Assumptions
11.3.5.2 Example #1: ReadMemoryByAddress – 4-byte (32-bit) addressing <\/td>\n<\/tr>\n
178<\/td>\nTable 201 \u2014 ReadMemoryByAddress positive response message flow example #1
11.3.5.3 Example #2: ReadMemoryByAddress – 2-byte (16-bit) addressing. <\/td>\n<\/tr>\n
179<\/td>\n11.3.5.4 Example #3: ReadMemoryByAddress, 3-byte (24-bit) addressing
11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description <\/td>\n<\/tr>\n
180<\/td>\n11.4 ReadScalingDataByIdentifier (2416) service
11.4.1 Service description
11.4.2 Request message
11.4.2.1 Request message definition
Table 206 \u2014 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 \u2014 Request message data-parameter definition
11.4.3 Positive response message
11.4.3.1 Positive response message definition <\/td>\n<\/tr>\n
181<\/td>\nTable 208 \u2014 Positive response message definition
11.4.3.2 Positive response message data-parameter definition
Table 209 \u2014 Response message data-parameter definition
11.4.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
182<\/td>\nTable 210 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
183<\/td>\n11.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 \u2014 ReadScalingDataByIdentifier request message flow example #1 <\/td>\n<\/tr>\n
184<\/td>\n11.4.5.2 Example #1: readScalingDataByIdentifier wth dataIdentifier F19016 (VIN number)
Table 211 \u2014 ReadScalingDataByIdentifier request message flow example #1
Table 212 \u2014 ReadScalingDataByIdentifier positive response message flow example #1
11.4.5.3 Example #2: readScalingDataByIdentifier wth dataIdentifier 010516 (Vehicle Speed) <\/td>\n<\/tr>\n
185<\/td>\nTable 214 \u2014 ReadScalingDataByIdentifier positive response message flow example #2
11.4.5.4 Example #3: readScalingDataByIdentifier wth dataIdentifier 096716
Table 215 \u2014 Example data definition
Table 216 \u2014 ReadScalingDataByIdentifier request message flow example #3 <\/td>\n<\/tr>\n
186<\/td>\nTable 216 \u2014 ReadScalingDataByIdentifier request message flow example #3
Table 217 \u2014 ReadScalingDataByIdentifier positive response message flow example #3
11.5 ReadDataByPeriodicIdentifier (2A16) service
11.5.1 Service description <\/td>\n<\/tr>\n
189<\/td>\n11.5.2 Request message
11.5.2.1 Request message definition <\/td>\n<\/tr>\n
190<\/td>\n11.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 \u2014 Request message data-parameter definition
11.5.3 Positive response message
11.5.3.1 Positive response message definition
Table 220 \u2014 Positive response message definition
Table 221 \u2014 Periodic data response message data definition <\/td>\n<\/tr>\n
191<\/td>\nTable 221 \u2014 Periodic data response message data definition
11.5.3.2 Positive response message data-parameter definition
Table 222 \u2014 Periodic message data-parameter definition
11.5.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
192<\/td>\nTable 223 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
193<\/td>\nFigure 23 \u2014 NRC handling for ReadDataByPeriodicIdentifier service
11.5.5 Message flow example ReadDataByPeriodicIdentifier
11.5.5.1 General assumptions <\/td>\n<\/tr>\n
194<\/td>\n11.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 \u2014 ReadDataByPeriodicIdentifier request message flow example \u2013 step #1
Table 225 \u2014 ReadDataByPeriodicIdentifier initial positive response message flow example \u2013 step #1 <\/td>\n<\/tr>\n
195<\/td>\nTable 226 \u2014 ReadDataByPeriodicIdentifier subsequent positive response message #1 flows \u2013 step #1
Table 227 \u2014 ReadDataByPeriodicIdentifier subsequent positive response message #2 flows \u2013 step #1
11.5.5.2.3 Step #2: Stop the transmission of the periodicDataIdentifiers
Table 228 \u2014 ReadDataByIdentifier request message flow example \u2013 step #2 <\/td>\n<\/tr>\n
196<\/td>\nTable 229 \u2014 ReadDataByIdentifier positive response message flow example \u2013 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 \u2013 Read multiple periodicDataIdentifiers E316 and 2416 at medium rate <\/td>\n<\/tr>\n
199<\/td>\nTable 231 \u2014 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 <\/td>\n<\/tr>\n
200<\/td>\nTable 232 \u2014 Example #3: Periodic scheduler table for scheduler type 1 <\/td>\n<\/tr>\n
201<\/td>\nTable 232 \u2014 Example #3: Periodic scheduler table for scheduler type 1 <\/td>\n<\/tr>\n
202<\/td>\n11.5.5.5 Example #4 – Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates <\/td>\n<\/tr>\n
203<\/td>\n11.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 <\/td>\n<\/tr>\n
204<\/td>\n11.5.5.6 Example #5 – Tabular example of ReadDataByPeriodicIdentifier service periodic schedule rates
Table 235 \u2014 Example #5: Periodic scheduler table
11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description <\/td>\n<\/tr>\n
205<\/td>\n11.6 DynamicallyDefineDataIdentifier (2C16) service
11.6.1 Service description <\/td>\n<\/tr>\n
206<\/td>\n11.6.2 Request message
11.6.2.1 Request message definition
Table 236 \u2014 Request message definition – SubFunction = defineByIdentifier
Table 237 \u2014 Request message definition – SubFunction = defineByMemoryAddress <\/td>\n<\/tr>\n
207<\/td>\nTable 237 \u2014 Request message definition – SubFunction = defineByMemoryAddress
11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 \u2014 Request message SubFunction parameter definition <\/td>\n<\/tr>\n
208<\/td>\n11.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 239 \u2014 Request message SubFunction parameter definition
11.6.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
209<\/td>\n11.6.3 Positive response message
11.6.3.1 Positive response message definition
Table 241 \u2014 Positive response message definition
11.6.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
210<\/td>\nTable 242 \u2014 Response message data-parameter definition
11.6.4 Supported negative response codes (NRC_)
Table 243 \u2014 Supported negative response codes
11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions <\/td>\n<\/tr>\n
211<\/td>\n11.6.5 Message flow examples DynamicallyDefineDataIdentifier
11.6.5.1 Assumptions <\/td>\n<\/tr>\n
212<\/td>\nTable 244 \u2014 Composite data blocks – DataIdentifier definitions
Table 245 \u2014 Elemental data records – DID definitions <\/td>\n<\/tr>\n
213<\/td>\nTable 246 \u2014 Memory data records – Memory address definitions
11.6.5.2 Example #1: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 247 \u2014 DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #1 <\/td>\n<\/tr>\n
214<\/td>\nTable 248 \u2014 DynamicallyDefineDataIdentifier positive response DDDDI F30116 message flow example #1
Table 249 \u2014 ReadDataByIdentifier request DDDDI F30116 message flow example #1 <\/td>\n<\/tr>\n
215<\/td>\n11.6.5.3 Example #2: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier
Table 251 \u2014 DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #2 <\/td>\n<\/tr>\n
216<\/td>\nTable 253 \u2014 ReadDataByIdentifier request DDDDI F30216 message flow example #2
11.6.5.4 Example #3: DynamicallyDefineDataIdentifier, SubFunction = defineByMemoryAddress
Table 255 \u2014 DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3 <\/td>\n<\/tr>\n
217<\/td>\nTable 255 \u2014 DynamicallyDefineDataIdentifier request DDDDI F30216 message flow example #3 <\/td>\n<\/tr>\n
218<\/td>\nTable 257 \u2014 ReadDataByIdentifier request DDDDI F30216 message flow example #3
Table 258 \u2014 ReadDataByIdentifier positive response DDDDI F30216 message flow example #3
11.6.5.5 Example #4: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier <\/td>\n<\/tr>\n
219<\/td>\nTable 259 \u2014 DynamicallyDefineDataIdentifier request DDDDI F2E716 message flow example #4
Table 260 \u2014 DynamicallyDefineDataIdentifier positive response DDDDI F2E716 message flow example #4 <\/td>\n<\/tr>\n
220<\/td>\nTable 262 \u2014 ReadDataByPeriodicIdentifier initial positive message flow example #4
Table 263 \u2014 ReadDataByPeriodicIdentifier periodic data response #1 DDDDI F2E716 message flow example #4
Table 264 \u2014 ReadDataByPeriodicIdentifier periodic data response #n DDDDI F2E716 message flow example #4
11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 \u2014 DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5 <\/td>\n<\/tr>\n
221<\/td>\n11.6.5.6 Example #5: DynamicallyDefineDataIdentifier, SubFunction = clearDynamicallyDefined-DataIdentifier
Table 265 \u2014 DynamicallyDefineDataIdentifier request clear DDDDI F30316 message flow example #5
Table 266 \u2014 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 \u2014 DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier) <\/td>\n<\/tr>\n
222<\/td>\nTable 267 \u2014 DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 1st portion (defineByIdentifier)
Table 268 \u2014 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) <\/td>\n<\/tr>\n
223<\/td>\nTable 269 \u2014 DynamicallyDefineDataIdentifier request DDDDI F30116 message flow example #6 definition of 2nd portion (defineByMemoryAddress)
Table 270 \u2014 DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.3 Step #3: DynamicallyDefineDataIdentifier, SubFunction = defineByIdentifier (3 rd portion) <\/td>\n<\/tr>\n
224<\/td>\nTable 271 \u2014 DynamicallyDefineDataIdentifier request DDDI F30116 message flow example #6 definition of 3rd portion (defineByIdentifier)
Table 272 \u2014 DynamicallyDefineDataIdentifier positive response DDDI F30116 message flow example #6
11.6.5.7.4 Step #4: ReadDataByIdentifier – dataIdentifier = DDDDI F30116
Table 273 \u2014 ReadDataByIdentifier request DDDDI F30116 message flow example #6 <\/td>\n<\/tr>\n
225<\/td>\nTable 274 \u2014 ReadDataByIdentifier positive response DDDDI F30116 message flow example #6
11.6.5.7.5 Step #5: DynamicallyDefineDataIdentifier – clear definition of DDDDI F30116
Table 275 \u2014 DynamicallyDefineDataIdentifier request clear DDDDI F30116 message flow example #6 <\/td>\n<\/tr>\n
226<\/td>\nTable 276 \u2014 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 <\/td>\n<\/tr>\n
227<\/td>\nTable 277 \u2014 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 \u2014 Request message data-parameter definition
11.7.3 Positive response message
11.7.3.1 Positive response message definition
Table 279 \u2014 Positive response message definition
11.7.3.2 Positive response message data-parameter definition
Table 280 \u2014 Response message data-parameter definition
11.7.4 Supported negative response codes (NRC_)
Table 281 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
228<\/td>\n11.7.4 Supported negative response codes (NRC_)
Table 281 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
229<\/td>\nFigure 26 \u2014 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) <\/td>\n<\/tr>\n
230<\/td>\n11.8 WriteMemoryByAddress (3D16) service
11.8.1 Service description <\/td>\n<\/tr>\n
231<\/td>\n11.8.2 Request message
11.8.2.1 Request message definition
Table 284 \u2014 Request message definition
11.8.2.2 Request message SubFunction parameter $Level (LEV_) definition
11.8.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
232<\/td>\nTable 285 \u2014 Request message data-parameter definition
11.8.3 Positive response message
11.8.3.1 Positive response message definition
Table 286 \u2014 Positive response message definition
11.8.3.2 Positive response message data-parameter definition
Table 287 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
233<\/td>\n11.8.3.2 Positive response message data-parameter definition
Table 287 \u2014 Response message data-parameter definition
11.8.4 Supported negative response codes (NRC_)
Table 288 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
234<\/td>\nFigure 27 \u2014 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 <\/td>\n<\/tr>\n
235<\/td>\n11.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 \u2014 WriteMemoryByAddress request message flow example #1
Table 290 \u2014 WriteMemoryByAddress positive response message flow example #1
11.8.5.3 Example #2: WriteMemoryByAddress, 3-byte (24-bit) addressing <\/td>\n<\/tr>\n
236<\/td>\nTable 291 \u2014 WriteMemoryByAddress request message flow example #2
Table 292 \u2014 WriteMemoryByAddress positive response message flow example #2
11.8.5.4 Example #3: WriteMemoryByAddress, 4-byte (32-bit) addressing
Table 293 \u2014 WriteMemoryByAddress request message flow example #3 <\/td>\n<\/tr>\n
237<\/td>\nTable 294 \u2014 WriteMemoryByAddress positive response message flow example #3
12 Stored data transmission functional unit
12.1 Overview
Table 295 \u2014 Stored data transmission functional unit
12.2 ClearDiagnosticInformation (1416) service
12.2.1 Service description <\/td>\n<\/tr>\n
238<\/td>\n12.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 <\/td>\n<\/tr>\n
239<\/td>\nTable 297 \u2014 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 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
240<\/td>\n12.2.5 Message flow example ClearDiagnosticInformation <\/td>\n<\/tr>\n
241<\/td>\nTable 301 \u2014 ClearDiagnosticInformation positive response message flow example #1
12.3 ReadDTCInformation (1916) service
12.3.1 Service description
12.3.1.1 General description <\/td>\n<\/tr>\n
243<\/td>\n12.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) <\/td>\n<\/tr>\n
244<\/td>\n12.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) <\/td>\n<\/tr>\n
245<\/td>\n12.3.1.6 Retrieving DTCStoredData record data for a client defined record number (SubFunction = 0516 reportDTCStoredDataByRecordNumber) <\/td>\n<\/tr>\n
246<\/td>\n12.3.1.7 Retrieving DTCExtendedData record data for a client defined DTC mask and a client defined DTCExtendedData record number (SubFunction = 0616 reportDTCExtDataRecordByDTCNumber) <\/td>\n<\/tr>\n
247<\/td>\n12.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) <\/td>\n<\/tr>\n
248<\/td>\n12.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) <\/td>\n<\/tr>\n
249<\/td>\n12.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) <\/td>\n<\/tr>\n
250<\/td>\n12.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) <\/td>\n<\/tr>\n
251<\/td>\n12.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) <\/td>\n<\/tr>\n
252<\/td>\n12.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 <\/td>\n<\/tr>\n
254<\/td>\nTable 305 \u2014 Request message definition – SubFunction = reportDTCExtDataRecordByDTCNumber
Table 306 \u2014 Request message definition – SubFunction = reportNumberOfDTCBySeverityMaskRecord, reportDTCSeverityInformation
Table 307 \u2014 Request message definition – SubFunction = reportSeverityInformationOfDTC <\/td>\n<\/tr>\n
255<\/td>\nTable 308 \u2014 Request message definition – SubFunction = reportSupportedDTC, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCFaultDetectionCounter, reportDTCWithPermanentStatus
Table 309 \u2014 Request message definition – SubFunction = reportDTCExtDataRecordByRecordNumber
Table 310 \u2014 Request message definition – SubFunction = reportUserDefMemoryDTCByStatusMask <\/td>\n<\/tr>\n
256<\/td>\nTable 311 \u2014 Request message definition – SubFunction = reportUserDefMemoryDTCSnapshotRecordByDTCNumber
Table 313 \u2014 Request message definition – SubFunction = reportSupportedDTCExtDataRecord <\/td>\n<\/tr>\n
257<\/td>\nTable 314 \u2014 Request message definition – SubFunction = reportWWHOBDDTCByMaskRecord
Table 315 \u2014 Request message definition – SubFunction = reportWWHOBDDTCWithPermanentStatus
Table 316 \u2014 Request message definition – SubFunction = reportDTCInformationByDTCReadinessGroupIdentifier
12.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 317 \u2014 Request message SubFunction definition <\/td>\n<\/tr>\n
261<\/td>\n12.3.2.3 Request message data-parameter definition
Table 318 \u2014 Request data-parameter definition <\/td>\n<\/tr>\n
262<\/td>\n12.3.3 Positive response message
12.3.3.1 Positive response message definition <\/td>\n<\/tr>\n
263<\/td>\n12.3.3 Positive response message
12.3.3.1 Positive response message definition
Table 319 \u2014 Response message definition – SubFunction = reportNumberOfDTCByStatusMask, reportNumberOfDTCBySeverityMaskRecord <\/td>\n<\/tr>\n
264<\/td>\nTable 320 \u2014 Response message definition – SubFunction = reportDTCByStatusMask, reportSupportedDTCs, reportFirstTestFailedDTC, reportFirstConfirmedDTC, reportMostRecentTestFailedDTC, reportMostRecentConfirmedDTC, reportDTCWithPermanentStatus
Table 322 \u2014 Response message definition – SubFunction = reportDTCSnapshotRecordByDTCNumber <\/td>\n<\/tr>\n
265<\/td>\nTable 322 \u2014 Response message definition – SubFunction = reportDTCSnapshotRecordByDTCNumber <\/td>\n<\/tr>\n
270<\/td>\nTable 328 \u2014 Response message definition – SubFunction = reportUserDefMemoryDTCByStatusMask <\/td>\n<\/tr>\n
271<\/td>\nTable 330 \u2014 Response message definition – SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber <\/td>\n<\/tr>\n
272<\/td>\nTable 330 \u2014 Response message definition – SubFunction = reportUserDefMemoryDTCExtDataRecordByDTCNumber <\/td>\n<\/tr>\n
273<\/td>\nTable 333 \u2014 Response message definition – SubFunction = reportWWHOBDDTCWithPermanentStatus <\/td>\n<\/tr>\n
274<\/td>\n12.3.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
277<\/td>\n12.3.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
278<\/td>\nTable 336 \u2014 Supported negative response codes
12.3.5 Message flow examples \u2013 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 \u2014 statusOfDTC = 2416 of DTC P0805-11 <\/td>\n<\/tr>\n
279<\/td>\nTable 337 \u2014 statusOfDTC = 2416 of DTC P0805-11
Table 338 \u2014 statusOfDTC = 2616 of DTC P0A9B-17
Table 339 \u2014 statusOfDTC = 2F16 of DTC P2522-1F
12.3.5.2.3 Example #1 message flow <\/td>\n<\/tr>\n
280<\/td>\n12.3.5.2.3 Example #1 message flow
Table 341 \u2014 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 <\/td>\n<\/tr>\n
281<\/td>\n12.3.5.3.2 Example #2 assumptions
Table 342 \u2014 statusOfDTC= 2416 of DTC P0A9B-17
Table 343 \u2014 statusOfDTC = 0016 of DTC P2522-1F <\/td>\n<\/tr>\n
282<\/td>\nTable 344 \u2014 statusOfDTC = 2F16 of DTC P0805-11
12.3.5.3.3 Example #2 message flow
Table 345 \u2014 ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #2
Table 346 \u2014 ReadDTCInformation, SubFunction = reportDTCByStatusMask, positive response, example #2 <\/td>\n<\/tr>\n
283<\/td>\n12.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 \u2014 statusOfDTC= 2416 of DTC P2522-1F <\/td>\n<\/tr>\n
284<\/td>\nTable 348 \u2014 statusOfDTC = 0016 of DTC P0A9B-17
12.3.5.4.3 Example #3 message flow
Table 349 \u2014 ReadDTCInformation, SubFunction = reportDTCByStatusMask, request message flow example #3
Table 350 \u2014 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 <\/td>\n<\/tr>\n
285<\/td>\n12.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 \u2014 ReadDTCInformation, SubFunction = reportDTCSnapshotIdentification, request message flow example #4 <\/td>\n<\/tr>\n
286<\/td>\n12.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 \u2014 DTCSnapshot record content <\/td>\n<\/tr>\n
287<\/td>\nTable 353 \u2014 DTCSnapshot record content
12.3.5.6.3 Example #5 message flow
Table 354 \u2014 ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, request message flow example #5
Table 355 \u2014 ReadDTCInformation, SubFunction = reportDTCSnapshotRecordByDTCNumber, positive response, example #5 <\/td>\n<\/tr>\n
288<\/td>\n12.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 \u2014 DTCStoredData record content
12.3.5.7.3 Example #6 message flow
Table 357 \u2014 ReadDTCInformation, SubFunction = reportDTCStoredDataByRecordNumber, request message flow example #6 <\/td>\n<\/tr>\n
289<\/td>\n12.3.5.7.3 Example #6 message flow
Table 357 \u2014 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 <\/td>\n<\/tr>\n
290<\/td>\n12.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 \u2014 DTCExtDataRecordNumber 0516 content
Table 360 \u2014 DTCExtDataRecordNumber 1016 content
12.3.5.8.3 Example #7 message flow <\/td>\n<\/tr>\n
291<\/td>\nTable 361 \u2014 ReadDTCInformation, SubFunction = reportDTCExtDataRecordByDTCNumber, request message flow example #7
Table 362 \u2014 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 \u2014 statusOfDTC = 2416 of DTC P0A9B-17 <\/td>\n<\/tr>\n
292<\/td>\nTable 363 \u2014 statusOfDTC = 2416 of DTC P0A9B-17
Table 364 \u2014 statusOfDTC = 0016 of DTC P2522-1F <\/td>\n<\/tr>\n
293<\/td>\nTable 365 \u2014 statusOfDTC = 2F16 of DTC P0805-11
12.3.5.9.3 Example #8 message flow
Table 366 \u2014 ReadDTCInformation, SubFunction = reportNumberOfDTCBySeverityMaskRecord, request message flow example #8 <\/td>\n<\/tr>\n
294<\/td>\nTable 367 \u2014 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 \u2014 ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, request message flow example #9
Table 369 \u2014 ReadDTCInformation, SubFunction = reportDTCBySeverityMaskRecord, positive response, example #9 <\/td>\n<\/tr>\n
295<\/td>\nTable 369 \u2014 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 \u2014 ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, request message flow example #10
Table 371 \u2014 ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10 <\/td>\n<\/tr>\n
296<\/td>\nTable 371 \u2014 ReadDTCInformation, SubFunction = reportSeverityInformationOfDTC, positive response, example #10
12.3.5.12 Example #11 \u2013 ReadDTCInformation – SubFunction = reportSupportedDTCs
12.3.5.12.1 Example #11 overview
12.3.5.12.2 Example #11 assumptions
Table 372 \u2014 statusOfDTC = 2416 <\/td>\n<\/tr>\n
297<\/td>\nTable 373 \u2014 statusOfDTC = 0016
Table 374 \u2014 statusOfDTC = 2F16
12.3.5.12.3 Example #11 message flow
Table 375 \u2014 ReadDTCInformation, SubFunction = reportSupportedDTCs, request message flow example #11
Table 376 \u2014 ReadDTCInformation, SubFunction = readSupportedDTCs, positive response, example #11 <\/td>\n<\/tr>\n
298<\/td>\nTable 376 \u2014 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 \u2014 statusOfDTC = 2616 <\/td>\n<\/tr>\n
299<\/td>\nTable 377 \u2014 statusOfDTC = 2616
12.3.5.13.3 Example #12 message flow
Table 378 \u2014 ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #12
Table 379 \u2014 ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #12
12.3.5.14 Example #13 – ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, no information available <\/td>\n<\/tr>\n
300<\/td>\n12.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 \u2014 ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, request message flow example #13
Table 381 \u2014 ReadDTCInformation, SubFunction = reportFirstTestFailedDTC, positive response, example #13
12.3.5.15 Example #14 – ReadDTCInformation, SubFunction = reportDTCFaultDetectionCounter
12.3.5.15.1 Example #14 overview <\/td>\n<\/tr>\n
301<\/td>\n12.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 \u2014 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 <\/td>\n<\/tr>\n
302<\/td>\n12.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 \u2014 DTCExtDataRecordNumber 0516 content for DTC 12345616
Table 385 \u2014 DTCExtDataRecordNumber 0516 content for DTC 23456116
12.3.5.16.3 Example #15 message flow
Table 386 \u2014 ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15 <\/td>\n<\/tr>\n
303<\/td>\n12.3.5.16.3 Example #15 message flow
Table 386 \u2014 ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, request message flow example #15 <\/td>\n<\/tr>\n
304<\/td>\nTable 387 \u2014 ReadDTCInformation, SubFunction = reportDTCExtDataRecordByRecordNumber, positive response, example #15
12.3.5.17 Example #16 \u2013 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 \u2014 ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16 <\/td>\n<\/tr>\n
305<\/td>\nTable 388 \u2014 ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, request message flow, example #16
Table 389 \u2014 ReadDTCInformation, SubFunction = reportDTCExtendedDataRecordIdentification, positive response, example #16
12.3.5.18 Example #17 – ReadDTCInformation, SubFunction = reportWWHOBDDTCByMaskRecord
12.3.5.18.1 Example #17 overview <\/td>\n<\/tr>\n
306<\/td>\n12.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 \u2014 ReadDTCInformation request, SubFunction = reportNumberOfDTCByStatusMask <\/td>\n<\/tr>\n
307<\/td>\nTable 392 \u2014 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 <\/td>\n<\/tr>\n
308<\/td>\n12.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 \u2014 ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, request message flow example #2
Table 395 \u2014 ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18 <\/td>\n<\/tr>\n
309<\/td>\nTable 395 \u2014 ReadDTCInformation, SubFunction = reportWWHOBDDTCWithPermanentStatus, positive response, example #18
12.3.5.20 Example #19 \u2013 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 \u2014 ReadDTCInformation, SubFunction = reportDTCByReadinessGroupIdentifier, request message flow, example #19 <\/td>\n<\/tr>\n
310<\/td>\n13 InputOutput control functional unit
13.1 Overview
Table 398 \u2014 InputOutput Control functional unit
13.2 InputOutputControlByIdentifier (2F16) service <\/td>\n<\/tr>\n
311<\/td>\n13 InputOutput control functional unit
13.1 Overview
Table 398 \u2014 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 <\/td>\n<\/tr>\n
312<\/td>\n13.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 \u2014 Request message data-parameter definition <\/td>\n<\/tr>\n
313<\/td>\n13.2.3 Positive response message
13.2.3.1 Positive response message definition
Table 401 \u2014 Positive response message definition
13.2.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
314<\/td>\nTable 402 \u2014 Response message data-parameter definition
13.2.4 Supported negative response codes (NRC_)
Table 403 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
315<\/td>\nFigure 29 \u2014 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 <\/td>\n<\/tr>\n
316<\/td>\n13.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 <\/td>\n<\/tr>\n
317<\/td>\nTable 407 \u2014 InputOutputControlByIdentifier positive response message flow example #1 – step #2
13.2.5.2.3 Step #3: ReadDataByIdentifier
Table 408 \u2014 ReadDataByIdentifier request message flow example #1 – step #3
Table 409 \u2014 ReadDataByIdentifier positive response message flow example #1 – step #3
13.2.5.2.4 Step #4: returnControlToECU <\/td>\n<\/tr>\n
318<\/td>\n13.2.5.2.4 Step #4: returnControlToECU
13.2.5.2.5 Step #5: freezeCurrentState <\/td>\n<\/tr>\n
319<\/td>\nTable 413 \u2014 InputOutputControlByIdentifier positive response message flow example #1 – step #5
13.2.5.3 Example #2 \u2013 EGR and IAC shortTermAdjustment
13.2.5.3.1 Assumptions
Table 414 \u2014 Composite data blocks \u2013 DataIdentifier definitions \u2013 Example #2 <\/td>\n<\/tr>\n
320<\/td>\nTable 415 \u2014 ControlEnableMaskRecord\u2013 Example #2
13.2.5.3.2 Case #1: Control IAC Pintle Position only
Table 416 \u2014 InputOutputControlByIdentifier request message flow example #2 \u2013 Case #1 <\/td>\n<\/tr>\n
321<\/td>\nTable 417 \u2014 InputOutputControlByIdentifier positive response message flow example #2 \u2013 Case #1
13.2.5.3.3 Case #2: Control RPM Only
Table 418 \u2014 InputOutputControlByIdentifier request message flow example #2 \u2013 Case #2
Table 419 \u2014 InputOutputControlByIdentifier positive response message flow example #2 \u2013 Case #2 <\/td>\n<\/tr>\n
322<\/td>\nTable 419 \u2014 InputOutputControlByIdentifier positive response message flow example #2 \u2013 Case #2
13.2.5.3.4 Case #3: Control both Pedal Position A and EGR Duty Cycle
Table 420 \u2014 InputOutputControlByIdentifier request message flow example #2 \u2013 Case #3 <\/td>\n<\/tr>\n
323<\/td>\nTable 421 \u2014 InputOutputControlByIdentifier positive response message flow example #2 \u2013 Case #3
13.2.5.3.5 Case #4: Return control of all parameters to the ECU <\/td>\n<\/tr>\n
324<\/td>\nTable 422 \u2014 InputOutputControlByIdentifier request message flow example #2 \u2013 Case #4
14 Routine functional unit
14.1 Overview <\/td>\n<\/tr>\n
325<\/td>\nTable 424 \u2014 Routine functional unit
14.2 RoutineControl (3116) service
14.2.1 Service description
14.2.1.1 Overview <\/td>\n<\/tr>\n
326<\/td>\n14.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 <\/td>\n<\/tr>\n
327<\/td>\nTable 425 \u2014 Request message definition
14.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
Table 426 \u2014 Request message SubFunction definition
14.2.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
328<\/td>\nTable 427 \u2014 Request message data-parameter definition
14.2.3 Positive response message
14.2.3.1 Positive response message definition
Table 428 \u2014 Positive response message definition
14.2.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
329<\/td>\nTable 429 \u2014 Response message data-parameter definition
14.2.4 Supported negative response codes (NRC_)
Table 430 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
331<\/td>\nFigure 30 \u2014 NRC handling for RoutineControl service
14.2.5 Message flow example(s) RoutineControl
14.2.5.1 Example #1: SubFunction = startRoutine
Table 431 \u2014 RoutineControl request message flow – example #1 <\/td>\n<\/tr>\n
332<\/td>\nTable 431 \u2014 RoutineControl request message flow – example #1
Table 432 \u2014 positive response message flow – example #1
14.2.5.2 Example #2: SubFunction = stopRoutine <\/td>\n<\/tr>\n
333<\/td>\nTable 433 \u2014 RoutineControl request message flow – example #2
Table 434 \u2014 RoutineControl positive response message flow – example #2
14.2.5.3 Example #3: SubFunction = requestRoutineResults
Table 435 \u2014 RequestRoutineResults request message flow \u2013 example #3 <\/td>\n<\/tr>\n
334<\/td>\n14.2.5.4 Example #4: SubFunction = startRoutine with routineControlOption
Table 437 \u2014 RoutineControl request message flow – example #4 <\/td>\n<\/tr>\n
335<\/td>\nTable 438 \u2014 RoutineControl positive response message flow – example #4
15 Upload download functional unit
15.1 Overview
Table 439 \u2014 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 \u2014 Request message definition <\/td>\n<\/tr>\n
336<\/td>\n15.2.2 Request message
15.2.2.1 Request message definition
Table 440 \u2014 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 \u2014 Request message data-parameter definition <\/td>\n<\/tr>\n
337<\/td>\n15.2.3 Positive response message
15.2.3.1 Positive response message definition
Table 442 \u2014 Positive response message definition
15.2.3.2 Positive response message data-parameter definition
Table 443 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
338<\/td>\n15.2.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
339<\/td>\nFigure 31 \u2014 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 <\/td>\n<\/tr>\n
340<\/td>\n15.3.2 Request message
15.3.2.1 Request message definition
Table 445 \u2014 Request message definition
15.3.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.3.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
341<\/td>\n15.3.3 Positive response message
15.3.3.1 Positive response message definition
Table 447 \u2014 Positive response message definition
15.3.3.2 Positive response message data-parameter definition
Table 448 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
342<\/td>\n15.3.4 Supported negative response codes (NRC_)
Table 449 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
343<\/td>\nFigure 32 \u2014 NRC handling for RequestUpload service
15.3.5 Message flow example(s) RequestUpload
15.4 TransferData (3616) service
15.4.1 Service description <\/td>\n<\/tr>\n
344<\/td>\n15.4 TransferData (3616) service
15.4.1 Service description
15.4.2 Request message
15.4.2.1 Request message definition
Table 450 \u2014 Request message definition
15.4.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.4.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
345<\/td>\n15.4.3 Positive response message
15.4.3.1 Positive response message definition
Table 452 \u2014 Positive response message definition
15.4.3.2 Positive response message data-parameter definition
Table 453 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
346<\/td>\n15.4.3.2 Positive response message data-parameter definition
Table 453 \u2014 Response message data-parameter definition
15.4.4 Supported negative response codes (NRC_)
Table 454 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
348<\/td>\nFigure 33 \u2014 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 \u2014 Request message definition <\/td>\n<\/tr>\n
349<\/td>\n15.5.2 Request message
15.5.2.1 Request message definition
Table 455 \u2014 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 \u2014 Request message data-parameter definition
15.5.3 Positive response message
15.5.3.1 Positive response message definition
Table 457 \u2014 Positive response message definition
15.5.3.2 Positive response message data-parameter definition <\/td>\n<\/tr>\n
350<\/td>\n15.5.4 Supported negative response codes (NRC_)
Table 459 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
351<\/td>\n15.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 \u2014 Definition of transferRequestParameter values
Table 461 \u2014 Definition of transferResponseParameter value <\/td>\n<\/tr>\n
352<\/td>\nTable 461 \u2014 Definition of transferResponseParameter value
15.5.5.1.2 Step #1: Request for download
Table 462 \u2014 RequestDownload request message flow example
Table 463 \u2014 RequestDownload positive response message flow example <\/td>\n<\/tr>\n
353<\/td>\nTable 463 \u2014 RequestDownload positive response message flow example
15.5.5.1.3 Step #2: Transfer data
Table 464 \u2014 TransferData request message flow example
Table 465 \u2014 TransferData positive response message flow example
Table 467 \u2014 TransferData positive response message flow example <\/td>\n<\/tr>\n
354<\/td>\nTable 467 \u2014 TransferData positive response message flow example
15.5.5.1.4 Step #3: Request Transfer exit
Table 468 \u2014 RequestTransferExit request message flow example
Table 469 \u2014 RequestTransferExit positive response message flow example
15.5.5.2 Upload data from a server <\/td>\n<\/tr>\n
355<\/td>\n15.5.5.2.1 Step #1: Request for upload
Table 472 \u2014 RequestUpload request message flow example
Table 473 \u2014 RequestUpload positive response message flow example <\/td>\n<\/tr>\n
356<\/td>\nTable 473 \u2014 RequestUpload positive response message flow example
15.5.5.2.2 Step #2: Transfer data
Table 474 \u2014 TransferData request message flow example <\/td>\n<\/tr>\n
357<\/td>\nTable 475 \u2014 TransferData positive response message flow example
Table 477 \u2014 TransferData positive response message flow example
15.5.5.2.3 Step #3: Request Transfer exit
Table 479 \u2014 RequestTransferExit positive response message flow example <\/td>\n<\/tr>\n
358<\/td>\nTable 479 \u2014 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 \u2014 Request message definition <\/td>\n<\/tr>\n
359<\/td>\n15.6.2.2 Request message SubFunction parameter $Level (LEV_) definition
15.6.2.3 Request message data-parameter definition <\/td>\n<\/tr>\n
360<\/td>\n15.6.3 Positive response message
15.6.3.1 Positive response message definition
Table 482 \u2014 Positive response message definition <\/td>\n<\/tr>\n
361<\/td>\n15.6.3.2 Positive response message data-parameter definition
Table 483 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
362<\/td>\n15.6.4 Supported negative response codes (NRC_)
Table 484 \u2014 Supported negative response codes <\/td>\n<\/tr>\n
364<\/td>\nFigure 35 \u2014 NRC handling for requestFileTransfer service
15.6.5 Message flow example(s) RequestFileTransfer
15.6.5.1 Assumptions <\/td>\n<\/tr>\n
365<\/td>\nTable 485 \u2014 Definition RequestFileTransfer message parameter values
15.6.5.2 Request file transfer
Table 486 \u2014 RequestFileTransfer request message example <\/td>\n<\/tr>\n
367<\/td>\nTable 487 \u2014 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 \u2014 Security sub-layer implementation <\/td>\n<\/tr>\n
368<\/td>\nFigure 36 \u2014 Security sub-layer implementation
16.1.3 Security sub-layer access <\/td>\n<\/tr>\n
369<\/td>\nFigure 37 \u2014 Physical communication during defaultSession – with SOM.ind and security sub-layer <\/td>\n<\/tr>\n
370<\/td>\nFigure 38 \u2014 Physical communication during defaultSession – with enhanced response timing and security sub-layer
16.1.4 General server response behaviour <\/td>\n<\/tr>\n
371<\/td>\n16.2 SecuredDataTransmission (8416) service
16.2.1 Service description <\/td>\n<\/tr>\n
372<\/td>\n16.2 SecuredDataTransmission (8416) service
16.2.1 Service description
16.2.2 Request message
16.2.2.1 Request message definition
Table 488 \u2014 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 \u2014 Request message data-parameter definition <\/td>\n<\/tr>\n
373<\/td>\n16.2.2.2 Request message SubFunction parameter $Level (LEV_) definition
16.2.2.3 Request message data-parameter definition
Table 489 \u2014 Request message data-parameter definition
Table 490 \u2014 Definition of Administrative Parameter <\/td>\n<\/tr>\n
374<\/td>\n16.2.3 Positive response message for successful internal message
16.2.3.1 Positive response message definition for successful internal message
Table 492 \u2014 Positive response message definition
16.2.3.2 Positive response message data-parameter definition
Table 493 \u2014 Response message data-parameter definition <\/td>\n<\/tr>\n
375<\/td>\n16.2.3.2 Positive response message data-parameter definition
Table 493 \u2014 Response message data-parameter definition
16.2.3.3 Positive response message definition for unsuccessful internal message
Table 494 \u2014 Positive response message definition <\/td>\n<\/tr>\n
376<\/td>\n16.2.3.4 Positive response message data-parameter definition
Table 495 \u2014 Response message data-parameter definition
16.2.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n
377<\/td>\nTable 496 \u2014 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 \u2014 SecuredDataTransmission request message flow example #1 <\/td>\n<\/tr>\n
378<\/td>\n16.2.5.3 Example #2: SecuredDataTransmission to Write DID
Table 499 \u2014 SecuredDataTransmission request message flow example #2 <\/td>\n<\/tr>\n
379<\/td>\nTable 499 \u2014 SecuredDataTransmission request message flow example #2 <\/td>\n<\/tr>\n
380<\/td>\nTable 500 \u2014 SecuredDataTransmission response message flow example #2
17 Non-volatile server memory programming process
17.1 General information <\/td>\n<\/tr>\n
383<\/td>\n17.2 Detailed programming sequence <\/td>\n<\/tr>\n
384<\/td>\n17.2 Detailed programming sequence
17.2.1 Programming phase #1 \u2014 Download of application software and\/or application data
17.2.1.1 Pre-Programming step of phase #1 \u2014 Setup of vehicle network for programming <\/td>\n<\/tr>\n
386<\/td>\n17.2.1.2 Programming step of phase #1 \u2014 Download of application software and data <\/td>\n<\/tr>\n
387<\/td>\n17.2.1.2 Programming step of phase #1 \u2014 Download of application software and data <\/td>\n<\/tr>\n
389<\/td>\n17.2.1.3 Post-Programming step of phase #1 \u2014 Re-synchronisation of vehicle network <\/td>\n<\/tr>\n
390<\/td>\n17.2.1.3 Post-Programming step of phase #1 \u2014 Re-synchronisation of vehicle network
Figure 43 \u2014 Post-programming step of phase 1 (STP3)
17.2.1.4 Preprogramming step of phase #2 \u2014 Server configuration <\/td>\n<\/tr>\n
391<\/td>\nFigure 44 \u2014 Preprogramming step of phase 2 (STP4)
17.2.1.5 Programming step of phase #2 \u2014 Final server configuration <\/td>\n<\/tr>\n
392<\/td>\nFigure 45 \u2014 Programming step of phase 2 (STP5)
17.2.1.6 Post-programming step of phase #2 \u2014 Re-synchronisation of vehicle network
17.3 Server reprogramming requirements <\/td>\n<\/tr>\n
393<\/td>\n17.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 <\/td>\n<\/tr>\n
394<\/td>\n17.3.1.1.2 Boot software diagnostic service requirements <\/td>\n<\/tr>\n
396<\/td>\nTable 503 \u2014 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 <\/td>\n<\/tr>\n
397<\/td>\n17.3.2.2 Software and data fingerprints
17.3.3 Server routine access
Table 504 \u2014 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 \u2014 Pre-Programming step <\/td>\n<\/tr>\n
398<\/td>\nTable 505 \u2014 StartDiagnosticSessionControl(extendedSession)
Table 506 \u2014 ControlDTCSetting(off)
Table 507 \u2014 CommunicationControl(disableRxAndTx in the application)
17.4.3 Programming phase #1 \u2014 Programming step
Table 508 \u2014 DiagnosticSessionControl(programmingSession) <\/td>\n<\/tr>\n
399<\/td>\nTable 509 \u2014 SecurityAccess(requestSeed)
Table 510 \u2014 SecurityAccess(sendKey)
Table 511 \u2014 RoutineControl(eraseMemory)
Table 512 \u2014 RequestDownload \u2014 Module #1 <\/td>\n<\/tr>\n
400<\/td>\nTable 513 \u2014 TransferData \u2014 Module #1 (block #1)
Table 514 \u2014 TransferData \u2014 Module #1 (block #2) <\/td>\n<\/tr>\n
401<\/td>\nTable 516 \u2014 RequestTransferExit \u2014 Module #1
Table 517 \u2014 RequestDownload \u2014 Module #2
Table 518 \u2014 TransferData \u2014 Module #2 (block #1) <\/td>\n<\/tr>\n
402<\/td>\nTable 519 \u2014 TransferData \u2014 Module #2 (block #2)
Table 520 \u2014 TransferData \u2014 Module #2 (block #3)
Table 521 \u2014 RequestTransferExit \u2014 Module #2 <\/td>\n<\/tr>\n
403<\/td>\nTable 522 \u2014 RoutineControl(validate application)
Table 523 \u2014 WriteDataByIdentifier \u2014 dataIdentifier = VIN
17.4.4 Programming phase #1 \u2014 Post-Programming step <\/td>\n<\/tr>\n
404<\/td>\nAnnex A (normative) Global parameter definitions
A.1 Negative response codes <\/td>\n<\/tr>\n
414<\/td>\nAnnex B (normative) Diagnostic and communication management functional unit data-parameter definitions
B.1 communicationType parameter definition
Table B.1 \u2014 Definition of communicationType and subnetNumber byte <\/td>\n<\/tr>\n
415<\/td>\nB.2 eventWindowTime parameter definition
B.3 linkControlModeIdentifier parameter definition
Table B.3 \u2014 Definition of linkControlModeIdentifier values <\/td>\n<\/tr>\n
416<\/td>\nB.3 linkControlModeIdentifier parameter definition
Table B.3 \u2014 Definition of linkControlModeIdentifier values
B.4 nodeIdentificationNumber parameter definition <\/td>\n<\/tr>\n
417<\/td>\nB.4 nodeIdentificationNumber parameter definition
B.5 AuthenticationReturnParameter definitions
Table B.5 \u2014 authenticationReturnParameter definitions <\/td>\n<\/tr>\n
419<\/td>\nAnnex C (normative) Data transmission functional unit data-parameter definitions
C.1 DID parameter definitions
Table C.1 \u2014 DID data-parameter definitions <\/td>\n<\/tr>\n
426<\/td>\nC.2 scalingByte parameter definitions <\/td>\n<\/tr>\n
429<\/td>\nTable C.3 \u2014 scalingByte (Low Nibble) parameter definition
C.3 scalingByteExtension parameter definitions
C.3.1 scalingByteExtension for scalingByte high nibble of bitMappedReportedWithOutMask
Table C.4 \u2014 scalingByteExtension for bitMappedReportedWithOutMask
C.3.2 scalingByteExtension for scalingByte high nibble of formula <\/td>\n<\/tr>\n
430<\/td>\nTable C.5 \u2014 scalingByteExtension Bytes for formula
Table C.6 \u2014 formulaIdentifier encoding
Table C.7 \u2014 Two byte real number format
C.3.3 scalingByteExtension for scalingByte high nibble of unit\/format <\/td>\n<\/tr>\n
431<\/td>\nC.3.3 scalingByteExtension for scalingByte high nibble of unit\/format
Table C.8 \u2014 Unit\/format scalingByteExtension encoding <\/td>\n<\/tr>\n
433<\/td>\nC.3.4 scalingByteExtension for scalingByte high nibble of stateAndConnectionType
Table C.9 \u2014 Encoding of scalingByte High Nibble of stateAndConnectionType <\/td>\n<\/tr>\n
434<\/td>\nTable C.9 \u2014 Encoding of scalingByte High Nibble of stateAndConnectionType
C.4 transmissionMode parameter definitions <\/td>\n<\/tr>\n
435<\/td>\nTable C.10 \u2014 transmissionMode parameter definitions
C.5 Coding of UDS edition version number
Table C.11 \u2014 Coding of UDS edition version number DID FF0016 \u2013 4 bytes unsigned value
Table C.12 \u2014 DID FF0016 UDS edition version values of this document <\/td>\n<\/tr>\n
436<\/td>\nAnnex D (normative) Stored data transmission functional unit data-parameter definitions
D.1 groupOfDTC parameter definition
Table D.1 \u2014 Definition of groupOfDTC and range of DTC numbers
D.2 DTCStatusMask and statusOfDTC bit definitions
D.2.1 Convention and definition <\/td>\n<\/tr>\n
438<\/td>\nD.2.2 Pseudocode data dictionary <\/td>\n<\/tr>\n
439<\/td>\nTable D.2 \u2014 Pseudocode data dictionary
D.2.3 DTC status bit definitions <\/td>\n<\/tr>\n
440<\/td>\nTable D.4 \u2014 DTC status bit 1 testFailedThisOperationCycle definitions <\/td>\n<\/tr>\n
442<\/td>\nTable D.6 \u2014 DTC status bit 3 confirmedDTC definitions <\/td>\n<\/tr>\n
444<\/td>\nTable D.7 \u2014 DTC status bit 4 testNotCompletedSinceLastClear definitions <\/td>\n<\/tr>\n
448<\/td>\nFigure D.8 \u2014 DTC status bit 7 WarningIndicator requested logic
D.2.4 Example for operation of DTC Status Bits <\/td>\n<\/tr>\n
450<\/td>\nD.3 DTC severity and class definition
D.3.1 DTC severity and class byte definition
Table D.11 \u2014 DTCSeverityMask\/DTCSeverity byte definition
D.3.2 DTC severity bit definition <\/td>\n<\/tr>\n
451<\/td>\nTable D.12 \u2014 DTC severity bit definitions (bit 7 to 5)
D.3.3 DTC class definition
Table D.13 \u2014 GTR DTC Class definition (bit 4 to 0) <\/td>\n<\/tr>\n
452<\/td>\nD.4 DTCFormatIdentifier definition
Table D.14 \u2014 Definition of DTCFormatIdentifier (DTCFID_) <\/td>\n<\/tr>\n
453<\/td>\nD.5 FunctionalGroupIdentifier definition
Table D.15 \u2014 Definition of FunctionalGroupIdentifiers (FGID_) <\/td>\n<\/tr>\n
454<\/td>\nD.6 DTCFaultDetectionCounter operation implementation example <\/td>\n<\/tr>\n
455<\/td>\nD.7 DTCAgingCounter example <\/td>\n<\/tr>\n
456<\/td>\nD.7 DTCAgingCounter example <\/td>\n<\/tr>\n
457<\/td>\nD.8 DTCExtendedDataRecordNumber value definition
Table D.16 \u2014 DTCExtendedDataRecordNumber value definition <\/td>\n<\/tr>\n
458<\/td>\nAnnex E (normative) Input output control functional unit data-parameter definitions <\/td>\n<\/tr>\n
459<\/td>\nAnnex F (normative) Routine functional unit data-parameter definitions <\/td>\n<\/tr>\n
461<\/td>\nAnnex G (normative) Upload and download functional unit data-parameter
Table G.1 \u2014 Definition of modeOfOperation values <\/td>\n<\/tr>\n
462<\/td>\nAnnex H (informative) Examples for addressAndLengthFormatIdentifier parameter values
Table H.1 \u2014 addressAndLengthFormatIdentifier example <\/td>\n<\/tr>\n
464<\/td>\nAnnex I (normative) Security access state chart
I.1 General
I.2 Disjunctive normal form based state transition definitions <\/td>\n<\/tr>\n
466<\/td>\nTable I.1 \u2014 State transitions \u2013 parameters <\/td>\n<\/tr>\n
472<\/td>\nAnnex J (informative) Recommended implementation for multiple client environments
J.1 Introduction
J.2 Implementation specific limitations
J.3 Use cases relevant for system design <\/td>\n<\/tr>\n
473<\/td>\nFigure J.1 \u2014 Example vehicle topology with onboard clients <\/td>\n<\/tr>\n
474<\/td>\nTable J.1 \u2014 Use case (UC) matrix of multiple client scenarios to be addressed
J.4 Use case evaluation <\/td>\n<\/tr>\n
475<\/td>\nJ.4 Use case evaluation
Table J.2 \u2014 Evaluation of multiple client use cases
J.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol <\/td>\n<\/tr>\n
476<\/td>\nJ.5 Multiple client server level implementation
J.5.1 Definition of diagnostic protocol
J.5.2 Assumptions
J.5.3 Multiple client handling flow <\/td>\n<\/tr>\n
478<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Road vehicles. Unified diagnostic services (UDS) – Application layer<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2020<\/td>\n482<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":258563,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-258556","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/258556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/258563"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=258556"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=258556"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=258556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}