EchoPoint User Interface Maunal
EchoPoint User Interface Maunal
© Copyright 2022, Fiber SenSys®, Inc. all rights reserved. No part of this publication
may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopy, recording, or any information storage and retrieval
system, without permission in writing from Fiber SenSys®, Inc., 6175 NE Century
Blvd., Hillsboro, Oregon 97124, USA.
This application note is provided by Fiber SenSys, Inc. While reasonable efforts have
been taken in the preparation of this material to ensure its accuracy, Fiber SenSys,
Inc. makes no express or implied warranties of any kind with regard to the
documentation provided herein. Fiber SenSys, Inc. reserves the right to revise this
publication and to make changes from time to time in the content hereof without
obligation of Fiber SenSys, Inc. to notify any person or organization of such revision or
changes.
Fiber SenSys® and Fiber Defender® are registered trademarks of Fiber SenSys, Inc.
Tel: 1-503-692-4430
Fax: 1-503-692-4410
[email protected]
www.fibersensys.com
SCOPE OF MANUAL
This manual includes the following:
• Software User Interface (UI) for configuration and tuning of EP301 system
• Installation of EP301 controller, and cable on fence or buried
INTRODUCTION
The EchoPoint EP301 system features the most advanced fiber-optic sensor technology for
intrusion detection and monitoring of fence and buried perimeters. The EP301 pinpoints the
location of an intrusion attempt to within a few meters and detects multiple simultaneous
events, such as coordinated intrusions. The system reports the precise location of an attempted
breach using XML or relay interfaces, which can activate PTZ cameras for verification and a
response. Precise location-sensing, advanced pattern-recognition and classification algorithms,
and sophisticated background rejection enable EP301 to have a high probability of detection
and low nuisance alarms due to environmental effects.
The EP301 controller supports two sensors, which can be installed in a loop configuration to
provide cut immunity. The EP301 is the first and only perimeter security system to offer both
cut immunity and 100% intelligent redundancy in the hardware. In a cut-immune configuration,
the EP301 system remains fully functional when the fence sensor is cut and immediately
reports the incident, including its exact location. When two controllers are installed in a
redundant configuration, as soon as the primary controller fails, the secondary controller
automatically turns on and begins protecting the perimeter. Both cut immunity and a 100%
redundant configuration architecture make EP301 one of the most reliable and compact (2U
size) solutions available to the market for high security.
Since the installation of the cable is straightforward on the fence (without any splice between
the start and the end) and the user interface is intuitive to use, the overall system is faster to
install and get operational with fewer problems. Support for this system is quick and effective
because the intrusion data can be saved locally and sent to our technical support group for
analysis if remote connectivity is not possible.
The EchoPoint user interface can be used to monitor alarms directly using in-built map and GPS
features or can be integrated with any 3rd party security management system using XML or relay
contacts.
Wide Applications
• Perimeter solution for fence, buried, wall, pipeline, data networks, hybrid
mediums
• Complete suite of products covering 10 m to 100 km
• Uses fiber-optic sensors, immune to EMI/RFI/Lightning
• Designed for high security
Intelligent Redundant System
• First 100% intelligent redundant controller by design
• Eliminates the single point of failure of controller
• 2nd system automatically turns on when 1st system fails
• Hot-swappable redundant controller
• Automatic data synchronization technology
• Complete redundant system in only 2U size
High Reliability
• The most reliable system by design
• Critical data is never lost with built-in memory backup
• Redundant hard drives/power supply
Top Performance
• Pattern-recognition algorithms for high PD and low NAR
• Typical 6 m location accuracy
• Cut immunity
Easy Deployment
• Easy system installation and tuning
• No electrical power in the field
• Software defined zones
• Remote troubleshooting
Flexible Integration
• Remote User Interface for monitoring multiple systems
• I/O options with XML and relays
• 3rd party integration via SDK/API, GPS Mapping
The EP301 system uses C-OTDR (Coherent Optical Time Domain Reflectometry) optical
technology for distributed acoustic sensing (DAS).
In a C-OTDR system, a pulse of light from a highly coherent laser source with a sufficient peak
power is launched into the fiber, typically a single-mode fiber. As the light propagates along the
fiber, a small fraction of light is scattered by tiny random fluctuations in the refractive index of
the glass in the fiber. Some of this scattered light in the backward direction is captured by the
core of the fiber and guided back to the launch end, where the intensity of this backscattered
light is detected as a function of time and hence location along the fiber. By continuously
monitoring the backscattered light, any changes in the signal due to the slightest movement of
the fiber at a particular location can be identified.
Since contributions to the backscattered light at any instant of time is from a specific location
within half of the pulse-width distance along the fiber, the intrusion signal or environmental
effects at that instant is specific to that location. For example, for a pulse width of ~20 meters
(~100 ns), intrusion and environmental signals will be localized to within ~10 meters along the
fiber for each sample of backscattered light, where the timing of each sample corresponds to a
specific location. This makes every ~10 meters of fiber largely behave independently of other
sections of the fiber, which provides significant advantages over other technologies including
interferometric and zone based. For example, this results in significantly fewer nuisance alarms
as environmental effects do not accumulate along the fiber with distance. Furthermore,
location of an intrusion can be accurately and reliably determined to within half of the distance
corresponding to the pulse width, which is ~10 meters in the above example. Accurate location
detection improves environmental rejection, such as from wind or rain, and allows for precise
tracking of vehicles or trains.
1. 2RU EP301 controller: Front and back of EP301 controller is shown below.
2. 1RU rack-mount LCD keyboard/monitor/mouse combo: This provides access to the user
interface controlling the system configuration and tuning
3. 1 RU splice module: This can connect to the lead-in cable from the fence and to the two
sensors on the EP301 controller. This can also hold the end modules at the end of both
sensors
4. End modules: Each sensor from the EP301 terminates into an end module. A double end
module is needed for both the sensors.
7. Cable ties: Sensing cable is preferably attached to the fence with stainless steel cable
ties if a long life and a high level of security is needed. A cable tie tool is required to
attach the stainless-steel ties to the fence. For situations where the cable will be
installed on a temporary basis, UV resistant plastic cable ties can be used.
8. Relay modules (optional): Sealevel relay boards are integrated with EchoPoint
products. Example of some Sealevel relay boards are 410U and 410N.
The EP301 controller combines both interrogator and processor functions in one 2U box. The
controller is a computer running Microsoft Windows operating system, and EP301 software and
firmware.
All software, firmware, and drivers needed to run the EP301 system are factory installed and
configured. Modifying the system configuration, installing, or running additional software may
result in performance degradation and system failure. Unauthorized modifications of the
computer system may further void existing warranties and service agreements.
The EP301 system software consists of backend and frontend software:
• Backend software: The backend handles data acquisition, alarm processing, interfaces to
3rd parties, and essentially everything except a graphical user interface.
• Frontend software: The frontend connects to the backend and provides a graphical user
interface to control, monitor, and visualize system data and graphs. Frontend software
can run on the EP301 controller, or it can run on any other computer that is networked
to the EP301 controller. In general, the frontend user interface can be closed after the
EP301 system is configured, without impacting the protection of the perimeter.
Auto Startup
By default, the system is configured to automatically initialize its hardware and software
components. This includes logging into a Windows administrator account and launching the
EchoPoint user interface after a short delay. Automatic startup is required for unattended
operation to counteract power interruptions.
• When the electrical power is turned on or restored, the system will automatically power
up.
• The EchoPoint controller will boot up into a Windows administrator account.
• After a one-minute delay that allows background initialization processes to complete,
the backend user interface will open with the login window displayed. Currently, the
backend software is running in the background protecting the perimeter.
• To view/change the system configuration, historical alarms, or to tune the system, the
frontend user interface can be opened.
If the EchoPoint system is configured for manual startup, the operator first has to login to
Windows with a combination of a Username and a Password. When using the system for the
first time, inquire with your supervisor about the account you should use to login to Windows.
Access Levels
There are five levels of access to EchoPoint, which are used to activate certain features of the
control panel and allow changes to be made to the system. The background operation of the
system does not depend on the access level. The Access Levels are
• Admin
• Operator
• Supervisor
• Installer
• Support
Admin
Admin access level controls user accounts and passwords. Initially, only an Admin can login with
a unique password provided by the factory. Once logged in, an Admin can create different user
logins with initial passwords and access levels.
Operator
This is the most used access level for day-to-day monitoring of the perimeter activity. In this
level, tuning parameters and system configuration cannot be changed.
Supervisor
This is the minimum level of access that is needed for changing system settings such as alarm
thresholds and zone definitions, and for accessing alarm and event logs.
Installer
This level of access allows the field service representative to setup and configure the system, to
diagnose the system operation, and to optimize the hardware and software performance. For
security reasons, at midnight, the system automatically terminates an installer session and then
logs in as an operator. The system continues to protect the perimeter.
Support
This level of access is for technical support staff at the factory to login into the system and assist
in advanced troubleshooting.
To launch EchoPoint backend, double-click on the shortcut icon “EchoPoint Backend”, located
on the desktop.
The default location of the program are: C:\EchoPoint\
EchoPoint Backend.exe C:\EchoPoint\ EchoPoint
Frontend.exe
The Backend user interface main panel will open, and you will be prompted to login to the
EchoPoint system. If logging in for the first time, inquire with your Admin about the username,
password, and access level for you to use. You do not have to login as the Backend runs in the
background.
To open the frontend, double click on the shortcut icon “EchoPoint Frontend”, located on the
desktop. You will be prompted to login. If you have any issues with the login, then consult the
Admin.
The Frontend user interface consists of several tabs and menu items that can be accessed by
clicking on them. The Tabs are:
• Monitoring
• Alarm History
• Log
• Tuning
• Setup
• Users
• System
• Map
• Alarm
• Help
Secure: Normal operating state. The system is actively protecting the perimeter and monitoring
for intrusions.
Warning: The system is still protecting the perimeter, but operation is compromised. This could
happen if there is a cable cut in a cut-immune installation.
Disarmed: At least a part of the perimeter is not protected. This can happen if system operation
is severely compromised. This requires immediate attention from the operator.
Alarm Types: The class of the alarm type is shown Intrusion (climb), fence cut, and cable cut. If
there are no current alarms, the Alarm Type says, “No Alarms”.
Alarm location: The actual location of the intrusion along the cable is shown in feet or meters. If
there are no current alarms, the Alarm Location is empty.
Zone name: Any zone name in an alarm state is indicated. If there are no current alarms, the
Zone name is empty.
Monitoring Tab
The monitoring tab is the main display for an operator to monitor alarms anywhere along the
perimeter, especially when the EchoPoint is used as a headend. This displays the map, alarms
on the map, alarms in a list below the map, and provides a means for an operator to clear
alarms.
This tab is accessible to all user levels.
Alarm list
The Alarm list contains all current alarms in the reverse chronological order. New alarms are
added to the top of the list as they are generated. The top-most alarm is the most recent.
Acknowledged alarms are removed from the list immediately. Un-acknowledged alarms are
removed from the list according to the Alarm Auto Clearing settings. Each line of the Alarm List
contains the detailed parameters of the corresponding alarm, including Date and Time the
alarm was generated, location of the alarm, zone name, alarm ID (a unique number assigned to
Map
The design of the map is driven by simplicity and ease of use. Any map of the site in “png” and
“jpeg” format can be uploaded. A perimeter can be drawn on the map and configured to show
GPS and footmarks. An alarm shows as a red solid circle on the perimeter. Zone labels can be
dragged to the map, which blinks red when there is an alarm in that zone. The map can be
zoomed in up to 4x, if necessary.
The Alarm Log table contains the attributes of each alarm since the previous midnight. New
alarm entries are added at the top of the list as soon as the corresponding alarm is declared.
These entries are copied from the Alarm List on the Current Events panel.
The Events list contains information on various system events related to system operation,
including user logging, new alarms and clearing, system changes, hardware performance
notifications, and any user actions.
Alarm and event information is saved to the hard drive every midnight and every time the
software is shut down. All Log Files are maintained indefinitely and can be used for tracing the
intrusion activity and the system performance beyond the current 24-hour time window. This
information is important for diagnosing and troubleshooting the system operation.
• New zones can be created for the system using the “Zone Settings” button
• Zones can be tuned for a high probability of detection and low nuisance alarms. Global
tuning parameters are accessible directly from the tuning tab, while zone-specific tuning
parameters can be accessed by clicking on the “Zone Settings” button.
• Background rejection parameters can be accessed by clicking on the “Background
Rejection” button.
• The waterfall view shows the magnitude of the signal as a function of location for the
entire system. This provides an awareness of activity throughout the perimeter.
• A spectrogram view for any location can be accessed by pressing the “Spectrogram”
button. This provides useful information for setting low-high frequencies for individual
zones.
The top graph displays the highest signal magnitude in the selected zone, or for the entire
perimeter when “View All Zones” is selected. The bottom graph displays intrusion event count
as a function of location. An event is shown as a blue bar, and an alarm as a red bar.
Low and High Frequency: Both low and high frequencies (in Hz) must be chosen based on the
actual signal from the perimeter. Use the spectrogram to look at signal frequencies for climbs
and fence cuts. Generally, “Low Frequency” for a fence cut is higher than for climbs.
Event Threshold: When the magnitude of the signal at a location exceeds the Event threshold
an Event is generated at that location.
Event Range: This is the distance on the cable in meters or feet, within which only a single event
is generated at the location with the highest magnitude within the processing frame time.
Event Expire: The length of time in seconds after which an event is no longer considered for
alarm creation.
Alarm Threshold: The event count necessary within the Event Range and a time range given by
the Event Expire to generate an alarm. This determines the sensitivity of the system together
with Event Threshold.
Alarm Range: This is the distance on the cable in meters or feet, within which only a single
alarm is generated
Alarm Expire: The length of time in seconds after which an alarm expires.
Alarm Mask: The length of time in seconds after an event is generated, during which any new
event is masked and not counted for an alarm.
By right clicking on any zone and choosing the option “Add New Zone”, any number of zones
can be added and configured. Similarly, any existing zones can be removed.
Background Rejection
Rejection of environmental noise is essential for a low nuisance alarm rate. This is achieved by a
sophisticated Background Rejection algorithm. Click on the “Background Rejection” button to
access local and distributed background rejection tuning parameters for Intrusion/climb and
fence cut.
Distributed Rejection removes the background based on environmental disturbances that affect
neighboring locations. The perimeter can be divided into a small number of regions (separately
from zones) if different background settings are needed.
Spectrogram
Alarms can be monitored using SeaLevel relay boards, which provide hardware-based relay
outputs and inputs. If Relays are used either for outputs or inputs, they can be set in the “Zone
Settings”. Click the “Zone settings” button, and then select Relay check box. Every zone can be
configured for output or input relays. Relay inputs can be used to mask a zone. Each relay board
(Board #) can support up to 32 relay output channels (Relay #). Generally, many Relay boards
can be connected in a daisy chain configuration to support many output/input relays.
To mask an alarm from a EchoPoint zone, a relay input can be used either from another EchoPoint
zone or from a 3rd party sensor.
Signal Graph
The graph shows the signal data as a function of fiber length for sensor 1 (blue) and sensor 2
(red). The length of the fiber is indicated by the location where the signal ends.
Gain Settings
Check the box for Auto Gain and Auto Bias. The system will automatically adjust the settings for
Tx, Rx1, and Rx2.
Length Units
Select the Length units: Meters or Feet.
Data Acquisition
This is reserved for Support. Do not change any parameters until recommended by Support.
System Connection
Do not make any changes if the Frontend is running on the controller.
Sensor Cable Settings
Actual Start and Actual End are calculated by the system and displayed. These values may
change slightly with time.
The steps for setting offset and sensor flip for cut immunity (installed in a loop) are as follows:
1. Set “Sensor Offset” to "0" for both sensors. Also set the "Sensor Flip" to FALSE for both
sensors.
2. Hit the fence at any active location and generate alarms for each sensor. Note the
locations.
3. Offset for sensor 2 = location 1 + location 2
4. Offset for sensor 1 = 0
5. For sensor 2, set “Sensor Offset” as in #3 above, and set "Sensor Flip" to TRUE
6. Generate alarms and verify that there is a single alarm each time.
Both sensors overlap completely and are installed in a line configuration. There is no cut
immunity. When there is a cable cut then the perimeter from the cable cut to the end of the
cable loses protection.
The steps for setting offset and sensor flip are as follows:
1. Set “Sensor Offset” to "0" for both sensors.
2. Set "Sensor Flip" to FALSE for both sensors.
3. Generate alarms and verify that there is a single alarm each time.
4. If there are multiple alarms, then do the following:
o Disable Sensor 2 by setting Offset = 100000 m
Hit the fence and find location of alarm from sensor 1 (say 500m)
o Set Offset for Sensor 2 to Offset = 0, and disable sensor 1 by setting Offset =
100000
Hit the fence and find sensor 2 alarm location (say 530 m)
o For the sensor with a lower footmark, add the offset difference.
In the above case, add (530 – 500 = 30m) to sensor 1 offset
Sensor 1 offset = 30, sensor 2 offset = 0, sensor flip = FALSE for both
sensors
• Users
• Map
• Alarm
• Help
Users
This is for user login, changing passwords, and creating new user credentials with Administrator
access.
This is used to save the current configuration, edit advanced configuration parameters, setup
remote interface, simulate system status and alarms, and save and load raw data.
Remote Interface
For details on Remote Interface, refer to the EP301 Interface Manual.
Save Configuration
Selecting this saves the current configuration of the system
Configuration Editor
This is only used if advanced parameters for the system need to be changed. Use this only at
the recommendation of the Support staff.
Simulate
This submenu allows easy integration and testing of EchoPoint system to a 3rd party headend.
“Simulate” can be used to create a simulated alarm in any zone, simulate a cable cut alarm, and
simulate various system status conditions.
For details on Simulate, refer to the EP301 Interface Manual.
Save/Load Data
To save all data, check the “Save All Data” box. However, the file size will be large as well. The
duration of the file save is set in the “Save Duration” field. A 60 s Save Duration is
recommended. The name of the file is set in the “Name” field.
The file size will be smaller if only relevant partial data is saved. For example, if somebody is
climbing around 500 m, then it is better to save ±100m of either side of the climb location. To
do this, uncheck “Save All Data” box, and set Start = 400 and End = 600. Click on “Start Save”
button to start saving.
To play saved data, check the “Load Data” box, select the file, and then click on the play icon.
To load a map and a create a new perimeter, follow the steps below:
1. Go to Monitoring tab
2. Go to Map -> Load Base Map -> jpeg or png, and select the map image to load on the
Monitoring tab.
3. Do the following to draw a perimeter on the map image:
The About submenu shows Model name, as well as software and hardware version numbers.
License Info shows the maximum length (of any of the two sensors) purchased. A new license
with a larger range can be purchased and updated from the License submenu.