PQM HTML Webpage Comtrade file time stamp

[Paul_Crouch]

When I view the Comtrade waveform on the HTML page, the time stamp is UTC time.  If I were to view the same waveform file in ION setup it has the proper time stamp for the region and time the meter is set for. 

This is specifically for PM8240 and ION 9K products, but could be for others.

Is there some setting I am missing to ensure the HTML page Comtrade waveform view are showing proper time stamps. 

It is more a nuisance than a problem, but if looking at multiple meters at the same site then the additional check for time can make trouble shooting take longer. 

I can provide screenshots if needed.

[Charles_Murison · Accepted solution]

Hello @Paul_Crouch 

The meter will store all timestamps as UTC, waveforms, data recorder logged data, event logs etc. Different user interfaces will convert the UTC time to local time. Web pages, ION Setup, PME etc. each have different decisions to show either local time or UTC time.

The phrase "proper" can be a bit subjective. Inside the COMTRADE file itself, the timestamp is UTC. Could also be confusing to people to read the contents of the COMTRADE file and see a difference between what is on the web page and what is in the file.

The meter's webpages use JavaScript to display the timestamps on the web pages. If you know JavaScript you could in theory apply the time difference between local and UTC inside the JavaScript. I do not have an example I could provide. Note that every firmware upgrade would overwrite any changes you made.

Regards,

Charles

[Paul_Crouch]

After I submitted this yesterday, I did read other tickets.  Applying Java Script is not a good solution, not when one of my Date Canters could have more than 25 meters at a site.  The other solution is to have enough users request a change from sales team to provide an internal SE based solution for all meters.  I understand this a merely a nuisance, but if there is utility network input issue which small amount of time needed to true up time stamps for a true time start can take a lot of time that would be better spent actually troubleshooting or evaluating an issue.  This seems to with Java script, SE is putting the onus on the user(s) to have some kind of solution.