We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.
To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.
This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.
This would be a really nice feature for all drivers.
[ENHANCEMENT] Request to have a feature added to the ABCLX driver to allow for driver specific categories (Group poll time, optimized blocks etc..) to be extracted is currently in Development and pending further testing before being incorporated for accessibility by the product. More details coming soon
Notes from Support Case:The mentioned ABCLX driver parameters - are these displayed as driver statistics in the kernel page? If yes, then it would be possible to create a number of virtual tags to represent the statistics counters. - Comment from Devs: It is only can be done in the SCADA itself. The driver only provides the statistics data to Citect. The driver can only create virtual tags to represent the statistics counters. And each driver would need to be modified separately.
Customer Feedback pertaining to this idea: "We’d been hearing reports from our operators that their SCADA performance was starting to lag. We went through our usual debugging steps to try and determine the root cause.
When the usual steps turned up nothing, I started investigating the driver. I noticed that the group poll times for the PLC’s in question had increased substantially. After some investigation, the root cause of this was Kepware making
additional connections to the affect plant area PLC’s. It was quite timely that I had recently taken some baseline statistics for the driver and PLCs, so we could compare.
This issue got me thinking, it would be nice to be able to have this information historized (group poll time, optimised blocks, good tags, bad tags, missed polls, total polls and what not). "