> 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.md).

# Configuring a Z10 Tension Sensor Group

### Introduction

This procedure describes how to configure a Z10 Tension Sensor Group.

Sensors must be grouped by fence, (e.g. North Fence Sensor Group). By grouping sensors you can logically identify the sensors belonging to a specific fence. This allows for easier monitoring and maintenance of individual fences on your site.

**Notes:**

* Multiple sensor groups can belong to one fence.
* A maximum of 64 Z10 sensors can be connected to a Controller 6000 and 7000; either all off the same HBUS port, or spread over two.
* A maximum of 55 sensors can be assigned to a sensor group.
* The sensors belonging to a sensor group cannot span multiple Controllers.
* The maximum constant tension rating for a sensor is 60 kg.
* The maximum tension rating for a sensor is 200 kg.
* To change the measurement units, (e.g. metric to imperial) select the **Measurement Units** tab in the **Server Properties**.

***

### Before you begin

Ensure all sensors for this group are connected to the same Controller. Once connected, the sensors will appear as un-configured devices on the **HBUS Devices** tab in the Controller's properties.

***

### Configuration

To configure a Z10 Tension Sensor Group, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Z10 Tension Sensor Groups**.

   The **Z10 Tension Sensor Group** List Window opens.
2. **Right click** and select **New\...Z10 Tension Sensor Group.**

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure the Z10 Tension Sensor Group:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f722e238c3f8ca75dfa2dff9662d876d15c8f656%2Fdts_connections_tab.png?alt=media)
2. Select the appropriate Controller from the drop-down list, (i.e. the Controller that the sensors in this group are connected to).

   **Note:** Once the sensor group has been configured, and the **Apply** button clicked, the version of sensor code stored on the selected Controller displays in the **Configured Version** field. This version of code will be automatically downloaded to all sensors belonging to this group. The Serial number and Version of code for each sensor belonging to this group is then displayed.

</details>

<details>

<summary>Fence Configuration tab</summary>

1. Click the **Fence Configuration** tab.

   This tab allows you to define the configuration of your fence.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-749b14e541b53baee000e1a5e27a530a259b0003%2Fdts_fenceconfiguration_tab.png?alt=media)
2. Configure the fields as required:

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Length</td><td>This value indicates the length of the fence. This value will alter the attack alarm threshold. (Default = 0.0 meters. Range = 0.0 meters to 304.5 meters)</td></tr><tr><td>Bay Width</td><td>This value indicates the length of each bay (space between intermediate posts). If you have bays of varying lengths, this value should be set to that of the largest bay. This value will alter the attack alarm threshold. (Default = 0.0 meters. Range = 0.0 meters to 30.4 meters)</td></tr><tr><td>Springs per Wire</td><td>This value indicates the number of springs per wire. You will need to specify the spring type used to enable this field. This value will alter the attack alarm threshold. (Default = 0 springs. Range = 0 springs to 9 springs)</td></tr><tr><td>Wire</td><td>Select the wire type used. This value will alter the attack alarm threshold.</td></tr><tr><td>Spring</td><td>Select the spring type used. This value will alter the attack alarm threshold.</td></tr><tr><td>Historic Temperature Range</td><td>These values indicate the minimum and maximum temperatures the fence may be subjected to. These values will alter the tension range. (Range -100 ºC to +100 ºC)</td></tr><tr><td>Offset</td><td>Specify the shift (offset) in tension range. (Range = 0 kg to 60 kg)</td></tr><tr><td>Attack Alarms</td><td>When this value (wire movement) is exceeded an attack alarm is raised in Command Centre. Most likely you will receive an alarm before this value is exceeded.</td></tr><tr><td>Maintenance Alarms</td><td><p>These values indicate the maximum and minimum wire tension that must be exceeded before a maintenance alarm is raised in Command Centre.</p><p><strong>Notes:</strong></p><ul><li>You will need to ensure you have configured the Maintenance Alarm limits to accommodate fluctuations in temperature and tension. If the Maintenance Alarm limits are tightly bound to the target tension range, then a high occurrence of maintenance alarms may occur. On the other hand, by having Maintenance Alarm limits set wider than the target tension range, there is a risk of wires requiring tensioning, being overlooked.</li><li>For a maintenance alarm to be raised, the condition must exist for more than 30 seconds. A hysteresis of 1 kg applies.</li></ul></td></tr></tbody></table>

   When configuring the tension span, you will be warned if:

   * The tension range exceeds the sensor tension rating. The maximum constant tension rating for the sensor is 60 kg.
   * The tension range exceeds the wire yield point. This may cause stretching for the wire selected.
   * The attack deflection could raise the tension over 200 kg. The maximum tension rating for the sensor is 200 kg.

</details>

<details>

<summary>Sensors tab</summary>

1. Click the **Sensors** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6c49268ff3ce65df58022927833630f8c4275c53%2Fdts_sensors_tab.png?alt=media)
2. Open the properties of the Controller that the sensors are connected to, and click the **HBUS Devices** tab.

   The sensors connected to this Controller are displayed.
3. Select the appropriate sensors for this group, and drag and drop them into the grid.

   **Notes:**

   * If required, you can add sensors to this group, by selecting a sensor from the **Serial** drop-down list. This drop-down lists all sensors assigned to the selected Controller, that have not been assigned to a group.
   * Once the sensors have been assigned to this group, and the **Apply** button clicked, the Tension, Temperature, and Status for each sensor belonging to this group displays in the grid.
4. Assign each sensor to the appropriate wire, by using the **up** and **down** arrow buttons below the grid.

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this sensor group.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this sensor group.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this sensor group.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this sensor group.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

A Z10 Tension Sensor Group has been configured.

When first configured a Maintenance Mode override will be in effect. This is represented by the icon overlay (yellow screw driver). Once the final tensioning has taken place, you will need to cancel the Maintenance Mode override. The sensor group will then be functioning normally. For details regarding the operation of the Maintenance Mode override, refer to the topic [Performing a Maintenance Mode Override](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-sensors/performing-a-maintenance-mode-override.md).

**Note:** A Site Configuration Report can be generated for a Z10 Tension Sensor Group. This report displays the parameters configured for the group and lists the sensors assigned to the group.


---

# 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.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.
