19.3 Interval Logger
The best use of memory is to log on change of state. However, some organizations may wish to log specific
tags on exact time intervals. Examples of where logging on an interval might be required are:
•
Regulatory reporting requirements
•
Hydraulic modeling software data input
•
Internal requirements for values in reservoir levels at midday and midnight
The interval logger provides this functionality.
The configuration screens are similar to the event logger and crisis logger above. The parameters that can
be set for interval logging for each tag are explained below:
Name
Description
Description
Description of the event as it will appear in the history page.
The tag being monitored and logged. The value of this tag will be saved to the history log at a
Source Tag
frequency defined by the interval.
Event types can be used for changing how a value is displayed in the history page or for filtering
Type
purposes. Standard mode is the default.
Enabled?
This checkbox allows logging to be disabled without deleting, to allow later re-enabling if required
DNP events are usually only triggered on change of state (a change outside deadband for an analog
DNP Event?
tag). If enabled, a DNP event will also be triggered when the value is logged to history – allowing
these interval logs to be reported to SCADA.
Intervals can be set as hh:mm:ss for more frequently logged data. There are also options for days,
Interval Type
weeks and months.
This value, in conjunction with Interval Type, is what sets the logging frequency. For example, if
Interval Type = "Days" and Interval = 5, this parameter will be logged every 5 days. The exact time of
Interval
logging is set by the Offset parameter.
This defines the offset to each time period at which to trigger the event log. For example, if the interval
is set to 1 hour and the offset is 30 minutes, the value will be logged at 30 minutes past each hour.
Offset
If the interval is defined to be a multiple of one day, then the offset specifies the time of the day to
trigger an event. If the interval is defined to be a multiple of one week then there is also the option to
specify the day of the week. If interval is monthly there is the option to specify the day of the month.
Table 32 – Interval Logger Configuration Parameters
19.4 Filtering the Data Viewed in the History Page
From the main operator screen, pressing the History button shows all events and faults logged. The History
page has the option for filtering the data to make it easier to find specific events or faults.
While in the History page, press Filters. This brings up a screen with five filter options. The screen also
shows if any filters are currently applied under each type.
By selecting each of the options on this screen, filters can be applied to a number of different areas as
explained in the following sections. A filter does not start or stop any data being logged, it only affects
viewing of that data in History.
NOTE: Any filters you apply remain in place for any future users of the History page, so if there are
many users of the system, it is best to remove the filters before leaving the station.
Page 168 of 260
MultiSmart Installation & Operation Manual
MultiSmart_IO_Manual_R20
Need help?
Do you have a question about the MultiSmart and is the answer not in the manual?
Questions and answers