{"id":257025,"date":"2024-10-19T16:59:53","date_gmt":"2024-10-19T16:59:53","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-22900-32009\/"},"modified":"2024-10-25T12:33:23","modified_gmt":"2024-10-25T12:33:23","slug":"bs-iso-22900-32009","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-22900-32009\/","title":{"rendered":"BS ISO 22900-3:2009"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
13<\/td>\n | Scope Normative references <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | Terms, definitions, symbols and abbreviated terms Terms and definitions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Abbreviated terms <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | Typographical conventions and mnemonics used in this part of <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | Legends for used graphics Hierarchical diagrams Sequence diagrams <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | Stereotypes General considerations Specification release version information <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Structure of MCD systems <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Function block common MCD MCD system object <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Version information retrieval Description of Terms General Client-controlled object Location <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Logical Link (LOGICAL-LINK) Project <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Server-controlled mutable object Server-controlled object (shared object) States of the MCD system object <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | State changes <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Project configuration <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Interface structure of MCD-server API Separation in database and runtime side <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Hierarchical model <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Structure of the database Overview Associations of DbLocation for MCD <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Database within the field Measurement and Calibration Database within the field Diagnostics Collections Types and methods <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | RunTime collections Overview <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | RunTime collections in MC RunTime collections in D <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Database collections <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Handling of collection of ASCIISTRING EventHandler Registering\/deregistering of the EventHandlers <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Methods of the EventHandlers <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Eventfilter <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Multi-Client capability Requirements <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Design <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Proxy in Multi Client Architecture <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Cooperation Level <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Symbolic Names of Clients Selection and de-selection of Project and VehicleInfo in a m <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Notification <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Remove shared objects <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Locking <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Client Controlled Objects <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Resource Release Use cases <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Requirements Solution Critical Section, Critical Groups of Methods <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Result access <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | MCD value Value types <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Method getValue Behaviour of MCDRequestParameter::getValue() Behaviour of MCDResponseParameter::getValue() Behaviour of MCDParameter::getValue() Method setValue <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Method createValue <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Use cases View Instantiation of projects <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Database access <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Destruction <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Function block Common MD Collector ERD <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Concept <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Result access Object list configuration Structure of the collector sample list <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Result structure <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Collector usage in diagnostics <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Use cases Measurement with a collector – activation <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Measurement with a collector – result access <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Measurement with a collector – polling for results <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Function block Diagnostics Description of Terms General Access Key Functional Class (FUNCTIONAL-CLASS) Job (SINGLE-ECU-JOB, MULTIPLE-ECU-JOB) Physical Interface Link <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Physical Link Physical Vehicle Link (PHYSICAL-VEHICLE-LINK) Structuring of the function block Diagnostics Separation in database and runtime side <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Relation between Vehicle Connector Information Table and Log <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Hierarchical model <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Entity Relationship Diagrams ERD DbLocation <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | ERD Logical Link and associated MCD Objects <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | ERD Request and Response Parameter associations <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | ERD Jobs <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | System Properties Diagnostic DiagComPrimitives and Services Diagnostic DiagComPrimitives and States Diagnostic DiagComPrimitives <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | States of DiagComPrimitives <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Service overview <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Non cyclic single shot diag service <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Cyclic diag service <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Repeated diag service <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Repeated send only diag service <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Repeated receive only diag service Updating repetition parameters <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Summary <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Protocol parameters General <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Introduction related to ODX <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Inheritance of protocol parameters <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Database part Runtime part <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Suppress Positive Response <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Diagnostic variables <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | eEND_OF_PDU as RequestParameter Database side <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Runtime side <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | COMPUCODE <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Variable length parameters <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Layer inheritance of services Goal Layer inheritance of services <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Service handling on functional and physical locations <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Variant Identification and Selection (VI \/ VIS) Goal Variant Identification Algorithm Logical Link Basics <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Principles of Variant Identification and Variant Identificat <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Variant Patterns and Matching Parameters <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Identification Algorithm <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | General VI\/VIS handling considerations <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Deselecting of selected variants Request and Response parameters of VI and VIS Goal <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Request Parameter Structure of VI and VIS <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Response Parameter Structure of VI and VIS <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Switching Database Template Generation On and Off <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Example Scenarios for VI and VIS <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Base Variant Identification and Selection <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Use Cases Creation of LogicalLink and usage of DiagComPrimitives <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | Removal of communication objects <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Service Handling Non cyclic diag service execution <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Cyclic diag service execution <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Result access General <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Result buffer <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | Error handling in results <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Result matching for database templates <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Filtering of results Principle <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Handling rules <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | Read DTC <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | Logical Link General Connection overview <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | State diagram of Logical Link <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | Logical Link examples <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | Gateway handling <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | Examples and Relations between Logical Links, Locations and <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | Functional Addressing <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | Tables General <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | Usage of tables within DiagComPrimitives <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | Dynamically Defined Local Id \/ Table Parameters (DDLID) General DDLID principle and requirements <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | Lifecycle General Creation of Dynamically Defined Local Id <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | Reading by Dynamically Defined Local Id Deletion of Dynamically Defined Local Id <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | DB-Templates for Requests and Responses regarding DDLID <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | Procedure description <\/td>\n<\/tr>\n | ||||||
284<\/td>\n | Internationalisation Multi language support Units Special Data Groups <\/td>\n<\/tr>\n | ||||||
285<\/td>\n | ECU Flash programming Goal <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | Description of Terms for ECU-Reprogramming General ECU-MEM Description Flash Class Description Flash Job Description Flash Key Description Flash Session Description <\/td>\n<\/tr>\n | ||||||
287<\/td>\n | Flash Session Desc Description Description of \u2018Late-bound data files\u2019 Mechanism Priority Description Structure of the function block flash programming Database part <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | Runtime part <\/td>\n<\/tr>\n | ||||||
292<\/td>\n | Handling binary flash data <\/td>\n<\/tr>\n | ||||||
294<\/td>\n | Identification mechanism <\/td>\n<\/tr>\n | ||||||
297<\/td>\n | Segmenting Flash Data <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Management of ECU-MEMs <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | Physical Memories <\/td>\n<\/tr>\n | ||||||
303<\/td>\n | Executing flash sessions Flash session execution basics <\/td>\n<\/tr>\n | ||||||
304<\/td>\n | Flash job basics <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | Uploading Flash Data from an ECU Downloading Flash Data to an ECU <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | Checksum calculation in Flash Jobs <\/td>\n<\/tr>\n | ||||||
311<\/td>\n | Library <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | Java Jobs General General information Java Jobs <\/td>\n<\/tr>\n | ||||||
313<\/td>\n | Types of Java Jobs General Single ECU Job Flash Job <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | Security access job <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | Multiple ECU Job <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | Handling of Java Jobs General Development of Java Jobs <\/td>\n<\/tr>\n | ||||||
318<\/td>\n | Deployment of Java Jobs Job Execution Modes <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | Hash signatures for Jobs <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Job Parameter handling <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | Job Communication Parameter handling Job Result handling Job Result Generation <\/td>\n<\/tr>\n | ||||||
325<\/td>\n | Progress information <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | Job execution General Single execution of a Job <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | Repeated execution of Job <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Cancellation of a Job <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | Job example <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | ECU configuration General ECU Configuration Database Part <\/td>\n<\/tr>\n | ||||||
348<\/td>\n | ECU Configuration Runtime Part <\/td>\n<\/tr>\n | ||||||
351<\/td>\n | Error Handling Initialising an MCDConfigurationRecord <\/td>\n<\/tr>\n | ||||||
352<\/td>\n | Offline versus Online Configuration <\/td>\n<\/tr>\n | ||||||
353<\/td>\n | Uploading and Downloading Configuration Strings Decomposing a Configuration String for Transfer <\/td>\n<\/tr>\n | ||||||
354<\/td>\n | Downloading Configuration Records to an ECU <\/td>\n<\/tr>\n | ||||||
356<\/td>\n | Uploading Configuration Records from an ECU <\/td>\n<\/tr>\n | ||||||
357<\/td>\n | Management of CONFIG-DATAs <\/td>\n<\/tr>\n | ||||||
358<\/td>\n | Audiences and Additional Audiences General <\/td>\n<\/tr>\n | ||||||
360<\/td>\n | Audiences Additional Audiences <\/td>\n<\/tr>\n | ||||||
361<\/td>\n | Function Dictionary and Sub-Components Terms and requirements General MCDDbFunctionDictionary MCDDbSubComponent Functions and function group in ODX <\/td>\n<\/tr>\n | ||||||
363<\/td>\n | Function dictionary data model description <\/td>\n<\/tr>\n | ||||||
365<\/td>\n | Function dictionary usage scenario <\/td>\n<\/tr>\n | ||||||
367<\/td>\n | Sub-Component data model description <\/td>\n<\/tr>\n | ||||||
368<\/td>\n | Sub-Component usage scenario <\/td>\n<\/tr>\n | ||||||
369<\/td>\n | ECU States <\/td>\n<\/tr>\n | ||||||
372<\/td>\n | Monitoring vehicle bus traffic <\/td>\n<\/tr>\n | ||||||
374<\/td>\n | Support of VCI module selection and other VCI module feature General Definitions General behaviour of D-PDU API related D-server methods <\/td>\n<\/tr>\n | ||||||
375<\/td>\n | Overview of VCI module related classes <\/td>\n<\/tr>\n | ||||||
376<\/td>\n | VCI module selection MCDInterface <\/td>\n<\/tr>\n | ||||||
377<\/td>\n | VCI module selection sequence <\/td>\n<\/tr>\n | ||||||
378<\/td>\n | Interface status events <\/td>\n<\/tr>\n | ||||||
379<\/td>\n | MCDInterfaceResource Selection of an interface resource <\/td>\n<\/tr>\n | ||||||
380<\/td>\n | Send Break Signal <\/td>\n<\/tr>\n | ||||||
381<\/td>\n | MCDDbInterfaceCable Accessing VCI module features <\/td>\n<\/tr>\n | ||||||
382<\/td>\n | Adding Logical Links which are not found in the Vehicle Info <\/td>\n<\/tr>\n | ||||||
383<\/td>\n | Behaviour of a MCD-server not supporting VCI Modules in acco <\/td>\n<\/tr>\n | ||||||
384<\/td>\n | Mapping of D-PDU API methods General Initialization and Selection of VCI Modules Communication on a Logical Link <\/td>\n<\/tr>\n | ||||||
386<\/td>\n | Handling of Communication Parameters Changing communication parameters from the client applicatio <\/td>\n<\/tr>\n | ||||||
387<\/td>\n | Setting temporary communication parameters for a DiagComPrim Changing UNIQUE_ID Communication Parameters <\/td>\n<\/tr>\n | ||||||
388<\/td>\n | MCDStartCommunication and MCDStopCommunication <\/td>\n<\/tr>\n | ||||||
389<\/td>\n | Error Codes Principle <\/td>\n<\/tr>\n | ||||||
391<\/td>\n | Description of the errors Error free behaviour Parameterisation errors Runtime \/ ProgramViolation errors Database errors System errors Communication errors Job error <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Road vehicles. Modular vehicle communication interface (MVCI) – Diagnostic server application programming interface (D-Server API)<\/b><\/p>\n |