Search

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

12 result(s) for process values

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

3.1.2.8 process values

process values input and output data (in a safety PDU) that are required to control an automated process
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.3 Safety measures

SafetyConsumer is defined in such a way that it will cease to deliver actual process values to the safety application but will deliver fail-safe substitute values instead. In addition
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

5.4 Safety communication layer structure

fail-safe substitute values are delivered to the safety application instead of the received process values . In contrast, it is not necessary for a SafetyProvider to know the SafetyConsumerID ... 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.3.3.2 SAPI of SafetyProvider

used to trigger a return from fail-safe substitute values ( FSV ) to actual process values ( PV ), see B.3.4 . OperatorAckRequested Boolean O Indicates that an operator acknowledge is requested ... instead of PV to the safety application program. NOTE If the replacement of process values by FSV is to be controllable in a more fine-grained way, this
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.2 SAPI of SafetyConsumer

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 ... 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 I By changing this input
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.3 Motivation for SAPI Operator Acknowledge (OperatorAckConsumer)

assumption is still valid, and switches to fail-safe substitute values otherwise. Returning to process values then requires an operator acknowledgment. Operator Acknowledge is expected to be initiated
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.3.4.5 Motivation for SPI SafetyOperatorAckNecessary

parameter determines whether automatic restart (i.e. automatically switching back from fail-safe values to process values ) is possible for the safety function or not. It is expected
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.5 ResponseSPDU: SafetyData

contain qualifiers for a fine-grained activation of fail-safe substitute values. For valid process values , the respective qualifiers are set to 1 (good), whereas the value ... used for invalid values. Invalid process values are replaced by fail-safe substitute values in the SafetyConsumer 's safety application
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram

shall answer all requests. The returned ResponseSPDUs may contain different values (e.g. currently available process values ) or contain the initially returned values. [RQ7.11] For each SafetyProvider , the implemented choice ... behaviour according to RQ7.10 (i.e. whether currently available process values or initially returned values will be used) shall be documented in the corresponding safety manual. NOTE 2 Since a SafetyConsumer
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

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

bidirectional connection. Both sides will cease delivering fail-safe values and continue sending process values . This is accomplished by connecting OperatorAckProvider with OperatorAckConsumer at the SafetyConsumer of controller B. Activating
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

B.3.5 Use case 4: bidirectional communication and single, two-sided OA

bidirectional connection. Both sides will cease delivering fail-safe values and continue sending process values . This is accomplished by the logic circuits shown in the safety applications
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

5.1 Example Serialize RIO Channel Groups

shows a Channel Group containing two output channel Objects , a configuration Object and Process Values . Figure 4 - RIO Channel Group From the Clients' perspective, certain use cases when accessing ... single subtrees are supported by the Server . A Client might be interested in the Process Values provided in the "Values" array and the associated Process Value Qualifiers