> 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/hardware/creating-inputs-and-outputs.md).

# Creating Inputs and Outputs

Inputs monitor a state, Outputs change a state.

**Note:**

Most of the screen shots in this topic are for an Input, and while they may differ slightly for an Output the procedure is still the same.

1. Click **Configure** from the menu bar, then **Hardware**.

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

   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. Are you creating an Input or an Output?

   If an **Input**, go to Step 7.

   If an **Output**, go to Step 9.
7. Click the **Reflected Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4d15a03a5179922dfa34e1e86808e42bc34d51d0%2Finput_refouttputs.png?alt=media)
8. Drag and drop the appropriate Output(s) into the two grids.

   The top grid lists the Output(s) that reflect the current state of the Input, and the bottom grid lists the Output(s) that reflect the opposite state of the Input.
9. Click the **Messages** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6ec81676e4d80825c1113132c4b795482761752f%2Finput_messages.png?alt=media)
10. Enter the state and event names (if different from the site-wide default), that will display in Command Centre when this Input/Output is activated and deactivated.
11. Click the **Advanced** tab.
12. Are you creating an Input or an Output?

    If an **Input**, go to Step 13.

    If an **Output**, go to Step 14.
13. The Input **Advanced** tab displays:

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

    Select the check boxes as required, then go to Step 15.

    <table><thead><tr><th width="192">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Input is inverted</td><td>If checked, the state of the Input is reversed, (i.e. the system considers the Input 'open' when it is closed, and 'closed' when it is open).</td></tr><tr><td>Input can not be isolated</td><td>If checked, the Input will not be ignored when an Alarm Zone is armed with the 'Isolate' option.</td></tr><tr><td>Input is a six-state device</td><td>If checked, the 6-state EOL Resistance settings will be used for this input. If left unchecked, the 4-state settings will be used.</td></tr></tbody></table>
14. The Output **Advanced** tab displays:

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

    Configure the behaviour of the Output as required.

    <table><thead><tr><th width="192">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Schedule for output activation</td><td>This drop-down list contains all Schedules in the operators Division(s).<br>The Output can be turned on and off at different times of the day by changing the Schedules Output field.<br><br><strong>Note:</strong> The <strong>View Schedule</strong> button beside this field only becomes enabled once a Schedule is selected. When clicked, the <strong>Calendar</strong> tab of the selected Schedule opens.</td></tr><tr><td>Output is pulsed when activated?</td><td><p>Valid range is 1 - 86400 seconds (24 hours).<br>Default = unchecked. When checked the default value becomes 1 second.<br>If checked, the following occurs:</p><ul><li>the <strong>Maximum time for the output to be activated</strong> field is disabled.</li><li>the <strong>Pulse</strong> option is enabled on the Output context menu (via right clicking on the Output from the <strong>Hardware</strong> List Window).<br>Selecting the Pulse option from the context menu activates the Output for the configured number of seconds and then deactivate the Output.</li></ul><p>When this Output is activated (not by manual override), then the Output will stay activated (pulsed) for the configured number of seconds, regardless of whether another event would normally deactivate the Output prior to the pulse time elapsing.</p></td></tr><tr><td>Maximum time for the output to be activated</td><td>Defaults to 0 seconds, and the maximum value is 86400 seconds (24 hours).<br>If a value greater than 0 is entered is this field, when the Output is activated (not by manual override), then the Output will deactivate when the configured number of seconds has elapsed, unless the Output is deactivated before that time.</td></tr><tr><td>Siren behaviour</td><td><p>This allows the operator to specify:</p><ul><li>if they want each input in an Alarm Zone to <strong>Activate output once only per source until alarm is acknowledged</strong>, (i.e. an action that would turn off the output if it was turned on due to an alarm source. With default Action Plan configuration, this includes disarming the Alarm Zone as well as acknowledging or processing an alarm).</li><li>the reset time, (i.e. <strong>Allow output to activate again after xx minutes of being inactive</strong>).<br>The siren is allowed to re-activate after this many minutes as soon as any alarm happens (i.e. there is no restriction on it having to be from a different source).<br>Default = 20 minutes, and the range is 1 - 720 minutes.<br><br><strong>Note:</strong> The Reset time is ignored when the output is triggered by a manual override. The time resets each time the output is triggered.</li></ul><p>See the siren behaviour diagram for further explanation of this functionality.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-33fd151b4150a0d0e9efcd5e2b9cb232ac18f5e1%2Foutputsirenbehaviourdiagram.png?alt=media" alt=""><br></p></td></tr><tr><td>Output is inverted</td><td>If checked, this reverses the behaviour of the physical Relay only, (i.e. When an inverted Output is turned ON in Command Centre, the Relay is de-energised. When an inverted Output is turned OFF in Command Centre, the Relay is energised.<br>The messages and status of the inverted Output in Command Centre do not change:<br>Output ON always = <img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ef2e9c6995b746615fe7e11ba477e32bdbef662b%2Fstandardoutputon.png?alt=media" alt=""><br>Output OFF always = <img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7613e7955563b28ab6fbc754fd9672aa258648e4%2Fstandardoutputoff.png?alt=media" alt=""></td></tr><tr><td>Mapping to an Input state</td><td>Allows you to specify the default state translation to be used when the Output is used in place of an Input, (i.e. when the Output is used where an Input is expected). When the Output is used where Command Centre expects an Output, the Output’s Mapping to an Input state setting is not applied.</td></tr></tbody></table>
15. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Input/Output.

    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).
16. Click the **Icons** tab if you want to change the Icon Set for this Input/Output.

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

    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).
18. Click the **Notes** tab if you want to add a note(s) about this Input/Output.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
19. 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.

### Hint

{% hint style="info" %}
**Manual Overrides**

Manual overrides of Outputs to ON or OFF (either from the Outputs context menu, from the Output properties **Status and Overrides** tab, or by a Macro), are not affected by the time values on the Outputs **Advanced** tab.

<table><thead><tr><th width="290.22222900390625">If a manual override is performed from...</th><th>then...</th></tr></thead><tbody><tr><td>the Outputs context menu</td><td>it will remain until the next schedule change (if the Output has a Schedule assigned), otherwise the override will remain until some other event turns the Output OFF, (e.g. an Input closing, a cancel override, etc.).</td></tr><tr><td>the Outputs <strong>Status and Overrides</strong> tab</td><td>it can be configured either until the next schedule change or for a set period of time (maximum 23 hours, 59 minutes).</td></tr></tbody></table>

You can also configure a Macro to run a Pulse override on an Output, in which case the Pulse time on the Outputs **Advanced** tab is used.
{% endhint %}


---

# 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/hardware/creating-inputs-and-outputs.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.
