By default, for any TriggerSchedule copied from the schedule palette, the main “Trigger” output slot is pinned on the component’s glyph (shape on wire sheet), as well as the following additional ones:
-
Enabled
Either true (default) or false. While false, firing of trigger outputs is disabled. If linking, note that this slot uses simple Boolean, you may need a StatusBooleanToBoolean (kitControl) component.
-
Last Trigger
Timestamp of the last firing of the trigger output.
-
Next Trigger
Next scheduled trigger firing time.
From the TriggerSchedule’s property sheet, you can access the following additional slots:
-
Next Trigger Search Limit
How far into the future to search for the next trigger. It is possible a poorly-configured schedule will never fire a trigger. This setting prevents an infinite search. Default is 90 days (2160 hours).
-
Last Modified
(read only) Timestamp of last configuration change.
-
Status
(read only) Status of the schedule component, typically “{ok}.”
In addition to the “main” Trigger output slot, the TriggerSchedule has “Trigger Missed” slot, also a topic type slot. If the station was not running when a scheduled trigger was to occur (appeared previously in “Next Trigger” property), upon station startup the Trigger Missed slot fires once.
Trigger Missed always fires only once, no matter how many triggers may have been missed.