Automotive Mechatronics Automotive Networking Driving Stability Systems Electronics 1st Edition by Konrad Reif 9783658039752 3658039752
Automotive Mechatronics Automotive Networking Driving Stability Systems Electronics 1st Edition by Konrad Reif 9783658039752 3658039752
com
https://ebookball.com/product/automotive-mechatronics-
automotive-networking-driving-stability-systems-
electronics-1st-edition-by-konrad-
reif-9783658039752-3658039752-18440/
OR CLICK BUTTON
DOWLOAD EBOOK
https://ebookball.com/product/digital-marketing-in-the-automotive-
electronics-industry-redefining-customer-experience-through-digital-
customer-engagement-1st-edition-by-uli-schneider-jurgen-hoika-
isbn-9783031307201-3031307208-2487/
ebookball.com
https://ebookball.com/product/automotive-cyber-security-introduction-
challenges-and-standardization-1st-edition-by-shiho-kim-rakesh-
shrestha-9811580537-9789811580536-20010/
ebookball.com
https://ebookball.com/product/automotive-cyber-security-introduction-
challenges-and-standardization-1st-edition-by-shiho-kim-rakesh-
shrestha-isbn-9811580553-978-9811580550-16670/
ebookball.com
https://ebookball.com/product/modelling-support-for-design-of-safety-
critical-automotive-embedded-systems-1st-edition-by-dejiu-chen-rolf-
johansson-henrik-lonn-yiannis-papadopoulos-anders-sandberg-fredrik-
torner-martin-torngren-isb/
ebookball.com
Marketing Innovations in the Automotive Industry
International Series in Advanced Management Studies 1st
Edition by Candelo ISBN 3030159981 978-3030159986
https://ebookball.com/product/marketing-innovations-in-the-automotive-
industry-international-series-in-advanced-management-studies-1st-
edition-by-candelo-isbn-3030159981-978-3030159986-24540/
ebookball.com
https://ebookball.com/product/reliability-in-automotive-and-
mechanical-engineering-determination-of-component-and-system-
reliability-1st-edition-by-bernd-bertsche-
isbn-3642070493-978-3642070495-17780/
ebookball.com
https://ebookball.com/product/chassis-handbook-fundamentals-driving-
dynamics-components-mechatronics-perspectives-1st-edition-by-bernhard-
heiaying-metin-ersoy-9783834897893-3834897892-18414/
ebookball.com
https://ebookball.com/product/3d-automotive-modeling-an-insider-s-
guide-to-3d-car-modeling-and-design-for-games-and-film-1st-edition-by-
andrew-gahan-isbn-0240814285-9780240814285-24956/
ebookball.com
https://ebookball.com/product/ebook-pdf-sustainable-supply-chain-
management-learning-from-the-german-automotive-industry-1st-edition-
by-minh-trang-rausch-phan-patrick-
siegfried-3030921557-978-3030921552-full-chapters-21854/
ebookball.com
Bosch Professional Automotive
Information
Automotive
Mechatronics
Automotive Networking · Driving
Stability Systems · Electronics
Bosch Professional Automotive Information
Bosch Professional Automotive Information is a definitive reference for
automotive engineers. The series is compiled by one of the world´s largest
automotive equipment suppliers. All topics are covered in a concise but
descriptive way backed up by diagrams, graphs, photographs and tables
enabling the reader to better comprehend the subject.
There is now greater detail on electronics and their application in the motor
vehicle, including electrical energy management (EEM) and discusses the
topic of intersystem networking within vehicle. The series will benefit
automotive engineers and design engineers, automotive technicians in
training and mechanics and technicians in garages.
Konrad Reif
Editor
Automotive Mechatronics
Automotive Networking, Driving Stability
Systems, Electronics
Editor
Prof. Dr.-Ing. Konrad Reif
Duale Hochschule Baden-Württemberg
Friedrichshafen, Germany
[email protected]
Springer Vieweg
© Springer Fachmedien Wiesbaden 2015
This work is subject to copyright. All rights are reserved, whether the whole or part of the material is
concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting,
reproduction on microfilm or in any other way, and storage in data banks. Duplication of this publication
or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965,
in its current version, and permission for use must always be obtained from Springer. Violations are liable
to prosecution under the German Copyright Law.
The use of general descriptive names, registered names, trademarks, etc. in this publication does not imply,
even in the absence of a specific statement, that such names are exempt from the relevant protective laws
and regulations and therefore free for general use.
▶ Foreword
▶ 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,
X Authors
#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
Basics of mechatronics Development methods 5
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)
Basics of mechatronics Outlook 7
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
8 Architecture Overview
"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
10 Architecture Overview
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
13
Architecture Vehicle system architecture
Vehicle motion
Vehicle guidance
Acceleration
requirement
Steering angle
Brake torque
Drive torque Steering angle
Steering angle
Stop lamp
SVA0035E
Body, interior
14 Architecture Vehicle system architecture
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.
5 Functional architecture
System level
Subsystem
level
Hardware Software
architecture architecture
Network architecture
SVA0036E
16 Architecture Vehicle system architecture
fields of application or domains and the reliability are fulfilled by the multiple use
comparatively slow growth of networking of proven standards. Autosar concerns
within these domains. itself with all vehicle domains.
Based on the uniform electronics plat-
Bus systems for the individual domains are form, which primarily consists of standard
becoming more specialized due to their software modules, each vehicle manufac-
plainly different requirements. With the turer is then free to build its own specific
CAN in the drivetrain as the point of ori- content. They enable integration into the
gin, new bus systems such as the LIN sub- electronics network. These software func-
bus have begun to infiltrate the area of tions permit differentiation between the
body electronics or FlexRay in the case of competition.
safety-relevant x-by-wire systems. In the Not only does software have to conform
multimedia field, where demands for high to the Autosar standard. The electronic
data rates but low safety requirements control units must be built in such a way
prevail, bus systems such as Bluetooth that the Autosar software is able to run on
have started to make an appearance. them. The Autosar members are hoping
Breaking through these traditional do- that the new development methods yield
mains with ever more applications leads such benefits as shorter development
to known consequences, e.g. dramatic in- times and lower development costs.
crease in complexity, high start-up costs,
increasing integration times and costs, and Until now, it was often the case that dedi-
more demanding work in customer service cated electronic control units would be
as a consequence of diagnostics no longer developed and fitted for new functions
being manageable. A solution for these (e.g. electronic transmission control,
multidimensional optimization tasks has in antilock brake system, air conditioning).
the past been sought in the software field. The number of electronic control units
In the case of technical systems in particu- fitted in the vehicle grew continuously;
lar, the paradigm is still king, especially in today’s generation of vehicles are
software realizations, because the absence equipped with between 20 and 80 elec-
of physical boundaries supports unlimited tronic control units. In future vehicle gen-
growth. erations, it is intended that all functions
be covered by a network of 10 to 20 elec-
Autosar Initiative tronic control units. Some of these will
The Autosar Initiative (AUTomotive Open function a little like main computers that
Systems ARchitecture) was founded in will bundle the important function groups
July 2003 by several vehicle manufacturers together. These include the drivetrain,
and suppliers – Bosch among them. Their suspension management system, body
global objective is the joint development and interior and the multimedia/telematics
of an open system architecture for future domain. On data buses, sensors with inte-
automotive applications. The aims of the grated electronics output processed and
partnership include the standardization verified signals, while the buses carry the
of fundamental system functions (basic relevant control commands to actuators
software) and function interfaces; they with integrated triggering electronics.
will replace the company-specific, individ- In future, new functions will often be
ual solutions used to date. Model-based able to use the existing computer architec-
concepts and methods ought to reduce ture up to its performance limit and will
complexity in spite of an expanding range be widely realized in the form of a soft-
of functions. The demands for quality and ware add-on. This would therefore render
17
Architecture Vehicle system architecture
&MFDUSPOJDDPOUSPMVOJU
1 Design of a control unit using the example of an ME Motronic (sectional view through housing cover)
UAE0992Y
20 Electronic control unit Data processing
Fig. 2
a Period duration stored in an EEPROM.
(fixed or variable)
Time
b Variable on-time
| Performance of electronic control units 21
Control unit
The performance of electronic control units I/O facilities for timer-controlled signals and
goes hand-in-hand with advances achieved in an integrated analog-digital converter at the
the field of microelectronics. The first gasoline end of the 1980’s. It was then possible to cre-
injection systems were still analog – with lim- ate relatively powerful systems. Figure 3 shows
ited flexibility in the implementation of control a comparison between the performance of a
functions. These functions were constrained fuel-injection system (LH3.2) and an ignition
by the hardware. system (EZ129K) – equipped with 80C515
Progress advanced in quantum leaps with controllers – and that of the succeeding
the arrival of digital technology and the micro- Motronic systems. The ME7 has approximately
controller. The entire engine management sys- 40 times the performance capability of the
tem was taken over by the universally applica- LH/EZ combination with a clock frequency of
ble semiconductor microchip. The actual con- 40 MHz. With the benefit of a new generation
trol logic in microcontroller-controlled systems of microcontrollers and a further increase in
is in a programmable semiconductor memory. clock frequency on the ME9, this figure will
From systems that initially simply con- increase to a factor of well over 50.
trolled fuel injection, complex engine-manage- In the foreseeable future microcontrollers
ment systems were then developed. They con- will process more than just digital control se-
trolled not only fuel injection but also the quences. Signal processors are integrated that
ignition system including knock control, ex- can also directly process the signals provided
haust-gas recirculation and a whole variety by knock sensors, for example.
of other systems. This continuous process of
development is bound to continue in a similar Advances in the development of semiconduc-
vein over the next decade as well. The integra- tor memory chips are also worthy of note.
tion of functions and, above all, their complex- Complex control programs require an enor-
ity are constantly increasing. This pattern of mous amount of memory space. The capacity
development is only possible because the of memory chips at the start of the 1980s
microcontrollers used are also undergoing was still only 8 kilobytes. The ME7 now uses
a similar process of improvement. 1-megabyte chips and soon memory capacities
Microcontrollers in the Intel 8051 family of 2 megabytes will be required. Figure 3
were used quite some time until they were re- shows this pattern of development and likely
placed with 80515 derivatives with additional future trends.
Fig. 3
Chart illustrating
▶ Performance
3 Development of electronic control units capability of
engine-management
2,500
160
kB
kB
50
136
kB
C167 24MHz
ME7.0 ▶ Data memory
10
Flash: 512 kB
ROM
RAM
80C517A 16MHz
capacity (RAM)
M4.4.1
128 kB
4
Flash: 128 kB
86
80C517 15.8MHz
8 kB
M4.3 Flash: 64 kB
By way of comparison:
The performance
80535 12MHz
M1.8
55
capability of a state-
32 kB
EPROM: 32 kB
SMK1930E
0.5 kB
of-the-art engine-
1
80535 12MHz
LH3.2 + EZ129K
60
EPROM: 32 kB
management system
1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 far exceeds that of
Apollo 13.
22 Electronic control unit Digital modules in the control unit
Microcontroller
(CPU) Volatile read/write (ROM, EPROM, write memory
memory (RAM) flash EPROM) (EEPROM)
for variable data For programs and
Arithmetic and logic unit permanent data records
(ALU) Memory capacity
4-, 8-, 16-, 32-bit Memory capacity Memory capacity 32 bytes to
64 bytes to 32 kbytes 2 kbytes to 512 kbytes 1 kbyte
…
(Timer, time SPI,
processing unit, CAN)
Electronic control unit
input capture,
output-compare
register)
Communication
Monitoring Resolution Resolution with external
circuit 50 ns 8 to 10 bit Data rate chips via
(watchdog) Counter Time range 4 to 32 8 to 32 200 bit/s to address/
8 to 64 bit 50 ns to 1s channels channels 1 Mbit/s data bus
… … … … … …
UAE0454-1E
Digital modules in the control unit
23
24 Electronic control unit Digital modules in the control unit
Semiconductor memories
Programmable
on a program- Programmable Static Dynamic
in the circuit memories memories
ming device
UV Electrically
Read-only erasable erasable
UAE0465-1E
The control unit program reacts to several to the speed sensor signal. For this pur-
of these interrupts. An interrupt source pose, the engine-speed signal is connected
can therefore request an interrupt while to a microcontroller interrupt input. Every
another interrupt routine is currently falling signal edge at this input interrupts
being executed. Every interrupt source the current calculations that are in prog-
therefore has a fixed priority assigned to ress and forces a branch to the interrupt
it. The priority controller decides which routine. After executing the commands in
interrupt is allowed to interrupt another the interrupt routine, the program contin-
interrupt. ues execution at its point of origin.
In order to perform certain operations
Tooth interrupt the control unit program requires the time
The crankshaft is equipped with a pulse taken for the crankshaft to travel between
wheel (Fig. 2a) that has a certain number one tooth and the next. This calculation is
of teeth on its circumference. The teeth performed by an internal timer. This is a
are scanned by the speed sensor. This freewheeling 16-bit counter (Fig. 3) that
allows the crankshaft position to be re- increments at a certain rate, depending on
corded. The typical distance between the microcontroller oscillator clock cycle.
a pair of teeth on the crankshaft sensor This time frame amounts to about 0.5 µs.
wheel is 6°. In order to determine the When the falling tooth flank occurs,
crankshaft position, the control unit pro- the current counter status is recorded.
gram must execute certain routines as The difference (and therefore the tooth
each tooth is detected. At 6,000 rpm the interval) is calculated using the stored
detection time between two teeth is ap- counter from the previous tooth.
proximately 300 µs. Every command in
these routines must be executed within Example: crankshaft position calculation
this time. This requires a rapid response The engine-management system (Motronic
for gasoline engines, EDC for diesel en-
gines) must know the crankshaft position
2 Crankshaft sensor ring with speed sensor at any given point in time. This is a pre-
requisite for injecting into the right cylin-
a
der at the right time and ensuring that ig-
nition takes place at the calculated ignition
angle (Motronic systems). In order to
Tn+1
Tn
Time t
Speed sensor
b
signal
Digital
signal
SAE1004E
SAE1005E
detect the engine position and the engine Since the synchronization program runs
speed, the control unit evaluates the speed over several teeth at fast engine speeds,
sensor signal (Fig. 2b). it has to be interrupted by the tooth inter-
There is gap in the crankshaft sensor rupt. The tooth interrupt is given higher
wheel in which two teeth are missing. priority than the synchronization pro-
The tooth space has a defined position gram.
in relation to the top dead center (TDC) of
cylinder no. 1. The control unit program Ignition interrupt
has to synchronize itself with this tooth The ignition output takes place within a
space. This is done by measuring the times certain crankshaft range, depending on
between two consecutive falling tooth the value from the ignition map. Since the
flanks. The time for the tooth space is specified ignition angle has to be adhered
considerably greater than the time before to exactly, the ignition output is controlled
and after the gap. Following a “short – by an interrupt. Like the synchronization
long – short” sequence the last thing to program, the ignition interrupt is also
be scanned was the falling flank of the called up once per combustion cycle.
second tooth after the space. The control unit program is aware of the
The crankshaft has rotated by 6° for crankshaft position in the 6° framework.
each falling tooth flank that has been de- However, this framework is not accurate
tected by the control unit program. This is enough for ignition angle output. For this
how the control unit program knows the reason, accurate ignition output between
crankshaft position within this time frame. two teeth must take place as well as this
Since cylinder no. 1 is in the tooth space approximate counting for the last 0 to
position in the vicinity of top dead center 6 crankshaft degrees. This is done using
(TDC) or bottom dead center (BDC), an ad- a timer (Fig. 5). Ignition angle output that
ditional signal is required to determine the was purely timer-controller would lead
position. The camshaft sensor provides to an ignition angle output error at high
a different voltage level in both cases. engine speed dynamics.
The control unit is therefore able to Firstly, the ignition coil must be enabled
uniquely assign the crankshaft and for a defined time (the so-called dwell pe-
camshaft positions. riod). In order to do this, the program cal-
culates the switch-on time by calculating
Combustion-synchronous interrupt
Some calculations have to be performed 4 Triggering the interrupt synchronously with
for every combustion cycle. For example, combustion
the ignition angle and the injection have
to be recalculated synchronously with
combustion for each cylinder. The pro-
gram does this by branching to the “syn-
Start synchronization
chronization program” after certain teeth
program
(Fig. 4). This interrupt takes place after
every 30 teeth (ignition interval) for a four-
Tooth counter elapsed
cylinder engine, and after every 20 teeth Synchronization program triggered
for a six-cylinder engine.
The synchronization program is fixed to Second tooth after the gap: reference mark
a certain tooth position and has to be exe- Preset tooth counter for triggering the
SAE1006E
backwards from the ignition angle at which 5 Dwell and ignition time output
the ignition coil has to be switched off.
This makes it possible to calculate the
tooth after which the ignition coil has to
be switched off (approximate counting Ignition output
in 6° time frame). The remaining angle
(detailed counting 0 to 6°) is converted Switch on the ignition coil
Enter the time for ignition
into an output time using the current en-
gine speed. As soon as the specified tooth Enter time for detailed counting
position has been reached using approxi-
mate counting, a time is loaded with the Synchronization program:
SAE1007E
Calculate the dwell period and ignition angle
output value from the detailed counting.
Preset the tooth counter for the dwell period
When this time period expires, the timer time (approximate counting)
triggers an interrupt. The commands that
switch on the ignition coil are programmed
in this interrupt routine. Then the timer Background program
is preset to the dwell period value, which All other activities that do not run in
causes an interrupt to be triggered when an interrupt routine or a time frame are
the timer elapses, switching off the igni- processed in the background program.
tion coil and therefore initiating ignition. At fast engine speeds, the synchronization
program and the tooth interrupt are called
Time frame frequently, leaving little CPU time for the
Many control algorithms have to run background program. The time taken for a
within a certain time frame. Lambda con- complete run-through of the background
trol, for example, has to be processed program therefore increases rapidly with
within a fixed time frame (e.g. 10 ms) so the increasing engine speed. The back-
that the correcting variables are calculated ground program must therefore only
quickly enough. contain low-priority functions.
30 Electronic Control Units (ECUs) Software Development
System System
Specification Test initialization delivery
Function analysis QA2
specification
System
QA1 integration/test
Function Function
initialization delivery
Function analysis QA2F
specification
æ UTS0325E
æ UTS0326E
Function
QA1F integration/test
Function
Implementation development
Electronic Control Units (ECUs) Software Development 31
쐌 The persons in charge of ReUse and These guidelines also serve as a source of
the project discuss the application and knowledge for effective code configuration in
establish the scopes and deadlines order to counteract the limitations in relation
together. to memory capacity and run time in the pro-
gramming of microcontrollers.
Tools for Creating Software As the wide variety of tools demonstrates, the
As well as the formal aspects such as process process involved in creating the software for
and programming guidelines, it is crucially an ECU of the latest generation is highly
important to ensure that the tools are subject complex. Figure 4 provides a simplified
to constant support in the interests of prod- overview of the interplay between the indi-
uct quality. Figure 3 provides an overview of vidual tools from the specification through to
the tools currently used for the various devel- the finished ECU program.
opment phases. Significant features of this
tool chain are: By way of example, two component parts of
쐌 constant support throughout the entire de- the tool chain will now be explained in closer
velopment process and detail:
쐌 product-specific, optimized solutions with 쐌 Design with ASCET-SD and
tools partly developed in-house. 쐌 Vehicle simulation with TCM-Simutec.
Test/application
Documentation: MS Word
INCA/PC
Key:
ASCET: advanced simulation and control
æ UTS0328E
engineering tool
ASCET-SD: ASCET software developer
StP: software through pictures
(Aonix) for OO modeling
ESPRIT: engineering software-production
5 Function design with ASCET-SD
user interface for tools
Innovator: Software-development
environment (MID)
Codewright: Software-development
environment (Premia)
DAMOS: database for microcontroller-
oriented systems
INCA-PC: integrated car application system
TCM-Simutec: Vehicle simulator
æ UTS0329Y
The next step is the automatic C-code creation Process and Maturity Model
and the creation of the corresponding data A clear definition of the development process
files for the application from the models. and the corresponding implementation in the
projects are made possible by a software de-
For further information, log on to velopment which can be evaluated with a ma-
turity model such as CMM (capture maturity
http://www.etas.de model).
2 4
1 Fig. 6
1 ASCET-SD and
3 INCA-PC
2 ASCET hardware
æ UTS0330Y
æ UTS0311Y
(ETAS ES 1000.2)
3 ETK
4 ETC-Simutec
(laboratory car)
34 Electronic Control Units (ECUs) Software Development
8 Software layer model The operating system with its services and the
hardware-compatible software are imple-
Transmission software from mented on this hardware:
vehicle manufacturer or Bosch
ERCOSEK EEPROM Hardware KWP 2000
(OS) driver Input/Output driver
Program
library Device Device Device
driver driver driver
Component
driver The interface layer and program library for
the application software contain:
Operating system Diagnosis Diagnosis Security
handling monitoring software
æ UTS0331E
functions (SSK)
Hardware EEPROM KWP2000 Shift by wire
handling application functions
Cooperative Scheduling
CPU core SPI TPU MIOS CAN UART In the case of cooperative scheduling,
timer and (2) (2)
a task can only be interrupted between two
Memory, hardware, driver, etc.
processes by a higher-priority task (Figure 10).
Electronic Control Units (ECUs) Software Development 35
The advantages of this procedure are low and a response time that is not dependent on
memory requirement (register banks, stack), process implementation. The disadvantages
simple management, and data consistency. are increased memory requirement (stack,
The disadvantages are the limited response register banks) and data-consistency prob-
time (dependent on the process run time) lems.
and the jitter over the task period.
Mixed Scheduling
Preemptive Scheduling ERCOSEK offers the option of mixing both
Owing to the drawbacks of cooperative types of scheduling in one application.
scheduling, preemptive scheduling is used in A combination of hardware and software
operating systems which operate as real-time scheduling serves this purpose. Figure 12
systems. shows the distribution between cooperative
With this form of scheduling, a higher-pri- and preemptive using the priorities assigned
ority task can interrupt a lower-priority task to the tasks.
at any time (Figure 11). The advantages of A software call starts the operating system.
this procedure are the very short response It can support different application modes
times, the minimal jitter over the task period, (e.g. different task sets for initialization, oper-
Task Activation
and start
Task B
Task B
Process 1
Task
Process 3
…
æ STS0334E
Prozess n Task A
Time t
Activation Task B
Hardware-based
Start Task B
scheduling
Task B preemptive
Priority
Task
æ STS0335E
cooperative
Task A
Time t Distribution
36 Electronic Control Units (ECUs) Software Development
13 Application-mode change ation and ECU run-on, Figure 13). Each ap-
plication mode consists of an initialization
phase and an execution phase. Interrupts are
Application
prohibited during initialization of an applica-
Mode n Mode n+1 tion mode.
Further documents on the subject of
ERCOSEK / OSEK can be found on the
Mode
Internet at:
Init Execution Init Execution http://www.etas.de
http://www.osek-vdx.org
æ STS0336E
Acquisition of Input and
Output Variables
Zeit t
Access to the hardware is obtained within the
framework of the software layer model in ac-
14 Hardware access in the layer model cordance with three layers (Figure 14):
쐌 user layer,
쐌 configuration layer, and
User layer 쐌 hardware layer.
"Low-level"-channels
Electronic Control Units (ECUs) Software Development 37
CAN - Bus
Fig. 15
a Conventional
b With CAN
38 Electronic Control Units (ECUs) Software Development
3 Bit rates as a function of cable (bus) length The system must also be resistant to tempera-
Maximum bit rate Bus length
ture and moisture. The CAN bus has also
kbit/s m gained acceptance in the field of automation
1000 40 technology. Table 3 lists the maximum possi-
500 100 ble data rates for different cable lengths.
250 250 Figure 16 shows the circuit-engineering
125 500
implementation of the CAN interface in an
40 1000
ECU.
Table 3
17 Use of dual-port RAM with the CAN bus 19 CAN standard data frame
recessive
Message 1 low high
1 11 1 1 1 4 0…64 15 1 1 1 7 3
Message 2 dominant
Bus idle
Start of Frame
Data Field
CRC Sequence
CRC Delimiter
ACK Slot
ACK Delimiter
End of Frame
Intermission
CAN-
Bus CPU
Message n
æ UTS0340E
æ UTS0342E
workload
Acceptance Message Host CPU
filter management
Arbitration Control CRC Acknowledge
Field Field Field Field
NODE A recessive
dominant 1 11 1 1 18 1 2 4 0…64 15 1 1 1 7 3
dominant
Bus idle
Start of Frame
Identifier
SRR Bit (R)
IDE Bit(R)
Extended Identifier
RTR Bit(D)
(2 reserved (D))
Data Field
CRC Sequence
CRC Delimiter
ACK Slot
ACK Delimiter
End of Frame
Intermission
Bus idle
Data Length Code
recessive
NODE B
æ UTS0343E
æ UTS0341E
dominant
NODE B loses the arbitration
switches to receive Arbitration Control CRC Acknowledge
mode Field Field Field Field
Electronic Control Units (ECUs) Software Development 39
S
1-2 H
0
tions for shifting-point control and pressure 0 30 km/h
control have already been discussed in the Vehicle speed υF
chapter sections entitled Shifting-Sequence
Control and Adaptive Pressure Control.
The following text will now deal with 22 1-2 curve with several driving programs
2-1 RS XS
2-1 RS XE
S XS
S XE
0
0 50 km/h
Vehicle speed υF Fig. 21 and 22
1 Upshift
Another Random Document on
Scribd Without Any Related Topics
CAPITULO XXIII
Avô.
Pae.
Filho.
Irmão.
Tio.
Sobrinho.
Primo.
Para as mulheres.
Avó.
Mãe.
Filha.
Irman.
Tia.
Sobrinha.
Prima.
Em sua linguagem.
Ariy ou Ché-Ariy.
Ai ou Chéai.
Tagyre ou Chéagyre.
Theindeure ou Chéreindeure.
Yaché ou Chéaché.
Reindure ou Chéreindure.
Yetipere ou Ché-yetipere.
Alem d’estas consaguinidades existem mais duas por contractos
de alliança; uma quando se dá sua filha á um individuo, ou quando
se recebe uma moça para casar-se com seu filho, e outra quando,
por contracto d’alliança com os francezes, lhes dam suas filhas para
concubinas.
Aos que dam suas filhas chamam taiuuen «genro», ou
Chéraiuuen, «meo genro».
Á mulher de seo filho chamam Tautateu, «nóra», ou Cherautateu,
«minha nora».
Chamam os Francezes seos alliados por hospitalidade Tuasap,
«compadre» ou ché-tuasap, «meo compadre» e as vezes Chéaire,
«meo filho,» ou Cheraiuuen, «meu genro,» quando sua filha é
concubina do Francez.
É este o ramo d’alliança.
Genro.
Nóra.
Compadre.
Em sua linguagem é
Taiuuen, ou Ché-raiuuen.
Tautateu ou Cherautateu.
Tuassap ou Chetuassap, ou então Ché-aire.
Logo que respondem e dizem d’onde vem e para onde vão, podeis
ficar certo que se trata de uma das coisas seguintes, constante
emprego de sua vida e exercicio, isto é, da pescaria no mar, da
entrada nos bosques, da derrubada das arvores, da visita de suas
roças, da plantação de raizes, da colheita dos fructos, e dos nabos,
da caçada, dos passeios por varios lugares, da visita das aldeias e
das habitações de uns e outros.
São estas as respostas d’elles.
Elle responde:
Respondem elles:
ebookball.com