Scripts

The heart of automation

Scripts form the heart of your layout automation. Your script essentially exists of a sequential set of actions divided into several sections.

For a better overview we recommend you to sort your script in a folder structure.

Configuration

A script can be repeatable, toggling the repeat option lets your skip repeat indefinitely until you manually stop it.

Execution

The execution trigger of your script can either be manual or by event.

Manual triggered scripts

Manual scripts can be triggered from the automation tab

Manual scripts can be started via the automate tab of the throttle or inside a time table.

Event triggered scripts

Scripts can be triggered by events originating from:

  • (layout) accessories

  • time

  • feedback sensors

  • cameras

  • vehicles

  • Or system events like startup or script execution

A script can have multiple execution events, any of these events will trigger a script execution.

Different types of execution events

Event based scripts can also define conditions for execution. Multiple conditions can be defined, you can select AND if all conditions should match or OR if any of the conditions should match before execution.

Different types of conditions

Conditions can be defined for (layout) accessories, feedback sensors, vehicle state or flag state.

Sections

Your script is divided into sections. The purpose of a section is to order your scripts functionally to keep an overview of the potentially many sequential steps. Below is a nice logical division of a script into multiple sections.

You can create, order the sections via the edit and add button in the top bar. Read here for more details around sections.

Examples

As a source of inspiration or better understanding of the features please have a look at the tutorials or the examples.

Last updated

Was this helpful?