|
<< Click to Display Table of Contents >> Time Based Event Setup |
  
|
|
<< Click to Display Table of Contents >> Time Based Event Setup |
|
Setting up a Time Based Event in Strategy Controller:
(There are also some specific examples here.)
|
Description is a text field to identify the event. Events are listed in alphabetical order so it is a good idea to use a numeric prefix so that related events may be grouped together in the list. |
|
When the 'Log to Event Log' box is checked each occurrence of the event will be time stamped in the Event Log . (If the event log has been set to record specified events) |
|
|
The time at which the event will trigger is determined by the settings in these lists
This event will last for one second every Monday at 6 o'clock in the morning. If 'Any' had been left in the 'Second' field the event would be true any time between 06:00:00 and 06:00:59. But the event will only be triggered ONCE during that minute, and will not trigger again until next Monday at 6am.
|
Note the 'Any 5, Any 10 etc. that are at the bottom of the Minute and Second lists. When possible, these should be used in place of the 'Repeat Every' function described below. |
Only use the 'Repeat every' setting with caution. The event will trigger every 6 hours with the setting shown. What SpecView does is compute when the next event should occur and automatically enter those values into the time and day fields. |
|
If the first event was set to be 06:00 on Monday, as shown above, and it is March 5, 2002 when the event is first triggered SpecView will compute that the next event will be:
If SpecView is not in Runtime Mode at that precise moment the event will be missed and will never be triggered again.
The user will need to re-edit the Strategy Controller event to get it to trigger again.
NOTE: It is recommended that a Value based event watching SpecView.Time with a test of Changed by a constant value be used instead of a time based event using 'Repeat every'.
Using Event Control (Enable On Boolean) to do an AND function with a time based event
Event Control allows an AND function with a secondary boolean
For example: Every Monday at 06:00 AND SpecView.AutoRecipeLoad = On
If it is required to AND a variable that is not a boolean, such as a number, an intermediate event must be defined:
For example, 06:00 on Monday AND Zone 3.Process Value > 300
A SpecView boolean User Variable must be defined 'Zone 3 over 300'
A Strategy Controller event/action: 'Zone 3.Process Value > 300 è Parameters: Download Specific Value of On to SpecView.Zone 3 over 300' turns on the boolean.
A second event: '06:00 on Monday' AND 'SpecView.Zone 3 over 300 = True' completes the required statement.
In such an example do not forget to have an event to turn OFF the boolean since the Strategy Controller has no implied ELSE function.
When this box is checked the Strategy Controller will NOT test the event. |
|
