ETAS Webinar ECU Basics

1 Confidential | ETAS/ESC | 2014-01-21 | ETAS GmbH 2014.
All rights reserved, also regarding any disposal, exploitation, reproduction,

editing, distribution, as well as in the event of applications for industrial property rights.
Electronic Control Unit(ECU) - Webinar
Basics of Automotive ECU
2 Confidential | ETAS/ESC | 2014-01-21 | ETAS GmbH 2014. All rights reserved, also regarding any disposal, exploitation, reproduction,
ETAS Embedded Systems Consulting
Embedded Software, AUTOSAR and Safety Consulting
Chandrashekara N (ETAS/ESC)
Lead Consultant Embedded Systems
Chandrashekara.N@etas.com
Phone+91 80 67836240
Mobile +91 9742399577
Importance of electronics and software within vehicles
Hardware architecture of a typical ECU.
Software Architecture , functions and implementation
Sample application of ECU within the vehicle.
Agenda
Hardware architecture of a typical ECU
Agenda
ENGINE
DRIVETRAIN
INSTRUMENTATION
SUSPENSION
STEERING
BRAKES
INFOTAINMENT
Major Systems in Automobiles
Forecast about Automotive Electronics in 2010
35% of the vehicle value will be electronics
5 to 8 Million lines of software code
Close to 70 ECUs in Cars
Almost Every subsystem will have electronic controls
Powertrain (Engine, Transmission, Hybrid etc.)
Chassis (Brakes, Steering, Roll Stability, etc.)
Body (Crash - Passive and in the future Active)
Body (Lighting, Windows, Locks)
Climate Control (Multi Zone, Instant Heat/Cool etc.)
Instrumentation
Infotainment (connecting both driver and passenger
to any available information ,Multi-media,
Navigation etc.)
Legislative Requirements for emission and fuel efficiency becoming critical
driving factors
Electronics growing
Estimates of 100-200 million source lines of code (SLOC)
To put this into perspective
There are 10,000 lines in a novel
> 20,000,000 SLOC
100,000 SLOC
6,500,000 SLOC
Sources
Pavey & Winsborrow, Demonstrating Equivalence of Source Code and PROM
Contents, Computer Journal Vol 36, No 7, 1993
Charette, This car runs on code, IEEE Spectrum, Feb 2009
Emission Legislation
Higher Power and Torque
Fuel Efficient
Smoother drivability
Cost effective
Need for an ECU
Improved exhaust-gas after-treatment systems
Greater fuel savings
Better engine protection
Customer Benefits
Function
Engine Control Units provide real-
time regulation of both Fuel
Injection and Ignition Timing thus
simultaneously guaranteeing
maximum engine performance and
minimum fuel consumption.
Engine management ECU
Reduced exhaust emission
Increased fuel efficiency
Improved drive-ability
Smoother and/or quieter engine operation
Safety functions
Comfort functions
Interactions with other systems
Diagnostics
Advantages of an ECU
Agenda
Automobile without ECU
Drivers
demand
Fuel-injection pump
+Governor
+Timer
Engine
Gear lever Gear box Wheels
Mechanical coupling
Automobile with ECU
Drivers
demand
Fuel-
injection
pump
Engine
Wheels
Electronic
Control
Unit
Electrical coupling
Mechanical coupling
Communication
Interface (CAN)
Sensors
Regulated Power
Supply Module (RPS)
Micro-processor
(or)
Micro-controller
(CPU) Electrically Erasable and Programmable
Memory (EEPROM)
Read only Memory (ROM) FLASH
Random Access Memory (RAM)
Non-volatile RAM (NVRAM)
Input and Output ( I / O ) Interface
System Clock
(Oscillator)
ECU Connector
ECU Hardware
ECU system blocks
Microprocessor/ Microcontroller
Executes the instructions as coded and generates output signals by
processing the information using specified control algorithms.
Input Output interface
Sensors - Registers the operating conditions and the desired values.
Actuators - Convert the electrical output from ECU to mechanical
parameters.
Memory Unit
Boot Memory (ROM/Flash)
Program memory (Flash)
Calibration memory (Flash)
Data memory (Flash, EEPROM, SRAM/Battery backed RAM)
Hardware architecture of a typical ECU.
Agenda
Standardize the software architecture of ECUs, contributing to
improved performance, safety and environmental friendliness.
Increasing amount of networked functionality and software
CO
2
reduction (Hybrids, E-Motors),
Safety enhancements (active, passive),
Because there was no common standard
Every company invented its own solutions
Integration of 3
rd
-party software creating prohibitive efforts
Who is responsible (for what), how to test (Methodology),
Implementation efficiency (e.g. Wrapper software, Interface
components)
Several tool chains required (own, plus those of 3
rd
parties)
Situation without AUTOSAR
OEM 'Standard Cores' to ensure correct network behavior
But Tier-1 had to integrate different SW for each OEM
integration problems difficult to identify and costly to debug
Hardware
Software
Hardware
Application
Software
(ASW)
Basic Software (BSW)
Proprietary
Hardware
Application
Software
AUTOSAR RTE
ECU Abstraction
and Complex Drivers
ECU Abstraction
and Complex Drivers
ECU Abstraction
and Complex Drivers
Microcontroller Abstraction
Services
AUTOSAR Runtime Environment (RTE)
Application Layer
Microcontroller
A
D
C
D
I
O
C
C
U
P
W
M
L
I
N
C
A
N
S
P
I
E
E
P
R
O
M
F
L
A
S
H
W
D
T
G
P
T
E
x
t
.

B
U
S
M
C
U

P
o
w
e
r

&

C
l
o
c
k

U
n
i
t
C
e
.
g
.

C
C
U
e
.
g
.

P
C
P
e
.
g
.

T
P
U
F
l
e
x
R
a
y
S
C
I
I/O Drivers
P
O
R
T

D
r
i
v
e
r
A
D
C

D
r
i
v
e
r
D
I
O

D
r
i
v
e
r
P
W
M

D
r
i
v
e
r
I
C
U

D
r
i
v
e
r
Microcontroller Drivers
W
a
t
c
h
d
o
g

D
r
i
v
e
r
M
C
U

D
r
i
v
e
r
G
P
T

D
r
i
v
e
r
Communication Drivers
C
A
N

D
r
i
v
e
r
L
I
N

D
r
i
v
e
r
S
P
I

H
a
n
d
l
e
r

D
r
i
v
e
r
Memory Drivers
R
A
M

T
e
s
t
i
n
t
e
r
n
a
l

E
E
P
R
O
M

D
r
i
v
e
r
i
n
t
e
r
n
a
l

F
l
a
s
h

D
r
i
v
e
r
Communication Services
Generic
NM
Interf.
F
l
e
x
R
a
y

N
M
FlexRay
TP
DCM
Diagnostic
Com.
Manager
IPDU
Mux
Communication Hardware Abstraction
Memory
Services
NVRAM
Manager
C
R
C

L
i
b
F
l
a
s
h

C
h
e
c
k
System Services
F
u
n
c
t
i
o
n

I
n
h
i
b
i
t
i
o
n

M
a
n
a
g
e
r

F
I
M
W
a
t
c
h
d
o
g

M
a
n
a
g
e
r
D
e
v
e
l
o
p
m
e
n
t

E
r
r
o
r

T
r
a
c
e
r
D
i
a
g
n
o
s
t
i
c

E
v
e
n
t

M
a
n
a
g
e
r

D
E
M
I/O Hardware
Abstraction
Memory Hardware Abstraction
Memory Abstraction Interface
Onboard Device
Abstraction
External
Watchdog
Driver
CAN
NM CAN
TP
Ext. Flash
Driver
Flash EEPROM
Emulation
F
R

D
r
i
v
e
r
LIN
Interface
E
x
t
.

C
A
N

D
r
i
v
e
r
CAN Interface
C
A
N

t
r
a
n
s
c

D
r
i
v
e
r
E
x
t
.

F
R

D
r
i
v
e
r
FR Interface
F
R

t
r
a
n
s
c

D
r
i
v
e
r
Ext.
EEPROM
Driver
EEPROM
Abstraction
Watchdog Interface
PDU Router
LIN
TP
AUTOSAR
COM CAN
Gen.
NM
L
I
N

C
o
m
m
u
n
i
c
a
t
i
o
n

S
t
a
c
k
B
S
W

S
c
h
e
d
u
l
e
r
E
C
U

S
t
a
t
e

M
a
n
a
g
e
r
C
o
m
m
u
n
i
c
a
t
i
o
n

M
a
n
a
g
e
r
I/O Hardware
Abstraction
C
A
N

S
t
a
t
e

M
a
n
.
F
l
e
x
R
a
y

S
t
a
t
e

M
a
n
.
A
U
T
O
S
A
R

O
S
L
I
N

S
t
a
t
e

M
a
n
.
Objectives: Basic SW: Decoupling of Hardware and Application Software
Application SW: Relocation / Reuse of SW-Components between ECUs
ECU-Hardware
AUTOSAR RTE
AUTOSAR Int.
SwitchEvent
Standardized Interface
Microcontroller Abstraction
Std. AUTOSAR
Interface
Services
Std. Interface
ECU
Abstraction
AUTOSAR
Interface
Std. Interface
Complex
Device
Drivers
AUTOSAR
Interface
Standardized
Interface
Communi-
cation
Std. Interface
Standardized
Interface
Operating
System
DIO
check_switch ()
AUTOSAR Interface
LightRequest
AUTOSAR Interface
Front-Light Manager
get_keyposition()
AUTOSAR Interface
Headlight
set_current ()
CAN Driver
switch_event(event)
switch_event
(event)
request_light
(type, mode)
request_light(type, mode)
set_light(type, mode)
set_light(type, mode)
PWM
S
t
a
n
d
a
r
d
i
z
e
d
I
n
t
e
r
f
a
c
e
Use case Front-Light Management
Read the Accelerator Pedal value and calculate the required Torque to be
generated from the Engine.
This function has to be repeated every 20 milliseconds.
Steps:
Read the data captured by the Analog-to-Digital Converter (ADC)
on the Channel to which the Accelerator Pedal is Connected.
Using this data, look-up the value from a 3D Table (Map), which
also contains the Engine RPM (Rotations per Minute), as another
input axis.
Take the output value from the Map, multiply it by a correction
factor (depending on, for e.g. Performance or Economy Mode).
The output of this calculation is the Torque to be generated by
the Engine.
Repeat this sequence every 20 milliseconds.
Example Software Function / Task
Sample application of ECU within the vehicle
Agenda
Chassis Systems ECU
The active chassis control help divers maintain
control over a wide range of challenging situations.
It is blend of broad range of braking, steering and
suspension technologies to enhance vehicle
control and help make the drive experience safer.
Modern automobiles are unthinkable without
systems like ABS or ESP.
Function
Improved steerability
Increased track stability
Reduced risk of skidding when braking
Reduced ABS braking distance
Customer Benefits
Body Control ECU
The BCM handles various switch inputs, LAN data,
and authentication for keyless entry devices in a
concentrated manner. (Power Seat Electronic
Control Unit, Anti-pinch Power Window Electronic
Control Unit) and many other functions.
Function
Safety systems
Passive Safety Systems
Airbag system
Seat Belt System
Steering Wheel System
Vision System
Pedestrian Protection
Tire Pressure Monitoring
Active Safety Systems
Brake systems
Driver Assist systems
Steering Control
Linkage & Suspension
Integrated Safety System
Pre-Crash Emergency Brake
systems
Lane Departure warning
Park assist
Roll Over protection
Collision Warning
Software and Safety Consulting
Service Portfolio
Embedded Software
Development
Embedded Software
Development
Systems Engineering Systems Engineering
Functional Safety Functional Safety
Optimized Software
Architectures
Optimized Software
Architectures
Process Improvement Process Improvement
Competencies
Services
Software Development and
Rapid Prototyping
Operative Support and
Project Management
Organizational Change
Management
Training and Coaching
ETAS AUTOSAR Solutions
Overview of ETAS AUTOSAR Solutions
Basic Software
Configuration and
Generation
(RTA-OS, RTA-RTE, BSW*)
ECU 1
ECU 2
ECU n
Software Component
Implementation
(Model-based, Hand Code)
SW
Make
/Build
ASCET
*)
AUTOSAR 4.0 Basic software modules developed and provided by Bosch.
Developed to meet ASIL-D requirements. Roadmap details defined by Bosch.
Consulting and Engineering Services
(Training, Coaching, SW Development and Integration, On-site Support)
AUTOSAR
System
Specification
(ISOLAR-A)
Importers of
non-AR formats
Virtual Validation
Platform
(based on RT-Linux)
ISOLAR
EVE
Third-Party Tools
ETAS AUTOSAR Solutions
INCA
*.arxml
SWC.c
RTE.c
OS.c
*.arxml
BSW.c
dbc/fibex/ldf
ETAS Support for Automotive Embedded Systems & Software
Any Questions?
Vielen Dank
Thank you
Merci beaucoup
Gracie Mille

ETAS Webinar ECU Basics

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ETAS Webinar ECU Basics

Încărcat de

Drepturi de autor:

Formate disponibile

1 Confidential | ETAS/ESC | 2014-01-21 | ETAS GmbH 2014.

All rights reserved, also regarding any disposal, exploitation, reproduction,

S-ar putea să vă placă și