> 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/engineering-and-design-reference/deployment-guidelines/hardware.md).

# Hardware

Design and install Command Centre hardware, power, wiring, readers, devices, and controllers.

This section details the guidelines for the installation of Gallagher Security Command Centre hardware and associated devices.

## Architecture and Design

It is recommended that any **local regional requirements are understood**, and the security solution is designed to comply with these.

Product drawings for Gallagher Security hardware can be found on our Knowledge Hub site for use in a design package. BIM and CAD files are available.

See [Product drawings and BIM elements](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/product-drawings-and-bim-elements.md).

![BIM file of a dual cabinet](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/vEGSRBQlClla4oTVWljL/images%2Fimage2.png)

BIM File of a Dual Cabinet

## Power Supply

Gallagher Security recommends the use of a **Gallagher (or approved LifeSafety) Power supply** as these have been tested and have applicable compliances with the use of Gallagher Security hardware.

Gallagher control hardware is specified to operate from 13.6Vdc ±15% (11.56V to 15.64V). For good design, Gallagher recommends that the supply voltage at the equipment terminals should not be below 12Vdc.

## Wiring

### Cable Management

Effective cable management is essential in security cabinets to ensure system reliability, safety, and maintainability. Poorly organized cables can lead to:

* **Signal interference and power issues** – tangled or improperly routed cables may cause electromagnetic interference or voltage drops, especially in high-current devices like door locks.
* **Troubleshooting difficulties** – clear labelling and separation of cables make it easier to identify faults and perform maintenance without disrupting other components.
* **Reduced risk of damage** – organized cables are less likely to be pinched, bent, or exposed to wear, which helps prevent hardware failures.
* **Compliance with standards** – many security and electrical standards require proper cable separation (for example, ELV vs LV) and shielding to ensure safe operation.
* **Professional installation quality** – neat cable layouts reflect high workmanship standards and improve client confidence in the system’s integrity.

![Example of good cable management](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/g1yhVI5H577MqT5DE9SI/images%2Fimage3.jpeg)

Example of good cable management

### Power Cables

It is recommended that power and communications circuits are each run in a separate, dedicated cable. However, for short runs of 2–3 m (6.5–10 ft), these circuits may share a single cable. The voltage drop caused by the cable should be such that the voltage at the device terminals should be no less than 12Vdc.

Door locks, such as strikes, should have dedicated cabling from a fused power source. Electronic locks can generate back electromotive force (EMF) if surge protection is absent or fails. They can also draw high current while locking or unlocking, which can affect other field devices on the same power circuit. Fit EMF diodes to locks where appropriate.

The recommendation is to **provide an additional dedicated 2C power cable for the lock**, the cable size should be considered based on volt drop calculation at peak operation load, not idle load.

### HBUS Cables

Multiple HBUS devices can share the same HBUS run. Whether they should depends on the site’s security requirements, the number of devices allowed on a single run, and the power requirements of the devices on it.

For standard security installations, multiple devices on one run are acceptable, noting that a cable break on that run can affect some or all of the devices on it. For high security installations, it is often a requirement for every device to have its own HBUS run back to the controller; the HBUS 8 Port Hub and HBUS modules described below can provide this. The HBUS cable is designed for HBUS field devices only and should not be used for lock power as well as HBUS devices. Daisy chaining HBUS field devices is acceptable, provided the voltage drop has been calculated at the furthest HBUS field device (no less than 12VDC at peak load). Where power is the limiting factor, multiple power supplies can be distributed around the site.

Furthermore, the HBUS power source should be considered as part of the design. Is the power going through a controller or will it be straight from a fused power source? If the power source is going through a controller, there will be some limitations as to how much the controller can support. Refer to the controller’s installation guide for its fused capacity per RS485 ports. It is recommended to use a dedicated fused power source per field device (any cable leaving the cabinet).

Regarding shielding on the HBUS, unshielded cable is acceptable. The intent for shielding is to prevent external “noise” issues to the RS485 communications. However, our HBUS RS485 communication is very stable and typically does not experience any issues with external noises in a typical installation (minimum 300 mm (12 in) gap between LV & ELV cabling). If the HBUS is likely to be subjected to HV induction, then the engineer should consider a cable that provides the appropriate shielding.

HBUS runs can be run underground with other communication cables. The cable must be rated for underground or wet locations, and the required separation from LV power cabling must be maintained.

The start and end devices on an HBUS circuit should be terminated using 120 ohm resistance. If the module is the start or end device on an HBUS circuit, terminate the module by connecting a short wire between “TRM Link” and “Com A” connectors. This applies for both RS485 in/out and RS485 Device(s). Termination varies between devices, so refer to each device's installation note. The entire HBUS run, measured from end to end, should not exceed 500 metres (1,640 ft). Devices on the run should be daisy-chained (serial); ‘T’ or ‘star’ connections between devices are not permitted. Where star or home-run wiring is needed, use an HBUS 8 Port Hub, HBUS 8H/4H Module or HBUS 8 In 2 Out Door Module, which allow devices to be wired individually back to one location. The HBUS 8 Port Hub also lets existing star or home-run wiring be re-used alongside daisy chains; it should be mounted in an enclosure with tamper detection and powered from a fused supply, and the Controller’s RS485 device limits still apply. If the Controller is at the end of the run, fit its on-board termination jumper; if it is in the middle, remove it. See the RS485 cabling diagrams in the [Controllers install notes](https://help.security.gallagher.com/knowledge-hub/deployment-resources/install-and-commission/hardware-install-notes/controllers-install-notes.md).

## Readers

### Gallagher Readers

Gallagher advise in both their reader Installation Notes and product brochures that read range may be affected by the presence of metal. This applies to any make or model of reader that uses radio transmission to operate. Gallagher recommend that readers not be mounted on or near metal surfaces. Doing so may adversely affect the read range and ultimately, the quality of the installation.

The distance separating any two readers must not be less than 200 mm (8 in) in all directions. When mounting a reader on an internal wall, check that any reader fixed to the other side of the wall is not less than 200 mm (8 in) away.

![Reader separation distance diagram](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/98ZiXQarMzA5hung8uLu/images%2Fimage4.png)

### Third Party Readers

It is recommended to follow the associated installation instructions for the third-party reader - sufficient grounding will be required in most cases.

## I/O and other HBUS Devices

There are multiple different devices that can be connected to a controller’s HBUS.

{% hint style="info" %}
It is recommended to read the [I/O expansion install notes](https://help.security.gallagher.com/knowledge-hub/deployment-resources/install-and-commission/hardware-install-notes/i-o-expansion-install-notes.md) to understand the limitations of each device.
{% endhint %}

## Tampers

Depending on the Controller variant, controllers utilise optical and/or mechanical tampers. The onboard front optical tamper will sense when the cabinet door is opened, the rear optical tamper detector will sense if the controller is removed from its mounting position.

{% hint style="info" %}
**It is good security practice to utilise the tampers on the Gallagher Security hardware.**
{% endhint %}

When the controller is repowered after servicing and is operating correctly, the optical tamper detectors may need to be re-initialised. During this time the cabinet door should be closed to accurately calibrate the sensor.

The Controller 7000 SD has physical front and rear tamper switches. The rear tamper tab must be screwed to the mounting surface for the rear tamper to work. When used in a cabinet, it is possible to configure input 1 as the cabinet tamper input. The Controller 7000 Standard is a separate hardware design. From version 9.30, inputs on a Controller 7000 Standard can be reserved for specific functions, including cabinet tamper, battery fail, mains fail, cabinet vibration and cabinet vibration tamper.

The T-series Readers also come with tampers; it is recommended that these are used as per the installation notes.

## Controllers

### Installation

{% hint style="info" %}
It is recommended to read the [Controllers install notes](https://help.security.gallagher.com/knowledge-hub/deployment-resources/install-and-commission/hardware-install-notes/controllers-install-notes.md) to understand each device.
{% endhint %}

### Plug-in modules

For plug-in module installation and removal instructions, see [Controllers install notes](https://help.security.gallagher.com/knowledge-hub/deployment-resources/install-and-commission/hardware-install-notes/controllers-install-notes.md).


---

# 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/engineering-and-design-reference/deployment-guidelines/hardware.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.
