Digital Trends and Trend Storage on Data Change

Hello,

We trend a lot of Digital tags, set to 2-byte storage method, but it would be so much better to storage them at a single bit. Also, we use the Wonderware Historian with the connector utility, all of our tags are configured as Analog with the 8-byte Trends stored as doubles and the 2-byte Trends stored as Integers. We have to set the engineering units to T/F and the range 0,1 to help sort them.

We run very fast trending, 100-250ms and it uses a lot of storage, we typically save about 13 months of data per site and I thought it might be possible to use the trigger in the Trend tag configuration to only store when the Variable tag data has changed. Has anybody done this? If so, what was your methods, workarounds and pitfall?

Thanks,

Chris

Parents
  • Hi ,
    If the Historize flag is set on the Trend Tag, and you have restarted the Citect SCADA Connector to re-read the config, and see this change, it should be publishing. Check the Connector logs to see if it is reading this Trend tag. You might also check on the Aveva Insight side, in case you have hit some point limit there?
    With regards to OEE in Aveva Insight, I am not familiar with this feature. It is best to get in contact with support.
    Kind regards
    Olivier
Reply
  • Hi ,
    If the Historize flag is set on the Trend Tag, and you have restarted the Citect SCADA Connector to re-read the config, and see this change, it should be publishing. Check the Connector logs to see if it is reading this Trend tag. You might also check on the Aveva Insight side, in case you have hit some point limit there?
    With regards to OEE in Aveva Insight, I am not familiar with this feature. It is best to get in contact with support.
    Kind regards
    Olivier
Children
No Data