The Editor Release of the Diagnose Configurator offers you all aspects of the development of UDS diagnostic software:
- The tracking history
- The creation all UDS diagnostic messages
- The creation the complete AutoSAR compatible DTC error memory
- The organisation of the non-volatile memory
All configurations, which are entered in the Diagnose Configurator are automatically written into html file, each time you for example move to another page.
To generate C, C++, C# and header code you need the Generate Code Release.
The tracking history
In the Authors table all members of the development team should be entered.
In the History table all changes of the development process should be entered.
The creation all UDS diagnostic messages
Requirement specifications from Doors or MS-Excel can be imported to the table on the Requirement Spec page.
In the Supported Services table all UDS services are deployed to the operating states. These data are common to the respective data of the System Configurator and can be modified in both configurators.
The Standard Jobs page offers the selection of all essential, optotinal and coding jobs.
On the pages Record DIDs, IO Control DIDs and Routine DIDs you interactively can edit all data IDs (DID) of the respective services "Read & Write Data by Identifier", "Input & Output Control By Identifier" and "Remote Routine Control". For each UDS message you can interactively edit its signals.
The creation the complete AutoSAR compatible DTC error memory
On the General page you can edit all global settings.
The Descriptors page offers the complete creation of the AutoSAR compatible DTC error memory for this project.
In an extra table the environment data of each DTC can interactively be edited
On the Freeze Frames page the global settings of the freeze frame can be configured. The freeze frame is the memory where the self diagnosis stores the detected errors.
The organisation of the non-volatile memory
Before the selected ECU goes from the run state into the sleep state all DTC freeze frame data and all additional data, which are configured in the Blocks page, must be copied into the non volatile memory (NVRAM). For this job the extra state GotoSleep was created. Before the ECU can return to the Run state, the WakeUp state is activated, where all NVRAM data are written back to the RAM of the ECU.