Commands and triggers
- 1 Overview
- 1.1 Commands
- 1.2 Triggers
A command is defined as a set of one or more predefined actions that can either be performed by an administrator or as a result of a predefined trigger event. Commands and triggers are found under the Configuration section in the main menu.
Some use cases for commands and triggers include:
- Perform an action simultaneously on a number of doors, a door group, or a combination of both (e.g. block all doors in a section of the building to achieve a "lockdown").
- Interact with an external system (e.g. arm or disarm an intrusion detection system or turn on the lights)
- Allow end users to perform an action normally only available to administrators (e.g. unlock a door or return it to schedule)
When creating a new command, you need to give it a name and define its target:
- Doors. Performs an action on one or more doors. The actions available are the same that the administrator can perform from the door detail page.
- External. Will make an http request to an external system. It is possible to specify the URL, http method, and body.
- Output port. Activate, deactivate, or pulse an output port.
- Controllers. Target the output port(s) of one or more specific controllers.
- Compound. Perform a series of commands of any type listed above. Furthermore, a compound command can also refer to other compound commands (they can be nested). One example usage of compound commands is to create a command which both affects doors and can interact with external systems, e.g. block all doors in one building, turn on a siren connected to an output port, and make an http request to an alarm center.
Performing commands from the administrator GUI
In most cases, it is possible to perform (or "run") the command straight from its detail page:
The exception to this rule is ouput port commands, which need to be started from a controller detail page (see below).
Commands targeting output ports
Configuring commands that target the output port(s) on one or more controllers is a little complicated. First, it is necessary to configure the command(s) with target Output port. It is necessary to specify which output port the command should act on and what the action should be (activate, deactivate, or pulse).
Note that not all controllers have all IO ports (e.g. Axis A1001 only has IO1 and IO2) so it is necessary to know which type of controller that will be used when specifying the output port of the command. It is also necessary to configure the IO ports of the controller.
Command(s) with target output port cannot be performed directly from the command detail page (as it has not been defined which controller(s) they should target). Instead, they can be performed from a controller detail page if the controller has a matching output port configured. The command button(s) will show up under the Actions section for the controller.
Another way to perform an output port command is to specify it as the action of a command with target Controllers and then tie the command to a trigger (see further below). One example where this could be relevant is if the output port of a specific controller has been directly connected to e.g. an alarm panel and it should be possible to arm or disarm the alarm from any of a number of readers.
Note: If no specific controllers are specified, the command will act on the output port of ALL the controllers in the system.
Triggers are a way to start one or more commands. There are two trigger types:
- Door triggers. The trigger is activated by entering a special code on an access control reader, followed by an optional authentication credential (e.g. card or PIN).
- Controller triggers. The trigger is activated when an input port on a door controller changes state.
Setting up a door trigger
Door triggers are activated by entering a special code on an access control reader. First, it is necessary to define which command(s) the trigger should start. A door trigger can start any type of command(s), including both door actions and user defined commands.
Native door actions are applied to the door where the trigger is activated and output port commands are applied to the controller of the door where the trigger is activated. If it is desired to manipulate other doors or other controllers, it is necessary to first create commands with target Doors and/or Controllers.
The next step is to define how to activate the trigger. Door trigger activation codes always start with a * followed by one or more digits. It is recommended to use the same number of digits as for normal user PIN codes minus one, so that the total length of the activation code including the * matches the max PIN length.
Door trigger activation codes need to be unique over the doors in their scope. This means that two different triggers can have the same activation code, as long as the doors they are restricted to (see below) do not overlap. An example of where this can be useful is if a trigger is used to lock down the building where the trigger is used. In this example, users only have to remember one code, but only the doors of the building where the activation code is entered will be affected.
If no credential is specified, anyone can activate the trigger. To avoid this, specify an authentication credential (card or PIN) and which role(s) that should have access to the trigger. Note that in this context, the PIN is the user's PIN, which has nothing to do with the trigger activation code.
Finally, it is possible to define restrictions on the trigger:
- When it can be entered (schedule)
- On which doors it can be entered (doors and/or door groups)
Activating a door trigger
All readers behave a bit differently, however the general process will look like this:
No authentication credential required
- Enter the activation code (e.g. *111).
- Wait for a blinking "success indicator" (will blink for approx. two seconds). The success indicator indicates that the command completed successfully, and will look different on different readers. If the success indicator is not displayed, the command failed to complete all of its actions.
Authentication credential required
- Enter the activation code (e.g. *111).
- Wait for the reader to start blinking (can take a few seconds). This means that the reader has been temporarily blocked and is ready to receive the authentication credential (i.e. card or user PIN) without granting access.
- Wait for a blinking "success indicator" (will blink for approx two seconds). The success indicator indicates that the command completed successfully, and will look different on different readers. If the success indicator is not displayed, the command failed to complete all of its actions.
Setting up a controller trigger
Controller triggers are identical to door triggers with regards to the command(s) they start and the restrictions, but the activation is obviously different. For a controller trigger it is necessary to specify the input port and transition that should activate the trigger.
Just as for commands targeting the output port(s) not all controllers have the same number of IO ports, so it is necessary to know which type of controller that will be used when specifying the input port for the trigger. It is also necessary to configure the IO ports of the controller.