• Not Answered

Process History View Timestamps Incorrect

Hi All,

I am working on a system with DeltaV v12.3.1. On the Operator Station that I am using, there is a strange recurrent issue with timestamps in Process History View that occurs every day between midnight and 8am. I believe the issue is specific to my Operator Station. Other stations do not have this issue, and the same issue applied regardless of whether I select one Events Data Server or the other. It also occurs regardless of the source node of the event.

It is easiest to describe the issue with specific dates. For example, at midnight on 7th October, the timestamp shifts from 10/07/2022 11:59pm to 11/07/2022 12:00am, then at 8am on 8th October the timestamp shifts back from 11/07/2022 7:59am to 10/08/2022 8:00am. That is, at midnight the month jumps forward by 1 instead of the day, then at 8am it corrects itself.

Any ideas as to what is going on here?

8 Replies

  • KBA AP-0900-0017 describes a similar strange issue with date/time which is caused by the Windows Regional Settings. You might want to compare the settings on the workstation that is affected with one that isn't. I believe that each Windows user has their own Windows Regional Settings so you might want to check if the affected workstation has a different user logged on.
  • Please let me know if you resolved the issue, i am also facing the same issue for my Engineering Station.
    Between 12:00 am to 5:30 am events date changes to next day, my time zone is +5:30
  • In reply to Cedric Dawnhawk:

    Please can you share the KBA cannot find the same, since facing the same issue as above.
  • In reply to dhananjay:

    AP-0900-0017 Process history incorrect date format.pdf

    Link above. I'm not suggesting that this is the answer, just that it describes strange effects in dates due to regional settings.

  • In reply to dhananjay:

    Hi, I tried following the workaround provided in the above mentioned KBA. I changed the Regional Setting to English (United States), and confirmed that the DeltaV locale registry is 409 (1033 decimal) in Registry Editor.
    I compared my short date format to another workstation which is not affected, and changed to match it from dd/MM/yyyy to M/d/yyyy. I restarted the workstation, confirmed that changes have been retained, but I still had the issue.
    However, I then changed the short date format back to original dd/MM/yyyy and the problem is now resolved.
    So the key was making the Regional Setting English (United States) and confirming the locale, there was no need to change the short date format.
  • In reply to Dean Chesterfield:

    Although the KBA is not very clear, it does say that, as you found, once the regional settings and locale are correct, you should be able to set any format for the date, time etc

    It is interesting that your symptoms do not appear to be as described in the KBA and as I experienced, These are that between the 1st and the 12th of the month the date format is mm/dd/yyyy then the rest of the month it changes back to that set by the regional settings, in my case dd/mm/yyyy.
  • In reply to Cedric Dawnhawk:

    Thank you for your help the issue is resolved... Changed my location to English united states
  • In reply to Dean Chesterfield:

    Yes making regional setting English United States resolved my issue
    Thank you precious time and help...