Search

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

11 result(s) for PicoSeconds

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.11.2 PicoSeconds

PicoSeconds Some applications require high resolution timestamps. The PicoSeconds fields allow applications to specify timestamps with a resolution of 10 picoseconds. The actual size of the PicoSeconds field depends ... example, if the UtcTime DataType has a resolution of 100 nanoseconds then the PicoSeconds field would need to store values up to 10 000 in order to provide the resolution
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.17 DataValue

SourcePicoseconds bit in the EncodingMask is False. If the source timestamp is missing the Picoseconds are ignored. ServerTimestamp DateTime The Server timestamp associated with the value. Not present ... ServerPicoseconds bit in the EncodingMask is False. If the Server timestamp is missing the Picoseconds are ignored. The Picoseconds fields store the difference between a high-resolution timestamp with
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.4 NetworkMessageContentMask

NetworkMessages . Timestamp 7 The sender timestamp is included in the NetworkMessage s. PicoSeconds 8 The sender PicoSeconds portion of the timestamp is included in the NetworkMessage s. This flag
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.2 DataSetMessageContentMask

this flag is set, a timestamp shall be included in the DataSetMessage header. PicoSeconds 1 If this flag is set, a PicoSeconds timestamp field shall be included in the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

SIGN or SIGNANDENCRYPT , this flag shall be set. Bit 5: Timestamp enabled Bit 6: PicoSeconds enabled This bit shall be false if the Timestamp bit is false. Bit 7: ExtendedFlags2 ... ExtendedFlags1 is false. The PublishingInterval , the SamplingOffset the PublishingOffset and the Timestamp and PicoSeconds in the NetworkMessage header shall use the same time base. PicoSeconds UInt16 Specifies the number
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

shall skip messages when reserved values are received. Bit 4: Timestamp enabled Bit 5: PicoSeconds included in the DataSetMessage header This bit shall be false if the Timestamp ... created. The Timestamp shall be omitted if Bit 4 of DataSetFlags2 is false. PicoSeconds UInt16 Specifies the number of 10 picoseconds (1,0 e-11 seconds) intervals which shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.4 Header layout for NetworkMessages

enabled = 0 Bit 4: SecurityHeader enabled = 0 Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2 enabled = 0 PublisherId UInt16 or UInt64 Configured value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.4 Header layout for NetworkMessages

enabled = 0 Bit 4: SecurityHeader enabled = 0 Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2 enabled = 0 PublisherId UInt64 Configured value for the PubSubConnection
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

UADP DataSetMessage type <anything> Bit 4: Timestamp enabled = 1 Bit 5: PicoSeconds enabled = 0 (not included in the DataSetMessage header) DataSetMessageSequenceNumber UInt16 Defined by Table 162 . Timestamp UtcTime
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.2 Header layout for NetworkMessages

SecurityHeader enabled configurable (default=1) Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2 enabled = 0 PublisherId UInt64 Configured value for the PubSubConnection. The datatype shall
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

Shall be 0011 for a Keep Alive Bit 4: Timestamp enabled = 0 Bit 5: PicoSeconds enabled = 0 (not included in the DataSetMessage header) For a description of Data KeyFrame, Data