We have an OPC Server wich is connected 1 time per day to donwload datas with timestamp from the source site.
We would like to use the ‘‘Database Driving Provider’’, but in the sqlt_core table we don’t have the timestamp from the data origin.
Attached file : a screenshot of the 2 parts.
Thanks and best regards
It depends on how many tags there are and how you want to use them, of course, but if you can use tag history instead, you can set the timestamp source to “data”, which will use the OPC timestamp. Of course, you’ll have to decode it from the unix time format that it’s stored it, but that is easy enough.
Another option would be to use a transaction group with the tag, and then a copy of the tag which references the “timestamp” property. That tag would be a “date” type, and will store the OPC timestamp for the value.
Unfortunately the “valuechange” column can’t be the opc time, because in the external tag provider system it’s used to detect changes, but we could probably add another column, which is “data time”. I believe this has actually been requested a few times…
Hi, and many thanks for your very quick answer.
Using the transaction group is an interesting way but we have too many datas to use.
We will try to work with the tag history.
Obviously, the best way for us should be the specific column you’re talking about in your third point.
Do you know if this add is planned to be in an update and in that case if it will be implemented soon?
Thanks and best regards.
In your last post, you suggested adding a timestamp column, in 7.6 it’s possible?
This has not yet been added to 7.6. It will likely make it into the 7.6.3 release.