Design Article
Q&A: Autosar's implications for auto engineers
By Guido Sandmann, Mathworks
11/13/2012 12:44 PM EST
Best strategies?
Q: Are there any real-world examples of results achieved through this approach?
Sandmann: IAV, an engineering company that works with OEMs such as the Volkswagen Group, has said that Simulink and Embedded Coder enabled them to automatically generate AUTOSAR-compliant C-code and other AUTOSAR artifacts. They recently presented an AUTOSAR project for a Drive-Select application that is on the road with the new AUDI A3 (here’s a link to the presentation, for reference: MathWorks Automotive Conference 2012-Presentation).
Q: What’s the best strategy for OEMs, suppliers, and other parties to work on standards such as AUTOSAR?
Sandmann: The best strategy is to adopt Model-Based Design for production code generation to reduce development time and increase product quality. What these engineers need is tool chain that supports AUTOSAR and enables iterative development across all phases of production ECU projects, which typically cannot strictly use a “top-down” or “bottom-up” development workflow. AUTOSAR fits seamlessly into this development paradigm and complements the goals of addressing challenges resulting from increasing complexity of the automotive applications and higher time-to-market pressure.
Today, high-level design tools have progressed to a stage where they can help engineers import and export AUTOSAR Software Component descriptions and generate AUTOSAR production code in one integrated, round-trip environment. What is notable with Simulink, is that it supports AUTOSAR using model configuration settings rather than AUTOSAR-specific blocks. As a result, a single
model can be used as
a golden reference for simulation, rapid prototyping, and production
code generation in both AUTOSAR and non-AUTOSAR environments,
facilitating software reuse. By using Model-Based Design in their
AUTOSAR projects, automotive design engineers are able to focus on
developing software component functionality, instead of getting
bogged down with ATUOSAR implementation details.
Guido Sandmann is the EMEA automotive marketing manager at MathWorks. He oversees messaging around various automotive industry standards ranging from AUTOSAR and MAAB to IEC 61508, ISO 26262 and MISRA C. He has more than 10 years of experience applying MathWorks products in various application areas. Guido has a Diploma degree in computer science from the University of Oldenburg.
Q: Are there any real-world examples of results achieved through this approach?
Sandmann: IAV, an engineering company that works with OEMs such as the Volkswagen Group, has said that Simulink and Embedded Coder enabled them to automatically generate AUTOSAR-compliant C-code and other AUTOSAR artifacts. They recently presented an AUTOSAR project for a Drive-Select application that is on the road with the new AUDI A3 (here’s a link to the presentation, for reference: MathWorks Automotive Conference 2012-Presentation).
Q: What’s the best strategy for OEMs, suppliers, and other parties to work on standards such as AUTOSAR?
Sandmann: The best strategy is to adopt Model-Based Design for production code generation to reduce development time and increase product quality. What these engineers need is tool chain that supports AUTOSAR and enables iterative development across all phases of production ECU projects, which typically cannot strictly use a “top-down” or “bottom-up” development workflow. AUTOSAR fits seamlessly into this development paradigm and complements the goals of addressing challenges resulting from increasing complexity of the automotive applications and higher time-to-market pressure.
Today, high-level design tools have progressed to a stage where they can help engineers import and export AUTOSAR Software Component descriptions and generate AUTOSAR production code in one integrated, round-trip environment. What is notable with Simulink, is that it supports AUTOSAR using model configuration settings rather than AUTOSAR-specific blocks. As a result, a single
model can be used as
a golden reference for simulation, rapid prototyping, and production
code generation in both AUTOSAR and non-AUTOSAR environments,
facilitating software reuse. By using Model-Based Design in their
AUTOSAR projects, automotive design engineers are able to focus on
developing software component functionality, instead of getting
bogged down with ATUOSAR implementation details. Guido Sandmann is the EMEA automotive marketing manager at MathWorks. He oversees messaging around various automotive industry standards ranging from AUTOSAR and MAAB to IEC 61508, ISO 26262 and MISRA C. He has more than 10 years of experience applying MathWorks products in various application areas. Guido has a Diploma degree in computer science from the University of Oldenburg.
|
|
|
|
|
Navigate to related information