Skip to main content
I
imsnide3-Newcomer
3-Newcomer
July 12, 2023
Question

Timestamp logging question

  • July 12, 2023
  • 1 reply
  • 1819 views

I am reading some tag values programmatically and for some reason the Kepware tags being read are passing the system time instead of the recorded timestamp value. I can see the correct value when viewing in the QuickClient, however when I call on the program to read the values the timestamp value is changed to whatever time the read is made. 

 

Has anyone ever seen something like this?

 

 

 

 

 

 

1 reply

C
cmorehead13-Aquamarine
13-Aquamarine
July 17, 2023

@imsnide 

 

How are you programmatically requesting the data? Typically, Client applications make OPC DA or OPC UA data requests to KEPServerEX in which VQT(value, Quality and timestamp) are passed per the OPC specs. I presume you will need to get your program to make either OPC DA or OPC UA request in order to get the time stamp of the read request. The Quick Client makes an OPC DA connection.

 

Thanks,

*Chris

I
imsnide3-NewcomerAuthor
3-Newcomer
July 24, 2023

I am making the connection through an OPC DA client that I built. It works well in most environments, however I have one Kepware server that is logging the system time in place of the recorded time, and I can't figure out why...it's annoying, and I have made some modifications on the backend to work around the issue. My other use cases for this exact same logging application it picks up the time as seen in the OPC quick client/kepware. 

 

 

C
cmorehead13-Aquamarine
13-Aquamarine
July 25, 2023

@unknown_10736284

 

It sounds like time stamp issue is specific to your custom-built Client application since the behavior described is not seen in any other Client application making read requests of KEPServerEX. Are you able to open a Support Ticket with the Kepware Technical Support Team to properly troubleshoot your connection. The team will need to analyze some diagnostics and collect some files which are not suitable for this public community format. 

 

Thanks,

*Chris

Terms & ConditionsCookie settingsAccessibility statement