CxEye UserManual V1 81 PDF

Kelvin Hughes – Security Systems Ref.
KHS-1003 | Issue 11
TM
CxEye™ Display, Control and Integration

Software Version 1.81
Operator Manual | Issue 11 | January 2019

Commercial in Confidence
Ref: CxEye™ Operation Manual

KHS-1003 issue: 11 Page 2 of 128

The copyright of this document is the property of KELVIN HUGHES LIMITED (2018).
The recipient is to ensure that the contents are only disclosed to those persons having a legitimate
right to know. The recipient should also note that this document is being provided on the express
terms that it is not to be copied in part or as a whole, used or disclosed in any manner or by any
means whatsoever except as authorised in writing by KELVIN HUGHES LIMITED.
Kelvin Hughes Limited
Voltage
6 Mollison Avenue
Enfield
EN3 7XQ
UK
Tel: +44 (0) 1992 805 291
Fax: +44 (0) 1992 805 310
WEBSITE: WWW.KELVINHUGHES.COM
DISTRIBUTION
Copy Held by Organisation
Master Originator Kelvin Hughes
CHANGE HISTORY
Date Issue Summary of change Name
Issue 1 generated from KH document ref
August 2017 1 NCD-22590/CP-25-239-01 issue 5. KH
Updated to reflect software version 1.76.5
September 2017 2 Updated to reflect software version 1.77 KH
November 2017 3 Updated to reflect software version 1.77.4 KH
February 2018 4 Updated to reflect software version 1.78.3 KH
May 2018 5 Updated to reflect software version 1.79 KH
Minor updates added and document
June 2018 6 KH
template updated. Software version 1.79.1
August 2018 7 Updated to reflect software version 1.79.13 KH
November 2018 8 Updated to reflect software version 1.80.6 KH
December 2018 9 Updated to reflect software version 1.80.8 KH
December 2018 10 Updated to reflect software version 1.80.10 KH
January 2019 11 Updated to reflect software version 1.81 KH
REFERENCED & RELATED DOCUMENTS

Number Title Revision Date Authority

Page intentionally blank


1 Contents
1 Contents .......................................................................................................................... 5
2 Introduction ..................................................................................................................... 7
2.1 Summary Specification ............................................................................................................... 9
2.2 Camera Support........................................................................................................................ 10
2.3 Related Documents .................................................................................................................. 11
3 Installation of CxEye .................................................................................................... 13
3.1 Host Requirements ................................................................................................................... 13
3.2 Licensing ................................................................................................................................... 13
3.3 Installing the Software ............................................................................................................... 14
3.4 Command Line Options ............................................................................................................ 16
3.5 Starting CxEye .......................................................................................................................... 16
4 Configuring CxEye ....................................................................................................... 17
4.1 Application Overview ................................................................................................................ 17
4.2 Functional Overview (Local, Drone and C2 Modes).................................................................. 20
4.3 Functional Overview (Client Mode) ........................................................................................... 23
4.4 Operational Overview (Local, Drone and C2 Modes)................................................................ 23
4.5 Operational Overview (Client Mode) ......................................................................................... 25
4.6 Configuration Files .................................................................................................................... 26
4.7 Initial Configuration ................................................................................................................... 27
4.8 Position Data............................................................................................................................. 29
4.9 Radar Field of View................................................................................................................... 29
4.10 Radar Platform .......................................................................................................................... 30
4.11 Spexer Auto-Classification ........................................................................................................ 30
5 Operating CxEye ........................................................................................................... 31
5.1 Menu Bar .................................................................................................................................. 31
5.2 Options… .................................................................................................................................. 34
5.3 PPI Display ............................................................................................................................... 60
5.4 Target Categorisation ............................................................................................................... 71
5.5 Auto Clutter Sequence .............................................................................................................. 73
5.6 Camera Video Display .............................................................................................................. 74
5.7 Target Tote ............................................................................................................................... 83
5.8 Snapshot History....................................................................................................................... 84
5.9 User Account Control ................................................................................................................ 85
5.10 TTM Track Output ..................................................................................................................... 86
5.11 C2 Mode ................................................................................................................................... 87
5.12 Shortcut Keys............................................................................................................................ 89
5.13 Touchscreen Operation ............................................................................................................ 90

APPENDIX A: Area Definition Files ......................................................................................... 91

APPENDIX B: Track Logging to File ........................................................................................ 93
APPENDIX C: Perle IOLAN Configuration .............................................................................. 97
APPENDIX D: Tracker Class Rules File ................................................................................ 103
APPENDIX E: Indigo Vision VMS Integration ....................................................................... 111
APPENDIX F: SPx Camera Manager ...................................................................................... 113
APPENDIX G: Alarm Message Format .................................................................................. 115
APPENDIX H: Heartbeat Message Format ............................................................................ 119
APPENDIX I: RF Target Logging to File ................................................................................ 121
APPENDIX J: Argos RF Detectors ......................................................................................... 123
Contact details ......................................................................................................................... 127

2 Introduction
This manual describes the installation, configuration and operation of the Kelvin Hughes CxEye™
surveillance software application.
CxEye is a self-contained application that provides radar tracking and display, and camera video
display. CxEye is designed to work with Kelvin Hughes SxV radars and provides control of connected
radars as well as receiving ASTERIX CAT-240 radar video data from them.
CxEye can operate in one of several possible modes:
 Local Mode – Provides a local display of radar video or tracks and camera video. When
receiving radar video, performs radar target tracking and track fusion. It is intended for
operators to monitor up to four radar sensors and multiple cameras. Data generated by
instances of CxEye running in this mode is passed up to CxEye instances running in C2
Mode. An instance of CxEye running in Local Mode and its associated sensors together form
a “local node”.
 Drone Mode – As for “Local Mode”, but with the addition of video tracking of drones.
 C2 Mode – Radar track data and camera snapshots received from multiple operator nodes
(operating in Local Mode) and displayed. In this mode, no radar or camera video is
displayed. It is intended for commanders, to give an overall situational awareness. As well as
receiving target information from each of the local nodes, a C2 user can change target
classifications and these changes will flow back down to the local nodes.
 Client Mode – Provides a local display of radar and camera video. Tracking and track fusion
is performed by an external Fusion Server. Multiple instances of CxEye running in client
mode may interface to the Fusion Server to receive track reports and configure threat
information in the Fusion Server’s track and threat database.
The following table summarises the main features that are supported by each of the different CxEye
operating modes.
Local Drone C2 Client
Display of ASTERIX CAT-240 video from multiple radars    
Display of ASTERIX CAT-48/62 tracks from multiple radars    
Remote control of SxV radars via ASTERIX CAT-253    
Internal plot extraction and tracking    
Receipt of SPx format network track reports    
Display of track markers    
Receipt of AIS track data    [1]  [1]
Fusion of AIS tracks with radar tracks    
Provisional auto-classification of tracks    
Threat classification data shared between nodes  [2]  [2]  
Operator classification of targets    
Alarm zones    
Output of network alarm messages    
ATI and no-ATI zones    


Local Drone C2 Client
Manual track initiation and deletion    
Display of camera video    
Control of PTZ cameras including slew-to-cue    
Terrain mapping for camera control    
Automatic camera control    
External joystick for camera control    
Generation of snapshots from camera video    
Display of snapshots    [3] 
Output of TTM reports for all tracks or selected track    
Interfacing to an Indigo Vision VMS system    
Video tracking of drones   [4]  
RF detector target input and fusion with radar tracks    
RF jammer control    
Table 1 – CxEye Operating Modes
[1] AIS data may be used to display additional information for fused tracks that contain a
secondary AIS track MMSI.
[2] When controlled by a C2 node.
[3] Display of snapshots acquired by local nodes.
[4] Video tracking is only supported when used with a compatible external video tracker.
CxEye is designed to be scalable, allowing additional sensors to be added to a node, and additional
nodes to be added to the network.
CxEye is designed to run on a wide range of devices, from desktop PCs with HD resolution monitors
to tablet devices with screen resolutions down to 800x600.

2.1 Summary Specification
Number of radars: Up to 4 Kelvin Hughes SxV supported per local node (up to 11
radars can be configured, but only 4 are fully supported for
tracking and display – the remaining units only provide radar
control).
Radar video input format: ASTERIX CAT-240.
Radar track input format: ASTERIX CAT-48 or CAT-62.
Radar control interface: SxV radar network interface: ASTERIX CAT-253.
Radar tracking: Multi-hypothesis tracker, manual and auto initiation,

programmable initiation areas.
Video tracking: Available with compatible video tracker, fusion between radar
and video track information.
Number of tracks: Not limited by software.
AIS: Receipt of NMEA-0183 AIS tracks as network UDP packets.
Track fusion: Up to 4 track streams plus single AIS stream.
Number of video sources: Unlimited (one camera selected for display at a time, dual head
cameras displayed as picture-in-picture).
Supported video inputs: Any DirectShow compatible devices, RTSP sources.
Camera control interfaces: Pelco-D over serial or network TCP, Chess proprietary, FLIR
Nexus.CGI over TCP, ZEOSys over TCP.
Camera steering mode: Slew-to-cue on selected radar track, manual control (including
external joystick support).
Terrain mapping: Support for use of terrain mapping to automatically slew

cameras to targets on the ground.
Threat evaluation: Manual target classification, automatic provisional classification,

target tote display.
Maps: Support for multiple open source tiled maps, easy zoom and pan
controls, integrated measuring tool, north-up and reference-up
modes.
Alarms: Programmable alarm zones, up to 8 programmable barriers,

visual and audible alerts. Control of alarm zones in an Indigo
Vision VMS system. Output of network alarm messages.
Recording: Screen capture at programmable rate.

Recording of radar video for analysis.
Licensing: USB dongle or MAC address file.


2.2 Camera Support
Pelco-D
CxEye supports control of PTZ cameras using Pelco-D over a serial line or a TCP network
connection. To enable a PTZ camera to be fully utilised by CxEye it should support absolute
positioning. This is part of the extended Pelco-D command set which allows the bearing, elevation,
zoom and focus to be set (e.g. pan to bearing 60 degrees) rather than adjusted (e.g. pan left/right).
For most cameras the absolute positioning extensions to the Pelco-D specification are fairly well
standardised. The only exception is absolute focus control, which is not widely supported. In CxEye,
absolute focus is supported using the command 0x14F.
For absolute zoom and focus control, the values used in Pelco-D messages do not map directly to
real-world units - field-of-view in degrees and focal range in metres. To overcome this limitation,
CxEye supports look-up tables for both zoom and focus that map the values used by the camera to
real-world units. The data required to create these look-up tables may be available from the camera
manufacturer or may need to be determined empirically.
Some Silent Sentinel cameras support “traditional” and “strict” Pelco-D modes. The main difference is
that in traditional mode, tilt is a signed value whereas in strict mode, tilt is an unsigned value. The
flavour of Pelco-D is set in the CxEye camera wizard and must match the camera configuration. The
most common symptom of a mismatch is that tilt operation is inverted. Strict Pelco-D is the
recommended operating mode for Silent Sentinel cameras.
Chess
CxEye supports the control of a Chess ASP director and a Chess Piranha36 camera. Only serial line
control is supported.
FLIR
CxEye supports the control of a FLIR camera using the Nexus.CGI network TCP protocol. Where the
FLIR camera does not support absolute focus control (focal range in metres), CxEye supports a look-
up table as described in section 2.2.1, mapping from camera focus percentage to focal range.
ZEOSys
CxEye supports the control of Hensoldt NightOwl M, NightOwl Z, NightOwl ZM and SparrowHawk
cameras using the ZEOSys network TCP protocol.
Video Tracking
CxEye supports camera control through a video tracking unit. Control uses UDP commands. When
video tracking, the video tracking unit will take partial or full control of the camera.

2.3 Related Documents

The following documents should be consulted for further information:
[1] CP-25-110-13 Dongle Installation
[2] CP-25-110-12 Licence File Installation Notes
[3] CP-25-110-83 ASTERIX Cat-240 Network Data Format
[4] CP-25-110-32 SPx Data Reference Manual
[5] CP-25-110-123 SPx Camera Manager
[6] CP-25-172-01 P172 SBS Radar Controller Manual




3 Installation of CxEye
CxEye is normally supplied on a CD-ROM. Installation is simply a matter of copying the CxEye
directory structure onto a suitable host PC.
3.1 Host Requirements

The requirements for the host PC are dependent upon the number and type of devices CxEye is
interfacing to. For example, how many radars are connected and what camera video sources are
present. These factors will affect the amount of processing CxEye must perform.
The following minimum host specification is suggested, based on two connected radars and receipt of
H.264 compressed camera video over RTP/RTSP:
Operating System: Windows 7, 8 or 10 (desktop mode).

Processor: Intel i5 or better (dependent on configuration).
RAM: At least 2GB.
Graphics: PCIe x16 graphics card installed, NVidia
recommended (NVidia GeForce GT250 or better).
Network Interface: 1GbE, IPv4.
Other Interfaces: USB ports/COM ports/DirectShow video capture
devices, as required by connected equipment.
3.2 Licensing
CxEye is licensed software and requires a valid licence file or USB dongle to be present in the host
system. The application will not run correctly unless a valid licence is detected.
Please refer to reference [1] for details of USB dongle installation or to reference [2] for details of
licence file installation.
Tiled Map Display

The following attributions apply to the map tiles displayed in CxEye.
Default map data is provided by © OpenStreetMap contributors, licensed under ODbL.
Some aerial image data is courtesy NASA/JPL-Caltech and U.S. Department of Agriculture, Farm
Service Agency.
Shuttle Radar Topography Mission (SRTM) terrain data produced by the U.S. Geological Survey.
Map tiles are provided by OpenStreetMap, licensed under CC-BY-SA.
Bing Maps are provided by © Microsoft Corporation.
Google Maps are provided by © Google LLC.

3.3 Installing the Software

CxEye requires no special installation process. It simply needs to be copied or unpacked into the
directory of your choice on the host machine. It may be removed at any time by simply deleting the
directory.
The software may be supplied in a number of different formats, including:
 A zip file, e.g. CxEye.zip
 Uncompressed directory tree on a CD-ROM
Old configuration files may be migrated to add new features and set defaults by running the new
version of the CxEye software with the old configuration file, and saving the configuration with the Set
Defaults checkbox checked (see 5.1.1.7 for further details).
The suggested location for the software is:
C:\CxEye

The standard CxEye installation has a set directory structure, as follows:

Top-level Directory\
∟ CxEye_64.exe - CxEye 64-bit executable file
CxEye.rpi or CxEye-Local.rpi - Default configuration file for Local operation
CxEye-Drone.rpi - Default configuration file for Local drone operation
CxEye-Barriers.rpi - Default configuration file for interfacing with barriers
CxEye-C2.rpi - Default configuration file for C2 operation
Config\ - Configuration subdirectory
∟ Alarms\ - Contains alarm sound files
Areas\ - Contains area definition files
Cameras\ - Contains camera configuration files
Languages\ - Contains language configuration files
Maps\ - Contains world map files
MapTiles\ - Contains tiled map files
MHT\ - Contains additional tracker configuration files
Raster\ - Contains user-defined raster image files
Symbols\ - Contains user-defined target symbol image files
Terrain\ - Contains terrain data (for terrain map)
Wizards\ - Contains Wizard definition files
Docs\ - Documentation subdirectory
Logs\ - Destination directory for log files
Recordings\ - Destination directory for screen recordings
Snapshots\ - Destination directory for camera snapshots
Utils\ - Useful tools (including screen recording replay)
Win32\ - Contains CxEye 32-bit executable file
Note that the CxEye 32-bit executable must be used on 32-bit systems and when VMS integration is
required. When the 32-bit executable is required, copy the contents of the Win32 directory to the top-
level directory.

3.4 Command Line Options

CxEye reads a single configuration file at start-up. By default, CxEye will look for and read a
configuration file named “CxEye.rpi” in the same folder as the CxEye executable. However, it is
possible to provide the name of an alternative configuration file to load, as a command line argument:
CxEye.exe [configFile]
In this case, the application will use the nominated configuration file in preference to the default
configuration file.
CxEye will display a warning and exit if a configuration file is not found.
3.5 Starting CxEye

CxEye may be started in the same way as any other Windows application and will use the default
configuration file.
There are several ways to start CxEye with an alternative configuration file:
 Drag and drop a configuration file onto the CxEye.exe icon or shortcut.
 Create a shortcut to CxEye.exe, edit the properties of the shortcut and append the name of a
configuration file to the Target field.
 Create an empty batch file (e.g. CxEye.bat) and add the following line, replacing
<configFile> with the name of the file. Note that it may be necessary to specify the full
path of the CxEye executable and configuration file.
START CxEye.exe <configFile>


4 Configuring CxEye
This section describes the configuration of CxEye. This is the initial setup of CxEye that affects its
operation and interaction with sensors, rather than the general runtime controls that an operator may
be expected to use.
It is expected that configuration will occur when the CxEye installation is deployed or is being
prepared for deployment and thereafter will not be changed by the operator. The general runtime
operation of CxEye is described in the following section.
CxEye is a licensed software application, requiring an appropriate software licence (supplied as a file
or USB dongle) to be installed on the host system.
4.1 Application Overview

The initial appearance of the application depends on values of certain parameters that have been set
in the configuration file. A typical display is shown in Figure 1.
The application’s main window is divided into several key areas:
 Main radar PPI display
 Camera video display
 Target tote
 Recent camera snapshot display
CxEye is primarily intended for use in full screen mode, where it fills all of the available screen space.
The relative size of each of the main display areas is fixed. In order to preserve usability on smaller
screen resolutions (e.g. 800x600), the camera snapshot display will not be present.
CxEye may be configured for dual screen display (example in following picture), where the camera
video and snapshots are displayed on a second screen, and the PPI and target tote areas are
expanded to fill the primary display.
In Local and Client modes, the camera and snapshots sections will be hidden when CxEye is
configured for zero cameras (the example in the following picture shows a radar-only configuration).

PPI Display
The main radar PPI display area provides the overall situational overview. This area of the window
displays the radar video (in Local, Drone and Client mode) and target positions, as well as the
locations of available cameras and radars. A tiled map underlay is available to provide geographic
reference.
Information about the currently selected target is displayed in the bottom right-hand corner of this
region.
Current, unacknowledged alarms are displayed in the top-left hand corner of this region.
Camera Video Display

In Local, Drone and Client mode, this area of the application GUI provides a display of the currently
selected camera video. In C2 mode, this area is used to display snapshots received from the Local
Nodes.
If the selected camera position has two sensors, both supplying video to the CxEye application, then
the videos are displayed as a picture-in-picture image, with a main video and a thumbnail video. The
videos may be cycled by clicking on the thumbnail video.
Target Tote
The target tote region displays a listing of the top targets, as ranked by their threat level. The threat
level is determined automatically by the application, based on the target’s position, speed and
classification.
Recent Snapshot Display

CxEye provides a means to capture snapshots from the current camera video. This area of the
application interface provides a history of recently captured snapshots.
Snapshots are taken automatically once a target is selected and a camera is slewed onto it for the
first time or when the operator clicks the snapshot button.
User Account Control and Version

When user account control is enabled, a padlock is displayed above the
CxEye logo. A closed padlock indicates Operator mode, an open padlock
indicates Supervisor or Administrator mode.
The version number of the application is displayed below the CxEye logo
and also in the message window.
Menu Bar Active Radar View Scale PPI Camera Camera Camera Video Snapshot
Alarms PPI in km North/fwd Selection Snapshot Window History
Window Button
Camera control
status indicator

Range Selection Target Display Camera Position Selected Target PPI Tools or Target Target Camera Control
Figure 1 - Application Overview (Local Mode)

Buttons Filters Marker (active) Data Display Jammer controls Classification Tote Panel
Buttons

4.2 Functional Overview (Local, Drone and C2 Modes)

Depending on the mode of operation (Local, Drone or C2) CxEye takes in a number of different inputs
and produces various output data. These inputs and outputs are summarised in Figure 2 and Figure
4.
When operating in Local mode, CxEye expects to receive at least one radar video input from a Kelvin
Hughes SxV radar or radar track input from a Hensoldt SPEXER radar (see Spexer Auto-
Classification in section 4.11). It may optionally receive NMEA-0183 AIS data, camera video from up
to fifty cameras (each with single or dual sensors) for display, GPS data for any/all of the connected
sensors and tilt/roll data from any/all of the connected SxV radars.
The outputs of CxEye running in Local Mode are: SxV radar control messages, camera PTZ control
messages, "TTM" track messages for all tracks or selected track, as configured in the Wizard.
Additionally, the following outputs are available for receipt by CxEye operating in C2 Mode: fused
target track messages (for all tracks) and camera snapshot images.
Outputs to CxEye C2
Fused Target Track
Camera Snapshots
Messages
(SPx)
(SPx)
Radar Video
(ASTERIX CAT-240)
Radar Tracks N≤4

(ASTERIX CAT-48/62)
N≤4
Camera Sensor Video
(various formats) Display
Output
GPS Data CxEye
(NMEA 0183)
(Local Mode)
Tilt/Roll Data
(NMEA 0183)
AIS
(NMEA 0183)
RF Target Data
(proprietary format)
(ASTERIX CAT-253)
Messages
Radar Control
(Chess, Pelco-D)
Messages
Camera Control
(NMEA 0183 “TTM”)

Messages
Designated Track
Messages
RF Jammer Control
Outputs to Sensors/External Equipment
Figure 2: CxEye Local Mode IO


Drone mode is the same as Local mode with the addition of video tracking.
Outputs to CxEye C2
Fused Target Track
Camera Snapshots
Messages
(SPx)
(SPx)
Radar Video
(ASTERIX CAT-240)
Radar Tracks N≤4

(ASTERIX CAT-48/62)
N≤4
Camera Sensor Video
(various formats)
Display
GPS Data Output
(NMEA 0183) CxEye
Tilt/Roll Data
(NMEA 0183)
(Drone Mode)
AIS
(NMEA 0183)
Video Tracks
(UDP)
RF Target Data
(ASTERIX CAT-253)
Messages
Radar Control
Pelco-D)
(Video Tracker, Chess,
Messages
Camera Control
(NMEA 0183 “TTM”)

Messages
Designated Track
Messages
RF Jammer Control
Outputs to Sensors/External Equipment
Figure 3: CxEye Drone Mode IO


When operating in C2 Mode, CxEye does not receive data directly from any sensors. Instead, its
inputs are provided by a number of CxEye local nodes. These inputs are target track messages and
camera snapshot images. In return, the CxEye C2 passes down changes to the target classification.
Fused Target Track

Messages
(SPx)
Inputs from CxEye Local Nodes
N≤5
Display
Output
CxEye
(C2 Mode)
Camera Snapshots
(SPx)
N≤5
(SPx)
Target Classification
Outputs to CxEye Local Nodes
Figure 4: CxEye C2 Mode IO


4.3 Functional Overview (Client Mode)

When operating in Client mode, CxEye receives a single channel of fused track reports from a Fusion
Server. The Fusion Server will be running one or more instances of Cambridge Pixel’s SPx Server
application (for plot extraction and tracking) and SPx Fusion Server application (to combine multiple
channels of tracks from SPx Server and provide a centralised track database). Optionally, each
CxEye node may receive up to four channels of radar video for scan conversion and display only.
To Fusion Server
(SPx)
Reports
Fused Track
Threat Reports
(SPx)
Radar Video
(ASTERIX CAT-240)
N≤4
Camera Sensor Video

(various formats) Display
Output
CxEye
GPS Data (Client Mode)
(NMEA 0183)
Tilt/Roll Data
(NMEA 0183)
(ASTERIX CAT-253)
Messages
Radar Control
(Chess, Pelco-D)
Messages
Camera Control
Figure 5: CxEye Client Mode IO
4.4 Operational Overview (Local, Drone and C2 Modes)

A local node consists of a CxEye installation, operating in Local Mode, with one or more sensors
connected directly to it. Data created by a number of nodes may be passed up to an installation
running CxEye in C2 Mode. In C2 Mode, CxEye has no direct sensor inputs of its own but it has
visibility of data from multiple nodes (up to five) and may override the target classifications assigned
by any of the nodes. Drone mode is the same as Local mode, but with the addition of video tracking.
CxEye supports the concept of an "own position", which is typically the position of the operator. The
own position also has an associated heading, which may be used to change the orientation of the PPI
window. Each sensor also has its own position and heading. The CxEye configuration allows all of
this information to be entered manually or received as NMEA 0183 data, for example from a GPS
device.

CxEye operating in C2 Mode,

receives data from multiple
Each CxEye node has a CxEye nodes.
single instance of CxEye
operating in Local Mode and
receiving sensor data directly C2 Centre
from multiple sensors.
CxEye
CxEye
Node 1
CxEye
Node 3
CxEye
Node 2
Figure 6: CxEye Operational Overview, showing example with three nodes and one C2

4.5 Operational Overview (Client Mode)
AIS
(NMEA 0183) There are two Fusion Servers in
a dual-redundant configuration.
The active Fusion Server
Each Fusion Server runs
generates fused track reports.
one instance of SPx Server
for each radar video and an
SPx Fusion Server to
generate a single stream of
fused track reports. Fusion Server Fusion Server
(Primary) (Backup)
SPx Server SPx Server SPx Server SPx Server Shared cameras
controlled by CxEye
nodes via a camera
SPx Fusion Server SPx Fusion Server
manager.
SPx Camera Manager SPx Camera Manager

Each CxEye node has a
single instance of CxEye
operating in Client Mode.
CxEye CxEye
Node 1 Node 3
CxEye
Node 2
Figure 7: CxEye Operational Overview (Client Mode)
The Fusion Server is used to perform plot extraction, tracking and fusion of tracks from one or more
radar video streams and AIS. It also provides a centralised database of tracks and threat data.
Each CxEye node, operating in Client Mode, receives track and threat information from the Fusion
Server. Each CxEye node is able to flow changes to threat information, made by an operator, back to
the Fusion Server, where it is subsequently distributed to all other CxEye nodes.
In this example configuration, there are dual-redundant Fusion Servers, each receiving radar video
from two radars. Three CxEye nodes operating in Client Mode receive track reports from the active
Fusion Server. In this example, each Fusion Server also runs an SPx Camera Manager. This allows
each of the CxEye nodes to control the two shared PTZ cameras, although only one node can act as
the controller at a time.
While the primary Fusion Server is online, CxEye will use it to receive track reports. The backup
Fusion Server operates in “slave mode” and will populate its internal database with tracks received
from the primary Fusion Server. If the primary Fusion Server fails, this will be detected by both the
backup Fusion Server and CxEye. The backup Fusion Server will exit slave mode and make itself the
active Fusion Server. CxEye will start receiving track reports from the backup Fusion Server and also
switch to using the backup camera manager. For further information on slave mode operation, please
refer to the documentation for SPx Fusion Server.

4.6 Configuration Files

The initial state of CxEye is set at start-up through a text-based configuration file.
For each configurable aspect of the application there is a named parameter within the application
configuration file. The graphical controls provided by the application affect the values of certain
parameters at run-time. However, not every available parameter has a corresponding graphical
control.
The configuration file should not be edited directly, unless under instruction from Cambridge Pixel.
Rather, the Wizards (see section 4.7) should be used for the majority of the initial configuration and
the Tools  Options… dialog for any additional configuration changes.
Changes made to the configuration of the application may be saved to a new or existing configuration
file using the File  Save As… menu item.
In addition to the main application configuration file a number of auxiliary files may be used by the
application. These files describe geographic areas for alarms and track initiation and the field-of-view
(FOV) versus range look-up table for the camera sensors.
Area Files
Area files are used by CxEye to define geographic regions in which automatic track initiation (ATI)
should be enabled or disabled (Local Mode), as well as regions which will raise an operator alarm if a
target enters or exits them.
Area files are text files which all use the same format, described in Appendix A on page 91. The
recommended way of creating, editing and saving area files is via the CxEye graphical interface, as
explained in section 5.3.13.3.
4.6.1.1 ATI Area File

CxEye operating in Local Mode uses a single ATI area file to define areas in which ATI is enabled. By
default, this file is named “areas-ati.txt”.
4.6.1.2 Non-ATI Area File

CxEye operating in Local Mode uses a single ATI area file to define areas in which ATI is disabled. By
default, this file is named “areas-no-ati.txt”.
Note that existing tracks may still be updated through non-ATI regions and new tracks may be
initiated manually within non-ATI regions.
Camera Zoom Look-Up Files

CxEye uses a simple text look-up table file to define the camera zoom as a function of range. This
look-up table is used to set the zoom (field-of-view) on the camera sensor when given a target range.
Each line of the file should contain a range value (in metres) followed by the corresponding field-of-
view (in degrees), separated by whitespace. Range values should be monotonically increasing. Lines
beginning with the “#” character are treated as comments.
By default, all cameras will use a file named “zoomLUT.txt”; however, individual files may be specified
via the Camera Wizard.
Camera Field of View and Focus Look-Up Files

CxEye can use look-up files to convert between camera internal zoom position and real-world field of
view (the field of view look-up table, or LUT), and between camera internal focus position and real-
world range (the focus LUT). These may be used when the camera does not support absolute zoom
or absolute focus respectively. They are specified within the configuration file as

Camera<N>.Sensor<N>FovLUTFilename and Camera<N>.Sensor<N>FocusLUTFilename. Each line of

the look-up file should contain a position value followed by the real-world value (degrees of field of
view or focal range), separated by whitespace. Lines beginning with the “#” character are treated as
comments.
4.7 Initial Configuration

Initial configuration of CxEye is best performed using the Wizards provided within the application
itself. The Wizards include descriptions for each of the settings being affected.
The Language Wizard is used to select the language used for text displayed by CxEye. You should
set the language before running any of the other wizards.
The Application Wizard is used to configure the top-level application parameters, such as whether the
application is to run in Local, C2, Client or Drone mode. The Radar Wizard is used to configure
various parameters relating to the radar interfaces, such as the number of radars and their video
output addresses. The Camera Wizard is used to configure parameters relating to the camera
interfaces, such as the number of available cameras and whether they are controllable.
The Wizards are started from within the application itself
and are located under the Configuration menu bar item.
It is strongly recommended that each Wizard is worked
through in turn, saving the configuration at the end of
each.
Language Wizard
This option allows the operator to select the language that will be used for the user interface wording.
Application Wizard
The Application Wizard allows the main top-level application configuration settings to be made. These
settings include:
 User account control
 Operate as Local node, Drone node, C2 node or Client node
 Node ID and name
 Network addresses applicable to the operating mode
 Heartbeat messages
 Full screen and dual screen display, enable/disable click sounds for user interface controls
 Own-platform position or source of position data
 Provisional height classification
 AIS input
 PPI settings (including tiled map source)
 Set the colour to use for unclassified targets
 Target types (names and symbols)
 Target type heights

 Spexer target types (see section 4.11)

 Enable/disable lost threat trails
 Screen recording settings (frame rate, file prefix, max file size)
 Radar recording settings (file prefix, max file size)
 Evidence store enable/disable
 Enable use of external USB joystick
 TTM target output
 Alarm message output
 Control of Indigo Vision VMS
 RF detector settings (including support for Argos RF detectors – see Appendix J)
 RF jammer settings (see section 5.3.18)
Radar Wizard
The Radar Wizard allows setting of all configuration items relating to the radar sensor input and
control. These settings include:
 The number of connected radars
 Name of radars
 Radar resolution
 Radar position or source of position data
 Address for receipt of radar data
 Tracker processing including clutter processing
 Type of radar input – video or tracks
 Radar video display colour
 Radar control settings
 Radar Platform settings
Camera Wizard
The Camera Wizard allows setting of all configuration items relating to the camera sensor input and
control. These settings include:
 Automatic camera mode
 Focus control
 The number of available cameras
 Camera name
 Camera manager settings
 Name of associated alarm zone and VMS integration
 Camera position or source of position data
 Address for control of camera

 PTZ control settings

 Director settings
 Number of sensors / shared video output
 Sensor settings / video source settings (DirectShow or RTSP network)
 Camera presets (only supported with Pelco-D cameras and Pelco-D cameras connected to
video trackers)
Alarm Wizard
The Alarm Wizard allows setting of all configuration items relating to alarms and barriers. These
settings include:
 General alarm settings (area disable intervals and enabling hostile threat lost alarms)
 Alarm sounds (enter the names of .wav files that will be used for the different alarm types)
 Network alarm message reporting
 The number of reference points (up to 5 reference points can be defined)
 Reference point configurations
 The number of barriers
 Barrier start and end position
 Colours used for displaying barriers in the PPI window
 Weighting used in threat calculation
 Generation of target crossing alarms
 Address and port settings used to interface to a Perle IOLAN server
4.8 Position Data

The geographic locations of the own-platform (i.e. the location of the CxEye instance itself), the
radar(s) and any cameras may be set at fixed static locations, by entering their latitude and longitude
coordinates manually. This data may be entered via the relevant Wizard or at run-time via the Tools
 Options… dialog.
Alternatively, any of the required positions may be supplied to the application from external sources of
NMEA 0183 data. NMEA data may be input from a network or serial port source. CxEye can interpret
“RMC” and “HDT” messages to set the position (latitude, longitude) and orientation respectively. In
addition, CxEye can interpret “XDR“ messages to set the pitch and roll of the radar platform for use in
camera positioning when a camera is mounted on the radar.
The network addresses or serial ports to receive data may be configured within the relevant Wizard.
4.9 Radar Field of View

Some radars supported by CxEye are directional, meaning they have a field of view of less than 360
degrees. This field of view can be specified on the Video page of the Radar wizard. When the field of
view for a radar is configured to less than 360 degrees, two radial lines beginning at the radar position
will be displayed in the PPI window to indicate the radar's field of view (example in following picture).
These radial lines are displayed in the configured radar video colour.

4.10 Radar Platform

Directional radars may be mounted on a rotating platform. CxEye supports control of some radar
platforms using a network interface. The configuration of the radar platform is on the Radar Platform
page of the Radar Wizard. The Radars tab of the Options dialog includes a "Platform" section, in
which the communication status is displayed and the current radar platform bearing is displayed and
can be set.
When this option is enabled, one or more “Pan <RADAR> here" context menu items will be displayed
in the PPI right-click menu:
Each configured radar that supports radar platform control will have its own separate context menu
item. The radar field of view indicators detailed in section 4.9 will rotate as the radar platform rotates.
4.11 Spexer Auto-Classification

When ASTERIX CAT-62 tracks are being received from a Spexer radar, the radar may auto-classify
the tracks. These classifications can feed into provisional CxEye target types. The mapping between
Spexer classifications and CxEye target types are configured on the Spexer Target Types page of
the Application Wizard. Each CxEye target type may be given a comma-separated list of Spexer
classifications. A reported track in any of these Spexer classifications will be mapped to the
associated provisional CxEye target type.

5 Operating CxEye
5.1 Menu Bar

The menu bar at the top of the application provides access to controls and settings that are less
frequently needed or adjusted.
File Menu
The File menu contains controls for managing the state of the application. This menu provides the
controls for saving the current configuration, switching to full screen mode and exiting the application.
5.1.1.1 Full Screen

The Full Screen item toggles the CxEye application between Full Screen and window mode. Full
Screen mode is the expected mode of operation in most cases and CxEye will often be configured
(via the Application Wizard) to start in Full Screen mode automatically.
In Full Screen mode, the window border is removed and the application fills the whole screen area,
including the normal Windows menu bar.
The F11 shortcut key may also be used to toggle Full Screen mode on and off.
Note that Full Screen mode is not the same as simply maximising the application window.
5.1.1.2 Second Screen

When CxEye is configured for Dual Screen display, the Second Screen item toggles the display of
the second CxEye window. This second window contains the camera video display and snapshots.
5.1.1.3 Switch User…

When user account control is enabled, the Switch User… item opens a dialog that allows switching
between the Operator, Supervisor and Administrator user modes. A password will be required when
switching to the Supervisor or Administrator user mode.
The F12 shortcut key may also be used to open the Switch User dialog.
5.1.1.4 Set Administrator Password…

The Set Administrator Password… item is used to change the current Administrator password. This
option is only available when the current user mode is Administrator or user account control is
disabled.
5.1.1.5 Set Supervisor Password…

The Set Supervisor Password… item is used to change the current Supervisor password. This
option is only available when the current user mode is Supervisor or Administrator or user account
control is disabled.
5.1.1.6 Save
The Save item saves all configuration changes, overwriting the currently-saved application
configuration. A “Saving all changes…” message will be displayed underneath the company logo.
5.1.1.7 Save As…

The Save As… item is used to save the current application configuration to a file. Any run-time
changes made to the operation of CxEye will be saved when the configuration file is written.
A “Saving all changes…” message will be displayed underneath the company logo.

Note that different configuration files may not be loaded at runtime. The application must be restarted
with a different configuration file at start-up.
The Upgrade checkbox within the save dialog will upgrade various default configuration options to the
values required for recent versions of CxEye. When installing a new version of CxEye with an old
configuration file, it is recommended to use this feature to upgrade any required parameters to match
the requirements of the new version of software.
5.1.1.8 Exit
Select the Exit item to close the application.
Note that any runtime changes made to the configuration will be lost at this stage unless they have
previously been saved to a configuration file.
Tools Menu
The Tools menu provides useful tools and runtime configuration options for the application.
5.1.2.1 Screen Recording…

When selected, the Screen Recording… item will open the screen recording tool.
Clicking on the recording button will initiate screen
recording.
The Screens checkboxes allow selection of the screen(s)
that will be included in the recording (up to a maximum of
3 screens). By default, only the primary screen is
recorded; the default screen can be set by using the
application wizard.
While screen recording is active, the recording button will
change to a pause button and the name of the current
recording file, data rate and free disk space will be
reported.
The filename will be generated automatically, based on a
user-defined file prefix and appended with the date and time.
The file prefix, recording frame rate, file size limit and key frame interval are all configured within the
Application Wizard and may not be changed at runtime.
The New File button can be used when screen recording to immediately start a new recording
file. This allows the screen replay tool to access the recording file that was being written to, without
having to wait for a new file to be created based on the file limit settings. This button is only active
during recording.
Recording files may be replayed using the “SPxScreenReplayWin.exe” application, which is supplied
with CxEye.
The main settings for screen recording can be made in the Screen Recording page of the Application
Wizard. This page can be used to enable or disable screen recording and to make settings for the
files that will be created. The “Auto-start recording” control can be used to start screen recording on
startup of the application (this setting will not disable the screen recording controls described above).
Screen recording can also be initiated on startup of the application, by enabling the ‘evidence store’
mode (in the Evidence Store page of the Application Wizard):

With evidence store mode enabled, the screen recording controls described above will be overridden
and cannot be used. The evidence recording will operate continuously from startup. The screen
recording files will be stored in the “Recordings” folder in date stamped folders for each day.
Recordings will be automatically deleted after a week.
5.1.2.2 Radar Recording…

When selected, the Radar Recording… item will open the radar recording tool.
Radar recording is primarily intended to capture radar
video so that tuning of CxEye’s internal radar tracker may
be performed off-site. There is no facility in CxEye to
replay radar video from a file.
The radar to record is selected using the drop-down menu. Only one channel may be recorded at a
time.
The filename will be generated automatically, based on a user-defined file prefix and appended with
the radar name, date and time.
The file prefix and file size limit are all configured within the Application Wizard and may not be
changed at runtime.
5.1.2.3 On-Screen Keyboard…

The On-Screen Keyboard… item opens an on-screen keyboard as shown in Figure 8. This keyboard
may be used for text data entry on touchscreen devices which do not have an external keyboard. For
example, for target name entry or to input configuration data into the Wizards.
Figure 8: On-screen Keyboard for Touchscreen Operation


5.1.2.4 Messages…
The Messages… item provides a display of information, error and warning messages reported by the
CxEye for the current session.
The messages may be removed
from the memory buffer by clicking
on the Clear Buffer button.
The Freeze Window option may be
selected to prevent messages
scrolling up the window as new
messages are printed.
5.2 Options…
The Options… item opens the CxEye Options dialog, where all of the available runtime configuration
settings may be adjusted. Tabs are provided to adjust the PPI window display, each of the radar
inputs, the camera inputs and to adjust the weightings used for threat analysis.
The Radar Options button in the PPI Tools section of the display may be used as a shortcut to open
the first radar tab of the Options dailog.
PPI Tab
Figure 9: PPI Options Dialog


The PPI tab allows the own-platform position and heading to be specified manually or to be set
automatically from a GPS data source, by checking the Enable GPS box. A status indicator will
display green if GPS data is successfully being received or red otherwise.
The source of GPS data must be pre-configured via the Application Wizard and these settings may
not be changed at runtime.
The brightness of all of the displayed radar videos may be adjusted via the Brightness drop-down
control. Four brightness levels are provided: Off, Dim, Normal and Bright. This control has the same
functionality as the Radar Video control in the main window; it is provided here because, when the
jammer feature is enabled, the Radar Video drop-down is replaced by the jammer controls.
The length of target history trails may be adjusted via the Trail Length drop-down control. Trail history
lengths may be set from 0 minutes (off) up to 20 minutes. This control has the same functionality as
the Track Trails control in the main window; it is provided here because, when the jammer feature is
enabled, the Track Trails drop-down is replaced by the jammer controls.
All of the current tracks may be deleted by clicking on the Delete All Tracks button.
Alarm behaviour may be configured, using the checkboxes in the Alarm Areas section. Display of
visual alarms and sounding of audible alarms may be toggled on/off. Alarms may also be ignored for
targets which are not currently being displayed because target filters have been applied.
All barriers can be reset by clicking the Reset All Barriers button.
The Show Cursor Position checkbox enables or disables the display of the cursor position (this is
shown on-screen as lat/long coordinates when the cursor is held over the PPI display).
The Configure… button within the Tiled Map frame will open a separate dialog to control the tiled
map data.
Figure 10: Tiled Map Options Dialog
The Map Server drop-down menu may be used to select one of a number of different maps for
display. Map tiles for each map are maintained in separate cache directories.

By default, map tiles are cached in the following location, where <server> is the name of the server
that provides the map tiles:
Config/MapTiles/<server>
It is important to note that all cache operations that can be configured through the Tiled Map dialog
will only apply to the cache for the currently selected Map Server.
Note: The tiled map can be enabled or disabled with the PPI Tiled Map section of the Application
Wizard. It is also possible to specify the initial tiled map that will be displayed.
The following map servers are supported:
Open Street Map Mapnik

Coverage: Whole world
Zoom Levels: 0 to 18
This is the default map server. It provides
good coverage and detail including
coastal features.
SRTM Contours
Coverage: 60° N to 56 ° S
This map server uses Shuttle Radar
Topography Mission terrain data to
generate a contour map.
Google Maps
This is the Google map server. It
provides good coverage and detail
including coastal features.
These maps can only be displayed
when an Internet connection is
available.

Bing Maps
Zoom Levels: Road map 0 to 21
Aerial and Hybrid maps 0 to 19
This is the Bing map server. It provides
good coverage and detail including
coastal features.
These maps can only be displayed
when an Internet connection is
available.
To use Google Maps, a licence key must be obtained from:

https://developers.google.com/maps/documentation/javascript/get-api-key
Clicking the Set Key… button in the Google Maps section opens a small dialog:
Enter the licence key and click OK.

Google’s terms of use can be viewed by clicking on the Google Maps Terms of Use link underneath
the Set Key… button.
Available maps are: Google Aerial, Google Aerial Hybrid, Google Road and Google Terrain.
To use Bing Maps, a licence key must be obtained from:
https://www.microsoft.com/en-us/maps/licensing
Clicking the Set Key… button in the Bing Maps section opens a small dialog:
Enter the licence key and click OK.

Bing’s terms of use can be viewed by clicking on the Bing Maps Terms of Use link underneath the
Set Key… button.
Available maps are: Bing Aerial, Bing Aerial Hybrid and Bing Road.
Note: The Bing and Google maps can only be displayed when an Internet connection is
available. They cannot be cached for viewing offline.
The Tiled Map dialog may be used to cache an area for offline display. The area to cache is defined
by the view displayed in the PPI window. The Tiled Map dialog shows the North, South, East and
West lat/long boundaries of the area displayed in the PPI window, together with the current zoom
level.

The Maximum Zoom slider is used to set the maximum zoom level that will be cached. Tiles that are
aligned to the area are cached from zoom level 0 (a single tile displaying the whole world) to the
maximum zoom level set by the slider. The Tiles in Area field shows the total number of tiles in the
area. The lower limit of the Maximum Zoom slider is set to match the current zoom level displayed in
the PPI window. Therefore setting the Maximum Zoom slider to the lowest value will cache all tiles
from zoom level 0 up to and including the current zoom level displayed in the PPI window. Increasing
the maximum zoom level will mean that higher resolution tiles are downloaded and will be available
for display when the view is zoomed in. Increasing the maximum zoom level will significantly increase
the number of tiles in the area.
The Not in Cache field shows that number of tiles in the selected area that are missing from the
cache. The Expired in Cache field shows that number of tiles that are in the cache but are out-of-
date.
The Tiles to Dwnld field shows that number of tiles that will be downloaded. The maximum number of
downloads is limited to 9999 per session. If the value of the Tiles to Dwnld field is displayed in red
and prefixed with “>” then the number of downloads is limited and not all tiles in the area will be
downloaded to the cache. The Disk Space field provides an indication of the amount of free space
available on the disk where the cache directory is located.
Clicking the Start button will start the area caching process. A progress bar will be displayed. The
session may take several minutes or even hours to complete, depending on the number of tiles to
download and the speed of the Internet connection. Whilst a session is in progress the Tiled Map
dialog may be closed and you can continue to use CxEye. Changes made to the view displayed in the
PPI window whilst a session is in progress will not affect the area being cached.
The following steps are recommended to define an area to be cached:
1. Ensure that tiled map display is enabled in CxEye (this is an Application Wizard setting).
2. Select the map that you wish to cache using the Map Server combo box.
3. Zoom in or out in the PPI to determine the maximum level of detail required. Make a note of
the current zoom level, as shown in the Tiled Map dialog.
4. Zoom out in the PPI window to set the coverage required.
5. Set the Maximum Zoom slider to the zoom level determined in step 3.
6. Check the number of tiles to be downloaded and adjust the coverage and/or maximum zoom
if needed.
7. Click the Start button to start the caching process.
Clicking the Update Cache button will update ALL tiles cached for the currently selected Map Server
to the latest version. A confirmation dialog will be displayed showing the cache directory to be
updated. The cache may not be updated while an area caching session is in progress.
Clicking the Delete Cached Tiles button will delete all tiles cached for the currently selected Map
Server. A confirmation dialog will be displayed showing the cache directory to be deleted. The cache
may not be deleted while an area caching session is in progress.

Radars Tab (Local Mode, Drone Mode and Client Mode)
Figure 11: Radar Options Tab
If CxEye is configured to operate in Local Mode, Drone mode or Client Mode, a radar options page
will be present for each radar sensor. CxEye will receive either ASTERIX CAT-240 video or ASTERIX
CAT-48/62 tracks (as configured via the Radar Wizard).
The scroll buttons at the top of this tab are used to select the radar
to configure.
CxEye will support up to 11 radars (set in the Number of Radars section of the Radar Wizard).
However, only a maximum of the first 4 radars (0 to 3) can be used for tracking and display, or the
maximum allowed by the licence - whichever is the smallest.
Any radars that are enabled in the configuration (but do not support tracking and display) may still be
used to provide radar control.
For example, the following picture shows the settings for RADAR_4, which supports control only.

Figure 12: Example of Control-Only Radar Options
Each radar page allows the radar sensor position, heading and pitch/roll to be specified manually or to
be set automatically from a GPS data source, by checking the Enable GPS box. The status indicator
beneath will display green if GPS data is successfully being received or red otherwise. The source of
GPS data must be pre-configured via the Radar Wizard and these settings cannot be changed at
runtime.
The Heading field, which may be set manually or updated from a GPS data source, defines the
heading of the radar relative to north. CxEye will correct the azimuth of received radar video and the
bearing of a co-mounted camera based on the radar's heading so that both are north aligned.
The Pitch and Roll fields, which may be set manually or updated from a GPS data source, define the
pitch and roll of the radar platform. CxEye will correct the bearing of a co-mounted camera based on
the pitch and roll values.
The Platform section allows a bearing to be entered for the radar platform, if control has been
enabled in the Radar Wizard. See section 4.10 for further details.
If the radar is configured for video input, the display of radar video for this radar sensor may be
enabled or disabled by selecting the drop-down in the Video section (available options here are No
Video, Raw Video or Tracker Video). The display of tracker video is intended to assist with
configuration and tuning of the tracker. For normal user display, the Raw Video option should be
selected.
The processed tracker video has a low intensity compared with the raw video. To see the
tracker video in the PPI window, it may be necessary to set the Radar Display Brightness
control on the PPI tab to “BRIGHT” and disable the underlay map.
The status indicator beneath will be green if radar video is successfully being received or red
otherwise. The network address on which to receive ASTERIX CAT-240 video from the radar is set

through the Radar Wizard and cannot be changed at runtime. The colour of each radar video within
the PPI is also configured within the Radar Wizard and cannot be changed at runtime.
The Azimuth Correction field is used to rotate the radar video to correct for any rotational mounting
error between the radar and the heading value.
For Local Mode and Drone Mode only, and for radars configured for video input only, target tracking is
performed on each radar video source separately and the resultant tracks are then passed through a
track fusion process, which aggregates the tracks from each radar video into a single combined set.
The Tracker section of the radar options page provides controls for a subset of tracking parameters,
which may usefully be configured by the operator:
 Sensitivity - this control takes values between 0 and 1. It sets how sensitive the tracking
process is to targets within noise. Lower values will result in fewer false detections, at the
expense of possible missed detections of smaller targets. Conversely, higher values will
result in greater probability of detection but at the expense of a higher false alarm rate.
 ATI Desensitise – this control takes values between 0 and 1. It sets how desensitised auto-
track initiation is, relative to the overall tracking sensitivity. A value of 0 results in ATI with the
same sensitivity as tracking. Higher values will result in reduced sensitivity for ATI relative to
tracking – this may allow the overall tracking sensitivity to be higher, while still avoiding false
positives.
 Min Plot Span – this control takes values between 1 and 5. The span of video that passes
the sensitivity test is considered for further processing if its length exceeds this value, which
is in units of polar store samples. A very small value will allow through small plots, as is
required when tracking small targets. The downside of setting a small value is that more false
tracks will be generated on noise in the radar video. A value of 1 should be used when
tracking very small targets such as people, and a value of 2 or 3 used when tracking larger
targets.
 Max Plot Span – this control sets the maximum span of plots that will be considered for
tracking (in metres). The slider ranges from 0 to 200 metres. Setting the slider to 200 metres
will disable the max size limit so that any size plot is considered.
 Filter Gain - once a track has been acquired, the tracker updates the track’s position, speed
and course using measurements derived from the radar video. Since the measurements are,
in general, not 100% accurate, a combination of each measurement and the tracks predicted
movement will be used, as controlled by the filter gain. The filter gain effectively defines a
level of confidence associated with each measurement. A higher filter gain allows the tracker
to be more responsive to changes in a target’s direction or speed, but also makes it more
susceptible to measurement error. A lower filter gain gives good damping of noise, but
makes the filter slower to adapt to a change in a target’s direction or speed. To overcome
this, CxEye allows the filter gain to be set independently for steady state (non-manoeuvring)
targets and for manoeuvring targets. A manoeuvre is detected and declared by the tracker
based on a predefined criteria. The tracker then switches from the steady state filter gain to
the manoeuvre filter gain. In general, the steady state gain should be set to a low value to
make target tracking less sensitive to noise and errors. The manoeuvre filter gain should
have a high value to ensure that targets are tracked accurately while performing a
manoeuvre.
 Filter Gain (Steady) – this control takes values between 0 and 1. It sets the amount of
filtering applied to target measurements for non-manoeuvring steady state targets. In general
a value of about 0.4 is suggested for this control.

 Filter Gain (Manvre) – this control takes values between 0 and 1. It sets the amount of
filtering applied to target measurements for manoeuvring targets. In general a value of about
0.8 is suggested for this control.
 Auto Initiation – this control takes values from 2 scans to 12 scans. It sets the number of
scans of the radar for which a target must be detected before a track will automatically be
created on it. Lower values will result in tracks forming quickly, at the expense of a possibly
higher false alarm rate. Higher values will result in tracks taking longer to initiate but fewer
false tracks forming. A value of around 5 scans should be used in most situations.
 Max Coasts – this control takes values from 0 scans to 10 scans. It sets the number of radar
scans over which a target track should be “coasted” (estimated) when a suitable
measurement update is not available. Lower values will result in lost tracks being dropped
sooner, but can result in tracks (that would otherwise be returned) being deleted. Higher
values will result in track positions being estimated for longer but could lead to false tracks. A
value of around 3 scans is generally recommended.
 Max Target Speed – sets the maximum speed for tracked targets. If you are only interested
in slower targets then reducing this value can result in better tracking performance.
Note that the tracking and fusion processes have many control parameters within the configuration
file; however, the majority of these parameters should not require configuration. Editing of the
parameters in the configuration file is not recommended, unless specifically advised by Cambridge
Pixel.
When configured for internal tracking (Local or Drone mode), CxEye
supports a number of built-in tracker profiles. The profile is selected from
the Profile drop-down menu in the Tracker section.
In Local mode, the following profiles are available:
 Land - General settings to track surface targets.
 Drone - General settings to track drones.
 Rain - Settings optimised to reduce false alarms in high clutter rain environment.
 VTS - Settings optimised to track sea traffic.
In Drone mode, the following profiles are available:
 Land - General settings to track surface targets.
 Drone - General settings to track drone and surface targets.
 Drone Alert - Higher sensitivity drone detection and tracking.
 Drone Only - Settings optimised to track drones but not larger targets.
Selecting a profile will apply the tracker settings associated with the profile. If the tracker settings are
changed so that they do not match a profile, “Custom” is displayed. When changing from a Custom
profile to a defined profile, such as “Land”, CxEye will remember the custom settings. If required, the
custom settings can be restored by selecting “Custom” in the drop-down menu.
Note: Other profiles (customised) may be provided by Kelvin Hughes as required for specific
installations.
If configured for Client Mode, the tracking controls are disabled.
Control of the radar is provided by the Radar Controller dialog, which will appear when the Open
Controller… button is clicked.

5.2.2.1 Radar Control

CxEye is capable of controlling each of the connected SxV radars. The connection settings are
specified using the Radar Wizard.
To open the radar control dialog, click Open Controller... on the Radar options tab in the CxEye
Options dialog.
Figure 13: Radar Control Dialog
The controls on the left side of the dialog may be used to configure various settings on the radar. Next
to each control is a status indicator. The indicator will be green if the control setting matches the
current radar settings or red if there is a mismatch.
The right side of the dialog displays the current radar status. Clicking on either of the Details...
buttons will open pop-up dialogs displaying detailed status values obtained from the radar.

Figure 14: Radar Status Dialogs
The Alarms window display errors reported by the radar or control software. The Event window
records setting changes that have been made to the radar.
Cameras Tab (Local Mode, Drone Mode and Client Mode)
Figure 15: Camera Options Tab
If CxEye is configured to operate in Local Mode, Drone mode or Client Mode, a Cameras options tab
will be present for all available cameras (as configured via the Camera Wizard).

A “camera” in the context of CxEye means a position or mount hosting up to two physical camera
sensors. So for each camera there could be up to two sensor devices.
The scroll buttons at the top of this tab are used to select the
camera for which the options are set.
Next to the scroll buttons are several checkboxes that configure global camera settings:
 The Auto Camera checkbox mirrors the auto camera button in the controls below the PPI
window. When selected, CxEye operates in Auto Camera Mode. When deselected, the
cameras are controlled manually. For further details, please refer to section 5.6.4.
 If the Hostile Priority checkbox is selected, Auto Camera Mode will give priority to targets
that have been classified as Hostile. Auto Camera Mode will ensure that at least one camera,
and preferably two cameras, are assigned to a hostile target that has triggered an alarm.
If necessary, it will reassign cameras that were previously assigned to targets with a lesser
classification. When disabled, all targets have equal priority.
 If the Switch Display checkbox is selected, Auto Camera Mode will change the selected
camera when an alarm is triggered, to show the most recently assigned camera and display
the camera in the video window. When disabled, Auto Camera Mode will not change the
selected camera.
 If the Idle Return checkbox is selected, Auto Camera Mode will return a camera that has
been idle for an extended period to its home position. The idle period defaults to 60 seconds
but can be changed on the Automatic Camera Control page in the Camera Wizard.
 The Auto Zoom checkbox controls whether or not the camera zoom is continuously
updated, based on the target range as the target moves away or towards the camera.
 The Auto Vertical Scan checkbox enables or disables the use of vertical scanning.
When a radar track is selected, the camera will slew to the track, using the default target
height or home elevation to set the initial camera tilt. With the vertical scanning feature
enabled, the camera slowly tilts up and down while continuing to follow the radar track. The
user can stop the vertical scanning once the track is in view by clicking anywhere in the video
window, by applying any camera tilt, or by double-clicking the camera joystick. Vertical
scanning can also be started manually when following a radar track by double-clicking the
camera joystick.
The minimum and maximum heights for vertical scanning are specified on the Mounting
Location page of the Camera Wizard. The vertical scan speed percentage is set on one of
the Director pages of the Camera Wizard.
Vertical scanning can be combined with video tracker auto-acquisition (set using the V-Track
tab of the Options dialog).
The Calibrate… button opens the camera correction dialog. This calculates the camera height as well
as the camera lean. This is done using two pairs of correction points. Both points in a pair must be on
the same bearing and at the same height, and only one of each pair may be the horizon. Please see
section 5.2.3.1 for details.
Information boxes below the scroll buttons report the status of the selected camera:
 “Type” may be indicated as “Fixed” for static non-steerable cameras or “Pelco-D” or “Chess
ASP” for pan and tilt cameras, depending on the control protocol.
 “Source” indicates whether the sensor video is being captured locally by a DirectShow device
or received over the network from an RTSP source. In the case of DirectShow device input,
the relevant index number is also reported. In the case of RTSP input, the source IP address
and port number are also reported.

 “FOV” indicates the current field-of-view (zoom) for each sensor.

Note that this information reflects the configuration that has been set in the configuration (e.g. via the
Camera Wizard). These values cannot be changed at runtime.
If the camera is only configured for a single sensor (Sensor 0) then the information for Sensor 1 will
be displayed as “---”, to indicate it is absent.
The status indicators below will display green if video is being received from the respective sensors or
red otherwise.
The selected camera position may be specified manually or set automatically from a GPS data
source, by checking the Enable GPS box. The status indicator beneath will display green if GPS data
is successfully being received or red otherwise. The source of GPS data must be pre-configured via
the Camera Wizard and these settings cannot be changed at runtime.
It is also possible to “co-mount” a camera on a radar (within the Camera Wizard). In this case, the
attached camera will use the position of the radar as its position.
For a co-mounted camera, the “bearing correction” control is used to rotate the camera to correct for
any mounting error between the camera and the radar. For a standalone camera, this control is used
to correct the camera's bearing so that it is north aligned.
The “manual” label shows the amount of manual bearing correction that has been applied by panning
the camera while following a target. When switching to follow a different target, this manual correction
will automatically reset to zero. The button next to the manual bearing correction label shifts the
manual bearing correction over to the usual “bearing correction” control above.
Each target type can have a different default height associated with it (set with the Target Type
Heights page in the Application Wizard). With the “Def Target Height” control, it is possible to set (for
“Unknown” target types) a default target height that is used, in combination with the camera height, to
set the initial tilt position of the camera when the camera first moves to look at a target. Note that this
control sets the default target height for "Unknown" type targets only.
The “Use Terrain” control, when checked, indicates that the default target height is above the ground
level at the target’s location. Additionally, with this option enabled, the camera height is above the
ground level at the camera’s location.
The “home” direction of a camera is the reference bearing and elevation that may be set for steerable
cameras or the fixed pointing direction of non-steerable cameras. The Camera options tab allows the
home bearing and elevation angles to be set at runtime. Setting the home bearing and elevation of a
steerable camera will change its reference direction. Setting the home bearing and elevation of a non-
steerable camera will obviously not change its physical pointing direction but its display symbol within
the PPI window will change accordingly.
The “Set home here” button can be used to set the current camera position as the new home
position for that camera.
The camera director will be reported as “Chess ASP” or “Pelco-D” for steerable camera and “---” for
fixed cameras. The current bearing and elevation are also reported.
A value for the camera zoom when the camera is in its home position may be specified via the Home
FOV control. For cameras with full pan-tilt-zoom control this is the field-of-view value that will be used
when the camera is moved to its home position.

The slew-to-cue control selects how the camera is controlling while tracking a target. Two options are
supported:
 In “Absolute” mode, discrete absolute updates will be sent to the camera to update the
camera bearing.
 In “Smooth” mode, CxEye will use a combination of absolute and relative positioning to
control the camera bearing. Absolute positioning will be used to perform initial alignment of
the camera. After this point, relative pan will be used to achieve smooth control of the
camera.
Important: For smooth camera control to operate correctly, the maximum camera pan speed (in
degrees per second) must be set accurately in the Camera Wizard.
The “Data Log” checkbox starts or stops logging of camera-related information to a debug file. There
is a debug file for the camera, and also separate debug files for each sensor associated with the
camera.
5.2.3.1 Camera correction

The camera correction dialog can be used to calculate the camera height and correct for a leaning
camera platform. This is typically a task that would only need to be performed once for each camera.
In the video display, select the camera to which the correction will be applied.
In the CxEye Options dialog, click the Calibrate button to open the Camera Correction dialog.
Figure 16: Camera Correction dialog
Adjust the camera’s bearing and fixed tilt corrections so that the camera is facing in the correct
direction.
To set the bearing correction, find a target in the distance that can be seen on the map and can be
seen by the camera. Use the Pan Camera Here option from the PPI context menu to pan the camera
to the target. Adjust the bearing correction until the Pan Camera Here option successfully centres the
target within the video window.

There are 2 different ways to set correction points – (a) using the PPI or (b) using the horizon.
(a) Set the first correction point (using the PPI)
Figure 17: Correction point setup using the PPI
Specify the location of a known point that can be used for calculating the correction (the top of a
building in this example, but could be any fixed or controllable object appearing as a radar track). To
do this, the operator can either (a) type in the latitude, longitude and height of the point or (b) right-
click on a position in the PPI display and select the Set as camera correction point 1 option
(example in following picture).
If the correction point has a non-zero height, this must be manually entered.
The error in the camera tilt for this point can then be set:

Figure 18: Tilt adjustment
An on-screen indicator will be displayed in the video window to show where the first correction point
would be, based on the currently incorrect camera height and lean configuration. In the following
example, the point should be on top of a building, but the errors in camera height and lean result in
the point appearing some distance above the top of the building:
Right-click on the video display and select the Set as correction point option to specify the correct
location for the correction point in the video window. The best results will be achieved if the camera is
moved to centre this point in the video window.

An on-screen indicator will be displayed in the video window to show the tilt offset for the first
correction point:
(b) Set the first correction point (using the horizon)

Check the Horizon mode box:
Figure 19: Correction point setup using the horizon
Right-click on a point on the horizon in the video display, selecting the Set as horizon location option
(example in the following picture). The best results will be achieved if the camera is moved to centre
this point in the video window.
An on-screen indicator will be displayed in the video window to show the first correction point that has
been defined:

Set the second correction point

The process for setting the second correction point is the same as for setting correction point 1 using
the PPI. However, correction point 2 must use the same bearing and height as correction point
1, but will have a different range. Adjust the range as required.
Set the third and fourth correction points
The third and fourth correction points are set in the same way as the first and second.
Note that the third camera correction point should be set at approximately 90 degrees from the first
point. The third and fourth correction points use the same bearing.
Preview the corrections and finish
Figure 20: Preview correction settings
The Preview Old Correction and Preview New Correction options allow the old and new settings to
be compared before committing the new changes.
Click on Finish to close the dialog and use the new correction settings or click Cancel to discard any
changes.

Weightings Tab
Figure 21: Weightings Options Tab
The Weightings options tab sets the weights that are used in calculation of threat level.
Threat level is calculated according to the following formula:
Threat Level = Wtype + WRange . Range + WSpeed . Speed + WDirection . Direction +

WAlarm + WClassification
Where:
WType is the type-specific weight set in the Application wizard
WRange is the range weight set with the control dialog
WSpeed is the speed weight set with the control dialog
WDirection is the range weight set with the control dialog
Range is a normalised value for the target range (from own position)
Speed is a normalised value for the target speed
Direction is a value for the CPA
WAlarm is an additional weight given to targets within alarm zones
WClassification is an additional weight based on target classification
Adjusting the weights therefore changes the relative level of importance assigned to the target’s
current range, speed and direction.
For each defined alarm zone, as selected by the drop-down menu in this dialog, an additional weight
may also be set. This additional weight is applied to targets which fall within the selected alarm zone.
In addition to the weighting adjustment, there is a control to enable and disable alarm zones - this
control performs that same function as the control described in section 5.3.13.3.

If CxEye is configured to support network output of alarm messages, this feature can be enabled or
disabled here for each alarm zone. A test button (Test Network Alarm) is provided to generate test
alarm messages for the selected alarm zone. Please refer to Appendix G on page 115 for further
details on alarm messages.
It is possible to specify how an alarm is triggered, by selecting either “Enter” or “Exit” from the Rule
drop-down. The alarm zone to be used is specified with the Alarm drop-down.
An alarm can be triggered by a target’s proximity to a reference point. The reference points can be
used to create conditions for triggering alarms.
The following is an explanation of the Enter and Exit rules:
Enter Rule “Enter” is the default rule for alarm zones. With no conditions set, an alarm will be
triggered when a track enters the alarm zone or is created inside the alarm zone.
Optionally, a reference point and bearing condition may be set (with the Point
drop-down and the Bearing Err control). If set, then an alarm is only triggered if
the track is approaching the reference point, +/- the bearing error, either when the
track enters the alarm zone or while it is inside the alarm zone (see Fig. 1 below).
Course
Ref-1
20°
Bearing error Fig. 1 – Approaching reference point
Alternatively, if the Approaching Point checkbox is cleared, the alarm is triggered

when the track is moving away from the reference point, +/- the bearing error (Fig.
2).

Course
20°
Bearing error
Ref-2 Fig. 2 – Departing reference point
Exit Rule With no conditions set, an alarm will be triggered when a track exits from the alarm
zone. Optionally, a reference point and bearing condition may be set (with the
Point drop-down and the Bearing Err control). If set, then an alarm is only
triggered if the track has been consistently approaching the reference point, +/- the
bearing error, from the point it entered the alarm zone to the point it exited the
alarm zone.
Course
Ref-0
Exit point
Entry point
Bearing error Fig. 3 – Exit rule
Alternatively, if the Approaching Point checkbox is cleared, the alarm is triggered

if the track has been consistently moving away from the reference point, +/- the
bearing error, from the point it entered the alarm zone to the point it exited the
alarm zone.
A second optional condition for the exit rule is set by the Max Allowed Speed
control. This defines the maximum allowable speed inside the zone, defined in
metres per second, or disabled by setting to zero. With this condition set, an alarm

will be triggered on exit if the track's average speed while inside the zone exceeds
the maximum allowable speed.
Where multiple exit rule conditions are defined, they are combined using a logical
AND operation. Therefore if both the reference point and maximum allowable
speed conditions are set, the alarm is only triggered if the track was approaching
(or moving away from) the reference point while it progressed through the zone
AND the maximum allowable speed was exceeded.
V-Track Tab (Drone Mode)
Figure 22: V-Track Options Tab
If CxEye is configured to operate in Drone Mode, a V-Track Options tab will be present. The V-Track
Options tab allows control of the video tracker in a Kelvin Hughes SMS-D drone detection system.
The Acquire button within the Mode section will activate the Object Detection Mode (ODM) or the
Track button will activate Object Tracking Mode (OTM). For details of Object Tracking Mode and
Object Detection Mode, see sections 5.6.6.1 and 5.6.6.2.
The Active Area Zoom checkbox commands the system to zoom so that the Detection Area of
Interest (DAI) size matches the video size when transitioning to OTM. If the DAI is already the same
size as the video, then no further zoom will be necessary.
The Detection Area of Interest is the area of the video window in which objects suitable for video
tracking should be detected when in Object Detection Mode (see example in Figure 23). It is
displayed as an open-sided box.
The Auto Acquisition checkbox commands the tracker to transition straight to Object Tracking Mode
on confirmation of a primary target.
Vertical scanning (enabled on the Cameras tab of the Options dialog) can be combined with video
tracker auto-acquisition. Video tracker auto-acquisition will only acquire the video track after the
camera has successfully slewed to the radar track and the same video tracker detection has been
seen for at least 2 seconds. This means that when vertical scanning and video tracker auto-

acquisition are both enabled, the camera will scan up and down until it finds a suitable video track, at
which point it will start video tracking, and the video tracker will take over control of the camera.
The Fuse With Radar checkbox controls whether the current radar track and the current video track
are fused. When fused, the bearing and height indicated by the video track will be combined with the
range indicated by the radar track.
Note: Fusion will occur if (a) the video track is selected first, followed by the radar track or (b) if the
radar track is selected first, followed by the video track – either selection method can be
employed. Clicking anywhere in the video window that is not on the track will stop video
tracking.
Detection Area
of Interest (DAI)
Figure 23: Detection Area of Interest
DAI Size allows the size of the Detection Area of Interest to be adjusted. It has an aspect ratio of 4:3.
When the video tracker is used with dual sensors, the DAI Size setting only applies to the currently
active sensor and may be configured separately for the two sensors.
Radar Coast is the maximum time (specified in seconds) for which tracking of a target will continue
when the video track is valid, but the radar track has been lost.
OTM Coast is the maximum time in seconds for a visually-tracked object (in Object Tracking Mode) to
be lost before CxEye switches over to Object Detection Mode. For details of Object Tracking Mode
and Object Detection Mode, see sections 5.6.6.1 and 5.6.6.2. See section 5.6.6.3 for details of
Coasting Mode.
The Heading Line checkbox enables or disables the heading line (which shows the predicted path of
travel). This is displayed on-screen in Object Tracking Mode.
The video tracker graphics may include the current height of the tracked target or primary detection.
The display of the height as part of the video tracker graphics may be enabled or disabled using the
Label Track checkbox.
The Trails checkbox enables or disables the dotted line (which shows the path that the tracked object
has already taken). This is displayed on-screen in Object Tracking Mode.
The Data Log checkbox enables or disables logging of communications with the video tracker to a
file.
Target Type may be set to match the expected type of target for video tracking – Air, Land or Sea.
Separate options can be selected for the Target Type (Pri) and Target Type (Sec) video inputs (the
Primary and Secondary options are applicable whenever the video tracker has dual sensors, either
sharing a single video output or using separate video outputs). This sets suitable defaults for video

detection and tracking algorithms as shown in the Advanced Video Track Options dialog.
Alternatively, the advanced video track options may be manually configured. When manually
configured (in the Advanced Video Track Options dialog), the Target Type drop-down will display
“CUSTOM”.
The operator can manually configure these settings if they wish, by clicking on the Advanced
Options… button (see Figure 24).
Figure 24: Advanced Video Track Options
This dialog has separate tabs for the Primary and Secondary video inputs (used in the situation where
a camera has dual sensors). In this dialog, the following options can be selected:
Detect Algorithm
Option Description
Manual Allows the user to manually size an inner gate within the detection window.
This is a useful algorithm for targets which do not have a clearly defined bound or
in a cluttered environment where the other modes do not correctly localise the
target. It is very predictable and will always find something to track within the
inner gate. It does, however, require that the target be centred in the field of view
(FOV) and the inner gate must be suitably sized to contain the target and exclude
background clutter.
Hot Spot Detects objects based on their contrast with respect to the background.
Reacts rapidly to targets entering the detection window and accurately determines
target size. Works well for a wide range of target to detection window size ratios.
The target must have contrast (negative or positive) with respect to any other
objects or background present in the detection window. i.e., this algorithm needs
bland backgrounds and little clutter. Overall, this algorithm offers very good
performance for high contrast targets, e.g. air targets viewed by an IR camera.
Motion Detects objects based on their motion with respect to the background.
The algorithm detects objects that have either positive or negative contrast and
are moving with respect to the background within the detection window. It works
well in cluttered scenes, e.g. urban scenarios or those with a lot of trees etc., and
with a wide range of target to detection size ratios. However, sometimes only the
leading edge of a target will be detected and the requirement for movement
means that it takes some time to detect targets. This is a good general-purpose
detection algorithm, especially in cluttered scenes.

Option Description
Naval Contrast-based detection optimised for naval targets.
This is similar to the Hot Spot detection algorithm and detects objects that have
either positive or negative contrast with respect to the background. The algorithm
is optimised for the detection of small and medium size targets in a naval
environment and copes well with the horizontal background gradients of horizons.
It reacts rapidly to targets entering the detection window and offers particularly
good performance in naval scenes viewed with IR cameras.
Detection Priority
The detection priority sets the priority for target selection when multiple targets are
present in the acquisition window.
Option Description
None The user can use the left mouse button to manually select which of the candidate
targets will be designated as the detected target.
Size The largest candidate target within the acquisition window will be designated as
the detected target.
Position The candidate target closest to the boresight and within the acquisition window will
be designated as the detected target.
Combined A combination of distance from the boresight and size of object will be used to
determine which of the candidate targets within the acquisition window is
designated as the detected target.
Track Algorithm
Option Description
Combined Measures target positions using a combination of centroid and correlation
algorithms. The Combined algorithm performs better than the correlation
algorithm with rapidly changing targets and is better in clutter than the centroid
algorithm. This algorithm is a good general purpose default selection especially
where a variety of targets and backgrounds need to be accommodated.
Correlation Measures target positions by finding the best match between a historical image of
the target (pattern) and the incoming image. The algorithm is designed to
operate on objects within a complex scene or on part of the target (such as the
bridge of a large ship). It offers predictable performance and copes successfully
with “coast” events caused by target obscuration. Works well on large and small
targets but rapid target changes can cause the algorithm to lose track, e.g.
manoeuvring aircraft.
Sensor automatic gain control (AGC) changes can cause the algorithm to enter
coast mode when tracking small targets and the algorithm may not be able to
follow rapid target motion, e.g. elevation nod in a very narrow FOV. The algorithm
exhibits very good performance on slowly changing targets, particularly those at
long range (i.e. where AGC changes are slow).
MTT Measures multiple target positions using the selected detection algorithm. For
situations where multiple target tracking is required, the MTT algorithm should be
selected. In this mode of operation, target positions are determined using the
selected detection algorithm (except manual). MTT is more suited to bounded
objects and performs better than the centroid algorithm in clutter.

Option Description
Centroid Measures target positions by differentiating target pixels from background pixels
based on their intensity or contrast and then calculating the centre of the target
pixels. The algorithm is designed to operate on bounded objects (blobs). It is able
to estimate target size and adapt to changes in the target size. It copes well with
target dynamics (acceleration etc.) and target contrast changes (e.g. due to
background variations or changes in sensor gain and offset) but is susceptible to
seduction by bright points in the background or target obscuration. The algorithm
performs well with rapidly changing objects on bland backgrounds, e.g. aircraft
with IR camera.
Scene Measures motion of the whole scene using a modified large area correlation
Lock process. The Scene Lock algorithm is designed to estimate the motion of the
whole scene and ignore the motion of the small targets. This algorithm is useful
when trying to stabilise the motion of the electro-optical system.
Polarity
Option Description
Positive Only objects with a positive contrast relative to the background will be evaluated
by the detection algorithms (does not affect manual detection).
Negative Only objects with a negative contrast relative to the background will be evaluated
by the detection algorithms (does not affect manual detection).
Bipolar Objects with both positive and negative contrast relative to the background will
be evaluated by the detection algorithms (does not affect manual detection).
Automatic This option will select the most appropriate polarity type automatically.
Video Tracker Override
CxEye can usually automatically decide if a sensor configured as part of a camera using
the video tracker as director supports video tracking. In cases where a camera sensor
does support video tracking, but CxEye is receiving the camera video directly from the
sensor, CxEye must be told that this sensor supports video tracking. This can be done on
the Sensor Control pages of the Camera Wizard.

5.3 PPI Display

The PPI window occupies the largest area within the CxEye display. The PPI window shows a bird’s
eye view of the current situation, including map data, the positions of all available radar and camera
sensors and tracked targets. If CxEye is configured to operate in Local Mode, the PPI window may
optionally display the primary radar videos from any/all connected radars. If configured for use with an
optional RF Detector then RF targets will also be displayed.
The PPI window also provides a number of information overlays, such as data on the currently
selected target, a dynamic ruler and any unacknowledged alarms.
PPI
Current
North/Fwd
(unacknowledged)
alarms
Tracked
Target
Radar
Position
Selected
Target
Ruler
Camera Position
(selected)
Ruler
Data
Selected
Target Data
Display
Range
Selection Map
On/Off
Target
Display
Filters Display
Tools /
Jammer
Target Controls
Label
Filters
Figure 25: CxEye PPI Window


General Controls
The PPI window may be zoomed in/out using the scroll wheel on the mouse.
The current view may be panned by holding the left mouse button down whilst dragging the mouse.
Manual track intiation may be invoked by double-clicking with the left mouse button. Manually updated
tracks will be updated/deleted according to the same rules as automatically initiated tracks.
The underlay map may be toggled on and off by clicking on the MAP button near the bottom right
corner of the PPI window.
Clicking the button in the top-right corner of the PPI window will toggle the PPI window
between North-up mode and forward-up mode (the forward direction is defined by the Own
Position heading).
Context Menus (Local or Drone Mode)

Right-clicking inside the PPI window (not on a target) will open a context
menu. Left-click on Pan camera here to have the currently selected camera
point at this position (assuming the currently selected camera is steerable).
Left-clicking on Create track here will initiate a target track at this position.
Manually initiated tracks will be updated/deleted according to the same rules
as automatically initiated tracks. The Pan [Radar name] here option points the currently selected
radar at the specified position.
Right-clicking on a target will open a context menu with options to edit the
chosen target or to delete it.
Context Menus (C2 Mode)

In C2 Mode, right-clicking on a target will open a context menu with the option to edit the chosen
target.
Context Menus (Client Mode)

Right-clicking inside the PPI window will open a context menu. Left-click on Pan camera here to have
the currently selected camera point at this position (assuming the currently selected camera is
steerable).
Right-clicking on a target will open a context menu with options to edit the chosen target.
Target Selection
A target may be selected by left-clicking on it with the mouse. The target symbol for the selected
target will be shown with a box drawn around it, to highlight it.
If a camera is not currently being used by Auto Camera Mode and the
currently selected camera is steerable, then CxEye will automatically slew
the current camera to follow the selected target.
The track data box will appear in the bottom right corner of the PPI
window, displaying details for the currently selected track, such as its
range, bearing and speed.

Clicking on the edit target button (small pencil icon) will open the target editing control for this target.
Clicking on the small “x” icon will close the track data box and also de-select the target.
Clicking on the red “H” button will set the target classification to “Hostile”.
In Drone Mode, the track data box will include the calculated target height, if the target has or is being
video tracked. If the target is currently being video tracked, the calculated target height will be shown
in yellow. If the target has previously been video tracked, the last known target height will be shown in
grey.
When a target is selected, the track data box includes a "PPI TOT" item, showing the time until
closest point of approach between the target and the position of the first configured reference point.
Note that the "PPI TOT" item will not be shown if no reference points are configured.
Cursor Position Display

CxEye can display the latitude/longitude position of the cursor when the
cursor is over the PPI display.
This feature can be enabled or disabled with the Show Cursor Position
checkbox in the PPI tab of the Options dialog.
Radar Video Display

When operating in Local Mode or Client Mode, CxEye can optionally display the primary radar video
for any/all of the connected radars. The colour of the radar video for each radar is pre-configured
(using the Radar Wizard).
The display of individual radars may be toggled on/off within the corresponding radar tabs of the
Options dialog.
The brightness of all of the displayed radar videos may be adjusted via the Radar
Video drop-down control. Four brightness levels are provided: Off, Dim, Normal
and Bright. This control is not available if all the radars are configured for track
input rather than video input.
Note that in Local Mode, target tracking from the radar video will occur regardless
of whether the radar video is displayed.
Target History Trails

The positions of targets on previous radar scans may be displayed,
to show a history of where targets have been. History trails are
shown in the PPI window as sets of small squares behind a target,
matching the target’s symbol colour.
The length of target history trails may be
adjusted via the Track Trails drop-down control. Trail history lengths may be set
from 0 minutes (off) up to 20 minutes.
Clicking the button will clear all track trails displayed in the PPI window.
Using the Enable lost threat trails checkbox in the Application Wizard, CxEye can be configured to
continue to display trail points for a deleted track after the track has been deleted. When this is
enabled and a track has been deleted, the track trail will continue to be displayed in the PPI window in

grey. If the track was tracked for at least 30 seconds prior to deletion, the operator will be able to click
the point where the track was deleted to view details. This feature is disabled 60 seconds after
deletion. The track trail will decay in the same way as for a live track, based on the track trail length
configured in the Track Trails drop-down.
Jammer
The jammer feature is used to control an external RF jammer, typically used for disabling drones.
Settings for the jammer are made in the RF Jammer page of the Application Wizard.
When the feature is enabled, the Radar Video and Track Trails controls (mentioned above) are
replaced with the Jammer controls. The jammer controls are:
OFF – Jammer switched off
ALL – RF and GPS jamming enabled
RF – RF jamming only
GPS – GPS jamming only
Note that the jammer buttons will differ depending on the jammer type selected in the RF Jammer
page of the Application Wizard. The selected button flashes to show the current setting. The
Application Wizard can enable or disable flashing of buttons (using the Enable Flash checkbox).
Clicking the button will clear all track trails displayed in the PPI window.
Note: The Radar Video and Track Trails functionality is available in the PPI tab of the Options dialog
(see section 5.2 on page 34). These controls (Brightness and Trail Length) can be used
instead if the jammer functionality is enabled.
Camera Selection
The positions of all of the cameras available to CxEye (as configured by the Camera Wizard) are
displayed within the PPI window with grey camera icons. The orientation of the camera symbol
reflects its current bearing angle.
A single camera may be selected as active within CxEye.
When selected as active, the camera symbol will turn from grey to orange
and an indication of its field-of-view will be shown (in yellow).
The video(s) from the active camera are displayed in the Camera Video
window.
The active camera may be de-selected by clicking on it again. In which
case, there will be no active camera selected and the video window will be
blank.
Range Buttons
Up to five preset range buttons are displayed beneath the PPI window. Clicking any of these buttons
will cause the PPI display to re-centre on the own-platform position and will set the view scale to the
chosen range.
The ranges of these buttons may be defined in the configuration, via the Application Wizard.

Target Filtering
It is possible to select which targets are displayed based on their type (e.g. helicopter, car, man, etc.)
or their classification (friendly, neutral or hostile).
Clicking on a filter button will toggle it on and off. Target type filter buttons have a white background
when they are on. Target classification filter buttons are bright when they are on. Targets will be
displayed when the corresponding filter type and classification buttons are both on. Targets will be
hidden when either of the corresponding type or classification filter buttons is off.
Hidden targets (i.e. targets that are not displayed because they have been filtered) may still raise
alarms unless the Ignore Hidden Tracks option in the PPI tab of the options dialog has been
checked.
Target labels may be turned off based on target classification. For example, labels for all hostile
targets may be turned off by clicking the hostile labels button.
PPI Tools
CxEye provides graphical tools to select a region for display, measure range and bearing between
two references and to create/edit areas.
5.3.13.1 View Selection

Clicking on the View Selection button in the PPI controls box enables View Selection mode.
Whilst View Selection mode is active, a specific display region may be selected by
left-clicking and holding in the PPI window to set a corner position and then
dragging to define the diagonally opposite corner position.
Upon releasing, after defining the second corner, the PPI window will pan and zoom as necessary to
centre on the smallest area that encloses the selected region.
Note that View Selection mode will automatically be turned off after the first point is clicked.
5.3.13.2 Ruler
Clicking on the Ruler button in the PPI controls box enables the Ruler tool. The Ruler tool allows the
distance and bearing between two end points to be measured. Each end point may be a fixed static
location or a target. If either of the selected end points is a target then the end point will be locked to
the target as it moves and the ruler will be updated accordingly.
To set the ruler, first click on the Ruler tool button, then click on the desired start
point (or target) within the PPI window. Finally, click on the finish point (or target)
within the PPI window.

A dashed blue ruler will be drawn connecting the two chosen

points and an information box will appear in the bottom left of the
PPI window, reporting the distance between the ruler end points
and the bearing between them.
The finish point of the ruler may be re-defined by clicking the
Ruler tool button and then clicking the new finish point in the PPI window.
The ruler is removed by clicking on the “x” button within the ruler information
box.
The ruler displays a “TOT” label in addition to the distance and bearing, if at
least one of the end points of the ruler is a target. This time on target is the time
until the closest point of approach between the two targets or the target and the static location. If the closest
point of approach is in the past, the time will be shown as negative. See also the note about “PPI TOT” in
section 5.3.5.
5.3.13.3 Area Editing

CxEye includes a built-in graphical area editor to allow the simple definition of areas, which may be
used as ATI/non-ATI regions (Local Mode) or for alarms.
Area editing mode is entered by clicking the Area Edit tool button.
Whilst in Area Edit mode, normal PPI control is suspended and any defined areas
will be highlighted within the PPI. An existing area is selected by simply left-clicking
on it. The selected area is then outlined in white and its vertices are marked by
crosses.
Figure 26: Area Definitions
The whole area may be moved by left-clicking on it and dragging. An individual vertex may be moved
by left-clicking it and dragging. The vertex that is being repositioned will be displayed by a yellow
circle with a cross inside. A new vertex can be created by left-clicking on an outline and dragging.
An existing vertex may be deleted by right-clicking.
The Area Editing control will appear beneath the target tote (occupying some of the target tote’s
space) when Area Editing mode is activated, providing controls to change the area’s name,
enable/disable the area (globally or on a per-radar basis) and to exit area editing mode. The options
within the Area Editing control will change according to the type of area being edited:

Figure 27: Area Editing Control for Alarm Areas
Figure 28: Area Editing Control for ATI Areas
Figure 29: Area Editing Control for Non-ATI Areas
The ON / OFF toggle button enables or disables the selected area (note that an alarm area that is
disabled will not trigger alarms, an ATI area that is disabled will not auto-initiate tracks and a No-ATI
area that is disabled (and overlaps an ATI area) will not inhibit ATI).
The timed disable buttons are only displayed for Alarm and ATI areas. By default, they are labelled
10m, 30m, 1h and 6h, but these times can be changed in the General Alarms section of the Alarm
Wizard (Interval 1, Interval 2, Interval 3 and Interval 4 – as shown in Figure 30). The interval for each
button in the wizard is specified in seconds, up to 86400 seconds for 24 hours.
Figure 30: Area Disable Interval Settings in Alarm Wizard
Note: Please also see section 5.5 – the auto clutter timed disable intervals are set in the same
section of the wizard. If set, an auto clutter timed disable may also affect the Alarm and
ATI areas, depending on the intervals chosen.
Clicking on one of these timed disable buttons will disable the selected area for the specified time
interval. While a timed disable is in progress, a message is displayed at the bottom of the control
showing the time remaining for the selected area and the buttons (except ON / OFF) are greyed out:

Figure 31: Area Editing Control Showing Area Disabled Message
At the end of the specified time interval, the area is re-enabled. Alternatively, the operator can click
the ON / OFF button to enable the area and cancel the timed disable.
The radar buttons appear only when editing ATI areas. These are used to specify which radars the
ATI area applies to. ATI will only be performed in the area for the selected radars.
Right-clicking within the PPI window outside of an area will open a context
menu allowing creation of a new area to be used for ATI, non-ATI or for
alarms.
The different types of areas are coloured differently to distinguish them apart. Alarm areas are red,
ATI areas are green and non-ATI areas are blue.
Right-clicking while an area is selected will open an extended context menu, allowing creation of new
areas but also an option to delete the selected area.
Newly created areas begin as squares and vertices are then deleted, added and moved to create
polygons of the desired shape.
Area editing mode remains enabled until exited, by clicking the “X” button in the Area Editing control
or by clicking any of the PPI tools buttons. Any changes made to Areas are automatically saved when
the Area Editing control is closed.
5.3.13.4 Radar Options

Clicking on the Radar Options button in the PPI controls box will display the
settings of the first radar on the Radars tab (in the Options dialog). See “Radars
Tab” on page 39.
The Radar Options button is not available in C2 Mode.
Alarms
Alarms are raised whenever a target track enters a defined alarm zone. Depending on the options set
on the PPI tab of the Options dialog, alarms may be visual and/or audible.
Visual alarms appear as information boxes in the top left of the PPI
window. The target label and the name of the alarm zone that it has
entered are displayed.
Visual alarms are also displayed when CxEye is configured to use an RF detector and a target report
is received (please see section 5.3.17).
Visual alarms must be cleared by clicking on the icon.

If the “Ignore Hidden Tracks” PPI option has been set then alarms will not be raised for targets that
are not visible because they have been filtered.
As a special case, if the severity of a threat type is set to zero in the Application wizard, CxEye will
treat this threat type as an “ignore” type. A threat classified with this type will not trigger alarms.

CxEye can be configured to output an alarm message on the network when an alarm is raised.
Please refer to Appendix G on page 115 for details.
5.3.14.1 Zoom to Track when Alarm Message is Clicked
The track that generated the alarm can be viewed by clicking within the alert box (but not on the
icon). CxEye will zoom in to show the track in the PPI window and the track will also be selected. If a
camera is not currently being used by Auto Camera Mode, the closest camera will slew to the track.
Clicking the alert box a second time will revert the PPI view, track and camera selection back to the
original settings.
5.3.14.2 Customisable Audio Alarms

Alarm sounds for a variety of different types of alarms can be individually configured using the Alarm
Sounds section of the Alarm Wizard. Each different type of alarm may use the default sound (an
empty string in the wizard) or a custom wav or mp3 file. Alarm sound files should be placed in the
“Config/Alarms” folder.
Defined alarm sounds for specific target types will take precedence over the other alarm sounds. For
example, if a target of type 3 triggers an alarm by entering an alarm area (and if an alarm sound is
defined for targets with type 3), then that sound will be used, otherwise the alarm sound defined for
targets entering an alarm area will be used.
5.3.14.3 Lost Hostile Track Alarm

Using the Enable hostile threat lost alarms checkbox in
the Alarm Wizard, CxEye can be configured to trigger an
alarm when a track that has been classified as hostile is lost.
An alarm sound can be configured for this event by using
the Alarm Sounds section of the Alarm Wizard.
Barriers
CxEye may be configured to support up to eight barriers. Each barrier is defined by a start lat/long
position and an end lat/long position. Any targets that are tracked through a barrier will be elevated in
threat severity based on the weighting factor assigned to the barrier. Optionally, the barrier may be
configured to raise a visual/audio alarm. Barriers should be configured using the Alarm Wizard.
Barriers are displayed in the PPI window as a dashed circle.
When zoomed in, the actual position of the barrier will be visible,
represented as a solid line. The name of the barrier is displayed
at the bottom right of the dashed circle.
As a special case, if the severity of a threat type is set to zero in
the Application wizard, CxEye will treat this threat type as an
“ignore” type. A threat classified with this type will not trigger
barrier alarms.
Optionally, a barrier may be interfaced to a physical barrier via a Perle IOLAN server. When a signal
is received from the physical barrier to indicate that it has been triggered, the corresponding barrier
displayed in the PPI window will change from yellow to red (assuming the default colours are used)
and a visual/audio alarm raised. Acknowledging the alarm will send a signal to reset the physical
barrier.
In addition to acknowledging a barrier alarm, all barriers can be reset by clicking the Reset All
Barriers button on the PPI Tab in the Options Dialog.

If CxEye is unable to connect to a physical barrier or a connection is lost then the corresponding
barrier will be displayed in grey in the PPI window.
For details of how to configure a Perle IOLAN server for operation with CxEye, please refer to
Appendix C on page 97.
Reference Points
Up to 5 reference points can be set (using the Number of Reference Points section in the Alarm
Wizard). For each reference point, a name and lat/long position can be set (in the Alarm Wizard).
A reference point is displayed in the PPI as a blue circle with a cross.
Once created and configured, reference points can be used to specify
conditions for triggering enter and exit alarms (using the Point control –
see “Weightings Tab” on page 52).
RF Detector
CxEye can be configured to receive targets from an RF detector. When RF
target reports are received, an alert is displayed in the top-left corner of the
PPI window:
If the bearing of the RF target is known, then the RF target is displayed in the
PPI window as a coloured sector (see example below). A red sector represents a drone or unknown
target. A blue sector represents a remote control.
Figure 32: RF Detector Display
If an RF target report is received but the bearing of the target is not known, then the alert symbol will
flash. The alert will flash until either the operator clicks on it to acknowledge or the bearing of the
target is determined. Clicking on an alert when not flashing will delete the target. However, the target
may appear again if new reports are received from the RF detector.
If CxEye stops receiving reports for an RF target then the sector will be displayed with a reduced
intensity in the PPI window. After an additional period (defaulting to 15 seconds), a lost target will be
automatically deleted. This behaviour may be changed in the wizard. The wizard may also be used to
change the width and length of the target sectors displayed in the PPI window.

If an RF target sector is aligned to a track with the appropriate classification (DRONE for a drone RF
target or MAN for remote control RF target) then the RF target and track will be combined. Once
combined, the RF target and track are shown as a single item in the tote and the RF target class is
displayed below the track name in the PPI window. Clicking on the sector will display information
about the RF target, such as the drone’s RF signal amplitude (see below).
Figure 33: RF Target Details
For more information about RF target file logging, see Appendix I on page 120.
For more information about Argos RF detectors, see Appendix J on page 123.
Jammer RF detection
Some types of RF Jammer can also be used to perform RF detection.
Typically, a jammer that performs RF detection is mounted on top of a PTZ camera. This is configured
in the RF Jammer page of the Application Wizard by setting the zero-based index of the camera.
The bearing of the camera is used to determine the bearing of the RF target. This is indicated by a
coloured sector in the PPI window in the same way as for a stand-alone RF detector (example below).

Target Coasting
If the tracker loses the target, the target will coast. The on-screen graphic will change to indicate the
target is coasting (when all the trackers contributing to a target are reporting the target as coasted, the
target symbol is displayed more transparently than for a normal confirmed target). See example
below.
Normal target
Faded “coasting” target
Figure 34: Example of coasting target
See also section 5.6.6.3 for details of coasting targets in the video display.
5.4 Target Categorisation

Targets may be categorised by their type and by their classification. The mapping of target types can
be changed in the Target Types section of the Application Wizard. An “Unknown” target type is
normally assigned to a class code of 0. Any other target types (as shown in section 5.4.2) can be
assigned to class codes 1 to 6.
Targets may be classified as unknown, friendly, neutral or hostile.
Targets must be categorised manually, via the “Target Editing” control area on the GUI, to set their
type and classification.
Figure 35: Target Editing Control
The Target Editing control will appear beneath the target tote (occupying some of the target tote’s
space) whenever:
 A target symbol is right-clicked in the PPI display and “Edit <Target Name>” is selected from
the context menu,
 A target is selected in the PPI display and the edit button within the target data box is
clicked,
 Right-clicking on the target listing in the tote.
By default, when target tracks are created, their initial type and classification is unknown. Targets with
unknown classification are shown in the colour specified during configuration (in the Application
Wizard) as a plain circle, representing unknown type, until they have had a type set explicitly.

Targets classified as friendly will be displayed in blue, those classified as neutral will be displayed in
green and those classified as hostile will be displayed in red.
If CxEye’s internal tracker (in Local Mode or Drone Mode) or external tracker (in Client Mode) has
been configured to make a preliminary track classification, then the preliminary track type will be
shown in yellow (or a colour set in the Application Wizard). An operator may click on the preliminary
type to confirm it, at which point the standard track classification colour will be used.
Categorising a target as “ignored” will remove the target from the target tote list. The target itself will
still be displayed in the PPI, clearly labelled as an ignored item.
Clicking one of the target categorisation buttons with a target selected will assign the icon for that
target type (for as long as the track exists). The example below shows a target that has been
categorised as a car:
Figure 36: Example of target categorisation
Track Labelling
CxEye will automatically assign a unique track label to targets, based on their target type, appended
with a unique, internally-generated ID number. The Target Editing control allows the target label to be
edited manually.
To edit a track label, simply click in the track label text box and edit the
existing text. Press the ENTER key when finished. Note that the unique ID
number will always be appended to the track label.
User-Defined Target Types

CxEye supports six target types plus an unknown type. The Application Wizard may be used to
configure the name, symbol and severity associated with each target type.
The name assigned to a target type should be limited to a maximum of eight characters. With the
exception of the unknown type, a type may be disabled by setting the name to an empty string.
A target type may be assigned one of the built-in symbols supported by CxEye by setting the image
name to one of the following reserved name tags:
circle_image
cross_image
plane_image
car_image
truck_image

boat_image
drone_image
man_image
helo_image
armvech_image
In addition, the symbol may be read from an image file. If only the filename is specified, then CxEye
will look for the image file in the Config/Symbols directory. It is recommended that this approach is
used, as opposed to specifying the full path to the image file.
The image file must conform to the following rules:
 The image can be in BMP or PNG format
 There is no maximum size restriction on the image (it will be automatically resized to fit)
 The background pixels must be transparent (alpha = 0)
 The foreground pixels must be black with alpha > 0
Please note that colours cannot be used in the image, as when the image is displayed in the PPI
window, the colour of the foreground pixels will be changed to match the threat level colour, e.g.
green for neutral.
An example file, circle.bmp, is provided in the Config/Symbols directory.
The Application wizard also allows a type-specific severity to be assigned to each type in the range
0.0 to 1.0. If greater than zero, then this severity is used in the threat severity weighting calculation.
As a special case, the severity may be set to zero. This will configure the type as an “ignore” type.
Tracks categorised with an ignore type will not trigger alarm zones or barriers and will not appear in
the target tote. This feature can use used to implement a “nuisance” type that can safely be ignored
by CxEye. The cross image is typically used as an “ignore” symbol.
Note: The target types can be changed in the Target Types section of the Application Wizard, so may
differ from the ones in the screen shots presented in this manual.
5.5 Auto Clutter Sequence

Please refer to reference [6] for details of the P172 radar controller.
The P172 radar controller can be configured for AUTO clutter map control (note that this is the clutter
map that is built into the radar and is not related to the clutter map that is part of CxEye).
When this mode is selected and the radar's clutter map is enabled in the radar controller (see Figure
37), certain changes made to the radar via the control panel (such as a change to the radar's range)
will initiate an Auto Clutter Sequence (ACS).

Figure 37: Clutter Map Enabled in Radar Controller Dialog
To open the radar control dialog, click Open Controller... on the Radar options tab in the CXEye
Options dialog.
An Auto Clutter Sequence initiated by any radar controlled by CxEye will also start a timed disable of
all Alarm and ATI areas. The default disable interval is 30 seconds, but this can be changed in the
General Alarms section of the Alarm Wizard (Alarm Area Interval and ATI Area Interval) – see Figure
38.
Figure 38: Alarm Area and ATI Area Interval Settings in Alarm Wizard
Note: An auto clutter timed disable interval that has been set for the Alarm and ATI areas may
affect the primary timed disable settings, depending on the intervals that have been
chosen. See section 5.3.13.3 for details of the timed disable settings.
If required, the timed disable can be cancelled by the operator by clicking the ON / OFF button in the
Area Editing control to re-enable an area. Please also see section 5.3.13.3 for information about the
Area Editing control.
5.6 Camera Video Display

In Local Mode or Drone Mode, the camera video display area of CxEye displays the video from the
sensor(s) attached to the currently selected camera. In C2 Mode, this area shows selected
snapshots, received from local nodes.
If a camera has two sensors fitted and configured then the videos will both be displayed, as picture-in-
picture, with one sensor video occupying the whole area and the other displayed as a thumbnail video
in the top right corner. The videos may be swapped by clicking on the thumbnail video or by pressing
the “/” shortcut key.
If no camera is currently selected, the display area will be empty and black. If no video is being
received from a sensor, the display area will be empty and blue.
In Drone Mode, the Start/Stop Video Tracking button is visible (see Figure 39 and section 5.6.6 for
details).

Selected Target
Name
Camera
Selection drop-
down Second Sensor
Video Display
Thumbnail
Camera
Control Status
Indicator Manual Camera
Direction
Control
Snapshot
Button
Manual Zoom
Control
Start/Stop
VMS Recording Manual Focus
Button Control
Main Sensor Auto Focus Home Button

Video Display Button
Start/Stop Video
Direction Tracking (Drone
Indicator Mode only)
Auto Camera
Control
Laser Range
Auto Zoom Finder
Button
Figure 39: Camera Video Display
Camera Selection
CxEye may be configured to receive and display video from multiple cameras (via the Camera
Wizard). A single camera may be selected for video display. The chosen camera may be selected by
clicking on its icon in the PPI window or by using the drop-down menu above the camera video
window. The video(s) for the selected camera are displayed.
If the selected camera is steerable then any subsequent camera pan and tilt commands will affect that
camera. If a target is selected within the PPI window, the selected camera will be slewed to follow it. If
the Pan Here context menu item is selected from the PPI window, the selected camera will slew to
that position. If the manual camera controls (see below) are used, it is the current camera that will be
affected.
When automatically following a tracked target, the camera’s tilt is set based on the default target
height setting and the camera height, but may subsequently be changed by the operator. If the target
has previously been video tracked, then the last known target height will be used to set the initial
camera tilt position.
Similarly, the FOV is initially set to a value based on the target range (via the zoom LUT file), but may
be manually overridden by the operator. When Auto-Zoom is enabled, the FOV will be automatically
updated as the target moves away or towards the camera in range, but the operator may still apply an
offset to this zoom position in the usual way.

Camera Status Indicator

The camera icon next to the snapshot button, above the video window, shows the status of a network
TCP control connection to the selected camera. This is particularly useful when using CxEye with SPx
Camera Manager as it shows whether the camera is available for use or is being used by another
CxEye node. The camera control status indicator will show one of the following states:
Not connected to camera / camera manager.
Status of camera control is unknown.
Camera is in use by another CxEye node and control is blocked.

This indicator will show as if the camera has been assigned
to a target by Auto Camera Mode.
Camera is not in use and control is available.
Camera is in use by this CxEye node.
For serial control connections, CxEye is unable to determine the control status of the camera and will
therefore display a green “in use” indicator if the serial port is open or “not connected” otherwise.
Camera Controls
On-screen tools are provided, to allow manual control of the selected camera.
The pan and tilt of steerable cameras may be controlled
manually using the soft joystick. Left-clicking and dragging
the central circle of the soft joystick will affect the camera’s
pan and tilt. If supported by the camera, the speed of the
camera movement will be proportional to the displacement
of the joystick. In addition, a user may left-click on any of
the direction arrows in the outer ring to move the camera.
If supported by the camera, its zoom may be adjusted
manually using the Zoom slider control. Left-click the
control knob and drag left to zoom out or right to zoom in.
If supported by the camera, its focus may be adjusted

manually using the Focus slider control. Left-click the
control knob and drag left to decrease focal length or right
to increase focal length. By default, the Focus slider
controls the speed of focus adjustment (i.e. “relative” focus).

The Focus Control section of the Camera Wizard can be used to switch the Focus control’s
behaviour between Relative control, Mixed control, or Absolute control:
 “Relative” control always controls the speed of focus adjustment.

 In “Mixed“ control mode, clicking and dragging the Focus knob will control the speed of focus
adjustment, but clicking on the slider away from the knob will step the focus by either small or
large increments (depending on where it is clicked). The small focus and large focus
adjustment steps can be configured in the Focus Control section of the Camera Wizard.
 In “Absolute” control mode, the only available option is to click away from the Focus knob to
adjust the focus in steps. The small focus and large focus adjustment steps can be
configured in the Focus Control section of the Camera Wizard.
Mixed and Absolute modes require that the camera being controlled supports absolute focus control.
When in either of the Mixed or Absolute modes, the Focus control slider is
displayed with additional vertical lines.
Clicking the “home” button will move the camera back to its home position and adjust its zoom to
the preset home value. The values for home bearing (pan), home elevation (tilt) and home zoom
(Home FOV) are configurable at runtime through the Cameras tab in the CxEye Options dialog (see
“Cameras Tab” on page 44).
Clicking the AF button will enable autofocus on the camera, if supported by the camera.
The camera control area also provides an indication of the camera’s current pointing
direction and FOV, shown by the yellow segment in the plan indicator.
Control of the camera direction is also possible by left-clicking and dragging in the
video window itself. “Pinch-to-zoom” is supported inside the video window, to control
the camera zoom. While following a track with a camera, left-clicking inside the video
window will add a correction to the tracking to centre the video window on the position that was
clicked.
5.6.3.1 Supported Control Interfaces

Each camera control interface must be specified during the configuration (via the Camera Wizard)
and cannot be changed at runtime. Depending on the physical camera director and the sensor(s)
mounted on it, there may be different control protocols used to steer the camera and to perform
zooming and focusing.
Currently supported control protocols for the camera director are:
 “Chess ASP” – a Chess Dynamics proprietary protocol for control of its “ASP” camera
director.

 “Pelco-D (extended)” – an open camera control protocol with extended commands to allow
absolute positioning.
 “FLIR” – a proprietary protocol (Nexus.CGI) for control of the FLIR camera director.
 “NightOwl M”, “NightOwl Z”, “NightOwl ZM”, and “SparrowHawk” – a proprietary protocol
(ZEOSys) for control of various Hensoldt camera directors.
 “SMS-D” – camera control via the SMS-D video tracker (only available in Drone operating
mode).
Note that for the FLIR, NightOwl/SparrowHawk and SMS-D cameras, each of the sensors should
be set to use the director controller (“Combined with Director”) rather than separately configured.
Currently supported control protocols for zoom and focus are:
 “Chess Piranha36” – a Chess Dynamics proprietary protocol for control of its “Piranha 36”
daylight camera sensor.
 “Pelco-D (extended)” – an open camera control protocol.
5.6.3.2 External Joystick

If a USB joystick is connected to the CxEye host system then it may be used to control the camera’s
pan and tilt. Left and right control the camera’s horizontal rotation (pan). Up and down control the
camera’s vertical inclination (tilt).
The joystick button may be used to take snapshots. The joystick may also be used to control the
camera zoom.
Any driver software supplied with the joystick should be properly installed prior to running CxEye.
A joystick is enabled or disabled using the External Joystick section of the Application Wizard.
Auto Camera Mode

CxEye supports an automatic camera control mode (Auto Camera Mode). This can be enabled or
disabled from the GUI (or camera options dialog) using the following control:
Simultaneous control of multiple cameras is supported in
this mode. With automatic camera control enabled, CxEye
will automatically control the most appropriate camera to
track a target that enters or exits an alarm zone (depending
on the Enter and Exit rules that have been set – see
“Weightings Tab” on page 52).
When Auto Camera Mode is enabled, CxEye will automatically assign cameras to targets that have
triggered alarms (either Enter or Exit alarms, as configured for an alarm zone). CxEye will assign
cameras that are in the same alarm zone from which the alarm was triggered, or as a fall-back,
cameras that are not in any alarm zones. Alarm zone cameras are assigned in preference to fall-back
cameras. For Enter alarms, once a target exits the alarm zone, the camera will stop tracking. For Exit
alarms, the camera will only stop tracking when the target is lost or deleted, or is reassigned to a
higher priority target.
CxEye will decide which is the best camera to assign to a target. If a second camera is available, this
will be assigned as well - however, no more than two cameras will be assigned to a single target.
If two cameras are assigned to a target and one of the cameras is being used to perform video
tracking, CxEye will use the target's height to control the elevation of the second camera. The joystick
tilt controls for the second camera will therefore be disabled.

As targets move position and new alarms are triggered, Auto Camera Mode will reassign cameras to
ensure that the best coverage of targets is achieved. If an alarm zone contains multiple cameras,
CxEye will automatically hand over tracking from one camera to another as the target moves through
the alarm zone.
If a camera is not being used by Auto Camera Mode, it is available for the operator to control
manually. However, Auto Camera Mode will have priority and may take control of a camera at any
time if it is needed.
If CxEye is configured to control an Indigo Vision VMS system and automatic camera control is
enabled, CxEye will send a detector alert to the VMS system when a target enters an alarm zone and
send a clear zone message when a target exits an alarm zone. In addition, CxEye will command the
VMS system to export video for cameras once they have stopped tracking a target. For further details,
please refer to Appendix E on page 111.
Auto Zoom Control

This control has 3 states: disabled, auto zoom enabled,
focus-only auto zoom enabled. When enabled, the zoom of
the camera is adjusted as the target's range increases or
decreases. If absolute focus is supported, and auto-focus is
disabled, the focus distance will also be adjusted. When in
focus-only mode, only the focus distance will be adjusted as
the target's range increases or decreases. If a target stops or moves tangentially, no zoom or focus
changes will occur. The user may apply an offset to the automatically calculated zoom and focus
using the usual zoom and focus controls. These user offsets will be reset when selecting a new
target.
The following table shows the Auto Zoom button’s states and the corresponding states of the Auto
Zoom checkbox on the Cameras tab (in the Options dialog):
Button Auto Zoom checkbox state (Options dialog) Description
Auto Zoom disabled.
Auto Zoom enabled.
Focus-only mode enabled.

This option is only supported if the camera
supports absolute focus control.
Start/Stop Video Tracking

Note: This control is only visible if CxEye is in Drone Mode,
used with a Kelvin Hughes SMS-D system.
This toggle control starts or stops video tracking -
transitions between Object Detection Mode (ODM) and
Object Tracking Mode (OTM). The user can start video
tracking by either selecting one of the multiple detections in
the video window or by clicking this button to to video track the primary detection. Clicking this button
while video tracking will stop video tracking and transition back from OTM to ODM.

5.6.6.1 Object Detection Mode

With Object Detection Mode, the video tracker detects potential objects of interest.
In Object Detection Mode (see Figure 40), the area in which potential targets will be detected is the
Detection Area of Interest (DAI), displayed as an open-sided box within the video window. Secondary
detection targets are each shown with a small cross, whereas the primary detection target is shown
with a box around it. The camera boresight (i.e. the centre of the DAI) is represented by a cross-hairs
symbol.
Video tracking of a specific detection can be initiated by clicking on the detection within the camera
video window. Clicking elsewhere in the camera video window will recentre the camera on the click
position. Clicking and holding for more than 1 second elsewhere in the camera video window allows
the DAI to be resized. Once resizing is complete, by releasing, the camera video window will recentre
on the click position.
Primary
detection target
Secondary
detection target
Secondary
detection target
Camera
boresight
Detection Area
of Interest
Figure 40: Object Detection Mode
5.6.6.2 Object Tracking Mode

In Object Tracking Mode, the SMS-D video tracker takes control of the camera pan and tilt position
in order to maintain the tracked target in the centre of the camera video window.
When video tracking in Object Tracking Mode (see Figure 41), the tracked target is shown with a
rectangular box. In addition to this, the target displays a line that indicates the direction of travel (the
“Heading Line”). Trailing the target is a dotted line (“Trails”), tracing the path already travelled by the
target. The distribution of the dots in the line gives a rough indication of the object’s speed (the further
apart the dots are, the greater the speed). The camera boresight is represented by a cross-hairs
symbol. No DAI is shown in Object Tracking Mode.
To disengage from OTM (and thus stop video tracking), the user can select the cross-hair icon to
transition back to ODM. To resume video tracking of the same target, the user must manually re-
select the target.

Path travelled Direction of

by target travel (Heading
(Trails) Line)
Camera
boresight
Tracked target
Figure 41: Object Tracking Mode
5.6.6.3 Video Track Coasting

If the video tracker loses the target in Object Tracking Mode, the target will coast. The on-screen
graphic will change to indicate the target is coasting (see Figure 42). If the target is re-acquired by the
video tracker within the maximum coast time (as set by “OTM coast”), the video tracker will continue
to track the target and the on-screen graphics will revert to the usual Object Tracking Mode graphic. If
the target is not re-acquired within the maximum coast time, the video track will be lost and the video
tracker will transition back to Object Detection Mode.
“Coasting” graphic
Camera boresight
Figure 42: Coasting Mode


5.6.6.4 Manually Specifying the Detection Area of Interest

It is possible to manually specify a video tracking Detection Area of Interest (DAI) using the CxEye
camera window while in drone mode.
The operator can move the camera to align a new position with the boresight by touching or clicking
anywhere on the video window.
Figure 43: Adjusting the DAI area manually
To select a more focused tracking area, the operator can click and hold anywhere on the camera
window. After 1 second, the open box DAI graphic will appear, which can be adjusted by dragging the
cursor/finger inward or outward from the centre (as shown in Figure 43 – the green arrow has been
added for illustrative purposes only).
5.6.6.5 Cameras with Dual Sensors

Where a video tracker supports 2 camera inputs, with one of the 2 inputs being video tracked:
For cameras that have dual sensors, a choice of behaviour can be configured (using the Number of
Sensors section and the various Sensor sections in the Camera Wizard):
 A - Both camera inputs are displayed as separate video inputs to CxEye with the normal
picture-in-picture switch. The input that is in the main window in CxEye is the one that can be
video tracked.
 B - There is a single video input to CxEye (i.e. no picture-in-picture is displayed), but a button
(see below) in the top-right corner of the video display can be used to switch which video
input the video tracker will send to CxEye.
 Where a video tracker controls two sensors and both video streams are available to CxEye,
but only one sensor is controlled at any one time, this option is controlled with a “Dual
Cameras” option in the Number of Sensors section of the Camera Wizard. When the dual
cameras option is enabled, both camera sensors are individually controllable, but only a
single sensor is controllable at one time.
Where a single video input is configured and the camera has dual sensors, the video display
can be swapped between the sensors with this button. Settings for object tracking can be
different for each sensor, set with the Advanced Video Track Options dialog (see Figure 24)
and in the V-Track tab of the CxEye Options dialog. See “V-Track Tab (Drone Mode)”.

Note: This control is only visible if the Shared video output? checkbox has been checked in the
Number of Sensors section of the Camera Wizard.
When controlling the video tracker, CxEye may be configured for Slave Zoom Mode, where CxEye
does not control the zoom/focus of the non-active camera sensor. This mode is enabled/disabled with
the Video tracker slaving sensor? checkbox on the Number of Sensors section in the Camera
Wizard. Note that this control is only available when CxEye is in Drone mode and has at least
one camera set for SMS-D (this is set in the Director section of the Camera Wizard).
Laser Range Finder

Note: This control is only visible if CxEye is connected to a
camera with a supported laser range finder.
Clicking this button will initiate a one-shot laser range finder
measurement. The measured range will be displayed in the
bottom-right corner of the video window.
Manual VMS Control

When CxEye is configured to control an Indigo Vision VMS system, manual control of recording is
supported by the VMS record button. Manual recording applies to the camera that is currently
selected in CxEye.
The VMS record button will only be enabled if a camera is selected that is controllable (as shown by
the camera control status indicator) and automatic camera control is disabled.
Clicking the VMS record button will send a detector alert to
the VMS system for the selected camera and the button will
change to display a stop symbol, indicating that recording is
in progress.
Clicking the VMS record button a second time will send a
clear zone to the VMS and export a video clip from the
camera.
While recording, selecting a different camera will stop recording. Recording will also be stopped if the
camera becomes unavailable (when using SPx Camera Manager).
5.7 Target Tote

The target tote area displays principal details for the highest priority targets, ordered according to their
threat level. For each entry within the tote, the target’s name, range, bearing, type and classification is
shown.
Note: The HGT column only appears when CxEye is in Drone Mode, used with a Kelvin Hughes
SMS-D system. The HGT column shows the target height in yellow when the target is actively
being video tracked. When a target has previously been video tracked, but is no longer being
video tracked, its last known height is shown in grey or white. The target’s calculated height is
based on the target range indicated by the radar, the tilt of the camera when video tracking,
and the configured camera height.

Figure 44: Target Tote
Left-clicking on a target entry will highlight the entry in the tote and also select that target within the
PPI (see section 5.3.3).
Right-clicking on a target entry will highlight the entry within the tote, select that target within the PPI
and also open the Target Editing control.
The quick target switch button simplifies toggling between two targets. Left-clicking the quick
target switch button will toggle between the currently selected target and the previously
selected target. Right-clicking the quick target switch button will select the target with the
highest threat level.
When CxEye is configured to use an RF detector, the LEVEL column is replaced with a DRONE
TYPE column. The type of RF target is displayed here, for example “DJI Drone 2.4” (see below). See
section 5.3.17 for details of the RF detector functionality.
Figure 45: Drone Type Details
5.8 Snapshot History

The snapshot history area of the display shows a reel of the most recent still images taken from the
camera video. Assuming a camera is available, a snapshot is produced when:
 the snapshot button is pressed,
 the snapshot shortcut keyboard button is pressed,
 a target is selected and a steerable camera is slewed onto it.
Snapshots are generally associated with a target and the snapshot history area shows the most
recent snapshots for each target. If a target is selected that does not yet have any associated
snapshots then this area will be empty. Conversely, if a target is selected that has multiple snapshots
associated with it then these snapshots are displayed in chronological order, with the most recent
towards the top.
The first target snapshot will be taken automatically when a target is selected for the first time.

CxEye in Drone Mode will only take the first target snapshot after video tracking has been initiated on
a target.
If no target is currently selected then the most recent snapshots (irrespective of target), are displayed
in chronological order, with the most recent towards the top.
Snapshots are displayed with their date and time information above them.
If a target was selected when the snapshot was taken then the target name
will also appear. The target lat/long position is stored as metadata within
the snapshot image file.
Snapshots are shown most recent at the top. As new snapshots are taken,
previous ones are shifted down and will eventually disappear out of view.
Right-clicking on a snapshot opens a small context menu offering the

option to delete that snapshot.
The image reel may be scrolled by left-clicking and dragging up or down.
Snapshot Directory
CxEye saves every snapshot into a date-stamped directory on the host system. A fresh date-stamped
directory is automatically created when the first snapshot is taken after CxEye is started. These date-
stamped directories are created in the following location on the host system disk:
<CxEyeDirectory>\Snapshots\<DateStampDirectory>\
Where “CxEyeDirectory” is the location of the CxEye executable file.

The location of the snapshot directory is reported by CxEye within the Messages dialog.
5.9 User Account Control

CxEye supports user account control with three different user access levels: Administrator,
Supervisor and Operator. Some features of CxEye are only available to Administrators, and some
only to Administrators and Supervisors, while other features may or may not be available, depending
on configuration file settings. The customisable features may be configured using the Application
Wizard. Table 2 details which CxEye features are available (), locked down () or customisable (C)
for the different users.

Function Operator Supervisor Administrator
Camera Wizard   
Radar Wizard   
Alarm Wizard   
Application Mode Selection   
Radar Azimuth Correction   
Camera Bearing Correction  C 
Mast Height  C 
Application Wizard  C 
Change Language  C 
Default Target Height C C 
GPS Enable/Disable C C 
Area Editing C C 
Radar Tracker Settings C C 
Camera Home Position C C 
Full Screen Control C C 
Auto Camera Control C C 
Table 2: User Access Levels
The initial user access level is configurable through the Application Wizard. The Administrator and
Supervisor accounts require a password. This password must be entered when the application is
started with the initial user access level as Administrator or Supervisor or when switching user (see
section 5.1.1.3).
The Administrator password may be changed by an Administrator using the menu (see section
5.1.1.4). The Supervisor password may be changed by an Supervisor or an Administrator using the
menu (see section 5.1.1.5). After changing a password, the configuration file must be saved for the
change to persist after restarting the application.
User account control may be completely disabled using the Application Wizard. When user account
control is disabled, all CxEye features are available.
When user account control is enabled, an indication of the current user is shown using a padlock
symbol above the CxEye logo (see section 4.1.5). A closed padlock indicates the current user access
level is Operator, an open padlock indicates the current user access level is either Supervisor or
Administrator.
5.10 TTM Track Output

CxEye provides an optional output of NMEA-0183 “TTM” (Tracked Target Messages) for all targets or
the selected target. This output is intended as a general target designation output, which may be used
by external equipment (for example, an optical tracking system).
An example TTM string generated by CxEye is:
“$RATTM,8,0.5568,141.9,T,4.1,28.0,T,0.5,3.28,N,T8,T,,092154.559,A*51”

The individual fields of this message are described in the following table:
Field Example Value Description
Message name RATTM Five characters, ending in “TTM”.
Track ID 8 Unique internal track ID.
Target Range 0.5568 Target range in nautical miles.
Target Bearing 141.9 Target bearing in degrees.
Bearing Type T Bearing is TRUE.
Target Speed 4.1 Target speed in knots.
Target Course 28.0 Target course in degrees.
Course Type T Course is TRUE.
CPA 0.5 Closest Point of Approach, in nautical miles.
tCPA 3.28 Time to CPA in minutes

(-ve value implies target is receding).
Units N Distance units are nautical miles.
Target Name T8 Name of target (ID above prefixed with “T”).
Target Status T Target status (Lost, acQuiring, Tracked).
Not Used Empty This field is not used by CxEye.
Time 092154.559 Time since midnight in minutes and seconds.
Track Type A Automatic or Manually initiated target track.
Checksum 51 XOR of all fields, used to validate message.
Table 3: TTM Message Fields
The TTM track reports are provided as a UDP message output onto the network. The destination
address for these messages is pre-configured, through the Application Wizard, and cannot be
modified at runtime. The destination may address may be a unicast address (to send messages to a
single designated client) or it may be a multicast address (to send the messages to any number of
receiving clients).
This feature is not currently available in Client Mode.
5.11 C2 Mode
CxEye may be configured to operate in C2 Mode, receiving data from up to five local nodes, rather
than directly from sensors. A C2 system has the ability to change a target’s label, type and
classification and this change is passed down to the Local node(s).
In C2 mode the graphical interface is largely the same as in Local mode, with the exceptions that the
camera control area is not present and nor are the snapshot button or camera selection drop-down.
The Options dialog is also simplified in C2 mode, providing a PPI tab and a Weightings tab but not
sensor tabs.
The PPI area is used to display track data received from connected local nodes. Radar video is not
available in C2 mode.

The camera video display area is used to display snapshot images received from connected local
nodes. Live camera video is not available in C2 mode.
Configuration
The C2 system must be configured to tell it the details of the local nodes that it is expected to connect
with. It is recommended that the Application wizard is used for this configuration. Configuration may not
be changed at runtime.
The number of local nodes and their IP addresses must be specified within the configuration, along with
an ID to be used for each local node. The multicast address on which each local node and the C2
should exchange data must also be set. Note that the same data address may be used for all nodes, as
long as they all have unique IDs assigned.
A port number must also be specified for a TCP connection between the C2 and each local node. This
is used by the C2 system to send control commands down to the local node(s), for example, to change
a target’s label, type or classification.
Target Categorisation
CxEye supports the same target categorisation facilities in C2 mode as it does in Local mode. However,
any changes to a target’s label, type or classification made in a C2 system will be flowed down to
connected local nodes. Operators at the local nodes will see target details change on their displays.
Please note that in a C2 system, all instances of CxEye must be configured with identical names and
symbols for each of the user-configurable target types. Refer to section 5.4.2 for further details.
Area Definitions
In C2 mode, CxEye supports alarm zones, independently of the local nodes.
ATI and no-ATI areas are not relevant in C2 mode.
Snapshots
Snapshots produced by local nodes are automatically sent up to the C2 system as they are taken.
The C2 system uses the camera video area to show a large version of the snapshot image for a
selected target.
The snapshot history area shows a history of the snapshots for the currently selected target. When a
different target is selected, the large image and snapshot history will change accordingly.
Targets may be selected in C2 mode in exactly the same ways as for Local mode.

5.12 Shortcut Keys

A number of convenient keyboard shortcuts are available within CxEye to perform common tasks.
The CxEye application must have focus to receive shortcut keys. To support shortcut keys on the
numeric keypad, Num Lock must be on.
Keyboard Key Function
F11 Toggle full screen mode.
F12 Switch current user.
1 (Numeric keypad) Select camera before currently selected camera.
3 (Numeric keypad) Select camera after currently selected camera.
4 (Numeric keypad) Pan selected camera left.
6 (Numeric keypad) Pan selected camera right.
8 (Numeric keypad) Tilt selected camera up.
2 (Numeric keypad) Tilt selected camera down.
+ Zoom selected camera in.
- Zoom selected camera out.
/ Toggle between main and thumbnail in video window.
* Toggle selected camera autofocus on/off.
Home Slew selected camera to home position.
Enter (Numeric keypad) Take snapshot.
Page Up Select target above currently selected target in the tote (i.e. target with next highest severity).
Page Down Select target below currently selected target in the tote (i.e. target with next lowest severity).
F1 Toggle friendly target filter on/off.
F2 Toggle friendly target labels on/off.
F3 Toggle neutral target filter on/off.
F4 Toggle neutral target labels on/off.
F5 Toggle hostile target filter on/off.
F6 Toggle hostile target labels on/off.
F7 Classify selected target as friendly.
F8 Classify selected target as neutral.
F9 Classify selected target as hostile.
 (Cursor up) Select next highest PPI fixed range to zoom the PPI window out.
 (Cursor down) Select next lowest PPI fixed range to zoom the PPI window in.
End Start/stop video tracking (Drone Mode only).
Ctrl + S Saves the configuration, Areas and Alarms to the previously used files without confirmation.
Ctrl + Alt + S Saves all settings to another .rpi file (user can enter a new filename).
Table 4: Keyboard Shortcuts


5.13 Touchscreen Operation

CxEye has been written to be compatible with modern touchscreen displays. Each of the main
controls is designed to be easily accessible using a touchscreen device instead of a mouse pointer.
Throughout this manual control is described in terms of mouse control. The equivalent touchscreen
actions are described below:
 A brief touch is equivalent to a left mouse button click.
 A double-tap on the screen is equivalent to a left mouse button double-click.
 Touching and holding a point on the screen is equivalent to a right mouse button click.
 Touching and dragging is equivalent to left-click, hold and drag.
Where text entry is required, for example to edit a target label, an on-screen keyboard is available
under the Tools  Keyboard… option.

APPENDIX A: Area Definition Files

Area definition files use lines of the following form:
Command Arguments Description Example
# Comment. Lines # This is a comment

beginning with a # line
character are comments.
name ‘string’ Sets the name of the name ‘myname’
active region.
clear Clear the active region by clear
deleting all polygons and
segments.
default mode Clear the active region default THRO
and set the initial mode,
which must be either
THRO (pass through
video) or LUT.
offset offsetValue Define an azimuth offset offset 10.0
in degrees for the active
region. The provided
offsetValue is a real
number.
origin xy Sets the origin for the origin 0.0 0.0
radar active region. This
coordinate of the origin is
subtracted from the
coordinates of the
polygon to get the radar
relative coordinates. In
many applications this
sets the radar position.
See Note below.
originlatlong lat long Sets the radar position as originlatlong 51.533428
radarlatlong a lat long. 0.805690
scale Factor Sets the scale factor. The scale 1.0

provided factor is a real
number, which defaults
to 1.0.
weighting weight Sets the weighting to use weight 1.000
for threat calculations.
Only applies to alarm
areas.
alarmtype type Sets the type of area alarmtype 1
alarm (Enter = 0, Exit =
1). Only applies to alarm
areas.
alarmrefpoint ref point ID Sets the ID of a reference alarmrefpoint 1
point to use for alarms.
Only applies to alarm
areas.

Command Arguments Description Example
alarmbearingerror bearing error Sets the maximum alarmbearingerror

bearing error relative to 45.000
the reference point for an
alarm to trigger (positive
values indicate
approaching reference
point, negative values
receding from reference
point). Only applies to
alarm areas.
alarmmaxspeed max allowed Sets the maximum alarmmaxspeed 5.000
speed allowed speed for targets
within the area in metres
per second. Only applies
to alarm areas.
poly ‘name’ mode Start the definition of a poly ‘noextract’ LUT
polygon having a name 100 0
given by the ‘name’ 100 100
argument. The mode is
0 100
either THRO or LUT. The
following lines contain the 0 0
points of the polygon 0 100
until an endpoly. endpoly
polylatlong ‘name’ mode Start the definition of a polylatlong ‘area’ THRO
lat/long polygon having 51.530519, 0.914313
name given by the ‘name’ 51.499249, 0.979055
argument. The mode is
51.454030, 0.901989
either THRO or LUT. The
following lines contain the 51.501656, 0.847881
points of the polygon endpoly
until an endpoly.
endpoly End the definition of a endpoly
polygon.
radaractive index active Enable/disable this poly ‘area’ LUT
polygon for a specific radaractive 1 0
radar. Used within 100 0
poly/polylatlong and
100 100
endpoly lines.
endpoly
segment ‘name’ Define a range azimuth segment ‘noshow’ 0 500

segment of the specified 170 190 LUT
startRange
name. The segment has
endRange
the given start and end
startAzimuth range and azimuth values
endAzimuth and has the given mode
mode (THRO or LUT).

APPENDIX B: Track Logging to File

CxEye includes a facility to allow tracks in alarm zones to be reported to an external CSV file for
testing. Configuration of this facility is not supported through the wizard. Instead, the CxEye.rpi
configuration file must be edited using a suitable text editor, such as WordPad.
When enabled, each track in an alarm zone is logged by appending a new entry to a file in CSV
format. A new file is created when CxEye is started using the date/time and an optional prefix to
create a unique filename. Each entry in the file includes the following fields:
Field Description
Date Date in YYY-MM-DD format.
Time Local time in HH:MM:SS format.
SystemID System ID, which is defined by a parameter in the
configuration file (ThreatDatabase.AlarmLogSystemID).
Status Status, currently always set to ALARM.

Flag Single character flag, set to one of the following:
C = Track coasted in alarm zone.
D = Track deleted in alarm zone.
F = Track has entered alarm zone.
L = Track has exited alarm zone.
R = Real report for track in alarm zone.
Please note, at present all track updates including

interpolated updates are reported as real (R). The
interpolated flag (I) is not used.
Position1A These two fields define the position of the track. The
Position1B format of these fields is set by a parameter in the
configuration file
(ThreatDatabase.AlarmLogPosition1Format).
Position2A These two fields define the position of the track. The
Position2B format of these fields is set by a parameter in the
configuration file
(ThreatDatabase.AlarmLogPosition2Format).
Speed Track speed in metres per second.

Course Track course in degrees.
Track ID Unique track ID number (without threat name prefix),
e.g. 123.
Some example file entries are shown below:
2017-11-02,14:56:41,1,ALARM,F,32.56.32 N,112.44.27 W,9008.109,346.822,33.150,112.891,2

2017-11-02,14:56:41,1,ALARM,R,32.56.32 N,112.44.27 W,9003.375,346.864,33.150,112.891,2
2017-11-02,14:56:41,1,ALARM,R,32.56.32 N,112.44.26 W,8993.366,346.952,33.150,112.891,2
2017-11-02,14:56:42,1,ALARM,R,32.56.31 N,112.44.26 W,8982.862,347.044,33.150,112.891,2

The following parameters are used to configure logging of tracks:
Parameter Description
ThreatDatabase.AlarmLogEnabled Set to 1 to enable logging of tracks or 0
to disable.
The default setting is 0.
ThreatDatabase.AlarmLogFilenamePrefix The filename suffix is created from the
data and time when CxEye is started, as
follows: “YYYYMMDD-HHMMSS.csv”.
An optional file prefix may be set using
this parameter. If the file prefix is
omitted or does not define a path, e.g.
“cxeye-alarms-” then the file will be
created in the current working directory.
If the file prefix does define a path, e.g.
“..\..\Logs\” or “C:\Logs\cxeye-
alarms-” then the file will be saved in
the specified directory.
The prefix may define the location of the
file on a remote PC by setting a UNC
path name, e.g. “\\MyPC\Logs\ cxeye-
alarms-”.
The default setting is “Logs\cxeye-
alarms-”.
ThreatDatabase.AlarmLogSystemID This parameter specifies the value to
include in the SystemID field of each file
entry.

ThreatDatabase.AlarmLogPosition1Format Set the type and format for the track
position fields (Position1A and
Position1B) in each file entry. The
following options are supported:
0 Record latitude in Position1A and
longitude in Position1B. Each field
is formatted as degrees, minutes
and seconds in the form D:MM:SS
with an E/W or N/S suffix to
indicate polarity.
E.g. “32.56.15 N” for latitude and
“112.46.04 W” for longitude. Note
that in this format, the position is
rounded to whole seconds.
1 Record latitude in Position1A and
longitude in Position1B. Each field
is formatted as decimal degrees to
six decimal places.
E.g. “32.937500” for latitude and
“ -112.767778” for longitude.
2 Record X metres from own position
in Position1A and Y metres from
own position in Position1B. Each
field is formatted as a decimal
value to three decimal places.
E.g. “86.460”
3 Record range in metres from own
position in Position1A and bearing
in degrees from own position in
Position1B. Each field is formatted
as a decimal value to three decimal
places.
E.g. “80.230” for range and
“350.453” for bearing.
ThreatDatabase.AlarmLogPosition2Format Same as
ThreatDatabase.AlarmLogPosition1Fo
rmat but applies to Position2A and
Position2B.



APPENDIX C: Perle IOLAN Configuration

The Perle IOLAN server may be used to add I/O functionality to CxEye for interfacing with barriers.
This section outlines the configuration of an IOLAN for both input and output.
This is not an exhaustive guide; the IOLAN documentation must be consulted with regards to general
network configuration.
The Perle DeviceManager application should be used to configure an IOLAN. Once connected, a
password must be provided to access the IOLAN’s configuration. The default password is
“superuser”.
Important: As CxEye uses the IP address of an IOLAN to connect to it, each IOLAN must be
assigned a fixed IP address; either by assigning a static IP address using the DeviceManager or
using a DHCP server to assign a fixed address. Allowing a DHCP server to assign a temporary
address will cause problems as the address is likely to change once the address lease has expired.
Configuring IOLAN Inputs

IOLAN inputs must be configured to allow CxEye to connect using a TCP socket and receive
notifications when the state of an input changes.
Select Channels under I/O Interfaces.
Select each input to be configured and click Edit....

Select the I/O Extension tab.

Select Enable I/O extension.

Select Listen for connection. Each input is assigned a unique port, 20000 for D1, 20001 for D2, etc.
The default TCP port should be used.
Make sure that Enable TCP Keepalive is enabled. Without this, CxEye will not be able to quickly
detect if a connection to the IOLAN has been lost.
Once all changes have been made, download the configuration onto the IOLAN and reboot it.
Verifying Input Signals

To verify that an IOLAN is correctly reading the state of connected inputs, select I/O Status/Control
under Control.

Click Refresh and verify that the state of the inputs are displayed correctly.
This dialog will also show the I/O Extension as “Connected” if CxEye has established a connection to
an input.
Output Configuration
By default, all IOLAN signals are configured as inputs. A hardware jumper must be set inside the
IOLAN to change an input to an output.
IOLAN inputs must be configured to allow CxEye to connect using a TCP socket and send messages
to control the state of the output.
Select Channels under I/O Interfaces.
Select the output to be configured and click Edit....

Select the General tab.

Configure the output properties as required. For the barrier reset signal, the output should be set to
“Pulse Mode” with “Pulse Count” set to one.
Select the I/O Extension tab.
Select Enable I/O extension.

Select Listen for connection. Each output is assigned a unique port, 20000 for D1, 20001 for D2,
etc. The default TCP port should be used.
Make sure that Enable TCP Keepalive is enabled. Without this, CxEye will not be able to quickly
detect if a connection to the IOLAN has been lost.
Once all changes have been made, download the configuration onto the IOLAN and reboot it.

Controlling Output Signals

The DeviceManager can be used to set and clear outputs for testing purposes. To do this, select I/O
Status/Control under Control.
Click Activate Output to trigger an output pulse.

This dialog will also show the I/O Extension as “Connected” if CxEye has established a connection to
the output.



APPENDIX D: Tracker Class Rules File

The CxEye tracker supports assignment of a preliminary threat type based on the properties of the
track. The section applies to the CxEye’s internal tracker when configured in Local Mode. The same
can be achieved by an external tracker when CxEye is operating in Client Mode. For further details,
please refer to the tracker configuration documentation for SPx Server.
The class assigned to a track is defined by an integer value. This value must be a value in the range 1
to 6, corresponding to the six threat types supported in CxEye and configured using the Application
Wizard.
At each update of an established track, the configured list of class rules are examined to see which, if
any, class a track should be assigned to. A track can only be assigned to one class. The first class
whose rules accept the track is used. The class may change on the next update according to changes
in the track’s attributes.
The class rules are contained in a file that is read by CxEye at start-up. The file is located in the
following folder in the CxEye directory:
Config/MHT/TrackClass/trackclass.txt
Note: If using an external tracker, then please refer to documentation for SPx Server for details of the
file location.
The file contains the definitions of the track classes. The general form of the file is:
CLASS
<conditions>
Code = N
SetModel = modelRef
ENDCLASS
CLASS
<conditions>
Code = N
SetModel = modelRef
ENDCLASS
…
Each class definition provides a set of conditions that the track must meet if it can join the class. If all
the conditions are met, the track is assigned the appropriate code value in the class definition.
The following conditions can be used to decide if a track should be assigned to a specific class.

Condition Description
Speed The track’s speed can be required to be greater than a minimum value or less
than an upper value. If no value is specified then no check is made.
Weight The track’s average weight can be required to be greater than a minimum value
or less than an upper value. If no value is specified then no check is made.
Doppler speed The track’s Doppler speed can be required to be greater than a minimum value
or less than an upper value. If no value is specified then no check is made.
Note that this condition is only relevant if the radar is providing Doppler
information.
Age The track can be required to have a minimum age.
Area The track can be required to be inside an area, as defined by an Action Area
object, so any complex polygon or set of polygons.
Over land The track can be required to be over land or within a specified distance of land.
Over sea The track can be required to be over sea or within a specified distance of sea.
Range The track can be required to have a range between a minimum and maximum
value.
Azimuth The track can be required to have an azimuth between a minimum and
maximum value.
Course The track can be required to have a course between a minimum and maximum
value.
Course Standard Deviation The track can be required to have a course standard deviation between a
minimum and maximum value.
Approach Angle The track can be required to have an approach angle between a minimum and
maximum value.
Model The track can be required to be have been derived from a specific MBT model.
If the conditions for a class are all met, the track is assigned a code defined by the class. The code is
what will be reported in the track report to interested clients. The code is an integer that is defined by
the class definition. For example, the class definition:
CLASS
minSpeed = 10
Code = 1
ENDCLASS
will assign track class code 1 to all targets that have a speed greater than 10 m/s.
The numerical value of the code (1 in this case) has no particular significance other than as agreed
between the configuration of the track class in SPx Server and the client applications that use the
track class code.
It is possible for multiple class definitions to use the same value for code. For example, if it is desired
to use classes to identify a threat condition that depends on the OR of two situations, two separate
class definitions would be used to give the same code. For example, suppose we define a threat
condition as being:

Any target less than 1000m from the radar.
OR
Any target between 1000 and 5000 m from the radar that is moving greater than 20m/s
towards the radar (say the course is between 80 and 100 degrees, for the case where the
radar is due east of the target).
We want to output a class code of 1 (meaning threat in this example) if either of the two situations are
met, and 0 if neither condition is met. The following classes would be defined:
CLASS
maxRange = 1000
Code = 1
ENDCLASS
CLASS
minRange = 1000
maxRange = 5000
minSpeed = 20
minCourse = 80
maxCourse = 100
Code = 1
ENDCLASS
CLASS
Code = 0
ENDCLASS
The final CLASS sets the Code to 0 if none of the other rules trigger. This rule is not strictly necessary
as the code would default to that value.
The Track Class file is an UTF-8 text file that needs to be prepared outside of CxEye using a normal
text editor. The file is read in when CxEye starts.
The file contains lines that start with a “#” as comments or blocks of text that define a CLASS as:
CLASS
<Conditions>
ENDCLASS
The conditions are any of the following (in any order in the file):
minSpeed=<real>
maxSpeed=<real>
The minimum and maximum permitted speed of the target in metres/sec.
minWeight=<real>
maxWeight=<real>
The minimum and maximum permitted weight of the target. The weight is the number of
samples that contribute to the target and hence is a measure of the size of the target.

minRadSpeed=<real>
The minimum permitted Doppler speed of the target (+ve is toward radar). This parameter is
only applicable if the radar is providing Doppler.
maxRadSpeed=<real>
The maximum permitted Doppler speed of the target (+ve is toward radar). This parameter is
only applicable if the radar is providing Doppler.
minAge=<int>
This parameter defines the minimum age of the track in scans (after becoming established)
for the rule to apply.
area=<string>
The track must be inside the Active Area area named by this parameter. The area can be
created in the same way as a track parameter area.
overLand
The track must be over or near to land, as specified by the overLandMargin parameter.
overLandMargin=<real>
If the overLand parameter is specified, then the track must be at least this distance from
sea. The units are metres.
overSea
The track must be over or near to sea, as specified by the overSeaMargin parameter.
overSeaMargin=<real>
If the overSea parameter is specified, then the track must be at least this distance from land.
The units are metres.
minRange=<real>
maxRange=<real>
The minimum and maximum permitted range of the track. The units are metres.
minAzi=<real>
maxAzi=<real>
The minimum and maximum azimuth of the target. Both parameters must be defined in the
rule and the track passes the test if its azimuth is between the minimum and maximum value.
The maximum value can be less than the minimum, so that minAzi=350, maxAzi=10, for
example, means an azimuth +/- 10 degrees from North.
minCourse=<real>
maxCourse=<real>
The minimum and maximum course of the target. Both parameters must be defined in the rule
and the track passes the test if its course is between the minimum and maximum value. The
maximum value can be less than the minimum, so that minCourse =350, maxCourse =10,
for example, means a course +/- 10 degrees from North.

minCourseSD=<real>
maxCourseSD=<real>
The minimum and maximum standard deviation of the course of the target. The units are
degrees.
minApproachAngle=<real>
maxApproachAngle=<real>
The minimum and maximum approach angle of the target towards the radar. Both parameters
must be defined in the rule and the track passes the test if its approach angle is between the
minimum and maximum values. The maximum value can be less than the minimum, so that
minApproachAngle=350, maxApproachAngle=10, for example, means an approach
angle +/- 10 degrees from North.
code=<int>
This is the track code that is assigned to the track if all other conditions for the class pass.
The code of 0 is reserved to indicate that no code has been assigned.
name=<string>
This is a class name that is assigned to the track if all conditions for the class pass.
There are a number of special parameters that affect the behaviour of the classification:
lockAfter=<int>
If a track meets the requirements of a class for lockAfter consecutive scans, it will be
permanently locked into that class for the duration of the track’s life. This can be used to latch
a class once a sufficient number of scans have built confidence in a class. For example:
CLASS
maxSpeed = 5
lockAfter = 5
code = 1
ENDCLASS
Once the track is observed to have a speed of < 5 m.s for 5 consecutive scans, it will retain
the code=1 classification for the lifetime of the track.
holdFor=<int>
If the parameter holdFor is set, a track that meets the requirements for a class will remain in
that class for at least holdFor scans, even if it does not otherwise meet the membership
criteria. This parameter implements hysteresis on the track class membership.
noDefault=<int>
This parameter controls the behaviour of the processing when a track is currently classified,
but on the latest update there is no match with any class and there is no holdFor set. The
normal behaviour (noDefault=0) is to change the track’s code to 0. If nodefault = 1, the
track’s class remains unchanged.

For example, for:

CLASS
maxSpeed = 5
noDefault = 1
code = 1
ENDCLASS
For a target having speed < 5 m/s, the rule is triggered and code=1. If the target speed increases to 6
m/s, the rule will not be triggered. Since noDefault=1, the behaviour is to preserve the track code of
1. Without the noDefault line, (or noDefault = 0) the track’s code would return to 0 once the
speed was more than 5 m/s.
The Track Class file can contain any number of CLASS definitions. The class definitions are
considered in the order that they appear in the file. This means that a class definition that is more
specific than another (and otherwise the same) must occur first in the file.
For example, suppose a CLASS is created for slow targets:
CLASS
# Slow Targets
maxSpeed = 5
code = 1
ENDCLASS
A target will be classified with code 1 if its speed is less than 5 m/s.
It is now desired to create a second class to identify slow targets in a specific area. This is done with
the following class definition:
CLASS
# Slow Targets in critical area
maxSpeed = 5
area = “criticalArea”
code = 2
ENDCLASS
With these two rules, slow targets in the specific area will have code 2, whereas slow targets outside
that area will have code 1 (all other targets will have code = 0 assuming no other rules are defined).
Significantly, the second class definition must appear before the first definition because it is more
specific.
So in the file, the correct appearance is:

CLASS
# Slow Targets in critical area
maxSpeed = 5
area = “criticalArea”
code = 2
ENDCLASS
CLASS
# Slow Targets
maxSpeed = 5
code = 1
ENDCLASS
If the class definitions were the other way round, all small targets (irrespective of their position) would
appear as code 1 because that rule would be triggered first.
A rule can be defined with no conditions, other than a code or model assignment, for example:

CLASS
# Default class
code = 0
ENDCLASS
Since it has no conditions, this rule always triggers for a target. It can therefore only sensibly appear
at the end of the file and can be used to assign a code, or model, if no other rule has triggered.



APPENDIX E: Indigo Vision VMS Integration

CxEye may be configured to interface to an Indigo Vision VMS system to perform the following
functions:
 Triggering detectors when targets enter alarm zones
 Clearing of alarms when a target exits an alarm zone
 Export of video clips from recorded camera video
To support triggering of detectors and clearing zones, CxEye sends a network message to the VMS.
CxEye supports control of both a primary and backup VMS. The IP address of each VMS server is
defined using the Application Wizard.
To enable this feature, CxEye must be able to find the “ivbind2.dll” DLL at runtime. This DLL can
either be located in a standard Windows directory or in the same directory as the executable. If the
DLL is not found, the following message is displayed when CxEye is started. CxEye will continue to
operate, however control of VMS zones will be disabled.
To support exporting of video clips, CxEye communicates directly with the Indigo Vision Control
Center application running on the same PC as CxEye via a COM interface. To enable CxEye to use
the COM interface, it must first be registered. This can be performed by opening a DOS window in
Administrator mode and running the following command:
ControlCenter.exe /RegServer
At start-up, CxEye will check to see if Control Center is accessible (application registered and
running). If a problem is encountered, then the following message is displayed. CxEye will continue to
operate, however exporting of video clips will be disabled.
Configuration of the VMS software is beyond the scope of this document; however, the following
CxEye-specific configuration rules should be observed. For details of how to configure the VMS
software, please refer to Indigo Vision documentation.

 Each camera in CxEye may be assigned a VMS detector ID and a VMS zone name. This is
configured using the Camera Wizard. The detector ID is used to trigger alerts and the zone
name is used to clear alerts from all detectors assigned to the zone. The name of the zone
must match the name of a zone in the VMS software. The detector ID must match the Matrix
Number of a detector in the VMS software. The detector must be assigned to the same zone
in the VMS software.
 The VMS sensor IDs configured in the Camera Wizard must match the Matrix Numbers
assigned to cameras in the VMS software. The sensor IDs are used to export video from the
sensors.

APPENDIX F: SPx Camera Manager

The SPx Camera manager allows multiple CxEye nodes to control the same set of Pelco-D or FLIR
cameras by limiting control of each camera to one CxEye node at a time (although all CxEye nodes
can request the pan/tilt position, status, etc. of the camera at any time). The camera manager accepts
a TCP network connection from each CxEye node. The camera manager can connect to each
camera using a serial connection or a TCP connection directly to the camera’s MOXA serial-to-
network interface. To use a MOXA with a camera manager it must be configured for “TCP Server”
operation. If using dual-redundant camera managers, the MOXA must be configured to accept at least
two TCP connections.
Full details on the SPx Camera Manager can be found in reference [5].
Each camera in a CxEye node is assigned a priority in the range 1 to 255. The higher the priority
value, the higher the priority of the camera.
As all CxEye nodes connect to the camera manager using the same TCP address and port, the
Pelco-D address (which is a standard part of the Pelco-D interface and represented by an integer
value) is used to identify the camera to control. The Pelco-D address of each camera is set in the
camera manager configuration file. The same Pelco-D address must be assigned to each camera
controlled by CxEye using the Camera Wizard.
CxEye supports a dual-redundant camera manager configuration. Rather than specifying the IP
address of the PC running the camera manager in the Camera Wizard, a special tag “fusion_server”
may be used instead. This will configure CxEye to use the IP address associated with the active
Fusion Server. The address will be changed from the primary to the backup fusion server if CxEye
detects that the primary Fusion Server has failed.



APPENDIX G: Alarm Message Format

CxEye may be configured to generate an alarm message when a threat is inside an alarm zone.
While inside an alarm zone, a message is sent each time a track report for the threat is generated (or
received if operating in C2 or Client mode).
Alarm messages are sent as UDP packets to the address and port specified in the application wizard.
The default is 239.192.0.3:5003
The packet consists of a standard SPx header followed by a number of data fields. All multi-byte fields
in the packet header and data are in big-endian byte order.
Packet Header
No. Field Name Type Value Description
1 magic UINT16 0x4342 Magic value.
2 packetType UINT16 0x0250 Packet type.
3 totalSizeBytes UINT32 0x00000060 Total packet size.
4 timeSecs UINT32 <variable> Whole seconds since Unix
epoch (1st Jan 1970).
5 timeUsecs UINT32 <variable> Microseconds to be added
to timeSecs.
Packet Data
6 alarmAreaName[32] char <variable> Null terminated alarm
area name.
7 alarmStatus UINT8 <variable> Alarm status:
1 = Track entered alarm
area
2 = Track inside alarm
area
3 = Track exited alarm
area
4 = Track coasted inside
or outside alarm area
5 = Track deleted inside
or outside alarm area
6 = Track outside alarm
area
See note [1].
8 reserved1 UINT8 0x00 Reserved for future use.
10 trackID UINT32 <variable> Unique track ID.
11 rangeMetres REAL32 <variable> Range in metres from
CxEye own position.
12 azimuthDegs REAL32 <variable> Bearing in degrees from
CxEye own position.

Packet Data
13 speedMps REAL32 <variable> Target speed in metres
per second.
14 courseDegs REAL32 <variable> Target course in degrees.
15 latDegs REAL32 <variable> Latitude in degrees,
positive north.
16 longDegs REAL32 <variable> Longitude in degrees,
positive east.
17 weight UINT32 <variable> Weight of target (number
of samples).
18 sensors UINT32 <variable> A bit field indicating which
sensors are contributing
to the fused track.
Bit 0 = Radar-0
Bit 1 = Radar-1 etc.
A bit set indicates that a
sensor is contributing.
Note [1]: The sequence of alarm messages output by CxEye will depend on whether an alarm area is
configured with an Entry rule or an Exit rule.
For an alarm area with an Entry rule, a message with Alarm Status = 1 will be output either
when a track enters or is already inside the alarm area and meets the conditions configured
for the Entry rule. Subsequent updates of the track after triggering the alarm will output a
message with Alarm Status = 2 while inside the area, or Alarm Status = 4 if the track is
coasted. On exiting the area, a message with Alarm Status = 3 is output. If the track is
deleted then a message with Alarm Status = 5 is output. The alarm messages will stop
when the track exits the area or is deleted.
For an alarm area with an Exit rule, a message with Alarm Status = 3 will be output when a
track exits the alarm area and meets the conditions configured for Exit rule. Subsequent
updates of the track after triggering the alarm will output a message with Alarm Status = 6,
or Alarm Status = 4 if the track is coasted. If the track is deleted then a message with Alarm
Status = 5 is output. The alarm messages will stop when the track is deleted.

The following example shows a packet received on the network. The numbers in bold are the field
indices, referenced in the following table.
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 43 42 02 50 00 00 00 60 53 BB BB 20 00 0B 77 FE
1 2 3 4 5
10 50 6F 6C 79 2D 31 00 00 00 00 00 00 00 00 00 00
6
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30 00 00 00 00 00 00 00 01 46 24 CE 3E 43 B3 C4 6B
7 8 9 10 11 12
40 00 00 00 00 00 00 00 00 42 03 CA D2 C2 E1 8A 2C
13 14 15 16
50 00 00 00 64 00 00 00 01 00 00 00 00 00 00 00 00
17 18 19 20
No. Field Name Decode Value

1 magic 0x4342
2 packetType 0x0250
3 totalSizeBytes 96 bytes
4 timeSecs Time since epoch decodes to:
8th July 2014 09:34:24.751614 UTC.
5 timeUsecs
6 alarmAreaName[32] “Poly-1”
7 alarmStatus Status 1 = Entered alarm zone
8 reserved1 0
9 reserved2 0
10 trackID 1
11 rangeMetres 10547.560 metres
12 azimuthDegs 359.534 degrees
13 speedMps 0 m/s
14 courseDegs 0 degrees
15 latDegs 32.948065 degrees
16 longDegs -112.769870 degrees
17 weight 100
18 sensors 0x00000001
19 reserved5 0
20 reserved6 0

CxEye supports testing of alarm message output. Clicking the Test Network Alarm button in the
options dialog will generate a sequence of five test messages for the selected alarm zone at a rate of
approximately 1 message per second. The first message will have status set to 1 (entered alarm
zone) and the last message will have status set to 3 (exited alarm zone). All other messages will have
status set to 2 (inside alarm zone). In each message, the trackID will be set to 1. The position of the
track will be set to the position of the first polygon point in the alarm zone. Speed and course is set to
zero.

APPENDIX H: Heartbeat Message Format

CxEye can be configured to send a periodic (once per second) heartbeat message, which includes
fields showing the status of inputs to CxEye.
Packet Header
1 magic UINT16 0x4342 Magic value.
2 packetType UINT16 0x0290 Packet type.
3 totalSizeBytes UINT32 0x00000020 Total packet size.
4 timeSecs UINT32 <variable> Whole seconds since Unix epoch (1st
Jan 1970).
5 timeUsecs UINT32 <variable> Microseconds to be added to
timeSecs.
Packet Data
6 projectCode UINT16 0x00EF CxEye project code (239).
8 status UINT32 <variable> A bit field indicating status of inputs
and connections to CxEye.
Bit 0 = Primary fusion server
Bit 1 = Backup fusion server
Bit 2 = Fused track input
Bit 3 = Camera manager
Each bit has the following meaning:
0 = Status OK
1 = Error
9 radarStatus UINT32 <variable> A bit field indicating status of Cat-
240 radar video inputs to CxEye.
Bit 0 = Radar-0
Bit 1 = Radar-1 etc.
Each bit has the following meaning:
0 = Status OK
1 = Error
10 Reserved2 UINT32 0x00000000 Reserved for future use.
All multi-byte fields in the packet header and data are in big-endian byte order.
Where bit fields are used, bit 0 is the LSB.



APPENDIX I: RF Target Logging to File

CxEye includes a facility to allow RF targets to be reported to an external CSV file for testing.
Configuration of this facility is not supported through the wizard. Instead, the CxEye.rpi configuration
file must be edited using a suitable text editor, such as WordPad.
When enabled, RF targets are logged by appending a new entry to a file in CSV format. A new file is
created when CxEye is started using the date/time and an optional prefix to create a unique filename.
Each entry in the file includes the following fields:
Field Description
Date Date in YYY-MM-DD format.
Time Local time in HH:MM:SS format.
Target ID ID assigned to target.
Target Type DRONE, REMOTE or UNKNOWN.
Target State CREATED - RF target detected

PROVISIONAL - RF target has no bearing
CONFIRMED - RF target has bearing
LOST - RF target not updated for > 10 seconds
DELETED - RF target deleted (either manually or purged by timeout)
Target Class Descriptive class string, e.g. “DJI Drone 2.4”
Bearing 1 Bearing in degrees from detector.
Bearing 2 Bearing in degrees from reference position to centre position of target sector.
Source ID Numeric identifier of the station within the system that produced the report.
Comms Freq Communication frequency in MHz.
Comms Amplitude Communication amplitude in dBm.
Fused Track ID ID of fused radar track or blank if not fused.
Fused Track Latitude Fused track latitude in degrees, positive north.
Fused Track Fused track longitude in degrees, positive east.

Longitude
Some example file entries are shown below:
2018-01-26,15:05:30,8,UNKNOWN,CREATED,,,,0,0.000,0.000,,,
2018-01-26,15:05:30,8,REMOTE,PROVISIONAL,,,,0,0.000,0.000,,,
2018-01-26,15:05:33,7,DRONE,CONFIRMED,DJI Drone 2.4,317.600,324.390,3,2441.479,-61.300,3,32.873383,-
112.727234
2018-01-26,15:06:01,7,DRONE,CONFIRMED,DJI Drone 2.4,267.600,274.834,3,2442.583,-67.200,,,

The following parameters are used to configure logging of RF targets:
ThreatDatabase.RFTargetLogEnabled Set to 1 to enable logging of RF targets or 0 to
disable.
ThreatDatabase. The filename suffix is created from the date
RFTargetLogFilenamePrefix and time when CxEye is started, as follows:
“YYYYMMDD-HHMMSS.csv”.
An optional file prefix may be set using this
parameter. If the file prefix is omitted or does
not define a path, e.g. “cxeye-rftargets-”
then the file will be created in the current
working directory.
If the file prefix does define a path, e.g.
“..\..\Logs\” or “C:\Logs\cxeye-rftargets
-” then the file will be saved in the specified
directory.
The prefix may define the location of the file
on a remote PC by setting a UNC path name,
e.g. “\\MyPC\Logs\ cxeye-rftargets-”.
The default setting is “Logs\cxeye-alarms-”.
Please refer to section 5.3.17 on page 69 for information about the RF detector user interface
controls.

APPENDIX J: Argos RF Detectors

CxEye supports control and receipt of targets from one or more MyDefence RF detectors by
connecting to an Argos server.
CxEye connects to an Argos server (running on either the same PC or on a different PC to CxEye)
using a websocket connection. The Argos server supports multiple connected devices. A device may
have between 1 and 6 individual detectors, each covering a 60 degree sector.
The RF Detector page of the Application Wizard is used to configure the connection to the Argos
server and also to manage individual devices that will be reported to CxEye.
The network address should be set to the host address of the PC running the Argos service. The
default port used by the Argos service to receive a websocket connection is 5060.
The lat/long position and bearing in the Wizard defines the default position and bearing that will be
used for any devices reported by the Argos server.
If interfacing to multiple devices, set the number of devices to the number of devices expected.
The following pages of the Wizard (after the RF Detector page) allow each individual device to be
configured (example in following picture):

A device is identified by its unique alphanumeric ID, for example "988erbn4jktg6ftz". For each device,
this ID must be entered in the top field on the wizard page.

Notes (page 1 of 2)

Notes (page 2 of 2)

Contact details
Kelvin Hughes Limited

Voltage
6 Mollison Avenue
Enfield
EN3 7XQ
United Kingdom
Phone +44 (0) 1992 805 200
Fax +44 (0) 1992 805 310
Security email security.systems@kelvinhughes.co.uk

Systems
Phone +44 (0)1992 805 272
General
Security email security.tech@kelvinhughes.co.uk

Technical
Advice Phone +44 (0) 1992 805 264
Internet Website www.kelvinhughes.com

Kelvin Hughes – Security Systems Ref. KHS-1003 | Issue 11

CxEye UserManual V1 81 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CxEye UserManual V1 81 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Kelvin Hughes – Security Systems Ref.

CxEye™ Display, Control and Integration

Operator Manual | Issue 11 | January 2019

Ref: CxEye™ Operation Manual

Ref: CxEye™ Operation Manual

REFERENCED & RELATED DOCUMENTS

Ref: CxEye™ Operation Manual

Page intentionally blank

Ref: CxEye™ Operation Manual

Ref: CxEye™ Operation Manual

APPENDIX A: Area Definition Files ......................................................................................... 91

Ref: CxEye™ Operation Manual

Display of ASTERIX CAT-240 video from multiple radars    

Display of ASTERIX CAT-48/62 tracks from multiple radars    

Remote control of SxV radars via ASTERIX CAT-253    

Internal plot extraction and tracking    

Receipt of SPx format network track reports    

Display of track markers    

Receipt of AIS track data    [1]  [1]

Fusion of AIS tracks with radar tracks    

Provisional auto-classification of tracks    

Threat classification data shared between nodes  [2]  [2]  

Operator classification of targets    

Output of network alarm messages    

ATI and no-ATI zones    

Ref: CxEye™ Operation Manual

Local Drone C2 Client

Manual track initiation and deletion    

Display of camera video    

Control of PTZ cameras including slew-to-cue    

Terrain mapping for camera control    

Automatic camera control    

External joystick for camera control    

Generation of snapshots from camera video    

Display of snapshots    [3] 

Output of TTM reports for all tracks or selected track    

Interfacing to an Indigo Vision VMS system    

Video tracking of drones   [4]  

RF detector target input and fusion with radar tracks    

Table 1 – CxEye Operating Modes

Ref: CxEye™ Operation Manual

2.1 Summary Specification

Radar control interface: SxV radar network interface: ASTERIX CAT-253.

Radar tracking: Multi-hypothesis tracker, manual and auto initiation,

Number of tracks: Not limited by software.

AIS: Receipt of NMEA-0183 AIS tracks as network UDP packets.

Track fusion: Up to 4 track streams plus single AIS stream.

Supported video inputs: Any DirectShow compatible devices, RTSP sources.

Terrain mapping: Support for use of terrain mapping to automatically slew

Threat evaluation: Manual target classification, automatic provisional classification,

Alarms: Programmable alarm zones, up to 8 programmable barriers,

Recording: Screen capture at programmable rate.

Licensing: USB dongle or MAC address file.

Ref: CxEye™ Operation Manual

2.2 Camera Support

Ref: CxEye™ Operation Manual

2.3 Related Documents

[1] CP-25-110-13 Dongle Installation

[2] CP-25-110-12 Licence File Installation Notes

[3] CP-25-110-83 ASTERIX Cat-240 Network Data Format

[4] CP-25-110-32 SPx Data Reference Manual

[5] CP-25-110-123 SPx Camera Manager

[6] CP-25-172-01 P172 SBS Radar Controller Manual