FFT Aura Fence Operations Manual v2.0

FFT Aura Fence Operations Manual
The information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Future Fibre Technologies Pty. Ltd. Future Fibre Technologies Pty. Ltd. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not transfer rights or license to these patents, trademarks, copyrights, or other intellectual property except as expressly provided in any written license agreement from Future Fibre Technologies Pty. Ltd. 2013 Future Fibre Technologies Pty. Ltd. All rights reserved. Printed in Australia. Document Title: FFT Aura Fence Operations Manual Document Number: M903 3713 022, Version 2.0, FOSS 3 v1.20.5.91, Strain 7 Future Fibre Technologies Pty. Ltd., the Future Fibre Technologies logo, FFT, FFT Secure Zone, FFT Secure Fence, FFT Secure Link, FFT Secure Pipe, FOSS, FOSL, FOSF, FOPSS, FFT CAMS, FFT TAZ, FFT Locator, FFT Microstrain/Locator and Foptic are either registered trademarks or trademarks of Future Fibre Technologies Pty Ltd. Incorporated in Australia, the USA and/or other countries. Microsoft, MS, MS-DOS and Windows are registered trademarks of Microsoft Corporation. Fujikura FSM-60S Fusion Splicer is a product of Fujikara Limited. Joint closure instructions reprinted with permission of Tyco International Limited (TE Electronics) and Channell Commercial Corporation, USA. Westover FM-C320 Fibre Microscope is a product of Westover Scientific (JDSU). Alazar is a trademark of AlazarTech, USA. Basik is a trademark of NKT Electronics Co. Ltd, China. NI is a trademark of National Instruments, USA. Adlink is a trademark of ADLINK Technology Inc. Helios Web Interface (HWI) is a product of Fotech Solutions Ltd.
Contents
1.0 Company information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Company overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Contact details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 FFT terminology and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.0 Important product and safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1 FFT product disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2 Laser safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3 Reminders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.0 FFT Aura system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2 System outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.3 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.4 System performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.5 FFT Aura Fence deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.5.1 Fence-mounted fibre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.5.2 Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.0 FFT Aura Fence sensing controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.1 Connect cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.2 Front panel information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.3 Ventilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.0 Configuring the hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.1 Datasheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2 Start the laser and detection system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.3 System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.4 Tuning FFT Aura to the sensing fibre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.0 Web Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.1 Logging into the FFT Aura HWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2 Main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.3 Main Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.3.1 Colour map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.3.2 Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.3.3 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.4 Waterfall display / Sound field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.5 Configuration menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.6 System health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 7.7 Data Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Contents iii
7.8 Admin Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8.1 Hardware properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8.2 Fibre processing properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8.3 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8.4 View FDEL properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9 Level Crossings in HWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9.1 Signal Filtering and Level Crossings Counts . . . . . . . . . . . . . . . . . . . . 7.9.2 Dynamic Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.0 FFT Aura Fence Alarming Module: FOSS 3 Configuration . . . . . . . . . . . . . . . 8.1 Level Crossings in FOSS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 FOSS 3 Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 FOSS 3 Classification Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.3 FOSS 3 Diagnostic Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37 37 40 47 51 53 53 59 62 62 62 75 82
Appendix A Setting the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 A.1 Change the controllers IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 A.2 Change the front panel display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
iv
1.0
1.1
Company information
Company overview
Future Fibre Technologies (FFT) manufactures and markets a range of fibre optic intrusion detection and location systems for fences, pipelines, perimeters and other assets that are, quite simply, the worlds most effective solution for securing high value assets and critical infrastructure. FFTs core products include: FFT Aura FFT CAMS FFT Secure Fence FFT Secure Link FFT Secure Pipe FFT Secure Point FFT Secure Zone
Company information
1.2
Contact details
Washington DC Future Fibre Technologies (US) Inc. 11350 Random Hills Road, Suite 800 Fairfax, VA 22030 USA Toll free: +1 (877) 650 8900 Outside USA: +1 (650) 903 2222 Fax: +1 (435) 417 6671 Email: info@fft-usa.com Web: www.fftsecurity.com Europe Future Fibre Technologies Pty Ltd 3000 Hillswood Drive, Hillswood Business Park Chertsey, Surrey KT16 0RS England Phone: Fax: Email: Web: +44 (0)1932 895 317 +44 (0)1932 895 318 info.emea@fftsecurity.com www.fftsecurity.com
Americas Future Fibre Technologies (US) Inc 800 West El Camino Road Mountain View CA 94040 USA Toll free: +1 (877) 650 8900 Outside USA: +1 (650) 903 2222 Fax: +1 (435) 417 6671 Email: info@fft-usa.com Web: www.fftsecurity.com Australia Future Fibre Technologies Pty Ltd 10 Hartnett Close Mulgrave VIC 3170 Australia Phone: Fax: Email: Web: +61 (3) 9590 3100 +61 (3) 9560 8000 info.apac@fftsecurity.com www.fftsecurity.com
Middle East Future Fibre Technologies MENA FZ-LLC Building 11 Office G08 Dubai Internet City United Arab Emirates Phone: Fax: Email: Web: +971 4 4345361 +971 4 4393406 info.mena@fftsecurity.com www.fftsecurity.com
India Future Fibre Technologies M-12/23, DLF City Phase 2 Gurgaon, Haryana 122 002 India Phone: Fax: Email: Web: +91 124 4087020 +91 124 4087019 info.southasia@fftsecurity.com www.fft security.com
2.0
FFT terminology and acronyms

Description Application Programming Interface. Alarm Recognition and Discrimination. Can be made up of multiple zones. This term is used only for establishing views in FFT CAMS, for example, North Fence, Boundary Road Fence, etc. Refers to type of barrier on the perimeter or the various multiple lines of defence, for example, Chain mesh Outer Fence, Below Ground Sensor, Sterile Zone, Barbwire, Gates, Taut Wire Inner Fence, PIR, VMD, CCTV, etc. Below Ground Sensor. Each independent sensing cable monitored by a Controller. Microstrain/Locator has one channel. 408/408 systems have up to eight channels. The FFT Secure Zone system has up to 16 channels. The alarm channel has been disabled in FOSS, that is, the perimeter covered by that channel is no longer supervised. Control and Command. A single sensing controller (a PC running FOSS) that can control multiple zones. The sector may either be the complete perimeter or one section of the perimeter. It contains all the channels and zones monitored by an individual FOSS Controller. Distributed Acoustic System. An external device to FFT CAMS, for example, PLC, camera, etc. is not responding. Daylight Saving Time. Dense Wavelength Division Multiplexing. DWDM works by combining and transmitting multiple signals simultaneously at different wavelengths on the same fibre. Defines and terminates the end of the sensing cable for FFT Secure Zone systems. Defines and terminates the end of the sensing cable. Function Detect Event Locator. An insensitive singlemode lead-in cable connecting the sensing controller to the sensing cable. Used in all FFT products.
Acronym API ARaD Area Name (User defined) Barriers (User defined) BGS Channel
Channel Alarms Disabled Alarm CNCD Controller Sector (User defined)
DAS Device Not Responding Alarm DST DWDM
End Element End Sensor FDEL Feeder Cable
FFT CAMS
Central Alarm Monitoring System software that can be used on any computer on the sensing network. Used to integrate and centralise the information and signals from each of the sensing controllers on the network, including specific third-party equipment. Fibre optic perimeter security detection and location system. 8-channel fibre optic perimeter security detection system with a maximum range of 10 km for each individual channel. 8-channel fibre optic perimeter security detection system with a maximum range of 40 km for each individual channel. Fibre optic network security monitoring system. Fibre optic pipeline security monitoring system detecting third-party interference and tampering. Fibre optic perimeter protection of utility substations, solar farms, storage yards, pumping stations, block valve sites, etc. Fibre optic zone-based intrusion detection system for relatively short fence perimeters. An alarm that indicates that a fibre has been broken or cut. Fibre Optic Sensing System software used to operate the FFT sensing controller. An alarm that indicates that the FOSS software is running degraded. Normally this will require the FOSS PC to be restarted. The FOSS unit has been shut down. Gate isolator unit. Allows gates to be defined within the locating system as separate zones from the fence sensor; allows the gate to be isolated and not generate alarms. Graphical User Interface. Global Unique Identifier a unique identifier for an alarm. Keyboard, Video and Mouse console. An alarm that can be raised to indicate that the laser has been turned off. For example, this happens when an operator opens the configuration dialog on a FOSS unit configured as a locator. An alarm that indicates that the laser temperature has exceeded a set shutdown level. A technician should verify why the temperature in the room with the FOSS PC/unit has increased. An alarm that indicates that the laser temperature has exceeded a set warning level. It should be monitored from there on as it might keep increasing or it might decrease.
FFT Secure Fence FFT Secure Fence 108 FFT Secure Fence 408 FFT Secure Link FFT Secure Pipe FFT Secure Point FFT Secure Zone Fibre Break Alarm FOSS FOSS Degraded Alarm FOSS Unit Shutting Down GIU
GUI GUID KVM Laser Off Alarm
Laser Shutdown Alarm
Laser Temperature Warning
LED Locator Disabled For Channel Alarm Locator Fault Alarm Loss of Communications
Light Emitting Diode. FOSS indicates that the given channel is a locator channel, whereas FFT CAMS has it configured as an FFT Secure Zone channel. This is a configuration error. A system alarm that can be raised by a Locator system. This alarm type normally reflects that the installation of the FOSS unit is faulty. Please contact FFT. A system alarm that can be raised by either an FFT Secure Zone or a Locator system. It indicates that FOSS has not replied to the heartbeat sent by FFT CAMS within a set timeout period. The network connection should be verified between FOSS and FFT CAMS. Microstrain Locator. Multimode fibre optic cable. Optical Time Domain Reflectometer. An instrument used to test fibre systems and locate losses and reflections. Reserved for Future Use. The industrial computer that houses the FFT sensing hardware and software. Controls and monitors the fibre optic sensing cable, detecting events and intrusions. Software Development Kit. An interface provided to access the services of FFT CAMS. Singlemode fibre optic cable. Defines the beginning of the sensing cable for that zone for FFT Secure Zone systems. Defines the beginning of the sensing cable. Prior to the start sensor, the lead-in cable is insensitive. An intrusion alarm that normally reflects a short duration impact on the perimeter. FFT CAMS did not shutdown properly. An intrusion alarm that normally reflects a longer duration impact on the perimeter. Uninterruptable Power Supply. Coordinated Universal Time or Universal Time Coordinated. Refers to the localised breakdown of the individual sections of the barrier being monitored. Can be either (FFT Secure Zone, 8-channel, strain) hardware or software (M/L) zones.
M/L Multimode (MM) OTDR RFU
Sensing Controller
SDK Singlemode (SM) Start Element Start Sensor Stealth Alarm System Shutdown Error Alarm Threshold Count Alarm UPS UTC Zones (User defined)
3.0
3.1
Important product and safety information

FFT product disclaimers
Please read this document and any attached notes carefully before proceeding with installation and operation.
Future Fibre Technologies Pty. Ltd. (FFT) shall have no liability for incidental or consequential damages of any kind arising out of the sale, installation, or use of its products. All software described in this document is furnished under license. The software may only be used and copied in accordance with the terms of the licence. FFT or its affiliated companies or representatives assume no responsibility for the use or the reliability of the software, firmware or any equipment that is not supplied by FFT. The application software supplied with the fibre optic sensing system will perform in accordance with the performance specifications outlined in this manual only if it is used with hardware supplied by FFT. The specified performance of the application software is in no way guaranteed if it is used with hardware other than that supplied or specified by FFT.
3.2
Laser safety
The FFT Aura system is a Class 1 M Laser product as defined in ANSI Z136.1 2000 and AS/ NZS 2211.2:2006. Class 1 Lasers are low-power devices, which emit radiation levels lower than the Maximum Permissible Exposure. The maximum peak power level at the output ports of the FFT Aura system is below the maximum permissible exposure level.
At no time should the laser be turned on while there is no fibre connected to the controllers output port. Doing so will potentially cause serious damage to the optical transmission circuit. If this type of damage occurs, the controller must be returned to FFT for repair.
FFT always recommends that best practice is adhered to when dealing with optical fibre systems. These are listed below as a number of reminders and warnings.
3.3

Reminders
Always turn off the laser and sensing controller whenever installation or maintenance on the fibre is taking place or whenever a connector is disconnected or a fibre broken. Before you inspect fibre connectors, ensure that the laser LED is OFF. Never inspect fibre connectors with a fibre scope with laser on. Always inspect the connectors or adapters before you clean them. Always clean then reinspect the connector before making the connection. Always use the connector housing to plug or unplug a fibre never pull on the fibre. Always keep a protective cap on any unplugged fibre connectors. Always store unused protective caps in a resealable container to prevent the possibility of transferring dust to the fibre. Locate the containers near the connectors for easy access. Never use alcohol or wet cleaning without a way to insure that it does not leave residue on the endface. This residue can cause performance degradation of the system. Never look into a fibre while the system lasers are on. Never clean bulkheads or receptacle devices without a way to inspect them. Never touch the endface of the fibre connectors.
The information in this document is subject to change without notice and may not be construed in any way as a commitment by FFT. While FFT makes every effort to ensure the accuracy and contents of the document it assumes no responsibility for any errors that may appear.
Important product and safety information
4.0
4.1
FFT Aura system overview

Introduction
FFT Aura is a fibre optic based distributed acoustic sensing system. This system comprises a sensing controller and a fibre optic cable. Where possible, the system may be operated on existing fibre cables to turn existing infrastructure into a highly accurate distributed sensing system. When installed on a fence, FFT Aura is distributed, providing detection at every point along the fibre. The system is capable of highly accurate sensing with accuracy of up to 6 metres and a range of 16 kilometres from the sensing controller. The system is acoustic and operates by detecting all seismic and acoustic events on the fibre cable. The system provides continuous detection and monitoring in all weather conditions, being immune to electromagnetic (EM) and radiofrequency (RF) interference and being capable of being run alongside high voltage power cables. FFT Aura operates using a modified and highly controlled variant of an Optical Time Domain Reflectometry (OTDR) instrument. For buried applications, the system requires no specially manufactured fibre and operates with a standard telecommunications grade fibre optic cable. The FFT Aura sensing controller is connected to one end of the fibre optic cable and sends a pulsed laser light into the fibre. The fibre type required is a standard telecommunications grade, singlemode (SM) fibre. The fibre is inert and no power is required along the entire sensing length, only at the sensing controller.
4.2

System outline
Sensor: singlemode fibre optic cable, designed for specific application Sensing controller: rack-mountable unit, monitors up to 16 km of connected fibre Alarm Processing server: a server for analysis and generation of alarms.
The FFT Aura system comprises three major elements:
4.3
Technology
FFT Aura is a phase-sensitive OTDR-based sensing system employing one singlemode fibre within a sensing cable. Using a coherent laser, pulses of light are propagated down the fibre. The natural Rayleigh scattering process in optical fibres causes a small portion of this light to scatter or reflect back towards a detector, which is also appropriately placed next to the source to receive the scattered signals. Using this technique a series or array of distributed sensing channels or microphones are sequentially set up along the sensing fibre. By detecting and
8 FFT Aura Fence Operations Manual
monitoring the backscattered signal as well as its pulse timing information, a perturbation on the sensing cable can be detected and located to a high precision.
Figure 4-1 Principles of FFT Aura
When installed on a perimeter fence, FFT Aura provides real-time monitoring of the fence, detecting intrusion events such as climbs or cutting. Signal characterisation and analysis techniques are used to provide an operator or security team with highly accurate positional and threat information, allowing for a swift and informed response. This provides a monitoring capability for security and maintenance events. Mechanical vibrations easily generate detectable changes in the interferometric signal and allow for the generation of maps of vibration signals along the sensing cable, up to a maximum range of 16 kilometres from the sensing controller. This is then translated, using real-time software, to generate maps and customisable alarm signals for display and transmission to monitoring equipment. To reduce nuisance alarms, the system includes a fast electronic processor to automatically distinguish between intrusion and non-intrusion disturbances.
4.4

System performance
Perimeter security fence-mounted system Perimeter security below ground, covert system Pipeline security/leak detection above ground and below ground deployments Linear asset security buried using new or existing fibre optic cables.
FFT Aura can be deployed in a number of applications, including:
This manual is only concerned with the FFT Aura fence-mounted applications. For information on other applications, please contact FFT. The key features of FFT Aura for fence-mounted applications are: fully distributed sensing over entire fibre cable length of up to 16 kilometres perimeter fence-mounted location accuracy of within 6 metres FFT Aura is capable of setting hundreds of individually tunable zones on the fibre for: - prioritisation of key threat areas - desensitisation of non-core areas - tuning to detect specific events and filter against non-threat events - accounting for specific environmental conditions - allowing for multiple installation configurations - setting of specific detection parameters, including time. software configurable zones may be from 6 metres to several kilometres in length real-time detection, location and notification to any desired monitoring location, including to mobile security personnel no field electronics or power required to the cable sensitivity at acoustic frequencies greater than 3 kHz to 9 kHz, depending on sensor cable length low maintenance requirements capable of integration with CCTV via FFT CAMS probability of detection (POD) is high due to intelligent signal processing and analysis of disturbances no false alarms due to intelligent signal processing and analysis of disturbances. nuisance alarm rate (NAR) is minimal due to multi-parameter intelligent signal analysis, discarding non-intrusion and environmental events no seasonal calibration or adjustments are required.
In addition to the performance features detailed above, FFT Aura is capable of performing intelligent acoustic signature analysis to detect and classify or ignore specific events. For
fence-mounted systems, a level crossings (LC) algorithm is used to eliminate unwanted background noise and minimise false alarms. This could include concentrations of strong wind, incidents of rain or hail against the overhead cables, traffic noise or the energy of passing trains. The system is also capable of classifying specific events, including security events, such as digging, or climbing. FFT Aura is not affected by changes in fibre length along the length of the sensor and it is immune to radio frequency interference (RFI) and electromagnetic interference (EMI), external jamming and is intrinsically safe (IS). There are no electrical or active electronics installed in the field. Multiple controller units can be installed on a single fibre optic cable at suitable junction points and be networked together to monitor the entire length of the asset. The FFT Aura sensing controller contains the electronics and software required to continuously monitor, in real time for the detection of intrusion events over the entire length of the fibre optic sensing cable. The system will raise an alarm when an intrusion is detected, calculate and display the location of the intrusion event.
4.5
4.5.1
FFT Aura Fence deployment options

Fence-mounted fibre
When mounted on fences, FFT Aura will detect vibrations that may be caused by, but not limited to: physical action against the fence, including cutting or lifting attempts to climb the fence or ladders being placed against the infrastructure movements around the fence, including footsteps and vehicles.
FFT Aura is capable of monitoring an entire perimeter fence with a single fibre, which may be mounted on fences or walls, and may also be buried to provide additional protection on key threat areas. When FFT Aura is deployed as a fence-mounted fibre optic cable intrusion detection sensor system based on multi-core, single mode fibre optic cable. The fibre optic cable operates as a distributed sensor and is directly mounted on the fence along the perimeter or around an area to be protected. FFT Aura works equally well on chainmesh, weldmesh and palisade style fences. With an FFT Aura fence-mounted system, intrusions on approved fences can be detected and located to within 6 metres. There is no power required along the fence-line, and no electronics installed in the field. The sensors installed in the field are intrinsically safe and immune to lightning strikes, EMI and RFI events.
FFT Aura system overview 11
Figure 4-2 System logic fence
4.5.2
Resilience
FFT Aura has the ability to continue operating up to the point of fibre damage or a cable cut.
Figure 4-3 Cut survivability

Optionally, a fully redundant, cut-immune system will ensure that the fibre optic sensor cable, either side of the cut would continue to operate. Two controllers are required to perform this function.
Figure 4-4 Redundancy with two controllers
13
5.0
FFT Aura Fence sensing controller
FFT Aura Fence is an integrated system made up of three main modules: the FFT Aura sensing controller, the FOSS 3 alarming module and FFT CAMS. The three modules work together to provide event disturbance detection, analysis and alarm reporting. The configuration of the FFT Aura controller occurs in three parts. Firstly, the controller will need to be tuned to the connected fibre path; secondly, the sensing configuration will be set within the Helios Web Interface (HWI) utility, and thirdly, the alarm configuration and reporting will be configured in FOSS 3.
5.1
Connect cables
With the controller turned off, ensure that all cables are connected before proceeding.
At no time should the laser be turned on while there is no fibre connected to the controllers output port. Doing so may cause serious damage to the optical transmission circuit. If this type of damage occurs, the controller must be returned to FFT for repair.
Before starting the controller, perform the following steps: Ensure the controller is sitting on a shelf within the cabinet and fixed to the front rails with four screws. Ensure that there is 1RU of space available above the controller for ventilation. Clean and connect the supplied E2000 to SC/APC patch lead to the optical fibre port and the patch panel at the other end. Connect keyboard, video and mouse cables. Connect an Ethernet cable from the controller to a network switch. Connect coax cables from the two BNC ports to a BNC T-piece. This T-piece will be connected to channel 1 on an oscilloscope. Connect any external HDDs that may be required for data logging. Switch the power switch on the rear of the controller to the off position. Connect the power cable to a suitable UPS. A UPS should always be used to protect the equipment from an unreliable power supply. Switch the laser lockout key to the locked position (see Figure 5-1).
14
Figure 5-1 Laser in locked position
With the initial steps complete, switch the power supply to the on position and press the Power button on the front of the controller (see Figure 5-1).
5.2
Front panel information
The LCD display on the front of the controller displays the systems status and offers a number of hardware configurations. Note that detailed configurations will be performed via the web based interface. While in status mode, the display will cycle through a number of screens that will indicate items such as: Systems IP address System status Systems name Systems software version. Laser operating LED on when the laser is on Laser locked out LED on when the lockout key is in the locked position System error LED on when there is a hardware error Power LED on when the controller is switched on.
Below the display, there are a number of LEDs that quickly indicate the systems status:
When the controller is powered on and not in use, ensure that the laser light LED is off and the laser lockout LED is on.
FFT Aura Fence sensing controller
15
Figure 5-2 Laser locked out indicator
The LCD display is bordered by four soft buttons. Pressing any of the buttons will access configuration mode. If a change is made here or the menu is to be escaped from, wait 5 seconds and the display will reset itself to the status mode.
5.3
Ventilation
As the controller requires ventilation, ensure that the front mounted fans are not obscured and that there are no objects left on the top lid of the controller.
16
6.0
6.1
Configuring the hardware

Datasheet
Each controller will be supplied with a datasheet that contains a number of default values specific to that controller. Many of these values will need to be entered via the front panel before the laser is started.
Figure 6-1 Datasheet information
Importantly, the following values will need to be set or confirmed before proceeding: TEC set point Trigger level Back box delay Pulse width Pulse repetition frequency Bias current EDFA 1, 2 and 3. System Conf - TEC Ctrl to set the value of TEC 1 - EDFA Ctrl to choose one of three EDFA gain stages. Laser Conf - Pulse Width - Pulse Rep - Bias Current.
These settings will be found within the configuration menus:
Once set, the laser can be turned on and the system activated.
Configuring the hardware 17
6.2
Start the laser and detection system
To start the detection and laser systems, start by selecting Unlocked with the lockout key on the front panel. Note that the Laser Locked Out light will extinguish and the Laser Operating light will be lit.
Figure 6-2 Unlock the laser
To start the detection system, press any of the buttons next to the LCD display and select Detect On. Listen for a click as the data acquisition card enables.
6.3
System shutdown
In order to correctly shutdown the controller, enter the configuration menu on the front panel and select Detect Off. This will shut down the Event Detection System, and also turn off the source laser. Ensure that the laser lockout key is then set to the locked position. To power down the controller, press and the power button on the front panel once. The LCD screen will display the message CNCD exiting. Note that it may take 90 seconds for the controller to completely shut down.
18
6.4
Tuning FFT Aura to the sensing fibre
An oscilloscope is required to correctly tune FFT Aura to the sensing fibre. It will be used to correctly set the pulse width and repetition frequency, as well as determine the correct gain required for the sensor length. Connect and power on the oscilloscope and adjust until the pulse signal is visible.
Figure 6-3 Connect the oscilloscope Pulse width: determines the systems spatial resolution and is the period of time that the
pulse is energised. It also determines how much light is in the fibre at any one time. The pulse width used will be determined by the length of the total optical path and the controller supports pulse widths ranging from 10 ns up to 1 s. As light travels at approximately 2 x 108 m/s in an optical fibre, a 10 ns pulse width equates to approximately 1m in fibre length. To adjust the pulse width:
1 2 3 4 5
Press any button to access the configuration menus and select Laser Conf. Select pulse width to view the current pulse width. To reduce the pulse width press the lower left button, to increase the pulse width press the lower right button. The pulse width will immediately change to the value indicated next to the button pressed and the top line of the LCD display will indicate the new pulse width. When the correct value is set, allow 8 seconds to elapse and the display will revert to status mode.
Configuring the hardware
19
Pulse Repetition Frequency (PRF): defines the systems temporal resolution and therefore
the maximum detectable frequency of the disturbance. The maximum PRF is limited by the length of time it takes for a laser pulse to travel to the end of the fibre sensor and back (twice the length of the fibre sensor). As light travels at approximately 2 108 m/s in an optical fibre, it takes approximately 10 seconds for light to travel to the far end of a 1 km length of fibre and back. Therefore, the fastest allowable PRF in this example would be 100 kHz or a period of 10 seconds or the maximum PRF for a 10 kilometre length of fibre is 10 kHz. As the length of the fibre increases, the length of time for the pulse to get to the end of the fibre and back also increases. As the sampling rate is reduced, the maximum frequency of vibration that can be detected by the system is also reduced. The maximum frequency that a digital system can detect is half the sampling frequency. Table 6-1 shows a number of examples.
Table 6-1 PRF, maximum fibre length and detected frequency

PRF (kHz) 100 50 40 20 10 5 2.5 2 1 Max. fibre length (m) 1000 2000 2500 5000 10,000 20,000 40,000 50,000 100,000 Max. detected freq. (kHz) 50 25 20 10 5 2.5 1.25 1 0.5
Adjustment of the PRF should be done while viewing the oscilloscope. The scope show display noticeable individual pulses. If there is only one pulse, the PRF is too frequent, where large gaps between pulses indicates an insufficient PRF.
Figure 6-4 Pulses seen on the oscilloscope display
20
To adjust the PRF:

1 2 3 4
Press any button to access the configuration menus and select Laser Conf. Select PRF to view the current setting. To reduce the PRF, press the lower left button, to increase the PRF press the lower right button. The PRF will immediately change to the value indicated next to the button pressed and the top line of the LCD display will indicate the new PRF value.
Drive Current: determines intensity of the pulse being launched into the optical fibre. There are situations where adjusting the light intensity can improve the system's ability to detect event disturbances however, too much drive current will result in a saturated signal.
To adjust the drive current:

1 2 3
Select Bias Crnt from the Laser Conf menu. The bias current setting is displayed on the top row together with the maximum setting value. The setting is in normalised units. To reduce the bias current press the lower left button. To increase the bias current press the lower right button. The bias setting will immediately change to the value indicated next to the button pressed. The top line of the LCD display will indicate the new bias current setting. The available range of bias current settings is 1 to 255. If no buttons are pressed for 8 seconds, the display will automatically revert back to the main idle screen.
4 5 6
Ideal signal: The ideal pulse should look similar in form to Figure 6-5. The length of the
pulse will determine the length of the optical path. The height of the signal will be determined by the amount of gain added with the drive current and the EDFAs. Record the maximum height for use later in the configuration process.
Figure 6-5 Ideal pulse shape

Configuring the hardware 21
If there is no gap between the pulses, decrease the PRF. If the bottom of the pulse begins to lift, there is too much gain.
Figure 6-6 Too much gain
If there are any reflections in the optical path, it may greatly affect the pulse. If any are detected, they must be found and repaired before continuing the setup process.
Figure 6-7 Pulses with reflections
22
7.0
Web Configuration Utility
Once the sensing controller is configured, the Helios Web Interface (HWI), will be used to monitor the sensing signals and health of the system, configure the controller parameters and sensor configuration, and perform other functions such as recording and playing back signals. Access to HWI can be achieved by using a web browser such as GoogleR ChromeTM or FirefoxTM. For versions older than v4.4.0, only Google Chrome that has had Java installed should be used.
7.1
Logging into the FFT Aura HWI
To access the FFT Aura HWI, type the IP address of the controller into the address bar of Google Chrome. Each controller has a built-in web server that allows easy remote access for configuration and reporting purposes. Communication is via the default HTTP port number 80. If this port number needs to be changed, ensure the new port number is entered into FFT CAMS to maintain communications.
To access the different configuration and parameter menus, you will be required to log into the Access secure pages (see Figure 7-1). The login details will be specified on
the datasheet accompanying the sensing controller and can also be supplied by FFT.
Figure 7-1 Accessing configurations and parameter menus
23
7.2

Main screen
Colour map displays real time sensor disturbance Waterfall display historical display of the sensor disturbance Configuration menus access configurations Data logging enable logging of the live signal System control start and stop the detection and the laser System Health panel monitor system health and processing loads
The main screen consists of six main areas:
Colour map
Configuration menus
Waterfall display
Data logging
System control
System Health panel
Figure 7-2 HWI main screen
24
7.3
Main Configuration menu
The Main configuration menu can be accessed by clicking on the red button as shown in Figure 7-3, and contains information about the controller.
Figure 7-3 Main menu options
About this controller: displays SW version and serial numbers. Report a problem: email link used to report system errors if required.
View alarm list: lists the alarms currently active on the controller. Colour map: configure and change the colour map as described in the colour map section called Adjusting the scale. Clear sound field: clear the current display. Clear alarms from sound field: Preferences: adjust the system time zone and distance units. Print: prints a copy of the current sound field. Toggle oscilloscope mode: puts the screen into oscilloscope mode. Logout factory: log out of secure access mode.
25
7.3.1
Colour map
The colour map displays a real-time representation of the disturbances being detected by the sensor cable. The intensity of the disturbance is visually displayed by scaling it against a colour scale. The colour map also displays the location of the disturbance along the sensor path.
Figure 7-4 Colour map showing two disturbances
In Figure 7-4, the intensity is measured along the vertical axis and distance is determined along the horizontal axis.
Adjusting the scale If the received signal displayed is too tall for the colour map, enter a new number into
the scale box displayed at the top left of the window. Enter a new value then press ENTER to apply the change.
Figure 7-5 Colour map scale adjustment
To adjust the actual colour scale, click on the menu icon and select Colour Map
(Figure 7-6). The settings menu (Figure 7-7) allows the colour fades to be adjusted in stages or for new colours to be added.
26
Figure 7-6
Figure 7-7 Adjust colour scale
27
7.3.2
Preferences
The Preferences menu contains parameters for setting the time zone, distance units and waterfall configuration parameters.
Figure 7-8 Preferences
7.3.3
Print
To print the main screen, click on Print.
Figure 7-9 Print
28
Figure 7-10 Print the sound field
29
7.4
Waterfall display / Sound field
The waterfall displays a historical representation of the disturbances being detected by the sensor cable. Once displayed on the colour map, the disturbance is recorded to the waterfall, which allows the disturbances duration and direction of travel to be determined.
Figure 7-11 Real-time and historic display of the disturbance
Optionally, the waterfall can be configured to display other diagnostic features such as the raw disturbance signal. For FFT Aura fence-mounted systems, the setting should be set to Stream Detection Value ST-Level Crossings.
Figure 7-12 Waterfall views

Pause and zoom the display
The waterfall display can be paused by clicking the Pause icon shown in the colour map. The display will freeze; however, the background processing will continue. Pressing the Play icon will recommence the real-time display.
To view a specific section of the sensor, zoom in to the waterfall display. Click the Magnifying glass icon then place the cursor to the left of the location of interest, drag
the cursor to the right of the point of interest and then release the mouse button. Return to the full or previous view by selecting the Zoom out icon.
Figure 7-13 Viewing a section of the waterfall

Zoom in Pause or Play
Zoom out
Move around the display
Figure 7-14 Pause and zoom controls

Web Configuration Utility 31
7.5
Configuration menus
System control
The system control panel contains the following settings: Replay mode change controller to signal replay mode. Control start/stop Start or stop the data acquisition process. Will display either Running or Not Running. Laser control Turns the laser on or off. Will display Laser On or Laser Off.
Figure 7-15 System control
Start data acquisition To start the data acquisition process, click the green icon on the right-hand side of the
display. The system will begin to display data in the waterfall display, and the system status will change from Not Running to Running. The laser will also change to Laser On.
Figure 7-16 Not running, running
If the laser lockout key is in the locked position, it will not be possible to start the FFT Aura system. Unlock then attempt to restart.
32
Replay mode
Replay mode allows the system to replay previously acquired signals.

To enable replay mode, click on the icon with the green arrow in the system control
box. A warning message will be displayed requesting confirmation of the change.
Figure 7-17 Replay mode setting
Click the disk icon to select the data file. A file selection dialog is displayed showing a list of available raw FDS formatted data files. Navigate to the file and choose Select.
Figure 7-18 Select a file
33
Choose a replay start and end time then select the Play icon.
Figure 7-19 Press Play
The signal can be replayed at a faster rate using the fast forward button. Each time it is clicked the playback speed increases by a factor of 2, i.e. 1 2 4 8 16 32 MAX. The progress bar will show the files progress as it is replayed.
7.6
System health
The system health panel shows a real-time view of important system functions for the following modules: System Health Processing maintain below 80% Logging Display
Figure 7-20 System health display
34
7.7
Data Logging
Displays controls used to determine which data is to be logged, where it will be stored and the storage status. Data acquisition will need to be stopped before the mount option is available.
Figure 7-21 Data logging
To log a file, select the Mount Device icon. If an external drive connected via the USB
or eSata port has been detected, it will be available in the drive options window. Otherwise data can be logged to the internal HDD.
Figure 7-22 Drive mounting utility
Data Logging properties
Click on the Gear icon (see Figure 7-21) to determine the logging details such as the default directory, the part of the sensor to be logged and the ability to enable the logging.
By default, the system will log the entire monitored sensor. To reduce the effects of
logging on the controller, enter a start and end distance to limit the processing required to capture the data. Alternatively, choose a predefined zone that may be specifically logged.
35
Figure 7-23 Global logging properties
Once enabled, the status in the data logging window will change from Not Logging to Logging.
36
7.8
Admin Configuration menu
The Admin configuration menu contains settings used to configure the hardware as well as defining the system signal processing and alarming performance.
Figure 7-24 Admin menu options
7.8.1
Hardware properties
This option contains settings that setup the initial system properties. Any setting inputted into the front panel that differed from those supplied on the technical datasheet will need to be updated here.
Figure 7-25 Identity options
37
Identity
Contains factory assigned name and ID fields.
Optics Module
Importantly, this module contains three factory settings that must match the supplied datasheet.
Figure 7-26 Optics module
Note that if the serial numbers are incorrect, the controller may fail to function. The trigger level and box delay are factory set and should not be changed.
Laser bias current
The Laser Bias Current sets the amplitude of the light pulse being launched by the source laser. This value is not typically changed from the factor defaults, and for most deployments it should be left at the factor default.
MUX
This module describes the MUX parameters if a MUX option has been selected for the sensing controller. In most cases this will be blank.
Figure 7-27 Local Comms settings

Reporting
Contains settings that send alarms and sound field data to FFT CAMS. Once set at commissioning, these settings should not be changed.
Figure 7-28 Reporting options
Watchdog
These settings configure the behaviour of FDEL under different failure type scenarios.
Figure 7-29 Watchdog settings
39
7.8.2
Fibre processing properties
Settings used to acquire, analyse, process and log raw data from the optics module are defined here. The Optics and Data Capture menu options form the foundation of the processing flow. They are designed to optimise the raw data being acquired, as well as ensure that the correct portion of the fibre sensor is being monitored.
Optics
Optics properties will initially be set with values supplied in the controllers datasheet then adjusted after the controller has been connected to the sensor.
Figure 7-30 Optics properties
Laser properties
The laser properties are used to control the operational characteristics of the laser, which pulses the fibre in order to produce the fibre response.
PRF (Pulse Repetition Frequency)
The PRF determines how frequently the controller sends a pulse of light into the fibre sensor. It is equivalent to the sampling frequency, which dictates the maximum frequency that can be detected by the HWI interface. The fibre sensor length determines the maximum PRF that can be set as a new pulse cannot be sent until the previous pulse has been received. Increasing the PRF will increase the response bandwidth, but will increase the compute load, as there are more fibre shots to be processed in a given time interval.
Pulse Width
The larger the pulse width, the more light is launched into the fibre sensor, and the more sensitive the system is. Reducing the pulse width improves location accuracy and the ability to distinguish two nearby event disturbances (increased spatial resolution). The nominal pulse width is 50 ns, as this is a good compromise between maximizing spatial resolution and system sensitivity to event disturbances on reasonably short fibres (< 10 km). As fibre sensor lengths increase toward our maximum of 40 km, the pulse width needs to be increased to 200 ns in order to alarm on event disturbances at these longer distances.
EDFA properties
EDFA (Erbium Doped Fibre Amplifier) are optical amplifiers are used to set the optimal pulse amplitude, as well as to optimally amplify the very low level backscattered light. These are rarely changed from the factory defaults and should only be modified by a trained technician. There are three EDFAs with the controller.
TEC 1 controller set point
The TEC (Thermal Electric Cooler) controller is used to stabilise the centre wavelength of the laser. As the lasers temperature drifts, so does its centre wavelength. To obtain optimal fibre sensor response, the centre wavelength of the laser must stay in alignment with the receive chains FBG (Fibre Bragg Grating). This property will very rarely require field adjustment and requires an OSA (Optical Spectrum Analyser).
41
Data Capture properties
Determines how much of the sensor path is to be analysed and how the data is to be buffered.
Figure 7-31 Data capture Physical Fibre Length
Defines the maximum length of fibre that is to be monitored. The fibre length will also restrict the maximum PRF that can be used to ensure that the pulse has time to exit the fibre prior to the next one entering.
Zero Point
Determines the actual sensor start point and is typically set to zero.
Refractive Index
The Refractive Index (RI) is used to properly calibrate the speed of light (SOL) in the fibre. The typical value will be around 1.468 to 1.48 depending on the glass in the fibre sensor.
Monitor Start
Determines the optical distance where analysis will occur. This distance will be set to the same length as the lead-in and defines the start of the sensitive section.
42
Monitor End
Determines the optical distance where analysis will stop. This distance will be set to the same length as the lead-in plus the sensor and defines the length of the sensitive section.
Sample Rate
The Acquisition Sample Rate is the rate that the controller samples the incoming data. Default setting is 150 megasamples per second.
Number of Samples
Displays the number of data samples required to analyse the sensor.
Input Voltage
The input voltage is used to maximise the amplitude of the raw fibre shot without clipping data. Depending on the sensitivity of the optics module, the maximum amplitude of the analog voltage can vary between 100 and 500 mV at the beginning of the fibre sensor. This value can be determined via the oscilloscope or in the raw mode of the sound field.
Spectral Processing properties
These settings set the spectral processing parameters.
Figure 7-32 Spectral Processing module

Web Configuration Utility 43
FFT size
Sets the size of the FFTs used when performing the spectral analysis and is a fundamental component of the controller. Shorter FFT sizes, in the order of 128 samples, will provide better time domain resolution, at the expense of smearing out spectral resolution. Larger FFT sizes in the order of 1024 samples, will provide much better spectral resolution at the expense of reducing the temporal (time) resolution.
Analysis DC cutoff
Used to remove the very low frequency DC component from the signal prior to computing the output signal. A typical value for this property is on the order of 10-20 Hz.
Data Logging properties
The data logging tab contains all the properties used to log data. Allows the user to log raw or sound field data from the entire sensor or from a selected distance range. Files are selfcontained, and contain all the property information required to allow them to be used with the Playback module.
Figure 7-33 Data Logging
Data Logging directory
Determines where logged data will be written to.
44
Logging Filename
Tags the file name with relevant information.
Raw Logging properties
Enable or disable global raw signal logging.
Logging Start / End
Determine the starting and finishing distances used for global raw data logging.
Sound Field Logging properties
The processed Sound Field data can also be logged to disk. The size of a Sound Field data file is significantly smaller than that of a raw data file, so there is no need (or ability) to define a distance subset of the currently monitored section. To enable Sound Field data logging, ensure that the Sound Field logging checkbox is selected. If the check mark is visible, Sound Field logging is enabled.
Sound Field Logging Data Type
When logging Sound Field data, there is a choice to log either the currently displayed display type, all of the available display types, or a specific display type.
45
Fibre Break
The Fibre Break parameters activate the fibre break functionality as well as the fibre break monitoring period, which is typically 5 seconds. Make sure the checkbox is enabled for Fibre Break functionality to operate.
Figure 7-34 Fibre Break
Suppression
In the situation where sections of the sensor need to have their signals suppressed, a start and end distance can be defined to isolate individual areas or zones along the sensor. This can also be done visually by using the Select Visually button.
Figure 7-35 Suppression parameters

Alarm Report
The alarm report section determines which predefined signal stream is used and also allows its output to be reported to the sound field and FOSS 3 (for FFT Aura Fence) or FFT CAMS. For fence-mounted FFT Aura systems, AR-level crossings should be selected.
Figure 7-36 Alarm Report parameters
7.8.3
Zones
A zone is a defined section of the sensor path that may have unique processing requirements. For example, a fence line may have two different fence types, or a system may have a sensor cable run above and below ground within the same run. In these cases, unique filter ranges and detection parameters can be employed as a result of differing levels of sensitivity.
New zone To create a new zone, select the Zone option from the menu then click the green plus
symbol near the right edge of the dialog box. A popup is displayed allowing a name to be entered for the newly created zone. From here, the Sound Field display updates showing two drag handles, the left for the start distance and the right for the end distance of the new zone. If the exact distances are known, they can be entered in the two text fields accompanying the drag handles. This will allow the zone limits to be defined graphically on the waterfall plot.
47
Once the start and end distances have been entered, click the Submit button. Once confirmed, the zone is added to the Zone dialog, and the zone is displayed on the Sound Field display at the top of the waterfall section. Repeat this procedure for each zone to be defined on the fibre sensor.
Figure 7-37 Configuring zones
Figure 7-38 Naming a new zone
Figure 7-39 Add a zone
48
Figure 7-40 Define the zone size
Editing the start and end distance of a zone To change the zones start and end distance click on the Zone Resize icon (the icon
containing two small green squares third from the left). This displays the start and end drag handles showing the zones current extents, which can thereafter be graphically or manually altered (using the same procedure as creating the zone). Once edited, click the Submit button to register the change.
49
Editing zone properties By default, when a zone is first created, it inherits the global fibre properties such as the filters and the threshold counts. Click on the Zone Property icon, immediately to
the left of the red X icon, to display the zone properties dialog.
Figure 7-41 Resize zone
Figure 7-42 Zone properties set to defaults
50
To customise any of the parameters, deselect the Default to allow editing.
Figure 7-43 Editable parameters
7.8.4
View FDEL properties
Select to view the current configuration file.
Figure 7-44 Configuration file
51
Download diagnostic logs
In the event of an error, the system diagnostics log can be downloaded and forwarded to FFT for analysis.
Reset to factory defaults
Reset the controller to its factory defaults.
Restart
Selecting this option will initiate a system reboot.
52
7.9
Level Crossings in HWI
The FFT Aura Fence system uses FFTs level crossings (LC) algorithm to process the raw signals. This algorithm is effective for discriminating between intrusion and nuisance events, and to minimise nuisance alarms. logic. When using FFT Aura as a fence-mounted perimeter sensor, the LC algorithm must be used. For level crossings-based alarm logic, the HWI software performs the following tasks: filtering the sensor signal calculating level crossing counts for each sensing channel and generating a LC sound field applying dynamic threshold to the level crossings sound field.
7.9.1
Signal Filtering and Level Crossings Counts
The filter and level crossings parameters can be accessed via the HWI configuration menu (Admin Detection statistics DS-Level Crossing dialog).
Figure 7-45 Admin menu option with Detection statistics
53
The HWI detection statistics include the Band Pass Filter parameters and the Level Crossings parameters.
Figure 7-46 Detection statistics
Filter parameters
There are three filter parameters in the detection statistics windows (see Figure 7-47). These parameters are the bandpass filter cut-off frequency (Low frequency and High Frequency) and the filter Number of taps. The selection of these parameters influences the filter stability. The following table lists the parameters for stable bandpass filters.
Table 7-1 Stable filter sets
Filter band 50200 Hz 50300 Hz 50400 Hz 50500 Hz 50800 Hz Stable Number of Taps 3, 5 3, 5 3, 5, 7 3, 5, 7 3, 5, 7
54
Figure 7-47 Filter parameters
Always choose the largest stable number of tap within the band to get sharper cut off frequency.
Level crossings parameters
The level crossings counts have the following parameters:

Block size: the number of samples in a block. The configurable block sizes in HWI software are 16, 32, 64, 128, 256 and 512 samples. Threshold: the threshold used to detect level crossings. A signal must go from below this threshold to equal to or above it for a level crossing to occur. Threshold location: location at which Threshold is accurate. All other locations have the Degradation Factor applied to work out the threshold at that location. Degradation factor: number of units the Threshold goes down over one kilometre of sensor. For example, if the Threshold = 900; the Threshold location = 1000 m and the Degradation factor = 48, the new Threshold at 2000 m will be 852. Threshold minimum: the minimum threshold used to detect level crossings. If the degradation factor would cause the Threshold to go below this value for a given bin then this minimum threshold is used instead.
55
To set the correct value for the level crossings parameters (Threshold, Degradation factor and Threshold minimum), the Level Crossings Sound field can be used for
visualisation. A number of test points along the sensor can be set to calibrate the level crossings parameters by tapping at each point to visualise the response on the LCs sound field.
Figure 7-48 Level crossings parameters
Figure 7-49 LCs sound field with three test points for calibration
56
Setting the LC parameters (Degradation Factor)
An example of how to set the correct value for the important level crossings parameters (Threshold, Degradation factor and Threshold minimum) is shown in the Figures 7-50 to 7-52. Four test points along the 5 km sensor are chosen (at 1280 m, 1424 m, 1590 m and 4796 m). Strong event data, such as fence kicking or fence tapping, are collected. Figure 7-50 shows a strong event at 1280 m, 1424 m and 1590 m with two different thresholds (1200 and 2000). If the Degradation factor is set to zero, the threshold along the entire sensor is fixed and can lead to a loss of sensitivity over distance. Figure 7-50 shows a drop in the level crossings generated at the far end of the sensor if a zero Degradation factor is used, even if the Threshold is adjusted. The Degradation factor should have a value greater than zero to compensate for the attenuation in the signal over distance.
Figure 7-50 Strong events at 1280 m, 1424 m and 1590 m with two different fixed thresholds (1200 and 2000)
Figure 7-53 shows the effect of the Degradation factor on the detected level crossings sound field for a strong event. When the Degradation factor is increased to 50, it effectively lowers the Threshold with distance (per km), and the level crossings counts of the test events at 4796 m are now higher. This can be seen by looking at the LC waterfall in Figure 7-53, where a Degradation factor of 50 has increased the LC counts at the far end of the sensor. It is important that the Degradation factor is not too high, as an excessive value will reduce the Threshold too low and below the background noise, resulting in too many unwanted nuisance alarms. An example of this is shown in Figure 7-52 where the LC counts increase significantly with a degradation factor of 300. A factor of 50 is suitable for this example.
57
Figure 7-51 Effect of the degradation factor on the detected level crossings sound field for kicks event
Figure 7-52 Higher degradation factor triggers noise
58
7.9.2
Dynamic Threshold
The LC algorithm used by FFT Aura allows for a dynamic event threshold that automatically adjusts itself as the background nuisance event increases or decreases in strength (as is the case with wind or rainfall). The dynamic threshold parameters can be accessed via the HWI configuration menu (Admin Streams ST-Level Crossings dialog).
Figure 7-53 Admin menu option with streams
The HWI streams include parameters that monitor background noise to update the dynamic threshold and parameters for event detection when the level crossing goes above the dynamic threshold.
Figure 7-54 Streams parameters
59
Background noise monitoring
The background noise monitoring is used to update the dynamic threshold. It has the following parameters:
Monitor duration: the number of blocks (along shots axis) that are monitored to determine whether activity on the sensor is background noise or genuine activity. Indicates the duration of the Monitor Window. Monitor width: the number of bins (along bins axis) that are monitored to determine whether activity on the sensor is background noise or genuine activity. Indicates the width of the Monitor Window. Monitor overlap: the number of bins of Monitor Window overlap used when sliding the Monitor Window across the sensor to determine the dynamic threshold for each bin. Max variation: the maximum amount of variation in level crossings within the region of interest before activity is considered genuine. If the variation within the Monitor Window is less than this value then the region inside the Monitor Window is considered background noise. This parameter has direct impact on the sensitivity. Increasing the Max variation decreases the sensitivity and vice versa.
Figure 7-55 Background noise monitoring parameters
60
Event detection
In HWI software, any level crossings counts above the dynamic threshold will be sent to FOSS 3 for further event grouping and processing. The parameters that control these level crossings counts are:
Start disturbance threshold: the number of level crossings above the background noise required for an event to be generated. Increasing this number reduces detection sensitivity. End disturbance threshold: the number of level crossings above the background noise required for activity to be below before an event is determined to have finished. End disturbance duration: the number of consecutive blocks below the End disturbance threshold required before an event is determined to have finished. Max disturbance duration: the maximum length of an event. Event region margin: the number of bins either side of an event to be included in the area or interest.
Figure 7-56 Event detection parameters in FFT Aura
All level crossings values above the dynamic threshold in FFT Aura machines will be sent to FOSS 3, including their bins locations along the sensor for classification and alarming. The following section discusses the event detection, event classification and alarm reporting within FOSS 3.
61
8.0
FFT Aura Fence Alarming Module: FOSS 3 Configuration
FOSS 3 is FFT Aura Fences alarming module. It receives level crossing information from HWI, classifies the detected events, and processes them to generate intrusion alarms. FOSS 3 runs on a separate computer, typically on the same computer that also runs FFT CAMS. While HWI can interface directly to FFT CAMS, for fence-mounted FFT Aura systems, FOSS 3 replaces this interface.
8.1
Level Crossings in FOSS 3
The HWI software communicates all level crossings values above the dynamic threshold to FOSS 3 for further analysis and alarm generation. FFT Aura Fence uses all FOSS 3 utilities: FOSS 3 Manager FOSS 3 Classification Utility FOSS 3 Diagnostic Utility
8.1.1
FOSS 3 Manager
FOSS 3 can be connected to one or more FFT Aura sensing controllers. The FOSS 3 Manager has a number of configuration panels that are used for communicating with the FFT Aura sensing controller, event accumulation, event classification and event location methods.
Figure 8-1 FFT Aura configuration views and modules
62
The configuration of FOSS 3 to work with HWI can be performed by importing a preset default foss3.xml file that can be supplied by FFT. Alternatively, the configuration can also be done manually, but it is recommended that a default configuration file is obtained from FFT. The following sections describe each configuration panel in FOSS 3 Manager.
FFT Aura Configuration view
The FFT Aura parameters in FOSS 3 include event types/classes that are configured within the FOSS 3 Classification Utility and also include FFT Aura timeouts parameters that are used to check the status of the FFT Aura sensing controller. Event types include the list of events that can be used within the accumulator to trigger alarms. Some of the events can be used with level crossings detection method and others can be used with the FFT Aura standard detection method.
Figure 8-2 FFT Aura Configuration view
63
Figure 8-3 Events used with LCs detection method
Figure 8-4 Events used with FFT Aura standard detection method
The following list the FFT Aura timeouts parameters that are used to check the status of the FFT Aura system:
Connection retry interval: the time interval spend by FOSS 3 to reconnect to the FFT
Aura system.
Fibre break reset interval: the system sends fibre break messages at regular intervals. If a fibre break alarm is active and a fibre break message is not received in the required interval, the fibre break alarm will be reset. Laser temperature reset interval: the system sends laser temperature warning messages at 60-second intervals. If a temperature warning is active and a temperature warning message is not received within the required interval, the warning will be reset. Maximum heartbeat interval: the system sends heartbeat messages at regular intervals (apparently 15 seconds for binary connection). If a heartbeat message is not received in the required interval, an alarm will be generated. System shutdown interval: the system may occasionally be restarted. The system may be restarted due to a configuration change or because an error has occurred. Do not generate a system alarm until the system has been down for at least the specified period of time. Suppress duplicate events: the system may occasionally report the same event more than once with updated location information. This setting tells FOSS 3 application whether to ignore these updated events or report them as new ones. Maximum event history age: how long events are stored to determine if a new event is a duplicate of an old one. Fibre break location tolerance: the system send fibre break associated with its location. If another fibre break alarm is received from the system within the location tolerance, FOSS 3 will keep fibre break alarm active.
Figure 8-5 FFT Aura timeouts parameters
65
System Configuration view
The System view includes parameters that automatically acknowledge an alarm within a specified time duration.
Figure 8-6 System configuration view
Accumulation Configuration View
The Accumulation view has two types of accumulators; standard and clustering. This manual discusses only the standard accumulator. These accumulators work in a similar way to the accumulators as described in the FOSS 3 Locator manual.
66
Figure 8-7 Standard accumulator
The Accumulation view is used to configure the accumulation Instances such as events due to classification accumulators (for example, Aura Accumulator and Aura Fence Accumulator). Figure 8-8 illustrates how to create the Accumulator instances. Two accumulator instances created. A number of instances can be created, depending on the site requirements.
67
Figure 8-8 Accumulator Instances creation
Figure 8-9 shows how to suppress an event within a range of location. In Figure 8-10, an example is illustrated in which any AuraStrongActivity event will be suppressed occurring between the location range specified. This event will be suppressed from all the accumulator instances. It has to be noted that any other instances or events taking place during this Aura StrongActivity event duration will be suppressed completely and will not be reported. Accumulators have different rules and conditions that can be used for configuration. Accumulator reports alarm when it satisfies All the rules and conditions. The following section provides simple example of how to configure an accumulator.
68
Figure 8-9 Event Suppression within a range of location
Figure 8-10 Example of Event Suppression

FFT Aura Fence Alarming Module: FOSS 3 Configuration 69
Example of Accumulator configuration (FFT Aura Accumulator)
Each accumulator triggers an alarm when it satisfies specific weighting criteria within an Accumulation Duration. For example, this accumulator will trigger an alarm when the weight of the classified events is equal to or exceeds the Trigger Threshold AND the same accumulator includes at least one AuraStrongActivity event (one AuraStrongActivity event will have a weight of 2). The logic for this accumulator to trigger an alarm is as follows: (Meet the Events Accumulated rules) AND (The Required Events rules)
Figure 8-11 Example of reporting Alarm using multiple conditions
70
Connection with Sensor 1
FOSS 3 can be connected to single or multiple FFT Aura systems. Each machine in FOSS 3 has four configuration views. These views are FFT Aura Sensor, Accumulation, Locator and Event Classification.
FFT Aura Sensor view
The FFT Aura Sensor view for each FFT Aura system includes parameters that are used to group level crossings counts above dynamic threshold as an event for classification and also includes communication parameters (IP Address and Ports) to connect with FFT Aura system and FFT CAMS.
Figure 8-12 Event detection parameters within FOSS 3
71
Figure 8-13 Communication with Aura System and FFT CAMS
The status of the communication link between the FFT Aura system and FOSS 3 can be verified via the FOSS 3 Diagnostic Utility.
Figure 8-14 FOSS 3 - FFT Aura system communication status
72
The FFT Aura event detection parameters are described below:

Bin proximity threshold: the number of bins with zero LCs value allowed between two active (non-zero LCs value) bins to be included in the same event. Block proximity threshold: the number of blocks with zero LCs value allowed between two active (non-zero LCs value) blocks to be included in the same event. Minimum event duration: the minimum length of an event. Maximum event duration: the maximum length of an event. Minimum width: the minimum distance of an event.
Accumulation View
This view allows a user to enable certain accumulators to be used with each FFT Aura sensor (i.e Sensor 1).
Figure 8-15 Enabling accumulators
73
Locator view
The Locator view has binning and clustering methods. These location methods are used to determine the alarm that is generated by the accumulator.
Figure 8-16 Location methods
Event Classification view
This view allows the user to enable the event classification method and to specify the classification method to be used from the Classification Utility.
Figure 8-17 Event classification view
74
8.1.2
FOSS 3 Classification Utility
In the FOSS 3 Classification Utility, the event classification consists of classification methods and each method has the followings stages:
1 2 3
Event Detection Features Event Types (Classifiers).
Figure 8-18 shows three classification methods (Default, Aura Method 1, Aura Method 2). Each classification method can be configured independently and enabled within FOSS 3 Manager.
Figure 8-18 Classification methods in FOSS 3 Classification Utility. For training and tuning parameters, one method can be selected at a time from a drop-down list.
75
Note: While Training the Events Configuration, the Selected Classification Method has to be Default, for the First Method Parameters settings to be applicable and the selected Classification Method has to be Aura Method 1 for the Second Method and so forth as shown in Figure 8-19.
Figure 8-19 Method selection for tuning and training purposes
Event Detection
Event detection in FFT Aura software is based on level crossings and configured in the FOSS 3 Manager. The Event detection parameters in the FOSS 3 Classification Utility are not applicable to FFT Aura software.
76
Figure 8-20 Event detection parameters within FOSS 3 configured in FOSS 3 Manager (same as Figure 8-12) Features
After the event is detected, a number of features will be extracted. The FOSS 3 Classification Utility includes features used with the FFT Locator (not used here) and features used with FFT Aura system. The followings are the features that are used with FFT Aura system:
Duration: duration of event in blocks (similar to Height [Aura] feature). Area Density Windows [Aura]: number of windows where the density of the window is
greater than or equal to the Required Density. Area [Aura]: number of bin/block cells covered by event. LC Density Windows [Aura]: the number of shots in an event that have a bin/block value greater than the Required Level Crossings threshold. Value - Maximum [Aura]: maximum level crossings count for a bin/block cell included in the Aura event. Value - Total [Aura]: total number of level crossings in Aura event. Width [Aura]: width in bins of the Aura event. Height [Aura]: height (or duration) of event in blocks. Perimeter [Aura]: number of bin/block cells required to form a perimeter around the event. Area Density [Aura]: number of bin/block cells above/below (depending on 'Threshold Rule') the specified threshold divided by the total number of event bin/block cells multiplied by 100. Value - Minimum [Aura]: minimum level crossing count for a bin/block cell included in the FFT Aura event.
77
Shape Factor 1 [Aura]: The events perimeter squared divided by the area of the event as it appears on the LC waterfall (sound field). The event perimeter and area are classification features.
Figure 8-21 FFT Aura system classification features
Event Types (Classifiers)
After extraction of the feature vectors from the signal, a decision is taken about the class that the event belongs to (that is, in the case of an intrusion to generate an alarm, or if a nuisance to suppress). This process is performed with an appropriate classifier such as a neural network or simple decision rule tree. In the decision tree, an IF THEN decision rule is considered as a classifier to classify events. For example, in Figure 8-22 the event will be classified as VeryStrongActivity even IF the Width value is within the interval [5, 1000] AND the Height value is within the interval [10, 1000] AND the Value Total value is within the interval [100, 10000].
Note: to calibrate the classifier, training samples of intrusion (i.e climbs, cuts) and nuisance (i.e wind, rain) should be captured and saved through FOSS 3 Diagnostic Utility (Figure 8-23).
78
Figure 8-22 Classification Rules for VeryStrongActivity Class (class name can be any name)
Figure 8-23 Sample of training data for classification
The training data should be imported and processed through the FOSS 3 Classification Utility (Figures 8-24 and 8-25).
79
Figure 8-24 Importing training samples
Figure 8-25 Processing training samples for configuration

Features values and processed event type can be selected and viewed on the Classification Utility (Figure 8-26). The list of features value can be used to calibrate the classification system.
Figure 8-26 Columns selection for features and event type
81
8.1.3
FOSS 3 Diagnostic Utility
FOSS 3 Diagnostic Utility is a diagnostic tool used to display the status of the system along with other display tabs, Figure 8-27. The most important tabs for a FFT Aura system are the Classification tab, Aura Status tab and Aura Waterfall tab.
Figure 8-27 Display tabs
The Aura Status tab is used to display the laser and FFT AuraFOSS 3 link status.
Figure 8-28 Aura status tab

The Classification tab is used to display detected events, their waterfall and their features values (Figure 8-29).
Figure 8-29 Classification tab
83
The Aura Waterfall tab displays level crossings counts above the dynamic threshold of detected events (Figure 8-30). FOSS 3 Manager grouped these LCs counts into events for classification.
Figure 8-30 FFT Aura Waterfall tab
84
Appendix A Setting the IP address

The default IP address may not be appropriate, it will likely be changed. It will be necessary to change the IP address in two places. It is advised that a SSH client such as PuTTY be installed and used to perform these changes.
1 2 3
Open PuTTY and enter the default IP address. It will be shown on the LCD screen on the front panel. Ensure SSH is highlighted in the connection type, then select Run. Once established, a terminal window will open. Enter the user name root and the password supplied on the controllers datasheet.
A.1
1 2 3
Change the controllers IP address

Within the session type vi /etc/sysconfig/network-scripts/ifcfg-eth0. If this is not the correct interface, type ifconfig to determine which interface is in use. Press I to enter Insert mode then change the IP, DNS and default gateway addresses to the required values. Press ESC to exit then type :wq to write and quit.
A.2
1 2 3 4 5
Change the front panel display

Within the session type vi /etc/rc.d/init.d/cncd Find the line DAEMON="/home/Fotech/cncd/trunk/src/cncd -a 192.168.2x.xx Edit the IP address to match the new address by pressing I to enter Edit mode. Press ESC to exit then type :wq to write and quit. Reboot the controller by typing reboot -h and pressing ENTER.
Once this process has been completed, attempt to access the controller via the Web interface.
Appendix A Setting the IP address
85
86

FFT Aura Fence Operations Manual v2.0

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FFT Aura Fence Operations Manual v2.0

Загружено:

Авторское право:

Доступные форматы

FFT Aura Fence Operations Manual