02 Parte 02
02 Parte 02
in
VI Contents
▶ Contents
482 Drive and adjustment systems 496 Electromagnetic compatibility (EMC) and
482 Power windows interference suppression
483 Power sunroofs 496 EMC ranges
484 Seat and steering column adjustment 497 EMC between different systems in the
vehicle
485 Heating, ventilation and air conditioning 504 EMC between the vehicle and its
485 Electronic heater control surroundings
485 Electronically controlled air conditioning 508 Guarantee of immunity and interference
system suppression
Authors
Electric Actuators
Basic principles of networking
Dr.-Ing. Rudolf Heinz,
Automotive networking
Dr.-Ing. Robert Schenk.
Bus systems
Dipl.-Ing. Stefan Mischo,
Electrohydraulic Actuators
Dipl.-Ing. (FH) Stefan Powolny,
Electronic Transmission Control
Dipl.-Ing. Hanna Zündel,
Modules for Transmission Control
Dipl.-Ing. (FH) Norbert Löchel,
Dipl.-Ing. D. Fornoff,
Dipl.-Inform. Jörn Stuphorn,
D. Grauman,
Universität Bielefeld,
E. Hendriks,
Dr. Rainer Constapel, Daimler AG Sindelfingen,
Dipl.-Ing. T. Laux,
Dipl.-Ing. Peter Häussermann,
Dipl.-Ing. T. Müller,
Daimler AG Sindelfingen,
Dipl.-Ing. A. Schreiber,
Dr. rer. nat. Alexander Leonhardi,
Dipl.-Ing. S. Schumacher,
Daimler AG Sindelfingen,
Dipl.-Ing. W. Stroh.
Dipl.-Inform. Heiko Holtkamp,
Universität Bielefeld.
Antilock Braking System (ABS)
Traction Control System (TCS)
Automotive sensors
Electronic Stability Program (ESP)
Sensor measuring principles
Automatic brake functions
Sensor types
Hydraulic modulator
Dr.-Ing. Erich Zabler,
Dipl.-Ing. Friedrich Kost
Dr. rer. nat. Stefan Finkbeiner,
(Basic Principles of Vehicle Dynamics),
Dr. rer. nat. Wolfgang Welsch,
Dipl.-Ing. Heinz-Jürgen Koch-Dücker
Dr. rer. nat. Hartmut Kittel,
(Antilock Braking Systems, ABS),
Dr. rer. nat. Christian Bauer,
Dr.-Ing. Frank Niewels and
Dipl.-Ing. Günter Noetzel,
Dipl.-Ing. Jürgen Schuh
Dr.-Ing. Harald Emmerich,
(Traction Control Systems, TCS),
Dipl.-Ing. (FH) Gerald Hopf,
Dipl.-Ing. Thomas Ehret
Dr.-Ing. Uwe Konzelmann,
(Electronic Stability Program, ESP),
Dr. rer. nat. Thomas Wahl,
Dipl.-Ing. (FH) Jochen Wagner
Dr.-Ing. Reinhard Neul,
(Automatic Brake Functions),
Dr.-Ing. Wolfgang-Michael Müller,
Dipl.-Ing. (FH) Ulrich Papert
Dr.-Ing. Claus Bischoff,
(Wheel-Speed Sensors),
Dr. Christian Pfahler,
Dr.-Ing. Frank Heinen and
Dipl.-Ing. Peter Weiberle,
Peter Eberspächer
Dipl.-Ing. (FH) Ulrich Papert,
Basics
#BTJDTPGNFDIBUSPOJDT
1 Mechatronic system
Environment
Auxiliary
power
Actuator Sensor
engineering technology
Correcting Measured
variables variables
Reference
Feedback Processor variables
UAE1035E
Microsystem
Mechanical Electro-
components mechanical
components
segments segments beams of a circle stator comb stator comb segments segments
of a circle of a rectangle of a circle of a rectangle
Basic issues can often be clarified by pro- However, an analysis of the typical compo-
ducing relatively simple models of the nents in mechatronic systems shows that
components. If more detail is required, they can be composed of a few simple ele-
more refined component models are ments specific to the domains. These stan-
needed. The detailed models focus mainly dard elements are, for example:
on a specific physical domain: • In the hydraulic system: throttle, valve
• This means that detailed hydraulic mod- or electric line
els of common rail injectors are avail- • In the electronic system: resistor, capac-
able, for example. These can be simu- itor or transistor
lated using special programs with nu- • In the mechanical system: ground with
meric calculation methods that are friction, transmission or clutch (or the
exactly tailored to hydraulic systems. equivalent for micromechanics)
Cavitation phenomena have to be taken
into consideration, among other things. The preferable solution is that these ele-
• Detailed models are also needed to de- ments should be stored in a central stan-
sign the power electronics that trigger dard model library that is also decentrally
the injector. Again, this involves the use accessible to product development. The
of simulation tools which must be devel- essence of the standard model library is
oped specifically to design electronic a documentation of all the standard ele-
circuits. ments. For each element, this comprises:
The development and simulation of the Description of physical behavior in
software that controls the high-pressure words
pump and the power electronics in the The physical equations, parameters
control unit with the aid of the sensor (e.g. conductivity or permeability),
signals also takes place using tools that state variables (e.g. current, voltage,
are specially designed for this area of magnetic flux, pressure) and
the overall system. The description of the associated inter-
faces
As the components in the overall system
interact with each other, it is not sufficient In addition, a major part of the environ-
to consider specific detailed models of the ment is a reference model written in a
components in isolation. The optimum so- modeling language that is independent
lution is also to take into account the mod- of the tool. Overall, the library includes
els of other system components. In most reference models from the mechanical,
cases, these components can be repre- hydraulic, electronic, electrodynamic
sented by simpler models. For example, and software areas.
the system simulation that is focussed on
the hydraulic components only requires
a simple model of the power electronics.
Requirement
specification (what) Tool-supported
test-case creation
lopm
Specifications Validation,
feasibility
ent p
Design decisions
(”creative engineering
work”)
roces
Model,
Test cases
prototype
s
(Virtual)
sample
Performance
specifications
Design
UAE0943-1E
specification (how)
back level must also provide the pre- “Top-down” from system simulation,
scribed functionality in the event of a with the objective of overall optimiza-
problem. The condition for their imple- tion, through to finite element simula-
mentation is a high-reliability and high- tion to achieve a detailed understanding,
availability mechatronic architecture and “bottom-up” design engineering
which requires a “simple” proof of safety. from component testing through to
This affects both single components as system testing
well as energy and signal transmissions. • Horizontal:
mechatronic systems could achieve signifi- Step by step, the idea a “virtual sample”
cant progress for both users and vehicle is nearing our grasp
manufacturers.
Another challenge is training in order to
further an interdisciplinary mindset and
develop suitable SE processes and forms
of organization and communication.
Product
Develo
Customer
n
Functio
wishes
Validation Test
Requirement
analysis Acceptance test
pment
Model Test
cases
System
requirement
proces
specifications
Validation Test
System
specifications
Component
requirement
specifications
Validation Test
nts
prototypes cases
Compo
Component
UAE0944-1E
target
specifications
Component manufacture
"SDIJUFDUVSF
40%
Mechanics Mechanics Mechanics
Mechanics Mechanics Mechanics
20% Mecha- Mecha-
Mechanics
nics nics
0%
40% 30% 22% 8% 30% 30% 25% 7% 8%
Driving Safety Con- Info- Driving Safety Con- Info- Commun-
and braking venience tainment and braking venience tainment ication/
navigation
Fig. 1
SVA0032E
Source:
Proportion of electrics/electronics, Proportion of electronics,
approx. 22% approx. 35%
Mercer management
consulting
Technology of the present day shorten, the airbag and seat-belt preten-
In the 1990s the cabling work in a luxury sioners are set to emergency standby.
class vehicle amounted to around 3 km. The communication between the elec-
This figure clearly demonstrates how tronic control units cannot take more than
complex the vehicle system has become. fractions of a second. The more electronic
The growth of the proportion of electron- control units interact in the one complete
ics in the motor vehicle (Fig. 1) can mainly system, the more difficult it becomes for
be attributed to the growth in microelec- them to communicate undisturbed.
tronics and sensor technology. With the number of electronic control
At first, many of the new systems were units and the associated need for mutual
integrated into the vehicle by means of communication, the costs of developing
their own dedicated electronic control the systems rose as did the adaptation
unit. For the most part, the individual costs for making interfaces compatible.
electronic control units operated in mutual With the CAN bus (Controller Area Net-
independence. All the same, connecting work) developed by Bosch, a powerful and
lines became increasingly necessary be- widely used data bus system has become
tween electronic control units to enable commonplace in vehicles for the first time.
the exchange of data by means of PWM The data line of the CAN bus makes it pos-
signals, for example. Depending on the sible for the electronic control units to
vehicle class, there are between 20 and exchange specific and relevant items of
80 electronic control units fitted in today’s information with each other. At the start,
vehicles. They control such equipment as the network only comprised a few elec-
the engine, antilock brake system or the tronic control units, such as the engine-
airbags. The number of microcontrollers management system, the electronic stabil-
in the vehicle has therefore risen continu- ity program and the transmission control.
ously in recent years (Fig. 2). Gradually, further systems would expand
The components of the individual sys- this network, especially in the areas of
tems are optimally matched to each other. comfort and convenience and infotain-
The systems may originate from different ment. The CAN bus has gradually evolved
manufacturers that use previously agreed, into the standard for networking systems
albeit still their own, interfaces. The rain in the motor vehicle. Today it is the stan-
sensor, for example, “speaks” in a different dard for communication between elec-
way to the sensors for the engine manage-
ment. The following example demon- 2 Number of microcontrollers in the motor vehicle
110
traveling in front. If this distance is shorter
100
than a specified minimum distance, the 90
ACC electronic control unit sends this in- 80
formation to the engine management, the 70
60
ESP electronic control unit and the airbag
50
electronic control unit. The engine man- 40
agement reduces torque and thus driving 30
speed. If this is not sufficient, the elec- 20
SVA0033E
10
tronic stability program (ESP) must also
0
generate brake pressure to decelerate 1980 1985 1990 1995 2000 2005
the vehicle. If the distance continues to
systems). At this level, the driver is able functional component represents the tasks
to overrule the assistance systems at any of the navigation level, which are to inform
time. the driver of the driving route determined
At the stability level, there are the sub- by means of a mapping system (Fig. 3).
systems that are able to correct the deci- Vehicle guidance represents the guidance
sions taken at handling level if these hap- level, and stability intervention the tasks
pen to be outside the range of safe refer- of the stabilization level. The vehicle mo-
ence variables (e.g. ABS, ESP). This may tion coordinator determines the correcting
be the case when cornering or on wet road variables for the actuators, e.g. of the
surfaces, for example. drive and electronic stability program
At stabilization level, correcting vari- (ESP), from the information input by
ables for implementation by the vehicle’s vehicle guidance and stability interven-
actuators are determined. Information tion.
about the environment (e.g. road condi- Figure 4 shows how the functional com-
tion, air temperature, rain sensor signal) ponents of guidance level, stabilization
is still required at the various levels for level and vehicle actuators are related in
the implementation of the relevant tasks. a hierarchical structure within vehicle
These tasks can be assigned to func- motion. Communication relationships
tional components, which are the architec- between the components and interactions
tural elements of the functional architec- with other domains, e.g. body and interior,
ture. In this way, the driver information are also featured in the model.
Calculated distance
Vehicle motion
Vehicle motion
Vehicle guidance
Acceleration
requirement
Steering angle
Brake torque
Drive torque Steering angle
Steering angle
Stop lamp
SVA0035E
Body, interior
Rather, the decision is affected by non- ization stages. This required a decoupled
functional requirements such as safety, development process and the exploitation
availability, costs or resource availability. of synergies between subsystems. The de-
In addition to the functional requirements, velopment frameworks took into consider-
these requirements mainly determine how ation the dependencies and interface con-
the function is realized. The “how” is de- tents within the individual domains and
scribed by the architecture of the system. with the rest of the vehicle, as is the case
Different requirements result in different with a networked system such as ACC,
system architectures. for example.