Search

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

55 result(s) for SafetyConsumer

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

3.1.2.11 SafetyConsumer

SafetyConsumer entity (usually software) that implements the data sink of a unidirectional safety link
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

4.3 Features

necessary (no requirements regarding the accuracy between clocks at different nodes). Within the SafetyConsumer , a safety-related, local timer is required for implementing the SafetyConsumerTimeout . The accuracy of this timer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.3 Safety measures

document, the following safety measures shall be implemented: MonitoringNumber ; timeout with receipt in the SafetyConsumer ; set of IDs for the SafetyProvider ; Data Integrity check. Together, these safety measures address ... data integrity assurance" of IEC 61784‑3, based on CRC signature. The SafetyConsumer is specified in such a way that for any communication error according to Table
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.4 Safety communication layer structure

safety applications in the User Layer are either directly connected to the SafetyProvider or SafetyConsumer , or they are connected via a machine-specific or process-specific interface, which is described ... within the scope of this document. It defines the two services SafetyProvider and SafetyConsumer as basic building blocks. Together, they form the safety communication layer ( SCL ), implemented in a safety
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.5 Requirements for CRC calculation

with all values (incl. CRC signature) being zero shall be ignored by the receiver ( SafetyConsumer and SafetyProvider ). For Client/Server communication, this means that a Method Call with all fields making
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

SafetyProvider it implements, and one OPC UA Object derived from DataType SafetyConsumerType for each SafetyConsumer it implements. The corresponding Information Models shown in Figure 3 and Figure 4 shall ... found in OPC UA 10000-3. Figure 3 describes the SafetyProvider and the SafetyConsumer . NOTE 1 This document assumes (atomic) consistent data exchange between OPC mappers of the two endpoints
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

safety application that this Method is not concurrently called by multiple SafetyConsumers . Otherwise, the SafetyConsumer can receive invalid responses resulting in a safe reaction which can lead to either spurious ... DataTypeID ) is expected to be the same in both the SafetyProvider and the SafetyConsumer . Otherwise, the SafetyConsumer will not accept the transferred data and switch to fail-safe substitute values
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.5 Object SafetyPDUs

Both variables in the SafetyPDUsType have a counterpart within the Information Model of the SafetyConsumer . The SafetyConsumer publishes the RequestSPDU and subscribes to the ResponseSPDU . Table 11 - SafetyPDUsType definition Attribute
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.6 Objects SafetyProviderParameters and SafetyConsumerParameters

SafetyProviderParameters and SafetyConsumerParameters Figure 6 shows the safety parameters for the SafetyProvider and the SafetyConsumer . Figure 6 - Safety parameters for the SafetyProvider and the SafetyConsumer Table 12 shows the definition ... Refer to 6.3.4.4 for more details on the Safety Parameter Interface ( SPI ) of the SafetyConsumer . Table 13 - SafetyConsumerParametersType definition Attribute Value BrowseName SafetyConsumerParametersType IsAbstract False References Node class BrowseName DataType
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.1 InFlagsType

reserved for future use and shall be set to zero by the SafetyConsumer . They shall not be evaluated by the SafetyProvider . The InFlagsType representation in the AddressSpace is defined
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.2 OutFlagsType

Description OperatorAckProvider 0 Operator acknowledgment at the provider, hereby forwarded to the SafetyConsumer , see OperatorAckProvider in the SAPI of the SafetyProvider , 6.3.3.2 . ActivateFSV 1 Activation of fail-safe values ... safety application at the SafetyProvider , hereby forwarded to the SafetyConsumer , see ActivateFSV in the SAPI of the SafetyProvider , 6.3.3.2 . TestModeActivated 2 Enabling and disabling of test mode in the SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.1 Overview

commissioning for setting safety parameters such as IDs or the timeout value in the SafetyConsumer . The non-safety related Diagnostic Interface ( DI ) can be accessed at runtime for troubleshooting
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.2 SAPI of SafetyProvider

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 ... EnableTestMode Boolean I By setting this input to "1" the remote SafetyConsumer is informed (by Bit 2 in ResponseSPDU.Flags , see 6.2.3.2 ) that the SafetyData are test data
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

coming from a device with a low SIL will never be accepted when a SafetyConsumer is parameterized to implement a safety function with a high SIL . SafetyStructureSignature UInt32 ... behaviour of the SafetyProvider is suitable to fulfill the watchdog delay of the corresponding SafetyConsumer . SafetyServerImplemented Boolean 0x0 or 0x1 n.a. R This read-only parameter indicates whether the SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.1 General

General Figure 10 shows an overview of the SafetyConsumer interfaces. The Safety Application Program Interface ( SAPI ) is specified in 6.3.4.2 , the Safety Parameter Interface ( SPI ) is specified in 6.3.4.4 . Figure ... SafetyConsumer interfaces
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.2 SAPI of SafetyConsumer

SAPI of SafetyConsumer The SAPI of the SafetyConsumer represents the safety communication layer services of the SafetyConsumer . Table 25 lists all inputs and outputs of the SAPI of the SafetyConsumer ... RQ6.14] Each SafetyConsumer shall implement the SAPI as shown in Table 25 , however, the details are vendor-specific. Table 25 - SAPI of the SafetyConsumer SAPI Term Type I/O Definition SafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.3 Motivation for SAPI Operator Acknowledge (OperatorAckConsumer)

lower than a given threshold, depending on the desired SIL (see 9.3.1 ). Whenever the SafetyConsumer detects a faulty message, it checks whether the assumption is still valid, and switches ... Operator Acknowledge". For this reason, the parameter OperatorAckRequested is delivered by the SafetyConsumer to the safety application. See Clause B.2 for details on operator acknowledgment scenarios. Timeout errors
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.4 SPI of the SafetyConsumer

SafetyConsumer [RQ6.15a] Each SafetyConsumer shall implement the parameters and constants [RQ6.15b] as shown in Table 26 . The parameters (R/W in column "Access ... effective, and a diagnostic message should be shown when appropriate. The SPI of the SafetyConsumer represents the parameters of the safety communication layer management of the SafetyConsumer . The values
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.5 Cyclic and acyclic safety communication

curtain being interrupted. In these applications, cyclic safety communication is established. That means the SafetyConsumer is executed cyclically, and the time between two consecutive executions is safely bounded. The maximum ... time between two executions of the SafetyConsumer will contribute to the safety function response time ( SFRT ). Some safety functions, such as the transfer of safe configuration data at startup
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.4.1 General

communication errors. This document provides two types of diagnostics: Diagnostics messages generated by the SafetyConsumer and provided in a vendor-specific way. The Method ReadSafetyDiagnostics , defined
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.4.2 Diagnostics messages of the SafetyConsumer

Diagnostics messages of the SafetyConsumer [RQ6.17] Every time the macro <Set Diag(SD_IDerrOA, isPermanent)> is executed within the SafetyConsumer , the textual representation shown in Table 28 shall ... Extended error type (String) Error code (offset)1 Classification *) (optional) Mandatory SD_IDerrIgn The SafetyConsumer has discarded a message due to an incorrect ID. 0x01 A Yes SD_IDerrOA
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

General Figure 11 shows the structure of a RequestSPDU which originates at the SafetyConsumer and contains a SafetyConsumerID , a MonitoringNumber ( MNR ), and one octet of ( non-safety -related) Flags ... Platform Interface of the SafetyProvider to the OPC UA Platform Interface of the SafetyConsumer . This is the task of the respective OPC UA mapper , see Figure
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.2 RequestSPDU: SafetyConsumerID

RequestSPDU: SafetyConsumerID Identifier of the SafetyConsumer instance, for diagnostic purposes
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.3 RequestSPDU: MonitoringNumber

RequestSPDU: MonitoringNumber The SafetyConsumer uses the MNR to detect SPDUs with timeliness errors, e.g. such SPDUs which are continuously repeated by an erroneous network element which stores data. A different ... used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only be accepted if its MNR matches the MNR of the corresponding RequestSPDU . The checking for correctness
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.4 RequestSPDU: Flags

RequestSPDU: Flags [RQ7.1] The flags of the SafetyConsumer ( RequestSPDU.Flags ) shall be used as shown
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.5 ResponseSPDU: SafetyData

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 ... order in which this data is processed by the calculation is important. SafetyProvider and SafetyConsumer shall agree upon the number, type and order of application data transmitted in SafetyData
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.6 ResponseSPDU: Flags

zero by the SafetyProvider and shall not be evaluated by the SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.7 ResponseSPDU: SPDU_ID

ResponseSPDU: SPDU_ID This field is used by the SafetyConsumer to check whether the ResponseSPDU is coming from the correct SafetyProvider . For details
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.9 ResponseSPDU: MonitoringNumber

copy of the MonitoringNumber received in the corresponding RequestSPDU . See 7.2.3.1 . NOTE The SafetyConsumer uses the ResponseSPDU.MonitoringNumber to detect SPDUs received with timeliness error, e.g. SPDUs which are continuously repeated ... which stores data. A different MonitoringNumber is used in every RequestSPDU of a given SafetyConsumer , and a ResponseSPDU will only be accepted if its MonitoringNumber matches the MonitoringNumber
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.10 ResponseSPDU: CRC

calculated in the SafetyProvider and how it is checked in the SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.11 ResponseSPDU: NonSafetyData

source. [RQ7.9] When presented to the safety application (e.g. at an output of the SafetyConsumer ), non-safety values shall clearly be indicated as "non-safety" by an appropriate
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.1 General

General The two SCL services SafetyProvider and SafetyConsumer are specified using state diagrams
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram

SafetyProvider and SafetyConsumer 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 ... diagram for requests and responses (Client/Server) [RQ7.10] In the case of Client/Server communication, a SafetyConsumer 's OPC UA Mapper may call a SafetyProvider (either the state machine implementation itself
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.3 Duration of demand

value) that originates in the SafetyProvider 's safety application is being received by a SafetyConsumer and forwarded to the SafetyConsumer 's safety application, i.e. if no SafetyData in a series ... ResponseSPDUs as sent by a SafetyProvider . Due to the cycles of SafetyProvider and SafetyConsumer not being synchronized, a SafetyConsumer can evaluate any one of a given number of ResponseSPDUs
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

vendor-specific. Typically, in a real-time system the task performing the SafetyProvider or SafetyConsumer state machine is executed cyclically (see 6.3.5 ). Whenever the task is woken ... SAPI.SafetyConsumerID:= 0 SAPI.OperatorAckRequested:= 0 RequestSPDU_i:= 0 S1_WaitForRequest // waiting on next RequestSPDU from SafetyConsumer <Get RequestSPDU> S2_PrepareSPDU ResponseSPDU.Flags.ActivateFSV:= SAPI.ActivateFSV ResponseSPDU.Flags.OperatorAckProvider:= SAPI.OperatorAckProvider ResponseSPDU.Flags.TestModeActivated:= SAPI.EnableTestMode <Calc SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

SafetyConsumer state diagram [RQ7.14] Figure 18 shows a simplified representation of the state diagram of the SafetyConsumer . The exact behaviour is described in Table 33 , Table 34 , and Table ... SafetyConsumer shall implement this behaviour. It is not required to literally follow the entries given in the tables, if the externally observable behaviour does not change. To avoid unnecessary spurious
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.5 Signature over the SafetyData Structure (SafetyStructureSignature)

check the number, DataTypes , and order of application data transmitted in SafetyData . If the SafetyConsumer is expecting anything different than what the SafetyProvider actually provides, SafetyStructureSignature will differ, allowing ... SafetyConsumer to enable fail-safe substitute values . In addition, the identifier of the Structure DataType ( SafetyStructureIdentifier ) is also taken into account when calculating SafetyStructureSignature . This ensures that the SafetyProvider
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.6 Calculation of a CRC signature

signature The SafetyProvider calculates the CRC signature ( ResponseSPDU.CRC ) and sends it to the SafetyConsumer as part of the ResponseSPDU . This enables the SafetyConsumer to check the correctness of the ResponseSPDU ... without CRC , 12 octets of SafetyData ). The calculation of ResponseSPDU.CRC ( SafetyProvider ) or CRC_calc ( SafetyConsumer ) is done in reverse order, from bottom to top. In the example shown in Figure
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

8.2 Safety function response time part of communication

safety communication according to this document. SafetyConsumerTimeout: Watchdog timer running in the SafetyConsumer . It is started immediately before a new RequestSPDU is sent (T14 or T28). If the timer runs ... triggered (T18 or T29). ConsumerCycleTime: The maximum time for the cyclic execution of the SafetyConsumer , see 7.2.2.2 . NOTE 1 Formula (1) only addresses the part of the SFRT attributable
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.1.1 SafetyBaseID and SafetyProviderID

SafetyBaseID and SafetyProviderID The pair of SafetyProviderID and SafetyBaseID is used by the SafetyConsumer to check the authenticity of the ResponseSPDU . SafetyProviderID and SafetyBaseID are usually assigned during engineering
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.2 Initialization of the MNR in the SafetyConsumer

Initialization of the MNR in the SafetyConsumer The MNR is used to discriminate messages stemming from the same SafetyProvider and is therefore used to detect timeliness errors such as outdated ... value of the MNR shall be safely stored within non-volatile memory of the SafetyConsumer . After restart, the previously stored MNR is used for initialization
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.3.2 Safety related assumptions (informative)

require manual operator acknowledgment for restart, manual operator acknowledgment is mandatory whenever the SafetyConsumer has detected certain types of errors and indicates this using OperatorAckRequested. Hence, operator acknowledgment is expected
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.4 PFH and PFD values of a logical safety communication link

document depends on the parameter of SafetyErrorIntervalLimit (see Table 26 ) of the link's SafetyConsumer . Whenever the SafetyConsumer detects a mismatch of the SafetyConsumerID , SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.5 Safety manual

week in SIL 4 applications 7 High demand and low demand applications The SafetyConsumer shall be executed cyclically within a shorter time frame than the SafetyConsumerTimeout . 8 Maintenance Specific requirements
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.6 Indicators and displays

Indicators and displays [RQ9.4] The device a SafetyConsumer is running on shall be able to indicate if SAPI.OperatorAckRequested is enabled. This can be done for example by an indicator
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

SafetyProvider RQ6.13b Parameters of SafetyProvider SPI 6.3.3.3 SPI of SafetyProvider RQ6.14 Implementation of SafetyConsumer SAPI 6.3.4.2 SAPI of SafetyConsumer RQ6.15a Implementation of SafetyConsumer SPI 6.3.4.4 SPI of the SafetyConsumer RQ6.15b ... Parameters of SafetyConsumer SPI 6.3.4.4 SPI of the SafetyConsumer RQ6.16 Values for qualifiers 6.3.6 Principle for "application variables with qualifier" RQ6.17 SafetyConsumer diagnostic message texts 6.4.2 Diagnostics messages
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.2.1 Unidirectional communication

Unidirectional communication This is accomplished by placing a SafetyProvider on Controller A and a SafetyConsumer on Controller B. The connection between SafetyProvider and SafetyConsumer can be established and terminated during ... protocol is designed in such a way, that it is necessary for the SafetyConsumer to know the parametrized set of IDs of the SafetyProvider such that it is able
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.2.2 Bidirectional communication

data in both directions, which is accomplished by placing a SafetyProvider and a SafetyConsumer on each controller. Hence, bidirectional communication is realized using two safety connections according to this document
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.2.3 Safety Multicast

multicast Safety multicast is accomplished by placing multiple SafetyProviders on Controller A, and one SafetyConsumer on each of the Controllers B1, B2, … BN. Each of the SafetyProviders running on Controller ... irrelevant from a safety point of view to which SafetyProvider instance a given SafetyConsumer is connected. Thus, all SafetyProvider instances can be parametrized with the same
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.3.1 Explanation

Explanation This document supports operator acknowledgment both on the SafetyProvider side and on the SafetyConsumer side. For this purpose, both the interface of the SafetyProvider and the SafetyConsumer comprise ... parameters on the consumer side via the Boolean outputs OperatorAckRequested and OperatorAckProvider on the SafetyConsumer 's SAPI (see 6.3.4.2 ). Subclauses B.3.2 to B.3.5 show some examples
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.3.2 Use case 1: unidirectional communication and OA on the SafetyConsumer side

B.3.2 Use case 1: unidirectional communication and OA on the SafetyConsumer side Figure B.4 - OA in unidirectional safety communication In the scenario shown in Figure B.4 , operator acknowledgment is done ... SafetyConsumer side, operator acknowledgment on the SafetyProvider side is not possible
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.3.4 Use case 3: bidirectional communication and single, one-sided OA

continue sending process values . This is accomplished by connecting OperatorAckProvider with OperatorAckConsumer at the SafetyConsumer of controller B. Activating operator acknowledgment at controller B is not possible in this scenario
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.1 OPC UA Safety Information Model

exposes: a structured input Variable of DataType RequestSPDUDataType containing safety protocol elements (monitoring number, SafetyConsumer ID, etc.); a structured output Variable of a DataType derived from the ResponseSPDUDataType , containing ... elements (monitoring number, CRC, etc.), and optionally additional non-safety related data. The corresponding SafetyConsumer (representing the sink for safety data) mirrors input and output variables, e.g., the safety application
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.3 Usage of OPC UA safety Variables in Connections

Safety provides an application protocol using safety Variables , which is implemented by the SafetyProvider / SafetyConsumer . The communication layer is completely unaware that safety data is being transported. Any logical connection ... contains the unidirectional safety data exchange between the SafetyProvider on Controller A and the SafetyConsumer on Controller B (CtrBRequest à CtrARequest, CtrAResponse à CtrBResponse) and, in addition, data exchange between
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.11 UAFX Controller Safety Facet

functionality needed for a UAFX Controller to exchange safety-related data. Both SafetyProvider and SafetyConsumer functionality are provided. Table 50 - UAFX Controller Safety Facet Group Conformance Unit / Profile Title Optional ... SafetyProvider Facet SafetyConsumer Facet SafetyProviderPubSubMapper Facet SafetyConsumerPubSubMapper Facet