> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/logic-blocks-and-virtual-outputs/creating-a-new-logic-block.md).

# Creating a new Logic Block

### Introduction

This procedure details how to create a new Logic Block.

***

### Configuration

To configure a new Logic Block, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Logic Blocks**.

   The **Logic Block** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New…Logic Block**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure a Logic Block:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-da55857c07208cd9d5178c0ab988acf8b9cfe5b6%2Flogicblock_connectionstab.png?alt=media)
2. Select the appropriate **Controller** from the drop-down list.

</details>

<details>

<summary>Rules tab</summary>

1. Click the **Rules** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0fa5df8a308e73fbd574aae8435869285aa58897%2Flogicblock_rulestab.png?alt=media)

   The centre of the grid contains 10 rows of up to 10 columns, (i.e. 3 columns display, but more can be added, up to a total of 10). Each row has an item of a type that a logic block rule can be based on (see [Logic Block rules](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/logic-blocks-and-virtual-outputs.md#logic-block-rules)). Each column represents a rule (numbered 1 to 10). The cells of the grid allow states to be selected from drop-down lists that include “Ignore” and the states relevant to the item, (e.g. for a Door, “Free” and “Secure”).
2. Logic items will only be saved if one or more rules are set to something other than "Ignore".
3. Select the appropriate options from the drop-down lists for **If a logic item's state is unknown** and **If the logic is used as an input**.

   **Note:**

   The drop-down list for **If a logic item's state is unknown** includes the options 'Turn Logic Block on' and 'Turn Logic Block off'. If either of these are selected, the output is forced "on" or "off" as applicable, (i.e. it isn't the logic that gets turned on or off).

</details>

<details>

<summary>Timing tab</summary>

1. Click the **Timing** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5d505478ae029b4c045f6f98d445c56c0c0e7a29%2Flogicblock_timingtab.png?alt=media)

   There are six different timing modes available from the **Timing** drop-down list. The default mode is “Logic Block follows the rules explicitly”.

   f you require another timing mode from the default one, select the appropriate option as indicated:

   <table><thead><tr><th width="192">Mode</th><th>Description</th></tr></thead><tbody><tr><td>Logic Block follows the rules explicitly</td><td>The Logic Block will follow the rules explicitly, (i.e. it will be ON while one or more rules are met, and will be OFF while none of the rules are met).</td></tr><tr><td>Logic Block follows rules, with a maximum on time</td><td>The Logic Block will follow the rules, but with a maximum time for which it is turned on, (i.e. it will turn ON when one or more of the rules are met, and OFF when none of the rules are met, but with a maximum on time).<br>When selected, a <strong>Maximum on time</strong> edit box displays, allowing a time in seconds between 1 (default) and 86400 (24 hours) to be selected.</td></tr><tr><td>Logic Block is pulsed when the rules are met</td><td>The Logic Block will pulse when a rule is met for the configured pulse time and then switch off for the configured stay off time, (i.e. the pulse and off time occurs when one or more of the rules are met. Then it remains off until the next time the Logic Block transitions from 'no rules met' to 'one or more rules met').<br>When selected, two edit boxes display, allowing a <strong>Pulse on time</strong> (between 1 second and 24 hours) to be selected, and a <strong>Stay off time</strong> (between 0 seconds and 24 hours) to be selected after the pulse completes.</td></tr><tr><td>Logic Block output has a delayed off time</td><td>The Logic Block’s output will stay ON for the time specified after the rules are no longer met, (i.e. it will turn ON when one or more of the rules are met, and OFF at the specified time, after none of the rules are met).<br>When selected, a <strong>Delayed off time</strong> edit box displays, allowing a delay time in seconds between 1 (default) and 86400 (24 hours) to be selected.</td></tr><tr><td>Logic Block output has a delayed on time</td><td>The Logic Block’s output will be delayed by the time specified, (i.e. it will turn ON at the specified time after one or more of the rules have been met, but only if at least one rule remains met for the entire delay time. It will be OFF when none of the rules are met, and the delay time restarts each time there is a transition from ‘no rules met’ to ‘one or more rules met’.<br>When selected, a <strong>Delayed on time</strong> edit box displays, allowing a time in seconds between 1 (default) and 86400 (24 hours) to be selected.</td></tr><tr><td>Logic Block is latched until cleared by input</td><td><p>The Logic Block’s output will latch until cleared by an input, Logic Block or output (virtual or real). This means it will turn ON when one or more of the rules are met, and OFF when either:</p><ul><li>an input transitions from closed to open, or</li><li>a Logic Block or output transitions to the state that is mapped to “open”.</li></ul><p>The input, Logic Block or output (virtual or real) that resets the Logic Block’s state can be any item defined in Command Centre, subject only to operator privileges. Only one item resets the Logic Block.</p><p>When selected, a <strong>Cleared by input</strong> edit box displays, allowing an input, Logic Block or output to be selected.</p></td></tr></tbody></table>

</details>

<details>

<summary>Reflected Outputs tab</summary>

1. Click the **Reflected Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3cbd5b20d59a9b1bcda861d015b7734c7403056a%2Flogicblock_rfoutputstab.png?alt=media)

   Reflected outputs can be configured on this tab to carry out actions required in response to a rule being met and the Logic Block’s state changing as a result.
2. From the **Hardware** List Window, select the output(s) to reflect the Logic Block’s “On” state.
3. Drag and drop them into the top grid on the **Reflected Outputs** tab.

   These output(s) will turn on when the Logic Block turns on, and off when the Logic Block turns off.
4. From the **Hardware** List Window, select the output(s) to reflect the Logic Block’s “Off” state.
5. Drag and drop them into the bottom grid on the **Reflected Outputs** tab.

   These output(s) will turn on when the Logic Block turns off, and off when the Logic Block turns on.

   **Note:**

   The Find Tool can be used to locate outputs instead of opening the **Hardware** List Window. By selecting **Outputs** (in the "Look in" field) on the **General** tab, you then get some additional search options on the **Advanced** tab to help define your search further.

</details>

<details>

<summary>Messages tab</summary>

1. Click the **Messages** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6a73439a1ae6d68a65b3446df8182cbb8061e7f0%2Flogicblock_messagestab.png?alt=media)
2. Enter the **Event messages** and **State names** (if you require them to be different from the site-wide defaults), that will display in Command Centre when the Logic Block transitions to "on" and "off".

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Logic Block.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this Logic Block.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Logic Block.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this Logic Block.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

A Logic Block has been created.

***

### Duplicating Logic Blocks

Logic Blocks can be duplicated as long as an operator has the edit privilege to the existing Logic Block being duplicated. Any Command Centre items that the operator does not have the view privilege for, that are part of the existing Logic Block’s configuration, will not be copied to the new Logic Block.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/logic-blocks-and-virtual-outputs/creating-a-new-logic-block.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
