Set the order, delays and interruptions of a Link’nX scenario

In a Link’nX scenario, the actions follow the order of their cards, each preceded by an adjustable wait in hours, minutes and seconds. An interruption rule can also, when the scenario starts, abandon the delayed actions still pending in other scenarios.

Intended for administrators and installers. To add the actions themselves, first follow the scenario creation guide.

Before you start

• The scenario already contains actions. In Scenarios, a row’s name or pencil opens it for editing.
• Check the equipment concerned before changing its sequence.

Order the actions

1. In Actions, locate the cards below the Add the action button. They read from top to bottom.
2. Drag a card by its four-arrow handle on the left, then drop it at the desired position.
3. Check the new order.

Set the wait before each action

1. On each card, fill in Wait in hh:mm:ss format: whole hours zero or greater, minutes and seconds from 0 to 59.
2. Use 00:00:00 to add no wait before this action.
3. Review the card: Wait, duration, then, action name. The delay comes before this action in the sequence; it is not a time of day.

Fictitious example: with 00:00:10 on the first action and 00:00:05 on the second, the sequence waits ten seconds before requesting the first action, then five more seconds before requesting the second.

These delays separate the action requests, without taking into account the equipment’s physical response time or the completion of the previous command. If a command must be finished before the next one, plan a long enough wait.

Remove an action from the sequence

Click the trash can on the right of the card: it disappears from the form immediately, without confirmation. This occurrence is removed from the scenario; the action stays in the general Actions list.

To put it back before saving, select the action again, click Add the action, then restore its position and its delay.

Test an action from its card

The triangle in a circle, to the right of a card, requests an immediate test of this action alone, without waiting for the delay entered on the card or playing the rest of the sequence. Use it only for a deliberate test whose effects are known. After Action is running, check the result on the equipment. If there is no effect, see the execution guide.

Interrupt other scenarios at startup

1. In the Interruption section, use Interrupt the running scenarios when this one starts.
2. Search for a scenario by its name, then choose it. Its name appears in a chip. Repeat for the other targets you want. The scenario currently being edited and the targets already chosen are not offered.
3. Review all the targets. The Remove cross removes a target from this interruption rule.
4. Save with the floppy disk.

When this scenario starts, the delayed actions still pending in the targeted scenarios are abandoned. Actions already executed are not canceled.

Interruption is optional. To remove it, remove all its chips, then save. This removal applies to future starts; commands already interrupted are not restored.

Avoid reciprocal rules without a precise intention. For scenarios requested by the same event:

• if they are set to interrupt each other, neither of them starts;
• if only one interrupts the other, the target does not start.

Check the result

Save the scenario with the floppy disk at the bottom right, then reopen it to review the order of the cards, their delays and the Interruption targets. To validate the complete sequence of an enabled scenario, cause one of its triggers and watch the equipment as the delays elapse.

Troubleshooting

• A scenario stops carrying out its delayed actions: check its delays and the scenarios that target it in Interruption, then see the history.
• An action already carried out remains visible on the equipment after an interruption: this is expected, since the interruption does not cancel actions already executed.
• Do not launch the sequences repeatedly to diagnose an interruption: each launch can control the equipment.

If the result remains unexplained, contact support@can-nx.com with the scenario names, the time, the delays and the actions observed.