The possibility of declaring larger arrays in cicode, because the current restrictions do not allow you to make, for example, daily hourly reports, where logging data every 1s needed to calculate the average for the day 86400 number of samples for the TrendGetTable function.
We workaround this to have more tables indirect, but it makes the code much bigger.
It would be nice to open the code for the trendgetable trend function.
Guest
|
Idea business value
This would enable reports to be made over long periods. Customers expect to extract data from historical trends over long periods. |
|
| Idea priority | 5 – Critical to my company |
Cicode is essential for making such no standard report examples, with an interface built using Graphics Builder for operator. We have been developing this type of reports for years at the client's request. Not all this can be done with a historian.
If you don't want to develop these features, shouldn't they be made available to developers ?
Question: Plant SCADA 2023R2 now comes with AVEVA Historian, which already stores the data at high fidelity meaning that it is storing the data at the resolution of Plant SCADA already in the history blocks, plus it already had the Summary State details readily available for you to use as it stores, hourly, daily, yearly totals automatically, you simply request the date. Why would all this CiCode be necessary now that you have a true time series historian at your fingertips. It may be time to consider eliminating the amount of Custom CiCode required to complete a task of which is native now in the product. Custom CiCode makes it harder to maintain the lifecycle of the product where as out of the box functionality provides a much simpler solution to upgrade. I need more details as to even consider this now that a true time series historian is your solution.