> 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-remote-arming-terminal-operati.md). # Operate a Remote Arming Terminal Understand Remote Arming Terminal connections, privileges, keys, screens, and communication status. This page covers the fundamentals of operating a Remote Arming Terminal (RAT): how it connects, how privileges work, the keys and screens you use, the System Summary, and using a RAT as a keypad for a reader. The individual actions (logging on, arming, disarming, fence zones, alarms, testing) each have their own page in this section. Everything here applies equally to the **Gallagher Security Fence Keypad**, which is the same hardware under a different name. *** ### Hardware connectivity * Remote Arming Terminals connect to the **Gallagher Controller 6000**, **Controller 3000**, or **Controller 5000GL**. * They can be connected to **Dial-up Controllers** provided that: * the Remote Arming Terminal is local to the Controller, AND * there are no Alarm Zones spanning over multiple Controllers. *** ### Privileges **Operator Group privileges do NOT apply to Remote Arming Terminals.** Operators receive privileges via the **Access Groups they belong to** (Privileges tab of the Access Group properties). These privileges apply to the Alarm Zones assigned to both the Remote Arming Terminal and the Access Group. When you diagnose a permission issue at the RAT, check the Access Group, not the Operator Group. See [Command Centre - Access Groups](/knowledge-hub/products/cc-software/configure/command-centre-access-groups.md) for how to configure privileges, and [Command Centre - Operator Groups & Privileges](/knowledge-hub/products/cc-software/configure/command-centre-operator-groups-and-privileges.md) for the contrast. *** ### Key types * **Soft keys.** Four keys below the LCD screen. Their function changes depending on the screen being used, and is labelled on screen each time. * **Predefined keys.** Fixed function (numeric pad, Back, Cancel, OK). *** ### Communication status icons The communication status icon is shown at the top-left of the LCD. | Icon | Meaning | | ----------------------------- | ------------------------------------------------------------------------- | | Rotating icon | Normal operation | | Communicating icon | Active communication with Controller | | **Flashing alternating icon** | **Fault.** Check all network cables and ensure the correct address is set | *** ### Welcome screen * If "Backlight is always on" is **not** ticked in Command Centre, backlighting is disabled until a key is pressed. * If the keypad is "asleep" (missing info on the screen), press any key to return to idle mode. * If an Alarm Zone is selected on the Advanced property page of the RAT in Command Centre, the **status of that Alarm Zone displays on the Welcome screen**. ![Remote Arming Terminal key layout](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2d27c5b8d93d80920d9b56a50aaaf3ac2ed9b457%2FSECHUB-RAT-ALARMS-01-alarm-list.png?alt=media) *** ### View the System Summary 1. Log on to the Remote Arming Terminal. 2. Press the **More** key on the "Choose Action" screen to reach the "Main Menu". 3. Scroll to **"System Summary"** and press the key. The "System Summary" screen displays. The System Summary shows: * Total number of outstanding alarms * Number of Alarm Zones in secure state (armed) * Number of Inputs or Fence Zones not shunted/isolated * Number of Inputs or Fence Zones shunted/isolated * Current Date and Time Press the Back key to return to the "Main Menu" screen. *** ### Remote Arming Terminal as a reader keypad See [Use a Remote Arming Terminal as a reader keypad](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-as-a-ke.md) for door-access operations and access-zone overrides. *** ๐Ÿ”— **Related** * [Keypads - Logging on](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md). The four ways to log on to the terminal. * [Keypads - Arming](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-arming.md) ยท [Keypads - Disarming](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-disarming.md). Change alarm zone state at the terminal. * [Keypads - Viewing and Acknowledging Alarms](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-and-acknowledging-alar.md). Handle alarms from the terminal. * [Keypads - Viewing the System Summary](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-the-system-summary.md). The System Summary screen on its own page. * [Keypads - Remote Arming Terminal as a keypad for a reader](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-as-a-ke.md). Keypad-mode door access on its own page. --- # 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-remote-arming-terminal-operati.md?ask=&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.