OPC Foundation
  • Documents
  • NodeSets
  • Search
A.2.7 Header layout for DataSetMessages

A 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 key frame DataSetMessages are supported

The DataSetMessage header layout is shown in Figure A.4.

image056.png

Figure A.4 – UADP DataSetMessage header layout

Table A.5 shows the 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

01 RawData Field Encoding

Bit 3: DataSetMessageSequenceNumber enabled = 1

Bit 4: Status enabled

Bit 5: ConfigurationVersionMajorVersion enabled = 0

Bit 6: ConfigurationVersionMinorVersion enabled = 0

Bit 7: DataSetFlags2 enabled = 0

DataSetMessageSequenceNumber

UInt16

Defined by Table 142.

StatusCode

UInt16

Defined by Table 142.

Table A.6 defines the values for the configuration parameters representing this layout.

Table A.6 – Values for configuration parameters

Parameter

Value

KeyFrameCount

1

UadpDataSetMessageContentMask

0x00000024

This value results of the following options:

Bit 2: StatusCode enabled = 1

Bit 5: SequenceNumber enabled = 1

DataSetFieldContentMask

0x00000020

This value results of the following options:

Bit 5: RawData

DataSetOrdering

AscendingWriterId or AscendingWriterIdSingle

Please report errors or issues with the site to webmaster.

Copyright © 2023 - OPC Foundation