> 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/site-installation/setting-up-your-site/wizards/configuration-wizard/creating-controllers.md).

# Creating Controllers

### Introduction

The **Controller Wizard** offers the operator default choices with which to set up a Controller. The data configured in the wizard is the required basic information to configure a Controller in Command Centre.

### Controller Wizard

The **Controller Wizard** contains a number of pages which prompt you to enter certain information to create a Controller.

**Follow the instructions displayed.**

#### 'Controller Details' page

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f600c5b51e7d8fc160dcb848a752a0f1b7359cd8%2F37135.png?alt=media)

1. Enter a **Name**, **Description** and **Prefix** for the Controller.

   Refer to Step 4 of the [Configuration Wizard](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/configuration-wizard.md) procedure for details.
2. Enter the **MAC** Address for the Controller.

   The MAC Address can be found on a white sticker on one edge of the Controller.
3. What is the Controller configured for?

   <table><thead><tr><th width="169">If...</th><th>then...</th></tr></thead><tbody><tr><td>IPv4,</td><td>enter the <strong>IP address</strong>, <strong>Subnet</strong> and <strong>Gateway</strong> for the Controller.</td></tr><tr><td>IPv6,</td><td><ol><li>Tick the <strong>IPv6 Enabled</strong> check box.<br>The Network Prefix and the Address fields activate.</li><li>Select an IPv6 address from the <strong>Network Prefix</strong> drop-down menu or,</li><li>Select the <strong>Address</strong> radio button.</li><li>Enter the IPv6 in the <strong>address</strong> field.</li></ol></td></tr><tr><td>IPv4 or IPv6 using DHCP,</td><td>refer to the Enable DHCP for a new Controller 6000 using Wizard topic.</td></tr></tbody></table>

   This information will be provided by the IT Department for the organisation, or the IT provider of the network.

   If there is no IT support for the site, and it is a localised and dedicated LAN built for Command Centre, there are some standards that you can apply to the configuration of the Controllers, as described below:

   <table><thead><tr><th width="190.5555419921875">Configuration Parameter</th><th>Description</th></tr></thead><tbody><tr><td>IP Address</td><td>The Internet Assigned Numbers Authority (IANA) has reserved several blocks of TCP-IP address space for private networks.<br>These TCP-IP addresses have been set aside specifically for use when it is not necessary (or desirable) for the attached devices to be available on the Internet. If one of these TCP-IP addresses were accidentally broadcast on the Internet they would be ignored by the routing firewall server and would cause no conflict issues.<br>To simplify IP range selection use the Class B range:<br>Class B From 172.16.0.0 to 172.16.254.255<br><br><strong>Note:</strong> Each device, (i.e. Computer, Printer, Controller) on the localised LAN must have a unique TCP-IP address. Each address used must however be in the same Subnet Mask range.<br>This means when using the Class "B" TCP-IP address range, each TCP-IP address assigned to the localised LAN must start with 172.16 and then be unique, (e.g. 172.16.0.1, 172.16.0.2, 172.16.0.3, 172.16.0.4, etc.)</td></tr><tr><td>Subnet</td><td>There are default Subnet Mask settings for class categories.<br>The Class B setting is:<br>Class B From 172.16.0.0 to 172.16.254.255<br>Default Subnet Mask is 255.255.0.0<br>Use the associated Subnet Mask appropriate for the TCP-IP class used. The Subnet Mask differentiates between the network and client parts of the TCP-IP address. The "255's" identify the network section and the "0's" identify the clients.<br>For a Class "B" TCP-IP address the network identification numbers are "172.16" and will be identical for each TCP-IP address on that network. The following two numbers of the TCP-IP address uniquely identify each device on the network.</td></tr><tr><td>Gateway</td><td>Gateway settings when used in general LAN configurations provide a path to a different network environment. In a localised LAN environment for Gallagher there is no physical connection to a different network, so the Gateway setting is ineffective.<br>For single Subnet installations, it is recommended the Gateway information be set exactly as the TCP-IP address used.</td></tr></tbody></table>

   **Notes:** The **MAC** and **IP Address** fields cannot be defined in a template and must be entered by the operator.
4. Select the radio button to choose **Single** or **Dual** as your ethernet connection.
5. Click the **Next** button.

#### 'Controller Details - Part Two' page

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-91548b7841fe3217098906c6c9b83ce8ab989071%2F37138.png?alt=media)

6. Assign the Controller to an existing **Division** from the drop-down list.
7. The **Alarm Zone** field is automatically populated with the assigned Alarm Zone name.

   **Note:** If you entered a prefix on the previous wizard screen, then the name of the Alarm Zone will be changed to "\[Prefix] Alarm Zone".
8. Enter the **Timezone** string for the country your site is in by selecting the appropriate string from the drop-down **Quick list**.
9. The **Device Software** field is populated by default with the **-- None Selected --** option, giving you the flexibility to decide when the software on the Controller should be updated.

   You will be able to select a version of device software to be downloaded from the drop-down list.
10. The **EOL Resistors** drop-down list is populated with all EOL Resistance values available for the Controller type.

    Select the appropriate EOL Resistance.
11. If the Controller is not mounted in a cabinet, continuous tamper alarms will be generated. To prevent this from happening, tick the **Front** and/or **Rear** check box.
12. Select the appropriate **Plug-in Module** from the drop-down list.

    Options are No Module, 4R Module, 8R Module, 4 HBUS Module and 8 HBUS Module.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a3639a7622a0e5badb96249e79d16875c933cca2%2F37139.png?alt=media)
13. Select the appropriate Bus Type from the **RS-485 Bus 1** and **RS-485 Bus 2** drop-down lists.

    Both default to "HBUS", and have options for Aperio and Sensors.
14. Do the **Controller CCC** and **Alarm Zone GG** fields appear at the bottom of this screen?

    <table><thead><tr><th width="78">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>your site is licensed for the Contact ID feature.<br>Refer to Step 4 of the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/configuration-wizard.md">Configuration Wizard</a> procedure for details regarding the CCC code.<br>Go to Step 15.</td></tr><tr><td>no</td><td>your site is <strong>not</strong> licensed for the Contact ID feature.<br>Go to Step 16.</td></tr></tbody></table>
15. The Alarm Zones that are used for Contact ID need to have GG codes assigned to them.

    Change the code in the **Alarm Zone GG** field if required (2 Hex digits 0-9, B-F).

    **Note:** 00 can be used to indicate that no specific group or partition information applies.
16. Click the **Next** button.

    **Note:** For Controller 6000, If you do not select a Plug-in Module, you will not have the option to configure Inputs in the next page, then the next page to display is the **HBUS Devices**.

#### 'Inputs' page

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-77b56f29806c1f732f8d732f8caf49f6dbfa026a%2F37140.png?alt=media)

17. Either accept the default names for the Inputs, or change them as required.

    **Note:** The Controller 6000 Input numbers change depending on the selected Module. **Controller 6000** with **4H** and **4R** module have two pages of Inputs, **Controller 6000** with **8H** and **8R** Module have three pages of Inputs, (i.e. Inputs 1-8 on the first page, Inputs 9-16 on the second page and Input 17-24 on the third page).
18. Click the **Next** button.

#### 'Outputs' page

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d0ba16ef97a03f1e04a8460e90b07193d690654f%2F37202.png?alt=media)

19. Either accept the default name for the Output, or change it as required.

    **Notes:**

    * You can select on **Autofill** to automatically fill the CCC fields or fill each CCC field manually.
    * The Controller 6000 with 4H or 4R Module has Outputs 1-4.

#### 'HBUS Devices' page

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9ac9f0541a398e0c28cd136199e5cf252cb00043%2F37206.png?alt=media)

20. Either accept the default device names, or change them as required.
21. Select a **Device Type** from the the drop-down menu.

    The default device type is HBUS Reader.
22. Enter a unique Serial Number (optional) for each device.
23. Click the **Next** button.

#### 'Finish' page

This wizard page is the same for Controllers and Doors, and provides the same options. Refer to ['Finish' page](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/configuration-wizard.md) in the 'Configuration Wizard' procedure for further detail.


---

# 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/site-installation/setting-up-your-site/wizards/configuration-wizard/creating-controllers.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.
