Image Processing Reference
In-Depth Information
Oriented System Transport (MOST) [] and IDB- [] for multimedia applications belong the
this class.
The cooperative development process of networked embedded automotive applications brings
with itself heterogeneity of software and hardware components. Even with the inevitable stan-
dardization of those components, interfaces, and even complete system architectures, the support
for reuse of hardware and software components is limited, thus potentially making the design
of networked embedded automotive applications labor intensive, error-prone, and expensive. This
situation spurned a number of standardization initiatives aimed at the development of component-
based design integration methodologies of which OSEK/VDX [] and AUTomotive Open System
ARchitecture (AUTOSAR) [] are the most notable (both discussed in detail in this topic).
1.3 Networks Embedded Systems in Industrial Automation
Although for the origins of field area networks, one can look back as far as the end of s in the
nuclear instrumentation domain, CAMAC network [], and the beginning of s in avionics and
aerospace applications, MIL-STD- bus [], it was the industrial automation area which brought
the main thrust of developments. he need for integration of heterogeneous systems, difficult at the
time due to the lack of standards, resulted in two major initiatives that have had a lasting impact on
the integration concepts, and architecture of the protocol stack of field area networks. These ini-
tiatives were Technical and Office Protocol (TOP) [] and Manufacturing Automation Protocol
(MAP) [] projects. he two projects exposed some pitfalls of the full seven-layer stack implemen-
tations (ISO/OSI model []). As a result, typically, only the layers  (physical layer),  (data link layer,
including implicitly the medium access control layer), and  (application layer, which covers also user
layer) are used in the field area networks []; also prescribed by the international fieldbus standard,
IEC  []. In IEC , functions of layer  and  are recommended to be placed either in layer
 or layer —network and transport layers are not required in a single segment network typical of
process and industrial automation (situation is different though in building automation, for instance,
where the routing functionality and end-to-end control may be needed arising from a hierarchical
network structure); functions of layers  and  are always covered in layer .
The evolution of fieldbus technology which begun well over two decades ago has resulted in a
multitude of solutions reflecting the competing commercial interests of their developers and stan-
dardization bodies, both national and international: IEC [], ISO [], ISA [], CENELEC [],
and CEN []. [].This is also reflected in IEC  (adopted in ), which accommodates all national
standards and user organization championed fieldbus systems. Subsequently, implementation guide-
lines were compiled in to Communication Profiles, IEC - []. [].Those Communication Profiles
identify seven main systems (or Communication Profile Families) known by brand names as Foun-
dation Fieldbus (H, HSE, H) used in process and factory automation; ControlNet and EtherNet/IP
both used in factory automation; PROFIBUS (DP, PA) used in factory and process automation,
respectively;PROFINETusedinfactoryautomation;P-Net(RS,RS)usedinfactoryautoma-
tion and shipbuilding; WorldFIP used in factory automation; INTERBUS, INTERBUS TCP/IP, and
INTERBUS Subset used in factory automation; Swiftnet “transport,” Swiftnet “full stack” used by
aircrat manufacturers. he listed application areas are the dominant ones.
Ethernet, the backbone technology for office networks, is increasingly being adopted for commu-
nication in factories and plants at the fieldbus level. The random and native CSMA/CD arbitration
mechanism is being replaced by other solutions allowing for deterministic behavior required in
real-timecommunicationtosupportsotandhardreal-timedeadlines,timesynchronizationofactiv-
ities required to control drives, for instance, and for exchange of small data records characteristic
of monitoring and control actions. The emerging Real-Time Ethernet (RTE), Ethernet augmented
 
Search WWH ::




Custom Search