Search

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

4 result(s) for ResponseSPDU.Flags

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

6.3.3.2 SAPI of SafetyProvider

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, and are not to be used ... this input to "1" the SafetyConsumer is instructed (via Bit 1 in ResponseSPDU.Flags , see 6.2.3.2 ) to deliver FSV instead of PV to the safety application program. NOTE
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.6 ResponseSPDU: Flags

ResponseSPDU: Flags [RQ7.3] The flags of the SafetyProvider ( ResponseSPDU.Flags ) shall be used as shown in 6.2.3.2 . [RQ7.4] Flags in the ResponseSPDU.Flags which are reserved for future use shall
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.1 Build ResponseSPDU

task of building the ResponseSPDU . Figure 20 - Overview of task for SafetyProvider For the ResponseSPDU.Flags , see 7.2.1.6 . For the calculation of the SPDU_ID , see 7.2.3.2 . For the calculation
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

10.3 Index of requirements (informative)

RQ7.2 Contents and structure of SafetyData in ResponseSPDU 7.2.1.5 ResponseSPDU: SafetyData RQ7.3 Usage of 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