{"id":244978,"date":"2024-10-19T16:06:23","date_gmt":"2024-10-19T16:06:23","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-5-262019\/"},"modified":"2024-10-25T11:05:59","modified_gmt":"2024-10-25T11:05:59","slug":"bs-en-iec-61158-5-262019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-5-262019\/","title":{"rendered":"BS EN IEC 61158-5-26:2019"},"content":{"rendered":"

1.1 Overview<\/b><\/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 part of IEC 61158 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 26 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 International Standard defines in an abstract way the externally visible service provided by the different Types of 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 document 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 document specifies the structure and services of the IEC Fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO\/IEC 7498-1) and the OSI Application Layer Structure (see 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 document to provide access to the FAL to control certain aspects of its operation.<\/p>\n

      1.2 Specifications<\/b><\/p>\n

      The principal objective of this document 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 timecritical 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 document 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 any given Type of application layer services as defined in this document.<\/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
        PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
        2<\/td>\nNational foreword <\/td>\n<\/tr>\n
        5<\/td>\nAnnex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n
        7<\/td>\nCONTENTS <\/td>\n<\/tr>\n
        10<\/td>\nFOREWORD <\/td>\n<\/tr>\n
        12<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
        13<\/td>\n1 Scope
        1.1 Overview <\/td>\n<\/tr>\n
        14<\/td>\n1.2 Specifications
        1.3 Conformance
        2 Normative references <\/td>\n<\/tr>\n
        15<\/td>\n3 Terms, definitions, symbols, abbreviations and conventions <\/td>\n<\/tr>\n
        16<\/td>\n3.1 Terms and definitions from other ISO\/IEC standards
        3.1.1 Terms and definitions from ISO\/IEC\u00a074981
        3.1.2 Terms and definitions from ISO\/IEC\u00a08822
        3.1.3 Terms and definitions from ISO\/IEC\u00a09545
        3.1.4 Terms and definitions from ISO\/IEC 88241 <\/td>\n<\/tr>\n
        17<\/td>\n3.2 Fieldbus application layer Type\u00a026-specific definitions <\/td>\n<\/tr>\n
        23<\/td>\n3.3 Abbreviations and symbols <\/td>\n<\/tr>\n
        25<\/td>\n3.4 Conventions
        3.4.1 Overview
        3.4.2 General conventions
        3.4.3 Conventions for class definitions <\/td>\n<\/tr>\n
        26<\/td>\n3.4.4 Conventions for service definitions <\/td>\n<\/tr>\n
        27<\/td>\n4 Concepts <\/td>\n<\/tr>\n
        28<\/td>\n5 Data type ASE
        5.1 Overview
        5.2 Formal definition of data type objects
        5.2.1 Data type class definitions <\/td>\n<\/tr>\n
        29<\/td>\n5.2.2 Attributes <\/td>\n<\/tr>\n
        30<\/td>\n5.3 FAL defined data types
        5.3.1 Fixed length types <\/td>\n<\/tr>\n
        34<\/td>\n5.3.2 String types <\/td>\n<\/tr>\n
        35<\/td>\n5.4 Data type ASE service specification
        6 Communication model specification
        6.1 General
        6.2 Protocol stack for Type 26 fieldbus <\/td>\n<\/tr>\n
        36<\/td>\n6.3 Overview of Type 26 communication model
        Figures
        Figure 1 \u2013 Protocol stack for Type 26 fieldbus <\/td>\n<\/tr>\n
        37<\/td>\n6.4 Cyclic data communication service with Common-memory
        6.4.1 Overview
        6.4.2 Common\u2013memory: allocation to each node
        Figure 2 \u2013 Unconfirmed Push-Publisher\/Subscriber type interaction
        Figure 3 \u2013 Unconfirmed\/Confirmed Client\/Server type interaction <\/td>\n<\/tr>\n
        38<\/td>\n6.4.3 Data sharing among nodes with the CM
        Figure 4 \u2013 Common memory allocation <\/td>\n<\/tr>\n
        39<\/td>\nFigure 5 \u2013 Data sharing with the CM
        Figure 6 \u2013 Node #01 for reception only <\/td>\n<\/tr>\n
        40<\/td>\n6.4.4 CM data type
        6.5 ASEs
        6.5.1 Overview of Type 26 ASEs
        Figure 7 \u2013 Node #01 without the CM <\/td>\n<\/tr>\n
        41<\/td>\n6.5.2 Type\u00a026 specific conventions for FAL service common parameters
        Figure 8 \u2013 The structure of ASEs for Type 26 FAL <\/td>\n<\/tr>\n
        42<\/td>\n6.5.3 Cyclic-data ASE <\/td>\n<\/tr>\n
        44<\/td>\nTables
        Table 1 \u2013 Write service parameters <\/td>\n<\/tr>\n
        45<\/td>\nTable 2 \u2013 Send-CM service parameters
        Table 3 \u2013 Read service parameters <\/td>\n<\/tr>\n
        46<\/td>\nTable 4 \u2013 Update memory service parameters <\/td>\n<\/tr>\n
        47<\/td>\n6.5.4 Message data ASE
        Table 5 \u2013 Get- buffer service parameters <\/td>\n<\/tr>\n
        50<\/td>\nFigure 9 \u2013 Virtual-address-space for Byte block <\/td>\n<\/tr>\n
        51<\/td>\nTable 6 \u2013 Byte block read service parameters <\/td>\n<\/tr>\n
        52<\/td>\nTable 7 \u2013 Byte block write service parameters <\/td>\n<\/tr>\n
        53<\/td>\nFigure 10 \u2013 Virtual-address-space for Word block
        Table 8 \u2013 Word block read service parameters <\/td>\n<\/tr>\n
        54<\/td>\nTable 9 \u2013 Word block write service parameters <\/td>\n<\/tr>\n
        55<\/td>\nTable 10 \u2013 Network parameter read service parameters <\/td>\n<\/tr>\n
        56<\/td>\nTable 11 \u2013 Network parameter write service parameters <\/td>\n<\/tr>\n
        57<\/td>\nTable 12 \u2013 Stop command service parameters <\/td>\n<\/tr>\n
        58<\/td>\nTable 13 \u2013 Operation command service parameters
        Table 14 \u2013 profile read service parameters <\/td>\n<\/tr>\n
        61<\/td>\nTable 15 \u2013 Transparent message service parameters <\/td>\n<\/tr>\n
        62<\/td>\nTable 16 \u2013 Log data read service parameters
        Table 17 \u2013 Log data items <\/td>\n<\/tr>\n
        66<\/td>\nTable 18 \u2013 Log data clear service parameters <\/td>\n<\/tr>\n
        67<\/td>\nTable 19 \u2013 Message return service parameters <\/td>\n<\/tr>\n
        68<\/td>\nTable 20 \u2013 Vendor specific message service parameters <\/td>\n<\/tr>\n
        69<\/td>\nTable 21 \u2013 Set remote node configuration parameter service parameters
        Table 22 \u2013 Data elements and Node configuration parameters <\/td>\n<\/tr>\n
        70<\/td>\nTable 23 \u2013 Service parameters of Read remote participating node management information parameter service <\/td>\n<\/tr>\n
        71<\/td>\nTable 24 \u2013 Participating node management information parameters <\/td>\n<\/tr>\n
        72<\/td>\nTable 25 \u2013 Read remote node management information parameter service parameters
        Table 26 \u2013 Node management information parameters <\/td>\n<\/tr>\n
        73<\/td>\nTable 27 \u2013 Read remote node setting information parameter service parameters <\/td>\n<\/tr>\n
        74<\/td>\n6.5.5 Communication load measurement ASE
        Table 28 \u2013Node setting information parameters <\/td>\n<\/tr>\n
        76<\/td>\nTable 29 \u2013 Start TK-holding-time measurement service parameters
        Table 30 \u2013 Terminate TK-holding-time measurement service parameters <\/td>\n<\/tr>\n
        77<\/td>\nTable 31 \u2013 Token-holding-time measurement result <\/td>\n<\/tr>\n
        78<\/td>\nTable 32 \u2013 Start GP_Comm sender log service parameters
        Table 33 \u2013 Terminate GP_Comm sender log service parameters <\/td>\n<\/tr>\n
        79<\/td>\n6.5.6 Network management ASE
        Table 34 \u2013 GP_Comm sender log measurement result <\/td>\n<\/tr>\n
        82<\/td>\nTable 35 \u2013 Service parameters for Set configuration parameter <\/td>\n<\/tr>\n
        83<\/td>\nTable 36 \u2013 Configuration parameters
        Table 37 \u2013 Read node management information parameter service parameters <\/td>\n<\/tr>\n
        84<\/td>\nTable 38 \u2013 Node management information parameters <\/td>\n<\/tr>\n
        85<\/td>\nTable 39 \u2013 Service parameters for Read participating node mgt. information parameter
        Table 40 \u2013 Participating node management information parameters <\/td>\n<\/tr>\n
        86<\/td>\nTable 41 \u2013 Service parameters for Read network management information parameter
        Table 42 \u2013 Network management information parameters <\/td>\n<\/tr>\n
        87<\/td>\nTable 43 \u2013 Service parameters for Read message sequencenumber management information
        Table 44 \u2013 Read message sequence number management information parameters <\/td>\n<\/tr>\n
        88<\/td>\nTable 45 \u2013Read node status service parameters
        Table 46 \u2013 Read node status parameters <\/td>\n<\/tr>\n
        89<\/td>\nTable 47 \u2013 Upper layer operating condition matrix
        Table 48 \u2013Reset node service parameters <\/td>\n<\/tr>\n
        90<\/td>\nTable 49 \u2013 Set network address service parameters
        Table 50 \u2013 Register service parameters <\/td>\n<\/tr>\n
        91<\/td>\nTable 51 \u2013 Event service parameters
        Table 52 \u2013 Activate\/Deactivate measurement service parameters <\/td>\n<\/tr>\n
        92<\/td>\n6.5.7 General purpose command server ASE
        Table 53 \u2013 Get log data service parameters <\/td>\n<\/tr>\n
        95<\/td>\n6.5.8 AR ASE
        Table 54 \u2013 Send command service parameters <\/td>\n<\/tr>\n
        96<\/td>\nFigure 11 \u2013 AR ASE internal architecture <\/td>\n<\/tr>\n
        98<\/td>\nTable 55 \u2013 CT send service parameters <\/td>\n<\/tr>\n
        100<\/td>\nTable 56 \u2013 MT send service parameters <\/td>\n<\/tr>\n
        101<\/td>\nTable 57 \u2013 CS send service parameters <\/td>\n<\/tr>\n
        102<\/td>\nTable 58 \u2013 Notify state change service parameters
        Table 59 \u2013 Control measurement service parameters <\/td>\n<\/tr>\n
        104<\/td>\nFigure 12 \u2013 Structure of IP address
        Table 60 \u2013 DLSAP assignments <\/td>\n<\/tr>\n
        105<\/td>\nTable 61 \u2013 DLS Primitives and parameters <\/td>\n<\/tr>\n
        106<\/td>\n6.5.9 FAL ASE summary
        Table 62 \u2013 Lower layer T-profile and the required standards
        Table 63 \u2013 Summary of FAL ASEs <\/td>\n<\/tr>\n
        109<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

        Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 26 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>\n2019<\/td>\n110<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":244983,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[385,2641],"product_tag":[],"class_list":{"0":"post-244978","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-25-040-40","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\/244978","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\/244983"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=244978"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=244978"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=244978"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}