> 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/products/product-advisories/historical-notices/perimeter-solutions/detection-technologies-vibrasector-changes-may-2021.md).

# Detection Technologies - VibraSector changes - May 2021

Review updated VibraSector cable, gate, and zone limits for perimeter estimates.

### Notification

We have recently been advised of some changes in the application limits with the VibraSector Products we are distributing in the market, these changes will potentially impact on current estimates submitted to customers. These changes have been provided by Detection Technology and are as follows:

1\. Total loop length (sensor + dead cable) shall not exceed 1,250m (4,100’) – refer image below for impact on return loop scenario.

<figure><img src="https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2FhY5O8HDYrEPgoFukVtAQ%2Fimage.png?alt=media&amp;token=0d8e390b-161f-45f3-9afb-c8a13b1737a8" alt=""><figcaption></figcaption></figure>

2\. Total Length of sensor cable shall not exceed 1,000m (3,280’).

3\. Number of gate kit connection shall not exceed 4 (2x double leaf gates) per analyser.

4\. Total number of zones per analyser shall not exceed 25 – currently we recommend no more than 10 to remove the need for external relay card and non-encrypted communications.

For sites that are estimated to be impacted by these limitation changes please reach out to your Gallagher representative and we will work through the impact and required changes directly with Detection Technologies


---

# 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/products/product-advisories/historical-notices/perimeter-solutions/detection-technologies-vibrasector-changes-may-2021.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.
