{"id":422710,"date":"2024-10-20T06:42:32","date_gmt":"2024-10-20T06:42:32","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-6-262019-2\/"},"modified":"2024-10-26T12:34:43","modified_gmt":"2024-10-26T12:34:43","slug":"bs-en-iec-61158-6-262019-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-6-262019-2\/","title":{"rendered":"BS EN IEC 61158-6-26:2019"},"content":{"rendered":"
1.1 General<\/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 behavior provided by the Type 26 of the fieldbus Application Layer in terms of:<\/p>\n
the abstract syntax defining the application layer protocol data units conveyed between communicating application entities;<\/p>\n<\/li>\n
the transfer syntax defining the application layer protocol data units conveyed between communicating application entities;<\/p>\n<\/li>\n
the application context state machine defining the application service behavior visible between communicating application entities; and<\/p>\n<\/li>\n
the application relationship state machines defining the communication behavior visible between communicating application entities.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this document is to define the protocol provided to:<\/p>\n
define the wire-representation of the service primitives defined in IEC 61158-5-26, and<\/p>\n<\/li>\n
define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
This document specifies the protocol of the Type 26 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
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 1 Scope 1.1 General <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and definitions from other ISO\/IEC standards 3.1.1 Terms and definitions from ISO\/IEC 74981 <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 3.1.2 Terms and definitions from ISO\/IEC 8822 3.1.3 Terms and definitions from ISO\/IEC 9545 3.1.4 Terms and definitions from ISO\/IEC 88241 <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 3.1.5 Terms and definitions from ISO\/IEC 88251 3.2 Type 26 specific terms and definitions <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.3 Abbreviations and symbols <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 3.4 Conventions 3.4.1 Conventions used in state machines Tables Table 1 \u2013 Conventions used for state machines Table 2 \u2013 Conventions used in state machine <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 3.4.2 Convention for abstract syntax description 3.4.3 Convention for reserved bits and octets 3.4.4 Conventions for bit description in octets <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4 FAL syntax description 4.1 General Figures Figure 1 \u2013 Bit identification in an octet Figure 2 \u2013 Bit identification in multiple octets (four-octet case) <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 4.2 Overview of Type 26 fieldbus 4.2.1 Application field and Common-memory <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 4.2.2 Structure of Type 26 protocol Figure 3 \u2013 Data sharing with the CM <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 4.2.3 Structure of Type 26 FAL Figure 4 \u2013 Protocol stack for Type 26 fieldbus <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 4.2.4 Data link layer 4.3 Operating principle 4.3.1 Overview Figure 5 \u2013 The structure of ASEs for Type 26 FAL <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.3.2 Logical ring maintenance Figure 6 \u2013 A token circulation on a logical ring <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 7 \u2013 Logical ring recovery <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.3.3 Node addition <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 8 \u2013 An example in case of start simultaneously with another node <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 9 \u2013 Start alone case <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 4.3.4 Node in a logical ring 4.3.5 Node drop-out Figure 10 \u2013 Node addition: in-ring start-up state <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 4.3.6 Data transmission <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 11 \u2013 Data sharing with the CM <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 12 \u2013 Configuration of the Common-memory <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 13 \u2013 APDUs of cyclic-data frames containing fragmented data <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 3 \u2013 Available functions to message-data transfer on UDP channel <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 14 \u2013 Example of sequential diagram of ACK over UDP channel <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 15 \u2013 Delivery confirmation checked by TCP protocol <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 4.3.7 Data transmission frames Figure 16 \u2013 Train of data frames and a token frame <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 17 \u2013 Frame structure Table 4 \u2013 Data transmission frame and the TCD value <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 4.4 FAL PDU abstract syntax 4.4.1 Basic abstract syntax <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 4.4.2 Transparent-msg- PDU 4.4.3 Token-PDU 4.4.4 Participation-req-PDU 4.4.5 Byte-block-read PDUs <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 4.4.6 Byte-block-write PDUs 4.4.7 Word-block-read PDUs 4.4.8 Word-block-write PDUs 4.4.9 Network-parameter-read PDUs <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 4.4.10 Network-parameter-write PDUs 4.4.11 Stop-command PDUs 4.4.12 Operation-command PDUs 4.4.13 Profile-read PDUs <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 4.4.14 Trigger-PDU 4.4.15 Log-data-read PDUs 4.4.16 Log-data-clear PDUs 4.4.17 Message-return PDUs <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 4.4.18 Vendor-specific-msg PDUs 4.4.19 Start-TK-hld-time-mrmt PDUs 4.4.20 Terminate-TK-hld-time-mrmt PDUs <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 4.4.21 Start-GP_Comm-sndr-log PDUs 4.4.22 Terminate-GP_Comm-sndr-log PDUs 4.4.23 Set-remote-node-config-para PDUs 4.4.24 Read-rmt-partici-node-mgt-info-para PDUs <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 4.4.25 Read-rmt- node-mgt-info-para PDUs 4.4.26 Read-rmt-node-set-info-para PDUs 4.4.27 Reset-node PDUs 4.4.28 Cyclic-data PDUs 4.5 Data type assignments <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 5 Transfer syntax 5.1 Encoding rules 5.1.1 Basic encoding 5.1.2 Fixed length Unsigned encoding 5.1.3 Fixed length BitString encoding 5.1.4 OctetString encoding <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 5.1.5 SEQUENCE encoding 5.2 PDU elements encoding 5.2.1 FALARHeader <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 5 \u2013 Upper layer operating condition matrix <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 5.2.2 Transparent-msg PDU <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 5.2.3 Token-PDU Figure 18 \u2013 Structure of Trans-msgData Table 6 \u2013 Transparent-msg-PDU specific values <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 5.2.4 Participation-req-PDU Table 7 \u2013 Token-PDU specific values Table 8 \u2013 Participation-req -PDU specific values <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 5.2.5 Byte-block-read PDUs Table 9 \u2013 Byte-block-read-req-PDU specific values Table 10 \u2013 Byte-block-read-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 5.2.6 Byte-block-write PDUs Figure 19 \u2013 Structure of B_Blk_Rd_rspData with M_RLT = 0 Figure 20 \u2013 Structure of B_Blk_Rd_rspData in case of M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 11 \u2013 Byte-block-write-req-PDU specific values Table 12 \u2013 Byte-block-write-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 5.2.7 Word-block-read PDUs Figure 21 \u2013 Structure of B_Blk_Wt_reqDat Figure 22 \u2013 Structure of B_Blk_Wt_rspData in case of M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 13 \u2013 Word-block-read-req-PDU specific values Table 14 \u2013 Word-block-read-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 5.2.8 Word-block-write PDUs Figure 23 \u2013 Structure of W_Blk_Rd_rspData with M_RLT = 0 Figure 24 \u2013 Structure of W_Blk_Rd_rspData in case of M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 15 \u2013 Word-block-write-req-PDU specific values Table 16 \u2013 Word-block-write-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 5.2.9 Network-parameter-read PDUs Figure 25 \u2013 Structure of W_Blk_Wt_reqDat Figure 26 \u2013 Structure of W_Blk_Wt_rspData in case of M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 17 \u2013 Network-parameter-read-req-PDU specific values Table 18 \u2013 Network-parameter-read-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 27 \u2013 Structure of Net-para-Rd-rspData <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 5.2.10 Network-parameter-write PDUs Figure 28 \u2013 Structure of Net-para-Rd-rspData with M_RLT = 1 Table 19 \u2013 Values of data elements of Net-para-Rd-rspData <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 20 \u2013 Network-parameter-write-req-PDU specific values Table 21 \u2013 Network-parameter-write-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Figure 29 \u2013 Structure of Net-para-Wrt-reqData Table 22 \u2013 Values of the data elements of Net-para-Wrt-reqData <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 5.2.11 Stop-command PDUs Figure 30 \u2013 Structure of Net-para-Wrt-rspData with M_RLT = 1 Table 23 \u2013 Stop-command-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 24 \u2013 Stop-command-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 5.2.12 Operation-command PDUs Figure 31 \u2013 Structure of Stop-cmdData with M_RLT = 1 Table 25 \u2013 Operation-command-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 32 \u2013 Structure of Op-cmdData with M_RLT = 1 Table 26 \u2013 Operation-command-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 5.2.13 Profile-read PDUs Table 27 \u2013 Profile-read-req-PDU specific values Table 28 \u2013 Profile-read-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure 33 \u2013 Structure of Profile-readData with M_RLT = 0 <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 5.2.14 Trigger-PDU Figure 34 \u2013 Structure of Profile-readData with M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 5.2.15 Log-data-read PDUs Table 29 \u2013 Trigger-PDU specific values <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 30 \u2013 Log-data-read-req-PDU U specific values Table 31 \u2013 Log-data-read-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 35 \u2013 Structure of Log-readData with M_RLT = 0 Table 32 \u2013 Contents of Log-readData <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | 5.2.16 Log-data-clear PDUs Figure 36 \u2013 Structure of Log-readData with M_RLT = 1 Table 33 \u2013 Log-data-clear-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 37 \u2013 Structure of Log-clearData Table 34 \u2013 Log-data-clear-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 5.2.17 Message-return PDUs Table 35 \u2013 Message-return-req-PDU specific values Table 36 \u2013 Message-return-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 38 \u2013 Structure of Msg-return-reqData Figure 39 \u2013 Structure of Msg-return-rspData <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 5.2.18 Vendor-specific-msg PDUs Table 37 \u2013 Vendor-specific-msg-req-PDU specific values Table 38 \u2013 Vendor-specific-msg-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Figure 40 \u2013 Structure of V_msg_reqData <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 5.2.19 Start-TK-hld-time-mrmt PDUs Figure 41 \u2013 Structure of V_msg_rspData in case of M_RLT = 0 Figure 42 \u2013 Structure of V_msg_rspData in case of M_RLT = 1 <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 39 \u2013 Start-TK-hld-time-mrmt-req-PDU specific values Table 40 \u2013 Start-TK-hld-time-mrmt-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 5.2.20 Terminate-TK-hld-time-mrmt PDUs Table 41 \u2013 Terminate-TK-hld-time-mrmt-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 42 \u2013 Terminate-TK-hld-time-mrmt-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure 43 \u2013 Token-holding-time measurement result Table 43 \u2013 Value of the data element of TK-hld-timeData <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 5.2.21 Start-GP_Comm-sndr-log PDUs Table 44 \u2013 Start-GP_Comm-sndr-log-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 5.2.22 Terminate-GP_Comm-sndr-log PDUs Table 45 \u2013 Start-GP_Comm-sndr-log-rsp-PDU specific values Table 46 \u2013 Terminate-GP_Comm-sndr-log-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table 47 \u2013 Terminate-GP_Comm-sndr-log-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Figure 44 \u2013 Structure of Sndr-logData Table 48 \u2013 Value of the data element of Sndr-logData <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 5.2.23 Set-remote-node-config-para PDUs Table 49 \u2013 Set-remote-node-config-para-req-PDU specific values Table 50 \u2013 Set-remote-node-config-para-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Figure 45 \u2013 Structure of Set-remote-node-config-para-ReqData Table 51 \u2013 Value of the data element of Set-remote-node-config-para-ReqData <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Figure 46 \u2013 Structure of Set-remote-node-config-para-RspData Table 52 \u2013 Bit definition of Update flag Table 53 \u2013 Value of the data element of Set-remote-node-config-para-RspData <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 5.2.24 Read-rmt-partici-node-mgt-info-para PDUs Table 54 \u2013 Read-rmt-partici-node-mgt-info-para-req-PDU specific values Table 55 \u2013 Read-rmt-partici-node-mgt-info-para-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Figure 47 \u2013 Structure of Read-rmt-partici-node-mgt-info-ReqData Figure 48 \u2013 Structure of Read-rmt-partici-node-mgt-info-RspData <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | 5.2.25 Read-rmt- node-mgt-info-para PDUs Table 56 \u2013 Value of the data element of Read-rmt-partici-node-mgt-info-RspData Table 57 \u2013 Read-rmt- node-mgt-info-para-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 58 \u2013 Read-rmt- node-mgt-info-para-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Figure 49 \u2013 Structure of Rmt-node-mgt-info-paraData Table 59 \u2013 Value of the data element of Rmt-node-mgt-info-paraData <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 5.2.26 Read-rmt-node-set-info-para PDUs Table 60 \u2013 Bit definition of Node status Table 61 \u2013 Read-rmt-node-set-info-para-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Figure 50 \u2013 Structure of Set-info-para-read-data Table 62 \u2013 Read-rmt-node-set-info-para-rsp-PDU specific values <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 5.2.27 Reset-node PDUs Table 63 \u2013 Value of the data element of Set-info-para-read-data Table 64 \u2013 Rest-node-req-PDU specific values <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 5.2.28 Cyclic-data PDUs Table 65 \u2013 Rest-node-rsp-PDU specific values Table 66 \u2013 Cyclic-data-PDU specific values <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Figure 51 \u2013 Structure of ACKdata <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | 6 FAL protocol state machines structure 6.1 Overview Table 67 \u2013 Value of the element of ACKdata Table 68 \u2013 Value of R_STSx field <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | 6.2 Common variables, parameters, timers, counters, lists and queues 6.2.1 V(3CWT), P(3CWT), T(3CWT): Three-lap-time-period-of-the-token-circulation 6.2.2 V(ACK): ACK received 6.2.3 V(ACK_TN): ACK to this node Figure 52 \u2013 Relationship between FAL protocol machines <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 6.2.4 V(AWT), P(AWT), T(AWT): Waiting-time-period-for-receiving-message-acknowledge 6.2.5 V(CBN): Current fragment number for fragmented cyclic-data transmission 6.2.6 V(CTFG): Cyclic-data fragment transfer 6.2.7 V(CTRen), P (CTRen): Cyclic-data receive enable 6.2.8 V(CTRQ): Cyclic-data transfer request 6.2.9 C(MCNT): Cumulative count of message transmission carried over 6.2.10 V(MCV): Message transmission carried over Table 69 \u2013 Value of R_STSx field <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 6.2.11 V(NMTP): No message transmission in previous cycle 6.2.12 V(MFT), P(MFT), T(MFT): Allowable-minimum-frame-Interval-Time 6.2.13 V(MmtCntType): Measurement control type 6.2.14 V(MRVRQ): Message receive request 6.2.15 V(MSRQ): Message transfer request 6.2.16 Q(MSRXQ): Message-RX-Queue <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 6.2.17 Q(MTXQ):Message-TX-Queue 6.2.18 V(PAT), P(PAT), T(PAT): Participation-request-frame-acceptance-time 6.2.19 V(PnMgtIF): Participation-node-management-information List 6.2.20 V(PWT), T(PWT): Participation-request-frame-transmission-waiting-time 6.2.21 V(RCT): Allowable-refresh-cycle-time 6.2.22 V(RMT), T(RMT): Refresh-cycle-measurement-time <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 6.2.23 C(RTX): Retransmission count 6.2.24 V(SEQ): Sequence number value List 6.2.25 V(SN): Successor node 6.2.26 V(SrtMmt): Measurement started 6.2.27 Q(SVRXQ): Server-RX Queue 6.2.28 Q(SVTXQ): Server-TX Queue 6.2.29 V(TBN), P(TBN): Total fragment number of Cyclic-data 6.2.30 V(TDT), P(TDT), T(TDT): Joining-token-detection-time <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 6.2.31 V(THT), P(THT), T(THT): Token-holding-time 6.2.32 V(TK): Token holding 6.2.33 V(TKH): Token holding node 6.2.34 V(TN): Node identifier number 6.2.35 V(TrWT), T(TrWT): Trigger-frame-transmission-waiting-time 6.2.36 V(TSZ), P(TSZ): Total cyclic-data size 6.2.37 V(TW), P(TW ), T(TW)( ): Token-watchdog-time 6.2.38 V(VSEQ): Version of sequence number value List <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | 6.3 Functions used in state tables Table 70 \u2013 Functions used in state tables <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | 7 FAL service protocol machine (FSPM) 7.1 Overview <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | 7.2 Cyclic-data protocol machine 7.2.1 Overview 7.2.2 Cyclic-data primitives between FAL user and FSPM Figure 53 \u2013 Overall structure of FSPM Table 71 \u2013 Cyclic-data primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | 7.2.3 State table Figure 54 \u2013 State transition diagram of Cyclic-data protocol machine Table 72 \u2013 State table of Cyclic-data protocol machine <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 7.3 Message data protocol machine 7.3.1 Overview 7.3.2 Message-data primitive between FAL user and FSPM Table 73 \u2013 Message-data primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | 7.3.3 State table Figure 55 \u2013 State transition diagram of Message-data protocol machine Table 74 \u2013 State table of Message-data protocol machine <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | 7.4 Load measurement protocol machine 7.4.1 Overview 7.4.2 Load measurement primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Table 75 \u2013 Load measurement primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | 7.4.3 State table Figure 56 \u2013 State transition diagram of Load measurement protocol machine Table 76 \u2013 State table of Load measurement protocol machine <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | 7.5 General purpose communication server protocol machine 7.5.1 Overview 7.5.2 GP command server primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | 7.5.3 State table Figure 57 \u2013 State transition diagram of GP-command-server protocol machine Table 77 \u2013 GP command server primitives between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table 78 \u2013 State table of General purpose command server protocol machine <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | 7.6 Network management protocol machine 7.6.1 Overview 7.6.2 Network management primitives Table 79 \u2013 Primitives used in network management protocol machine <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | 7.6.3 State table Figure 58 \u2013 State transition diagram of Network management protocol machine <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Table 80 \u2013 State table of Network management protocol machine <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | 8 Application relationship protocol machine (ARPM) 8.1 Overview <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | 8.2 Cyclic-TX\/RX control 8.2.1 Overview 8.2.2 Cyclic-TX\/RX control primitives between FSPM and ARPM Figure 59 \u2013 Overall structure of ARPM <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | 8.2.3 State table 8.3 Message-TX\/RX control 8.3.1 Overview Figure 60 \u2013 State transition diagram of Cyclic-TX\/RX control Table 81 \u2013 Cyclic-TX\/RX control primitives between FSPM and ARPM Table 82 \u2013 State table of Cyclic-TX\/RX control <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | 8.3.2 Message-TX\/RX control primitives between FSPM and ARPM 8.3.3 State table 8.4 Command server TX\/RX control 8.4.1 Overview Figure 61 \u2013 State transition diagram of Message-TX\/RX control Table 83 \u2013 Message-TX\/RX control primitives between FSPM and ARPM Table 84 \u2013 State table of Message-TX\/RX control <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 8.4.2 Command server TX\/RX primitives between FSPM and ARPM 8.4.3 State table Figure 62 \u2013 State transition diagram of Command server TX\/RX protocol machine Table 85 \u2013 Command server TX\/RX primitives between FSPM and ARPM Table 86 \u2013 State table of Command server TX\/RX protocol machine <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | 8.5 AR control 8.5.1 Overview 8.5.2 AR control primitives between FSPM and ARPM 8.5.3 State table Table 87 \u2013 AR control primitives between FSPM and ARPM <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Figure 63 \u2013 Overall state transition diagram of AR control protocol machine <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Table 88 \u2013 Overall AR control state table <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Figure 64 \u2013 State transition diagram for message-data transmission <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table 89 \u2013 State table for message-data transmission <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Figure 65 \u2013 State transition diagram for ACK creation and message-data reception <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table 90 \u2013 State table for ACK creation and message-data reception <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | 9 DLL mapping protocol machine (DMPM) 9.1 Overview 9.2 Mapping of DMPM service primitives and DLL service primitives Figure 66 \u2013 Overall structure of DMPM <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Table 91 \u2013 Mapping of DMPM primitives and DLL service primitives Table 92 \u2013 Supposed Transport service primitives <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | 9.3 Mapping DMPM service port to DL-SAP Figure 67 \u2013 DL-SAP mapping Table 93 \u2013 Mapping of output and input ports to DL-SAP <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 9.4 Mapping of Network address to each node Figure 68 \u2013 Structure of IP address <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 26 elements<\/b><\/p>\n |