> 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-monitoring-fence-controller-te.md).

# Monitor fence controller temperature

View current and seven-day fence controller temperatures from a compatible Remote Arming Terminal.

> 📎 **Compatibility:** F31, F32, F41, F42 or F22 Fence Controllers ONLY.

**Required:** the cardholder must belong to an Access Group listing the Alarm Zones assigned to the Fence Zones.

### Procedure

1. Log on to the Remote Arming Terminal.
2. Press **More** on "Choose Action" to reach the "Main Menu".
3. Scroll to "Fence Zones" and press the key. The "Fence Zones" screen displays.
4. Scroll to the Fence Zone and press the key. The "Voltages" screen displays.
5. Press the key (Temperatures soft key). The "Temperatures" screen displays.

### Temperature screen details

* Fence name
* Current temperature (of the Fence Controller this fence is assigned to)
* Lowest temperature recorded within the last 7 days
* Highest temperature recorded within the last 7 days

Fence channels are displayed under their item name, for example "North Fence". The Back key returns to the "Main Menu".

***

🔗 **Related**

* [Keypads - Monitoring Fence Zone voltages](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-monitoring-fence-zone-voltages.md). Voltages for the same zone.
* [Keypads - Monitoring Fence Zone status](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-monitoring-fence-zone-status.md). Mode and status codes.


---

# 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-monitoring-fence-controller-te.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.