> 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/site-installation/doors/lock-cycle-counting-setup.md).

# Lock Cycle counting setup

### Lock Cycle Counting Overview

Lock Cycle Counting helps monitor how often a door lock is used, allowing proactive maintenance before failure.

### Configuration Options

The **Lock Cycle Counting** tab is available on the Door Properties page and works only on doors connected to a Controller 7000.

**Note:** The settings will always be available, but the lock cycle count will not increase on doors connected to a Controller 6000.

<table><thead><tr><th width="267">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Lock cycle count</td><td>Current number of lock/unlock cycles. Increases automatically.<br>(Editable field from 0 to 100000000)</td></tr><tr><td>Lock cycle limit</td><td>Max recommended cycles before maintenance.<br>(Default = 400,000. Editable field from 0 to 100000000)</td></tr><tr><td>Alarm threshold percentage</td><td>Percentage of the configured limit at which to raise the first alarm.<br>(Default = 80%. Editable field from 0 to 100%)</td></tr><tr><td>Enable lock cycle counting alarms</td><td>Checkbox to activate lock cycle alarms.</td></tr></tbody></table>

Clicking the **Apply** or **OK** button will confirm and save all changes made to the editable fields and checkbox.

### Alarm Behaviour

* An *"Approaching configured lock cycle limit"* maintenance warning alarm is generated when the threshold percentage of the limit is reached (medium-high priority).
* A stateful *"Configured lock cycle limit reached"* lock cycle warning alarm is generated when the limit is reached (medium-high priority).


---

# 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/site-installation/doors/lock-cycle-counting-setup.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.
