Timers

Prev Next

Click Automation > Timers in the navigation bar to show four tabs under the Timers section:

  • The Timers tab can be used to create interval, date/time, and recurring timers, which can execute changes either at specific times or after an interval. To use them, assign property changes in the time event, connect the timer to a Logic Flow, or both.

  • The Resources, Templates, and Calendars tabs are for use with the additional scheduling license.

Timers Tab

Timers allow Flows and/or property changes (such as a route change) to be executed at specific times. This list shows the Timers that have been created and may be used in Logic Flows. The page shows up-to-date information as the Timer states change.

Column

Notes

Name

The name of the Timer.

Type

The type of Timer.

Interval

For Interval Timers, this column displays the time in milliseconds. For Day of week Timers, the column displays the days per week that are selected. This column is not used for Date/Time Timers.

LastRaise

This column displays the date and time when the Timer last elapsed. If the Timer has never elapsed, it will display a default minimum date time value.

NextRaise

This column displays the date and time when the Timer is next scheduled to elapse. If the Timer has never been enabled, this column may also show a default minimum date time value. If a timer's start time has passed but the end time has not, this will show the end time.

DerivedStartTime

This column displays the time when the event will start. This will shift for day of week (recurring) events as days progress.

DerivedEndTime

This column displays the time when the event will end. This will shift for day of week (recurring) events as days progress.

ElapsedStart

The ElapsedStart column will turn true if the Start time of the Timer has elapsed. If a Timer is set to Autoreset, this value will immediately turn false again.

ElapsedEnd

The ElapsedEnd column will turn true if the End time of the timer has elapsed.

Enabled

This column displays whether the Timer is currently enabled. A Timer that is not enabled will never elapse.

AutoReset

A value of true indicates an Interval Timer set to auto reset. When the Timer elapses, it will automatically update its next raise time and start counting down again.

Click the edit link to change the parameters of a Timer. To delete a Timer, open it with edit and click the trash icon in the editor. Click Add + below the list to create a new Timer. Timers stopped by an execution block (see the Block Execution article) are shown in red.

Additionally, the Cleanup Options link can be used to specify what should happen with non-recurring Date/Time timers that have already elapsed. Clicking the cleanup options link opens the following dialog:

By default, the value is -1, which means Date/Time timers that have completed their execution are not deleted from the system. If you enter a number of days in this dialog and apply it, single-execution Date/Time events are deleted from the system that many days after the timer has completed executing. A value of 0 will cause the timer to be deleted within an hour or two after the timer has completed execution.

Timer Types

To create a new Timer, click Add + on the Timers dialog to open the Timer Editor. Timer names must be unique; names may include characters such as \.

Three types of Timers can be created in Pathfinder Core PRO: Interval, Day of Week, and Date/Time.

Interval Timers

If you want to create a Logic Flow with a delayed action, you could use a delay directly in the Flow, or you could create an Interval Timer. An Interval Timer raises an Elapsed property after a specified number of milliseconds.

Interval Timers can also be programmed to autoreset. An autoresetting Interval Timer will set the Elapsed flag to true after the Interval, and then immediately set it back to false and restart the countdown.

Leave the Autoreset and Enabled properties as false. Type a name for this Timer and apply it.

Now we can use this Timer in Logic Flows. For example, an Interval Timer can be used in a Logic Flow so that when GPI 1 pin 4 goes low, the Flow enables the Timer. Then, 5 seconds later, the Elapsed property causes GPO 1 pin 4 to be set low:

Interval Timers have three additional write-only properties:

  1. Reset: If the Timer is enabled, this property will disable and then re-enable the Timer to start the countdown over. If the Timer is disabled, this will set the elapsed property to false.

  2. ResetStart: Stops the Timer (if it is running) and then starts the Timer to reset the countdown.

  3. ResetStop: Disables the Timer and changes the elapsed state to false.

These are available in the Logic Flows simple tree when an Interval Timer endpoint is selected in the Logic Flow. Because these are write-only properties, they are shown only when Interval Timer endpoints are selected, not start points.

All three properties accept true/false values, and setting any of them to true starts the reset. They do not need to be set to false again afterward, because passing the true value is only a trigger. The value is not retained. Think of these properties as actions rather than traditional properties.

Day of Week Timers

If you want something to happen at a specific time every Monday, you can create a Day of Week Timer. With this type of Timer, you can specify a time and the days of the week on which the Timer should set its Elapsed property to true.

Each Day of Week timer represents a range of time. It has a start time and an end time. In Logic Flows, an Elapsed property and an ElapsedEnd property match the start and end times. If you only want to execute a single action at a specific time, you can use the Elapsed property and ignore the ElapsedEnd property. However, when you configure the event, the end time must be later than the start time.

Instead of, or in addition to, using the timer with Logic Flows, you can specify a change directly in the event itself. Click the ellipsis button next to the start property to open the Import Ios dialog, where you can select a destination.

The Import From drop-down lets you select the router to pick a destination from. Additionally, the Endpoints button in this dialog switches to a property selector similar to the one in Logic Flows, so that you can select some other property, such as a GPIO or console show profile load property:

The Ios button takes you back to audio IO selection. Because audio routing is often used with date/time events, both dialogs are offered for ease of selection. Once the property is selected, the value field will be filled with the current value of the destination's source or property value. Click the ellipsis button next to the value to change the property value that will be applied. For a source, this opens the source list; for other properties, such as a memory slot, it opens the Property Value Selector:

If you only want a change to happen at the start, then do not select a property and value for the end. In the example below, memory slot SlotB will be set to Morning Show at the start time of the event and no change will be made at the end of the event.

The Switch Fields To Advanced link should only be used by advanced users. It changes the input boxes to the literal API commands associated with the selections for manual adjustment.

The clock option buttons are described below, because they apply to both the Day of Week and Date/Time Timers.

Date/Time Timers

If you want something to happen on a specific day and time, you can create a Date/Time Timer. The Timer’s Elapsed property will be set to true at that day and time.

Click the calendar icon to open a calendar for setting the date and time. This event has the same parameters as the Day of Week event above for selecting properties to change at the start and end time of the event. The primary difference is that this event executes its start and end times only once at the specified date and time. It will then be deleted or retained according to the settings in the cleanup options above.

Virtual Mixing Routers and Property Selection

Virtual mixing routers work differently from other routers. For details on Virtual Mixing Routers, see their section in the Routers section of the manual. With virtual mixing destinations, you do not change the source that is routed to the destination. Instead, you add sources that will be mixed together by the mixing destination up to the supported quantity of the destination. As a result, it uses different routing properties than a normal router. For example, AddSource adds a source to the mixing destination, and RemoveSource removes a source from the destination, freeing that slot up for another source. Therefore, when importing a destination as a property change in a timer event, you need to define whether the change will add or remove a source. To support this, a Mixing Property drop-down appears in the import destination list when defining a start or end property in a timer.

The Mixing Property drop-down lets you select whether the operation adds a selected source to the destination or removes it. For example:

In this example, the timer will add the Phone source to the destination at the start of the event time range, and it will remove it at the end.

Clock Time and Fixed Time

In both the Day of Week and Date/Time Timers, it is important to understand the difference between clock time and fixed time. Within Pathfinder Core PRO, all times are stored with a UTC offset. Clock time means that the event will happen at a specific time (say 7 PM) according to the clock regardless of the UTC offset. If you want an event to happen at 7 PM according to what the clock shows both before and after a daylight saving time shift, you should pick the clock time option.

However, if you are picking up a satellite feed and the region from which the feed originates does not shift its clock to daylight saving time, then you should select fixed time because the event will happen at a different time (according to your wall clock) before and after the daylight saving time shift. In this case, it is fixed to the time and UTC offset.

Event Timezone

Day of Week and Date/Time Timers have an Event Timezone. The event's times are read in that time zone, so an event can follow the clock of another region, for example a network feed from another time zone, while the unit keeps its own. With Clock, the event also follows that zone's daylight saving changes.

Check the Event Timezone when you create a timer.

UTC Offset

Previous versions of Pathfinder Core PRO used the browser’s UTC offset when creating a new clock-based Date Time or Day of Week timer. This also caused odd display issues when editing events from a Core PRO in one time zone while using a browser in another. This version always displays the offset of the event and the specific time as it is set in Core PRO. Additionally, new events will be created using the offset defined in Core PRO by its current time zone rather than the browser’s offset.

Using Timers in Flows

In addition to specifying an action to take place directly in the event, you can also connect the event to a Logic Flow. In fact, this is the primary way to use an Interval Timer. To do that, create a Logic Flow with a start point that uses the Timer’s elapsed property to then change some other property in the system. For example, if you wanted to execute a scene change every Monday at a specific time, you would create a Logic Flow that uses the Day of Week Timer shown above.

In this way, we can use Timers to cause delays, do repetitive operations (using the autoreset property of Interval Timers), or execute actions at specific days/times and/or on a recurring daily schedule. This particular example could also be accomplished by selecting the Activate Scene property directly in the event, but to create more complex logic using logic gates, you need to build it in a Logic Flow. Both options are available. However, property changes that are defined within the actual event (as opposed to a Logic Flow) do not count against the logic licensing of the system.