> 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/configuring-a-z10-tension-sensor-group/fence-configuration-example.md).

# Fence Configuration example

### Introduction

The following example shows the fence configuration for a Z10 Tension Sensor Group. The Tension Span fields (Length, Bay Width, Springs per Wire, Wire, Spring, and Historic Temperature Range) determine the wire tension range for this fence.

### Example

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

### Tension Range Bar

The following table describes the information shown in the tension range bar.

<table><thead><tr><th width="192">Information</th><th>Explanation</th></tr></thead><tbody><tr><td>Tension range</td><td>9 kg to 56 kg (shown in blue). This is the tension range based on the values entered in the Tension Span fields.</td></tr><tr><td>Acceptable tension range</td><td>5 kg to 60 kg. The tension range must be within this range.</td></tr><tr><td>Offset</td><td>This is the shift in fence tension range. In the example above an offset of 2 kg has been entered.</td></tr><tr><td>Ideal tension</td><td><p>In this example the ideal tension for each wire is 27.2 kg (at 28.4 ºC). Wires should be tensioned to this value.</p><p><strong>Note:</strong> The sensors assigned to this item must be connected and online in order to view the ideal tension.</p></td></tr></tbody></table>


---

# 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/configuring-a-z10-tension-sensor-group/fence-configuration-example.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.
