persist an autosar-based powertrain control sw product line · observe evolution of autosar in...

Detroit, MI, 2014-10-23

J. Richenhagen (BEE-S), T. Tasky (BEA), A. Schloßer

(BEE-S)

PERSIST – An AUTOSAR-based

powertrain control SW product line

prepared for:

7th AUTOSAR Open Conference

Richenhagen, PERSIST – An AUTOSAR-based powertrain control SW

product line, 2014-10-23 1

© by FEV – all rights reserved. Confidential – no passing on to third parties

Agenda

Introduction and motivation

FEV SW strategy

Application examples

Summary and Outlook




FEV’s application areas

Diverse powertrain applications, SW development is cross-function

Business Region Europe

Business Region East

Business Region US

RE

RO

RU

BT BG BD BC BV BE BA

BUSINESS UNITS

Bu

sin

ess

Regio

ns

Advanced Applications

Gasoline Engines

Electrics/ Electronics

Vehicle Chassis&Transmission

Commercial, Industrial, Large Engines

Test & Instrumentation

Diesel Engines Passenger Cars

Software development

since 15 years

Application overview via

functional experts

Cross-function for

production code

Project-driven business

model/services




Software complexity raises, calibration is steadily more effort,

Software development costs increase

Left graphic: FEV, right graphic: R. Kremlicka, S. Mayer, G. Bittner, and G. Reich, Megatrends in der Automobilindustrie und ihre Auswirkungen auf den AC

Centrope . Wirtschaftsagentur Wien, 2011.

How to reduce code complexity?

How to reduce calibration effort?

How to ensure quality under market conditions (variants, time&cost pressure)?

5 15

25

0

20

40

60

80

100

1995 2010 2025(Prognosis)

pro

du

ct co

st sh

are

/%

year

Software

Electronics

Mechanics

0

2000

4000

6000

8000

10000

12000

14000

# la

be

ls

emission legislation

engine control

SCR

DPF

OBD

Sum




AUTOSAR strategy

Enable reuse by combining standards and customer needs

Source: AUTOSAR, 2013

Make software independent of hardware

De-couple software development

Increase software re-use through standardized basic software




New software business models

More software share by OEM and service suppliers

Source: Electroniksysteme im Automobil, Müchnen 12.-14-02.2012, Michael Walther, Robert Bosch GmbH

Increasing SW sharing by OEM / Tier-x

Tier-1 SW fraction will decrease

Required: SW competences

System integration

Supplier management

Functional powertrain excellence

Challenges

OEM: investment in own structures vs. low

costs today

Tier-1: multiple customers/OEM multiple

variants, how to keep consistency

Both: legacy code, architecture reflects

organization

0%

20%

40%

60%

80%

100%

2000 2005 2010 2015 2020

Bosch specific SW

Bosch platform SW

SW sharing (OEM/Tier-x)




Software

strategy




Bring reuse to projects

Integrated tool support for

the entire development

Consistent Architecture by

common design instruments

Follow relevant quality standards

PERSIST

FEV’s SW product line strategy

one SW architecture

project A project B ISO26262

quality config

release tests

ISO25010

Powertrain control architecture Enabling Reusable Software development for Intelligent System Tailoring




AUTOSAR Overview

Main elements and standardization status as of 2014

J. Richenhagen: Entwicklung von Steuerungs-Software für den automobilen Antriebsstrang mit agilen Methoden, Dissertation RWTH Aachen University, to be

published 2014

Runtime Environment (RTE)

BSW

APSW Actuator

SW-C

Services

Sensor

SW-C

Function

SW-C

Operating

System

Microcontroller

Abstraction

Function

SW-C

Commu-

nikation

ECU

Abstraction

Complex Driver

ECU-Hardware

SW module

standardized

interface

interface type

BSW-relevant

RTE-relevant

VFB-relevant




AUTOSAR specification status: focus Basic Software

Application Layer open to innovation, especially for powertrain

J. Richenhagen: Entwicklung von Steuerungs-Software für den automobilen Antriebsstrang mit agilen Methoden, Dissertation RWTH Aachen University, to be

published 2014

SW module

standardized

interface

interface type

BSW-relevant

RTE-relevant

VFB-relevant

specified and

standardized

partially

specified

not

addressed

Runtime Environment (RTE)

BSW

APSW Actuator

SW-C

Services

Sensor

SW-C

Function

SW-C

Operating

System

Microcontroller

Abstraction

Function

SW-C

Commu-

nikation

ECU

Abstraction

Complex Driver

ECU-Hardware

Powertrain-relevant

functions

How to fill conceptual gaps for powertrain domain?



Architecture specification instruments: Basis AUTOSAR

Fill architecture gaps through consistent approach

Reference Architecture

Base Architecture

Design Pattern

Design Concept

Design Principles

functional scope for architecture elements, hierarchical error management

Component-Based, reflection of physical components, wrapper for project work

model frame generation, access for automation

modularity, information hiding, design for change

instr

um

ent

priori

tization

hig

h

standard compliance is the base for architecture development

low

12

//upload.wikimedia.org/wikipedia/de/4/4f/Autosar_Logo.svg


PERSIST design patterns

Align project business and SW standardization by wrapper concept

customer

conditions

project

situation

!

!

? ?

!

!

? ?

introduce project-specific

components where required

keep interfaces of core

components stable

benefit

reusable core

components

flexibility

in projects

adaptability to

customer needs

Interface

mismatch Interface

unclear

solution solution adaption strategy

e.g. different

signal naming

e.g. Basic SW

not specified yet




Applications




Software architecture for FEV Diesel controls (simplified version)

Engine system physics, control strategy & software architecture match

Air filter

EgrHp:

high pressure EGR

ThrD: Throttle Valve

DOC

IntCo: Intercooler

Cyl: in_cylinder calculations

ExMfd: Exhaust Manifold

IntMfd: Intake Manifold

ExVlv: Exhaust Valve

AirFlt: Air Filter

MAF: Air Mass Flow

Sensor/weighting

TcHp: High Pressure

Turbocompressor Stage

InVlv: Intake Manifold

NOx based

EGR

coordinator

Dp – boost

setpoints

OxC: catalyst

PFlt: DPF

ExO2C: Exhaust oxygen

concentration

Physical based

component

Logic component

SW library




Software architecture for FEV Diesel controls (complex version)

Component reuse and scalability

SW library




Software architecture for FEV Transmission Control

Sustainable development over different projects

DCT

A1-Sample

ISO26262 related

AMT

Mass Production

Sub-functions

CVT

A1-Sample

Sub-functions

AMT

Mass Production

ISO26262 related

DCT

A1-sample

ISO 26262

DCT

Mass Production

AUTOSAR

AMT

Mass Production

ISO26262 related

Streamlined

Development




Summary and Outlook

Challenges

Rising SW complexity & costs

Industry answer: standardization

Result: more SW players (OEM, Tier-x)

Approach: FEV expands AUTOSAR to powertrain applications

PERSIST as a SW product line

AUTOSAR lacks powertrain specification for application layer

Achievement: AUTOSAR expansion with consistent guidelines

Outlook: SW product line, architecture-driven development

Observe evolution of AUTOSAR in powertrain domain

Projects will be more configuration & architecture-driven

Ease product line handling via database approach

5 15 25

0

20

40

60

80

100



Thanks for our attention!

Questions? ask now or email

[email protected]



mailto:[email protected]

persist an autosar-based powertrain control sw product line · observe evolution of autosar in...

Documents