• State Verified Answer
  • Replies 1 reply
  • Subscribers 14 subscribers
  • Views 112 views
  • Users 0 members are here
Options
Related

How to configure logging interval of Historical Logging to be 1 second?

Wolfgang Banger

Hello,

  according to the info from this webpage, the smallest time interval for a tag being logged is 5 minutes when using historical logging. Is it possible to set the interval to be 1 second in InTouch 2023 R2?

Also, if the use case is to log the data from approximately 1000 tags in an InTouch project every 1 second(1000 written records per second), can this be achieved with historical logging? If not, what would Aveva's recommendation be for achieving this goal?

Thanks in advance.

  • +1

    Hi Wolfgang, 

    I do believe InTouch always stores historical data down to 1 second resolution, as soon as the data changes and is within the tag's Log deadband specification.

    The setting you reefer to is focusing on enforced storage of a value, even if it would normally not be logged, since you have settings such as Log Deadband on your tag, or that your tag never changes value.

    Let say you have a Real value that has Log Deadband  setting of 1.0. (default is 0.0), this means that the tag has to change more than 1.0 to be logged to history.

    So a change from 100.0 to 100.5 will not be logged to history files, but as soon as it changes to 101.00, it will be logged. This setting is to give an option to omit values that might change alot, (for example on a very low decimal level), you still want to display the many decimals, but not log it to history.

    As another example, if you have a value from PLC that is 100.123456 and fluctuates a lot on the third or fourth decimal, is it still desirable to log with this resolution?

    • ForceLogging

      ForceLogging specifies the length of the fixed logging interval in minutes. ForceLogging can be set to a value between 5 and 120 minutes. The default is ForceLogging=60.

    • ForceLogCurrentValue

      ForceLogCurrentValue specifies that, at the fixed logging interval, the current tag value is logged, even if it is still within the log deadband of the last logged value. When set to 0, the last logged value is logged again. The default is ForceLogCurrentValue=0.

    So using the Forced Logging, you can ensure that you store data even though normal configuration would omit it.

    If sub second logging is needed you would look in to storing data in to AVEVA Historian.

    The scenario that you describe, in 1000 values on a 1 second level is no problem for InTouch, as long as you receive the data with a 1 second update from your data source.

     
    I hope it helps.