> 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/products/cc-software/configure/configuration-scenarios/scenario-pulsing-an-output-using-logic.md).

# Pulse an output using Logic Blocks

Configure two Logic Blocks to pulse an output at a defined interval.

There are many ways to create a pulsing output in Command Centre. This is a simple method using **2 Logic Blocks** that gives a 1-second pulse on and off time, triggered by a single output (it could also be an input or another logic block).

> **Keep it on one controller.** Ideally the input or output should be on the same controller that hosts the 2 logic blocks, to avoid cross-controller configuration.

### Procedure

1. First create two logic blocks with no configuration.

![Two empty logic blocks](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4013af713e14e35d9e62f2012cb222720127aefa%2FSECHUB-CCS-PULSE-01-two-empty-blocks.png?alt=media)

2. Open the **first Logic Block** and add the trigger item (here an input called "Pulse Trigger"), with the rule set to **On**.

![Logic Block 1 trigger set to On](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-136a23d036c1797bee3bf664302a20810b280fb5%2FSECHUB-CCS-PULSE-02-lb1-trigger-on.png?alt=media)

3. Add the second logic block as a rule and set it to **Off** (this stops the logic block from triggering if the second logic block is already on). Then go to the **Timing** tab and select **"Logic Block is Pulsed when the rules are met"**. Set the pulse time required (here, 1 second).

![Logic Block 1 timing set to pulse for 1 second](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-93fe058a40d6fae11a8056dc5aa7669b35a8a719%2FSECHUB-CCS-PULSE-03-lb1-timing-pulse.png?alt=media)

4. Open the **second Logic Block**, go to the **Rules** tab, select the 1st logic block and set the rule to **Off**.

![Logic Block 2 rules: LB1 set to Off](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fd3ed48af129dfdfc1852f252cf2628a01cb4c65%2FSECHUB-CCS-PULSE-04-lb2-rules-off.png?alt=media)

5. Go to the **Timing** tab and select **"Logic Block is Pulsed when the rules are met"**. Set the pulse time required (here, 1 second).

![Logic Block 2 timing set to pulse for 1 second](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3d7a047eacf5050c733807e5547964a81eb98aa5%2FSECHUB-CCS-PULSE-05-lb2-timing-pulse.png?alt=media)

6. Go to **Reflected Outputs** and add the output you wish to pulse.

![Logic Block 2 reflected output](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-296380632a38b9699429ed032edb0a113999c59a%2FSECHUB-CCS-PULSE-06-lb2-reflected-output.png?alt=media)

**Result:** the output pulses on and off at the configured interval.

![Pulse result animation](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8286b7ef63e0a56c59cebc98dacd8f9ad6e8b417%2FSECHUB-CCS-PULSE-08-result-animation.gif?alt=media)

> The pulsed output does not trigger until the Pulse Trigger has been turned on.

![Pulsed output state once the trigger is on](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-183591ae39e46315560e5e2fa5110d59feb07dc9%2FSECHUB-CCS-PULSE-07-final-state.png?alt=media)

### Related links

* [Scenario - Deactivate a Siren after a set time or an Alarm Zone is disarmed](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-deactivate-a-siren-after-a-se.md). A second logic-block recipe.
* [Scenario - Turnstile configuration with 1 door and 2 outputs](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-turnstile-configuration-with.md). Another logic-block use case.


---

# 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/products/cc-software/configure/configuration-scenarios/scenario-pulsing-an-output-using-logic.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.