Generation of AUTOSAR Diagnostic Communication Manager

AUTOSAR was created as a standard software infrastructure to be able to fulfill a very large amount of requirements. These days, more and more OEMs are trying to introduce AUTOSAR in their products. Since there are a large amount of diagnostic IDs needed in the Engine control unit and also a huge... Ausführliche Beschreibung

1. Verfasser:
Weitere Verfasser: [advisor] ; [advisor] ; [referee] ; [referee]
Format: Elektronische Hochschulschrift
veröffentlicht: Chemnitz : Universitätsbibliothek Chemnitz, 2016.
Schlagworte:
ECU
ECU
Kein Bild verfügbar
Gespeichert in:
Zusammenfassung: AUTOSAR was created as a standard software infrastructure to be able to fulfill a very large amount of requirements. These days, more and more OEMs are trying to introduce AUTOSAR in their products. Since there are a large amount of diagnostic IDs needed in the Engine control unit and also a huge effort is necessary to configure the ECU, it is very much important to have a tool to generate some parts of the Engine Control Unit software, most importantly the diagnostics software. Diagnostic Communication manager is one such AUTOSAR module which deals with a huge amount of diagnostic data identifiers. Also at BEG, In the actual Non-AUTOSAR Bosch Automotive software, there are a number of different features that are needed and expected in the future AUTOSAR software. The aim of this thesis is to develop a tool that successfully introduces AUTOSAR in the BEG projects with all the necessary features and that is best in terms of Usability, Maintainability, and Improvability. This tool has to generate the complete AUTOSAR Diagnostic communication manager software with all the necessary features. The work can be divided into two parts. The first part includes a complete analysis of the existing tools that are used to generate configuration files and code. Then, List out all the possibilities of each tool, find their advantages and disadvantages and compare each of the tools, either individually or as a combination of tools. This is followed by documenting the choice of best way to generate AUTOSAR DCM with all the necessary features. In the second part, the implementation is carried out. After the best tool is chosen, the implementation of the features for that particular tool is planned accordingly so that it generates the DCM software. Implementation is made and then it is tested with the existing test bench.
Fussnoten: masterThesis