> 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-alarm-input-test-modes.md).

# Test alarm inputs

How alarm zone inputs are tested from a Gallagher T20 Terminal.

A test runs when Test Mode is selected for the alarm zone from the T20, or during disarming.

Test modes are set up in Command Centre for the inputs, the alarm zone, the Access Group, cardholders and the terminal. See Alarm Input Test Modes in the Command Centre Configuration Client user guide.

### Scheduled test

A scheduled test is offered when you disarm, if you are authorized to test inputs. You can enter Test Mode or disarm as usual. If a test is due, it must be performed.

1. Press **Disarm**, then [log on](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md). If the Alarm Zones screen displays, press **Disarm All**. **Testing Scheduled** displays, with the alarm zones whose inputs are to be tested.
2. Press **Yes** to start an optional test, or **Ok** for a test you can't skip. A countdown shows the time set to complete the test, and you can extend it. The terminal beeps every second while in Test Mode.
3. Activate each input in the test, for example PIRs and duress buttons.
4. Press **End**. **Testing succeeded** displays, or **Testing failed** with the inputs that failed.
5. Press **Ok**.

### Unscheduled test

An unscheduled test leaves the alarm zone's state unchanged. No alarms are raised while it runs.

1. [Log on](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md) and choose **Test** from the Menu.
2. Select the alarm zone and press **Test**, or press **Test All**. A countdown shows the time set to complete the test, and you can extend it. The terminal beeps every second while in Test Mode.
3. Activate each input in the test.
4. Press **End**. **Testing succeeded** displays, or **Testing failed** with the inputs that failed.
5. Press **Ok**.

After either test, if set up in Command Centre, each failed input is reported to the alarm monitoring station and emailed to the manager.

***

🔗 **Related**

* [Disarm alarm zones](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-disarming.md). The disarm that can run a test.
* [View alarm zones and inputs](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.md). Check input state and shunts.


---

# 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-alarm-input-test-modes.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.
