Appendix2 About Monitoring Interval Timeout
Depending on the number of set jobs or the trigger condition setting, the monitoring interval timeout may be generated in
the MES interface function.
This section explains monitoring interval timeout.
Although up to 64 jobs can be registered and trigger conditions can be set to each of them, some adjustment in
trigger condition settings is required depending on the number of the jobs.
(1) Monitoring interval timeout
The monitoring interval timeout means that the trigger detection time (the time provided for the trigger
monitoring function to determine if the trigger conditions are met) becomes longer than the time limit of trigger
occurrence (monitoring interval). When a monitoring interval timeout occurs, the job may not be executed even
though set trigger conditions are met.
Monitoring interval: 1s
(2) Causes of monitoring interval timeout
A monitoring interval timeout occurs when the total jobs cannot be processed in a monitoring interval.
The monitoring interval includes the following sampling intervals.
• Sampling interval set for [Sampling setting] in [Device tag settings] when selecting [Value monitoring startup]
or [Handshake operation] for [Trigger conditions] in [Job settings]
• Sampling interval set for [Trigger conditions] when selecting [Specified time period startup] for [Trigger
conditions] in [Job settings]
In the following cases, monitoring interval timeouts do not occur.
• When selecting [Time specification startup] or [GOT Initializing] for [Trigger conditions] in [Job settings]
• When the total jobs are processed in a monitoring interval
When the time for trigger detection is shorter than the monitoring interval
Since processing for trigger detection is performed within each monitoring interval, no monitoring interval
App - 4
6.5 Device Tag Settings
6.7.2 Setting items in Trigger conditions