Search

Scope: Core (OPC-10000-*) All specs

30 result(s) for SafetyData

OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

3.1.2.12 SafetyData

SafetyData application data transmitted across a safety network using a safety protocol Note 1 to entry; The safety communication layer does not ensure the safety of the data itself
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

1 Scope

document describes a safety communication layer (services and a protocol) for the exchange of SafetyData using OPC UA mechanisms. It identifies the principles for functional safety communications defined
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

3.1.1.13 safety PDU

Note 1 to entry: The SPDU may include more than one copy of the SafetyData using differing coding structures and hash functions together with explicit parts of additional protections such
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

4.3 Features

depends on the timing requirements of the safety application. End-to-End Safety: functional SafetyData is transported between two safety endpoint devices across a standard network that is not functionally
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.4 Safety communication layer structure

layer ( SCL ), implemented in a safety-related way according to the IEC 61508 series. SafetyData is transmitted using point-to-point communication (unidirectional). Each unidirectional data flow internally communicates ... SafetyConsumer . If it is necessary for a pair of safety applications to exchange SafetyData in both directions, two pairs of SafetyProviders and SafetyConsumers shall be established, one pair for each
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

ReadSafetyData This Method is mandatory for the Facet SafetyProviderServerMapper . It is used to read SafetyData from the SafetyProvider . It is in the responsibility of the safety application that this Method ... Octet with non-safety -related flags from SafetyConsumer ", see 6.2.3.1 . OutSafetyData " SafetyData ", see 7.2.1.5 . OutFlags "Octet with safety-related flags from SafetyProvider ", see 6.2.3.2 . OutSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.4 ResponseSPDUDataType

define the concrete DataType for the ResponseSPDU (which specifies the concrete DataTypes for SafetyData and NonSafetyData , respectively), proceed as follows: (1) Derive a concrete DataType from the abstract ResponseSPDUDataType ... given order: (a) First, field OutSafetyData with the concrete Structure DataType for the SafetyData (see 7.2.1.5 ). (b) Second, field NonSafetyData with the concrete Structure DataType for the NonSafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.5 DataTypes and length of SafetyData

DataTypes and length of SafetyData This document supports sending of the Built-in and Simple DataTypes specified in OPC UA (see OPC 10000-3 and OPC 10000-6) within SafetyData ... Arrays are currently not supported by this document. The supported maximum length of the SafetyData is vendor-specific but still limited to 1 500 octets. Typical values for the maximum
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.1 Overview

Safety Application Program Interface ( SAPI ) is accessed by the safety application for exchanging SafetyData during runtime. The Safety Parameter Interface ( SPI ) is accessed during commissioning for setting safety parameters such
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.2 SAPI of SafetyProvider

vendor-specific. Table 23 - SAPI of the SafetyProvider SAPI Term Type I/O Definition SafetyData Structure I This input is used to accept the user data which is then transmitted ... SafetyData in the SPDU . NOTE Whenever a new MNR is received from a SafetyConsumer , the state machine of the SafetyProvider will read a new value of the SafetyData from
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

Figure 9 . NOTE 1 It is independent from the generation of the SafetyData at SAPI . NOTE 2 The SafetyProviderLevel is used to distinguish devices of a different ... with a high SIL . SafetyStructureSignature UInt32 0x0 to 0xFFFFFFFF 0x0 R/W Signature of the SafetyData structure, for calculation see 7.2.3.5 . NOTE "0" would not be a valid signature
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.2 SAPI of SafetyConsumer

vendor-specific. Table 25 - SAPI of the SafetyConsumer SAPI Term Type I/O Definition SafetyData Structure O This output either delivers the process values received from the SafetyProvider in the SPDU ... field SafetyData , or FSV . NonSafetyData Structure O This output delivers the non-safety process values (e.g. diagnostic information) which were sent together with safe data, see 7.2.1.11 Enable Boolean
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.4 SPI of the SafetyConsumer

Figure 9 . SafetyStructureSignature UInt32 0x0 to 0xFFFFFFFF 0x0 R/W Signature over the SafetyData structure, see 7.2.3.5 . SafetyStructureSignatureVersion UInt16 0x1 0x1 R/W Version used to calculate SafetyStructureSignature ... parameter is optional. SafetyStructureIdentifier String "" R/W Identifier describing the DataType of the SafetyData , see 7.2.3.5 . For the SafetyConsumer , this parameter is optional. SafetyConsumerTimeout UInt32 0x0 to 0xFFFFFFFF
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.6 Principle for "application variables with qualifier"

each individual value sent within an SPDU . The qualifiers are part of the SafetyData and hence not within the scope of this document. [RQ6.16] However, whenever qualifiers are used
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.4.2 Diagnostics messages of the SafetyConsumer

safe substitute values due to an incorrect ID. Operator acknowledgment is required. Mismatch of SafetyData structure or identifier.3 0x13 B, E Yes SD_IDerrOA The SafetyConsumer has switched to fail
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

shows the structure of a ResponseSPDU which originates at the SafetyProvider and contains the SafetyData (1 to 1 500 octets), an additional 25 octet safety code ( STrailer ) and the NonSafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.5 ResponseSPDU: SafetyData

ResponseSPDU: SafetyData [RQ7.2] SafetyData shall contain the safety-related application data transmitted from the SafetyProvider to the SafetyConsumer . It is comprised of a single or multiple basic OPC UA Variables ... sake of reducing distinctions of cases, SafetyData shall always be a Structure , even if it comprised of only a single basic OPC UA Variable . For the calculation
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.11 ResponseSPDU: NonSafetyData

This structure shall be used to transmit NonSafetyData values (e.g. diagnostic information) together with SafetyData consistently. NonSafetyData is not CRC -protected and can stem from an unsafe source. [RQ7.9] When
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram

Sequence diagram Figure 13 and Figure 14 show sequences of requests and responses with SafetyData for this document using OPC UA Client/Server and PubSub communication mechanisms, respectively. The figures show
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.3 Duration of demand

Duration of demand In case it is necessary to ensure that a given SafetyData (e.g. a safety demand or a command value) that originates in the SafetyProvider 's safety application ... SafetyConsumer and forwarded to the SafetyConsumer 's safety application, i.e. if no SafetyData in a series of SafetyData is to be missed, the following two cases shall be considered
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

SPDU_ID_1_i, SPDU_ID_2_i, SPDU_ID_3_i, Flags, the SafetyData and the NonSafetyData , as well as the calculated CRC . See 7.2.3.1 Table 31 shows
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.1 Build ResponseSPDU

copying RequestSPDU.MonitoringNumber and RequestSPDU.SafetyConsumerID into the ResponseSPDU . In addition, SPDU_ID , Flags , the SafetyData and the NonSafetyData shall be updated. Finally, ResponseSPDU.CRC shall be calculated and appended. Figure 20 gives
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.2 Calculation of the SPDU_ID_1, SPDU_ID_2, SPDU_ID_3

SPDU_ID_3 do not, the structure or identifier of the SafetyData do not match. If SPDU_ID_1 differs, but SPDU_ID_2 and SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.4 Coding of the SafetyProviderLevel_ID

SafetyProvider at all. The SafetyProviderLevel is independent to the SIL capability of the provided SafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.5 Signature over the SafetyData Structure (SafetyStructureSignature)

Signature over the SafetyData Structure (SafetyStructureSignature) SafetyStructureSignature is used to check the number, DataTypes , and order of application data transmitted in SafetyData . If the SafetyConsumer is expecting anything different than ... used. As of now, Structured DataTypes (including OptionSets ) shall not be used within SafetyData . Arrays are not supported. Instead, multiple variables of the same type are used. Enumeration DataTypes
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.6 Calculation of a CRC signature

ResponseSPDU . This enables the SafetyConsumer to check the correctness of the ResponseSPDU including the SafetyData , flags , MNR , SafetyConsumerID and SPDU_ID by recalculating the CRC signature (CRC_calc). [RQ7.22 ... generator polynomial 0xF4ACFB13 shall be used for the 32-Bit CRC signature. [RQ7.23] If SafetyData is longer than one octet (e.g. if it is of DataType UInt16 , Int16 or Float
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.3.2 Safety related assumptions (informative)

storing elements: No restrictions; any number of message storing elements is permitted Size of SafetyData within one ResponseSPDU : ≤ 1 500 octets Even for safety functions that do not require manual
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

NonSafetyDataPlaceHolder 6.2.3.4 ResponseSPDUDataType RQ6.9 Restriction to scalar types 6.2.5 DataTypes and length of SafetyData RQ6.10 List supported DataTypes in user manual 6.2.5 DataTypes and length of SafetyData RQ6.11 Values ... Boolean DataType 6.2.5 DataTypes and length of SafetyData RQ6.12 Implementation of SafetyProvider SAPI 6.3.3.2 SAPI of SafetyProvider RQ6.13a Implementation of SafetyProvider SPI 6.3.3.3 SPI of SafetyProvider RQ6.13b Parameters of SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.2.1 Unidirectional communication

received data is coming from the expected source. On the other hand, as SafetyData flows in one direction only, it is not necessary for the SafetyProvider to check
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.1 Controller-to-Controller communication

future releases of the specification. Exchanged data can be standard process data or SafetyData . Both bidirectional and unidirectional traffic can be used (see OPC 10000-81 ). TSN can provide guaranteed