🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN 62453-301:2009:2010 Edition

BS EN 62453-301:2009:2010 Edition

$256.21

Field device tool (FDT) interface specification – Communication profile integration. IEC 61784 CPF 1

Published By Publication Date Number of Pages
BSI 2010 132
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

IEC 62453-301:2009 provides information for integrating the FOUNDATION Fieldbus (FF) protocol into the FDT standard (IEC 62453-2). It describes communication definitions, protocol specific extensions and the means for block (e.g. transducer, resource or function blocks) representation. This part, in conjunction with the other parts of the first edition of the IEC 62453 series cancels and replaces IEC/PAS 62453-1, IEC/PAS 62453-2, IEC/PAS 62453-3, IEC/PAS 62453-4 and IEC/PAS 62453-5 published in 2006, and constitutes a technical revision. This bilingual version (2013-07) corresponds to the monolingual English version, published in 2009-06. This publication is to be read in conjunction with /2.

PDF Catalog

PDF Pages PDF Title
6 CONTENTS
9 INTRODUCTION
Figures
Figure 1 – Part 301 of the IEC 62453 series
10 1 Scope
2 Normative references
11 3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
3.2 Abbreviated terms
3.3 Conventions
12 4 Fundamentals
4.1 System and FDT topology
4.2 FDT topology for H1 devices
Figure 2 – Object relations for H1 Device DTM
13 4.3 FDT topology for HSE devices
Tables
Table 1 – Object relations for H1 Device DTM
14 Figure 3 – Object relations for HSE application with DTMs and BTMs
15 4.4 Nested communication
Table 2 – Object relations for HSE application wtith DTMs and BTMs
16 5 Bus category
6 Access to instance and device data
6.1 DTM
6.2 BTM
Table 3 – FF specific protocol identifiers
17 7 Protocol specific behavior
7.1 Connection management
Figure 4 – FMS mapping in the FDT connection
18 7.2 Abort
Figure 5 – FDT Disconnect service
19 7.3 Relation of FMS requests and FMS responses
Table 4 – Relation of FMS requests and FMS responses
20 7.4 Subscription mechanism
22 8 Protocol specific usage of general data types
8.1 Address
8.2 protocolID
8.3 applicationDomain
23 8.4 semanticId
24 9 Protocol specific data types
9.1 DTM
25 Table 5 – Action object definitions (refer to FF-890):
Table 6 – Link object definitions
26 Table 7 – Alert object definitions
28 Table 8 – Trend object definitions
29 Table 9 – View definition
Table 10 – Domain object definitions
30 Table 11 – Program invocation object definitions
31 9.2 BTM
Table 12 – Structured FF device data types
32 Table 13 – Parameter mnemonic
40 Table 14 – Mnemonic of structured data types
44 Table 15 – Simple common data types
45 10 Network management data types
10.1 General
10.2 H1 network management definitions
10.3 HSE network management data types
Table 16 – H1 Fieldbus Management data types
Table 17 – Simple HSE Fieldbus Management Definitions
51 Table 18 – Structured HSE Network management data types
87 11 Communication data types
11.1 Common data types
Table 19 – Simple common data types
89 Table 20 – Structured common data types
92 11.2 FF FMS data types
Table 21 – Simple FF FMS data types
93 Table 22 – Structured FF FMS data types
98 11.3 H1 communication data types
99 Table 23 – Simple H1 communication data types
100 Table 24 – Structured H1 communication data types
105 11.4 HSE communication data types
Table 25 – Simple HSE communication data types
106 Table 26 – Structured HSE communication data types
112 11.5 FDT FF standard block communication data types
113 Table 27 – Block communication data types
114 12 Channel parameter data types
Table 28 – Simple FF channel data types
115 Table 29 – Structured FF channel data types
116 13 Device identification
13.1 Protocol specific handling of data type STRING
117 13.2 Common device type identification data types
Table 30 – FieldbusFoundation H1 table
119 Table 31 – FieldbusFoundation HSE
121 Table 32 – FieldbusFoundation blocks
123 13.3 Scan identification data types
13.4 Device type identification data types – provided by DTM
Table 33 – Simple Fieldbus Scan definitions
124 Table 34 – Device identification data types
125 Annex A (informative) Implementation hints
127 Annex B (normative) Levels of support
128 Table B.1 – Levels of support
130 Bibliography

Related products

BS EN 62453-301:2009
$256.21