Search

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

8 result(s) for DataSetFlags1

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

6.3.1.3.3 ConfiguredSize

case it would be larger, the Publisher shall set bit 0 of the DataSetFlags1 to false to indicate that the DataSetMessage is not valid. NOTE The parameter ConfiguredSize
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.5 DataSetOffset

DataSetWriter is disabled and the DataSetOffset is not 0, the valid flag of the DataSetFlags1 in the DataSetMessage header at the offset shall be false. This parameter should
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

DataSetFieldContentMask and the DataSetMessageContentMask settings of the DataSetWriter control the flags in the fields DataSetFlags1 and DataSetFlags2 . The setting of the flags shall not change until the configuration ... DataSetWriter is changed. Table 162 - DataSetMessage header structure Name Type Description DataSetFlags1 Byte Bit 0: DataSetMessage is valid. If this bit is set to false, the rest of this DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.7 Event DataSetMessage

DataSet. The fields of Event DataSetMessages shall be encoded as Variant. The Field Encoding DataSetFlags1 of the DataSetMessage header (bit 1 and 2) defined in 7.2.4.5.4 shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.11 RawData field encoding

contains the same Structure DataType directly or indirectly. The DataSetMessage valid bit 0 in DataSetFlags1 shall be set to false if the fields do not fulfil these requirements
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

UADP 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 ... configuration for the DataSetMessage header. Table A.5 - UADP DataSetMessage header layout Name Type Restrictions DataSetFlags1 Byte Bit 0: Indicates whether this DataSetMessage is valid Bit range 1-2: Field Encoding
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

UADP DataSetMessage 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 ... configuration for the DataSetMessage header. Table A.11 - UADP DataSetMessage header layout Name Type Description DataSetFlags1 Byte Bit 0: Indicates whether this DataSetMessage is valid Bit range 1-2: Field Encoding
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 Additional remarks: Field is encoded as a Variant The following types of DataSetMessages (Data ... configuration for the DataSetMessage header. Table D.7 - UADP DataSetMessage header layout Name Type Description DataSetFlags1 Byte Bit 0: Indicates whether this DataSetMessage is valid Bit range 1-2: Field Encoding