Features
- Available in two models, single circuit (F31 and F41) or dual circuit (F32 and F42)
- F4 models feature HVplus mode for additional deterrent
- F-Series delivers 2.3J output per circuit (3.6J for F4 HVplus mode)
- Easy maintenance design
- Alarms for fence zone, battery missing, battery test failure, tamper, over-temperature, LV signal loss, conflicting sync masters, or service mode enabled
- Five day historic alarm retention
- Support for external power management options
- Voltage and temperature reporting
- Automatic software upgrades
- Internal temperature monitoring.
Note: Some features are only available in networked mode.
Stand-alone or networked solutions
F-Series Fence Controllers can be deployed as either stand-alone (no need for an HBUS connection) or with Command Centre (v7.40 or later) as a fully integrated networked fence controller with full capabilities. F-Series Fence Controllers are delivered in their stand-alone configuration and can easily be configured as networked fence controllers via a simple on-board switch.
Stand-alone
The stand-alone configuration is designed to integrate with a customer’s existing alarm panel using simple I/O connections. This allows the fence to be controlled with the arming and disarming of the site, using the alarm panel keypads. Configuration of the device is via internal switches, control is via input signals, monitoring is via alarms (visible on the cover display), and relay outputs is to an alarm panel or other indicator devices. Stand-alone systems may consist of an individual fence controller or multiple fence controllers which are synchronized.
Note: To avoid having multiple masters, the stand-alone unit has been designed to integrate with an existing alarm panel and to be monitored and controlled from the alarm panel keypads.
Networked – HBUS
F-Series Fence Controllers can be connected via HBUS to Command Centre, where alarm monitoring, hardware/software configuration and data reporting can all be undertaken. F-Series Fence Controllers use Gallagher’s HBUS protocol for secure communication to a Controller 6000 which communicates to the server/workstation (Command Centre) via a TCP/IP network.
Networked functionality requires Command Centre v7.40 or later.
