> 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

Test alarm-zone inputs from a Remote Arming Terminal using periodic or manual test modes.

There are two test modes: **Periodic Testing** and **Manual Testing**.

### Periodic testing

This occurs when a staff member authorised for Periodic Test Mode disarms the system via a RAT, then chooses to enter Test mode.

1. Log on to the Remote Arming Terminal.
2. Press the **Disarm** key on the "Choose Action" screen.
3. If assigned the "Prompt for alarm zone selection" privilege, select the Alarm Zone to disarm and test.
4. If the test is optional, press the key to enter Test mode. The "Testing" screen displays.
5. A **countdown timer displays**. With 1 minute to go, options to extend the testing time appear.
6. Check all inputs configured as part of the test (intrusion detectors, duress buttons, raise counter buttons, and so on).
7. Once all inputs are tested, press the key.
8. On success, the "Test successful" screen displays.
9. On failure, the "Test failed" screen lists all inputs that failed.
   * If configured in Command Centre, a **report is sent to the alarm monitoring station and an email is sent to the manager for each failed input**.
10. Press the key, then the key.

### Manual testing

This allows inputs to be tested **without changing the state of an Alarm Zone**.

1. Log on to the Remote Arming Terminal.
2. Press the **More** key on "Choose Action" to reach the "Main Menu".
3. Scroll to "Test Inputs" and press the key.
4. If assigned "Prompt for alarm zone selection", select the Alarm Zone to test.
5. Press the key. The "Testing" screen displays with a countdown timer.
6. With 1 minute to go, options to extend the testing time appear.
7. Check all inputs.
8. Press the key.
9. On success, "Test successful" displays. On failure, "Test failed" displays with a list of failed inputs.
10. Press the key, then the key.

***

🔗 **Related**

* [Keypads - Disarming](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-disarming.md). The disarm step that starts Periodic Testing.
* [Keypads - Viewing Alarms Zones and Inputs](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.md). Check input status and shunt state.


---

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