{"id":245615,"date":"2024-10-19T16:09:19","date_gmt":"2024-10-19T16:09:19","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61784-3-22017-tc\/"},"modified":"2024-10-25T11:09:53","modified_gmt":"2024-10-25T11:09:53","slug":"bs-en-61784-3-22017-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61784-3-22017-tc\/","title":{"rendered":"BS EN 61784-3-2:2017 – TC"},"content":{"rendered":"
IEC 61784 3-2:2016 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. This third edition cancels and replaces the second edition published in 2010. This edition constitutes a technical revision. The main changes with respect to the previous edition are listed below (and highlighted in yellow in this document): – Added detailed requirements for use of FSCP 2\/1 in conjunction with CP 16\/3 (see 4.1, 6.4.3, 6.5.3, 8.2, 8.13, and miscellaneous references when referencing CPF 2 networks); – Defined object class section keywords for safety to EDS file definition in 8.10.2.1; – New sections on safety CRC overview in 7.1.2.1 and Rollover counts for EF format in 7.4; – Corrections to PFH calculations in 9.5.2; – Change from MACID to NodeID as general reference to network identifier.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
281<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
298<\/td>\n | Figures Figure\u00a01 \u2013 Relationships of IEC\u00a0617843 with other standards (machinery) <\/td>\n<\/tr>\n | ||||||
299<\/td>\n | Figure\u00a02 \u2013 Relationships of IEC\u00a0617843 with other standards (process) <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
303<\/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 | ||||||
308<\/td>\n | 3.1.2 CPF\u00a02: Additional terms and definitions 3.2 Symbols and abbreviated terms 3.2.1 Common symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
309<\/td>\n | 3.2.2 CPF\u00a02: Additional symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | 3.3 Conventions 4 Overview of FSCP\u00a02\/1 (CIP Safety\u2122) 4.1 General 4.2 FSCP\u00a02\/1 <\/td>\n<\/tr>\n | ||||||
311<\/td>\n | 5 General 5.1 External documents providing specifications for the profile Figure\u00a03 \u2013 Relationship of Safety Validators <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | 5.2 Safety functional requirements 5.3 Safety measures <\/td>\n<\/tr>\n | ||||||
313<\/td>\n | 5.4 Safety communication layer structure Tables Table\u00a01 \u2013 Communications errors and detection measures matrix <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | 5.5 Relationships with FAL (and DLL, PhL) 5.5.1 General 5.5.2 Data types 6 Safety communication layer services 6.1 Introduction Figure\u00a04 \u2013 Communication layers <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | 6.2 Connection object 6.2.1 General 6.2.2 Class attribute extensions 6.2.3 Service extensions Table\u00a02 \u2013 New class attributes <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | 6.2.4 Explicit message response format for SafetyOpen and SafetyClose 6.3 Connection Manager object 6.3.1 General Table\u00a03 \u2013 Service extensions Table\u00a04 \u2013 SafetyOpen and SafetyClose response format <\/td>\n<\/tr>\n | ||||||
317<\/td>\n | 6.3.2 ForwardOpen for safety <\/td>\n<\/tr>\n | ||||||
318<\/td>\n | Figure\u00a05 \u2013 ForwardOpen with safety network segment <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | 6.3.3 Safety network segment Table\u00a05 \u2013 Safety network segment identifier Table\u00a06 \u2013 Safety network segment definition <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Figure\u00a06 \u2013 Safety network target format <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | Table\u00a07 \u2013 Safety network segment router format Table\u00a08 \u2013 Safety Network Segment Extended Format <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | 6.3.4 Originator rules for calculating the connection parameter CRC 6.3.5 SafetyOpen processing flowcharts <\/td>\n<\/tr>\n | ||||||
323<\/td>\n | Figure\u00a07 \u2013 Target Processing SafetyOpen with no configuration data(Form 2 SafetyOpen) <\/td>\n<\/tr>\n | ||||||
324<\/td>\n | Figure\u00a08 \u2013 Target Processing for SafetyOpen with configuration data(Form 1 SafetyOpen) <\/td>\n<\/tr>\n | ||||||
325<\/td>\n | 6.3.6 Checks required by Multipoint producers with existing connections Figure\u00a09 \u2013 Originator logic to determine which format to use <\/td>\n<\/tr>\n | ||||||
326<\/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 for safety Table\u00a09 \u2013 Multipoint producer parameter evaluation rules <\/td>\n<\/tr>\n | ||||||
327<\/td>\n | 6.3.10 Safety Validator connection types <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | Table\u00a010 \u2013 ForwardOpen setting options for safety connections <\/td>\n<\/tr>\n | ||||||
330<\/td>\n | 6.3.11 Application reply data in a successful SafetyOpen response Table\u00a011 \u2013 Network connection parameters for safety connections Table\u00a012 \u2013 CP\u00a02\/3 Safety target application reply (size: 10 octets) <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | Table\u00a013 \u2013 EF CP\u00a02\/3 Safety target application reply (size: 14 octets) Table\u00a014 \u2013 SafetyOpen target application reply (size: 18 octets) <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | 6.3.12 Unsuccessful SafetyOpen response Table\u00a015 \u2013 EF SafetyOpen target application reply (size: 22 octets) Table\u00a016 \u2013 New and extended error codes for safety <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Table\u00a017 \u2013 SafetyOpen error event guidance table <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | 6.3.13 ForwardClose for safety 6.4 Identity object 6.4.1 General 6.4.2 Changes to common services <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | 6.4.3 Extensions for CP\u00a016\/3 devices 6.5 Link objects 6.5.1 DeviceNet object changes Table\u00a018 \u2013 Identity object common service changes Table\u00a019 \u2013 Identity object extensions for CP\u00a016\/3 devices Table\u00a020 \u2013 New DeviceNet object instance attribute <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | 6.5.2 TCP\/IP Interface object changes 6.5.3 SERCOS III Link object Table\u00a021 \u2013 New TCP\/IP Interface object instance attribute Table\u00a022 \u2013 SERCOS III Link object class attributes <\/td>\n<\/tr>\n | ||||||
337<\/td>\n | 6.6 Safety Supervisor object 6.6.1 General Table\u00a023 \u2013 SERCOS III Link object instance attributes Table\u00a024 \u2013 SERCOS III Link Object Common Services <\/td>\n<\/tr>\n | ||||||
338<\/td>\n | 6.6.2 Safety Supervisor class attributes 6.6.3 Subclasses 6.6.4 Safety Supervisor instance attributes Table\u00a025 \u2013 Safety Supervisor class attributes <\/td>\n<\/tr>\n | ||||||
339<\/td>\n | Table\u00a026 \u2013 Safety Supervisor instance attributes <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | 6.6.5 Semantics <\/td>\n<\/tr>\n | ||||||
343<\/td>\n | Table\u00a027 \u2013 Device status attribute state values Table\u00a028 \u2013 Exception status attribute format <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | Table\u00a029 \u2013 Common exception detail attribute values <\/td>\n<\/tr>\n | ||||||
345<\/td>\n | Table\u00a030 \u2013 Exception detail format summary <\/td>\n<\/tr>\n | ||||||
347<\/td>\n | Table\u00a031 \u2013 Summary of device behavior for various CFUNID values <\/td>\n<\/tr>\n | ||||||
348<\/td>\n | 6.6.6 Subclasses 6.6.7 Safety Supervisor common services <\/td>\n<\/tr>\n | ||||||
349<\/td>\n | Table\u00a032 \u2013 Safety Supervisor common services Table\u00a033 \u2013 Safety Supervisor object specific services <\/td>\n<\/tr>\n | ||||||
351<\/td>\n | Table\u00a034 \u2013 Configure_Request message structure Table\u00a035 \u2013 Validate_Configuration message structure Table\u00a036 \u2013 Validate_Configuration success message structure <\/td>\n<\/tr>\n | ||||||
352<\/td>\n | Figure\u00a010 \u2013 Applying device configuration Table\u00a037 \u2013 Validate_Configuration error code Table\u00a038 \u2013 Validate_Configuration extended codes <\/td>\n<\/tr>\n | ||||||
353<\/td>\n | Figure\u00a011 \u2013 Configure and Validate processing flowcharts <\/td>\n<\/tr>\n | ||||||
354<\/td>\n | Table\u00a039 \u2013 Set_Password message structure Table\u00a040 \u2013 Reset_Password message structure <\/td>\n<\/tr>\n | ||||||
355<\/td>\n | Table\u00a041 \u2013 Configuration_Lock\/Unlock message structure Table\u00a042 \u2013 Mode_Change message structure <\/td>\n<\/tr>\n | ||||||
356<\/td>\n | Table\u00a043 \u2013 Safety_Reset message structure Table\u00a044 \u2013 Safety Supervisor safety reset types Table\u00a045 \u2013 Attribute bit map parameter <\/td>\n<\/tr>\n | ||||||
357<\/td>\n | Table\u00a046 \u2013 Reset processing rules for reset types Table\u00a047 \u2013 Propose_TUNID service <\/td>\n<\/tr>\n | ||||||
358<\/td>\n | Table\u00a048 \u2013 Apply_TUNID service <\/td>\n<\/tr>\n | ||||||
359<\/td>\n | 6.6.8 Safety Supervisor behavior Figure\u00a012 \u2013 UNID handling during \u201cWaiting for TUNID\u201d <\/td>\n<\/tr>\n | ||||||
360<\/td>\n | Figure\u00a013 \u2013 Safety Supervisor state diagram Table\u00a049 \u2013 Safety Supervisor events <\/td>\n<\/tr>\n | ||||||
361<\/td>\n | Table\u00a050 \u2013 State event matrix for Safety Supervisor <\/td>\n<\/tr>\n | ||||||
364<\/td>\n | Figure\u00a014 \u2013 Configuration, testing and locked relationships Table\u00a051 \u2013 Configuration owner control vs. device state <\/td>\n<\/tr>\n | ||||||
365<\/td>\n | Table\u00a052 \u2013 State mapping of Safety Supervisor to Identity object Table\u00a053 \u2013 Safety Supervisor object event mapping <\/td>\n<\/tr>\n | ||||||
366<\/td>\n | 6.7 Safety Validator object 6.7.1 General 6.7.2 Class attributes Table\u00a054 \u2013 Identity object event mapping <\/td>\n<\/tr>\n | ||||||
367<\/td>\n | 6.7.3 Instance attributes Table\u00a055 \u2013 Safety Validator class attributes Table\u00a056 \u2013 Safety Validator instance attributes <\/td>\n<\/tr>\n | ||||||
369<\/td>\n | Table\u00a057 \u2013 Safety Validator state assignments <\/td>\n<\/tr>\n | ||||||
370<\/td>\n | Figure\u00a015 \u2013 Safety connection types Table\u00a058 \u2013 Safety Validator type, bit field assignments <\/td>\n<\/tr>\n | ||||||
371<\/td>\n | Table\u00a059 \u2013 Multipoint producer SafetyOpen parameter evaluation rules <\/td>\n<\/tr>\n | ||||||
372<\/td>\n | 6.7.4 Class services Table\u00a060 \u2013 Safety Validator class services <\/td>\n<\/tr>\n | ||||||
373<\/td>\n | 6.7.5 Instance services 6.7.6 Object behavior Table\u00a061 \u2013 Safety Validator instance services Table\u00a062 \u2013 Safety Validator Get_Attributes_All service data <\/td>\n<\/tr>\n | ||||||
374<\/td>\n | Figure\u00a016 \u2013 Safety Validator state transition diagram <\/td>\n<\/tr>\n | ||||||
375<\/td>\n | Table\u00a063 \u2013 Safety Validator state event matrix <\/td>\n<\/tr>\n | ||||||
376<\/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\u00a064 \u2013 State mapping between Safety Supervisor and Safety Validator objects Table\u00a065 \u2013 Connection configuration object class attribute extensions Table\u00a066 \u2013 Connection Configuration Object instance attribute additions\/extensions <\/td>\n<\/tr>\n | ||||||
379<\/td>\n | 6.8.4 Instance attribute semantics extensions or restrictions for safety Table\u00a067 \u2013 Connection flag bit definitions <\/td>\n<\/tr>\n | ||||||
380<\/td>\n | Table\u00a068 \u2013 O-to-T connection parameters <\/td>\n<\/tr>\n | ||||||
381<\/td>\n | Table\u00a069 \u2013 T-to-O connection parameters <\/td>\n<\/tr>\n | ||||||
382<\/td>\n | Table\u00a070 \u2013 Data map formats <\/td>\n<\/tr>\n | ||||||
383<\/td>\n | 6.8.5 Special Safety Related Parameters \u2013 (Attribute 13) Table\u00a071 \u2013 Data map format 0 Table\u00a072 \u2013 Data map format 1 <\/td>\n<\/tr>\n | ||||||
385<\/td>\n | Table\u00a073 \u2013 Target device\u2019s SCCRC values Table\u00a074 \u2013 Target device\u2019s SCTS values <\/td>\n<\/tr>\n | ||||||
386<\/td>\n | Table\u00a075 \u2013 Time correction connection parameters for multipoint connection <\/td>\n<\/tr>\n | ||||||
387<\/td>\n | Table\u00a076 \u2013 Format Type attribute meaning <\/td>\n<\/tr>\n | ||||||
388<\/td>\n | Figure\u00a017 \u2013 Logic for Auto-detecting format type Table\u00a077 \u2013 Format Status attribute meaning <\/td>\n<\/tr>\n | ||||||
389<\/td>\n | 6.8.6 Object-specific services 6.8.7 Common service extensions for safety Table\u00a078 \u2013 Connection Configuration Object-specific services Table\u00a079 \u2013 Get_Attributes_All Response service data (added attributes ) <\/td>\n<\/tr>\n | ||||||
390<\/td>\n | Table\u00a080 \u2013 Get_Attributes_All Response service data (added parameters ) Table\u00a081 \u2013 Set_Attributes_All Request service data (added attributes) Table\u00a082 \u2013 Set_Attributes_All Response service data (added parameters ) <\/td>\n<\/tr>\n | ||||||
391<\/td>\n | 6.8.8 Object behavior Figure\u00a018 \u2013 Connection Configuration Object state diagram Table\u00a083 \u2013 State Mapping between Safety Supervisor and the CCO objects <\/td>\n<\/tr>\n | ||||||
392<\/td>\n | 7 Safety communication layer protocol 7.1 Safety PDU format 7.1.1 Safety PDU encoding Figure\u00a019 \u2013 Connection Configuration Object data flow <\/td>\n<\/tr>\n | ||||||
393<\/td>\n | Figure 20 \u2013 Format of the mode octet Table\u00a084 \u2013 Connection sections and PDU formats <\/td>\n<\/tr>\n | ||||||
394<\/td>\n | Figure\u00a021 \u2013 1 or 2 octet data section, Base Format Table\u00a085 \u2013 Mode octet variables <\/td>\n<\/tr>\n | ||||||
395<\/td>\n | Figure\u00a022 \u2013 1 or 2 octet data section, Extended Format Figure\u00a023 \u2013 3 to 250 octet data section format, Base Format <\/td>\n<\/tr>\n | ||||||
396<\/td>\n | Figure\u00a024 \u2013 3 to 250 octet data section format, Extended Format <\/td>\n<\/tr>\n | ||||||
397<\/td>\n | Figure\u00a025 \u2013 Time Stamp section format, Base Format Table\u00a086 \u2013 Time Stamp variables <\/td>\n<\/tr>\n | ||||||
398<\/td>\n | Figure\u00a026 \u2013 BF Time Coordination message encoding Figure\u00a027 \u2013 EF Time Coordination message encoding Table\u00a087 \u2013 Time Coordination message variables <\/td>\n<\/tr>\n | ||||||
399<\/td>\n | Figure\u00a028 \u2013 BF Time Correction message encoding Figure\u00a029 \u2013 EF Time Correction message encoding <\/td>\n<\/tr>\n | ||||||
400<\/td>\n | Table\u00a088 \u2013 Time Correction Message variables <\/td>\n<\/tr>\n | ||||||
401<\/td>\n | Figure\u00a030 \u2013 1 or 2 octet point-to-point PDU encoding Figure\u00a031 \u2013 1 or 2 Octet multipoint PDU encoding <\/td>\n<\/tr>\n | ||||||
402<\/td>\n | Figure\u00a032 \u2013 1 or 2 Octet, multipoint, Format 2 safety connection format Figure\u00a033 \u2013 3 to 250 Octet Point-to-point PDU encoding <\/td>\n<\/tr>\n | ||||||
403<\/td>\n | Figure\u00a034 \u2013 3 to 248 Octet Multipoint PDU encoding Figure\u00a035 \u2013 3 to 248 Octet, Multipoint, safety connection format <\/td>\n<\/tr>\n | ||||||
404<\/td>\n | 7.1.2 Safety CRC Figure\u00a036 \u2013 CRC Calculation order for Extended Format messages Table\u00a089 \u2013 CRC polynomials used <\/td>\n<\/tr>\n | ||||||
405<\/td>\n | 7.2 Communication protocol behavior 7.2.1 Sequence of safety checks 7.2.2 Connection termination 7.2.3 Cross checking error Table\u00a090 \u2013 Connection sections and message formats <\/td>\n<\/tr>\n | ||||||
406<\/td>\n | 7.3 Time stamp operation Figure\u00a037 \u2013 Time stamp sequence <\/td>\n<\/tr>\n | ||||||
407<\/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\u00a038 \u2013 Sequence diagram of a normal producer\/consumer safety sequence <\/td>\n<\/tr>\n | ||||||
408<\/td>\n | 7.5.3 Lost, corrupted and delayed message transmission Figure\u00a039 \u2013 Sequence diagram of a normal producer\/consumersafety sequence (production repeated) <\/td>\n<\/tr>\n | ||||||
409<\/td>\n | Figure\u00a040 \u2013 Sequence diagram of a corrupted producer to consumer message <\/td>\n<\/tr>\n | ||||||
410<\/td>\n | Figure\u00a041 \u2013 Sequence diagram of a lost producer to consumer message <\/td>\n<\/tr>\n | ||||||
411<\/td>\n | 7.5.4 Lost, corrupted or delayed message transmission with production repeated Figure\u00a042 \u2013 Sequence diagram of a delayed message <\/td>\n<\/tr>\n | ||||||
412<\/td>\n | Figure\u00a043 \u2013 Sequence diagram of a corrupted producer to consumer message with production repeated <\/td>\n<\/tr>\n | ||||||
413<\/td>\n | 7.5.5 Point-to-point ping Figure\u00a044 \u2013 Sequence diagram of a connection terminated due to delays Figure\u00a045 \u2013 Sequence diagram of a failure of safety CRC check <\/td>\n<\/tr>\n | ||||||
414<\/td>\n | 7.5.6 Multipoint ping on CP\u00a02\/3 Safety Figure\u00a046 \u2013 Sequence diagram of a point-to-point ping \u2013 normal response <\/td>\n<\/tr>\n | ||||||
415<\/td>\n | 7.5.7 Multipoint ping on CP\u00a02\/2 safety networks Figure\u00a047 \u2013 Sequence diagram of a successful multipoint ping, CP\u00a02\/3 safety <\/td>\n<\/tr>\n | ||||||
416<\/td>\n | 7.5.8 Multipoint ping \u2013 retry with success Figure\u00a048 \u2013 Sequence diagram of a successful multipoint ping, CP\u00a02\/2 safety <\/td>\n<\/tr>\n | ||||||
417<\/td>\n | 7.5.9 Multipoint ping \u2013 retry with timeout Figure\u00a049 \u2013 Sequence diagram of a multipoint ping retry Figure\u00a050 \u2013 Sequence diagram of a multipoint ping timeout <\/td>\n<\/tr>\n | ||||||
418<\/td>\n | 7.6 Safety protocol definition 7.6.1 General 7.6.2 High level view of a safety device 7.6.3 Safety Validator object Figure\u00a051 \u2013 Safety device reference model entity relation diagram <\/td>\n<\/tr>\n | ||||||
419<\/td>\n | 7.6.4 Relationship between SafetyValidatorServer and SafetyValidatorClient 7.6.5 Extended Format time stamp rollover handling Figure\u00a052 \u2013 Two devices interchanging safety data via a SafetyValidatorClient and a SafetyValidatorServer <\/td>\n<\/tr>\n | ||||||
421<\/td>\n | Figure\u00a053 \u2013 Point-to-point, originating consumer. target producer <\/td>\n<\/tr>\n | ||||||
422<\/td>\n | Figure\u00a054 \u2013 Point-to-point, originator producer, target consumer <\/td>\n<\/tr>\n | ||||||
423<\/td>\n | Figure\u00a055 \u2013 Multi-point, originator consumer, target producer <\/td>\n<\/tr>\n | ||||||
424<\/td>\n | 7.6.6 SafetyValidatorClient function definition Figure\u00a056 \u2013 Safety production data flow <\/td>\n<\/tr>\n | ||||||
432<\/td>\n | 7.6.7 SafetyValidatorServer function definition <\/td>\n<\/tr>\n | ||||||
433<\/td>\n | Figure\u00a057 \u2013 Consumer safety data monitoring <\/td>\n<\/tr>\n | ||||||
434<\/td>\n | Figure\u00a058 \u2013 SafetyValidatorServer \u2013 application triggered <\/td>\n<\/tr>\n | ||||||
435<\/td>\n | Table\u00a091 \u2013 Data reception \u2013 Link triggered Table\u00a092 \u2013 Time_Correction reception \u2013 Link triggered Table\u00a093 \u2013 Data reception \u2013 Application triggered <\/td>\n<\/tr>\n | ||||||
436<\/td>\n | Table\u00a094 \u2013 Time_Correction reception \u2013 Application triggered Table\u00a095 \u2013 Consuming application \u2013 Safety data monitoring <\/td>\n<\/tr>\n | ||||||
445<\/td>\n | 7.7 Safety message and protocol data specifications 7.7.1 Mode octet <\/td>\n<\/tr>\n | ||||||
446<\/td>\n | 7.7.2 Time Stamp Section 7.7.3 Time Coordination Message <\/td>\n<\/tr>\n | ||||||
447<\/td>\n | 7.7.4 Time correction message 7.7.5 Safety data production <\/td>\n<\/tr>\n | ||||||
448<\/td>\n | Table\u00a096 \u2013 Producer connection status determination <\/td>\n<\/tr>\n | ||||||
455<\/td>\n | 7.7.6 Producer dynamic variables <\/td>\n<\/tr>\n | ||||||
457<\/td>\n | 7.7.7 Producer per consumer dynamic variables <\/td>\n<\/tr>\n | ||||||
458<\/td>\n | 7.7.8 Consumer data variables <\/td>\n<\/tr>\n | ||||||
459<\/td>\n | Table\u00a097 \u2013 Consuming safety connection status <\/td>\n<\/tr>\n | ||||||
460<\/td>\n | 7.7.9 Consumer input static variables <\/td>\n<\/tr>\n | ||||||
461<\/td>\n | 7.7.10 Consumer dynamic variables <\/td>\n<\/tr>\n | ||||||
463<\/td>\n | 8 Safety communication layer management 8.1 Overview 8.2 Definition of the measures used during connection establishment Table\u00a098 \u2013 Connection establishment errors and measures to detect errors <\/td>\n<\/tr>\n | ||||||
464<\/td>\n | Table\u00a099 \u2013 SNN Date\/Time allocations Table\u00a0100 \u2013 SNN legal range of time values <\/td>\n<\/tr>\n | ||||||
467<\/td>\n | 8.3 Originator-Target relationship validation 8.4 Detection of mis-routed connection requests Figure\u00a059 \u2013 Target ownership <\/td>\n<\/tr>\n | ||||||
468<\/td>\n | 8.5 SafetyOpen processing 8.6 Ownership management Figure\u00a060 \u2013 SafetyOpen forms <\/td>\n<\/tr>\n | ||||||
469<\/td>\n | 8.7 Bridging different physical layers Figure\u00a061 \u2013 Connection ownership state chart Figure\u00a062 \u2013 SafetyOpen UNID mapping <\/td>\n<\/tr>\n | ||||||
470<\/td>\n | Figure\u00a063 \u2013 Common CPF\u00a02 application layer Figure\u00a064 \u2013 End-to-End routing example <\/td>\n<\/tr>\n | ||||||
471<\/td>\n | 8.8 Safety connection establishment 8.8.1 Overview 8.8.2 Basic facts for connection establishment 8.8.3 Configuring safety connections <\/td>\n<\/tr>\n | ||||||
472<\/td>\n | Table\u00a0101 \u2013 Safety connection parameters <\/td>\n<\/tr>\n | ||||||
473<\/td>\n | 8.8.4 Network time expectation multiplier Figure\u00a065 \u2013 Sources for safety related connection parameters <\/td>\n<\/tr>\n | ||||||
474<\/td>\n | 8.8.5 Establishing connections Figure\u00a066 \u2013 Parameter mapping between originator and target <\/td>\n<\/tr>\n | ||||||
475<\/td>\n | Table\u00a0102 \u2013 SafetyOpen summary <\/td>\n<\/tr>\n | ||||||
476<\/td>\n | Figure\u00a067 \u2013 CP\u00a02\/3 Safety connection establishment in targets for Form 2a SafetyOpen <\/td>\n<\/tr>\n | ||||||
477<\/td>\n | 8.8.6 Recommendations for consumer number allocation Figure\u00a068 \u2013 General sequence to detect configuration is required <\/td>\n<\/tr>\n | ||||||
478<\/td>\n | 8.8.7 Recommendations for connection establishment 8.8.8 Ownership establishment <\/td>\n<\/tr>\n | ||||||
479<\/td>\n | 8.8.9 Ownership use cases <\/td>\n<\/tr>\n | ||||||
482<\/td>\n | 8.8.10 PID\/CID usage and establishment 8.8.11 Proper PID\/CID usage in multipoint and point-to-point connections Figure\u00a069 \u2013 PID\/CID exchanges for two originator scenarios <\/td>\n<\/tr>\n | ||||||
483<\/td>\n | Figure\u00a070 \u2013 Seed generation for multipoint connections <\/td>\n<\/tr>\n | ||||||
484<\/td>\n | 8.8.12 Network supported services Figure\u00a071 \u2013 PID\/CID runtime handling <\/td>\n<\/tr>\n | ||||||
485<\/td>\n | 8.8.13 FSCP\u00a02\/1 safety device type <\/td>\n<\/tr>\n | ||||||
486<\/td>\n | Table\u00a0103 \u2013 Originator\/Target service mapping Table\u00a0104 \u2013 Unsupported originator\/target service types <\/td>\n<\/tr>\n | ||||||
487<\/td>\n | Figure\u00a072 \u2013 Connection categories and supported services <\/td>\n<\/tr>\n | ||||||
488<\/td>\n | Figure\u00a073 \u2013 Recommended connection types Figure\u00a074 \u2013 Logic-to-logic supported services <\/td>\n<\/tr>\n | ||||||
489<\/td>\n | 8.9 Safety configuration process 8.9.1 Introduction to safety configuration 8.9.2 Configuration goals Figure\u00a075 \u2013 Recommended connection types for logic to logic <\/td>\n<\/tr>\n | ||||||
490<\/td>\n | 8.9.3 Configuration overview Figure\u00a076 \u2013 Configuration data transfers Table\u00a0105 \u2013 Configuration goals <\/td>\n<\/tr>\n | ||||||
491<\/td>\n | 8.9.4 User configuration guidelines <\/td>\n<\/tr>\n | ||||||
492<\/td>\n | 8.9.5 Configuration process SIL3 justification Figure\u00a077 \u2013 Protection measures in safety devices <\/td>\n<\/tr>\n | ||||||
493<\/td>\n | 8.9.6 Device functions for tool configuration 8.9.7 Password security 8.9.8 SNCT interface services 8.9.9 Configuration lock <\/td>\n<\/tr>\n | ||||||
494<\/td>\n | 8.9.10 Effect of configuration lock on device behavior Figure\u00a078 \u2013 Configuration, testing and locked relationships <\/td>\n<\/tr>\n | ||||||
495<\/td>\n | 8.9.11 Configuration ownership 8.9.12 Configuration mode 8.9.13 Measures used to ensure integrity of configuration process Table\u00a0106 \u2013 Configuration owner control vs. device state <\/td>\n<\/tr>\n | ||||||
496<\/td>\n | Figure\u00a079 \u2013 Originator’s configuration data <\/td>\n<\/tr>\n | ||||||
497<\/td>\n | 8.9.14 Download process <\/td>\n<\/tr>\n | ||||||
498<\/td>\n | Figure\u00a080 \u2013 SNCT to device download process <\/td>\n<\/tr>\n | ||||||
499<\/td>\n | Figure\u00a081 \u2013 SNCT Downloads to originators that perform Form 1 configuration <\/td>\n<\/tr>\n | ||||||
500<\/td>\n | 8.9.15 Verification process <\/td>\n<\/tr>\n | ||||||
501<\/td>\n | Figure\u00a082 \u2013 Protection from locking and ownership Figure\u00a083 \u2013 Example of read back and comparison of original and printout <\/td>\n<\/tr>\n | ||||||
502<\/td>\n | 8.9.16 Verification process Figure\u00a084 \u2013 Diverse display without full data read back <\/td>\n<\/tr>\n | ||||||
503<\/td>\n | 8.9.17 Configuration error analysis Figure\u00a085 \u2013 Verification process including all alternatives <\/td>\n<\/tr>\n | ||||||
504<\/td>\n | Table\u00a0107 \u2013 Errors and detection measures <\/td>\n<\/tr>\n | ||||||
507<\/td>\n | 8.10 Electronic Data Sheets extensions for safety 8.10.1 General rules for EDS based safety devices <\/td>\n<\/tr>\n | ||||||
508<\/td>\n | 8.10.2 EDS extensions for safety Table\u00a0108 \u2013 Object Class section keywords <\/td>\n<\/tr>\n | ||||||
509<\/td>\n | Table\u00a0109 \u2013 Safety Classx entry format Table\u00a0110 \u2013 Parameter class keywords <\/td>\n<\/tr>\n | ||||||
510<\/td>\n | Table\u00a0111 \u2013 New Connection Manager section keywords for safety <\/td>\n<\/tr>\n | ||||||
511<\/td>\n | Table\u00a0112 \u2013 Connection Manager field usage for safety <\/td>\n<\/tr>\n | ||||||
512<\/td>\n | Table\u00a0113 \u2013 Connection parameter field settings for safety <\/td>\n<\/tr>\n | ||||||
513<\/td>\n | 8.11 Requirements for CP\u00a02\/2 8.11.1 EPI rules for safety messages that travel over CP\u00a02\/2 8.11.2 Default safety I\/O service 8.11.3 Duplicate IP detection 8.11.4 Priority for safety connections <\/td>\n<\/tr>\n | ||||||
514<\/td>\n | 8.12 Requirements for CP\u00a02\/3 8.12.1 Allocation of CP\u00a02\/3 identifiers Table\u00a0114 \u2013 CP\u00a02\/3 ID assignment rules <\/td>\n<\/tr>\n | ||||||
516<\/td>\n | 8.12.2 Additional requirements 8.13 CP\u00a016\/3 requirements 8.13.1 General architecture for CPF\u00a02 on CP\u00a016\/3 <\/td>\n<\/tr>\n | ||||||
517<\/td>\n | 8.13.2 Baseline FSCP\u00a02\/1 on CP\u00a016\/3 device Figure\u00a086 \u2013 Baseline FSCP\u00a02\/1 on CP\u00a016\/3 device <\/td>\n<\/tr>\n | ||||||
518<\/td>\n | 8.13.3 Supported objects and services in CP\u00a016\/3 devices 8.13.4 Transport layer requirements <\/td>\n<\/tr>\n | ||||||
520<\/td>\n | Figure\u00a087 \u2013 FSCP\u00a02\/1 Adaptation Layer and SMP interaction <\/td>\n<\/tr>\n | ||||||
521<\/td>\n | 8.13.5 FSCP\u00a02\/1 and the CP\u00a016\/3 device model Figure\u00a088 \u2013 FSCP\u00a02\/1 Adaptation <\/td>\n<\/tr>\n | ||||||
522<\/td>\n | 8.13.6 UNID assignment on CP\u00a016\/3 Figure\u00a089 \u2013 CP\u00a016\/3 device model <\/td>\n<\/tr>\n | ||||||
524<\/td>\n | Figure\u00a090 \u2013 Adding a standard module to a modular device <\/td>\n<\/tr>\n | ||||||
525<\/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\u00a0115 \u2013 LED indications for setting UNID <\/td>\n<\/tr>\n | ||||||
526<\/td>\n | 9.1.4 Indicator warning 9.1.5 Network Status LED Table\u00a0116 \u2013 Module Status LED Table\u00a0117 \u2013 Network status LED states <\/td>\n<\/tr>\n | ||||||
527<\/td>\n | 9.1.6 Switches <\/td>\n<\/tr>\n | ||||||
529<\/td>\n | 9.2 Installation guidelines Figure\u00a091 \u2013 Safety device NodeID processing logic <\/td>\n<\/tr>\n | ||||||
530<\/td>\n | 9.3 Safety function response time 9.3.1 Overview 9.3.2 Network time expectation Figure\u00a092 \u2013 Safety function response time <\/td>\n<\/tr>\n | ||||||
531<\/td>\n | 9.3.3 Equations for calculating network reaction times Table\u00a0118 \u2013 Connection reaction time type \u2013 producing\/consuming applications <\/td>\n<\/tr>\n | ||||||
532<\/td>\n | Figure\u00a093 \u2013 Safety function response time components <\/td>\n<\/tr>\n | ||||||
533<\/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 Figure\u00a094 \u2013 Network protocol reliability block diagram (RBD) <\/td>\n<\/tr>\n | ||||||
535<\/td>\n | Figure\u00a095 \u2013 Network PFH summary <\/td>\n<\/tr>\n | ||||||
536<\/td>\n | 9.5.3 Bit Error Rate (BER) Figure\u00a096 \u2013 Extended Format PFH summary <\/td>\n<\/tr>\n | ||||||
537<\/td>\n | 9.6 Maintenance 9.7 Safety manual 10 Assessment <\/td>\n<\/tr>\n | ||||||
538<\/td>\n | Annex A (informative) Additional information for functional safety communication profiles of CPF 2 A.1 Hash function example code <\/td>\n<\/tr>\n | ||||||
552<\/td>\n | A.2 \u2026 <\/td>\n<\/tr>\n | ||||||
553<\/td>\n | Annex B (informative) Information for assessment of the functional safety communication profiles of CPF 2 <\/td>\n<\/tr>\n | ||||||
554<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Industrial communication networks. Profiles – Functional safety fieldbuses. Additional specifications for CPF 2<\/b><\/p>\n |