Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


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.

Status Future consideration
Created by Nina NICHOLLS
Created on Nov 4, 2019

Enhanced logging for Ampla timers

https://schneiderampla.atlassian.net/browse/CE-1902

[System Info]
Ampla 6.0.7022

[Raised by]
Customer Company: Rio Tinto Iron Ore
Customer Contact: Thejus.jose@riotinto.com

[Enhancement Request]

Rio Tinto experienced a couple of instances with two separate servers where Ampla startup appeared to be stalled or really slow. After reviewing the issue further it was found that the Timers had stalled. I provided a workaround to overcome some of the Ampla v 6.0 timer limitations which involved changing the StartDateTime to a more recent value (see https://schneiderampla.atlassian.net/browse/CE-373).

However, Rio Tinto would like better tracing with the Ampla Timer object where it would be possible to trace events (either by setting the TraceLevel to Verbose) and also to log errors (SEQ or Windows Application Log) when Timers stop updating. Currently, setting Verbose Tracing on Timers does not seem to do anything in terms of messages in the Server Messages or SEQ.

  • Attach files