> 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-virtual-output.md).

# Creating a new Virtual Output

### Introduction

Normal (or 'real') outputs are relays that activate any number of things, (e.g. alarms, light switching, doors unlocking, etc.). Virtual Outputs are used as an input to a Logic Block without going to the expense of creating a real output. When a real output goes to a Controller, a device is activated. With a Virtual Output, the Controller is aware that the output is not to trigger a physical action.

### Procedure

1. The procedure for creating a Virtual Output is basically the same as creating a real output. Therefore, refer to [Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md) for the steps required.

   **Note:**

   On the **Advanced** tab of the Output properties there is an 'Output is inverted' option. This feature does not apply to Virtual Outputs, as it reverses the behaviour of a physical relay.
2. From the **Hardware** List Window, open the Controller that the Virtual Output is to be assigned to.
3. Click the **Virtual Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c0743733ca815eaf18d9a9f3d92c2bfe44a31034%2Fftc_virtualoutputstab.png?alt=media)
4. Drag and drop the Virtual Output you have just created into the grid on this screen.

   **Note:**

   Outputs assigned to this grid are automatically removed from any other Controller's Virtual Outputs grid, or from its physical slot on a Controller or device.
5. Click **Apply**.

### Result

A Virtual Output has been created.


---

# 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-virtual-output.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.
