Search

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

10 result(s) for flags

OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.4 Header layout for NetworkMessages

UADP NetworkMessage header shall contain the following fields according to this header layout: Version / Flags ExtendedFlags1 PublisherId GroupFlags WriterGroupId GroupVersion NetworkMessageNumber SequenceNumber Additional restrictions: The datatype for the PublisherId shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.4 Header layout for NetworkMessages

NetworkMessage header shall consist of the following fields according to this header layout: Version / Flags ExtendedFlags1 PublisherId PayloadHeader Additional restrictions: The datatype for the PublisherId shall be UInt64 Note
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.3 Method ReadSafetyData

MonitoringNumber in Table 23 . InFlags "Octet with non-safety -related flags from SafetyConsumer ", see 6.2.3.1 . OutSafetyData " SafetyData ", see 7.2.1.5 . OutFlags "Octet with safety-related flags
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.1 General

contains a SafetyConsumerID , a MonitoringNumber ( MNR ), and one octet of ( non-safety -related) Flags . See 7.2.1.2 to 7.2.1.4 for details. See 6.2.3.3 for details on the RequestSPDUDataType definition. NOTE
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.1.4 RequestSPDU: Flags

RequestSPDU: Flags [RQ7.1] The flags of the SafetyConsumer ( RequestSPDU.Flags ) shall be used as shown
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

SafetyProvider by copying RequestSPDU.MonitoringNumber and RequestSPDU.SafetyConsumerID into the ResponseSPDU . In addition, SPDU_ID , Flags , the SafetyData and the NonSafetyData shall be updated. Finally, ResponseSPDU.CRC shall be calculated and appended. Figure
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

7.2.3.6 Calculation of a CRC signature

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

10.3 Index of requirements (informative)

RQ6.17 SafetyConsumer diagnostic message texts 6.4.2 Diagnostics messages of the SafetyConsumer RQ7.1 RequestSPDU Flags 7.2.1.4 RequestSPDU: Flags RQ7.2 Contents and structure of SafetyData in ResponseSPDU 7.2.1.5 ResponseSPDU: SafetyData RQ7.3 Usage ... 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
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.2 Header layout for NetworkMessages

NetworkMessage header shall consist of the following fields according to this header layout: Version / Flags ExtendedFlags1 PublisherId DataSetClassId Additional restrictions: The datatype for the PublisherId shall be UInt64 Note