Settings for Device Monitor schedules

Log aggregation delay

Select or enter the amount of time to wait for more potential changes before completing the change report after the last change has occurred. The default value is set to 10 minutes.

Device Monitor schedules run all the time when the schedule is active. The device is monitored and when a change is detected, change entries from the controller log are collected into a report. When the Log aggregation delay time or Maximum Runtime is reached, change entries cease to be added to the report and the email messages configured for the schedule are sent. The device continues to be monitored and when another change is detected, another report is started. FactoryTalk AssetCentre reports are in PDF format and are attached to the schedule-generated email messages and to the schedule completed event in the Event Log.

Maximum Runtime

Select or enter the maximum time in hours and minutes that the operation should collect changes into a report. The default value is set to 1 hour.

The Log aggregation delay time will not be reached if changes are continuous, so you may need a Maximum Runtime to force a report to be generated. Changes will continue to be collected into a new report (no changes are missed) until the Log aggregation delay time or Maximum Runtime is reached.

Scan Interval

Select or enter the time interval between two consecutive controller log readings for the same controller.

A shorter interval means more frequent communication with the controller, allowing for quicker detection of changes. Meanwhile, it increases the load on the controller. Conversely, a longer interval reduces communication frequency and conserves controller resources, but may delay detection of changes. The default value is set to 5 seconds. The value of scan interval must be smaller than the value of log aggregation delay.

Connection Retry Count

Select or enter the maximum number of attempts to establish a connection with the controller after a failure. The default value is set to 3.

For example, if this number is set to 3, the system will attempt to connect up to three times. If the connection succeeds, the detection process proceeds. If all retry attempts fails, the system initiates new retries after a delay of 25 seconds plus the scan interval to ensure a successful connection. For example, if the scan interval is set to 3 seconds and the retry limit is 3, the system will make three failed connection attempts, and then wait 28 seconds before retrying. This cycle continues, with the system retrying every 28 seconds, until a successful connection is established.