![]() Inside the Create Data Identifier window can be configured: The first step is the creation of a DID clicking on the command Create Data Identifier: The DIDs, Data Element, UDS Services, Sessions, Security Levels and Access Permission can and should be created from this window. The Configure DIDs window is the first step of the workflow shown opening the DEXT Editor and also the first that has to be configured: Identifier Services Workflow Configure DIDs window Anyway, it can be changed manually in the ARXML file if needed. ![]() N.B.: Unfortunately the Service Table name can be only set during this step and not changed anymore through the DEXT Editor. To do so right click on the project name and click on Open with > DEXT EditorĪfter this step a window will open asking for the names of Contribution Set and Service Table that can be set as shown in this image: If a diagnostic configuration is not present on your project yet you can simply create one opening the DEXT editor. Contribution Set and Service Table creation Is very important that the second step of the workflow will be the creation of a Data Identifier because through this command not only a DID will be created, it will also generate automatically DataElements and UDS Services. Create a Data Identifier (that will generate DID, DataElements and UDS Services).Create a ContributionSet and a ServiceTable.To configure correctly the UDS from the DEXT Editor a specific workflow has to be follow: IOC, ComControl, EcuReset, SecurityAccess services, Sessions, map R/WDBI ![]() Sessions, security levels, environmental condition, access permissionĭID, Data Element, RDBI, WDBI, DDDI services, Map services It is assumed you are using the RTA-CAR 9.2.0 toolchain: Definitions and AbbreviationsīSW: AUTOSAR Basic Software, Hardware independent service layer In this guide we will explain how to create a Diagnostic Extract file with a UDS configuration through the DEXT Editor of ISOLAR-AB. Therefore, the Diagnostic Extract format is based on the Diagnostic Extract Template (DEXT) that allows gradual enrichment of definitions by the different roles.įurther, it supports the automatic code generation process for diagnostic modules. The Diagnostic Extract is a standardized AUTOSAR exchange format on diagnostic functionality (DCM, DEM and FIM), formalized as an ARXML file.ĭuring an ECU development project, three main roles (OEM, Application Developer and ECU Integrator) exchange Diagnostic Extract files.
0 Comments
Leave a Reply. |