Timestamps
- Last UpdatedNov 22, 2022
- 1 minute read
In some cases, the default method used to calculate the UTC offset between interface and PI Server nodes does not work properly.
One example is the Foxboro interface on UNIX or Windows, where the time zone on the interface node is always set to GMT standard time. During daylight savings time, when the wall clock time is adjusted 1 hour forward, the net effect is that the UTC time on the interface node jumps by 1 hour, independently of whether the PI SDK is enabled.
In this case, select Use alternate method of determining UTC seconds to determine the UTC time of the PI Server node in the same manner that the Foxboro interface determines the UTC time of the PI Server node. This feature can also be used when the PI SDK is not enabled. For example, the default UTC offset calculation fails when the interface communicates to a PI Server across a time zone that differs by a fraction of an hour, such as a 30-minute difference in time zones between the interface node and the PI Server node. In this case, the 30-minute time zone difference can be handled by enabling Use alternate method of determining UTC seconds or Enable PI SDK.
The command-line equivalent for enabling this option is /foxutc.