Table of contents
- Creating a sequence
- Editing a sequence
- Action types
- DALI command
- DALI arc level
- DALI emergency command
- Profile function
- General function
- Warn function
- Override function
- Store level to scene (memory dim)
- System variable
- Copy between two targets
- Restore from database value
- Colour function
- LED function
- Colour change (tuneable white sequences only)
- Set dim time (tuneable white sequences only)
- Set arc nudge method (tuneable white sequences only)
- Set arc nudge from system variable (tuneable white sequences only)
- Tridonic DGC occupancy sensor/light sensor/IR remote (relevant Tridonic DGC sequences only)
- Run Pharos trigger
- DMX function
- Sequence templates
- Tunable white
- Central battery
- Tridonic DGC
A sequence is a list of actions which can be triggered via switches, sensors and other means. For more information on triggers, visit the FAQ on them. Sequences can be as complex or as simple as required but require a good understanding to unlock the full potential of them.
Sequences are located under the Triggers & sequences perspective in the grid view. Creating a new sequence can be done by editing the label field of the last row. Sequences require a label and type to be created. The sequence editor is opened by default after creating a sequence unless the checkbox to do so is unchecked.
Sequence templates can also be used when creating a sequence to populate the sequence with predefined actions for the particular use case that the template is designed for. Checking the From template checkbox will display a dropdown of sequence templates that have been designed by zencontrol. Clicking any of these options will update the label of the sequence to the one provided from the template. A description of the template will also be displayed. Different sequence types can potentially contain different sequence templates.
If you created the sequence using a template then you will have actions populated for you already otherwise the sequence will be created as a blank slate with no actions.
Sequences can be created with different types. Some action types are only available for certain types of sequences and others are purely used for categorising sequences and have no other effect.
These sequences types are all standard types and are used for categorising sequences. These sequence types will have all of the standard actions available. There are many different applications for these sequence types as they have many action types available for use.
A comfort sequence has the same actions available as the standard types but a comfort sequence is designed to be used with a comfort trigger and target. It cannot be used with any other trigger type other than a comfort trigger type. See the Human Centric Light (HCL) FAQ for more information about comfort triggers.
This sequence type includes action types specific to tuneable white fittings such as colour temperature and intensity change actions. This sequence type can only be used in conjunction with the tuneable white trigger type.
This sequence type can only have a maximum of 15 actions set for it.
Tridonic sequence types are designed for configuration of Tridonic DGC based products only. They contain available actions specific to the type selected. They can only be used with trigger types that correspond to the sequence type.
Sequences can be edited using the sequence editor. The sequence editor can be accessed by clicking either of the two pencil icons on a sequence row or opening the actions dropdown. Actions can be reordered by clicking the row number on the left to select the whole row and then click and drag the row number up or down the list.
An action has two main parameters, a delay in seconds and a command to send. Each action will count its delay before executing the command.
If a sequence is running and a profile change occurs and the sequence is still valid in the new profile (ie, there is a trigger entry for both profiles for this sequence), the user can set a profile change action to jump to, upon entering this profile. The most common application for this is a during hours / after hours migration where there is a desire for all occupancy controlled rooms (that are still on) to go into "warn", regardless of where they are, when transitioning to after hours.
When a sequence is triggered again whilst it is already running it will run the override behaviour for the current action that the sequence is executing. This is usually going to a different action but can also be ignored so the sequence will continue to run from where it currently is.
The delay columns have a type and value. If the type is set to seconds then the delay will be a number in seconds before the action is ran. If the type is set to percentage of day light then the number will be a percentage of time between sunrise and sunset.
Conditions specify what requirement must be met in order for the action to run - otherwise, the prescribed action will be skipped and the sequence will continue on to the next action instead. This is evaluated after the delay. This is generally a one-time evaluation, but the user can set the checkbox Block until condition true which will wait until the condition requirements are met.
The action is what will happen when the sequence reaches this point after the delay time has been exceeded and the conditions for this action are met. There are many types of actions that can be set in a sequence which allows for many scenarios that sequences can be useful for. The available actions may differ based on the type of sequence set. The different action types are listed under this section.
A remote target can be set for a sequence which will execute the action on the selected target. This field cannot be set for tuneable white or comfort sequences. This function became available in firmware version 0.11 and will not function on previous versions.
The conditions for the action will be evaluated on the target control system that the sequence is targeting, not the control system that is running the sequence. If you wish to send an action to a remote target as a result of a local condition, two actions will be required.
Action 1: Evaluates local target condition and jumps to a new action
Action 2: Run remote target action (ie, GO TO SCENE 2)
Once the action has been run (or skipped by not meeting conditions) it will run the behaviour specified in the post action field.
There are many different action types that can be selected in the sequence editor. Some action types are only available for certain sequence types. Some action types have a regular type and an override target type. The regular type will use the target that is passed in from the trigger to run the action on. If an override target action is selected then the action command will run on the specified override target instead.
A selection of DALI specified commands.
Sets the arc level of the target to the given value. If enable dim time is checked then will dim to the given level over the specified number of seconds.
A selection of DALI specified emergency commands.
Contains actions for changing to a profile or returning to the scheduled profile. If the profile selected to change to is already the currently active profile it will be reloaded and the profile on entry triggers will be triggered again. Unless the action selected ignores priority then you will not be able to enter a different profile that has a higher priority than the currently active profile.
Contains miscellaneous functions that are not specific to other categories.
The trigger standard sequence action will not re-trigger the same sequence if it is a standard sequence that is currently running and will just ignore the action.
Warn functions are used to specify to the control system that the group is about to time out in occupancy. This ensures that light sensor dimming will not occur during this time. This can be set to recall min or to go to a specific arc level.
Locks out the specified target for a given amount of time. A delay time of 0 will remove the override if possible.
Stores the current arc level to scene 15 which is the memory dim scene.
Contains functions for system variable functionality. The commands are used for storing/restoring values to system variables or setting them to specific values. These are useful for storing values for use later on in the sequence or in other sequences to compare the value in a condition check for an action.
Used to copy the current value of a property from one target to another.
Restores the value of a property to a target from the stored value. Can be used if the value was copied from another target and you want to restore the currently stored value instead.
Includes a range of colour functions to be used with DT8 devices. Some of the functions contain an optional dim time. This dim time is an independent for each channel which can have varying values or delays. The dim time will be executed after the delay for the action has been executed. Subsequent dims can still be executed whilst the first dim is running. The dim time and delay between subsequent dims must be considered when using these functions.
If a sequence is cancelled through another sequence or a cancel on trigger then any running dims will also be discontinued. If a sequence ends naturally it is possible for a dim to continue running and there is no way to cancel it. If this behaviour is undesirable then an action must be inserted at the end of the sequence to keep the sequence alive until the dim has ended.
Sets the LED state of a switch or absolute input using either the inherited target taken as input by the sequence or a direct instance target.
Changes the colour of the fitting to the specified temperature and intensity using the given transition of fading between the colour or going straight to it. There are two other actions for changing only the temperature and another for changing only the intensity. When a target is under intensity control via a tuneable white sequence, any occupancy sequence ON commands will be modified to use the current intensity specified in the sequence, allowing seamless integration with other sequence functionality.
Sets the dim time period for colour change transitions.
This action is to be used in conjunction with set arc nudge from system variable. This action should be set at the start of the tuneable white sequence along with set arc nudge from system variable.
Sets the specified arc nudge method which will step up if the lux goes up by the given amount/percentage or will step down if the lux goes down by the given amount/percentage. If the inverted checkbox is ticked then this behaviour is inverted - it will step down if the lux goes up by the given amount/percentage or step up if the lux goes down by the given amount/percentage.
The amount in which the fitting steps up or down as well as which system variable to read the lux level from is specified in the set arc nudge from system variable action.
This action is to be used in conjunction with set arc nudge method. This action should be set at the start of the tuneable white sequence along with the set arc nudge method.
This action will step up or down if the lux value that is stored in the given system variable changes by a certain amount which is specified in the set arc nudge method action that should be set along with this action. The step count is how many steps to step up or down when the arc nudge method is condition is met. The period is a time in seconds that specifies how long the arc nudge is ran for until the arc value is reset back to the projected arc level dim for the tuneable white sequence.
For more information on Tridonic DGC functionality, refer to the Tridonic website.
For example, to run Pharos trigger 6 with a target of 192.168.1.100 Port 8888 the controller will send "start_timeline_00006\r" to IP address 192.168.1.100 at Port 8888.
Turns the lights off after the given amount of minutes if there is no activity detected on the sensor after going to warn level for 1 minute. It relies on the sequence being called whenever a sensor is triggered although can be used on a switch for running the sequence onec. The action overrides will reset the delays back to the start when it is triggered.
Similar to the above default template except it will store the current levels to the memory dim scene, use recall min instead of go to warn and recalls the memory dim levels when the sequence is triggered.
A very simple sequence that showcases how logic can affect the flow of a sequence. Generally won't be used in a real world case but is useful for getting an idea of how you can use logic in your own sequences.
Designed to be used for a profile on entry sequence. It will turn off any lights that are currently turned on. Useful for when your running sequence requires the lights to be in a certain state at the start of the sequence.
Similar to the above cleanup sequence but recalls min for 60 seconds before the off command is sent.
Disables automatic lighting control from PIR sensors and enters scene 0. Useful for meeting or presentation modes where you want the lights to be at a certain level and in a certain scene. Should be used in conjunction with exit meeting mode sequence template below to restore automatic lighting for PIR sensors.
Should be used in conjunction with the above enter meeting mode template. Used to restore automatic lighting control for PIR sensors after your meeting or presentation has concluded.
Turns the lights off after the given amount of time of inactivity, simulating absence. Should be used on sensor that are in presence mode as absence mode sensors should work as normal without this template. Will recall min as warn for 1 minute before turning off.
Turns off any lights after some time if no motion is detected. If the target has already been unoccupied for some amount of time when the sequence starts then it will turn them off straight away. The lights will turn to warn a short time before they are completely turned off. If movement is detected during this sequence, it will continue to the normal profile instead of turning off any lights. This template is design to be used in a profile on entry sequence.
Changes the colour temperature of the lights over the course of the day to follow a circadian rhythm. The lights will start off in a warm white, slowly change to a cool white around the middle of the day and end on a warm white towards the end of the day. This will help to emulate natural sunlight in otherwise unnaturally lit indoor environments that can help boost alertness, productivity and more.
Tests a central battery system but keeping it on for the duration and ensuring that it doesn't fail by losing power at any point or any other fault. There are some requirements for this sequence to run without issues. For more information on setting up central battery tests, visit our FAQ.
Similar to the above duration test template but runs on a very short duration to test that the system is functional rather than ensuring that the system will run for a given duration.
Commissions a Tridonic DGC occupancy sensor using the given values. These are commonly used values that should fit most cases but they can be altered for certain circumstances.