{"id":244022,"date":"2024-10-19T16:01:26","date_gmt":"2024-10-19T16:01:26","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-5-22012\/"},"modified":"2024-10-25T10:59:35","modified_gmt":"2024-10-25T10:59:35","slug":"bs-en-61158-5-22012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-5-22012\/","title":{"rendered":"BS EN 61158-5-2:2012"},"content":{"rendered":"

1.1<\/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 2 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 Type 2 fieldbus application layer in terms of<\/p>\n

    \n
  1. \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

  2. \n

    the primitive actions and events of the service;<\/p>\n<\/li>\n

  3. \n

    the parameters associated with each primitive action and event, and the form which they take; and<\/p>\n<\/li>\n

  4. \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

      \n
    1. \n

      the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and<\/p>\n<\/li>\n

    2. \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 Type 2 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.2<\/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

        \n
      1. \n

        the sizes and octet ordering of various multi-octet service parameters, and<\/p>\n<\/li>\n

      2. \n

        the correlation of paired request and confirm, or indication and response, primitives.<\/p>\n<\/li>\n<\/ol>\n

        1.3 Conformance<\/b><\/p>\n

        This standard does not specify individual implementations or products, nor does it 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 the Type 2 application layer services as defined in this standard.<\/p>\n

        PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
        PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
        7<\/td>\nCONTENTS <\/td>\n<\/tr>\n
        10<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
        11<\/td>\n1 Scope
        1.1 Overview <\/td>\n<\/tr>\n
        12<\/td>\n1.2 Specifications
        1.3 Conformance
        2 Normative references <\/td>\n<\/tr>\n
        13<\/td>\n3 Terms, definitions, symbols, abbreviations and conventions
        3.1 ISO\/IEC\u00a07498 1 terms <\/td>\n<\/tr>\n
        14<\/td>\n3.2 ISO\/IEC\u00a08822 terms
        3.3 ISO\/IEC\u00a09545 terms
        3.4 ISO\/IEC\u00a08824 terms
        3.5 Type 2 fieldbus data-link layer terms
        3.6 Type 2 fieldbus application-layer specific definitions <\/td>\n<\/tr>\n
        21<\/td>\n3.7 Type 2 abbreviations and symbols <\/td>\n<\/tr>\n
        22<\/td>\n3.8 Conventions <\/td>\n<\/tr>\n
        25<\/td>\n4 Common concepts
        5 Data type ASE
        5.1 General
        5.2 Formal definition of data type objects
        5.3 FAL defined data types <\/td>\n<\/tr>\n
        34<\/td>\nTables
        Table 1 \u2013 Valid IANA MIB printer codes for character set selection <\/td>\n<\/tr>\n
        35<\/td>\n5.4 Data type ASE service specification
        6 Communication model specification
        6.1 Concepts <\/td>\n<\/tr>\n
        37<\/td>\nFigures
        Figure 1 \u2013 Overview of ASEs and object classes <\/td>\n<\/tr>\n
        38<\/td>\nFigure 2 \u2013 Addressing format using MAC, class, instance and attribute IDs <\/td>\n<\/tr>\n
        40<\/td>\nTable 2 \u2013 Common elements <\/td>\n<\/tr>\n
        41<\/td>\nTable 3 \u2013 ST language elements
        Table 4 \u2013 Type conversion operations <\/td>\n<\/tr>\n
        42<\/td>\nTable 5 \u2013 Values of implementation-dependent parameters <\/td>\n<\/tr>\n
        43<\/td>\n6.2 ASEs
        Table 6 \u2013 Extensions to IEC\u00a061131 3:2003 <\/td>\n<\/tr>\n
        55<\/td>\nFigure 3 \u2013 Identity object state transition diagram <\/td>\n<\/tr>\n
        56<\/td>\nTable 7 \u2013 Identity object state event matrix <\/td>\n<\/tr>\n
        60<\/td>\nFigure 4 \u2013 Static Assembly state transition diagram
        Table 8 \u2013 Static Assembly state event matrix <\/td>\n<\/tr>\n
        61<\/td>\nFigure 5 \u2013 Dynamic Assembly state transition diagram
        Table 9 \u2013 Dynamic Assembly state event matrix <\/td>\n<\/tr>\n
        64<\/td>\nTable 10 \u2013 Message Router object Forward_Open parameters <\/td>\n<\/tr>\n
        67<\/td>\nTable 11 \u2013 Acknowledge Handler object state event matrix <\/td>\n<\/tr>\n
        68<\/td>\nTable 12 \u2013 Producing I\/O application object state event matrix <\/td>\n<\/tr>\n
        70<\/td>\nFigure 6 \u2013 Typical timing relationships for acknowledged data production
        Figure 7 \u2013 Example of a COS system with two acking devices
        Figure 8 \u2013 Message flow in COS connection \u2013 one Connection object, one consumer <\/td>\n<\/tr>\n
        71<\/td>\nFigure 9 \u2013 Message flow in COS connection \u2013 multiple consumers <\/td>\n<\/tr>\n
        80<\/td>\nTable 13 \u2013 Profile identification
        Table 14 \u2013 Profile default settings and ranges <\/td>\n<\/tr>\n
        81<\/td>\nTable 15 \u2013 Default PTP clock settings <\/td>\n<\/tr>\n
        82<\/td>\nTable 16 \u2013 Hand_Set clock quality management <\/td>\n<\/tr>\n
        83<\/td>\nFigure 10 \u2013 CPF2 time synchronization offset clock model
        Figure 11 \u2013 CPF2 time synchronization system with offset clock model <\/td>\n<\/tr>\n
        86<\/td>\nFigure 12 \u2013 CPF2 time synchronization group startup sequence <\/td>\n<\/tr>\n
        92<\/td>\nFigure 13 \u2013 Parameter object state transition diagram
        Table 17 \u2013 Parameter object state event matrix <\/td>\n<\/tr>\n
        95<\/td>\nTable 18 \u2013 Status codes <\/td>\n<\/tr>\n
        97<\/td>\nTable 19 \u2013 Get_Attribute_All service parameters <\/td>\n<\/tr>\n
        98<\/td>\nTable 20 \u2013 Set_Attribute_All service parameters <\/td>\n<\/tr>\n
        100<\/td>\nTable 21 \u2013 Get_Attribute_List service parameters <\/td>\n<\/tr>\n
        102<\/td>\nTable 22 \u2013 Set_Attribute_List service parameters <\/td>\n<\/tr>\n
        104<\/td>\nTable 23 \u2013 Reset service parameters <\/td>\n<\/tr>\n
        106<\/td>\nTable 24 \u2013 Start service parameters <\/td>\n<\/tr>\n
        108<\/td>\nTable 25 \u2013 Stop service parameters <\/td>\n<\/tr>\n
        109<\/td>\nTable 26 \u2013 Create service parameters <\/td>\n<\/tr>\n
        111<\/td>\nTable 27 \u2013 Delete service parameters <\/td>\n<\/tr>\n
        112<\/td>\nTable 28 \u2013 Get_Attribute_Single service parameters <\/td>\n<\/tr>\n
        114<\/td>\nTable 29 \u2013 Set_Attribute_Single service parameters <\/td>\n<\/tr>\n
        115<\/td>\nTable 30 \u2013 Find_Next_Object_Instance service parameters <\/td>\n<\/tr>\n
        117<\/td>\nFigure 14 \u2013 Example of Find_Next_Object_Instance service <\/td>\n<\/tr>\n
        118<\/td>\nTable 31 \u2013 NOP service parameters <\/td>\n<\/tr>\n
        119<\/td>\nTable 32 \u2013 Apply_Attributes service parameters <\/td>\n<\/tr>\n
        121<\/td>\nTable 33 \u2013 Save service parameters <\/td>\n<\/tr>\n
        122<\/td>\nTable 34 \u2013 Restore service parameters <\/td>\n<\/tr>\n
        124<\/td>\nTable 35 \u2013 Group_Sync service parameters <\/td>\n<\/tr>\n
        126<\/td>\nTable 36 \u2013 Add_AckData_Path service parameters <\/td>\n<\/tr>\n
        127<\/td>\nTable 37 \u2013 Remove_AckData_Path service parameters <\/td>\n<\/tr>\n
        128<\/td>\nTable 38 \u2013 Get-Enum_String service parameters <\/td>\n<\/tr>\n
        136<\/td>\nTable 39 \u2013 CM_Open service parameters <\/td>\n<\/tr>\n
        138<\/td>\nTable 40 \u2013 CM_Close service parameters <\/td>\n<\/tr>\n
        140<\/td>\nTable 41 \u2013 CM_ Unconnected_Send service parameters <\/td>\n<\/tr>\n
        142<\/td>\nTable 42 \u2013 CM_Get_Connection_Data service parameters <\/td>\n<\/tr>\n
        143<\/td>\nTable 43 \u2013 CM_Search_Connection_Data service parameters <\/td>\n<\/tr>\n
        144<\/td>\nTable 44 \u2013 CM_Get_Connection_Data service parameters <\/td>\n<\/tr>\n
        149<\/td>\nTable 45 \u2013 I\/O Connection object attribute access <\/td>\n<\/tr>\n
        150<\/td>\nTable 46 \u2013 Bridged Connection object attribute access <\/td>\n<\/tr>\n
        151<\/td>\nTable 47 \u2013 Explicit messaging object attribute access <\/td>\n<\/tr>\n
        152<\/td>\nFigure 15 \u2013 Transmission trigger timer <\/td>\n<\/tr>\n
        153<\/td>\nFigure 16 \u2013 Inactivity watchdog timer <\/td>\n<\/tr>\n
        154<\/td>\nFigure 17 \u2013 Using tools for configuration <\/td>\n<\/tr>\n
        155<\/td>\nFigure 18 \u2013 Production inhibit timer <\/td>\n<\/tr>\n
        156<\/td>\nTable 48 \u2013 Connection_Bind service parameters <\/td>\n<\/tr>\n
        157<\/td>\nTable 49 \u2013 Service_Name service parameters <\/td>\n<\/tr>\n
        158<\/td>\n6.3 ARs <\/td>\n<\/tr>\n
        160<\/td>\nTable 50 \u2013 How production trigger, transport class, and CM_RPI determine when data is produced <\/td>\n<\/tr>\n
        161<\/td>\nFigure 19 \u2013 Context of transport services within the connection model
        Figure 20 \u2013 Application\u2013to\u2013application view of data transfer <\/td>\n<\/tr>\n
        162<\/td>\nFigure 21 \u2013 Data flow diagram for a link producer <\/td>\n<\/tr>\n
        163<\/td>\nFigure 22 \u2013 Data flow diagram for a link consumer <\/td>\n<\/tr>\n
        164<\/td>\nFigure 23 \u2013 Triggers <\/td>\n<\/tr>\n
        165<\/td>\nFigure 24 \u2013 Binding transport instances to the producer and consumer of a transport connection that does not have a reverse data path
        Figure 25 \u2013 Binding transport instances to the producers and consumers of a transport connection that does have a reverse data path <\/td>\n<\/tr>\n
        166<\/td>\nFigure 26 \u2013 Binding transport instances to the producer and consumers of a multipoint connection when the transport connection does not have a reverse data path
        Figure 27 \u2013 Binding transport instances to the producers and consumers of a multipoint connection when the transport connection does have reverse data paths <\/td>\n<\/tr>\n
        171<\/td>\nTable 51 \u2013 Transport classes <\/td>\n<\/tr>\n
        188<\/td>\nTable 52 \u2013 UCMM_Create service parameters <\/td>\n<\/tr>\n
        189<\/td>\nTable 53 \u2013 UCMM_Delete service parameters <\/td>\n<\/tr>\n
        190<\/td>\nTable 54 \u2013 UCMM_Write service parameters <\/td>\n<\/tr>\n
        191<\/td>\nTable 55 \u2013 UCMM_Abort service parameters <\/td>\n<\/tr>\n
        192<\/td>\nTable 56 \u2013 TR_Write service parameters <\/td>\n<\/tr>\n
        193<\/td>\nTable 57 \u2013 TR_Trigger service parameters
        Table 58 \u2013 TR_Packet_arrived service parameters <\/td>\n<\/tr>\n
        194<\/td>\nTable 59 \u2013 TR_Ack_received service parameters
        Table 60 \u2013 TR_Verify service parameters <\/td>\n<\/tr>\n
        195<\/td>\n6.4 Summary of FAL classes
        Table 61 \u2013 TR_Status_updated service parameters <\/td>\n<\/tr>\n
        196<\/td>\n6.5 Permitted FAL services by AR type
        Table 62 \u2013 FAL class summary <\/td>\n<\/tr>\n
        197<\/td>\nTable 63 \u2013 FAL services by AR type <\/td>\n<\/tr>\n
        198<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

        Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 2 elements<\/b><\/p>\n\n\n\n\n
        Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
        BSI<\/b><\/a><\/td>\n2012<\/td>\n200<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":244028,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[675,2641],"product_tag":[],"class_list":{"0":"post-244022","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-100-70","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/244022","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/244028"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=244022"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=244022"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=244022"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}