Search

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

12 result(s) for SafetyProviders

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

5.4 Safety communication layer structure

SafetyConsumer , thus eliminating the necessity for synchronized clocks. When SafetyConsumers connect to SafetyProviders , they have prior expectations regarding the pair of SafetyProviderID and SafetyBaseID (e.g. by configuration). If this expectation ... SafetyConsumer and will provide its process values to any SafetyConsumer requesting it. SafetyProviders can not detect communication errors. All required error detection is performed by the SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.1 General

safe exchange of SPDUs at runtime online browsing, to identify SafetyConsumers and SafetyProviders , and to check their parameters for diagnostic purposes offline engineering: the Information Model of one controller
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.1 SafetyACSet Object

called SafetyACSet with a fixed NodeID in the Namespace of this document. Because all SafetyProviders and SafetyConsumers on this Server contain a hierarchical Reference from this Object to themselves ... used to directly access all SafetyProviders and SafetyConsumers . SafetyACSet is intended for safety-related purposes only. It should not reference non-safety -related items. See Table 3 for the definition
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.5 Object SafetyPDUs

assumed that SafetyAutomationComponent 1 sends a value to the other three SafetyAutomationComponents using three SafetyProviders , each comprising a pair of SPDUs . For each recipient, there is an individual pair
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.6 Objects SafetyProviderParameters and SafetyConsumerParameters

zero via the SAPI parameters ( SafetyProviderID , SafetyBaseID ). The Property SafetyBaseIDConfigured is shared for all SafetyProviders with the same SafetyBaseIDConfigured value. If multiple instances of SafetyObjectsType are running on the same ... viable optimization that a Property SafetyBaseIDConfigured is referenced by either multiple SafetyProviders or SafetyConsumers , or both. For releases up to Release 2.0 of the document, the value for the SafetyStructureSignatureVersion
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

that the SafetyProvider is not properly configured. SafetyConsumers will never try to communicate with SafetyProviders having a SafetyProviderID of 0x0, see Transitions T13/T27 in Table 35 and the macro ... that the SafetyProvider is not properly configured. SafetyConsumers will never try to communicate with SafetyProviders having a SafetyBaseID of 0x0, see Transitions T13/T27 in Table 35 and the macro
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

configured (e.g. its SafetyProviderID is zero). However, SafetyConsumers will never try to communicate with SafetyProviders having incorrect parameters, see Transitions T13 and T27 in Table 35 and the macro
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.1.1 SafetyBaseID and SafetyProviderID

responsibility of the end user or OEM to assign unique SafetyProviderID to individual SafetyProviders whenever this is reasonable possible. For instance, a machine builder should assign unique SafetyProviderIDs within ... level of 4. It is not necessary to generate an individual SafetyBaseIDs for all SafetyProviders . If two SafetyProviders can be discriminated by their SafetyProviderIDs , they may share the same SafetyBaseID
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.4 PFH and PFD values of a logical safety communication link

There is no effect on the PFH and PFD values of the components the SafetyProviders and SafetyConsumers are running on. The requirements for the implementation of these components are specified
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

Requirements for CRC calculation RQ6.1 Singleton SafetyACSet Folder 6.2.2.1 SafetyACSet Object RQ6.2 Objects for SafetyProviders and SafetyConsumers 6.2.2.1 SafetyACSet Object RQ6.3a Usage of Call Service for Client/Server 6.2.2.1 SafetyACSet Object
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.2.3 Safety Multicast

simultaneously. Figure B.3 - Safety multicast Safety multicast is accomplished by placing multiple SafetyProviders on Controller A, and one SafetyConsumer on each of the Controllers B1, B2, … BN. Each ... SafetyProviders running on Controller A is connecting to one of the SafetyConsumers running on one of the Controllers B1, B2, … BN. See Figure B.3 for an example. The safety protocol
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.3 Usage of OPC UA safety Variables in Connections

connection could reference any number of safety and non-safety Variables , even from different SafetyProviders or SafetyConsumers . There is nothing special in establishing a connection containing safety Variables . In fact