Search
12 result(s) for Payload Header
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.3.1.1.4 NetworkMessageContentMaskincluded in the GroupHeader . The flag is only valid if Bit 1 is set. PayloadHeader 6 The PayloadHeader is included in the NetworkMessages . Timestamp 7 The sender timestamp is included
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.3.1.3.4 NetworkMessageNumberNetworkMessage is not fixed. The NetworkMessage shall have a fixed layout if the PayloadHeader flag in the NetworkMessageContentMask is false. If the NetworkMessage layout is fixed and all DataSetMessages
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.3.1.3.5 DataSetOffsetheader at the offset shall be false. This parameter should be set if the PayloadHeader flag in the NetworkMessageContentMask is false and therefore the NetworkMessage has a fixed layout
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.3.1.4.2 NetworkMessageNumberthis parameter shall be ignored. The NetworkMessage shall have a fixed layout if the PayloadHeader flag in the NetworkMessageContentMask is false
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.3.1.4.3 DataSetOffsetDataSetMessage in a NetworkMessage is not fixed. This parameter should be set if the PayloadHeader flag in the NetworkMessageContentMask is false and therefore the NetworkMessage has a fixed layout
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.2.4.4.2 NetworkMessage layoutExtendedFlags1 PublisherId Type flags shall be false. Bit 5: GroupHeader enabled Bit 6: PayloadHeader enabled Bit 7: ExtendedFlags1 enabled The bit shall be false, if ExtendedFlags1 is 0. ExtendedFlags1 Byte ... This field shall be omitted if bit 3 of the GroupFlags is false. PayloadHeader Byte [*] The payload header depends on the UADP NetworkMessage type flags defined in the ExtendedFlags2
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.2.4.4.4 UADP Chunk NetworkMessagesplit across multiple NetworkMessages, the chunks are sent in multiple NetworkMessages . The PayloadHeader of each NetworkMessage contains the payload header defined in Table 158 . The Payload of each NetworkMessage contains
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubA.2.1.2 Overviewrequired for ad-hoc parsing of messages with dynamic layout can be omitted (e.g. PayloadHeader or Sizes ). Finally, a Subscriber needs an easy way to verify that a received message
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubPublisherId enabled = 1 Bit 5: GroupHeader enabled = 1 Bit 6: PayloadHeader enabled = 0 Bit 7: ExtendedFlags1 enabled = 1 ExtendedFlags1 Byte Bit range 0-2: PublisherId Type with
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubA.2.1.7 . The configuration ensures that every NetworkMessage sent has the same layout of header fields and also the same layout of DataSet fields. This allows a highly efficient encoding ... because the offset of all fields is constant and can be pre-calculated. The Payload Header ( Count and Sizes for the DataSetMessages and DataSetWriterIds ) is deactivated and the Subscriber
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSubconsist 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: For the PublisherId ... PublisherId enabled = 1 Bit 5: GroupHeader enabled = 0 Bit 6: PayloadHeader enabled = 1 Bit 7: ExtendedFlags1 enabled = 1 ExtendedFlags1 Byte Bit range 0-2: PublisherId Type 011 The PublisherId
-
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias NamesPublisherId enabled = 1 Bit 5: GroupHeader enabled = 0 Bit 6: PayloadHeader enabled = 0 Bit 7: ExtendedFlags1 enabled = 1 ExtendedFlags1 Byte Bit range 0-2: PublisherId Type 011 The PublisherId