{"id":257660,"date":"2024-10-19T17:02:45","date_gmt":"2024-10-19T17:02:45","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-14229-12013\/"},"modified":"2024-10-25T12:37:40","modified_gmt":"2024-10-25T12:37:40","slug":"bs-iso-14229-12013","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-14229-12013\/","title":{"rendered":"BS ISO 14229-1:2013"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
5<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1 \nScope 2 Normative references 3 Terms, definitions, symbols and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4 Conventions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 5 Document overview <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 6 Application layer services 6.1 General <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 6.2 \nFormat description of application layer services 6.3 \nFormat description of service primitives 6.3.1 General definition <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 6.3.2 Service request and service indication primitives <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 6.3.3 \nService response and service confirm primitives <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 6.3.4 \nService request-confirm and service response-confirm primiti 6.4 \nService data unit specification 6.4.1 \nMandatory parameters 6.4.1.1 \nGeneral definition 6.4.1.2 \nA_Mtype, Application layer message type <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.4.1.3 \nA_SA, Application layer source address 6.4.1.4 \nA_TA, Application layer target address <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.4.1.5 \nA_TA_Type, Application layer target address type 6.4.1.6 \nA_Result 6.4.1.7 \nA_Length 6.4.1.8 \nA_Data 6.4.2 \nVehicle system requirements <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 6.4.3 \nOptional parameters – A_AE, Application layer remote address 7 \nApplication layer protocol 7.1 \nGeneral definition <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.2 \nProtocol data unit specification 7.3 \nApplication protocol control information 7.3.1 \nPCI, Protocol Control Information <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 7.3.2 \nSI, Service Identifier 7.3.3 \nNR_SI, Negative response service identifier <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 7.4 \nNegative response\/confirmation service primitive 7.5 \nServer response implementation rules 7.5.1 \nGeneral definitions <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 7.5.2 \nGeneral server response behaviour <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 7.5.3 \nRequest message with sub-function parameter and server respo 7.5.3.1 \nGeneral server response behaviour for request messages with <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 7.5.3.2 \nPhysically addressed client request message <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 7.5.3.3 \nFunctionally addressed client request message <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 7.5.4 \nRequest message without sub-function parameter and server re General server response behaviour for request messages witho Physically addressed client request message <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Functionally addressed client request message <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 7.5.5 \nPseudo code example of server response behaviour <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 7.5.6 \nMultiple concurrent request messages with physical and funct 8 \nService description conventions 8.1 \nService description <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 8.2 \nRequest message 8.2.1 \nRequest message definition <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 8.2.2 \nRequest message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 8.2.3 \nRequest message data-parameter definition <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 8.3 \nPositive response message 8.3.1 \nPositive response message definition 8.3.2 \nPositive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 8.4 \nSupported negative response codes (NRC_) 8.5 \nMessage flow examples <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 9 \nDiagnostic and Communication Management functional unit 9.1 \nOverview <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 9.2 \nDiagnosticSessionControl (0x10) service 9.2.1 \nService description <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 9.2.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Request message data-parameter definition 9.2.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 9.2.4 \nSupported negative response codes (NRC_) 9.2.5 \nMessage flow example(s) DiagnosticSessionControl Example #1 – Start programmingSession <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 9.3 \nECUReset (0x11) service 9.3.1 \nService description 9.3.2 \nRequest message Request message definition Request message sub-function Parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 9.3.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 9.3.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 9.3.5 \nMessage flow example ECUReset <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 9.4 \nSecurityAccess (0x27) service 9.4.1 \nService description <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 9.4.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Request message data-parameter definition 9.4.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 9.4.4 \nSupported negative response codes (NRC_) 9.4.5 \nMessage flow example(s) SecurityAccess Assumptions <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Example #1 – server is in a \u201clocked\u201d state Step #1: Request the Seed Step #2: Send the Key <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Example #2 – server is in an \u201cunlocked\u201d state Step #1: Request the Seed 9.5 \nCommunicationControl (0x28) service 9.5.1 \nService description <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 9.5.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Request message data-parameter definition 9.5.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 9.5.4 \nSupported negative response codes (NRC_) 9.5.5 \nMessage flow example CommunicationControl (disable transmiss <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 9.5.6 \nMessage flow example CommunicationControl (switch a remote n 9.5.7 \nMessage flow example CommunicationControl (switch to applica <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 9.6 \nTesterPresent (0x3E) service 9.6.1 \nService description 9.6.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 9.6.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 9.6.4 \nSupported negative response codes (NRC_) 9.6.5 \nMessage flow example(s) TesterPresent Example #1 – TesterPresent (suppressPosRspMsgIndicationBit = Example #2 – TesterPresent (suppressPosRspMsgIndicationBit = <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 9.7 \nAccessTimingParameter (0x83) service 9.7.1 \nService description <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 9.7.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Request message data-parameter definition 9.7.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 9.7.4 \nSupported negative response codes (NRC_) 9.7.5 \nMessage flow example(s) AccessTimingParameter Example #1 \u2013 set timing parameters to default values <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 9.8 \nSecuredDataTransmission (0x84) service 9.8.1 \nService description Purpose Security sub-layer <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Security sub-layer access <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 9.8.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 9.8.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 9.8.4 \nSupported negative response codes (NRC_) 9.9 \nControlDTCSetting (0x85) service 9.9.1 \nService description <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 9.9.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Request message data-parameter definition 9.9.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 9.9.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 9.9.5 \nMessage flow example(s) ControlDTCSetting Example #1 – ControlDTCSetting (DTCSettingType = off) Example #2 – ControlDTCSetting ( DTCSettingType = on) <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 9.10 \nResponseOnEvent (0x86) service 9.10.1 \nService description <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 9.10.2 \nRequest message Request message definition Request message sub-function Parameter $Level (LEV_) Definit ResponseOnEvent request message sub-function Parameter defin <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Detailed request message sub-function onTimerInterrupt param Detailed request message sub-function onChangeOfDataIdentifi Detailed request message sub-function onComparisonOfValues p <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Request message data-parameter definition 9.10.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 9.10.4 \nSupported negative response codes (NRC_) 9.10.5 \nMessage flow example(s) ResponseOnEvent Assumptions <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Example #1 – ResponseOnEvent (finite event window) <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Example #1 – flowcharts <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Example #2 – ResponseOnEvent (infinite event window) <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Example #2 – Flowcharts <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Example #3 – ResponseOnEvent (infinite event window) \u2013 sub-f <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 9.11 \nLinkControl (0x87) service 9.11.1 \nService description <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 9.11.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Request message data-parameter definition 9.11.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 9.11.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 9.11.5 \nMessage flow example(s) LinkControl Example #1 – Transition baudrate to fixed baudrate (PC baudr Step#1: Verify if all criteria are met for a baudrate switch <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Step#2: Transition the baudrate Example #2 – Transition baudrate to specific baudrate (150kB Step#1: Verify if all criteria are met for a baudrate switch Step#2: Transition the baudrate <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Example #3 – Transition FlexRay cycle design to ‘Programming Step#1: Verify if all criteria are met for a scheduler switc Step#2: Transition to programming scheduler <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 10 \nData Transmission functional unit 10.1 \nOverview 10.2 \nReadDataByIdentifier (0x22) service 10.2.1 \nService description <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | 10.2.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) Definit Request message data-parameter definition 10.2.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Positive response message data-parameter definition 10.2.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 10.2.5 \nMessage flow example ReadDataByIdentifier Assumptions Example #1: read single dataIdentifier 0xF190 (VIN number) <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Example #2: Read multiple dataIdentifiers 0x010A and 0x0110 <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 10.3 \nReadMemoryByAddress (0x23) service 10.3.1 \nService description <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 10.3.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | 10.3.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 10.3.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | 10.3.5 \nMessage flow example ReadMemoryByAddress Assumptions Example #1: ReadMemoryByAddress – 4-byte (32-bit) addressing <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Example #2: ReadMemoryByAddress – 2-byte (16-bit) addressing Example #3: ReadMemoryByAddress, 3-byte (24-bit) addressing <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 10.4 \nReadScalingDataByIdentifier (0x24) service 10.4.1 \nService description 10.4.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 10.4.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Positive response message data-parameter definition 10.4.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 10.4.5 \nMessage flow example ReadScalingDataByIdentifier Assumptions <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Example #1: readScalingDataByIdentifier wth dataIdentifier 0 Example #2: readScalingDataByIdentifier wth dataIdentifier 0 <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Example #3: readScalingDataByIdentifier wth dataIdentifier 0 <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | 10.5 \nReadDataByPeriodicIdentifier (0x2A) service 10.5.1 \nService description <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | 10.5.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 10.5.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | 10.5.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | 10.5.5 \nMessage flow example ReadDataByPeriodicIdentifier Assumptions Example #1 – Read multiple periodicDataIdentifiers 0xE3 and Assumptions Step #1: Request periodic transmission of the periodicDataId <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Step #2: Stop the transmission of the periodicDataIdentifier <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Example #2 – Graphical and tabular example of ReadDataByPeri ReadDataByPeriodicIdentifier example overview <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Example #2 \u2013 Read multiple periodicDataIdentifiers 0xE3 and <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Example #3 – Graphical and tabular example of ReadDataByPeri ReadDataByPeriodicIdentifier example overview Read multiple periodicDataIdentifiers at different periodic <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Example #4 – Tabular example of ReadDataByPeriodicIdentifier ReadDataByPeriodicIdentifier example overview <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Example #5 – Tabular example of ReadDataByPeriodicIdentifier ReadDataByPeriodicIdentifier example overview 10.6 \nDynamicallyDefineDataIdentifier (0x2C) service 10.6.1 \nService description <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | 10.6.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | 10.6.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | 10.6.4 \nSupported negative response codes (NRC_) 10.6.5 \nMessage flow examples DynamicallyDefineDataIdentifier Assumptions <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Example #1: DynamicallyDefineDataIdentifier, sub-function = <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Example #2: DynamicallyDefineDataIdentifier, sub-function = <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Example #3: DynamicallyDefineDataIdentifier, sub-function = <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Example #4: DynamicallyDefineDataIdentifier, sub-function = <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Example #5: DynamicallyDefineDataIdentifier, sub-function = <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Example #6: DynamicallyDefineDataIdentifier, concatenation o Step #1: DynamicallyDefineDataIdentifier, sub-function = def <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Step #2: DynamicallyDefineDataIdentifier, sub-function = def <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Step #3: DynamicallyDefineDataIdentifier, sub-function = def <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Step #4: ReadDataByIdentifier – dataIdentifier = DDDDI 0xF30 <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Step #5: DynamicallyDefineDataIdentifier – clear definition <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 10.7 \nWriteDataByIdentifier (0x2E) service 10.7.1 \nService description 10.7.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 10.7.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | 10.7.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 10.7.5 \nMessage flow example WriteDataByIdentifier Assumptions Example #1: write dataIdentifier 0xF190 (VIN) <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | 10.8 WriteMemoryByAddress (0x3D) service 10.8.1 \nService description 10.8.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | 10.8.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 10.8.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | 10.8.5 \nMessage flow example WriteMemoryByAddress Assumptions Example #1: WriteMemoryByAddress, 2-byte (16-bit) addressing Example #2: WriteMemoryByAddress, 3-byte (24-bit) addressing <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Example #3: WriteMemoryByAddress, 4-byte (32-bit) addressing <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | 11 Stored Data Transmission functional unit 11.1 \nOverview <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | 11.2 \nClearDiagnosticInformation (0x14) Service 11.2.1 Service description 11.2.2 Request message Request message definition <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 11.2.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 11.2.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | 11.2.5 \nMessage flow example ClearDiagnosticInformation <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 11.3 \nReadDTCInformation (0x19) Service 11.3.1 \nService description General description <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Retrieving the number of DTCs that match a client defined st Retrieving the list of DTCs that match a client defined stat <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Retrieving DTCSnapshot record identification (sub-function = Retrieving DTCSnapshot record data for a client defined DTC <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Retrieving DTCStoredData record data for a client defined re <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Retrieving DTCExtendedData record data for a client defined <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Retrieving the number of DTCs that match a client defined se Retrieving severity and functional unit information that mat Retrieving severity and functional unit information for a cl <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Retrieving the status of all DTCs supported by the server (s Retrieving the first \/ most recent failed DTC (sub-function Retrieving the first \/ most recently detected confirmed DTC <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Retrieving the list of DTCs out of the server DTC mirror mem Retrieving mirror memory DTCExtendedData record data for a c Retrieving the number of mirror memory DTCs that match a cli Retrieving the number of “only emissions-related OBD” DTCs t Retrieving the list of “only emissions-related OBD” DTCs tha <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Retrieving a list of “prefailed” DTC status (sub-function = Retrieving a list of DTCs with “permanent DTC” status (sub-f Retrieving DTCExtendedData record data for a client defined Retrieving the list of WWH-OBD DTCs from a functional group Retrieving a list of WWH-OBD DTCs with “permanent DTC” statu <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Retrieving the list of DTCs out of the server’s user defined Retrieving user defined memory DTCSnapshot record data for a <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Retrieving user defined memory DTCExtendedData record data f <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | 11.3.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | 11.3.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 11.3.4 \nSupported negative response codes (NRC_) 11.3.5 \nMessage flow examples \u2013 ReadDTCInformation General assumption Example #1 – ReadDTCInformation, sub-function = reportNumber Example #1 overview Example #1 assumptions <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Example #1 message flow Example #2 – ReadDTCInformation, sub-function = reportDTCByS Example #2 overview <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | Example #2 assumptions <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | Example #2 message flow <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | Example #3 – ReadDTCInformation, sub-function = reportDTCByS Example #3 overview Example #3 assumptions <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Example #3 message flow <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | Example #4 – ReadDTCInformation, sub-function = reportDTCSna Example #4 overview Example #4 assumptions Example #4 message flow <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Example #5 – ReadDTCInformation, sub-function = reportDTCSna Example #5 overview Example #5 assumptions <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | Example #5 message flow <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Example #6 – ReadDTCInformation, sub-function = reportDTCSto Example #6 overview Example #6 assumptions <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | Example #6 message flow <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Example #7 – ReadDTCInformation, sub-function = reportDTCExt Example #7 overview Example #7 assumptions <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | Example #7 message flow <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | Example #8 – ReadDTCInformation, sub-function = reportNumber Example #8 overview Example #8 assumptions <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Example #8 message flow <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Example #9 – ReadDTCInformation, sub-function = reportDTCByS Example #9 overview Example #9 assumptions Example #9 message flow <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Example #10 – ReadDTCInformation, sub-function = reportSever Example #10 overview Example #10 assumptions Example #10 message flow <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | Example #11 \u2013 ReadDTCInformation – sub-function = reportSupp Example #11 overview Example #11 assumptions <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Example #11 message flow <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | Example #12 – ReadDTCInformation, sub-function = reportFirst Example #12 overview Example #12 assumptions <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Example #12 message flow <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | Example #13 – ReadDTCInformation, sub-function = reportFirst Example #13 overview Example #13 assumptions Example #13 message flow Example #14 – ReadDTCInformation, sub-function = reportNumbe Example #14 overview <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | Example #14 assumptions <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | Example #14 message flow <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Example #15 – ReadDTCInformation, sub-function = reportEmiss Example #15 overview Example #15 assumptions Example #15 message flow <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | Example #16 – ReadDTCInformation, sub-function = reportEmiss Example #16 overview Example #16 assumptions <\/td>\n<\/tr>\n | ||||||
250<\/td>\n | Example #16 message flow Example #17 – ReadDTCInformation, sub-function = reportDTCEx Example #17 overview Example #17 assumptions <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | Example #17 message flow <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Example #18 – ReadDTCInformation, sub-function = reportWWHOB Example #18 overview Example #18 assumptions <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | Example #18 message flow <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | 12 \nInputOutput Control functional unit 12.1 \nOverview 12.2 \n InputOutputControlByIdentifier (0x2F) service 12.2.1 \nService description <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 12.2.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | Request message data-parameter definition 12.2.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Positive response message data-parameter definition 12.2.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | 12.2.5 \nMessage flow example(s) InputOutputControlByIdentifier Assumptions Example #1 – \u201dAir Inlet Door Position\u201d shortTermAdjustment Step #1: ReadDataByIdentifier <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | Step #2: shortTermAdjustment Step #3: ReadDataByIdentifier <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | Step #4: returnControlToECU <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | Step #5: freezeCurrentState <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | Example #2 \u2013 EGR and IAC shortTermAdjustment Assumptions <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | Case #1: Control IAC Pintle Position only <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | Case #2: Control RPM Only <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | Case #3: Control both Pedal Position A and EGR Duty Cycle <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | Case #4: Return control of all parameters to the ECU <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | 13 \nRoutine functional unit 13.1 \nOverview <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | 13.2 \nRoutineControl (0x31) service 13.2.1 \nService description Overview Start a routine referenced by a routineIdentifier <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | Stop a routine referenced by a routineIdentifier Request routine results referenced by a routineIdentifier 13.2.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 13.2.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | Positive response message data-parameter definition 13.2.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | 13.2.5 \nMessage flow example(s) RoutineControl Example #1: sub-function = startRoutine Example #2: sub-function = stopRoutine <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | Example #3: sub-function = requestRoutineResults <\/td>\n<\/tr>\n | ||||||
277<\/td>\n | Example #4: sub-function = startRoutine with routineControlO <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | 14 \nUpload Download functional unit 14.1 \nOverview 14.2 \nRequestDownload (0x34) service 14.2.1 \nService description 14.2.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | 14.2.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
282<\/td>\n | 14.2.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
283<\/td>\n | 14.2.5 \nMessage flow example(s) RequestDownload <\/td>\n<\/tr>\n | ||||||
284<\/td>\n | 14.3 \nRequestUpload (0x35) service 14.3.1 \nService description 14.3.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
285<\/td>\n | Request message data-parameter definition 14.3.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
287<\/td>\n | 14.3.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | 14.3.5 \nMessage flow example(s) RequestUpload <\/td>\n<\/tr>\n | ||||||
289<\/td>\n | 14.4 \nTransferData (0x36) service 14.4.1 \nService description 14.4.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit <\/td>\n<\/tr>\n | ||||||
290<\/td>\n | Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | 14.4.3 \nPositive response message Positive response message definition Positive response message data-parameter definition 14.4.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
293<\/td>\n | 14.4.5 \nMessage flow example(s) TransferData <\/td>\n<\/tr>\n | ||||||
294<\/td>\n | 14.5 \nRequestTransferExit (0x37) service 14.5.1 \nService description 14.5.2 \nRequest message Request message definition Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition 14.5.3 \nPositive response message Positive response message definition <\/td>\n<\/tr>\n | ||||||
295<\/td>\n | Positive response message data-parameter definition 14.5.4 \nSupported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | 14.5.5 \nMessage flow example(s) for downloading\/uploading data Download data to a server Assumptions <\/td>\n<\/tr>\n | ||||||
297<\/td>\n | Step #1: Request for download <\/td>\n<\/tr>\n | ||||||
298<\/td>\n | Step #2: Transfer data <\/td>\n<\/tr>\n | ||||||
299<\/td>\n | Step #3: Request Transfer exit <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Upload data from a server <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | Step #1: Request for upload Step #2: Transfer data <\/td>\n<\/tr>\n | ||||||
302<\/td>\n | Step #3: Request Transfer exit <\/td>\n<\/tr>\n | ||||||
304<\/td>\n | 14.6 \nRequestFileTransfer (0x38) service 14.6.1 \nService description 14.6.2 \nRequest message Request message definition <\/td>\n<\/tr>\n | ||||||
305<\/td>\n | Request message sub-function parameter $Level (LEV_) definit Request message data-parameter definition <\/td>\n<\/tr>\n | ||||||
306<\/td>\n | 14.6.3 \nPositive response message Positive response message definition Positive response message data-parameter definition <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | 14.6.4 Supported negative response codes (NRC_) <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | 14.6.5 \nMessage flow example(s) RequestFileTransfer Assumptions Request file transfer <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | 15 Non-volatile server memory programming process 15.1 \nGeneral information <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | 15.2 \nDetailed programming sequence 15.2.1 \nProgramming phase #1 \u2014 Download of application software and\/ Pre-Programming step of phase #1 \u2014 Setup of vehicle network <\/td>\n<\/tr>\n | ||||||
318<\/td>\n | Programming step of phase #1 \u2014 Download of application softw <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Post-Programming step of phase #1 \u2014 Re-synchronization of ve Pre-programming step of phase #2 \u2014 Server configuration <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | Programming step of phase #2 \u2014 Final server configuration <\/td>\n<\/tr>\n | ||||||
323<\/td>\n | Post-programming step of phase #2 \u2014 Re-synchronization of ve <\/td>\n<\/tr>\n | ||||||
324<\/td>\n | 15.3 \nServer reprogramming requirements 15.3.1 \nRequirements for servers to support programming Boot software description and requirements Boot software general requirements <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | Boot software diagnostic service requirements <\/td>\n<\/tr>\n | ||||||
327<\/td>\n | Security requirements <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | 15.3.2 \nSoftware, data identification and fingerprints Software and data identification Software and data fingerprints 15.3.3 \nServer routine access 15.4 \nNon-volatile server memory programming message flow examples 15.4.1 \nGeneral information <\/td>\n<\/tr>\n | ||||||
329<\/td>\n | 15.4.2 Programming phase #1 \u2014 Pre-Programming step 15.4.3 \nProgramming phase #1 \u2014 Programming step <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | 15.4.4 \nProgramming phase #1 \u2014 Post-Programming step <\/td>\n<\/tr>\n | ||||||
400<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Road vehicles. Unified diagnostic services (UDS) – Specification and requirements<\/b><\/p>\n |