• State Not Answered
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 69 views
  • Users 0 members are here
Options
Related

Hello,

Ayoub EAUADEN

Hello,

I am experiencing a timestamp offset issue for tags between two PI servers: Historian (VDRSQLITKQ03) and View (VDRSQLITKQ02).

From PI SMT on the View server, the tag timestamps are correct. However, on the Historian server, the same tag shows a 9-hour offset.

Example:

On the View server, the latest value of the tag = 2 is timestamped at 29/07/2025 at 15:52:31,

whereas on the Historian server, the same tag at the same moment is timestamped at 29/07/2025 at 06:52:31.

Both servers have the same time zone.

 


View Server.png

Historian Server.png
 

Could you help me identify the cause of this offset and suggest a solution?

Thank you !

Ayoub EAUADEN

  • 0

    Forgive me but I found this a bit confusing or misleading since you said the offset if between "two PI servers". Your 2 images are of the same PI Point on the same PI Data Archive. However, each image is from a different PI SMT Client. Granted, it just so happens that each SMT Client also happens to be a PI Server, but the fact that they coincidentally are PI Servers does not have any bearing with your problem, and is why I found it misleading.

     

    Focus instead that you have 2 different PI SMT Clients, and that both are looking at the same PI Point but that the timestamps appear different. Since the PI Values for that PI Point are coming from the same PI Server, the archived UTC Time is the same though you are asking for it to be shown in the Client Timezone on each respective SMT Client.

     

    What we are really dealing with is that SMT Clients are using different formats and/or time zones for displaying that same timestamp. From SMT's toolbar, go to View -> Settings, and then click the Time Format tab. Compare those on both SMT Clients. Also compare the Windows Time Zone setting on each machine hosting the SMT Client.

  • 0

    Thank you for your feedback and for pointing that out.

    You're absolutely right — the two screenshots were taken from different PI SMT clients, each running on a separate server (VDRSQLITKQ02 and VDRSQLITKQ03), which also happen to be PI Servers. My intention was not to suggest that the issue is caused by them being PI Servers, but simply to highlight that the same PI Point shows a 9-hour timestamp difference depending on which PI SMT client is used to view it.

    Both servers are synchronized in terms of system time and time zone. I have also verified the Time Zone settings and the Timestamp format on both servers, and everything appears to be correctly configured.

    To support this, I’ve attached an image showing the relevant settings.

     


    Time-Zone_HistServ.png
    
    Time-Zone_ViewServ.png

    Time-Format-Tab_ViewServ.png

    Time-Format-Tab_HistServ.png
    Would you have any suggestions or recommendations on what else I should check to resolve this timestamp offset?

    Thanks again for your help.

  • 0

    Hello,

    I’ve resolved the issue. It was related to the "Localhost.tz" configuration file used by Historian, where the time zone was incorrectly set to Pacific (-9h).

    To fix this, I replaced the file with another of the same type, retrieved from a properly configured Historian, using the UTC+1 (Romance Standard Time - RST) time zone.

    Thank you