> 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/configuration-client/licensable-features/perimeter-fence-controllers/creating-a-temperature-report.md).

# Creating a Temperature Report

### Introduction

This procedure is applicable for the F31, F32, F41, F42 and F22 Fence Controller only. The Temperature Report details the temperature readings measured within the Fence Controller, and uses the settings configured on the **Data Logging** tab of the relevant Fence Controller.

You need to be in the same or parent Division of the Division holding the Fence Zone, and have the "View Site" operator privilege to perform this procedure.

**Note:** The Temperature Report is only supported when the screen resolution is 1024 x 768 or higher. While it will run against a lower resolution, the results cannot be guaranteed

### Procedure

1. Click **Reports** from the menu bar, then **Report Descriptions**.

   The **Report Description** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Temperature Report**.

   The **Reporting Dates and Times** page of the Temperature Report wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-44ff58afb21e8b14a90ef5e3493c239a8416fb08%2Ftemperaturerpt1.png?alt=media)

   This page allows you to enter a start and end time for the report. Pre-defined periods are provided for simplicity, or custom start and end times can be entered.
3. Configure the period required for the report, and click the **Next** button.

   The **Choose the item that you wish to report on** page displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-790768b1c4e218ac48609bf45127151e31d4ab42%2Ftemperaturerpt2.png?alt=media)
4. Select the Fence Controller to report on from the drop-down list.
5. Click the **Next** button.

   The **Report Generation and Saving** page displays. This wizard page is the same for all report types, and provides the same options. Refer to [Report Generation and Saving](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md) in the *Creating a new report* procedure for further detail.

### Result

The temperature readings measured within the Fence Controller are displayed on screen as a line graph, which can be printed out, or saved to file as a CSV format.


---

# 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/configuration-client/licensable-features/perimeter-fence-controllers/creating-a-temperature-report.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.
