Search

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

14 result(s) for SafetyProviderID

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

3.1.2.15 SafetyProviderID

SafetyProviderID user-assigned, locally unique identifier which is used to safely authenticate SafetyProviders within a certain area Note 1 to entry: Together with the SafetyBaseID, it is an instance
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.4 Safety communication layer structure

clocks. When SafetyConsumers connect to SafetyProviders , they have prior expectations regarding the pair of SafetyProviderID and SafetyBaseID (e.g. by configuration). If this expectation is not fulfilled by the SafetyProvider , fail
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.6 Objects SafetyProviderParameters and SafetyConsumerParameters

PropertyType Mandatory HasProperty Variable SafetyPubSubImplemented Boolean PropertyType Mandatory Conformance units SafetyProviderParameters The parameters for SafetyProviderID and SafetyBaseID exist in pairs for "Configured" and "Active" states: SafetyProviderIDConfigured ... still offline; the values which have been set during runtime via the SAPI parameters ( SafetyProviderID , SafetyBaseID ); the corresponding "[...]Configured" values if the active values have been
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.3.3 SPI of SafetyProvider

Range Initial value (before configuration) Access Note SafetyProviderIDConfigured UInt32 0x0 to 0xFFFFFFFF 0x0 R/W SafetyProviderID of the SafetyProvider that is normally used, see 3.1.2.15 and 9.1.1 . For dynamic systems ... program can overwrite this ID by providing a non-zero value at the input SafetyProviderID of the SafetyProvider 's SAPI . This runtime value can be queried using the SafetyProviderIDActive parameter
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.4 SPI of the SafetyConsumer

value (before configuration) Access Note SafetyProviderIDConfigured UInt32 0x0 to 0xFFFFFFFF 0x0 R/W The default SafetyProviderID of the SafetyProvider this SafetyConsumer uses to make a connection, see Figure ... program can overwrite this ID by providing a non-zero value at the input SafetyProviderID of the SafetyConsumer 's SAPI . This runtime value can be queried using the SafetyProviderIDActive parameter
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 SafetyProviderID . 0x12 B, E Yes SD_IDerrOA The SafetyConsumer has switched to fail-safe substitute values ... vendor-specific): Extend diagnostic data by expected value and received value, e.g.: Mismatch of SafetyProviderID : Expected SafetyProviderID : 0x00000005 Received SafetyProviderID : 0x00000007 Extend diagnostic data if a parameter of the SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

configuration. It will reply to requests even if it is incorrectly configured (e.g. its SafetyProviderID is zero). However, SafetyConsumers will never try to communicate with SafetyProviders having incorrect parameters
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

SafetyConsumerID_i UInt32 Local variable to store the parameter SafetyConsumerID SPI_SafetyProviderID_i UInt32 Local variable to store the parameter SafetyProviderID SPI_SafetyBaseID_i UInt128 Local variable to store ... BaseID:= SPI_SafetyBaseID_i Else BaseID:= SAPI.SafetyBaseID Endif If(SAPI.SafetyProviderID == 0) Then ProviderID:= SPI_SafetyProviderID_i Else ProviderID:= SAPI.SafetyProviderID Endif SPDU_ID_1_i:= BaseID (octets 0…3) XOR SafetyProviderLevel
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:= SafetyBaseID (octets 8…11) XOR SafetyBaseID (octets 12…15) XOR SafetyProviderID (octets 0…3) In case of a mismatch between expected SPDU_ID and actual SPDU ... SPDU_ID_1 and SPDU_ID_2 do not, there is a mismatching SafetyProviderID . If SPDU_ID_2 differs, but SPDU_ID_1 and SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.3 Example for the calculation of SPDU_ID_1, SPDU_ID_2 and SPDU_ID_3 (informative)

calculation: SafetyBaseID is the GUID "72962B91-FA75-4AE6-8D28-B404DC7DAF63", SafetyProviderID has the value 0xE0EA6B40, SafetyStructureSignature has the value 0xDE7329FD and the SafetyProviderLevel_ID is chosen as 0xDEAA9DEE
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 ... 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
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.1.2 SafetyConsumerID

checking the SafetyConsumerID would also be detected by other mechanisms, including the MNR , the SafetyProviderID , and the SafetyConsumerTimeout . From a safety point of view, there are no qualitative requirements regarding
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.5 Safety manual

responsibility of the either the vendor or the integrator, or both. 4 SafetyBaseID / SafetyProviderID Information on how the SafetyBaseID and SafetyProviderID are generated and assigned. See 9.1.1 5 Commissioning Either
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

SafetyProviderDelay 8.2 Safety function response time part of communication RQ9.1 Storage of SafetyBaseID and SafetyProviderID 9.1.1 SafetyBaseID and SafetyProviderID RQ9.2a (Option 1) Use stored MNR after restart 9.2 Initialization