I am running Aveva (Citect) Scada 8.2 and Aveva Historian 2020 R2 with Citect connector. The connector only brings over trend tags. Is there a way to get it to bring over historized Citect Tags?
I am running Aveva (Citect) Scada 8.2 and Aveva Historian 2020 R2 with Citect connector. The connector only brings over trend tags. Is there a way to get it to bring over historized Citect Tags?
Yes, you'll just need to set the variable tag historize flag to true. Restart both Citect and the connector. Just keep in mind that you will loose data when the connector is off line as it can't back fill from the trend tags. When using the trend tags, the connector keeps a record of the last sample that has pushed to the historian, and picks up from that point. It can't do that with straight variable tags. The connector will also bring over alarms too that are set to historize BTW.
Your situation may be different that ours, but we set all alarm (you don't get charged for alarm/event tags in the WW historian) and trend tags to historize but not the variable tags. If we want a tag to be historized, we create a trend tag that is historize, that way the data can be trended both locally and on the historian.
Ah, thanks for the clarification, and sorry about that. Are you running the latest version of the connector with the latest patch? Have you set the options to poll the variable tags? Are any of the tags named that same as the trend tags? I just looked through the help again, it looks like it only pulls digital and string data types for the variable tags. We're using connector version 3.0 with the latest patch applied.
Have you looked at the connector logs?
To view connector events
Ah, thanks for the clarification, and sorry about that. Are you running the latest version of the connector with the latest patch? Have you set the options to poll the variable tags? Are any of the tags named that same as the trend tags? I just looked through the help again, it looks like it only pulls digital and string data types for the variable tags. We're using connector version 3.0 with the latest patch applied.
Have you looked at the connector logs?
To view connector events