> 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/licensable-features/perimeter-fence-controllers/configuring-an-f3x-f4x-f5x-f6x-fence-controller.md).

# Configuring an F3x/F4x/F5x/F6x Fence Controller

### Introduction

An F3x, F4x, F5x or F6x Fence Controller can be operated in a networked mode, instead of stand-alone mode, by changing the Stand Alone/HBUS SW1 dipswitch 9 to ON and then connecting the Fence Controller via HBUS to a Controller 7000 or 6000 and Command Centre. In this configuration the Fence Controller’s behaviour is configured and managed from Command Centre, replacing the Fence Controller’s default stand-alone behaviour.

Within Command Centre up to 24 F3x, F4x, F5x, F6x or F22 Fence Controllers can be assigned to a single Gallagher Controller 7000 or 6000.

The difference between the Fence Controllers is shown below:

| Fence Controller | Fence Channels | Inputs | Outputs | HV Sync | LV Sync | HVplus                 |
| ---------------- | -------------- | ------ | ------- | ------- | ------- | ---------------------- |
| F31              | 1              | 2      | 4       | No      | Yes     | No                     |
| F32              | 2              | 3      | 5       | Yes     | Yes     | No                     |
| F41              | 1              | 2      | 4       | No      | Yes     | Yes                    |
| F42              | 2              | 3      | 5       | Yes     | Yes     | Yes                    |
| F51              | 1              | 2      | 4       | Yes     | Yes     | No                     |
| F52              | 2              | 3      | 5       | Yes     | Yes     | No                     |
| F61              | 1              | 2      | 4       | Yes     | Yes     | Yes (excl. EN variant) |
| F62              | 2              | 3      | 5       | Yes     | Yes     | Yes (excl. EN variant) |

This procedure describes how to create an F3x, F4x, F5x or F6x Fence Controller in Command Centre.

***

### Before you begin

Before you begin this procedure:

* Ensure the following components have already been created:
  * a **Fence Zone**

    Refer to "[Creating a Fence Zone](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-fence-controllers/creating-a-fence-zone.md)"
  * a **Gallagher Controller 7000 or 6000**

    Refer to "[Creating Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers.md)"
  * **Inputs and Outputs**

    Refer to "[Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md)"
  * **Alarm Zones**

    Refer to "[Setting up Alarm Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/alarm-zones/setting-up-alarm-zones.md)"
* You need to be in the same or parent Division of the Command Centre items mentioned, and have the "Edit Site" operator privilege to perform this procedure.

***

### Configuration

To configure a Fence Controller, perform the following procedures in Gallagher Configuration Client:

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. **Right click** and select **New\...HBUS Devices** > **F31/32/41/42 Fence Controller** or **F5x/F6x** **Fence Controller**.

   **Note:** If **Fence Controller** is disabled in the context menu, this could be due to one of the following reasons:

   * the number of Fence Controllers already created has reached the limit as specified in the license, or
   * you do not have the operator privilege required to create Fence Controllers.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).

   **Note:** The Division must be the same as, or a parent of, the Division used for the new Fence Zone.
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).

   The Fence Controller needs to be placed in an Alarm Zone and have the Battery Alarms and Temperature Alarms settings configured to generate alarms for complete perimeter security.

   **Note:** It is possible to configure a "Pre-arm Timeout" (from 0-60 seconds) for Fence Controllers to ignore any alarms, via the **Alarm Warnings** tab of the Alarm Zone.
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure a Fence Controller:

<details>

<summary>Status and Overrides tab</summary>

1. Click the **Status and Overrides** tab.

   **Notes:**

   * If a Fence Controller cover is removed, continuous tamper alarms will be generated. To prevent this from happening, tick the **Disable Tamper** checkbox.
   * The on-board optical tamper is re-calibrated:

     * 60 seconds after Service Mode SW1 dipswitch 1 has been changed from ON to OFF when the **Allow use of Service Mode for local control** checkbox is checked and the **Disable Tamper** checkbox remains unchecked. This allows time to replace the cover before re-calibration, or
     * 10 seconds after power up and the **Disable Tamper** checkbox remains unchecked, or
     * 10 seconds after a 'Reset' override has been performed and the **Disable Tamper** checkbox remains unchecked, or
     * 10 seconds after the **Disable Tamper** checkbox is unchecked.

     The Tamper LED located on the Fence Controller will enter a fast flash pattern that indicates the re-calibration countdown is in progress. Once the countdown timer for tamper re-calibration has started, if any SW1 dipswitch subsequently changes during the countdown period, the timer is restarted.
   * When a **'Reset'** override is performed, all inactive (historic) alarms shown on the Fence Controller are removed.
   * When a **'Shunt'** override is performed Command Centre will stop communication to the Fence Controller. All Inputs and Outputs assigned to the Fence Controller will no longer respond to commands from Command Centre. It will remain this way until you 'Unshunt'. Alarms continue to be displayed on the Fence Controller.
   * **'Initiate Battery Test' override:** Normally a battery test will only happen 24 hours after an energizer startup/reset. This override provides the ability to initiate a battery test immediately when needed, as long as at least one Fence Zone is operating.
   * **'Reset LV Sync Secondaries' override:** When an energizer is removed or replaced, the Primary unit will continue expecting pulse acknowledgements from the previous Secondary. This causes the system to enter a 'sync-lost' state, preventing normal operation. Performing a 'Reset LV Sync Secondaries' override resolves this by removing any non-responsive Secondaries from the Primary’s list and resyncing with active ones.
   * The **Status and Overrides** tab displays the current battery voltage, the current temperature measured within the Fence Controller unit and the highest and lowest temperature recorded within the last 7 days.

</details>

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-282c85e8d0f39ccbe0ce775498a174a90751ed43%2Ff32_connectionstab.png?alt=media)
2. Select the Controller you want to assign this Fence Controller to, from the **Controller** drop-down list.

   **Note:** When an HBUS device is added to a Controller 7000 or 6000, it will appear on the **HBUS Devices** tab of the Controller. In this case, the **Controller** field will be pre-populated with that Controller name.
3. If not already present, enter the HBUS serial number (10 character hexadecimal string) into the **HBUS Serial Number** field.

   **Note:** The HBUS serial number is optional, however the Fence Controller will be considered as not properly configured unless one is entered.
4. If you click the **Apply** button, software version numbers display.

   The **Configured Version** is the version of the device software in the configured Controller 7000 or 6000 FTS file, (i.e. not the version of the Controller 7000 or 6000 software). The **Current Version** is the version of software as last reported by the Fence Controller itself.
5. Select the appropriate **Hardware Variant** from the drop-down list, (i.e. F3x, F4x, F5x or F6x Fence Controller).

</details>

<details>

<summary>EOL Resistors tab</summary>

1. Click the **EOL Resistors** tab.

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

   This screen allows you to define the wiring and resistance values used on inputs that are connected to the Fence Controller.
2. Select the required resistor values from the drop-down list.

</details>

<details>

<summary>Devices tab</summary>

1. Click the **Devices** tab.

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

   **Note:** The appearance of this screen may differ depending on the Fence Controller type selected.
2. Assign the appropriate Inputs, Outputs and Fence Zones to configure the Fence Controller.

   **Notes:**

   * Each Input, Output and Fence Zone can belong to only one Fence Controller.
   * Fence Zones may or may not be connected to a physical fence.

</details>

<details>

<summary>Power Supply Setup tab</summary>

1. Click the **Power Supply Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-749af242ff7fa1a76ce0181ce1f5c82e478e6fe5%2Ff32_powersupplytab.png?alt=media)
2. Click the appropriate radio button for the type of battery backup you want to use, (i.e. **Use Power Supply and Internal Battery (standard configuration)** or **Use Power Supply with external battery backup** ).

   **Note:** When using an external battery backup, battery charging and testing is not supported, battery monitoring is supported. The **Power supply has failed for (mins)** option becomes disabled and Battery Alarms on the **Alerts** tab are disabled.
3. Configure as appropriate.

   <table><thead><tr><th width="228">Field</th><th>Description</th></tr></thead><tbody><tr><td>Enter Power Save Mode when</td><td><p>The Fence Controller will enter Power Save mode when:</p><ul><li>the mains power has failed for a period of time greater than or equal to 30 minutes (default value), or</li><li>the mains power has failed and the battery voltage is less than or equal to 11.5 V (default value) for 7-10 seconds.</li></ul><p><strong>Note:</strong> If the <strong>Power supply has failed for (mins)</strong> checkbox is un-ticked, the Fence Controller will continue to pulse as normal until the Power Save Voltage Threshold or Stop mode Voltage Threshold is reached.</p></td></tr><tr><td>In Power Save Mode</td><td><p>Select the appropriate behaviour when the Fence Controller enters Power Save mode. Either:</p><ul><li>Go Slow (skip every alternative pulse), or</li><li>Switch to Low Feel</li></ul></td></tr><tr><td>Stop Mode Voltage Threshold (Volts)</td><td>The Fence Controller will enter Stop mode (cease producing pulses) when the battery voltage is less than or equal to 11.0 V (default value) for 7-10 seconds.</td></tr></tbody></table>

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

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

   **Note:** The appearance of this screen may differ depending on the Fence Controller type selected.
2. Configure as appropriate.

   <table><thead><tr><th width="222">Field</th><th>Description</th></tr></thead><tbody><tr><td>Pulse Interval (sec)</td><td><p>This is the pulse interval (period of time between pulses) for this Fence Controller.</p><p><strong>Note:</strong> If this Fence Controller has been configured as a secondary device the pulse interval will be set to that of the primary device.</p></td></tr><tr><td>High Voltage Power Level (%)</td><td><p>This is the percentage of high voltage power that will be delivered per pulse, by this Fence Controller (default = 100%).</p><p><strong>Note:</strong> An F41 or F4 Fence Controller in HVplus mode will be at 100% regardless of the value configured here. HVplus 100% = 10 kV.</p></td></tr><tr><td>Low Feel Power Level (%)</td><td><p>This is the percentage of low feel power that will be delivered per pulse, by this Fence Controller (default = 25%).</p><p>The voltage chaser on the Fence Controller shows the measured return voltage delivered from the previous pulse, at or near its configured maximum.</p></td></tr><tr><td>Synchronisation Source</td><td><p><strong>Note:</strong> This field is only applicable to F3x/4x Fence Controllers. For F5x/6x controllers, synchronisation is configured on the <strong>Synchronisation</strong> tab.</p><p>Select the appropriate synchronisation source for this Fence Controller.</p><p>If the Fence Controller is not synchronised to a primary device, the red synchronisation lost icon overlays the Fence Controller icon and a blue exclamation icon overlays the Fence Zone icons.</p><p><strong>IMPORTANT:</strong> If the F3x/4x Fence Controller is synced with an F5x/6x, the F3x/4x must be set as a secondary controller, with an F5x/6x as the primary. An F5x/6x will not sync from an F3x/4x primary controller.</p></td></tr></tbody></table>
3. Check the **Allow use of Service Mode for local control** checkbox if you want technicians to be able to use Service Mode SW1 dipswitch 1 for local arm/disarm control. For details about Service mode see [Using Service mode](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-fence-controllers/using-service-mode.md).
4. Are you configuring an F41/F42 Fence Controller?

   If **no**, go to the next step.\
   If **yes**, deselect the **Enable HVplus Mode** checkbox if you do not want to use HVplus mode. For details about HVplus mode see [Using HVplus mode](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-fence-controllers/using-hvplus-mode.md).
5. Are you configuring an F5x/6x Fence Controller?

   If no, go to the **Alerts** tab.\
   If yes, go to the **Synchronisation** tab before continuing to the **Alerts** tab.

</details>

<details>

<summary>Synchronisation tab</summary>

1. Click the **Synchronisation** tab and select 'Primary' or 'Secondary' as appropriate for this Fence Controller.

   **Note:** This tab only appears on the F5x/F6x properties.

   <table><thead><tr><th width="104">Option</th><th>Description</th></tr></thead><tbody><tr><td>Primary</td><td>The Fence Controller that manages the LVSync bus and sends the PulseNow command to all Secondary devices connected.</td></tr><tr><td>Secondary</td><td>A Fence Controller on the LVSync bus that is managed by a Primary and pulses in response to a received PulseNow command.</td></tr></tbody></table>
2. If you select **Primary**, the Fence Controller will be assigned as the primary in the LV Sync Bus and will set the pulse timing for all connected secondaries.

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

   **Note:** If a Fence Controller is removed, you can reinitialize the LV Sync bus by using the “Reset LV Sync Secondaries” override on the **Status and Overrides** tab. This action will automatically detect and register all connected Fence Controllers on the LV Sync bus.
3. If you select **Secondary**, the Fence Controller will be assigned as a secondary in the LV Sync Bus and will wait to receive the sync now command from the primary.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6a0c40f93c65062fdab77778c6dd1757316f98f2%2Ff5xf6x_synchronisationtab_secondary.png?alt=media)
4. Select the appropriate **High Voltage Sync Source**:

   <table><thead><tr><th width="98">Option</th><th>Description</th></tr></thead><tbody><tr><td>None</td><td>No HV Sync source is connected. +ve channel is an output.</td></tr><tr><td>Internal</td><td>The HV Sync source is part of the same fence system, (i.e. synchronisation is mandatory). This is available on F52 and F62 Primaries, and Secondaries for bidirectional HV Sync.</td></tr><tr><td>External</td><td>This option only appears when the Fence Controller is set as <strong>Primary</strong>. It indicates the sync source is from a separate fence system, (e.g. synchronisation to a neighbouring Fence Controller is recommended but not mandatory).</td></tr></tbody></table>

   **IMPORTANT:**

   * If the F5x/6x Fence Controller is synced with an F3x/4x, an F5x/6x must be set as the primary controller. An F5x/6x will not sync from an F3x/4x primary controller.
   * The maximum number of energisers connected to a primary F5x/6x Fence Controller is 100.

</details>

*(F5x/F6x Fence Controllers only)*

<details>

<summary>Alerts tab</summary>

1. Click the **Alerts** tab.

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

   <table><thead><tr><th width="174">Field</th><th>Description</th></tr></thead><tbody><tr><td>Battery Alarm</td><td><p>If the battery voltage drops below the configured <strong>Low Battery</strong> level (Default = 12.0 V), an alarm is raised. This alarm is not reflected by the Battery icon on the Fence Controller. The Battery icon illuminates if the battery test has failed or a battery is not present.</p><p>If the battery voltage drops below the configured <strong>Test Level</strong> (Default = 11.5 V) during the battery test, an alarm is raised. This alarm is reflected by the Battery icon on the Fence Controller. The <strong>Test Level</strong> can be used to change the value used when the Fence Controller is used in stand-alone mode.</p><p><strong>Notes:</strong></p><ul><li>The Fence Controller will automatically test the battery within 24 hours of switching on and every fortnight +/- a random 50 hours. An event is raised when the battery test starts and when the battery test finishes.</li><li>The Battery Alarm fields will be disabled if "Use custom Power Supply with external battery backup" is selected on the <strong>Power Supply Setup</strong> tab.</li></ul></td></tr><tr><td>High Temperature Output</td><td><p>The Fence Controller is equipped with an on-board temperature sensor. This sensor measures the temperature within the Fence Controller unit. When the temperature exceeds the configured Threshold (default 60 °C), the Output, (e.g. fan or cooling unit) will activate. When the temperature has dropped by 10 °C below the Threshold, the Output switches off.</p><p>The optimal temperature measured within the Fence Controller unit is 40 °C.</p><p>If the measured temperature exceeds 75 °C a very high temperature alarm is raised. The energizer will skip every alternate pulse (Go Slow mode). A hysteresis of 10 °C applies.</p><p>If the measured temperature exceeds 85 °C a critical temperature alarm is raised. The energizer will stop pulsing (Stop mode). A hysteresis of 10 °C applies.</p></td></tr></tbody></table>

</details>

<details>

<summary>Data Logging tab</summary>

1. Click the **Data Logging** tab.

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

   This screen allows you to configure voltage and temperature logging for the Fence Controller. The events logged due to these settings will be used when a Voltage Report or Temperature Report is run for this Fence Controller.
2. Configure the Data Log change and/or time interval triggers as required, for either Battery Voltage, Temperature, or for both.

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Fence Controller.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this Fence Controller.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Fence Controller.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this Fence Controller.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. 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

An F3x, F4x, F5x or F6x Fence Controller has been created, with Fence Zone(s) assigned to it, and it has been assigned to a Gallagher Controller 7000 or 6000. As a result, the following occurs:

* the Fence Controller and Fence Zone(s) will display within the **Hardware** List Window. The Fence Zones as child(ren) of the Fence Controller, and the Fence Controller as a child of the Gallagher Controller 7000 or 6000.
* on the **Connections** tab of the Fence Controller, the Gallagher Controller 7000 or 6000 name will appear in the **Connected to** field.


---

# 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/licensable-features/perimeter-fence-controllers/configuring-an-f3x-f4x-f5x-f6x-fence-controller.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.
