• Replies 12 replies
  • Subscribers 582 subscribers
  • Views 672 views
  • Users 0 members are here
Options
Related

Digital Trends and Trend Storage on Data Change

Chris

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
  • Olivier,

    We plan to roll out v3.0 soon, just didn't know what will happen to the existing historian tag names as there doesn't seem to be any documentation on our specific situation.

    One thing that would be EXTREMELY useful is a direct back fill utility from CitectSCADA to Wonderware Historian. We have struggled with back-filling all of our systems into the Wonderware Historian when we switched from the Citect Historian. We have 7 server pairs, 8 clusters, and about 5000 trend tags, all of which get historized. I've always though there could be an easy way to incorporate this functionality in the Connector.

    On the Trend Deaband subject, so what you are saying is if we use Periodic storage method combined with a Trend tag Deadband, it will still log a sample even if the Deadband has not be exceeded, that sample would be that last know variable tag value?
    I'll need to spend some time testing this, just trying minimize the data storage we consume with Trending. We keep 13 months of 0.100 second sample data, most tags don't change much and we could save a lot a space.

    Thanks,
    Chris
Reply
  • Olivier,

    We plan to roll out v3.0 soon, just didn't know what will happen to the existing historian tag names as there doesn't seem to be any documentation on our specific situation.

    One thing that would be EXTREMELY useful is a direct back fill utility from CitectSCADA to Wonderware Historian. We have struggled with back-filling all of our systems into the Wonderware Historian when we switched from the Citect Historian. We have 7 server pairs, 8 clusters, and about 5000 trend tags, all of which get historized. I've always though there could be an easy way to incorporate this functionality in the Connector.

    On the Trend Deaband subject, so what you are saying is if we use Periodic storage method combined with a Trend tag Deadband, it will still log a sample even if the Deadband has not be exceeded, that sample would be that last know variable tag value?
    I'll need to spend some time testing this, just trying minimize the data storage we consume with Trending. We keep 13 months of 0.100 second sample data, most tags don't change much and we could save a lot a space.

    Thanks,
    Chris
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.