Talk
AUTOSAR Methodology applied to ECU Diagnostics Architecture and Workflow
Salvador Almanza
40:36
The system complexity of automotive E/E systems keeps growing, reaching an impressive number of 100+ million lines of code in recent years. Most of this complexity is due to the algorithm implementation in each Electronic System Unit (ECU) in the vehicle architecture. Additionally, automobiles must meet multiple standards and government regulations (e.g., Diagnostics and OBD), adding contributing factors not just to complexity but also to the development effort, making it very difficult to meet deadlines, milestones, and time to market. This presentation focuses on the AUTOSAR methodology and the architecture solution to diagnostics modeling and workflow using a top-down approach that helps reduce time and effort during ECU development by abstracting the complexity of the implementation and relieving the ECU integrators of exhausting and complex manual work.
1 / 4
Please log in or create an account to test your knowledge and see the answers.
What is the main reason the speaker recommends using the AUTOSAR methodology for ECU software development?
A
To enforce a single-vendor toolchain so OEMs fully control implementations.
B
To manage growing system complexity by abstracting the Basic Software via the RTE, maximizing software reuse and speeding time-to-market.
C
To eliminate the need for diagnostics and testing by relying entirely on model-based designs.
D
To replace all ECU hardware with a single generic microcontroller standard.
E
To ensure all diagnostic processing is moved offboard to the cloud rather than performed in the vehicle.
Great talk, Savador Almanza! For those in the Automotive world, I recommend also the talk "SDV and the new moving computers", were I give an overview about SDV and its pillars.