Search

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

15 result(s) for SafetyConsumerID

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

5.4 Safety communication layer structure

process values . In contrast, it is not necessary for a SafetyProvider to know the SafetyConsumerID of the SafetyConsumer and will provide its process values to any SafetyConsumer requesting it. SafetyProviders
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

Table 7 - ReadSafetyData Method arguments Argument Description InSafetyConsumerID "Safety Consumer Identifier", see SafetyConsumerID in Table 23 . InMonitoringNumber " MonitoringNumber of the RequestSPDU ", see 7.2.1.3 and MonitoringNumber ... Safety PDU Identifier Part3", see 7.2.3.2 . OutSafetyConsumerID "Safety Consumer Identifier", see SafetyConsumerID in Table 23 and Table 26 . OutMonitoringNumber MonitoringNumber of the ResponseSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.6 Objects SafetyProviderParameters and SafetyConsumerParameters

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

6.3.3.2 SAPI of SafetyProvider

grained way, this can be realized by using qualifiers within the SafetyData , see 6.3.6 . SafetyConsumerID UInt32 O This output yields the ConsumerID used in the last access to this SafetyProvider ... implementation of this document, the safety application is not required to check this SafetyConsumerID . MonitoringNumber UInt32 O This output yields the MonitoringNumber ( MNR ). It is updated whenever a new request
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.2 SAPI of SafetyConsumer

static systems, this input is usually always kept at value "0". SafetyConsumerID UInt32 I For dynamic systems, this input can be set to a non-zero value ... this case, the SafetyConsumer uses this variable instead of the SPI parameter SafetyConsumerID . This input is only read in the first cycle, or when a rising edge occurs
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.4 SPI of the SafetyConsumer

more information on GUID . SafetyConsumerIDConfigured UInt32 0x0 to 0xFFFFFFFF 0x0 R/W SafetyConsumerID of the SafetyConsumer , see 9.1.2 . For dynamic systems, the safety application program can overwrite this ID by providing ... zero value at the input SafetyConsumerID of the SafetyConsumer 's SAPI . This runtime value can be queried using the SafetyConsumerIDActive parameter. See 6.2.2.6 for details on configured and active values
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.4.2 Diagnostics messages of the SafetyConsumer

CoIDerrOA The SafetyConsumer has switched to fail-safe substitute values due to an incorrect SafetyConsumerID . Operator acknowledgment is required. 0x16 B Yes MNRerrIgn The SafetyConsumer has discarded a message
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

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
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.8 ResponseSPDU: SafetyConsumerID

ResponseSPDU: SafetyConsumerID [RQ7.5] The SafetyConsumerID in the ResponseSPDU shall be a copy of the SafetyConsumerID received in the corresponding RequestSPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.4 SafetyProvider state diagram

clarification <build ResponseSPDU> Macro Take the MNR and the SafetyConsumerID of the received RequestSPDU . Add the SPDU_ID_1_i, SPDU_ID_2_i, SPDU
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.5 SafetyConsumer state diagram

prevMNR_i UInt32 Local memory for previous MNR ConsumerID_i UInt32 Local memory for SafetyConsumerID in use CRCCheck_i Boolean Local variable used to store the result ... UInt32 Local variable to store the expected SPDU_ID_3 SPI_SafetyConsumerID_i UInt32 Local variable to store the parameter SafetyConsumerID SPI_SafetyProviderID_i UInt32 Local variable to store
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.6 Calculation of a CRC signature

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] The generator polynomial 0xF4ACFB13 shall
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.1.2 SafetyConsumerID

SafetyConsumerID The SafetyConsumerID allows for discrimination between RequestSPDUs and ResponseSPDUs belonging to different SafetyConsumers . It is mainly used for diagnostic purposes, such as detecting unintentional concurrent access of a single ... SafetyProvider by multiple SafetyConsumers . Safety-related communication errors which are detected by checking the SafetyConsumerID would also be detected by other mechanisms, including the MNR , the SafetyProviderID , and the SafetyConsumerTimeout
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

9.4 PFH and PFD values of a logical safety communication link

link's SafetyConsumer . Whenever the SafetyConsumer detects a mismatch of the SafetyConsumerID , SPDU_ID , MNR or CRC , it will only continue operating if the last occurrence of such an error
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

ResponseSPDU.Flags 7.2.1.6 ResponseSPDU: Flags RQ7.4 Zero out reserved flags 7.2.1.6 ResponseSPDU: Flags RQ7.5 Copy SafetyConsumerID into ResponseSPDU 7.2.1.8 ResponseSPDU: SafetyConsumerID RQ7.6 Copy MonitoringNumber into ResponseSPDU 7.2.1.9 ResponseSPDU: MonitoringNumber RQ7.7 Usage