> 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-sensors/performing-a-log-tuning-data-override-on-a-z20-disturbance-sensor.md).

# Performing a 'Log Tuning Data' override on a Z20 Disturbance Sensor

### Introduction

Log Tuning Data mode on a Z20 Disturbance Sensor is used for maintenance checks and fault finding. During Log Tuning Data mode, Command Centre monitors and records the Dynamic Threshold value of a Z20 Disturbance Sensor.

This procedure describes how to perform a ‘Log Tuning Data (48 hours)’ override on a Z20 Disturbance Sensor.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** the appropriate Z20 Disturbance Sensor, and click **Override...** from the drop-down menu.

   The **Status and Overrides** tab on the Properties window for the item displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c33a31bb1da7fc16ec8d295108ffc1bf9724f9be%2Fz20sensor_statusoverridestab.png?alt=media)
3. Click within the Override field and select **Log Tuning Data (48 hours)** from the drop-down.
4. Click the **Override Now** button.

   From this screen you can see the status change from ‘Normal’ to ‘Logging Data’ as a result of the override.
5. Click the **OK** button.

   This override will last for up to 48 hours or until it is cancelled.

   Sensors that are overridden this way will raise an alarm that stays active until the override is cancelled or it times out.

   **Note:** A report can be run from Command Centre Client, (i.e. not Configuration Client) that displays the data recorded over the 48 hours.


---

# 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-sensors/performing-a-log-tuning-data-override-on-a-z20-disturbance-sensor.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.
