> 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/deployment-resources/install-and-commission/wiring-basics.md).

# Wiring basics

Learn core wiring principles for reliable Gallagher hardware installations.

[Compliance & Reference](broken://pages/xT7N7IT3BP4gxJvnsCrN) › Wiring Basics

This section covers wiring Gallagher I/O. It explains how inputs are monitored, what outputs can switch, and the electrical fundamentals behind both.

> 🧭 **Where to start**
>
> * **New to voltage, current and resistance?** → [Wiring Primer](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-primer.md)
> * **Wiring a detector or other monitored contact?** → [Wiring Inputs](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-inputs.md)
> * **Wiring a siren, door control or other switched load?** → [Wiring Outputs](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-outputs.md)

## In this section

| Page                                                                                                         | What it covers                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| [Wiring Primer](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-primer.md)   | Voltage, current and resistance in plain terms, why the default resistor value is 4k7, and how much resistance the cable itself adds. |
| [Wiring Inputs](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-inputs.md)   | Resistor configurations and where to install them, the states each configuration can detect, response time, and cable limits.         |
| [Wiring Outputs](/knowledge-hub/deployment-resources/install-and-commission/wiring-basics/wiring-outputs.md) | What a Gallagher relay output can switch, its voltage and current limits, and how to switch a larger load.                            |

***

🔗 **Related**

* [Input and Output (I/O) Devices](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-hardware/input-and-output-io-devices/README.md). The hardware these inputs and outputs terminate on.

*Source: SECHUB-CR-WIRING-INPUTS, SECHUB-CR-WIRING-OUTPUTS, SECHUB-CR-WIRING-PRIMER*


---

# 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/deployment-resources/install-and-commission/wiring-basics.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.