Search

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

6 result(s) for DataSetMessageSequenceNumber

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

6.3.2.3.1 DataSetMessageContentMask

included in the DataSetMessage header. SequenceNumber 2 If this flag is set, the DataSetMessageSequenceNumber is included in the DataSetMessage header. Timestamp 3 If this flag is set, a timestamp shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.4 UADP Chunk NetworkMessage

MessageSequenceNumber UInt16 Sequence number of the payload as defined for the NetworkMessage type like DataSetMessageSequenceNumber in a DataSetMessage . NetworkMessages may be received out of order. In this case, a chunk
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

sender and the receiver shall skip messages when reserved values are received. Bit 3: DataSetMessageSequenceNumber enabled Bit 4: Status enabled Bit 5: ConfigurationVersionMajorVersion enabled Bit 6: ConfigurationVersionMinorVersion enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetMessageSequenceNumber Status Additional restrictions: Fields within the payload use RawData Field Encoding Only data key frame ... valid Bit range 1-2: Field Encoding 01 RawData Field Encoding Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 DataSetMessageSequenceNumber Timestamp Status MinorVersion Additional remarks: Fields can use any encoding All types of DataSetMessages (Data ... DataSetMessage is valid Bit range 1-2: Field Encoding <anything> Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled = 1 Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

this DataSetMessage is valid Bit range 1-2: Field Encoding 00 - Variant Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled = 0 Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion