> 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/assigning-z20-and-d10-sensors-to-a-controller-6000-or-7000.md).

# Assigning Z20 and D10 sensors to a Controller 6000 or 7000

### Introduction

This procedure describes how to assign either a Z20 Disturbance Sensor or a D10 Tautwire Sensor to a Controller 6000.

**Note:** A maximum of 32 (Z20 and D10) sensors can be connected per BUS to a Controller 6000, (i.e. a total of 64 Z20 and D10 sensors can be connected per Controller 6000).

***

### Procedure

To assign a sensor to a Controller 6000, perform the following procedures in Gallagher Configuration Client:

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. **Double click** on the Controller 6000 you want to assign the sensor device to.

   By default the **General** tab displays.
3. Click each tab in turn to assign the sensor:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fa55cd4a5e808b5d5c11b4a66913d76eb5a81bec%2Fftc6000_assigningsensordevices1.png?alt=media)
2. Select the Sensor from the RS-485 Bus 1 drop-down list.

   The tabs Sensor Devices 1 1-16 and Sensor Devices 1 17-32 appear, allowing you to now add up to 32 Sensor Devices to the Bus 1 port of this Controller.

   **Note:** If you want to assign Sensor Devices to Bus 2, configure the Bus 2 port as above. The tabs Sensor Devices 2 1-16 and Sensor Devices 2 17-32 will appear.

</details>

<details>

<summary>Sensor Devices 1 1-16 tab</summary>

1. Click the **Sensor Devices 1 1-16** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cf2cb6daffca22334e3fa517a872c80f1363a6f4%2Fftc6000_assigningsensordevices2.png?alt=media)
2. Assign the sensor to the appropriate device address by selecting it from the relevant drop-down list. The device address in Command Centre should be the same as the address configured for the sensor.

   **Notes:**

   * Two sensors with the same address must not be connected to the same BUS. They can however be connected to different BUSes.
   * We recommend you do not use Device 1 address, so it can act as a buffer if needed in the future.

     Sometimes when sensors go offline their address resets to 1. If this happens, performing a "Re-assign from Address 1" override (via the **Status and Overrides** tab of the sensors properties) will re-address the sensor correctly.

     Misaddressed Z20 Disturbance Sensors can be corrected by performing a 'Reset Z20 address to 1' override, which will re-address the sensor to 1.

     **Important:** A 'Reset Z20 address to 1' override should only be performed on one device on a bus at a time, otherwise all devices will go offline.

</details>

4. 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 sensor device has been assigned to the Controller 6000.

**Notes:**

* The address of the sensor now appears on **Connections** tab of the sensor's property pages.
* The sensor's version number now appears at the bottom of the sensor's **Configuration** property page, (e.g. Device Version: v0.22).


---

# 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/assigning-z20-and-d10-sensors-to-a-controller-6000-or-7000.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.
