> 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/device-software/assigning-device-software-to-controllers.md).

# Assigning Device Software to Controllers

### Introduction

The following procedure enables you to assign device software to Controllers.

**Note:** To simplify the process of upgrading firmware on multiple Controllers, the Controller Upgrade feature can be used instead. Refer to [Upgrading Multiple Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/device-software/upgrading-multiple-controllers.md) for further detail.

### Before you begin

Before you begin this procedure:

* You need to create the Controller you wish to assign the device software to. Refer to [Creating Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers.md) for the procedure.
* It is recommended you link the Controller to an [Alarm Zone](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#alarm-zone) before assigning device software to it. Otherwise, the software version number will not display in the **Software** tab of the Controller's properties.

**Notes:**

* Software can be upgraded on Controller 6000s and 7000s from a USB memory stick. If you require the procedure for this, refer to [Loading Device Software to a Controller 6000 or 7000 using a USB stick](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/device-software/loading-device-software-to-a-controller-6000-or-7000-using-a-usb-stick.md).
* If downgrading a Controller 6000 to a version before v7.80, you will need to perform a "revalidate certificate" override in order for the Controller to come back online. If this is not done, you will see "invalid certificate" alarms for this Controller.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the required Controller, (i.e. the one you wish to assign the device software to).
3. **Right click** and select **Properties**.
4. Click the **Software** tab.

   **Note:** The fields on this tab vary slightly for the different devices.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fee7ae71a9503bdb798d588855e5be1470189e93%2Fftc6000_softwaretab_v812.png?alt=media)
5. Click the **Upgrade Version** drop-down list and select the required Controller version.

   **Notes:**

   * If you click the **Apply** button, the version of software displays on the screen once the download has completed. If it doesn't complete successfully, the version number that displays will be the version that the Controller "thinks" it has, which may not match what the device software is labelled as.
   * Other versions of software display as well as the **Controller Version**, (i.e. **Package**, **Application Software** and **Plug-in Versions** ).
6. The **Installed Software** section allows for downloading DLLs and assigning a customisation to a Controller.

   To assign a customisation, drag it from the **Device Software** List Window into the Customisations grid and click **Apply**.

   **Note:** Only one customer card customisation at a time can be deployed on any one Controller.
7. Do you want to upgrade the Controller now or schedule it for later?

   If **now**, go to Step 8.

   If **later**, go to Step 9.

   **Note:** Upgrades require Controllers to be online and Dipswitch 2 to be OFF. A warning message will display below the **Upgrade Now** button if the Controllers are offline OR Dipswitch 2 is ON:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e3a94417839536fcf12322bf7dc560154858d7e2%2Fupgradefailmessage.png?alt=media)
8. Click the **Upgrade Now** button.

   The Controller starts downloading the software, and a progress bar shows the progress of the download. Once the upgrade is complete the Controller restarts and comes back online.

   Go to Step 11.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-61f8c7c32a11ebb2b20411b37d879546e73b69de%2Fcontroller_softwaretab.png?alt=media)
9. Tick the **Schedule Upgrade** checkbox.

   A Date and Time drop-down displays.
10. Specify a suitable time for the Controller upgrade to occur by entering the required **Date** and **Time**, and click **Apply**.
11. The **USB Upgrading** section allows the software installed on the Controller to be upgraded with FTS files from a USB memory stick plugged into the USB port of the Controller 6000.

    To enable this option, uncheck the **Use site default settings** checkbox, and check the **Perform upgrades via USB** checkbox.

    **Notes:**

    * When selected, upgrades can be performed via USB for this Controller only. To change the site default settings for all Controller 6000s, refer to the [Controller Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/controller-defaults.md) tab in Server Properties.
    * When an upgrade has been initiated but can only be performed via USB, the following message is displayed at the bottom of this page:

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9b31fbc4dfded605f57968b0d5cff535b9f0693e%2Fftc6000_downloadmessage.png?alt=media)
12. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

The device software is assigned to the appropriate device.

**Notes:**

* If you were assigning software to a Controller, the Controller will be automatically restarted after the download.

  If the Controller software is upgraded and the Controller has custom DLLs installed, the Controller will delete the custom DLLs prior to downloading the upgraded Controller software, and then the Controller automatically restarts. The DLLs are then downloaded again to the Controller, and the Controller will restart a second time.
* For Controller 6000s that have HBUS devices configured, these devices will be automatically upgraded after the Controller has completed its upgrade if the Controllers Device Software contains a newer version of the HBUS Devices firmware.


---

# 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/device-software/assigning-device-software-to-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.
