{"id":244024,"date":"2024-10-19T16:01:26","date_gmt":"2024-10-19T16:01:26","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-5-32012\/"},"modified":"2024-10-25T10:59:36","modified_gmt":"2024-10-25T10:59:36","slug":"bs-en-61158-5-32012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-5-32012\/","title":{"rendered":"BS EN 61158-5-3:2012"},"content":{"rendered":"
1.1<\/b> General<\/p>\n
This standard is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the \u201cthree-layer\u201d fieldbus reference model described in IEC\/TR 61158-1.<\/p>\n
This sub-part contains material specific to Type 3 fieldbus.<\/p>\n
1.2<\/b> Overview<\/p>\n
The fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a \u201cwindow between corresponding application programs.\u201d<\/p>\n
This standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 3 fieldbus. The term \u201ctime-critical\u201d is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.<\/p>\n
This standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of<\/p>\n
an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,<\/p>\n<\/li>\n
the primitive actions and events of the service;<\/p>\n<\/li>\n
the parameters associated with each primitive action and event, and the form which they take; and<\/p>\n<\/li>\n
the interrelationship between these actions and events, and their valid sequences.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this standard is to define the services provided to<\/p>\n
the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and<\/p>\n<\/li>\n
Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.<\/p>\n<\/li>\n<\/ol>\n
This standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO\/IEC 7498-1) and the OSI Application Layer Structure (ISO\/IEC 9545).<\/p>\n
FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.<\/p>\n
Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send\/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation.<\/p>\n
1.3<\/b> Specifications<\/p>\n
The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for time-critical communications.<\/p>\n
A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6.<\/p>\n
This specification may be used as the basis for formal Application Programming-Interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this specification, including<\/p>\n
the sizes and octet ordering of various multi-octet service parameters, and<\/p>\n<\/li>\n
the correlation of paired request and confirm, or indication and response, primitives.<\/p>\n<\/li>\n<\/ol>\n
1.4<\/b> Conformance<\/p>\n
This standard do not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems.<\/p>\n
There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfill any given Type of application layer services as defined in this part of IEC 61158.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 1 Scope 1.1 General 1.2 Overview <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 1.3 Specifications 1.4 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Referenced terms and definitions <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 3.2 Fieldbus Application Layer type 3 \u2013 specific terms and definitions <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.3 Abbreviations and symbols 3.4 Conventions <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 4 Concepts 5 Data type ASE 6 Communication model specification 6.1 DP concepts <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Tables Table 1 \u2013 Requirements and features of fieldbus\u00a0DP <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figures Figure 1 \u2013 Example of DP communication with a single controlling device Figure 2 \u2013 Example of DP communication with several controlling devices <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 3 \u2013 Example of DP communication between field devices <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 4 \u2013 DP-slave model (modular DP-slave) <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure 5 \u2013 DP-slave model (compact DP-slave) <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Figure 6 \u2013 Overview of application processes <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 7 \u2013 DP-slave model (modular DP-slave) <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 8 \u2013 Application Service Elements (ASEs) <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 10 \u2013 Access to a remote APO <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 11 \u2013 Access to a remote APO for publisher\/subscriber association <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 12 \u2013 Example of one AR with two AREPs <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table 2 \u2013 Status values of the service primitives <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 6.2 ASEs <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Figure 13 \u2013 Relation of a simple process data object to the real object <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 3 \u2013 Access Rights MS1 Table 4 \u2013 Access Rights MS2 <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure 14 \u2013 Relation of a combined process data object to the real objects <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table 5 \u2013 Access Rights MS1 Table 6 \u2013 Access Rights MS2 <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 7 \u2013 SCL matching rules Table 8 \u2013 Read <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 9 \u2013 Write <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 10 \u2013 Data transport <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 11 \u2013 Format (simple input data description) Table 12 \u2013 Consistency (simple input data description) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 13 \u2013 Format (simple output data) Table 14 \u2013 Consistency (simple output data) <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 15 \u2013 Format (extended input data) <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 16 \u2013 Consistency (extended input data) <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 17 \u2013 Format (extended output data) <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 18 \u2013 Consistency (extended output data) <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 19 \u2013 Set Input Table 20 \u2013 Read Input <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 21 \u2013 Get Input <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 22 \u2013 New Input <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 23 \u2013 Set Output <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 24 \u2013 Final Table 25 \u2013 Read Output <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 26 \u2013 Get Output Table 27 \u2013 Clear Flag <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 28 \u2013 New Flag Table 29 \u2013 New Output Table 30 \u2013 Clear Flag <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 31 \u2013 Global Control Table 32 \u2013 Clear Command Table 33 \u2013 Sync Command <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 34 \u2013 Freeze Command Table 35 \u2013 New publisher data <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 36 \u2013 Get publisher data Table 37 \u2013 New Flag <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 38 \u2013 SYNCH Table 39 \u2013 SYNCH Delayed <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 40 \u2013 DX Finished Table 41 \u2013 SYNCH Event Table 42 \u2013 Status <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 15 \u2013 Sequence of an isochronous DP cycle with one DP-master (class 1) <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 16 \u2013 Additional time relationships in a DP system operating in isochronous mode <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure 17 \u2013 DP system with optimized isochronous DP cycle <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 18 \u2013 Buffered synchronized isochronous mode at the DP-master (class 1) <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure 19 \u2013 Enhanced synchronized isochronous mode at the DP-master (class 1) Figure 20 \u2013 Input, output and PLL state machine interaction <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table 43 \u2013 Primitives issued by the AL to the PLL state machine Table 44 \u2013 Primitives issued by the user to the PLL state machine Table 45 \u2013 Allowed values of Status <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 46 \u2013 Primitives issued by the user to the input state machine Table 47 \u2013 Primitives issued by the user to the output state machine Table 48 \u2013 Primitives issued by the PLL to the output state machine Table 49 \u2013 Primitives issued by the output to the PLL state machine Table 50 \u2013 Primitives issued by the PLL to the input state machine <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 51 \u2013 Primitives issued by the output to the input state machine Table 52 \u2013 Primitives issued by the output state machine to the AL Table 53 \u2013 Primitives issued by the AL to the output state machine Table 54 \u2013 Primitives issued by the input state machine to the AL Table 55 \u2013 Primitives issued by the AL to the input state machine <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 21 \u2013 PLL state diagram <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 56 \u2013 PLL state table <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Figure 22 \u2013 OUTPUT state diagram <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 57 \u2013 OUTPUT state table <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Figure 23 \u2013 INPUT state diagram <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 58 \u2013 INPUT state table <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table 59 \u2013 Identifier status <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table 60 \u2013 Channel type <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table 61 \u2013 IO type Table 62 \u2013 Status type <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table 63 \u2013 Status specifier <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Table 64 \u2013 Status specifier Table 65 \u2013 Module status <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table 66 \u2013 Status specifier Table 67 \u2013 Link status <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 68 \u2013 Link error <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 69 \u2013 Set Slave Diag <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Table 70 \u2013 Ext Diag Flag <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 71 \u2013 Get Slave Diag <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table 72 \u2013 Read Slave Diag <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table 73 \u2013 New Slave Diag <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Figure 24 \u2013 Treatment of an alarm in the DP system <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Table 74 \u2013 Alarm type <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Table 75 \u2013 Add Ack Table 76 \u2013 Alarm specifier <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table 77 \u2013 Alarm notification <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Table 78 \u2013 Alarm Ack <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Table 79 \u2013 Prm data type <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Table 80 \u2013 Supported feature Table 81 \u2013 Supported profile feature <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table 82 \u2013 Role <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Table 83 \u2013 Check user\u00a0Prm <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Table 84 \u2013 Prm structure <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Table 85 \u2013 MS1 Command <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Table 86 \u2013 Check\u00a0user\u00a0Prm\u00a0result <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Table 87 \u2013 Status values <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Table 88 \u2013 Check Ext user\u00a0Prm <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Table 89 \u2013 Check\u00a0Ext user\u00a0Prm\u00a0result <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Table 90 \u2013 Status values Table 91 \u2013 Check\u00a0Cfg <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table 92 \u2013 Check\u00a0Cfg\u00a0result <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Table 93 \u2013 Status values Table 94 \u2013 Set\u00a0Cfg <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table 95 \u2013 Get Cfg <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Table 96 \u2013 Set\u00a0Slave\u00a0Add <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Table 97 \u2013 Initiate <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table 98 \u2013 Abort Table 99 \u2013 Instance <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table 100 \u2013 MS0 init DP-slave Table 101 \u2013 MS1 init DP-slave <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table 102 \u2013 MS2 init DP-slave Table 103 \u2013 DP-slave started <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Table 104 \u2013 Alarm limit Table 105 \u2013 DP-slave stopped <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Table 106 \u2013 Reset DP-slave Table 107 \u2013 DP-slave fault Table 108 \u2013 Application ready DP-slave <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Table 109 \u2013 Start subscriber Table 110 \u2013 Stop subscriber <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Table 111 \u2013 Publisher active <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Table 112 \u2013 Status Table 113 \u2013 Init DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Table 114 \u2013 DP-master Cl1 started <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Table 115 \u2013 Alarm limit Table 116 \u2013 DP-master Cl1 stopped Table 117 \u2013 Reset DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Table 118 \u2013 DP-master Cl1 fault Table 119 \u2013 DP-master Cl1 reject <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Table 120 \u2013 Set\u00a0mode DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table 121 \u2013 DP-master Cl1 mode\u00a0changed <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Table 122 \u2013 Load\u00a0bus\u00a0Par DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table 123 \u2013 Mark DP-master Cl1 Table 124 \u2013 Abort DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Table 125 \u2013 Read\u00a0value DP-master Cl1 Table 126 \u2013 Delete\u00a0SC DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Table 127 \u2013 DP-master Cl1 event <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Table 128 \u2013 Init DP-master Cl2 <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Table 129 \u2013 Reset DP-master Cl2 Table 130 \u2013 DP-master Cl2 fault Table 131 \u2013 DP-master Cl2 reject <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Table 132 \u2013 DP-master Cl2 closed Table 133 \u2013 DP-master Cl2 event <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | Table 134 \u2013 USIF state <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | Table 135 \u2013 Data rate <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Table 136 \u2013 USIF state Table 137 \u2013 Isochronous mode <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Table 138 \u2013 Slave type <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Table 139 \u2013 Alarm mode <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Table 140 \u2013 Get\u00a0Master\u00a0Diag Table 141 \u2013 MDiag identifier <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Table 142 \u2013 Start\u00a0Seq <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Table 143 \u2013 Area code (start seq) <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Table 144 \u2013 Download <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Table 145 \u2013 Upload <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | Table 146 \u2013 End\u00a0Seq <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Table 147 \u2013 Act\u00a0Para\u00a0Brct Table 148 \u2013 Area code (Act Para Brct) <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Table 149 \u2013 Act\u00a0param <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Table 150 \u2013 Area code (Act param) Table 151 \u2013 Activate <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | Table 152 \u2013 Access rights MS1 <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Table 153 \u2013 Access rights MS2 Table 154 \u2013 Load region state <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | Table 155 \u2013 Initiate load <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | Table 156 \u2013 Default values for the parameter Intersegment Request Timeout <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Table 157 \u2013 Push segment <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Table 158 \u2013 Pull segment <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Table 159 \u2013 Terminate load <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Table 160 \u2013 Primitives issued by the user to the Load Region state machine <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | Table 161 \u2013 Primitives issued by the Load Region state machine to the user Table 162 \u2013 Primitives issued by the Function Invocation to the Load Region state machine <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | Table 163 \u2013 Primitives issued by the Load Region to the Function Invocation state machine Table 164 \u2013 Load Region state definitions <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Table 165 \u2013 Load Region function table <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Figure 25 \u2013 Load Region state diagram for erasable memory <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | Figure 26 \u2013 Load region state diagram for non erasable memory Table 166 \u2013 Load Region state table for erasable memory <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Table 167 \u2013 Load Region state table for non erasable memory <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Table 168 \u2013 Access rights MS1 Table 169 \u2013 Access rights MS2 <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | Table 170 \u2013 Function Invocation state Table 171 \u2013 Load Region object in use <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Table 172 \u2013 Access rights MS1 <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | Table 173 \u2013 Access rights MS2 Table 174 \u2013 Load Region object in use <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | Table 175 \u2013 Start <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | Table 176 \u2013 Stop <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | Table 177 \u2013 Resume <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | Table 178 \u2013 Reset <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | Table 179 \u2013 Get FI state <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | Table 180 \u2013 Call <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | Table 181 \u2013 Primitives issued by the user to the Function Invocation state machine <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | Table 182 \u2013 Primitives issued by the Function Invocation state machine to the user Table 183 \u2013 Primitives issued by the Load Region to the Function Invocation state machine <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | Table 184 \u2013 Primitives issued by the Function Invocation to the Load Region state machine Table 185 \u2013 Function Invocation state definitions <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | Table 186 \u2013 Function definitions <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | Figure 27 \u2013 Function invocation state diagram Table 187 \u2013 Function Invocation state table <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | Table 188 \u2013 CS status Table 189 \u2013 Summertime <\/td>\n<\/tr>\n | ||||||
289<\/td>\n | Table 190 \u2013 Synchronization active Table 191 \u2013 Announcement hour <\/td>\n<\/tr>\n | ||||||
290<\/td>\n | Table 192 \u2013 Summertime Table 193 \u2013 Accuracy <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | Table 194 \u2013 Set time <\/td>\n<\/tr>\n | ||||||
292<\/td>\n | Table 195 \u2013 Sync interval violation <\/td>\n<\/tr>\n | ||||||
293<\/td>\n | Figure 29 \u2013 Assignment of communication relationship to application relationship <\/td>\n<\/tr>\n | ||||||
299<\/td>\n | Figure 30 \u2013 MS0 application relationship <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Figure 31 \u2013 Output buffer model of a DP-slave without sync functionality Figure 32 \u2013 Output buffer model of a DP-slave with sync functionality <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | Figure 33 \u2013 Input buffer model of a DP-slave without freeze functionality Figure 34 \u2013 Input buffer model of a DP-slave with freeze functionality <\/td>\n<\/tr>\n | ||||||
302<\/td>\n | Figure 35 \u2013 MS1 application relationship Figure 36 \u2013 MS2 application relationship <\/td>\n<\/tr>\n | ||||||
304<\/td>\n | Figure 37 \u2013 Example of inter-network communication Figure 38 \u2013 Example without inter-network addressing <\/td>\n<\/tr>\n | ||||||
305<\/td>\n | Figure 39 \u2013 First example with inter-network addressing Table 196 \u2013 Parameter of Initiate service without inter-network addressing Table 197 \u2013 Parameter of Initiate service with inter-network addressing (first example) <\/td>\n<\/tr>\n | ||||||
306<\/td>\n | Figure 40 \u2013 Second example with inter-network addressing Table 198 \u2013 Parameter of Initiate service with inter-network addressing (second example) <\/td>\n<\/tr>\n | ||||||
307<\/td>\n | Figure 41 \u2013 MS3 application relationship Figure 42 \u2013 MM1 application relationship <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | Figure 43 \u2013 MM2 application relationship <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | Table 199 \u2013 AR type <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | Table 200 \u2013 Sync supported Table 201 \u2013 Freeze supported <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | Table 202 \u2013 Group identifier Table 203 \u2013 DPV1 enabled <\/td>\n<\/tr>\n | ||||||
317<\/td>\n | Table 204 \u2013 Fail\u00a0safe Table 205 \u2013 WD base <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | Table 206 \u2013 No Add change <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | Table 207 \u2013 Alarm mode supported <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | Table 208 \u2013 Isochronous mode supp Table 209 \u2013 Isochronous mode <\/td>\n<\/tr>\n | ||||||
327<\/td>\n | Table 210 \u2013 Alarm mode <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | Table 211 \u2013 Time device type <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | Table 212 \u2013 S_SAP_index <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | Table 213 \u2013 D_addr Table 214 \u2013 Service_activate <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Table 215 \u2013 Role_in_service <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | Table 216 \u2013 Indication_mode Table 217 \u2013 Max_DLSDU_length_req_low <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | Table 218 \u2013 Max_DLSDU_length_req_high Table 219 \u2013 Max_DLSDU_length_ind_low <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | Table 220 \u2013 Max_DLSDU_length_ind_high <\/td>\n<\/tr>\n | ||||||
341<\/td>\n | Table 221 \u2013 S_SAP_index Table 222 \u2013 D_SAP_index <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | Table 223 \u2013 D_addr Table 224 \u2013 Service_activate <\/td>\n<\/tr>\n | ||||||
343<\/td>\n | Table 225 \u2013 Role_in_service Table 226 \u2013 Indication_mode <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | Table 227 \u2013 Max_DLSDU_length_req_low Table 228 \u2013 Max_DLSDU_length_req_high <\/td>\n<\/tr>\n | ||||||
345<\/td>\n | Table 229 \u2013 Max_DLSDU_length_ind_low Table 230 \u2013 Max_DLSDU_length_ind_high <\/td>\n<\/tr>\n | ||||||
346<\/td>\n | Table 231 \u2013 Sync <\/td>\n<\/tr>\n | ||||||
347<\/td>\n | Table 232 \u2013 Freeze <\/td>\n<\/tr>\n | ||||||
348<\/td>\n | Table 233 \u2013 DPV1 enabled Table 234 \u2013 Fail\u00a0safe <\/td>\n<\/tr>\n | ||||||
349<\/td>\n | Table 235 \u2013 Enable publisher Table 236 \u2013 WD base <\/td>\n<\/tr>\n | ||||||
350<\/td>\n | Table 237 \u2013 Alarm mode <\/td>\n<\/tr>\n | ||||||
360<\/td>\n | Table 238 \u2013 Fail\u00a0safe <\/td>\n<\/tr>\n | ||||||
367<\/td>\n | Table 239 \u2013 S_SAP_index <\/td>\n<\/tr>\n | ||||||
368<\/td>\n | Table 240 \u2013 D_SAP_index Table 241 \u2013 D_addr Table 242 \u2013 Service_activate <\/td>\n<\/tr>\n | ||||||
369<\/td>\n | Table 243 \u2013 Role_in_service Table 244 \u2013 Max_DLSDU_length_req_low Table 245 \u2013 Max_DLSDU_length_req_high <\/td>\n<\/tr>\n | ||||||
370<\/td>\n | Table 246 \u2013 Max_DLSDU_length_ind_low Table 247 \u2013 Max_DLSDU_length_ind_high <\/td>\n<\/tr>\n | ||||||
371<\/td>\n | Table 248 \u2013 DLL init DP-slave <\/td>\n<\/tr>\n | ||||||
372<\/td>\n | Table 249 \u2013 Load ARL DP-slave <\/td>\n<\/tr>\n | ||||||
378<\/td>\n | Table 250 \u2013 Get ARL DP-slave <\/td>\n<\/tr>\n | ||||||
384<\/td>\n | Table 251 \u2013 Set ARL isochronous mode <\/td>\n<\/tr>\n | ||||||
385<\/td>\n | Table 252 \u2013 Load ARL DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
388<\/td>\n | Table 253 \u2013 Get ARL DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
390<\/td>\n | Table 254 \u2013 ARL Slave update DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
392<\/td>\n | Table 255 \u2013 Load ARL DP-master Cl2 <\/td>\n<\/tr>\n | ||||||
393<\/td>\n | Table 256 \u2013 Get ARL DP-master Cl2 <\/td>\n<\/tr>\n | ||||||
394<\/td>\n | Table 257 \u2013 Load CRL DP-slave <\/td>\n<\/tr>\n | ||||||
396<\/td>\n | Table 258 \u2013 Load CRL DXB link entries <\/td>\n<\/tr>\n | ||||||
397<\/td>\n | Table 259 \u2013 Get CRL DP-slave <\/td>\n<\/tr>\n | ||||||
399<\/td>\n | Table 260 \u2013 Load CRL DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
412<\/td>\n | Table 261 \u2013 Get CRL DP-master Cl1 <\/td>\n<\/tr>\n | ||||||
425<\/td>\n | Table 262 \u2013 CRL Slave activate <\/td>\n<\/tr>\n | ||||||
426<\/td>\n | Table 263 \u2013 CRL Slave new Prm <\/td>\n<\/tr>\n | ||||||
427<\/td>\n | Table 264 \u2013 CRL Slave new Prm data <\/td>\n<\/tr>\n | ||||||
429<\/td>\n | Table 265 \u2013 Load CRL DP-master Cl2 <\/td>\n<\/tr>\n | ||||||
431<\/td>\n | Table 266 \u2013 Get CRL DP-master Cl2 <\/td>\n<\/tr>\n | ||||||
432<\/td>\n | 6.3 Summary of FAL classes Table 267 \u2013 Fieldbus\u00a0AL class summary <\/td>\n<\/tr>\n | ||||||
433<\/td>\n | 6.4 Permitted FAL services by AREP role <\/td>\n<\/tr>\n | ||||||
434<\/td>\n | Table 268 \u2013 Assignment of the services to DP-masters and DP-slaves <\/td>\n<\/tr>\n | ||||||
435<\/td>\n | Table 269 \u2013 Support of AR types in the different DP-device types <\/td>\n<\/tr>\n | ||||||
436<\/td>\n | Table 270 \u2013 Support of services at the different AREPs respectively CREPs <\/td>\n<\/tr>\n | ||||||
437<\/td>\n | 6.5 Conformance classes <\/td>\n<\/tr>\n | ||||||
438<\/td>\n | 6.6 Application characteristics Table 271 \u2013 Conformance classes DP-master (class 1) Table 272 \u2013 Conformance classes DP-master (class 2) <\/td>\n<\/tr>\n | ||||||
439<\/td>\n | Figure 44 \u2013 Cycle time of the DP system <\/td>\n<\/tr>\n | ||||||
440<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 3 elements<\/b><\/p>\n |