> 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/z10-tension-sensor-g13110-may-2021.md).

# Z10 Tension Sensor variant change — May 2021

Review the Z10 Tension Sensor replacement introduced in 2021.

The **Z10 Tension Sensor** provides real-time tension measurement of a fence wire, detecting wire disturbance during an attack on the fence line.

Recent changes improved **High Voltage fence compatibility**, making it suitable for use with F4 series fence energisers. A new variation was released as a **direct replacement** for the existing product (G13110).

**Replacement product: G13115, Z10 Tension Sensor - TVS.**

There is **no price change** as a result of the product improvements. All product supplied going forward is the new variant.

Price lists were updated and the older product removed. A substitution is in place within sales order management systems, so any pending orders for the older product are changed to the new variant (G13115).

***

🔗 **Related**

* [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices.


---

# 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/z10-tension-sensor-g13110-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.