Search

12 result(s) for serverTimestamp

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.37 UtcTime
  local time. It should be noted that the SourceTimestamp (see OPC 10000-4 ) and ServerTimestamp (see OPC 10000-4 ) may originate from different clocks that have no synchronization
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.2 Parameters
  milliseconds. The age of the value is based on the difference between the ServerTimestamp and the time when the Server starts processing the request. For example if the Client specifies
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.2 Parameters
  array even if only one element is being written. If the SourceTimestamp or the ServerTimestamp is specified, the Server shall use these values. The Server returns a Bad_WriteNotSupported error
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.2 RedundantServerSet Requirements
  exposing data from a downstream device (PLC, DCS etc.) then the SourceTimestamp and ServerTimestamp reported by all redundant Servers should match as closely as possible. Clients should favour
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.4 ServerTimestamp
  ServerTimestamp The serverTimestamp is used to reflect the time that the Server received a Variable value or knew it to be accurate. In the case of a bad or uncertain ... status, serverTimestamp is used to reflect the time that the Server received the status or that the Server last tried to recover from the bad or uncertain status
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.4 AggregateFilter
  carried over and used to calculate a value returned in the next publish. The ServerTimestamp for each interval shall be the time of the end of the processing interval
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  received the Event from the underlying device of another Server . ReceiveTime is analogous to ServerTimestamp defined in OPC 10000-4 , i.e. in the case where the OPC UA Server gets
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.5 Attributes of DataItems
  quality and the Server's ability to access/provide the value) and, optionally, a ServerTimestamp and/or a SourceTimestamp - based on the Client's request. See OPC 10000-4 for details
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.5 Timestamps
  request is in terms of SourceTimestamp but the reply could be in SourceTimestamp , ServerTimestamp or both timestamps. If the reply has the Server timestamp the timestamps could fall outside ... range of the requested time. SOURCE Return the SourceTimestamp . SERVER Return the ServerTimestamp . BOTH Return both the SourceTimestamp and ServerTimestamp . NEITHER This is not a valid setting for any HistoryRead
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.2.2 Operation level result codes
  Client requested history using a TimestampsToReturn the Server does not support. For example requested ServerTimestamp when Server only supports SourceTimestamp . Bad_InvalidArgument One or more arguments are invalid or missing
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.4.2 DataSetFieldContentMask
  DataSetMessage s. If this bit is set, the fields are represented as DataValue . ServerTimestamp 2 The DataValue structure field ServerTimestamp is included in the DataSetMessage s. If this ... fields are represented as DataValue . This bit is ignored if the ServerTimestamp bit is not set. RawData 5 If this bit is set for UADP message mapping, the fields
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  each change to a given ConnectionConfigurationSet , no matter the source of the change. Its ServerTimestamp shall be set to the time of the change. When a ConnectionConfigurationSet is added