Embedded Systems in Real Time Applicatio
Embedded Systems in Real Time Applicatio
A.L.SUSEELA (III-IT)
V.LALITH KUMAR (III-EEE)
S.T.I.E.T, GARIVIDI, VZM DT.
Motivation
Introduction
Embedded syst ems and Real Time Operating system s (RTOS) are two
among the several technol ogies that will play a major role in making these
concepts possible. A large number of people are already depending on
operating syst ems for real time applications, these 'eyes in the sky' are
now going to make an impact on our every day lives in a more significant
manner. What kind of help wil l these 'embedded syst ems' render unto
humankind in the future? Even Nostradam us would have been hard
pressed to answer thi s question. Embedded syst ems ar e pre-designed
without connections and operate as per the required task. But in operating
syst ems instructi on is design-ori ented. These syst ems are basicall y
platform-less system s. Embedded system s are the unsung heroes of much
of the technology we use today -- the video game we play, or the CD
player or the washing machines we use em ploy them. Without an
embedded system we would not even be able to go online using modem.
Design O rientation
Embedded system s are usually low cost and are easily available off
the shelf for most applications. They usually have low design risks, since
it is easy to verify the design usi ng tool s fueling the growth of embedded
syst ems.
Embedded system s have received a major shot in the arm as the result
of three development s:
During operation, the design struct ure may be changed as per our tasks.
For example, consider two transi stors; we can mould them using other
passive el ement s as emitter coupled circui t, Darlington pair, etc., as per
instruction.
Automobil es :
Almost every car that roll s off the production line these days makes
use of embedded technology in one form or the other; most of the
embedded system s in automobiles are rugged in nature, as most of these
syst ems are made up of a single chip. No driver clashes or 'system s busy '
conditions happen in these syst ems. Their compact profil es enable them to
fit easily under the cramped hood of a car . These system s can be used to
implement features ranging from adjustment of the suspension to suit road
conditions and the octane content in the fuel to antilock braking systems
(ABS) and security system s.
GPS WINDOWS
AIR BAG DEEBOSTER
FUEL
INJECTION
Embedded syst ems can also make drive-l ess vehicle control a reality.
Major autom obile manufactur ers are already engaged in work on these
concepts. One such technology is Adaptive Cruise control (ACC) from
Ford. ACC allows car s to keep safe di stances from other vehi cles on busy
highways. The driver can set the speed of his car and the dist ance between
his car and others. He can over side the system anyt ime he wants by
braking. Each car with ACC has a microwave radar unit or laser
transceiver s fixed in front of it to determine the dist ance and relative
speed of any vehicl e in its pat h. The ACC computer constantl y control s
the throttle and brakes of the car.
Another revolution is the way Internet servi ces will be
integrated into the car. So when you drive past your mechanic's, you will
be reminded that that your engine oil needs a refill, and when you cross
the city limits, the toll will automati cally get deduct ed from your bank
accou nt. And while passing the shopping mail, your PDA, which is
connected to the Net via the car, will inform you about a new scale. In
fact, the automati c to;l deduction concept is already in effect in several
countries around the gl obe.
The upper control generates a desired host vehicle accel eration, which is
sent to the lower-level controller. The lower-level controll er convert s thi s
desired acceleration to a desir ed torque, then chooses whether to apply the
brakes or throttle, and in what amount. Both controllers are run on
separ ate control computer s.
1) Throttle control
From the desired torque, the desired thrott le angle i s computed using an
engine map.
2) Brake control
From the desired torque, two different brake control strategies have been
implement ed. In the first strategy, the master cylinder pressur e is
controlled. A pressur e regulator val ve controls the pressur e applied on th e
hydraulic actuator. Seal friction exist s in the mast er cylinder and the
actuator, and a small amount of hyster esi s is present in the pressure
regulation valve. The friction is modeled as hyperbolas from various
points in the hyster esi s loop and can be written as
Pmc = g (u)
Feed-forward plus proportional feedback control is used, as developed.
The control law can be written as:
Where ub is the applied command input to the brake sol enoid val ve,
Pmc_des the desired master cylinder pressure, Pmc the measur ed master
cylinder pressure, and kb>0 a feedback gain. In the second brake control
strateg y, the wheel brake pressure i s contr olled, and the brake system is
modeled. The control law uses dynamic surface control and can be written
as:
Where Pw_des i s the desired wheel pressure, V is the volume of displ aced
brake fluid, Pw the pressure at the wheel, Cq a flow coeffici ent,
Cruise Control Law:
The purpose of crui se control i s to maintain a desired velocity. A vehi cle
may be in cruise control mode if it is not equipped with ACC or CACC,
has no vehicle immediately in front of it or has at least 100 meter s of
clearance to the preceding vehicl e, or by deci sion of the human driver.
The controller uses a feedback and feed-f orward control law of the form:
Typical values for headway time range form 1.8 seconds to 0.7 seconds.
The control law was designed using sliding control, where a surface is
usuall y defined as a function of the error, derivatives of the error and/or
integral s of the error. The surface is defined such that the st ate will
exponentially decay al ong the surface to t he desir ed point. The input is
chosen to guarant ee that the stat e will converge and stay on the sliding
surface. Error e is defined as:
e = R – Rd, where R=x1-x2.
The sliding surface control is derived in two different ways, which
basi cally lead to the same control law.
Feedback linearization:
Once again, the first two term s in the cont rol law are feed forward, and
the last two ar e feedback. Both control laws are in essence equival ent.
Software Development Process
A model-based approach is used throughout the control softwar e
developm ent. Switching conditions from one mode to the next (for
example ACC int o CACC) were designed by hand. The chosen
architecture can then be sim ulated, and C or C++ code can be generat ed
for each task independentl y. This allows maintaining a single model
containi ng all of control and software information. The code that i s
generat ed for the controller' s interfaces with legacy code, such as device
drivers, driver displ ay unit s etc, through t he use of a shared-mem ory
database on the "publi sh-and-subscri be" model. On the experim ental test
vehicles, all of the software is run on Pent ium computer s running the
QNX4.25 real-tim e operating system.
Experimental Platform:
They are equipped with throttle, brake and steering actuati ng system s, as
well as wit h numerous sensor s, including accel eromet ers, wheel speed
sen sors, engi ne speed and manifold pressure sensors, as well as
magnetom eter s that are used as part of the lateral control. In addition,
both radars and the Lidar described above were mounted to the front
bumper of the vehicl es. There are two control computers located in the
trunk. Both run the QNX 4.25 operat ing system and communi cate over
serial port connecti ons. The computers run a host of tasks necessary for
automat ed control of the vehi cles, includi ng reading sensor data and
writing to actuat ors, control com putations such as those described above
for the ACC/ CACC system and low-level controller s, and tasks pert aining
to driver display inform ation. There are about 30 different tasks running
on the most heavily loaded of the control computer s, and timing is fairly
critical as human test driver s are in the cars during runs and their safet y is
paramount.
Other Applications
Wired Wearables
A mobile phone in the form of a ring or earring? What about cool
sungl asses, with streaming video di spl ays built into them? All these can
soon be a reality. Embedded syst ems have a small footprint and consum e
very little power, which makes them ideal for wearable comput ing
applications. The minimal system requirements of the devices ensure that
the hardwar e is almost microscopi c.
IBM is already working on the prototype of a mobile phone that can be
worn as jewelry. The components of the phone will be di stributed among
different pieces of jewelry -- earring, necklace, ring and bracelet.
The phone is likely to have blue tooth capabil ity built into it. The
earring will have embedded speakers and will act as the recei ver. The
necklace will have embedded mi crophones that will act as mouthpiece
user s can talk int o. IBM call s the ring par t of the phone the 'decoder ring'.
Light emitting diodes (LED's) will flash to indicate an incoming call. The
ring will also have features that will enabl e it to be programmed to flash
different colour s for a particular user or to indicate the importance of a
call. A video graphi cs array (VGA) will be built into the bracelet, which
will displ ay the name and plans to incorporate voice recognition
technology for dialing a number. The phone may also have features to
indicat e new E-mail.
Pacemakers
Imagine a time when body transpl ants like cardiac pacemakers will be
able to monitor & manage them selves rem otely. These syst ems wi ll be so
compact that the pati ent wouldn't even be aware that they are embedded in
his body, and developm ents are pointing t owards the use of pacemakers
that can be transpl anted in or near the heart itself. The pacemaker will be
able to monitor param eter like blood pleasure blood flow, pressure rate
temperatur e, etc., using microsensors placed in various parts of the body.
The capabilit y will enable the pacemaker to automatically vary it s
operation to suit the changing body condit ions. It will also transmit dat a
using micro sensors pl anted in various par ts of the body. This capability
will enabl e the pacemaker to automati call y vary its operati on to suit the
changing body condi tions. It will also transmit data using wir eless
transmi ssi on.
Embedded technology ad vances l ess transmi ssion is likely to be done
by a transmitt er implanted near the surface of the skin. In case in an
abnormality i s detected. The doctor will be able to take rem edial action
even from remote locations.
A variety of operating system s are available for use wit h embedded
computer s. Many of them ar e not true real-time operating syst ems
(RTOS), as they do not support the preci se scheduling of tasks and
predictable react ions tim es of real-tim e events. A true RTOS must suspect
prioritized, pre-emptive scheduling.
Embedded computer s perform their jobs by executing software
instructions. Unlike desktop computers, the user has little or no
information on what i s happening -- code is executed automati cally in
respon se to 'real time' events. For exampl e, when an intruder opens a door
connected to a security syst em, the microprocessor turns on an alarm s,
dials the number of the security company, and transmit s an alarm signal.
Smarter system s analyze dat a about the intrusion and turn on only if the
intruder has hum an attribut es. Other than setting the alarm and checki ng
for messages, the user of the alarm has no control over the software being
execut ed.
Conclusi on
This paper presents the use of a model -base approach to the
developm ent of real-time, embedded, hybr id control software. The
concepts are illustrat ed with a scenario involving speed profile tracking
and vehicl e following applications for usi ng the cruise controller. Robotic
technologies such as range, velocity and acceler ation measurement s, and
their processing and fusion were used as part of the syst em. In addition,
vehicles can present very nonlinear behavior, especi ally at low speeds,
and their control present s a formidabl e challenge. The problem domain of
intelligent cruise control appli cations has been described in detail, along
with control and software development methodologies. All these
application areas are just tiny drops in the big ocean of embedded syst ems
technology. These proverbial Davids ar e all set to conquer a world that is
forbidden territory for the popular desktop OS Goliaths -- so hold your
breath and wait for the fireworks to com e. They are sure to blow our
mind.
REFERENCES:
[1] Personal communication, Ken Henry, GM Research.
[2] http://www.wikipedi a.org/wiki/Embedded_syst em, from Wikipedia,
the free Encyclopedia
[4] D. Cho and J.K. Hedrick, "Automotive Engine Modeling for Control", ASME
Journal of Dynamic Systems, Measurement and Control, December 1989, Vol. 111, pp.
568-576.
[5] Girard, A.R., Spry, S.C., Kretz, P.R. Dickey, S.R., Empey, D.M.,
Misener, J.A., Variaya, P.P. and Hedrick, J.K., "Vehicl e-to-Vehi cle Open
Experimental Platform Reference Manual. "
[6] www.teja.com