<div class="section abstract"><div class="htmlview paragraph">Due to increase in complexity of vehicle functionality and involvement of electronic components, the use of complex electronic control units is prevalent in today’s vehicles. This has led to increased amount of Electronic Control Unit (ECU) data, and in turn increased Diagnostic data. This Diagnostic data is described in the Automotive Open System Architecture Diagnostic Exchange Template (AUTOSAR DEXT), which is a standard diagnostic data format specified in AUTOSAR 4.2.1 for Unified Diagnostic Services and fault memory. It enables consistent exchange of Diagnostic information across Original Equipment manufacturer OEMs and between OEM and Suppliers, thereby aiding uniformity in configuration of basic software modules described in Automotive Open System Architecture (AUTOSAR) Layered Architecture across enterprise boundaries. DEXT provides the possibility to describe the data to be transported, using respective protocol, along with origin of data in ECU’s application software. When there is availability of both information and data, the configuration of diagnostic basic software becomes possible. This Paper explains the steps which are necessary to process diagnostic data which is being populated in DEXT file, and further tailor it for a production ECU.</div><div class="htmlview paragraph"><i>Index Terms</i></div><div class="htmlview paragraph">—Automotive Open System Architecture, Autosar Extensiable markup language, Basic Software, Controller Area Network, Communication Manager, Diagnostic Communication Manager, Diagnostic Event Manager, Diagnostic Extract Template, Diagnostic Data Identifier, Diagnostic Trouble Code, Electronic Unit Control, Function Inhibition Manager, Local Interconnect Network, Onboard Diagnostics, Open Diagnostic Extract, Original Equipment Manager, Diagnostic Extract Template, Electronic Control Unit, Original Equipment Manufacturer, Unified Diagnostic Services.</div></div>