BS EN 61158-5-3:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 3 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2012 | 442 |
1.1 General
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 “three-layer” fieldbus reference model described in IEC/TR 61158-1.
This sub-part contains material specific to Type 3 fieldbus.
1.2 Overview
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 “window between corresponding application programs.”
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 “time-critical” 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.
This standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of
-
an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
-
the primitive actions and events of the service;
-
the parameters associated with each primitive action and event, and the form which they take; and
-
the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
-
the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
-
Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.
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).
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.
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.
1.3 Specifications
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.
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.
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
-
the sizes and octet ordering of various multi-octet service parameters, and
-
the correlation of paired request and confirm, or indication and response, primitives.
1.4 Conformance
This standard do not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems.
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.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | CONTENTS |
| 15 | INTRODUCTION |
| 16 | 1 Scope 1.1 General 1.2 Overview |
| 17 | 1.3 Specifications 1.4 Conformance 2 Normative references |
| 18 | 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Referenced terms and definitions |
| 19 | 3.2 Fieldbus Application Layer type 3 – specific terms and definitions |
| 27 | 3.3 Abbreviations and symbols 3.4 Conventions |
| 34 | 4 Concepts 5 Data type ASE 6 Communication model specification 6.1 DP concepts |
| 36 | Tables Table 1 – Requirements and features of fieldbus DP |
| 37 | Figures Figure 1 – Example of DP communication with a single controlling device Figure 2 – Example of DP communication with several controlling devices |
| 38 | Figure 3 – Example of DP communication between field devices |
| 40 | Figure 4 – DP-slave model (modular DP-slave) |
| 41 | Figure 5 – DP-slave model (compact DP-slave) |
| 42 | Figure 6 – Overview of application processes |
| 43 | Figure 7 – DP-slave model (modular DP-slave) |
| 45 | Figure 8 – Application Service Elements (ASEs) |
| 47 | Figure 10 – Access to a remote APO |
| 48 | Figure 11 – Access to a remote APO for publisher/subscriber association |
| 49 | Figure 12 – Example of one AR with two AREPs |
| 53 | Table 2 – Status values of the service primitives |
| 54 | 6.2 ASEs |
| 55 | Figure 13 – Relation of a simple process data object to the real object |
| 56 | Table 3 – Access Rights MS1 Table 4 – Access Rights MS2 |
| 57 | Figure 14 – Relation of a combined process data object to the real objects |
| 59 | Table 5 – Access Rights MS1 Table 6 – Access Rights MS2 |
| 60 | Table 7 – SCL matching rules Table 8 – Read |
| 62 | Table 9 – Write |
| 63 | Table 10 – Data transport |
| 67 | Table 11 – Format (simple input data description) Table 12 – Consistency (simple input data description) |
| 69 | Table 13 – Format (simple output data) Table 14 – Consistency (simple output data) |
| 70 | Table 15 – Format (extended input data) |
| 71 | Table 16 – Consistency (extended input data) |
| 72 | Table 17 – Format (extended output data) |
| 73 | Table 18 – Consistency (extended output data) |
| 74 | Table 19 – Set Input Table 20 – Read Input |
| 76 | Table 21 – Get Input |
| 77 | Table 22 – New Input |
| 78 | Table 23 – Set Output |
| 79 | Table 24 – Final Table 25 – Read Output |
| 80 | Table 26 – Get Output Table 27 – Clear Flag |
| 81 | Table 28 – New Flag Table 29 – New Output Table 30 – Clear Flag |
| 82 | Table 31 – Global Control Table 32 – Clear Command Table 33 – Sync Command |
| 83 | Table 34 – Freeze Command Table 35 – New publisher data |
| 84 | Table 36 – Get publisher data Table 37 – New Flag |
| 85 | Table 38 – SYNCH Table 39 – SYNCH Delayed |
| 86 | Table 40 – DX Finished Table 41 – SYNCH Event Table 42 – Status |
| 88 | Figure 15 – Sequence of an isochronous DP cycle with one DP-master (class 1) |
| 90 | Figure 16 – Additional time relationships in a DP system operating in isochronous mode |
| 91 | Figure 17 – DP system with optimized isochronous DP cycle |
| 93 | Figure 18 – Buffered synchronized isochronous mode at the DP-master (class 1) |
| 94 | Figure 19 – Enhanced synchronized isochronous mode at the DP-master (class 1) Figure 20 – Input, output and PLL state machine interaction |
| 96 | Table 43 – Primitives issued by the AL to the PLL state machine Table 44 – Primitives issued by the user to the PLL state machine Table 45 – Allowed values of Status |
| 97 | Table 46 – Primitives issued by the user to the input state machine Table 47 – Primitives issued by the user to the output state machine Table 48 – Primitives issued by the PLL to the output state machine Table 49 – Primitives issued by the output to the PLL state machine Table 50 – Primitives issued by the PLL to the input state machine |
| 98 | Table 51 – Primitives issued by the output to the input state machine Table 52 – Primitives issued by the output state machine to the AL Table 53 – Primitives issued by the AL to the output state machine Table 54 – Primitives issued by the input state machine to the AL Table 55 – Primitives issued by the AL to the input state machine |
| 100 | Figure 21 – PLL state diagram |
| 101 | Table 56 – PLL state table |
| 104 | Figure 22 – OUTPUT state diagram |
| 105 | Table 57 – OUTPUT state table |
| 108 | Figure 23 – INPUT state diagram |
| 109 | Table 58 – INPUT state table |
| 111 | Table 59 – Identifier status |
| 112 | Table 60 – Channel type |
| 113 | Table 61 – IO type Table 62 – Status type |
| 114 | Table 63 – Status specifier |
| 115 | Table 64 – Status specifier Table 65 – Module status |
| 116 | Table 66 – Status specifier Table 67 – Link status |
| 117 | Table 68 – Link error |
| 118 | Table 69 – Set Slave Diag |
| 119 | Table 70 – Ext Diag Flag |
| 121 | Table 71 – Get Slave Diag |
| 130 | Table 72 – Read Slave Diag |
| 140 | Table 73 – New Slave Diag |
| 141 | Figure 24 – Treatment of an alarm in the DP system |
| 142 | Table 74 – Alarm type |
| 143 | Table 75 – Add Ack Table 76 – Alarm specifier |
| 144 | Table 77 – Alarm notification |
| 145 | Table 78 – Alarm Ack |
| 150 | Table 79 – Prm data type |
| 160 | Table 80 – Supported feature Table 81 – Supported profile feature |
| 161 | Table 82 – Role |
| 162 | Table 83 – Check user Prm |
| 163 | Table 84 – Prm structure |
| 166 | Table 85 – MS1 Command |
| 167 | Table 86 – Check user Prm result |
| 168 | Table 87 – Status values |
| 169 | Table 88 – Check Ext user Prm |
| 172 | Table 89 – Check Ext user Prm result |
| 173 | Table 90 – Status values Table 91 – Check Cfg |
| 174 | Table 92 – Check Cfg result |
| 175 | Table 93 – Status values Table 94 – Set Cfg |
| 176 | Table 95 – Get Cfg |
| 177 | Table 96 – Set Slave Add |
| 178 | Table 97 – Initiate |
| 181 | Table 98 – Abort Table 99 – Instance |
| 182 | Table 100 – MS0 init DP-slave Table 101 – MS1 init DP-slave |
| 183 | Table 102 – MS2 init DP-slave Table 103 – DP-slave started |
| 184 | Table 104 – Alarm limit Table 105 – DP-slave stopped |
| 185 | Table 106 – Reset DP-slave Table 107 – DP-slave fault Table 108 – Application ready DP-slave |
| 186 | Table 109 – Start subscriber Table 110 – Stop subscriber |
| 187 | Table 111 – Publisher active |
| 188 | Table 112 – Status Table 113 – Init DP-master Cl1 |
| 189 | Table 114 – DP-master Cl1 started |
| 190 | Table 115 – Alarm limit Table 116 – DP-master Cl1 stopped Table 117 – Reset DP-master Cl1 |
| 191 | Table 118 – DP-master Cl1 fault Table 119 – DP-master Cl1 reject |
| 192 | Table 120 – Set mode DP-master Cl1 |
| 193 | Table 121 – DP-master Cl1 mode changed |
| 194 | Table 122 – Load bus Par DP-master Cl1 |
| 195 | Table 123 – Mark DP-master Cl1 Table 124 – Abort DP-master Cl1 |
| 196 | Table 125 – Read value DP-master Cl1 Table 126 – Delete SC DP-master Cl1 |
| 197 | Table 127 – DP-master Cl1 event |
| 198 | Table 128 – Init DP-master Cl2 |
| 199 | Table 129 – Reset DP-master Cl2 Table 130 – DP-master Cl2 fault Table 131 – DP-master Cl2 reject |
| 200 | Table 132 – DP-master Cl2 closed Table 133 – DP-master Cl2 event |
| 201 | Table 134 – USIF state |
| 205 | Table 135 – Data rate |
| 206 | Table 136 – USIF state Table 137 – Isochronous mode |
| 209 | Table 138 – Slave type |
| 210 | Table 139 – Alarm mode |
| 213 | Table 140 – Get Master Diag Table 141 – MDiag identifier |
| 214 | Table 142 – Start Seq |
| 215 | Table 143 – Area code (start seq) |
| 216 | Table 144 – Download |
| 217 | Table 145 – Upload |
| 218 | Table 146 – End Seq |
| 219 | Table 147 – Act Para Brct Table 148 – Area code (Act Para Brct) |
| 220 | Table 149 – Act param |
| 221 | Table 150 – Area code (Act param) Table 151 – Activate |
| 223 | Table 152 – Access rights MS1 |
| 224 | Table 153 – Access rights MS2 Table 154 – Load region state |
| 226 | Table 155 – Initiate load |
| 227 | Table 156 – Default values for the parameter Intersegment Request Timeout |
| 228 | Table 157 – Push segment |
| 230 | Table 158 – Pull segment |
| 232 | Table 159 – Terminate load |
| 234 | Table 160 – Primitives issued by the user to the Load Region state machine |
| 235 | Table 161 – Primitives issued by the Load Region state machine to the user Table 162 – Primitives issued by the Function Invocation to the Load Region state machine |
| 236 | Table 163 – Primitives issued by the Load Region to the Function Invocation state machine Table 164 – Load Region state definitions |
| 237 | Table 165 – Load Region function table |
| 239 | Figure 25 – Load Region state diagram for erasable memory |
| 240 | Figure 26 – Load region state diagram for non erasable memory Table 166 – Load Region state table for erasable memory |
| 252 | Table 167 – Load Region state table for non erasable memory |
| 257 | Table 168 – Access rights MS1 Table 169 – Access rights MS2 |
| 258 | Table 170 – Function Invocation state Table 171 – Load Region object in use |
| 259 | Table 172 – Access rights MS1 |
| 260 | Table 173 – Access rights MS2 Table 174 – Load Region object in use |
| 261 | Table 175 – Start |
| 262 | Table 176 – Stop |
| 263 | Table 177 – Resume |
| 264 | Table 178 – Reset |
| 265 | Table 179 – Get FI state |
| 266 | Table 180 – Call |
| 268 | Table 181 – Primitives issued by the user to the Function Invocation state machine |
| 269 | Table 182 – Primitives issued by the Function Invocation state machine to the user Table 183 – Primitives issued by the Load Region to the Function Invocation state machine |
| 270 | Table 184 – Primitives issued by the Function Invocation to the Load Region state machine Table 185 – Function Invocation state definitions |
| 271 | Table 186 – Function definitions |
| 272 | Figure 27 – Function invocation state diagram Table 187 – Function Invocation state table |
| 288 | Table 188 – CS status Table 189 – Summertime |
| 289 | Table 190 – Synchronization active Table 191 – Announcement hour |
| 290 | Table 192 – Summertime Table 193 – Accuracy |
| 291 | Table 194 – Set time |
| 292 | Table 195 – Sync interval violation |
| 293 | Figure 29 – Assignment of communication relationship to application relationship |
| 299 | Figure 30 – MS0 application relationship |
| 300 | Figure 31 – Output buffer model of a DP-slave without sync functionality Figure 32 – Output buffer model of a DP-slave with sync functionality |
| 301 | Figure 33 – Input buffer model of a DP-slave without freeze functionality Figure 34 – Input buffer model of a DP-slave with freeze functionality |
| 302 | Figure 35 – MS1 application relationship Figure 36 – MS2 application relationship |
| 304 | Figure 37 – Example of inter-network communication Figure 38 – Example without inter-network addressing |
| 305 | Figure 39 – First example with inter-network addressing Table 196 – Parameter of Initiate service without inter-network addressing Table 197 – Parameter of Initiate service with inter-network addressing (first example) |
| 306 | Figure 40 – Second example with inter-network addressing Table 198 – Parameter of Initiate service with inter-network addressing (second example) |
| 307 | Figure 41 – MS3 application relationship Figure 42 – MM1 application relationship |
| 308 | Figure 43 – MM2 application relationship |
| 312 | Table 199 – AR type |
| 314 | Table 200 – Sync supported Table 201 – Freeze supported |
| 316 | Table 202 – Group identifier Table 203 – DPV1 enabled |
| 317 | Table 204 – Fail safe Table 205 – WD base |
| 319 | Table 206 – No Add change |
| 322 | Table 207 – Alarm mode supported |
| 326 | Table 208 – Isochronous mode supp Table 209 – Isochronous mode |
| 327 | Table 210 – Alarm mode |
| 328 | Table 211 – Time device type |
| 331 | Table 212 – S_SAP_index |
| 332 | Table 213 – D_addr Table 214 – Service_activate |
| 333 | Table 215 – Role_in_service |
| 334 | Table 216 – Indication_mode Table 217 – Max_DLSDU_length_req_low |
| 335 | Table 218 – Max_DLSDU_length_req_high Table 219 – Max_DLSDU_length_ind_low |
| 336 | Table 220 – Max_DLSDU_length_ind_high |
| 341 | Table 221 – S_SAP_index Table 222 – D_SAP_index |
| 342 | Table 223 – D_addr Table 224 – Service_activate |
| 343 | Table 225 – Role_in_service Table 226 – Indication_mode |
| 344 | Table 227 – Max_DLSDU_length_req_low Table 228 – Max_DLSDU_length_req_high |
| 345 | Table 229 – Max_DLSDU_length_ind_low Table 230 – Max_DLSDU_length_ind_high |
| 346 | Table 231 – Sync |
| 347 | Table 232 – Freeze |
| 348 | Table 233 – DPV1 enabled Table 234 – Fail safe |
| 349 | Table 235 – Enable publisher Table 236 – WD base |
| 350 | Table 237 – Alarm mode |
| 360 | Table 238 – Fail safe |
| 367 | Table 239 – S_SAP_index |
| 368 | Table 240 – D_SAP_index Table 241 – D_addr Table 242 – Service_activate |
| 369 | Table 243 – Role_in_service Table 244 – Max_DLSDU_length_req_low Table 245 – Max_DLSDU_length_req_high |
| 370 | Table 246 – Max_DLSDU_length_ind_low Table 247 – Max_DLSDU_length_ind_high |
| 371 | Table 248 – DLL init DP-slave |
| 372 | Table 249 – Load ARL DP-slave |
| 378 | Table 250 – Get ARL DP-slave |
| 384 | Table 251 – Set ARL isochronous mode |
| 385 | Table 252 – Load ARL DP-master Cl1 |
| 388 | Table 253 – Get ARL DP-master Cl1 |
| 390 | Table 254 – ARL Slave update DP-master Cl1 |
| 392 | Table 255 – Load ARL DP-master Cl2 |
| 393 | Table 256 – Get ARL DP-master Cl2 |
| 394 | Table 257 – Load CRL DP-slave |
| 396 | Table 258 – Load CRL DXB link entries |
| 397 | Table 259 – Get CRL DP-slave |
| 399 | Table 260 – Load CRL DP-master Cl1 |
| 412 | Table 261 – Get CRL DP-master Cl1 |
| 425 | Table 262 – CRL Slave activate |
| 426 | Table 263 – CRL Slave new Prm |
| 427 | Table 264 – CRL Slave new Prm data |
| 429 | Table 265 – Load CRL DP-master Cl2 |
| 431 | Table 266 – Get CRL DP-master Cl2 |
| 432 | 6.3 Summary of FAL classes Table 267 – Fieldbus AL class summary |
| 433 | 6.4 Permitted FAL services by AREP role |
| 434 | Table 268 – Assignment of the services to DP-masters and DP-slaves |
| 435 | Table 269 – Support of AR types in the different DP-device types |
| 436 | Table 270 – Support of services at the different AREPs respectively CREPs |
| 437 | 6.5 Conformance classes |
| 438 | 6.6 Application characteristics Table 271 – Conformance classes DP-master (class 1) Table 272 – Conformance classes DP-master (class 2) |
| 439 | Figure 44 – Cycle time of the DP system |
| 440 | Bibliography |
