Timestamps and the MQTT modules

PLC > Edge > MQTT Server > MQTT Engine module

The timestamp for an Edge tag read from a PLC will be the timestamp assigned by the PLC and associated Ignition driver. 

The timestamp for any other Edge tag will be the Ignition server OS time for change in Qualified Value (Value, Quality or Timestamp)

All timestamps published on the wire are in UTC and displayed converted to local time.

In general, the Edge is the source of truth for tag timestamps although there are several events that will cause the timestamps to differ across the system:

In a Transmission/Injector BIRTH message

• The BIRTH message for each Edge Node and Device will set the timestamp associated with each tag to the current time of the publishing client server's OS.
• If using MQTT engine, the timestamp at the Edge will show the last known timestamp from the PLC and Engine will display the timestamp included in the BIRTH message

OPC Tag Disabled

• When an OPC tag is disabled, the timestamp at Edge and Engine will reflect the time the tag was disabled.

OPC Tag Enabled

• When an OPC tag is enabled, the timestamp at Edge will reflect the last known change timestamp from the PLC whilst Engine will reflect the timestamp of the enabled change.

OPC Restart Tag

• When an OPC tag is restarted, the timestamp at Edge will reflect the last known change timestamp from the PLC whilst Engine will reflect the timestamp of the restart. 

Common Issue with tag timestamps

Time at PLC is older than Transmission or Engine leading to tag change events being ignored as the new event time is before current time for the tag at Engine