Fieldbuses and interoperability
Identifieur interne : 00A846 ( Main/Curation ); précédent : 00A845; suivant : 00A847Fieldbuses and interoperability
Auteurs : Jean-Pierre Thomesse [France]Source :
- Control Engineering Practice [ 0967-0661 ] ; 1999.
English descriptors
- Teeft :
- Actuator, Application architectures, Application development, Application entities, Application interoperability, Application layer, Application process, Application programs, Automation architectures, Automation system, Automation systems, Benkhellat, Building automation, Canonical tester, Cenelec, Communication system, Communication systems, Companion standards, Complete application, Comput, Computer control systems, Conformance, Conformance classes, Conformance testing, Conformance testing methods, Constraint, Controller area network, Data item, Data link layer, Data link service, Data rate, Design stage, Digital data communications, Dynamic behaviour, Dynamic scheduling, Eldbus, Eldbus networks, Eldbus services, Eldbus solution, Eldbuses, Elsevier science, Engineering practice, Factory communication systems, Factory instrumentation protocol, Fieldbus, Fieldbus foundation, Function blocks, Functional architecture, German draft, Gestion technique, Global system, Heterogeneous devices, High communications subsystems, Ieee, Industrial automation, Industrial control systems, International level, Interoperability, Interoperability guidelines, Interoperability testing, Interoperable, Layer, Layer interoperability, Manufacturing message, Master stations, Medium access control, Much work, National standards, Network layer, Network management, Networks isdn systems, Operational architecture, Orkshop, Other hand, Other kinds, Other services, Passive testing, Performance testing, Physical layer, Presentation layer, Protocol, Protocol point, Real time, Real time applications, Real time communications, Real time systems, Realistic models, Response time, Same protocols, Same time, Same view, Semiconductor manufacturing, Sensor, Small data packages, Software, Specialized magazines, Spinal column, Standardization, Standards interfaces, State values, Task force, Temporal aspects, Temporal mechanisms, Thomesse, Time coherence, Time coherences, Time constraints, Time window, Timing constraints, Transport layer, Typical exchanges, User layer, User requirements, Users group, Usual mechanism, Voltage switchgear, Worldfip.
Abstract
Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.
Url:
DOI: 10.1016/S0967-0661(98)00140-3
Links toward previous steps (curation, corpus...)
- to stream Istex, to step Corpus: Pour aller vers cette notice dans l'étape Curation :001D15
- to stream Istex, to step Curation: Pour aller vers cette notice dans l'étape Curation :001C94
- to stream Istex, to step Checkpoint: Pour aller vers cette notice dans l'étape Curation :002231
- to stream Main, to step Merge: Pour aller vers cette notice dans l'étape Curation :00AE98
Links to Exploration step
ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBBLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title>Fieldbuses and interoperability</title>
<author><name sortKey="Pierre Thomesse, Jean" sort="Pierre Thomesse, Jean" uniqKey="Pierre Thomesse J" first="Jean" last="Pierre Thomesse">Jean-Pierre Thomesse</name>
<affiliation><country>France</country>
<placeName><settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="laboratoire" n="5">Laboratoire lorrain de recherche en informatique et ses applications</orgName>
<orgName type="university">Université de Lorraine</orgName>
<orgName type="institution">Centre national de la recherche scientifique</orgName>
<orgName type="institution">Institut national de recherche en informatique et en automatique</orgName>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB</idno>
<date when="1999" year="1999">1999</date>
<idno type="doi">10.1016/S0967-0661(98)00140-3</idno>
<idno type="url">https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/fulltext.pdf</idno>
<idno type="wicri:Area/Istex/Corpus">001D15</idno>
<idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Corpus" wicri:corpus="ISTEX">001D15</idno>
<idno type="wicri:Area/Istex/Curation">001C94</idno>
<idno type="wicri:Area/Istex/Checkpoint">002231</idno>
<idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Checkpoint">002231</idno>
<idno type="wicri:doubleKey">0967-0661:1999:Pierre Thomesse J:fieldbuses:and:interoperability</idno>
<idno type="wicri:Area/Main/Merge">00AE98</idno>
<idno type="wicri:Area/Main/Curation">00A846</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title level="a">Fieldbuses and interoperability</title>
<author><name sortKey="Pierre Thomesse, Jean" sort="Pierre Thomesse, Jean" uniqKey="Pierre Thomesse J" first="Jean" last="Pierre Thomesse">Jean-Pierre Thomesse</name>
<affiliation wicri:level="3"><country xml:lang="fr">France</country>
<wicri:regionArea>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre</wicri:regionArea>
<placeName><region type="region" nuts="2">Grand Est</region>
<region type="old region" nuts="2">Lorraine (région)</region>
<settlement type="city">Vandœuvre</settlement>
</placeName>
<placeName><settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="laboratoire" n="5">Laboratoire lorrain de recherche en informatique et ses applications</orgName>
<orgName type="university">Université de Lorraine</orgName>
<orgName type="institution">Centre national de la recherche scientifique</orgName>
<orgName type="institution">Institut national de recherche en informatique et en automatique</orgName>
</affiliation>
<affiliation wicri:level="1"><country wicri:rule="url">France</country>
<placeName><settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="laboratoire" n="5">Laboratoire lorrain de recherche en informatique et ses applications</orgName>
<orgName type="university">Université de Lorraine</orgName>
<orgName type="institution">Centre national de la recherche scientifique</orgName>
<orgName type="institution">Institut national de recherche en informatique et en automatique</orgName>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series><title level="j">Control Engineering Practice</title>
<title level="j" type="abbrev">CONPRA</title>
<idno type="ISSN">0967-0661</idno>
<imprint><publisher>ELSEVIER</publisher>
<date type="published" when="1999">1999</date>
<biblScope unit="volume">7</biblScope>
<biblScope unit="issue">1</biblScope>
<biblScope unit="page" from="81">81</biblScope>
<biblScope unit="page" to="94">94</biblScope>
</imprint>
<idno type="ISSN">0967-0661</idno>
</series>
</biblStruct>
</sourceDesc>
<seriesStmt><idno type="ISSN">0967-0661</idno>
</seriesStmt>
</fileDesc>
<profileDesc><textClass><keywords scheme="Teeft" xml:lang="en"><term>Actuator</term>
<term>Application architectures</term>
<term>Application development</term>
<term>Application entities</term>
<term>Application interoperability</term>
<term>Application layer</term>
<term>Application process</term>
<term>Application programs</term>
<term>Automation architectures</term>
<term>Automation system</term>
<term>Automation systems</term>
<term>Benkhellat</term>
<term>Building automation</term>
<term>Canonical tester</term>
<term>Cenelec</term>
<term>Communication system</term>
<term>Communication systems</term>
<term>Companion standards</term>
<term>Complete application</term>
<term>Comput</term>
<term>Computer control systems</term>
<term>Conformance</term>
<term>Conformance classes</term>
<term>Conformance testing</term>
<term>Conformance testing methods</term>
<term>Constraint</term>
<term>Controller area network</term>
<term>Data item</term>
<term>Data link layer</term>
<term>Data link service</term>
<term>Data rate</term>
<term>Design stage</term>
<term>Digital data communications</term>
<term>Dynamic behaviour</term>
<term>Dynamic scheduling</term>
<term>Eldbus</term>
<term>Eldbus networks</term>
<term>Eldbus services</term>
<term>Eldbus solution</term>
<term>Eldbuses</term>
<term>Elsevier science</term>
<term>Engineering practice</term>
<term>Factory communication systems</term>
<term>Factory instrumentation protocol</term>
<term>Fieldbus</term>
<term>Fieldbus foundation</term>
<term>Function blocks</term>
<term>Functional architecture</term>
<term>German draft</term>
<term>Gestion technique</term>
<term>Global system</term>
<term>Heterogeneous devices</term>
<term>High communications subsystems</term>
<term>Ieee</term>
<term>Industrial automation</term>
<term>Industrial control systems</term>
<term>International level</term>
<term>Interoperability</term>
<term>Interoperability guidelines</term>
<term>Interoperability testing</term>
<term>Interoperable</term>
<term>Layer</term>
<term>Layer interoperability</term>
<term>Manufacturing message</term>
<term>Master stations</term>
<term>Medium access control</term>
<term>Much work</term>
<term>National standards</term>
<term>Network layer</term>
<term>Network management</term>
<term>Networks isdn systems</term>
<term>Operational architecture</term>
<term>Orkshop</term>
<term>Other hand</term>
<term>Other kinds</term>
<term>Other services</term>
<term>Passive testing</term>
<term>Performance testing</term>
<term>Physical layer</term>
<term>Presentation layer</term>
<term>Protocol</term>
<term>Protocol point</term>
<term>Real time</term>
<term>Real time applications</term>
<term>Real time communications</term>
<term>Real time systems</term>
<term>Realistic models</term>
<term>Response time</term>
<term>Same protocols</term>
<term>Same time</term>
<term>Same view</term>
<term>Semiconductor manufacturing</term>
<term>Sensor</term>
<term>Small data packages</term>
<term>Software</term>
<term>Specialized magazines</term>
<term>Spinal column</term>
<term>Standardization</term>
<term>Standards interfaces</term>
<term>State values</term>
<term>Task force</term>
<term>Temporal aspects</term>
<term>Temporal mechanisms</term>
<term>Thomesse</term>
<term>Time coherence</term>
<term>Time coherences</term>
<term>Time constraints</term>
<term>Time window</term>
<term>Timing constraints</term>
<term>Transport layer</term>
<term>Typical exchanges</term>
<term>User layer</term>
<term>User requirements</term>
<term>Users group</term>
<term>Usual mechanism</term>
<term>Voltage switchgear</term>
<term>Worldfip</term>
</keywords>
</textClass>
<langUsage><language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en">Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</div>
</front>
</TEI>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Main/Curation
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 00A846 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Main/Curation/biblio.hfd -nk 00A846 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Wicri/Lorraine |area= InforLorV4 |flux= Main |étape= Curation |type= RBID |clé= ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB |texte= Fieldbuses and interoperability }}
![]() | This area was generated with Dilib version V0.6.33. | ![]() |