{"id":374639,"date":"2024-10-20T02:39:36","date_gmt":"2024-10-20T02:39:36","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61784-3-22021\/"},"modified":"2024-10-26T04:38:03","modified_gmt":"2024-10-26T04:38:03","slug":"bs-en-iec-61784-3-22021","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61784-3-22021\/","title":{"rendered":"BS EN IEC 61784-3-2:2021"},"content":{"rendered":"
IEC 61784-3-2:2021 specifies a safety communication layer (services and protocol) based on CPF 2 of IEC 61784 1, IEC 61784 2 and IEC 61158 Type 2. It identifies the principles for functional safety communications defined in IEC 61784 3 that are relevant for this safety communication layer. This safety communication layer is intended for implementation in safety devices only. NOTE 1 It does not cover electrical safety and intrinsic safety aspects. Electrical safety relates to hazards such as electrical shock. Intrinsic safety relates to hazards associated with potentially explosive atmospheres. This document defines mechanisms for the transmission of safety-relevant messages among participants within a distributed network using fieldbus technology in accordance with the requirements of IEC 61508 (all parts) for functional safety. These mechanisms may be used in various industrial applications such as process control, manufacturing automation and machinery. This document provides guidelines for both developers and assessors of compliant devices and systems.<\/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 | ||||||
9<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 0 Introduction 0.1 General Figure 1 \u2013 Relationships of IEC 617843 with other standards (machinery) <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 0.2 Patent declaration Figures Figure 2 \u2013 Relationships of IEC 617843 with other standards (process) <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions 3.1.1 Common terms and definitions <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 3.1.2 CPF 2: Additional terms and definitions <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 3.2 Symbols and abbreviated terms 3.2.1 Common symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 3.2.2 CPF 2: Additional symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 3.3 Conventions 4 Overview of FSCP 2\/1 (CIP Safety\u2122) 4.1 General 4.2 FSCP 2\/1 <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5 General 5.1 External documents providing specifications for the profile Figure 3 \u2013 Relationship of Safety Validators <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 5.2 Safety functional requirements 5.3 Safety measures Tables Table 1 \u2013 Communications errors and detection measures matrix <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.4 Safety communication layer structure 5.5 Relationships with FAL (and DLL, PhL) 5.5.1 General 5.5.2 Data types Figure 4 \u2013 Communication layers <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 6 Safety communication layer services 6.1 General 6.2 Connection object 6.2.1 General 6.2.2 Class attribute extensions Table 2 \u2013 New class attributes <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 6.2.3 Service extensions 6.2.4 Explicit message response format for SafetyOpen and SafetyClose Table 3 \u2013 Service extensions Table 4 \u2013 SafetyOpen and SafetyClose response format <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 6.3 Connection Manager object 6.3.1 General 6.3.2 ForwardOpen for safety <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure 5 \u2013 ForwardOpen with safety network segment <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.3.3 Safety network segment Table 5 \u2013 Safety network segment identifier Table 6 \u2013 Safety network segment definition <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 6 \u2013 Safety network target format <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 7 \u2013 Safety network segment router format Table 8 \u2013 Safety Network Segment Extended Format <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 6.3.4 Originator rules for calculating the connection parameter CRC 6.3.5 SafetyOpen processing flowcharts <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 7 \u2013 Target Processing SafetyOpen with no configuration data(Type 2 SafetyOpen) <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 8 \u2013 Target Processing for SafetyOpen with configuration data(Type 1 SafetyOpen) <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 6.3.6 Checks required by Multipoint producers with existing connections Figure 9 \u2013 Originator logic to determine which format to use <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 6.3.7 Electronic key usage for safety 6.3.8 RPI vs. API in safety connections 6.3.9 Application path construction rules for safety connections Table 9 \u2013 Multipoint producer parameter evaluation rules <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 6.3.10 Safety Validator connection types <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table 10 \u2013 ForwardOpen setting options for safety connections with object-based application paths <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table 11 \u2013 ForwardOpen setting options for safety connections with ANSI Extended symbol segment application path <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 6.3.11 Application reply data in a successful SafetyOpen response Table 12 \u2013 Network connection parameters for safety connections Table 13 \u2013 SafetyOpen target application reply (size: 10 octets) <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 14 \u2013 EF CP 2\/2 or CP 16\/3 SafetyOpen target application reply (size: 14 octets) Table 15 \u2013 BF CP 2\/3 SafetyOpen target application reply (size: 18 octets) <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 6.3.12 Unsuccessful SafetyOpen response Table 16 \u2013 EF CP 2\/3 SafetyOpen target application reply (size: 22 octets) Table 17 \u2013 New and extended error codes for safety <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 18 \u2013 SafetyOpen error event guidance table <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 6.3.13 ForwardClose for safety 6.4 Identity object 6.4.1 General <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 6.4.2 Changes to common services 6.4.3 Extensions for CP 16\/3 devices 6.5 Link objects 6.5.1 DeviceNet object changes Table 19 \u2013 Identity object common service changes Table 20 \u2013 Identity object extensions for CP 16\/3 devices <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 6.5.2 TCP\/IP Interface object changes 6.5.3 SERCOS III Link object Table 21 \u2013 New DeviceNet object instance attribute Table 22 \u2013 New TCP\/IP Interface object instance attribute <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 23 \u2013 SERCOS III Link object class attributes Table 24 \u2013 SERCOS III Link object instance attributes <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 6.6 Safety Supervisor object 6.6.1 General 6.6.2 Safety Supervisor class attributes Table 25 \u2013 SERCOS III Link Object Common Services <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 6.6.3 Subclasses 6.6.4 Safety Supervisor instance attributes Table 26 \u2013 Safety Supervisor class attributes Table 27 \u2013 Safety Supervisor instance attributes <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 6.6.5 Semantics <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 28 \u2013 Device status attribute state values Table 29 \u2013 Exception status attribute format <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 30 \u2013 Common exception detail attribute values <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 31 \u2013 Exception detail format summary <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 32 \u2013 Summary of device behavior for various CFUNID values <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 6.6.6 Subclasses <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 6.6.7 Safety Supervisor common services Table 33 \u2013 Safety Supervisor common services Table 34 \u2013 Safety Supervisor object specific services <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 35 \u2013 Configure_Request message structure <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 36 \u2013 Validate_Configuration message structure Table 37 \u2013 Validate_Configuration success message structure Table 38 \u2013 Validate_Configuration error code Table 39 \u2013 Validate_Configuration extended codes <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 10 \u2013 Applying device configuration <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 11 \u2013 Configure and Validate processing flowcharts <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 40 \u2013 Set_Password message structure Table 41 \u2013 Reset_Password message structure <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 42 \u2013 Configuration_Lock\/Unlock message structure Table 43 \u2013 Mode_Change message structure <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 44 \u2013 Safety_Reset message structure Table 45 \u2013 Safety Supervisor safety reset types Table 46 \u2013 Attribute bit map parameter <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 47 \u2013 Reset processing rules for reset types Table 48 \u2013 Propose_TUNID service <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 49 \u2013 Apply_TUNID service <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure 12 \u2013 UNID handling during “Waiting for TUNID” <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 6.6.8 Safety Supervisor behavior Table 50 \u2013 Propose_TUNID_List service Table 51 \u2013 Apply_TUNID_List service <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 13 \u2013 Safety Supervisor state diagram Table 52 \u2013 Safety Supervisor events <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table 53 \u2013 State event matrix for Safety Supervisor <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Figure 14 \u2013 Configuration, testing and locked relationships Table 54 \u2013 Configuration owner control vs. device state <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 55 \u2013 State mapping of Safety Supervisor to Identity object Table 56 \u2013 Safety Supervisor object event mapping <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 6.7 Safety Validator object 6.7.1 General 6.7.2 Class attributes Table 57 \u2013 Identity object event mapping <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 6.7.3 Instance attributes Table 58 \u2013 Safety Validator class attributes Table 59 \u2013 Safety Validator instance attributes <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 60 \u2013 Safety Validator state assignments Table 61 \u2013 Safety Validator type, bit field assignments <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Figure 15 \u2013 Safety connection types <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table 62 \u2013 Multipoint producer SafetyOpen parameter evaluation rules <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 6.7.4 Class services 6.7.5 Instance services Table 63 \u2013 Safety Validator class services <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 6.7.6 Object behavior Table 64 \u2013 Safety Validator instance services Table 65 \u2013 Safety Validator Get_Attributes_All service data <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure 16 \u2013 Safety Validator state transition diagram <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 66 \u2013 Safety Validator state event matrix <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 6.8 Connection Configuration Object 6.8.1 General 6.8.2 Class attribute extensions 6.8.3 Instance attributes, additions and extensions. Table 67 \u2013 State mapping between Safety Supervisor and Safety Validator objects Table 68 \u2013 Connection configuration object class attribute extensions <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 69 \u2013 Connection Configuration Object instance attribute additions\/extensions <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 6.8.4 Instance attribute semantics extensions or restrictions for safety Table 70 \u2013 Connection flag bit definitions <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table 71 \u2013 O-to-T connection parameters <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table 72 \u2013 T-to-O connection parameters <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table 73 \u2013 Data map formats <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | 6.8.5 Special Safety Related Parameters \u2013 (Attribute 13) Table 74 \u2013 Data map format 0 Table 75 \u2013 Data map format 1 <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Table 76 \u2013 Target device\u2019s SCCRC values <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table 77 \u2013 Target device\u2019s SCTS values Table 78 \u2013 Time correction connection parameters for multipoint connection <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 79 \u2013 Format Type attribute meaning <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Figure 17 \u2013 Logic for Auto-detecting format type Table 80 \u2013 Format Status attribute meaning <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 6.8.6 Object-specific services 6.8.7 Common service extensions for safety Table 81 \u2013 Connection Configuration Object-specific services Table 82 \u2013 Get_Attributes_All Response service data (added attributes) <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table 83 \u2013 Get_Attributes_All Response service data (added parameters) Table 84 \u2013 Set_Attributes_All Request service data (added attributes) <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | 6.8.8 Object behavior Figure 18 \u2013 Connection Configuration Object state diagram Table 85 \u2013 Set_Attributes_All Response service data (added parameters) Table 86 \u2013 State Mapping between Safety Supervisor and the CCO objects <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 7 Safety communication layer protocol 7.1 Safety PDU format 7.1.1 Safety PDU encoding Figure 19 \u2013 Connection Configuration Object data flow <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | Table 87 \u2013 Connection sections and PDU formats Table 88 \u2013 Connection sections and message format <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Figure 20 \u2013 Format of the mode octet Figure 21 \u2013 1 or 2 octet data section, Base Format Table 89 \u2013 Mode octet variables <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Figure 22 \u2013 1 or 2 octet data section, Extended Format Figure 23 \u2013 3 to 250 octet data section format, Base Format <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Figure 24 \u2013 3 to 250 octet data section format, Extended Format <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Figure 25 \u2013 Time Stamp section format, Base Format Table 90 \u2013 Time Stamp variables <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | Figure 26 \u2013 BF Time Coordination message encoding Figure 27 \u2013 EF Time Coordination message encoding Table 91 \u2013 Time Coordination message variables <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Figure 28 \u2013 BF Time Correction message encoding Figure 29 \u2013 EF Time Correction message encoding <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table 92 \u2013 Time Correction Message variables <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | Figure 30 \u2013 1 or 2 octet point-to-point PDU encoding Figure 31 \u2013 1 or 2 Octet multipoint PDU encoding <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Figure 32 \u2013 1 or 2 Octet, multipoint, Format 2 safety connection format Figure 33 \u2013 3 to 250 Octet Point-to-point PDU encoding <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Figure 34 \u2013 3 to 248 Octet Multipoint PDU encoding Figure 35 \u2013 3 to 248 Octet, Multipoint, safety connection format <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | 7.1.2 Safety CRC Figure 36 \u2013 CRC Calculation order for Extended Format messages Table 93 \u2013 CRC polynomials used <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | 7.2 Communication protocol behavior 7.2.1 Sequence of safety checks 7.2.2 Connection termination Table 94 \u2013 CRC usage for connection and configuration <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | 7.2.3 Cross checking error 7.3 Time stamp operation Figure 37 \u2013 Time stamp sequence <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 7.4 Rollover counts in the EF 7.5 Protocol sequence diagrams 7.5.1 General 7.5.2 Normal safety transmission Figure 38 \u2013 Sequence diagram of a normal producer\/consumer safety sequence <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Figure 39 \u2013 Sequence diagram of a normal producer\/consumer safety sequence (production repeated) <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | 7.5.3 Lost, corrupted and delayed message transmission Figure 40 \u2013 Sequence diagram of a corrupted producer to consumer message <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Figure 41 \u2013 Sequence diagram of a lost producer to consumer message <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | 7.5.4 Lost, corrupted or delayed message transmission with production repeated Figure 42 \u2013 Sequence diagram of a delayed message <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure 43 \u2013 Sequence diagram of a corrupted producer to consumer message with production repeated Figure 44 \u2013 Sequence diagram of a connection terminated due to delays <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | 7.5.5 Point-to-point ping Figure 45 \u2013 Sequence diagram of a failure of safety CRC check Figure 46 \u2013 Sequence diagram of a point-to-point ping \u2013 normal response <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | 7.5.6 Multipoint ping on CP 2\/3 Safety <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure 47 \u2013 Sequence diagram of a successful multipoint ping, CP 2\/3 safety <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | 7.5.7 Multipoint ping on CP 2\/2 safety networks 7.5.8 Multipoint ping \u2013 retry with success Figure 48 \u2013 Sequence diagram of a successful multipoint ping, CP 2\/2 safety <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | 7.5.9 Multipoint ping \u2013 retry with timeout Figure 49 \u2013 Sequence diagram of a multipoint ping retry Figure 50 \u2013 Sequence diagram of a multipoint ping timeout <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 7.6 Safety protocol definition 7.6.1 General 7.6.2 High level view of a safety device Figure 51 \u2013 Possible safety architectures for FSCP 2\/1 <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | 7.6.3 Safety Validator object 7.6.4 Relationship between SafetyValidatorServer and SafetyValidatorClient Figure 52 \u2013 Safety device reference model entity relation diagram <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | 7.6.5 Extended Format time stamp rollover handling Figure 53 \u2013 Two devices interchanging safety data via a SafetyValidatorClient and a SafetyValidatorServer <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Figure 54 \u2013 Point-to-point, originating consumer. target producer <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Figure 55 \u2013 Point-to-point, originator producer, target consumer <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Figure 56 \u2013 Multi-point, originator consumer, target producer <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | 7.6.6 SafetyValidatorClient function definition Figure 57 \u2013 Safety production data flow <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 7.6.7 SafetyValidatorServer function definition <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure 58 \u2013 Consumer safety data monitoring <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Figure 59 \u2013 SafetyValidatorServer \u2013 application triggered <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Table 95 \u2013 Data reception \u2013 Link triggered Table 96 \u2013 Time_Correction reception \u2013 Link triggered Table 97 \u2013 Data reception \u2013 Application triggered <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Table 98 \u2013 Time_Correction reception \u2013 Application triggered Table 99 \u2013 Consuming application \u2013 Safety data monitoring <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | 7.7 Safety message and protocol data specifications 7.7.1 Mode octet <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | 7.7.2 Time Stamp Section 7.7.3 Time Coordination Message <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | 7.7.4 Time correction message 7.7.5 Safety data production <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table 100 \u2013 Producer connection status determination <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 7.7.6 Producer dynamic variables <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | 7.7.7 Producer per consumer dynamic variables <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | 7.7.8 Consumer data variables <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Table 101 \u2013 Consuming safety connection status <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | 7.7.9 Consumer input static variables <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | 7.7.10 Consumer dynamic variables <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | 8 Safety communication layer management 8.1 Overview 8.2 Definition of the measures used during connection establishment Table 102 \u2013 Connection establishment errors and measures to detect errors <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Table 103 \u2013 SNN Date\/Time allocations Table 104 \u2013 SNN legal range of time values <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | 8.3 Originator-Target relationship validation Figure 60 \u2013 Target ownership <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | 8.4 Detection of mis-routed connection requests 8.5 SafetyOpen processing 8.6 Ownership management Figure 61 \u2013 SafetyOpen forms <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | 8.7 Bridging different physical layers Figure 62 \u2013 Connection ownership state chart Figure 63 \u2013 SafetyOpen UNID mapping <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Figure 64 \u2013 Common CPF 2 application layer Figure 65 \u2013 End-to-End routing example <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | 8.8 Safety connection establishment 8.8.1 Overview 8.8.2 Basic facts for connection establishment <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | 8.8.3 Configuring safety connections <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | 8.8.4 Network time expectation multiplier Table 105 \u2013 Safety connection parameters <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Figure 66 \u2013 Sources for safety related connection parameters <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | 8.8.5 Establishing connections Figure 67 \u2013 Parameter mapping between originator and target <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Table 106 \u2013 SafetyOpen summary <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Figure 68 \u2013 CP 2\/3 Safety connection establishment in targets for Type 2a SafetyOpen Figure 69 \u2013 General sequence to detect configuration is required <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | 8.8.6 Recommendations for consumer number allocation 8.8.7 Recommendations for connection establishment <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | 8.8.8 Ownership establishment 8.8.9 Ownership use cases <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 8.8.10 PID\/CID usage and establishment <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | 8.8.11 Proper PID\/CID usage in multipoint and point-to-point connections Figure 70 \u2013 PID\/CID exchanges for two originator scenarios <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Figure 71 \u2013 Seed generation for multipoint connections <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | 8.8.12 Network supported services Figure 72 \u2013 PID\/CID runtime handling <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | 8.8.13 FSCP 2\/1 safety device type <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Table 107 \u2013 Originator\/Target service mapping Table 108 \u2013 Unsupported originator\/target service types <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Figure 73 \u2013 Connection categories and supported services <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Figure 74 \u2013 Recommended connection types Figure 75 \u2013 Logic-to-logic supported services <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 8.9 Safety configuration process 8.9.1 Introduction to safety configuration 8.9.2 Configuration goals Figure 76 \u2013 Recommended connection types for logic to logic <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | 8.9.3 Configuration overview Figure 77 \u2013 Configuration data transfers Table 109 \u2013 Configuration goals <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | 8.9.4 User configuration guidelines <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | 8.9.5 Configuration process justification Figure 78 \u2013 Protection measures in safety devices <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | 8.9.6 Device functions for tool configuration 8.9.7 Password security 8.9.8 SNCT interface services <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 8.9.9 Configuration lock 8.9.10 Effect of configuration lock on device behavior <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Figure 79 \u2013 Configuration, testing and locked relationships Table 110 \u2013 Configuration owner control vs. device state <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | 8.9.11 Configuration ownership 8.9.12 Configuration mode 8.9.13 Measures used to ensure integrity of configuration process <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Figure 80 \u2013 Originator’s configuration data <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | 8.9.14 Download process <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Figure 81 \u2013 SNCT to device download process <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | Figure 82 \u2013 SNCT Downloads to originators that perform Type 1 configuration <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | 8.9.15 Verification process <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | Figure 83 \u2013 Protection from locking and ownership <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | 8.9.16 Configuration error analysis Figure 84 \u2013 Verification process including all alternatives <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Table 111 \u2013 Errors and detection measures <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | 8.10 Electronic Data Sheets extensions for safety 8.10.1 General rules for EDS based safety devices <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | 8.10.2 EDS extensions for safety Table 112 \u2013 Object Class section keywords <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Table 113 \u2013 Safety Classx entry format Table 114 \u2013 Parameter class keywords <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | Table 115 \u2013 New Connection Manager section keywords for safety <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | Table 116 \u2013 Connection Manager field usage for safety <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | 8.11 Requirements for CP 2\/2 8.11.1 EPI rules for safety messages that travel over CP 2\/2 8.11.2 Default safety I\/O service Table 117 \u2013 Connection parameter field settings for safety <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | 8.11.3 Duplicate IP detection 8.11.4 Priority for safety connections 8.12 Requirements for CP 2\/3 8.12.1 Allocation of CP 2\/3 identifiers Table 118 \u2013 CP 2\/3 ID assignment rules <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | 8.12.2 Additional requirements 8.13 CP 16\/3 requirements 8.13.1 General architecture for CPF 2 on CP 16\/3 8.13.2 Baseline FSCP 2\/1 on CP 16\/3 device <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | 8.13.3 Supported objects and services in CP 16\/3 devices Figure 85 \u2013 Baseline FSCP 2\/1 on CP 16\/3 device <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | 8.13.4 Transport layer requirements <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | Figure 86 \u2013 FSCP 2\/1 Adaptation Layer and SMP interaction <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 8.13.5 FSCP 2\/1 and the CP 16\/3 device model Figure 87 \u2013 FSCP 2\/1 Adaptation <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | 8.13.6 UNID assignment on CP 16\/3 Figure 88 \u2013 CP 16\/3 device model <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | Figure 89 \u2013 Adding a standard module to a modular device <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | 9 System requirements 9.1 Indicators and switches 9.1.1 General indicator requirements 9.1.2 LED indications for setting the device UNID 9.1.3 Module Status LED Table 119 \u2013 LED indications for setting UNID <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 9.1.4 Indicator warning 9.1.5 Network Status LED Table 120 \u2013 Module Status LED Table 121 \u2013 Network status LED states <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | 9.1.6 Switches <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | 9.2 Installation guidelines Figure 90 \u2013 Safety device NodeID processing logic <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | 9.3 Safety function response time 9.3.1 Overview 9.3.2 Network time expectation Figure 91 \u2013 Safety function response time <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | 9.3.3 Equations for calculating network reaction times Table 122 \u2013 Connection reaction time type \u2013 producing\/consuming applications <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | Figure 92 \u2013 Safety function response time components <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | 9.4 Duration of demands 9.5 Constraints for calculation of system characteristics 9.5.1 Number of nodes 9.5.2 Network PFH of Extended Format Figure 93 \u2013 Network protocol reliability block diagram (RBD) <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | 9.5.3 Bit Error Rate (BER) <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | 9.6 Maintenance 9.7 Safety manual 10 Assessment <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | Annex A (informative) Additional information for functional safety communication profiles of CPF 2 <\/td>\n<\/tr>\n | ||||||
285<\/td>\n | Annex B (informative) Information for assessment of the functional safety communication profiles of CPF 2 <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Profiles – Functional safety fieldbuses. Additional specifications for CPF 2<\/b><\/p>\n |