Universal Installation Service Tool II Manual Ver H

Download as pdf or txt
Download as pdf or txt
You are on page 1of 107

Southwest Microwave, Inc.

Security Systems Division

INTREPID™
Universal Installation Service Tool II
Technical Manual

Version H
UIST II Manual

Trademark Notice and Certifications


INTREPID™, MicroPoint™ and MicroTrack™ are registered trademarks of Southwest Microwave, Inc.
Copyright 1995 and 2014 Southwest Microwave, Inc. All rights Reserved.

Windows™, XP™, Windows 7™ and Windows 8™ are registered trademarks of Microsoft Corp.

Copyright Southwest Microwave, Inc. May, 2015

Southwest Microwave, Inc.


9055 South McKemy Street
Tempe, Arizona 85284-2946

Tel: (480) 783-0201


Fax: (480) 783-0401
Email: [email protected]
Web: www.southwestmicrowave.com

2 Version H
UIST II Manual

Table of Contents

1. Introduction ................................................................................................................................................ 6

2. Software Installation.................................................................................................................................. 6

3. Universal Installation Service Tool II .................................................................................................... 11

3.1 Connection Screen .............................................................................................................................. 12


3.1.1 Configure Ports .............................................................................................................................. 12
3.1.2 Add ports ....................................................................................................................................... 13
3.1.3 Discover Devices ........................................................................................................................... 14
3.1.3.1 Sensor Direct RS232 Connection............................................................................................ 14
3.1.3.2 CM II or GCM II-HD Direct RS232 Connection to Service/UIST II Port ............................. 15
3.1.3.3 CM II-N or RPM II USB or Network Connection .................................................................. 16
3.1.4 Show All Devices .......................................................................................................................... 18
3.1.5 Connecting to a Sensor .................................................................................................................. 19
3.1.6 Diagnostics .................................................................................................................................... 19
3.1.7 Supported Devices ......................................................................................................................... 21
3.1.8 About ............................................................................................................................................. 21

MicroPoint II ................................................................................................................................................... 22

4. MicroPoint II Installation Service Tool ................................................................................................. 23

4.1 Sensor ................................................................................................................................................. 23


4.1.1 Sensor Information ........................................................................................................................ 24
4.1.2 Sensor Settings .............................................................................................................................. 24
4.1.2.1 Sensor ID Tag ......................................................................................................................... 25
4.1.2.2 Sensor Date/Time .................................................................................................................... 25
4.1.2.3 Response Timer Value ............................................................................................................ 25
4.1.2.4 Cable A Status – Cable B Status ............................................................................................. 26
4.1.2.5 Reboot Sensor ......................................................................................................................... 27
4.1.2.6 Restore Factory Defaults ......................................................................................................... 27
4.2 Cable A and Cable B .......................................................................................................................... 27
4.2.1 Configuration Parameters .............................................................................................................. 27
4.2.1.1 Analog Channel Gain Setting.................................................................................................. 28
4.2.1.2 Intergrator Sample Length ...................................................................................................... 28
4.2.1.3 Threshold Factor ..................................................................................................................... 28
4.2.1.4 Alarm Mask Time ................................................................................................................... 30
4.2.1.5 Alarm Mask Window .............................................................................................................. 30
4.2.1.6 Alarm Hold Time .................................................................................................................... 30
4.2.2 Clutter ............................................................................................................................................ 31
4.2.3 Target ............................................................................................................................................. 32
4.2.4 Target Location.............................................................................................................................. 33
4.2.5 Incremental Threshold ................................................................................................................... 36
4.2.6 Incremental Enable/Disbale ........................................................................................................... 38
4.2.7 Detection Level.............................................................................................................................. 41
4.2.8 Detection Window ......................................................................................................................... 43
4.3 External Inputs .................................................................................................................................... 46
4.4 Alarm History ..................................................................................................................................... 47
3 Version H
UIST II Manual

4.4.1 Erase Alarm History ...................................................................................................................... 48


4.4.2 Retrieve from Device..................................................................................................................... 48
4.4.2.1 Alarm Counts .......................................................................................................................... 50
4.4.2.2 Alarm Scatter .......................................................................................................................... 50
4.4.2.3 Event Counts ........................................................................................................................... 51
4.4.2.4 Event Scatter ........................................................................................................................... 52
4.5 Software Setup and Testing ................................................................................................................ 53
4.5.1 Software Setup............................................................................................................................... 53
4.5.2 Testing ........................................................................................................................................... 53
4.6 Reports ................................................................................................................................................ 54
4.7 General................................................................................................................................................ 55

MicroTrack II .................................................................................................................................................. 56

5. MicroTrack II Installation Service Tool ................................................................................................ 57

5.1 Sensor Parameters............................................................................................................................... 57


5.1.1 Sensor ID Tag ................................................................................................................................ 58
5.1.2 Sensor Date/Time .......................................................................................................................... 58
5.1.3 Response Timer Valye................................................................................................................... 58
5.1.4 Cable Pair A Status – Cable Pair B Status ..................................................................................... 59
5.1.5 Reboot Sensor ................................................................................................................................ 60
5.1.6 Clear Site Information ................................................................................................................... 60
5.1.7 Restore Factory Defaults ............................................................................................................... 60
5.1.8 Sensor Address .............................................................................................................................. 60
5.1.9 Sweep Channel Pair ....................................................................................................................... 60
5.1.10 Sensor Information ........................................................................................................................ 61
5.2 Cable Pair A and Cable Pair B ........................................................................................................... 61
5.2.1 Parameters ..................................................................................................................................... 62
5.2.1.1 Clutter Threshold Factor ......................................................................................................... 62
5.2.1.2 Target Input Attenuation ......................................................................................................... 63
5.2.1.3 Security Level ......................................................................................................................... 64
5.2.1.4 Alarm Threshold Factor .......................................................................................................... 64
5.2.1.5 Alarm Mask Time ................................................................................................................... 65
5.2.1.6 Alarm Mask Window .............................................................................................................. 66
5.2.1.7 Alarm Hold Time .................................................................................................................... 66
5.2.2 Clutter Input................................................................................................................................... 67
5.2.3 Clutter Location ............................................................................................................................. 68
5.2.4 Target Input ................................................................................................................................... 68
5.2.5 Target Location.............................................................................................................................. 69
5.2.6 Incremental Threshold ................................................................................................................... 71
5.2.7 Incremental Enable/Disbale ........................................................................................................... 73
5.2.8 Target Location Alarm .................................................................................................................. 75
5.3 Alarm History ..................................................................................................................................... 76
5.3.1 Erase Alarm History ...................................................................................................................... 76
5.3.2 Retrieve from Device..................................................................................................................... 76
5.3.3 Alarm Counts................................................................................................................................. 79
5.3.4 Alarm Scatter ................................................................................................................................. 79
5.4 Software Setup and Testing ................................................................................................................ 80
5.4.1 Software Setup............................................................................................................................... 80
5.4.2 Testing ........................................................................................................................................... 81
5.5 Reports ................................................................................................................................................ 81
5.6 General................................................................................................................................................ 82
4 Version H
UIST II Manual

MicroWave 330................................................................................................................................................ 83

6. MicroWave 330 Installation Service Tool .............................................................................................. 84

6.1 Sensor Information ............................................................................................................................. 84


6.1.1 Sensor ID Tag ................................................................................................................................ 85
6.1.2 Sensor Date/Time .......................................................................................................................... 86
6.1.3 Response Timer Value................................................................................................................... 87
6.1.4 Restore Factory Defaults ............................................................................................................... 87
6.1.5 Reboot Sensor ................................................................................................................................ 88
6.2 Sensor Settings ................................................................................................................................... 88
6.2.1 Mode .............................................................................................................................................. 88
6.2.2 Channel .......................................................................................................................................... 90
6.2.3 Tethered ......................................................................................................................................... 90
6.2.4 Recognition Algorithm .................................................................................................................. 91
6.2.5 FSA ................................................................................................................................................ 92
6.2.6 Alarm Hold Time........................................................................................................................... 93
6.2.7 Tamper Trigger .............................................................................................................................. 93
6.3 Alignment ........................................................................................................................................... 94
6.3.1 Start Alignment.............................................................................................................................. 95
6.3.2 Align/Path Alarm........................................................................................................................... 96
6.4 Target .................................................................................................................................................. 98
6.4.1 Gain ............................................................................................................................................... 98
6.4.2 Threshold to Noise Ratio ............................................................................................................... 99
6.4.3 Remote Test ................................................................................................................................... 99
6.5 Alarm History ................................................................................................................................... 100
6.5.1 Erase Alarm History .................................................................................................................... 101
6.5.2 Retrieve from Device................................................................................................................... 101
6.6 Software Setup and Testing .............................................................................................................. 102
6.6.1 Software Setup............................................................................................................................. 103
6.6.2 Testing ......................................................................................................................................... 103
6.7 Reports .............................................................................................................................................. 105
6.8 General.............................................................................................................................................. 106

5 Version H
UIST II Manual

1.0 Introduction
The Universal Installation Service Tool II (UIST II) is software used with INTREPID™ Series II family of
products. Its function is to configure the detection parameters of the MicroPoint™ II, MicroNet™ II,
MicroTrack™ II and MicroWave 330 sensors. It is also used to service and troubleshoot the sensors. It is
provided on a CD.

The UIST II is an application program designed to run on a standard PC or laptop computer with: Windows
XP™ Pro, Windows 7™ Pro or Windows 8™ Pro operating system and a CD, USB and Network port. The
minimum PC spec is: Pentium 4 @ 2.40GHz, 1.0GB memory and 80GB hard driver. If using Windows XP or 7
be sure the PC has *.Net Framework 4.0 (x86 and x64) installed. This applies to the UIST II Version D, E, F,
G and H programs.

Currently the UIST II has seven (7) languages available in its program. The languages are: English, German,
French, Spanish, Portuguese, Russian and Chinese.

This manual is divided into three (3) sections. These sections cover the MicroPoint II and MicroNet II Fence
Detection System, MicroTrack II Buried Cable System and MicroWave 330 Digital Microwave Intrusion
Detection System.

2.0 Software Installation


Prior to the software installation all programs must be exited or closed or the software may not load correctly. If
using a Windows XP™ or Windows 7™ PC be sure that it has the *.NET Framework 4.0 (x86 and x64)
installed.

2.1 Insert CD into the proper drive and choose run from the start menu.

2.2 Type d:\setup.exe and click OK (or appropriate drive).

2.3 The “Run” dialog box as shown in Figure 2.1 will open.

Figure 2.1 – Run Program Screen

2.4 The “License Agreement” dialog box will open as shown in Figure 2.2. This dialog box will only show if
the .NET Framework is not currently installed on the PC. Select “Accept” to continue loading the
software. The setup will initialize and configure components. This function may take several minutes to
complete.

6 Version H
UIST II Manual

Figure 2.2 – License Agreement

2.5 After all components have been configured the UIST II splash screen as shown in Figure 2.3 will open.
Select “Next” to continue the installation process or select “Cancel” to end the installation.

Figure 2.3 – Splash Screen

2.6 Selecting “Next” from the splash screen will open the “UIST II Setup Wizard” as shown in Figure 2.4.
Select “Next” to continue the setup or “Back” to step back to the previous screen or “Cancel” to stop the
installation.

7 Version H
UIST II Manual

Figure 2.4 – UIST II Setup Wizard

2.7 Selecting “Next” from the Setup Wizard will open the “Select Installation Folder” screen as shown in
Figure 2.5. It is recommended to install the software to the default “Program Files” folder on the PC.

Figure 2.5 – Installation Folder Options

If a different destination is required, type in the location or select the “Browse” button to locate the
destination. Selecting “Disk Cost” will show the file size to be installed and available hard drive space.
“Everyone” and “Just me” are permissions to use the program on the PC with the loaded software.
8 Version H
UIST II Manual

2.8 Selecting “Next” from the Select Installation Folder will open the “Confirm Installation” screen as shown
in Figure 2.6. This will confirm that the UIST II is ready to be installed on the PC.

Figure 2.6 – Confirm Installation

2.9 Selecting “Next” from the Confirm Installation screen will open the “Installing Universal Installation
Service Tool II” screen as shown in Figure 2.7. The blue progress bar will increase showing the progress
of the software installation. Once completed, select “Next” to continue the setup or “Back” to step back to
the previous screen or “Cancel” to stop the installation.

Figure 2.7 – Installing Universal Installation Service Tool II

9 Version H
UIST II Manual

2.10 Once the “Next” button is selected from the Installing Universal Installation Service Tool II screen, the
“Installation Complete” screen as shown in Figure 2.8 will open. This will be the indication that the
software has been successfully installed. Select “Close” to exit the installation.

Figure 2.8 – Installation Complete

10 Version H
UIST II Manual

3.0 Universal Installation Service Tool II


To start the Universal Installation Service Tool II (UIST II) program, double click the shortcut icon that has
been created on the desktop or use the Start/All Programs menu to open the main screen as shown in Figure 3.1.

Figure 3.1 – UIST II Main Screen

A “Choose Language” dialog box will open for default language selection as shown in Figure 3.1. This dialog
box will only show the first time the software is opened. Available languages are: English, French, German,
Spanish, Portuguese, Russian, Turkish and Chinese and can also be selected from the pull down language menu
at any time. Select the language that will be used to operate the software and select “OK” to open the “Connect”
screen as shown in Figure 3.2. Note: Clicking the screen will skip the delay time for opening Figure 3.2. Ensure
the correct keyboard is selected from the operating system for the language to be used.

Figure 3.2 – Connect Screen


11 Version H
UIST II Manual

3.1 Connection Screen


The “Connect” screen as shown in Figure 3.2 will be used by the computer to communicate to the MicroPoint™
II, MicroNet™ II, MicroTrack™ II or MicroWave 330 Digital Microwave Link and find devices by an “Auto
Detect” function. There is also a “Diagnostics Tab” and a “Supported Devices” tab. The language can be
changed by using the pull down tab next to “File”. The “File” menu allows for opening an Alarm History file.
The “About” menu provides information about the UIST II program. The “Discover Devices” button is used to
discover all connected devices and the “Show All Devices” box will show all devices and sensors.

3.1.1 Configure Ports

Selecting the “Configure Ports” button will open the “Configure Device Ports” screen as shown in Figure 3.3.
This is where the computer ports will be configured to allow communications to the sensors.

Figure 3.3 – Configure Device Ports

A dB9 serial cable with a male and female connector will be required to establish communications from a laptop
or desktop PC to the PM II, MTP II or MicroWave 330 Digital Microwave Receiver or CM II Service/UIST II
port using RS232. A USB to RS232 converter may be required if the PC does not have a physical dB9 port.

If connecting to the sensors through the Control Module II-Networked (CM II-N) or Remote Polling Module II
(RPM II) controller a network cable or USB A-B cable will be required.

If connecting to the sensors through the Graphic Control Module II-HD a network cable or dB9 null modem
cable will be required.

When opened, any physical port that the laptop or desktop PC has will be shown because of the “Auto Detect”
function. It will list the Location and if the port is “Enabled”. To enable or disable a port select the box in the
“Enabled” field. A check indicates the port is “Enabled”. Note: The “Secure” function is not active at this
time.

12 Version H
UIST II Manual

3.1.2 Add Ports

To add a network port(s) that will be used for communicating to the sensors, select the “Add Ports” button to
open the “Add Device Location” screen as shown in Figure 3.4.

Figure 3.4 – Add Device Location

In the “Network Address” field enter the IP address of the Remote Polling Module II (RPM II), the Control
Module II Networked (CM II-N) or the Graphic Control Module II-Heavy Duty (GCM II-HD) that the UIST II
will be connected to. The RPM II, CM II-N or GCM II-HD is the “Poll Master” and is connected to all the
devices and sensors installed at a particular site. Each module has a default IP address that can be changed using
the Controller Setup Tool II (CST II). The GCM II-HD IP address can be changed in its program. Typically the
IP address would be assigned by the sites IT administrator.

In the “Port” field enter the port number that the UIST II has been assigned. The default port number for the
UIST II is 50000. The port number can be changed in the RPM II or CM II-N using the CST II. Typically the
Port address would be assigned by the sites IT administrator. Figure 3.5 shows the “Location” and “Port” fields
entered.

Figure 3.5 – Added Device Location

The “Secure” function is not active at this time.

Once the correct information has been entered select the “Add Location” button to add the port to the
“Configure Device Port” screen as shown in Figure 3.6.

An IP port can be deleted by selecting the “Remove Port” button on the “Configure Device Port” screen as
shown in Figure 3.6.

13 Version H
UIST II Manual

Figure 3.6 – Added Device Location

3.1.3 Discover Devices

3.1.3.1 Sensor Direct RS232 Connection

Once the port to be used has been assigned and enabled select the “Discover Devices” button as shown in Figure
3.2 to start the discovery process. With a direct RS232 connection from the laptop or desktop PC to a sensor a
“Discovering Devices” dialog box will be displayed as shown in Figure 3.7 showing that the device has been
discovered.

Figure 3.7 – Discovering Devices

After the discovery is complete the screen will be populated with the sensor discovered as shown in Figure 3.8.

The list will show the “Location” (communications port), the “Status” of the device (normal/comm. fail),
“Device” type (MicroPoint II/MicroNet II, MicroTrack II or MicroWave 330), “Software Version” (application
software), “Address” (node address of device found) and “ID Tag” (name given for the device).

14 Version H
UIST II Manual

Figure 3.8 – Discovered Sensor

3.1.3.2 CM II or GCM II-HD Direct RS232 Connection to Service/UIST II Port

Once the port to be used has been assigned and enabled select the “Discover Devices” button as shown in Figure
3.2 to start the discovery process. With a direct RS232 connection from the laptop or desktop PC to a CM II or
GCM II-HD a “Discovering Devices” dialog box will be displayed as shown in Figure 3.9 showing that the
devices and sensors are being discovered.

Figure 3.9 – Discovering Devices

After the discovery is complete the screen will be populated with all sensors discovered as shown in Figure 3.10.

The list will show the “Location” (communications port), the “Status” of the device (normal/comm. fail),
“Device” type (MicroPoint II/MicroNet II, MicroTrack II or MicroWave 330), “Software Version” (application
software), “Address” (node address of device found) and “ID Tag” (name given for the device).

15 Version H
UIST II Manual

Figure 3.10 – Discovered Sensors

3.1.3.3 CM II-N or RPM II USB or Network Connection

Once the port to be used has been assigned and enabled select the “Discover Devices” button as shown in Figure
3.2 to start the discovery process. With a direct USB or Network connection from the laptop or desktop PC to a
CM II-N or RPM II a “User Authentication” dialog box will be displayed as shown in Figure 3.11.

Figure 3.11 – User Authentication

To establish a connected the “Password” configured in the controller must be entered. The “User ID” is not
required. The default password of the controller is sixteen (16) zeros. Once the password is entered select the
“Authenticate” button. A “Discovering Devices” dialog box will be displayed as shown in Figure 3.12 (USB)
and Figure 3.13 (Network) showing that the devices and sensors are being discovered.

Note: the GCM II-HD will operate in the same manner but the “User Authentication” will not be displayed as it
is not required. It will open directly to the “Discovering Devices” screen as shown in Figure 3.13.

16 Version H
UIST II Manual

Figure 3.12 – Discovering Devices – USB Connection

Figure 3.13 – Discovering Devices – Network Connection

After the discovery is complete the screen will be populated with all sensors discovered as shown in Figure 3.14
(USB) and 3.15 (Network).

The list will show the “Location” (communications port), the “Status” of the device (normal/comm. fail),
“Device” type (MicroPoint™ II/MicroNet II, MicroTrack™ II, or MicroWave 330), “Software Version”
(application software), “Address” (node address of device found) and “ID Tag” (name given for the device).

Figure 3.14 – Discovered Sensors – USB Connection


17 Version H
UIST II Manual

Figure 3.15 – Discovered Sensors – Network Connection

3.1.4 Show All Devices

With any discovery list, selecting the “Show All Devices” box will highlight all devices discovered as shown in
Figure 3.16. Sensors (MicroPoint™ II/MicroNet II, MicroTrack™ II and MicroWave 330) will not be
highlighted.

If any device is in a communications failure it will be highlighted red and also show “Comfail” in the “Status”
column as shown in Figure 3.16. In this example the MicroTrack II address “0” is in comfail.

Figure 3.16 – Show All Devices

18 Version H
UIST II Manual

3.1.5 Connecting to a Sensor

Once the connection has been established double click the sensor from the discovered devices list to be
communicated with to open the “INTREPID™ Devices Found” screen as shown in Figure 3.17.

The connected device selected will be shown. In this example, the connection is to the MicroPoint™ II /
MicroNet™ II Processor Module (PM II) so the PM II has been selected and found.

Clicking the screen will skip the delay time for opening the Installation Service Tool II (IST II) for the
connected sensor.

When using a network or USB connection through the CM II-N or RPM II the “User Authentication” dialog box
will open before any diagnostics or parameter changes can be made to the sensor. Enter the password and select
the “Authenticate” Button to gain access to the Installation Service Tool II for that sensor. Note: If connecting
with the UIST II to the USB port after using the CST II, be sure the CST II was exited from the Main Menu
or the UIST II will fail to connect…!

Figure 3.17 – INTREPID Devices Found

3.1.6 Diagnostics

The “Diagnostics” tab allows for testing from the laptop or desktop PC communications port to the sensor as
shown in Figure 3.18. For the sensor, select the correct port from the “Com Channel” pull down menu.

Selecting the “Test” button in the “Com Channel Selection” will start the test when connected to a sensor. This
test is to insure that the device is sending and receiving data packets. If the port is working correctly two (2)
lights will alternate under the Transmit and Receive as shown in Figure 3.18. A failure will only display one (1)
light. The “Stop” button will end the test.

19 Version H
UIST II Manual

Note: if this test is being performed with a USB connection to a CM II-N or RPM II the “User Authentication”
dialog box will open before the test can begin. Enter the password and select the “Authenticate” button to start
the test.

Figure 3.18 – Com Channel Diagnostics Test

Selecting the “Test” button in the “IP Address Selection” will start the test when connected to a GCM II-HD or
a network connection to the RPM II or CM II-N. The correct IP address of the GCM II-HD, RPM II or CM II-N
must be entered into the IP Address field. This test is to check that the local laptop or PC running the UIST II
can ping the GCM II-HD, RPM II or CM II-N. If the port is working correctly the word “Success” will be
displayed as shown in Figure 3.19 if not “Failure” will be displayed. A wrong IP address will display “Timed
Out” or “Destination Unreachable”.

Figure 3.19 – IP Address Diagnostics Test

20 Version H
UIST II Manual

3.1.7 Supported Devices

The “Supported Devices” tab will display all devices supported by this version of the UIST II as shown in
Figure 3.20. It will list the device type (MicroPoint II/MicroNet II, MicroTrack II or MicroWave 330), the
version of software being used by the device and the path to where the UIST II is installed.

Figure 3.20 – Supported Devices Tab

3.1.8 About

The “About” button will display the product name, part number, revision and build date as shown in Figure
3.21. It will also list the copyright information.

Figure 3.21 – About Screen


21 Version H
UIST II Manual

MICROPOINT II

22 Version H
UIST II Manual

4.0 MicroPoint™ II / MicroNet™ II Installation Service Tool


To open the MicroPoint II/MicroNet II Installation Service Tool click on the INTREPID™ MicroPoint II /
MicroNet II icon on the splash screen as shown in Figure 4.1. If nothing is clicked the Installation Service Tool
will open automatically.

Figure 4.1 – MicroPoint II Icon

4.1 Sensor
Once the INTREPID™ MicroPoint II/MicroNet II icon has been selected, the Installation Service Tool “Sensor”
tab for the MicroPoint II/MicroNet II will open as shown in Figure 4.2. There are two (2) tabs: Sensor
Information and Sensor Settings.

Figure 4.2 – Sensor Information Screen


23 Version H
UIST II Manual

4.1.1 Sensor Information

Selecting the “Sensor Information” tab will open the screen as shown in Figure 4.2. This screen will display
basic MicroPoint™ II/MicroTrack II™ Processor Module II (PM II) information. The information displayed is:

 Sensor Address (the dip switch address setting on the sensor)


 Sensor ID Tag (a descriptive name entered for the sensor)
 Response Timer Value (message turn around delay time – used for SDK development and line delays)
 Alarm Poll Function Type (type of device being polled)
 Electronic Serial Number (the MAC address – for Southwest Microwave use only)
 Hardware Version (hardware version of the PM II)
 Software Version (the version of software operating in the PM II)
 Software Build Date (the date the software was compiled)
 Software Build Time (the time the software was compiled)
 Current Sensor Date (the current date residing in the PM II – used in the alarm log)
 Current Sensor Time (the current time residing in the PM II – used in the alarm log)

Other tabs shown on this screen that will be used to configure the PM II are: Sensor Settings, Cable A, Cable B,
and External Inputs. Also on the screen are status LED’s to indicate Tamper alarm, Cable A alarm, Cable B
alarm, Fault cable A, Fault cable B and External Inputs 1 through 4 alarms. If the LED is “Green” it is in a
secured state. If the LED is “Red” it is an alarm state and if the LED is “Gray” it is in an inactive (disabled)
state. These will be shown no matter what tab has been opened. The scrolling blue bar at the bottom left of the
screen indicates correct polling from the laptop or PC to the PM II. Orange in the bar indicates bad packets of
information and Red means a communications failure. The bottom of all screens will show if a cable is
calibrated or disabled, the sensor address and sensor name. Certain screens will also show an X and Y
coordinate (by use of the mouse) location for measurements.

4.1.2 Sensor Settings

Selecting the “Sensor Setting” tab will open the Sensor Settings screen as shown in Figure 4.3.

Figure 4.3 – Sensor Settings Screen


24 Version H
UIST II Manual

4.1.2.1 Sensor ID Tag

Selecting the “Sensor ID Tag” edit button will open a “Cancel” and “Accept” button as shown in Figure 4.4.
This field is used to enter a unique name for the sensor. Accept will save the change while Cancel will end the
task. Once accepted, the name will be displayed at the bottom of the screen and in the sensor ID tag field. The
Sensor ID Tag can be up to 64 characters and supports Unicode.

Figure 4.4 – Sensor ID Tag

4.1.2.2 Sensor Date/Time

Selecting the “Sensor Date/Time” edit button will open a “Cancel” and “Accept” button. This field is used to set
the correct year, month, day, hours, minutes and seconds for the sensor. Select any one of the fields and type in
the correct information or select the field and use the up/down arrows for changes. Accept will save the change
while Cancel will end the task.

4.1.2.3 Response Timer Value (ms)

Selecting the “Response Timer Value” edit button will open a “Cancel” and “Accept” button as shown in Figure
4.5. This field is used to set the response timer value in milliseconds for the sensor. The time adjustment is done
by a slide bar (or the directional arrows) and has a range from 10ms to 40ms with a default value of 10ms as
shown in Figure 4.5. This adjustment is typically used when doing SDK development which may require
different poll response turn around delay times. Accept will save the change while Cancel will end the task.

25 Version H
UIST II Manual

Figure 4.5 – Response Timer Value

4.1.2.4 Cable A Status – Cable B Status

Selecting the “Cable A Status” or “Cable B Status” edit button will open a “Cancel” and “Disable” button as
shown in Figure 4.6. “Enabled” (will detect) is the default setting. Selecting “Disabled” (will not detect) will
turn that cable off and “Cancel” will end the task. Select the required operation. Note: If a cable is Disabled and
the edit button is selected a Cancel and Enabled button will be available.

Figure 4.6 – Cable Status


26 Version H
UIST II Manual

A “Disabled” cable will show the alarm and fault LED on the screen in gray (inactive) and no alarms will be
generated. The cable status at the bottom of the screen will be red for disabled.

4.1.2.5 Reboot Sensor

Selecting the “Reboot Sensor” reboot button will open a “Cancel” and “Reboot” button. Cancel will end the task
and Reboot will send a software reboot command to the PM II processor to initiate a reboot of the sensor in the
same manner as if power was removed and restored.

4.1.2.6 Restore Factory Defaults

Selecting the “Restore Factory Defaults” restore button will open a “Cancel” and “Restore” button. Cancel will
end the task and Restore will send a software message command to the PM II to restore all factory default
settings. This function should be done on a new installation to ensure no erroneous data is in the PM II. This will
also erase any alarm history that may be stored in the PM II.

4.2 Cable A and Cable B


Selecting either Cable A or Cable B tab will open the configuration tabs as shown in Figure 4.7. The tabs for
viewing and configuring the cables are: Configuration Parameters, Clutter, Target, Target Location, Incremental
Threshold, Incremental Enable/Disable, Detection Level, and Detection Window. Note: Each cable is set up
independently of the other cable so both cables (if used) need to be configured. The screens associated with
these tabs will only be active if the cable has been set to “Enable” as discussed in Section 4.1.2.4. If a cable is
set as “Disabled”, the screens in these tabs will be “grayed” out (inactive).

Figure 4.7 – Cable A or B Configuration Tabs

4.2.1 Configuration Parameters

Selecting the “Configuration Parameters” tab will open the screen as shown in Figure 4.7. This screen will be
used to set the Analog Channel Gain Setting, Integrator Sample Length, Threshold Factor, Alarm Mask Time,
Alarm Mask Window and Alarm Hold Time.
27 Version H
UIST II Manual

4.2.1.1 Analog Channel Gain Setting

Selecting the “Analog Channel Gain Setting” edit button will open a “Slide Bar” “Cancel” button “Default”
button and “Accept” button as shown in Figure 4.8. This setting will add 6db of gain to the system. Using the
slide bar the value can be changed from “0” to “1” (adds the gain). The change can be viewed in the Clutter tab
by an increase or decrease of signal. This gain can be used to improve target response on different mediums.
Cancel will end the task, Default will set the line back to the factory default setting (0) and Accept will save any
change made to the parameter.

Figure 4.8 – Analog Channel Gain

4.2.1.2 Integrator Sample Length

Selecting the “Integrator Sample Length” edit button will open a “Slide Bar” “Cancel” button “Default” button
and “Accept” button as shown in Figure 4.9. This setting is used to change the target response time for fast,
medium or slow climbing targets on the fence. Using the slide bar or directional arrows the value can be
changed from “0” (fast), “1” (medium) or “2” (slow) to meet site detection requirements. Cancel will end the
task, Default will set the line back to the factory default setting (2) and Accept will save any change made to the
parameter.

4.2.1.3 Threshold Factor

Selecting the “Threshold Factor” edit button will open a “Slide Bar” “Cancel” button “Default” button and
“Accept” button as shown in Figure 4.10. This setting is used to change the threshold (sensitivity) of the entire
cable that has been selected (A or B). Using the slide bar or directional arrows the value can be changed from “0
dB” (minimum sensitivity) to “-40 dB” (maximum sensitivity). Cancel will end the task, Default will set the line
back to the factory default (-12dB) setting and Accept will save any change made to the parameter. The change
can be seen on the “Target Location” screen.

28 Version H
UIST II Manual

Figure 4.9 – Integrator Sample Length

Figure 4.10 – Threshold Factor

29 Version H
UIST II Manual

4.2.1.4 Alarm Mask Time

Selecting the “Alarm Mask Time” edit button will open a “Slide Bar” “Cancel” button “Default” button and
“Accept” button as shown in Figure 4.11. This setting is used to set the time delay between multiple alarms
occurring at the same location. Using the slide bar or directional arrows the value can be changed from “1
second” to “60 seconds”. Cancel will end the task, Default will set the line back to the factory default setting
(15) and Accept will save any change made to the parameter.

Figure 4.11 – Alarm Mask Time

4.2.1.5 Alarm Mask Window

Selecting the “Alarm Mask Window” edit button will open a “Slide Bar” “Cancel” button “Default” button and
“Accept” button as shown in Figure 4.12. This setting is used to set the number of cells to be blocked from
reporting another alarm once an alarm has been declared. This is used in conjunction with the Alarm Mask
Time. Using the slide bar or directional arrows the value can be changed from “0 cells” to “207 cells”. Cancel
will end the task, Default will set the line back to the factory default setting (5) and Accept will save any change
made to the parameter. The “Alarm Mask Window” and “Alarm Mask Time” are typically used in conjunction.

4.2.1.6 Alarm Hold Time

Selecting the “Alarm Hold Time” edit button will open a “Slide Bar” “Cancel” button “Default” button and
“Accept” button. This setting is used to set the time duration that an alarm will be held active before
automatically resetting. Using the slide bar or directional arrows the value can be changed from “1 second” to
“60 seconds”. Cancel will end the task, Default will set the line back to the factory default setting (5) and Accept
will save any change made to the parameter.

30 Version H
UIST II Manual

Figure 4.12 – Alarm Mask Window

4.2.2 Clutter

Selecting the “Clutter” tab will open the screen as shown in Figure 4.13. This screen is used for reference only
and no adjustments can be made other than the Analog Channel Gain Setting as discussed in Section 4.2.1.1.
Clutter is the fixed measurement of reflections from all cells in a steady state (no target present). The amplitude
should not exceed +/- 7168 in the steady state. If there is no clutter, the sensor will not operate properly.

Figure 4.13 – Clutter


31 Version H
UIST II Manual

4.2.3 Target

Selecting the “Target” tab will open the screen as shown in Figure 4.14. This screen is used for reference only
and no adjustments can be made. This is the ambient noise level in a steady state (no target present). This noise
level should not exceed +/- 256. The screen resolution can be increased or decreased by using the slide bar at the
bottom of the screen by the magnifying glass. When a target is present, as shown in Figure 4.15, the cable is
modulated providing a point target characteristic signature. The target should not saturate on the maximum
screen setting.

Figure 4.14 – Target (Steady State)

Figure 4.15 – Target (Present)


32 Version H
UIST II Manual

4.2.4 Target Location

Selecting the “Target Location” tab will open the screen as shown in Figure 4.16. This screen is used for
calibrating the cable and viewing activity on the cable. The “red” line displayed on the screen is a default flat
line calibration at 48dB that provides the system a nominal calibration level if calibration has not been
performed. To start the calibration process, select the “Start Calibration” button then the “Clear Calibration”
button. Walk along the cable rattling the fence with a large screwdriver or piece of metal conduit for all cable
associated with that side of the PM II. Figure 4.17 shows “Cable B” being calibrated.

Figure 4.16 – Target Location

Figure 4.17 – Cable Being Calibrated


33 Version H
UIST II Manual

When the calibration is started the red line will be at the top of the screen and the bottom of the screen will say
“Cable B Calibrating”. If there had been a previous calibration in the PM II processor, then the “Clear
Calibration” button should be selected to remove that calibration. Note: calibration must be done at the default
threshold factor of -12dB. If the calibration process needs to be stopped select the “Cancel Calibration” button.
To keep the flat line calibration, start the calibration and then save the calibration. Note: the processor will not
report alarms until the cable is calibrated.

Once the cable(s) has been calibrated from the PM II to the LU II, TU II or CTU II and back to the PM II, select
the “Save Calibration” button to save the calibration profile to the flash memory of the processor. A fully
calibrated cable is shown in Figure 4.18. The blue line represents the calibration profile while the red line is the
alarm threshold with the default -12 dB threshold (sensitivity) setting applied. The calibration, in this example,
starts to drop off at cell 191 which is the length of cable attached to the fence. Since there is no cable to calibrate
beyond this point the threshold stays at a high level. Figure 4.19 shows the threshold with the blue line
calibration cleared by selecting the “Clear Max Hold” button.

Figure 4.18 –Calibrated Cable

The red line on the display is the threshold. It can be increased or decrease as required by using the “Threshold
Factor” as discussed in Section 4.2.1.3. A blue line from the bottom of the display represents a target on the
fence in the form of a “Max Peak Hold” as shown in Figure 4.20. If the blue line crosses threshold and meets the
event count an alarm will be declared and displayed as a “Red Dot” on the bottom of the display in the cell the
alarm occurred. Moving the mouse over the dot, the X and Y coordinate at the bottom of the screen shows the
alarm occurred in cell 35. Moving the mouse to the top of the max peak shows the amplitude to be 68 dB.

To clear any Max Peak Hold signal select the “Clear Max Hold” button as shown in Figure 4.20. A Max Peak
that gets to within 3dB of the threshold will be recorded in the alarm history buffer as a Target.

To clear any alarms displayed on the bottom of the screen select the “Clear Latched Alarms” button as shown in
Figure 4.20.
34 Version H
UIST II Manual

Figure 4.19 – Threshold from Calibrated Cable

Figure 4.20 – Target on Fence

35 Version H
UIST II Manual

4.2.5 Incremental Threshold

Selecting the “Incremental Threshold” tab will open the screen as shown in Figure 4.21. This screen is used for
selecting any section of cable (from cell 1 to 207) and increasing or decreasing the threshold (sensitivity) in the
cell(s) selected. Select the “Edit” button to open the edit screen as shown in Figure 4.22.

Figure 4.21 – Incremental Threshold

Figure 4.22 – Incremental Threshold Edit


36 Version H
UIST II Manual

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 4.23. As the arrow is moved across the
screen it will display the cell number associated with its location. In the Figure 4.23 example the cells from 90 to
110 are to be changed. The default value is 0 dB. In Figure 4.24 the threshold is being changed 4 dB by using
the “Increase” button (reduces the sensitivity in these cells) and is shown with the red line. The adjustments are
made in 1 dB steps. The coordinates show the mouse to be at cell 100 with a 4 dB change.

Figure 4.23 – Incremental Threshold Range

Figure 4.24 – Incremental Threshold Value


37 Version H
UIST II Manual

Once the threshold has been changed using the “Increase” (less sensitive) or “Decrease” (more sensitive)
buttons to the required level, select the “Accept” button to save the change as shown in Figure 4.25. The change
can be stopped by selecting the “Cancel” button or set back to the default setting of 0 by selecting the “Default”
button. This threshold change can also be seen in the “Target Location” tab.

Figure 4.25 – Incremental Threshold Change

4.2.6 Incremental Enable/Disable

Selecting the “Incremental Enable/Disable” tab will open the screen as shown in Figure 4.26. This screen is used
for selecting any section of cable (from cell 1 to 207) and making it “Active (Enabled)” or “Inactive (Disabled)”
in the cell(s) selected. Select the “Edit” button to open the edit screen as shown in Figure 4.27.

Figure 4.26 – Incremental Enable/Disable


38 Version H
UIST II Manual

Figure 4.27 – Incremental Enable/Disable Edit

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 4.28. As the arrow is moved across the
screen it will display the cell number associated with its location. Once the required area has been defined select
the “Disable” button to make that section of cable inactive or “Enable” to make that section of cable active. In
the Figure 4.28 example the cells from 60 to 65 where the cables goes under the gate has been set to “Disable”
as well as where the cable ended at cell 191. Select “Accept” to save the change as shown in Figure 4.29.The
action can be stopped by selecting the “Cancel” button.

Figure 4.28 – Incremental Enable/Disable Range


39 Version H
UIST II Manual

Figure 4.29 – Incremental Enable/Disable Change

The changes made in the Incremental Enable/Disable tab can also be seen in the “Target Location” tab as shown
in Figure 4.30. Remember to disable the cell at the end of the active cable.

Figure 4.30 – Incremental Enable/Disable Change in Target Location Tab


40 Version H
UIST II Manual

4.2.7 Detection Level

Selecting the “Detection Level” tab will open the screen as shown in Figure 4.31. This screen is used for
selecting any section of cable (from cell 1 to 207) to change the number of events required to declare an alarm.
The adjustment is from 1 to 4. Select the “Edit” button to open the edit screen as shown in Figure 4.32.

Figure 4.31 – Detection Level

Figure 4.32 – Detection Level Edit


41 Version H
UIST II Manual

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 4.33. As the arrow is moved across the
screen it will display the cell number associated with its location. Once the required area has been defined select
the “Increase” button to raise the number of events to declare an alarm or “Decrease” to reduce the number of
events to declare an alarm. In the Figure 4.34 example the entire cable is being changed from 2 events to 3
events to declare an alarm. Select “Accept” to save the change as shown in Figure 4.35.The action can be
stopped by selecting the “Cancel” button or set back to the default of 2 by selecting the “Default” button.

Figure 4.33 – Detection Level Range

Figure 4.34 – Detection Level Value


42 Version H
UIST II Manual

Figure 4.35 – Detection Level Change

4.2.8 Detection Window

Selecting the “Detection Window” tab will open the screen as shown in Figure 4.36. This screen is used for
selecting the time duration that multiple events must occur on any section of cable (from cell 1 to 207) to declare
an alarm. This only applies to Detection Level 2, 3 or 4 setting. The adjustment is from 30 to 240 seconds.
Select the “Edit” button to open the edit screen as shown in Figure 4.37. The default window time is 30 seconds.

Figure 4.36 – Detection Window


43 Version H
UIST II Manual

Figure 4.37 – Detection Window Edit

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 4.38. As the arrow is moved across the
screen it will display the cell number associated with its location. Once the required area has been defined select
the “Increase” button to raise the time or “Decrease” to reduce the time. In the Figure 4.39 example the time for
the entire active cable is being changed from 30 seconds to 60 seconds. Select “Accept” to save the change as
shown in Figure 4.40. The action can be stopped by selecting the “Cancel” button or set back to the default of 30
seconds by selecting the “Default” button.

Figure 4.38 – Detection Window Range


44 Version H
UIST II Manual

Figure 4.39 – Detection Window Value

Figure 4.40 – Detection Window Change


45 Version H
UIST II Manual

4.3 External Inputs


Selecting the “External Inputs” tab will open the External Inputs Configuration screen as shown in Figure 4.41.
This tab is used for setting up external inputs that are connected to any of the four (4) “External Alarms” inputs
on the PM II processor. The inputs can be set to Normally Open (default setting), Normally Closed or Disabled.
Selecting the “Edit” button next to the input will open the external input settings as shown in Figure 4.42.

Figure 4.41 – External Inputs

Figure 4.42 – External Input Edit


46 Version H
UIST II Manual

Select the required setting for the input (Cancel to keep the default Normally Open setting, Disabled or
Normally Closed). Note: If an input is set as “Disabled”, the associated LED in the top bar will be “grayed”
out (inactive) and no alarms will be generated as shown in Figure 4.43.

Figure 4.43 – External Input Disabled

4.4 Alarm History


Selecting the “Alarm History” menu in the top left corner of the screen will open two (2) options: Erase Alarm
History and Retrieve from Device as shown in Figure 4.44. This is available from all screens.

Figure 4.44 – Alarm History


47 Version H
UIST II Manual

4.4.1 Erase Alarm History

Selecting the “Erase Alarm History” menu will erase all event and alarm activity stored in the PM II processor.
A dialog box will open after it has been selected stating “Are you sure you want to erase the Alarm History”
with a “Yes” and “No” button. To erase: select “Yes” and to cancel select “No”.

On a new installation this function should be done before testing the system to set the threshold and/or
incremental threshold for proper detection requirements. This way only the data from the current testing is
retained in the processor.

On an existing installation this function should be done after the data from the processor has been retrieved,
evaluated and any adjustments made from the relevant information.

4.4.2 Retrieve from Device

Selecting the “Retrieve from Device” menu will retrieve all target, event, fault, external alarms, notice, service
and alarm activity stored in the PM II processor. The alarm buffer in the PM II processor will store up to 1024
records. When selected a dialog box stating “Retrieving Alarm History” will be displayed as shown in Figure
4.45. When the download is complete the box will disappear.

Figure 4.45 – Alarm Retrieve

The alarm history report as shown in Figure 4.46 will display a header with document number, copyright
information, report retrieval time, node address, tag name, mac address, software version, CPLD version, Cable
A and Cable B status, array types, array start and end (threshold value in that cell) and the alarm information.

The alarm history log format will have an index number (last entry is always on top), entry type (alarm, event,
fault, external alarm, tamper, notice and service), date, time and comment. For cable alarms it will also list the

48 Version H
UIST II Manual

cable (A or B), cell number, peak signal in that cell, threshold in that cell and calibration in that cell. A fault will
also list the cable while an external alarm will list the input number.

#57A46511-A01
#******************************************************************************
# Copyright (C) 2012, Southwest Microwave, Inc.
#
# All rights reserved, proprietary and confidential material.
# Unauthorized reproduction, modification and distribution is not permitted.
#******************************************************************************
# PM II ALARM HISTORY
# Report Retrieved on 2012-02-29 at 12:08:43
#******************************************************************************
# PM II NODE ADDRESS = 6
# PM II TAG NAME = PM II Chain Link Fence
# PM II MAC ADDRESS = aa:01:00:17:d8:9d
# PM II SOFTWARE VERSION = 64A46370-A01 REV Gxx
# PM II CPLD VERSION = 512
# PM II CABLE A ENABLED
# PM II CABLE A CALIBRATED
# PM II CABLE B ENABLED
# PM II CABLE B CALIBRATED
# Date=yyyy-mm-dd, Time=hh:mm:ss (24 hr). Peak, Threshold, and Calib in dB
#******************************************************************************
# Array types : 1 = cable A alarm threshold array
# 2 = cable A incremental threshold array
# 3 = cable A target calibration array
# 4-32 = reserved for future
# 33 = cable B alarm threshold array
# 34 = cable B incremental threshold array
# 35 = cable B target calibration array
# 36-64 = reserved for future
#******************************************************************************
Array 1 start
49,49,49,48,48,48,90,90,90,90,90,90,42,43,47,48,48,48,46,46,47,48,49,51,
50,50,50,48,48,47,47,46,47,47,47,48,49,47,49,49,49,50,49,48,47,47,48,49,
49,48,47,44,43,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
Array 1 end
Array 33 start
60,58,60,59,58,59,57,58,60,59,59,60,59,60,61,59,60,61,60,62,62,62,63,61,
61,61,61,63,63,63,62,61,62,63,63,62,62,60,60,60,59,59,59,60,62,62,63,62,
61,61,60,61,61,60,61,62,62,64,64,62,63,62,60,62,61,62,63,61,62,63,61,61,
60,60,62,61,60,60,58,57,57,56,57,57,57,57,56,56,57,57,58,57,55,56,55,54,
56,55,55,56,55,55,56,55,56,57,57,59,58,58,58,57,57,56,57,58,57,56,57,56,
57,58,56,56,56,55,57,57,57,57,55,55,57,57,59,59,58,60,60,60,60,59,58,58,
58,59,58,58,58,57,59,59,58,58,57,56,58,59,59,60,60,60,61,60,61,61,60,60,
60,58,60,60,59,58,56,56,57,57,58,59,59,61,60,60,60,59,60,60,59,58,55,90,
90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,90,
Array 33 end
#******************************************************************************
# Alarm History Log Format:
# INDEX, ALARM, DATE, TIME, CABLE, CELL, PEAK, THRESH, CALIB, COMMENT
# INDEX, EVENT, DATE, TIME, CABLE, CELL, PEAK, THRESH, CALIB, COMMENT
# INDEX, FAULT, DATE, TIME, CABLE, , , , , COMMENT
# INDEX, EXTALM, DATE, TIME, EXT#, , , , , COMMENT
49 Version H
UIST II Manual

# INDEX, TAMPER, DATE, TIME, , , , , , COMMENT


# INDEX, NOTICE, DATE, TIME, , , , , , COMMENT
# INDEX, SERVICE, DATE, TIME, , , , , , COMMENT
#******************************************************************************
# Alarms in process will be logged after alarm history flash buffer is erased
#******************************************************************************
1, MASKED, 2012-02-29, 12:06:55, B, 62, 69, 62, 74, MASKED EVENT
2, ALARM, 2012-02-29, 12:06:53, B, 63, 66, 60, 72, CABLE ALARM
3, EVENT, 2012-02-29, 12:06:51, B, 62, 69, 62, 74, CABLE EVENT
4, MASKED, 2012-02-29, 12:06:18, B, 51, 63, 60, 72, MASKED EVENT
5, ALARM, 2012-02-29, 12:06:16, B, 53, 62, 61, 73, CABLE ALARM
6, EVENT, 2012-02-29, 12:06:15, B, 52, 64, 61, 73, CABLE EVENT
7, MASKED, 2012-02-29, 12:05:49, B, 37, 65, 62, 74, MASKED EVENT
8, ALARM, 2012-02-29, 12:05:42, B, 37, 67, 62, 74, CABLE ALARM
9, EVENT, 2012-02-29, 12:05:40, B, 37, 66, 62, 74, CABLE EVENT
10, TARGET, 2012-02-29, 12:05:38, B, 38, 59, 60, 72, CABLE TARGET
11, ALARM, 2012-02-29, 12:05:07, B, 23, 69, 63, 75, CABLE ALARM
12, TARGET, 2012-02-29, 12:05:05, B, 22, 61, 62, 74, CABLE TARGET
13, EVENT, 2012-02-29, 12:05:03, B, 23, 67, 63, 75, CABLE EVENT
14, TARGET, 2012-02-29, 12:05:01, B, 23, 62, 63, 75, CABLE TARGET
15, MASKED, 2012-02-29, 12:04:27, B, 7, 69, 57, 69, MASKED EVENT
16, MASKED, 2012-02-29, 12:04:25, B, 7, 69, 57, 69, MASKED EVENT
17, ALARM, 2012-02-29, 12:04:23, B, 8, 65, 58, 70, CABLE ALARM
18, EVENT, 2012-02-29, 12:04:20, B, 7, 63, 57, 69, CABLE EVENT
19, SERVICE, 2012-02-29, 12:00:11, , , , , , UIST II CONNECTED
20, NOTICE, 2012-02-29, 12:00:11, , , , , , ALM HISTORY ERASED

Figure 4.46 – Alarm History

The Service Alarm is generated when the UIST II has been connected or disconnected. Notice alarms are
generated from actions such as a PM II reboot, alarm history erased and file system erased. A “Target” is a
signal that was 3 dB below threshold, “Event” is a target that was above threshold and “Masked” is an event that
would have been declared an alarm but occurred within the Mask Time and/or Mask Window.

There are other tabs to view the alarm history and are also used to set the appropriate threshold for the system.
These tabs are: Alarm Count Cable A and Cable B, Alarm Scatter Cable A and Cable B, Event Count Cable A
and Cable B and Event Scatter Cable A and Cable B.

4.4.2.1 Alarm Counts Cable A or B

Selecting the “Alarm Counts Cable A or B” tab will open the Alarm Counts screen as shown in Figure 4.47.
This screen will list all reported alarms and are displayed with a red line on the bottom of the screen in the cell
they occurred. It will also list the total amount of alarms from any cell. The bottom of the screen shows the cell
number while the left side of the screen shows the number of alarms. Moving the mouse pointer over an alarm
count will display the information as an X - Y coordinate in the lower right corner of the screen.

4.4.2.2 Alarm Scatter Cable A or B

Selecting the “Alarm Scatter A or B” tab will open the Alarm Scatter screen as shown in Figure 4.48. This
screen will list all reported alarms and are displayed as blue dots above the threshold line. The bottom of the
screen shows the cell number while the left side of the screen shows amplitude in dB. Moving the mouse pointer
over an alarm point will display the location and amplitude of the alarm as an X - Y coordinate in the lower right
corner of the screen.

50 Version H
UIST II Manual

Figure 4.47 – Alarm Counts

Figure 4.48 – Alarm Scatter

4.4.2.3 Event Counts Cable A or B

Selecting the “Event Counts Cable A or B” tab will open the Event Counts screen as shown in Figure 4.49. This
screen will list all reported cable events and displayed with a red line on the bottom of the screen in the cell they
occurred. It will also list the total amount of events from any cell. The bottom of the screen shows the cell
number while the left side of the screen shows the number of events. Moving the mouse pointer over an event
count will display the information as an X - Y coordinate in the lower right corner of the screen.
51 Version H
UIST II Manual

Figure 4.49 – Event Counts

4.4.2.4 Event Scatter Cable A or B

Selecting the “Event Scatter A or B” tab will open the Event Scatter screen as shown in Figure 4.50. This screen
will list all reported cable events and displayed as blue dots. The bottom of the screen shows the cell number
while the left side of the screen shows amplitude in dB. Moving the mouse pointer over an event point will
display the location and amplitude of the event as an X - Y coordinate in the lower right corner of the screen.

Figure 4.50 – Event Scatter


52 Version H
UIST II Manual

This screen also provides the capability to open, save and print the alarm history file from the “File” menu (the
file is a *.txt format so it can be imported into Excel™ for review and reports once saved), access to the Direct
Connect, Controller, Diagnostics and Supported Devices tabs as well as returning to the IST by selecting the
“Return to IST” menu. Selecting any of the other menus will terminate the UIST II session.

4.5 Software Setup and Testing


This manual has covered all the parameter settings required for system operation. The next two sections will
cover the software setup steps and testing.

The system should be installed per the MicroPoint™ II Installation and Operation manual. All communications
and power wiring should be correctly connected and the proper address for the PM II set.

4.5.1 Software Setup

The following procedure is a step by step process to setup the PM II processor. Start by connecting to the PM II
as described in Section 3.1.1 or 3.1.2.

1. Select “Restore Factory Defaults” from the Sensor Settings tab (Section 4.1.2.6).
2. Set the “Sensor ID Tag” from the Sensor Settings tab (Section 4.1.2.1).
3. Set the “Sensor Date/Time” from the Sensor Settings tab (Section 4.1.2.3).
4. Set the cable to Enabled or Disabled from the Sensor Settings tab (Section 4.1.2.4).
5. Check the “Clutter” and “Target” values (Sections 4.2.2 and 4.2.3).
6. Adjust the “Analog Channel Gain” (if needed based on Clutter level) from the Configuration Parameters
tab (Section 4.2.1.1).
7. Calibrated the cable(s) (Section 4.2.4) and set disabled cells (4.2.6).
8. Set the “Threshold Factor” to -20 dB from the Configuration Parameters tab (Section 4.2.1.3).
9. Set the “Detection Level” to 2 (Section 4.2.7).
10. Using the Cut Simulator tool, strike the center of each fence panel once for all cable associated to the
PM II being tested.
11. Retrieve the Alarm History File and display with the Event Scatter for Cable A and then Cable B
(Section 4.4).
12. Find the average dB level for all retrieved cut simulations.
13. Return to the IST II Configuration Parameters screen and adjust the Threshold Factor to be 3 dB below
the average level found in step 11.
14. Retrieve Alarm History File and display with the Event Scatter to verify that adjustment is correct.
15. Check/Set External Inputs at the PM II (if used) (Section 4.3)

4.5.2 Testing

After steps 1 through 15 have been completed for each PM II, the system is now ready for functional testing.
The functional testing is based on the user’s requirements. Typically this would be using the Cut Simulator tool
to simulate cutting the fence fabric to generate alarms and having a person climb the fence to generate alarms.

For cut simulation, the number of times to impact the fence is one more than the detection level is set. Example:
if the detection level is set to two (2) then the cut test should be done three (3) times to generate the alarm. Keep
in mind that the cut simulation needs to be done on the same panel.

When performing a climb test, care should be taken to avoid grabbing or stepping directly on the sensor cable.
Usually the posts and the cable are on the protected side of the fence. This means that the climb tests should be
performed on the opposite side of the fence from the sensor cable. The climber should weight at least 77 pounds
(35 kilograms).
53 Version H
UIST II Manual

The climber should grasp the fabric with both hands at shoulder height and begin climbing with one foot and
proceed in an aggressive and continuous motion, simultaneously altering hand above hand and foot above foot
to the maximum allowable height on the fence. If there is Razor Wire on the top of the fence, the climber
should stop short of this wire to avoid personal injury. In the absence of Razor Wire the climber should climb to
the point where the top of the fence is at waist height. After reaching the maximum height the climber should
immediately proceed to climb down to the ground in a continuous motion. The time to complete the climb up
and down should not exceed 0.8 times the height of the fence in feet (2.6 times the height of the fence in
meters). This means that for a typical 12 foot prison fence the simulated climb should not exceed 9.6 seconds
while for a typical 6 foot industrial fence the simulated climb should not exceed 4.8 seconds.

Make any adjustments to the system parameters such as threshold factor, detection window, detection level and
incremental threshold that may be required from the testing results and retest if necessary.

Monitor the system for at least a week for nuisance and false alarm activity. Retrieve the alarm history, evaluate
and make any needed adjustments.

4.6 Reports
Once a PM II has been fully configured and tested, a Configuration Report can be generated that captures all
information and settings of that processor and captures the Clutter, Target, Target Location, Incremental
Threshold, Incremental Enable/Disable, Detection Level and Detection Window screens for each attached cable.

To generate the report, select the “Reports” menu to open the Configuration Report menu as shown in Figure
4.51.

Figure 4.51 – Configuration Report


54 Version H
UIST II Manual

Selecting the “Configuration Report” will open the “Configuration Report Generator” as shown in Figure 4.52.
This dialog box will show the download process. Once the download is completed the standard Windows dialog
box for saving files will open. Select an appropriate location to save the report. The default report name will be
based on the electronic serial number of the unit along with the date and time the report was generated and will
be in *.PDF format.

Example: PM II-AA-01-00-17-D8-9D-CONFIG-REPORT-2012-09-26-13-45-50.pdf

This file should be saved for future reference and sent to Southwest Microwave prior to any site certification
trips or to assist in any troubleshooting. The report is in English only.

Figure 4.52 – Configuration Report Generator

4.7 General
The pull down list on the menu bar allows changing available languages at any time. The “About” menu
provides information on the MicroPoint™ II / MicroNet™ II Service Tool being used.

55 Version H
UIST II Manual

MICROTRACK II

56 Version H
UIST II Manual

5.0 MicroTrack™ II Installation Service Tool


To open the MicroTrack II Installation Service Tool, connect to the sensor as outlined in Section 3.1. Click on
the INTREPID™ MicroTrack II icon on the splash screen as shown in Figure 5.1. If nothing is clicked the
Installation Service Tool will open automatically.

Figure 5.1 – MicroTrack II Icon

5.1 Sensor Parameters


Once the INTREPID MicroTrack II icon has been selected, the Installation Service Tool “Sensor Parameters”
tab for the MicroTrack II will open as shown in Figure 5.2. This tab will display the MicroTrack II Sensor
Settings. The bottom status bar will show Cable Pair A and B initializing.

Figure 5.2 – Sensor Parameters


57 Version H
UIST II Manual

5.1.1 Sensor ID Tag

Selecting the “Sensor ID Tag” edit button will open a “Cancel” and “Accept” button as shown in Figure 5.3.
This blank field is used to enter a unique name for the sensor. Accept will save the change while Cancel will end
the task. Once accepted, the name will be displayed in the field and at the bottom of the screen. The Sensor ID
Tag supports Unicode and is limited to 64 characters. The status bar at the bottom of the screen will now display
that Cable Pair A and B are not calibrated.

Figure 5.3 – Sensor ID Tag

5.1.2 Sensor Date/Time

Selecting the “Sensor Date/Time” edit button will open that field to set the correct year, month, day, hours,
minutes and seconds for the sensor. Select any one of the fields and type in the correct information or select the
field and use the up/down arrows for changes. A “Cancel” or “Accept” button will be available after a change
has been made. Accept will save the change while Cancel will end the task.

5.1.3 Response Timer Value (ms)

Selecting the “Response Timer Value” edit button will open a “Slide Bar”, “Cancel” and “Accept” button as
shown in Figure 5.4. This field sets the response timer value in milliseconds for the sensor. The time adjustment
is done by the slide bar (or the directional arrows) and has a range from 10ms to 40ms with a default setting of
10ms. This adjustment is typically used when doing SDK development which may require different poll
response turn around delay times. A “Cancel” or “Accept” button will be available after a change has been
made. Accept will save the change while Cancel will end the task.

58 Version H
UIST II Manual

Figure 5.4 – Response Timer Value

5.1.4 Cable Pair A Status – Cable Pair B Status

Selecting the “Cable Pair A Status” or “Cable Pair B Status” edit button will open a “Cancel” and “Disable”
button as shown in Figure 5.5. The default setting is “Enable” (will detect). Select the required operation. If a
cable has been set to “Disable” (will not detect) the alarm and fault LED on the screen for that cable will be gray
(inactive) and no alarms will be generated. The status bar on the bottom of the screen will show that cable
disabled.

Figure 5.5 – Cable Pair Status; Enabled or Disabled


59 Version H
UIST II Manual

5.1.5 Reboot Sensor

Selecting the “Reboot Sensor” reboot button will open a “Cancel” and “Reboot” button. Reboot will send a
software command to the MTP II processor to initiate a reboot of the sensor in the same manner as if power was
removed and restored. Cancel will end the task.

5.1.6 Clear Site Information

Selecting the “Clear Site Information” clear button will open a “Cancel” and “Clear” button. Clear will erase all
information that has been set in the processor except for the MTP II address. Cancel will end the task.

5.1.7 Restore Factory Defaults

Selecting the “Restore Factory Defaults” restore button will open a “Cancel” and “Restore” button. Restore will
erase all information that has been set in the processor and return them to factory default settings including the
address for the MPT II. This function should be done on a new installation to ensure that no erroneous data
resides in the MTP II. Cancel will end the task.

5.1.8 Sensor Address

Selecting the “Sensor Address” edit button will open a “Slide Bar”, “Cancel” and “Accept” button as shown in
Figure 5.6. Using the slide bar or directional arrows, set the required address of the MTP II for this installation.
The address range is from 0 to 239. Accept will save the change while Cancel will end the task.

Figure 5.6 – MTP II Address

5.1.9 Sweep Channel Pair

Selecting the “Sweep Channel Pair” edit button will open a “Slide Bar”, “Cancel” and “Accept” button as shown
in Figure 5.7. Setting the value to 1 will change the frequency sweep from A and B to C and D. This adjustment
should not be made unless authorized by Southwest Microwave, Inc factory service technicians. It is only
used on unique site configurations. Accept will save the change while Cancel will end the task.
60 Version H
UIST II Manual

Figure 5.7 – Sweep Channel Pair

5.1.10 Sensor Information

Other sensor information that can be viewed for reference in the MicroTrack II Sensor Settings screen is:

 Electronic Serial Number (the MAC address – for Southwest Microwave use only)

 Alarm Poll Function Type (type of device being polled)

 Hardware Version (hardware version of the MTP II)

 Boot Version (boot version operating in the MTP II – part and version number)

 Boot Build Date (the date the boot was complied – YYYY-MM-DD)

 Boot Build Time (the time the boot was complied – hh-mm-ss)

 Application Version (the version of software operating in the MTP II – part and revision number)

 Application Build Date (the date the application software was compiled – YYYY-MM-DD)

 Application Build Time (the time the application software was compiled – hh-mm-ss)

5.2 Cable Pair A and Cable Pair B


Selecting either Cable Pair A or Cable Pair B tab will open the configuration tabs as shown in Figure 5.8. The
tabs for viewing and configuring the cables are: Parameters, Clutter Location, Target, Target Location,
Incremental Threshold and Incremental Enable/Disable. Note: Each cable is set up independently of the other
cable so both cables (if used) need to be configured. The screens associated with these tabs will only be active if
the cable has been set to “Enable” as discussed in Section 5.1.4. If a cable is set as “Disabled”, the screens in
these tabs will be “grayed” out (inactive).
61 Version H
UIST II Manual

Figure 5.8 - Cable Pair Configuration Tabs

5.2.1 Parameters

Selecting the “Parameters” tab will open the information as shown in Figure 5.8. This tab will be used to set the:

 Clutter Threshold Factor (sets the threshold factor for cable fault alarms)

 Target Input Attenuation (sets target input to correct magnitude)

 Security Level (sets unit for low or high security applications)

 Alarm Threshold Factor (cable sensitivity setting)

 Alarm Mask Time (sets time duration before another alarm can be declared in the same cell)

 Alarm Mask Window (sets number of cells to be masked out after an alarm has been reported)

 Alarm Hold Time (sets time duration to hold active alarm before resetting)

5.2.1.1 Clutter Threshold Factor

Selecting the “Clutter Threshold Factor” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept”
button as shown in Figure 5.9. This setting is used to change the value required to declare a Cable Fault Alarm.
The default value is 12dB. The minimum value is 0dB and the maximum value is 30dB. Using the slide bar or
directional arrows, adjust as needed to meet site requirements. To view the setting select the “Clutter Location”
tab as shown in Figure 5.17. The blue line represents the clutter value while the red lines represent the cable
fault thresholds. Accept will save the change, Cancel will end the task while Default will set the parameter back
to the default setting. Note: a 0 dB setting will cause a continuous cable fault alarm.

62 Version H
UIST II Manual

Figure 5.9 - Clutter Threshold Factor

5.2.1.2 Target Input Attenuation

Selecting the “Target Input Attenuation” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept”
button as shown in Figure 5.10. This setting is used to set the input attenuation value to obtain the nominal
operating level of +/- 256 to +/- 1024 counts after the gain has been set. The default value is 3dB. The minimum
value is 0dB and the maximum value is 16dB. Using the slide bar or directional arrows, adjust to get as close as
possible to +/- 512 count. To view the setting select the “Target Input” tab as shown in Figure 5.18. Accept will
save the change, Cancel will end the task while Default will set the parameter back to the default setting.

Figure 5.10 - Target Input Attenuation


63 Version H
UIST II Manual

5.2.1.3 Security Level

Selecting the “Security Level” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept” button as
shown in Figure 5.11. This setting is used to change from a low to high security level. The default value is 0
(low). The minimum value is 0 (low) and the maximum value is 1 (high). Using the slide bar or directional
arrows, adjust as needed to meet site requirements. Accept will save the change, Cancel will end the task while
Default will set the parameter back to the default setting.

Typically a high security site requires detection of crawling, walking, running and running/jumping intruders
while a low security site only requires detection of a walking and running intruder. Most sites can meet all site
detection requirements using the 0 value.

Figure 5.11 - Security Level

5.2.1.4 Alarm Threshold Factor

Selecting the “Alarm Threshold Factor” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept”
button as shown in Figure 5.12. This setting is used to change the threshold (sensitivity) of the cable being
configured. The default value is -12dB. The minimum value is 0dB and the maximum value is -40dB (most
sensitive). Using the slide bar or directional arrows, adjust as needed to meet site requirements. To view the
setting, select the “Target Location” tab as shown in Figure 5.19. Cancel will end the task while Default will set
the parameter back to the default setting.

After the cable has been calibrated, perform site testing requirements such as walk tests, run tests, crawl tests,
etc. and increase or decrease the threshold factor to meet the detection requirements of the site.

64 Version H
UIST II Manual

Figure 5.12 – Alarm Threshold Factor

5.2.1.5 Alarm Mask Time

Selecting the “Alarm Mask Time” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept” button
as shown in Figure 5.13. This setting is used to change the time duration that prohibits the reporting of another
alarm in that location for a set time. The default value is 15 seconds. The minimum value is 0 seconds and the
maximum value is 60 seconds. Using the slide bar or directional arrows, adjust as needed to meet site
requirements. Accept will save the change, Cancel will end the task while Default will set the parameter back to
the default setting.

Figure 5.13 – Alarm Mask Time


65 Version H
UIST II Manual

5.2.1.6 Alarm Mask Window

Selecting the “Alarm Mask Window” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept”
button as shown in Figure 5.14. This setting is used to change the number of cells that will be masked after an
alarm has been reported. The default value is 5 cells. The minimum value is 0 cells and the maximum value is
104 cells. Using the slide bar or directional arrows, adjust as needed to meet site requirements. Accept will save
the change, Cancel will end the task while Default will set the parameter back to the default setting.

The “Alarm Mask Window” is typically used in conjunction with the “Alarm Mask Time”.

Example: if the Alarm Mask Window and the Alarm Mask Time is set at default settings and an alarm is
reported at cell 50, another alarm would not be reported in cells 45 to 55 for 15 seconds. The Alarm Mask
Window is at default +/- 5 cells and the Alarm Mask Window is at default 15 seconds. Note: with these settings
a second crossing will be displayed on the Target Location screen but no alarm will be shown or recorded in the
alarm buffer as it has been masked.

Figure 5.14 – Alarm Mask Window

5.2.1.7 Alarm Hold Time

Selecting the “Alarm Hold Time” edit button will open a “Slide Bar”, “Cancel”, “Default” and “Accept” button
as shown in Figure 5.15. This setting is used to change the time duration that an alarm is held in the MPT II
processor before resetting. The default value is 3 seconds. The minimum value is 0 seconds and the maximum
value is 60 seconds. Using the slide bar or directional arrows, adjust as needed to meet site requirements. Accept
will save the change, Cancel will end the task while Default will set the parameter back to the default setting.

66 Version H
UIST II Manual

Figure 5.15 – Alarm Hold Time

5.2.2 Clutter Input

Selecting the “Clutter Input” tab will open the screen as shown in Figure 5.16. This screen is used to view the
gain of the cable set being configured. Once a cable set has been “Enabled” the clutter will increase from 0
counts to +/- 88 counts and set the “Channel Gain” which can be viewed in the upper right corner of the screen.
The gain will range from 0 to 255. The bottom of the screen shows the 64 frequency bins. If the gain is below 40
dB in line attenuators will be required.

Figure 5.16 – Clutter Input


67 Version H
UIST II Manual

5.2.3 Clutter Location

Selecting the “Clutter Location” tab will open the screen as shown in Figure 5.17. This screen is used to view
and set the clutter threshold for reporting a Cable Fault Alarm. The blue line represents the clutter value while
the red lines represent the cable fault thresholds. If the blue line crosses either of the red lines a Cable Fault
Alarm will be reported. The threshold can be changed as discussed in section 5.2.1.1, Clutter Threshold Factor.

Figure 5.17 – Clutter Location

5.2.4 Target Input

Selecting the “Target Input” tab will open the screen as shown in Figure 5.18. This screen is used to set and
view the Target Input Attenuation. An acceptable range for nominal operation is +/- 256 to +/- 1024 counts with
an average range to obtain of +/- 512 counts. The “Target Input Attenuation” adjustment, which is found in
Section 5.2.1.2, will either double this signal strength if you decrease it’s value by 1, or it will cut the signal
strength in half if you increase it’s value by 1. Using the slide bar or directional arrows, adjust as needed to meet
+/- 512 counts range.

Note that this is an attenuation value. Increasing the attenuation will decrease the signal strength, and vise-versa.
Since the signal can be doubled or cut it in half, it is not always possible to hit +/- 512, so select the closest
setting that meets the range. Typically this is the default setting 3.

The counts are shown on the left side of the screen while the frequency bins are displayed at the bottom of the
screen. A magnifying glass is also available at the bottom left of the screen to zoom in or out by using the slide
bar.

68 Version H
UIST II Manual

Figure 5.18 – Target Input

5.2.5 Target Location

Selecting the “Target Location” tab will open the screen as shown in Figure 5.19. This screen is used for
calibrating the cable and viewing activity on the cable. The “red” line displayed on the screen is a default flat
line calibration that provides the system a nominal calibration level if calibration has not been performed. The
blue line is the ambient noise on the system. To start the calibration process, select the “Start Calibration”
button then the “Clear Calibration” button. Walk between the cable pair from the MTP II processor to the
cable end where the MTT or MTI are installed and then back to the MTP II processor. Figure 5.20 shows the
“Cable Pair A” being calibrated. Note: the noise is typically between 35 and 45 dB.

Figure 5.19 – Target Location


69 Version H
UIST II Manual

Figure 5.20 – Calibration Walk

Once the calibration walk has been completed select the “Save Calibration” button to save the calibration to the
memory of the MTP II processor. Figure 5.21 show a completely calibrated cable pair. After the cable pair has
been calibrated, the system will now be able to report alarms.

Figure 5.21 – Calibrated Cable


70 Version H
UIST II Manual

To adjust the threshold (sensitivity) of the entire cable pair, open the “Alarm Threshold Factor” as discussed in
Section 5.2.1.4. Increase or decrease the value using the slide bar or directional arrows. This adjustment should
be done during site detection requirement testing.

5.2.6 Incremental Threshold

Selecting the “Incremental Threshold” tab will open the screen as shown in Figure 5.22. This screen is used for
selecting any section of a cable pair (from cell 9 to 104) and increasing or decreasing the threshold (sensitivity)
in the cell(s) selected. Select the “Edit” button to open the screen as shown in Figure 5.23.
.

Figure 5.22 – Incremental Threshold

Figure 5.23 – Incremental Threshold Range


71 Version H
UIST II Manual

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 5.24. As the arrow is moved across the
screen it will display the cell number associated with its location. In the Figure 5.24 example the cells from 40 to
50 are to be changed. The default value is 0dB. In Figure 5.24 the threshold is being changed 6dB by using the
“Increase” button (increases the Threshold to make these cells less sensitive) and is shown with the red line. The
adjustments are made in 1 dB steps. The coordinates at the bottom of the screen show the mouse to be at cell 45
with a 6dB change.

Figure 5.24 – Incremental Threshold Value

Figure 5.25 – Incremental Threshold Change


72 Version H
UIST II Manual

Once the threshold has been changed using the “Increase” or “Decrease” buttons to the required level, select the
“Accept” button to save the change as shown in Figure 5.25. The change can be stopped by selecting the
“Cancel” button or set back to the default setting by selecting the “Default” button. This threshold change can
also be seen in the “Target Location” tab.

5.2.7 Incremental Enable/Disable

Selecting the “Incremental Enable/Disable” tab will open the screen as shown in Figure 5.26. This screen is used
for selecting any section of a cable pair (from cell 9 to 104) and making it “Active (Enabled)” or “Inactive
(Disabled)” in the cell(s) selected. This must be done for the start and end of each cable pair. Select the “Edit”
button to open the screen as shown in Figure 5.27.

Figure 5.26 – Incremental Enable/Disable

Figure 5.27 – Incremental Enable/Disable Range


73 Version H
UIST II Manual

Select the bottom red arrow and position it at the beginning of the cell(s) to be edited. Select the top red arrow
and position it at the end of the cell(s) to be edited as shown in Figure 5.28. As the arrow is moved across the
screen it will display the cell number associated with its location. In the Figure 5.28 example the cells from 100
to 104 are being “Disabled” as cell 100 is the last active detection cell. Cells 9 to 13 have also been disabled as
detection is to begin in Cell 14. Note: cells 0 to 9 are the lead-in cable.

Figure 5.28 – Incremental Enable/Disable Value

Figure 5.29 – Incremental Enable/Disable Change

Once the cell locations have been set, select the “Enable” or “Disable” button to make the change as shown in
Figure 5.29. This start and end setting can also be seen in the “Target Location” tab as shown in Figure 5.30.

74 Version H
UIST II Manual

Figure 5.30 – Target Location with Starting/Ending Cell Disabled

5.2.8 Target Location Alarm

Figure 5.31shows the Target Location screen with a single alarm. Moving the mouse pointer over the alarm
peak will show the location and amplitude at the bottom of the screen. In this example the alarm is in cell 25
with amplitude of 74dB.

Figure 5.31 – Target Location with Single Alarm


75 Version H
UIST II Manual

5.3 Alarm History


Selecting the “Alarm History” menu will open two (2) options: Erase Alarm History and Retrieve from Device
as shown in the upper left corner of Figure 5.32. It can be opened from any tab.

Figure 5.32 – Erase or Retrieve Alarm History

5.3.1 Erase Alarm History

Selecting the “Erase Alarm History” menu will erase all alarm activity stored in the MTP II processor. A dialog
box will open after it has been selected stating “Are you sure you want to erase the Alarm History” with a “Yes”
and “No” button. To erase: select “Yes” and to cancel select “No”.

On a new installation this function should be done before testing the system to set the threshold and/or
incremental threshold for proper detection requirements. This way only the data from the current testing is
retained in the processor.

On an existing installation this function should be done after the data from the processor has been retrieved,
evaluated and any adjustments made from the relevant information.

5.3.2 Retrieve from Device

Selecting the “Retrieve from Device” menu will retrieve all alarm, fault, notice, tamper and service activity
stored in the MTP II processor. The alarm buffer in the MTP II processor will store up to 1024 records. When
selected a dialog box stating “Retrieving Alarm History” will be displayed as shown in Figure 5.33. When the
download is complete the box will disappear.

76 Version H
UIST II Manual

Figure 5.33 – Alarm History Retrieve

The alarm history report as shown in Figure 5.33 will display a header with document number, copyright
information, report retrieval time, node address, tag name, mac address, software version (boot and apps), FPGA
version, Cable A and Cable B status, array types, array start and end (threshold value in that cell) and the alarm
information.

The alarm history log format will have an index number (last entry is always on top), entry type (alarm, fault,
tamper, notice and service), date, time and comment. For cable pair alarms it will also list the cable pair (A or
B), cell number and peak signal in that cell, threshold in that cell, calibration in that cell and ASV value. A fault
will also list the cable pair.

#57A46510-A01
#******************************************************************************
# Copyright (C) 2012, Southwest Microwave, Inc.
#
# All rights reserved, proprietary and confidential material.
# Unauthorized reproduction, modification and distribution is not permitted.
#******************************************************************************
# MTP II ALARM HISTORY
# Report Retrieved on 2012-03-09 at 07:54:19
#******************************************************************************
# MTP II NODE ADDRESSS = 0
# MTP II TAG NAME = MTP II #0 Buried
# MTP II MAC ADDRESSS = aa:05:18:37:a3:13
# MTP II BOOT VERSION = 64A46237-A01 REV Bx
# MTP II APPS VERSION = 64A46607-A01 REV Axy
# MTP II FPGA VERSION = 20
# MTP II CABLE A ENABLED
# MTP II CABLE A CALIBRATED
# MTP II CABLE B DISABLED
# MTP II CABLE B NOT CALIBRATED
# Date=yyyy-mm-dd, Time=hh:mm:ss (24 hr). Peak, Threshold, and Calibration in dB
#******************************************************************************

77 Version H
UIST II Manual

# Array types: 1 = cable A alarm threshold array


# 2 = cable A incremental threshold array
# 3 = cable A target calibration array
# 4-32 = reserved for future
# 33 = cable B alarm threshold array
# 34 = cable B incremental threshold array
# 35 = cable B target calibration array
# 36-64 = reserved for future
#******************************************************************************
Array 1 start
93,93,93,93,93,93,93,93,93,93,93,93,59,60,61,62,62,62,60,60,59,58,60,60,
62,65,66,66,66,66,65,64,64,62,64,67,66,66,65,60,62,64,66,67,67,66,67,66,
64,64,64,66,65,66,66,65,65,65,65,65,65,67,66,67,65,65,64,65,65,66,64,65,
65,64,60,57,55,56,59,61,62,61,60,59,59,60,60,60,60,56,57,55,56,57,59,60,
61,60,59,57,93,93,93,93,93,93,93,93,93,93,93,93,93,93,
Array 1 end
Array 33 start
93,93,93,93,93,93,93,93,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,
21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,
21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,
21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,
21,21,21,21,21,21,21,21,93,93,93,93,93,93,93,93,93,93,
Array 33 end
#******************************************************************************
# Alarm History Log Format:
# INDEX, ALARM, DATE, TIME, CABLE, SC, PEAK, THRESH, CALIB, ASV, COMMENT
# INDEX, FAULT, DATE, TIME, CABLE, , , , , , COMMENT
# INDEX, TAMPER, DATE, TIME, , , , , , , COMMENT
# INDEX, NOTICE, DATE, TIME, , , , , , , COMMENT
# INDEX,SERVICE, DATE, TIME, , , , , , , COMMENT
#******************************************************************************
# Alarms in process will be logged after alarm history flash buffer is erased
#******************************************************************************
1, FAULT, 2012-03-09, 07:54:12, A, , , , , , NO CABLE FAULT
2, FAULT, 2012-03-09, 07:54:07, A, , , , , , CABLE FAULT
3, ALARM, 2012-03-09, 07:50:34, A, 78, 66, 56, 68, -1, CABLE ALARM
4, ALARM, 2012-03-09, 07:50:08, A, 70, 77, 66, 78, -1, CABLE ALARM
5, ALARM, 2012-03-09, 07:49:49, A, 64, 78, 67, 79, -1, CABLE ALARM
6, ALARM, 2012-03-09, 07:49:29, A, 59, 76, 65, 77, -1, CABLE ALARM
7, ALARM, 2012-03-09, 07:49:10, A, 55, 77, 66, 78, -1, CABLE ALARM
8, ALARM, 2012-03-09, 07:48:49, A, 48, 76, 66, 78, -1, CABLE ALARM
9, ALARM, 2012-03-09, 07:48:30, A, 43, 75, 66, 78, -1, CABLE ALARM
10, ALARM, 2012-03-09, 07:48:08, A, 37, 75, 66, 78, -2, CABLE ALARM
11, ALARM, 2012-03-09, 07:47:34, A, 32, 76, 64, 76, -2, CABLE ALARM
12, ALARM, 2012-03-09, 07:47:06, A, 27, 79, 66, 78, 0, CABLE ALARM
13, ALARM, 2012-03-09, 07:46:45, A, 23, 68, 60, 71, -3, CABLE ALARM
14, ALARM, 2012-03-09, 07:46:19, A, 18, 72, 62, 74, -2, CABLE ALARM
15, ALARM, 2012-03-09, 07:45:53, A, 14, 73, 60, 72, 0, CABLE ALARM
16, SERVICE, 2012-03-09, 07:45:13, , , , , , , UIST II CONNECTED
17, NOTICE, 2012-03-09, 07:45:13, , , , , , , ALM HISTORY ERASED

Figure 5.34 – Alarm History

78 Version H
UIST II Manual

The Service Alarm is generated when the UIST II has been connected or disconnected. Notice alarms are
generated from actions such as a MTP II reboot, alarm history erased and file system erased.

Four (4) other tabs are available to view the alarm history and are also used to set the appropriate threshold for
the system and system diagnostics. These tabs are: Alarm Counts Cable A and Cable B and Alarm Scatter Cable
A and Cable B.

5.3.3 Alarm Counts Cable A or B

Selecting the “Alarm Counts Cable A or B” tab will open the Alarm Counts screen as shown in Figure 5.35.
This screen will list all reported alarms and are displayed with a red line on the bottom of the screen in the cell
they occurred. It will also list the total amount of alarms from any cell. The bottom of the screen shows the cell
number while the left side of the screen shows the number of alarms. Moving the mouse pointer over an alarm
count will display the information as an X - Y coordinate in the lower right corner of the screen.

If a cable is “Disabled” and the tabs is selected the screen will show “No Data to be Displayed”.

Figure 5.35 – Alarm Counts

5.3.4 Alarm Scatter Cable A or B

Selecting the “Alarm Scatter A or B” tab will open the Alarm Scatter screen as shown in Figure 5.36. This
screen will list all reported alarms and are displayed as blue dots above the threshold line. The bottom of the
screen shows the cell number while the left side of the screen shows the amplitude in dB. Moving the mouse
pointer over an alarm point will display the location and amplitude of the alarm as an X - Y coordinate in the
lower right corner of the screen.

If a cable is “Disabled” and the tabs is selected the screen will show “No Data to be Displayed”.

79 Version H
UIST II Manual

Figure 5.36 – Alarm Scatter

5.4 Software Setup and Testing


This manual has covered all the parameter settings required for system operation. The next two sections will
cover the software setup steps and testing.

The system should be installed per the MicroTrack™ II Installation and Operation manual. All communications
and power wiring should be correctly connected and the proper address for the MTP II set.

5.4.1 Software Setup

The following procedure is a step by step process to setup the MTP II processor. Start by connecting to the MTP
II as described in Section 3.1.1 or 3.1.2.

1. Select “Restore Factory Defaults” from the Sensor Settings tab (Section 5.1.7).
2. Set the “Sensor ID Tag” from the Sensor Settings tab (Section 5.1.1).
3. Set the “Sensor Date/Time” from the Sensor Settings tab (Section 5.1.2).
4. Set the cable pair to Enabled or Disabled from the Sensor Settings tab (Section 5.1.4).
5. Set the correct “Sensor Address” from the Sensor Settings tab (Section 5.1.8).
6. Check the “Clutter Input” for gain setting (Section 5.2.2)
7. Check and set the “Clutter Location” (Section 5.2.3).
8. Check the “Target Input” (Section 5.2.4) and set “Target Input Attenuation” (Section 5.2.1.2).
9. Set “Security Level” from the Sensor Parameters tab (Section 5.2.1.3)
10. Calibrated the cable pair(s) (Section 5.2.5).
11. Set the beginning and ending detection cells (Section 5.2.7).

80 Version H
UIST II Manual

12. Test by walking, running or crawling at 10 foot (3m) intervals along the cable pair length.
13. Retrieve the Alarm History File and display with the Alarm Scatter for Cable A and then Cable B
(Section 5.3).
14. Find the average dB level for all retrieved testing.
15. Return to the IST II Configuration Parameters screen and adjust the Threshold Factor to be 1 dB below
the average level found in step 14.
16. Retrieve Alarm History File and display with the Alarm Scatter to verify that adjustment is correct.

5.4.2 Testing

After steps 1 through 16 have been completed for each MTP II, the system is now ready for functional testing.
The functional testing is based on the user’s requirements. Typically this would be walking, running, jumping
and crawling intrusion attempts to generate alarms. The testing person should weight at least 77 pounds (35
kilograms).

Make any adjustments to the system parameters that may be required from the testing results such as Alarm
Threshold adjustment, Incremental Threshold adjustments, Alarm Masking Time, Alarm Masking Window and
Alarm Hold Time and retest if necessary.

Monitor the system for at least a week for nuisance and false alarm activity. Retrieve the alarm history, evaluate
and make any needed adjustments.

5.5 Reports
Once a MTP II has been fully configured and tested, a Configuration Report can be generated that captures all
information and settings of that processor and captures the Clutter Input, Clutter Location, Target Input, Target
Location, Incremental Threshold and Incremental Enable/Disable screens for each attached cable.

To generate the report, select the “Reports” menu to open the Configuration Report menu as shown in Figure
5.37.

Figure 5.37 – Configuration Report Menu


81 Version H
UIST II Manual

Selecting the “Configuration Report” will open the “Configuration Report Generator” as shown in Figure 5.38.
This dialog box will show the download process. Once the download is completed the standard Windows dialog
box for saving files will open. Select an appropriate location to save the report. The default report name will be
based on the electronic serial number of the unit along with the date and time the report was generated and will
be in *.PDF format.

Example: MTP II-AA-01-00-17-D8-9D-CONFIG-REPORT-2012-09-26-13-45-50.pdf

This file should be saved for future reference and sent to Southwest Microwave prior to any site certification
trips or to assist in any troubleshooting. The report is in English only.

Figure 5.38 – Configuration Report Generator

5.6 General
The pull down list on the menu bar allows changing available languages at any time. The “About” menu
provides information on the MicroTrack II Service Tool being used.

82 Version H
UIST II Manual

MICROWAVE 330

83 Version H
UIST II Manual

6.0 MicroWave 330 Installation Service Tool


To open the MicroWave 330 Installation Service Tool, connect to the sensor as outlined in Section 3.1. Click on
the INTREPID™ MicroWave 330 icon on the splash screen as shown in Figure 6.1. If nothing is clicked the
Installation Service Tool will open automatically.

Figure 6.1 – MicroWave 330 Icon

6.1 Sensor Information


Once the INTREPID MicroWave 330 icon has been selected, the Installation Service Tool “Sensor Information”
tab for the MicroWave 330 will open as shown in Figure 6.2. This tab will display the MicroWave 330 Sensor
Information.

Figure 6.2 – Sensor Information


84 Version H
UIST II Manual

All tabs will display the header. The menu bar will display:

 Alarm History: Allows retrieving the stored alarm history from the receiver or erasing the alarm history.
 Language: Allows selecting one of the four (4) languages (English, Spanish, Russian and Chinese).
 About: Provides information about the IST II software being used.

The LED’s displayed are:

 Alarm: The intrusion alarm from the receiver.


 Tamper: The tamper switch alarm from the receiver.
 Ext Input/Tamper: The alarm from an external input into the receiver.
 Align/Path Alarm: An alarm from the alignment signal changing by a preset value set in the IST II.
 Low Voltage: A low voltage alarm from the receiver that is activated at 11.0vdc.
 Wrong Channel: An alarm when the transmitter and receiver are set on different modulation channels in
the Un-Tethered mode.
 Jam: An alarm when a secondary RF source is trying to capture the receiver. Note: only applies to the
Un-Tethered mode.

If the LED is green it is in the “Secured” state. If red it is the “Alarm” state. The Wrong Channel and Jam
LED’s are gray and will not activate until that type of signal is received as there is no secure state associated to
these LED’s. These are indicators only.

The information displayed is:

 Mode: Shows if the synchronization is set to Off, Master or Slave.


 Channel: Shows which modulation channel the receiver is set to (A, B, C, D, E or F).
 Tether: Shows if the link is set in the Un-Tethered (No) mode or Tethered (Yes) mode.
 Recognition Algorithm: Show which algorithm is set in the link (Off, Standard, Enhanced Vehicle,
Enhanced Crawl or Maximum Security).
 FSA: Shows if the Fresnel Suppression Algorithm is On or Off.

The header will also display the Alignment Signal Voltage and Threshold to Noise Ratio of the link.

6.1.1 Sensor ID Tag

Selecting the “Sensor ID Tag” edit button will open a “Cancel” and “Accept” button as shown in Figure 6.3.
This blank field is used to enter a unique name for the sensor. Accept will save the change while Cancel will end
the task. Once accepted, the name will be displayed in the field as shown in Figure 6.4 and will also be
displayed at the bottom of the screen next to the Sensor ID Tag. The Sensor ID Tag supports Unicode and is
limited to 64 characters.

85 Version H
UIST II Manual

Figure 6.3 – Sensor ID Field

Figure 6.4 – Sensor ID Entered

6.1.2 Sensor Date/Time

Selecting the “Sensor Date/Time” edit button will open that field to set the correct year, month, day, hours,
minutes and seconds for the sensor. Select any one of the fields and type in the correct information or select the
field and use the up/down arrows for changes. A “Cancel” or “Accept” button will be available after a change
has been made. Accept will save the change while Cancel will end the task.

86 Version H
UIST II Manual

6.1.3 Response Timer Value (ms)

Selecting the “Response Timer Value” edit button will open a “Slide Bar”, “Cancel” and “Accept” button as
shown in Figure 6.5. This field sets the response timer value in milliseconds for the sensor. The time adjustment
is done by the slide bar (or the directional arrows) and has a range from 10ms to 40ms with a default setting of
10ms. This adjustment is typically used when doing SDK development which may require different poll
response turn around delay times. A “Cancel” or “Accept” button will be available after a change has been
made. Accept will save the change while Cancel will end the task.

Figure 6.5 – Response Timer

The “Sensor Information” will also display:

 Sensor Address (the dip switch address setting on the receiver)


 Alarm Poll Function Type (type of device being polled)
 Electronic Serial Number (the MAC address – for Southwest Microwave use only)
 Hardware Version (hardware version of the MicroWave 330 Receiver)
 Software Version (the version of software operating in the MicroWave 330 Receiver)
 Software Build Date (the date the software was compiled)
 Software Build Time (the time the software was compiled)

6.1.4 Restore Factory Defaults

Selecting the “Restore Factory Defaults” restore button will open a “Cancel” and “Restore” button. Cancel will
end the task and Restore will send a software message command to the MicroWave 330 Receiver to restore all
factory default settings. This function should be done on a new installation to ensure no erroneous data is in the
MicroWave 330 Receiver. This will also erase any alarm history that may be stored in the MicroWave 330
Receiver.

87 Version H
UIST II Manual

6.1.5 Reboot Sensor

Selecting the “Reboot Sensor” reboot button will open a “Cancel” and “Reboot” button. Cancel will end the task
and Reboot will send a software reboot command to the MicroWave 330 Receiver to initiate a reboot of the
sensor in the same manner as if power was removed and restored.

6.2 Sensor Settings


Selecting the “Sensor Settings” tab button will open the sensor configuration settings for MicroWave 330
Receiver as shown in Figure 6.6.

Figure 6.6 – Sensor Settings

6.2.1 Mode

Selecting the “Mode” edit button will open a “Cancel” and “Accept” button as well as a pull down menu as
shown in Figure 6.7. Cancel will end the task and Accept will save the Synchronization setting selected from the
pull down menu. Synchronization eliminates mutual interference between Southwest Microwave sensors.

The available synchronization setting available in the mode are:

 Synchronization “Off” (no other MicroWave 330 Receivers or Model 380 or Model 385 transceiver is
used that will cause potential interference)
 Synchronization “Master” (this receiver is being used with another 330 receiver or 380 or 385
transceiver and is set as the master unit)
 Synchronization “Slave” (this receiver is being used with another 330 receiver or 380 or 385
transceiver and is set as the slave unit)

Note: these units must be wired as described in the MicroWave 330 Manual to operate correctly in the
synchronized mode.

88 Version H
UIST II Manual

Figure 6.7 – Synchronization Mode

If the Synchronization has been set to the “Synchronization Master” or “Synchronization Slave” Mode, the
Phase of the sensor must also be set as shown in Figure 6.8 for the sensors to operate properly. It can be set to:
Phase 0 or Phase 1.

When the synchronization and phase mode are first selected the sensor will go into the alarm state while it re-
establishes the new setting.

Figure 6.8 – Phase Number


89 Version H
UIST II Manual

6.2.2 Channel

Selecting the “Channel” edit button will open a “Cancel” and “Accept” button as well as a pull down menu as
shown in Figure 6.9. Cancel will end the task and Accept will save the Channel Setting selected from the pull
down menu. Available channels are A, B, C, D, E and F. The channel must be set in Un-Tethered or Tethered
mode. In the Un-Tethered mode the Transmitter channel dip switch must be set to match the Receiver channel.

Figure 6.9 – Channel Setting

6.2.3 Tethered

Selecting the “Tethered” edit button will open a “Cancel” and “Accept” button as well as a pull down menu as
shown in Figure 6.10. Cancel will end the task and Accept will save the “Yes” or “No” selected from the pull
down menu.

If “No” is selected the sensor is in Un-Tethered mode. In the Un-Tethered mode the Transmitter Channel dip
switch, SW1, must be set to match the Receiver channel that has been set in software and the Modulation
switch, SW2, set to “Internal”.

If “Yes” is selected the sensor is in the Tethered mode. The Transmitter Modulation switch, SW2, needs to be
set to “External” and the Modulation Input terminals on the Transmitter wired to the Mod Output terminals on
the Receiver. In the Tethered mode the Transmitter tamper terminals can be wired to the Receiver external input
terminals. Reference the MicroWave 330 Manual for correct wiring.

90 Version H
UIST II Manual

Figure 6.10 – Tethered Mode

6.2.4 Recognition Algorithm

Selecting the “Recognition Algorithm” edit button will open a “Cancel” and “Accept” button as well as a pull
down menu as shown in Figure 6.11. Cancel will end the task and Accept will save the algorithm selected from
the pull down menu. The algorithms that can be selected are:

 Off (no digital signal processing algorithms applied)


 Standard (algorithms applied for optimum reliability for industrial applications)
 Enhanced Vehicle (operates with algorithms applied to detect fast moving targets)
 Enhanced Crawl (operates with algorithms applied to detect slow moving targets such as a prone
crawling intruder)
 Maximum Security (operates with algorithms to enhance slow and fast moving targets)

The algorithm selected should be the one that best meets the detection requirements of the facility where the
sensor is being deployed. As always the sensor should be set up to have the best alignment signal, best algorithm
setting and the lowest gain (sensitivity) setting to meet site requirements and keep a low nuisance alarm rate.

As an example, if no prone crawling intruder detection is required and only detection of an upright walking
intruder is required, the algorithm to select would be “Off” or “Standard”. Also the mounting height of the
sensor should comply with the detection that is trying to be achieved as discussed in the MicroWave 330
manual.

91 Version H
UIST II Manual

Figure 6.11 – Recognition Algorithm

6.2.5 FSA

Selecting the “FSA” edit button will open a “Cancel” and “Accept” button as well as a pull down menu as
shown in Figure 6.12. Cancel will end the task and Accept will save the “Yes” or “No” selected from the pull
down menu. FSA is the Fresnel Suppression Algorithms which is unique built-in algorithms to improve
rejection of outer field disturbance detection and enhance operation in challenging applications.

Figure 6.12 – FSA Setting

92 Version H
UIST II Manual

6.2.6 Alarm Hold Time

Selecting the “Alarm Hold Time” edit button will open a “Slide Bar”, “Cancel”, “Accept” and “Default button
as shown in Figure 6.13. Cancel will end the task and Accept will save the time set using the slide bar (from 1 to
60 seconds). Default sets the time to the default value of 5 seconds. This function sets the time duration that an
alarm will be held in the sensor. Once an alarm is declared there is 8 seconds (sensor re-establishment time)
before the alarm hold time takes effect.

Figure 6.13 – Alarm Hold Time Setting

6.2.7 Tamper Trigger

Selecting the “Tamper Trigger” edit button will open a “Selection Table”, “Cancel”, “Accept” and “Default
button as shown in Figure 6.14. Cancel will end the task and Accept will save the selected settings. Default sets
only the Receiver Enclosure as selected. The selectable triggers are:

 Receiver Enclosure (always active as this is the default setting)


 Ext Input/Tamper (any input connected to the Input terminal on the receiver)
 Align/Path Alarm (the alarm received when the alignment signal has changed by the set range)
 Low Voltage (the alarm received when the input voltage is at 11vdc or less)

This is an OR function that allows the selected function to activate. This feature is not typically set in the
receiver as the specific alarm type must be set using one of the controllers.

93 Version H
UIST II Manual

Figure 6.14 – Tamper Trigger

6.3 Alignment
Selecting the “Alignment” tab will open the Alignment and Align/Path Alarm screen for MicroWave 330
Receiver as shown in Figure 6.15. Note: on initial setup the unit will be in Alarm and Align/Path Alarm as no
parameters have been set.

Figure 6.15 – Alignment Tab

The “Alignment” tab will be used to align the MicroWave 330 link and set the voltage for the Align/Path Alarm
function.
94 Version H
UIST II Manual

6.3.1 Start Alignment

Selecting the “Start Alignment” button will open the alignment screen as shown in Figure 6.16. The left side of
the screen shows the Current Alignment voltage and the Max Peak alignment signal. The right side of the screen
shows a graph of voltage and time. Note: in alignment mode the unit will be in alarm.

Figure 6.16 – Alignment Started

Proper alignment of the Microwave 330 link will require two people, one at the transmitter location and the
other at the receiver location. The following steps should be performed to properly align the link:

1. With radomes removed, apply power to the Transmitter and Receiver.

2. Be sure the identical modulation frequency, channel A through F, is being used on the Transmitter and
Receiver in Un-Tethered mode or modulation terminals are connected in Tethered mode.

3. Check for transmitter and receiver operation by monitoring the “POWER” LED on transmitter circuit
board and “PULSE” LED on the receiver board. The LED’s must be illuminated.

4. After checking wire connections and step 2 and 3, replace radome on Transmitter using all six screws.

5. Visually aim the Transmitter and Receiver for “bore-sight” alignment. Aim the transmitter and receiver
at each other. Make sure the transmitter and receiver are parallel and perpendicular to the ground plane
that is being secured.

6. Using the IST II software program monitor the alignment signal while performing steps 7, 8 and 9.
Select the “Clear Max Hold” button to clear the maximum voltage level found from any previous
alignment. The Max Peak is the maximum voltage level that that has been found during the current
alignment process and is shown with a value and a red arrow indicator. The “Current Alignment” is the
current alignment voltage that the link is set to and is shown with a value and a red arrow indicator. The
gray graph on the IST II will also track the alignment signal.

95 Version H
UIST II Manual

7. Swivel Transmitter up and down and side to side, to obtain maximum voltage reading on IST II. Tighten
locking nut on mounting bracket to secure sensor in this position.

8. Raise or lower mounting height of receiver and/or transmitter, as required, to obtain maximum voltage
reading on IST II.

9. Swivel Receiver up and down and side to side, to obtain maximum voltage reading on IST II. Tighten
locking nut on mounting bracket to secure sensor in this position. The minimum alignment voltage for
the MicroWave 330 is 0.5VDC. Although this is the minimum voltage, proper alignment and mounting
height will typically be greater. The Max Peak alignment voltage should range between 0.5 and 3.3
VDC depending upon link distance. The further apart the units the smaller the alignment voltage.

10. Once the alignment process has been completed select the “Stop Alignment” button as shown in Figure
16 to return to the alignment screen as shown in Figure 6.17.

11. Replace Receiver radome using all six screws.

Figure 6.17 – Alignment Stopped

The screen will now display the Current Alignment, the Initial Alignment with the Align/Path Alarm LED and
Alarm LED secured (green) as this has now been set by stopping the alignment. The graph now shows the
Align/Path Alarm, Initial Alignment and Alignment Threshold value.

6.3.2 Align/Path Alarm

The Align/Path Alarm is an alarm indication that the initial alignment voltage has changed. Selecting the
“Alignment Threshold” edit button will open a “Slide Bar”, “Cancel”, “Accept” and “Default button as shown in
Figure 6.18. Cancel will end the task and Accept will save the value set using the slide bar (from 0.1 to 2.0
volts). Default sets back the default value of 0.5 volts. Align/Path Alarms can come from vehicles parked
parallel and in close proximity of the detection field, objects inserted into the detection field, etc. which will
change the alignment. In some cases an Intrusion Alarm will also cause an Align/ Path Alarm. The graph can be
“Paused” or “Cleared” using the buttons on the bottom and the graph speed can also be changed by using the
slide bar on the bottom. The centered black line of the graph will rise or fall depending on the alignment status.
96 Version H
UIST II Manual

Figure 6.18 – Alignment Threshold

Figure 6.19 shows an Align/Path alarm condition. The black line of the graph is into the Alignment Threshold
(shaded) area showing the change in the alignment signal. The Align/Path signal must be beyond the Alignment
Threshold for a minimum of 15 seconds before the Align/Path alarm is declared and LED is illuminated.

Figure 6.19 – Align/Path Alarm

97 Version H
UIST II Manual

6.4 Target
Selecting the “Target” tab will open the detection screen for MicroWave 330 Receiver as shown in Figure 6.20.
This tab will be used to set the gain (sensitivity) of the system, view target signals and view the Threshold to
Noise Ratio for detection requirements.

Figure 6.20 – Target Screen

6.4.1 Gain
Selecting the “Gain” edit button will open a “Slide Bar”, “Cancel”, “Accept” and “Default button as shown in
Figure 6.21. Cancel will end the task and Accept will save the Gain value set using the slide bar (from 0 to 20
dB). Default sets the value to 0 dB.

Figure 6.21 – Gain


98 Version H
UIST II Manual

The “Gain” (sensitivity) should be adjusted to optimize the sensor performance to meet site detection
requirements and be at the lowest setting possible to minimize nuisance alarms. To find this value the link
should be aligned as discussed is section 6.3.1 and the sensor settings configured as discussed in section 6.2.

6.4.2 Threshold to Noise Ratio

The “Threshold to Noise Ratio” bar and number on the Target screen is a dB value showing the ratio between
the noise and signal to the alarm threshold (2 dB) point as shown in Figure 6.21. The best ratio is when the bar is
“Green”.

The bar will turn “Yellow” when the ratio level is between 13dB and 18dB as shown in Figure 6.22. It will turn
“Red” at 12dB. In an alarm condition the bar will be “Red” and at 2dB as shown in Figure 6.27. The target will
also be in the red area of the graph when in alarm.

Figure 6.22 – Threshold to Noise Ratio

6.4.3 Remote Test

In the Tethered Mode a “Remote Test” button is available to turn off the modulation and RF signal at the
transmitter remotely from the IST II as shown in Figure 6.22 “Remote Test On”. Selecting the button will
activate the software command turning off the transmitter as shown in Figure 6.23. Select the “Remote Test
Off” button to turn off the remote test command from the IST II software.

In the Un-Tethered Mode the “Remote Test” button will not be displayed and can not be activated. To perform
the “Remote Test” in the un-tethered mode requires a voltage applied to the remote test terminal of the
transmitter. Reference the MicroWave 330 manual for additional information.

99 Version H
UIST II Manual

Figure 6.23 – Remote Test

6.5 Alarm History


Selecting the “Alarm History” menu will open two (2) options: Erase Alarm History and Retrieve from Device
as shown in the upper left corner of Figure 6.24.

Figure 6.24 – Erase or Retrieve Alarm History


100 Version H
UIST II Manual

6.5.1 Erase Alarm History

Selecting the “Erase Alarm History” menu will erase all alarm activity stored in the MicroWave 330. A dialog
box will open after it has been selected stating “Are you sure you want to erase the Alarm History” with a “Yes”
and “No” button. To erase: select “Yes” and to cancel select “No”.

On a new installation this function should be done before testing the system so only the data from the current
testing is retained in the processor.

On an existing installation this function should be done after the data has been retrieved, evaluated and any
adjustments made from the relevant information.

6.5.2 Retrieve from Device

Selecting the “Retrieve from Device” menu will retrieve all notice, service, path alarm, tamper, external alarms,
low voltage, and alarm activity stored in the MicroWave 330. The alarm buffer in the MicroWave 330 will store
up to 1024 records. When selected a dialog box stating “Retrieving Alarm History” will be displayed as shown
in Figure 6.25. When the download is complete the box will disappear.

Figure 6.25 – Alarm History Retrieve

The alarm history report as shown in Figure 6.26 will display a header with document number, copyright
information, report retrieval time, node address, tag name, mac address, software version (boot and apps) and
hardware version.

The alarm history log format will have an index number (last entry is always on top), entry type (alarm, path
alarm, tamper, external alarm, low voltage, notice and service), date, time and comment. A Jam alarm will be
listed as Microwave Alarm – Jam in the comment field.

101 Version H
UIST II Manual

#57A46512-A01
#******************************************************************************
# Copyright (C) 2012, Southwest Microwave, Inc.
#
# All rights reserved, proprietary and confidential material.
# Unauthorized reproduction, modification or distribution is not permitted.
#******************************************************************************
# MODEL 330 ALARM HISTORY
# Report Retrieved on 2012-11-02 at 12:14:30
#******************************************************************************
# MODEL 330 NODE ADDRESS = 7
# MODEL 330 TAG NAME = MW 330 #7
# MODEL 330 MAC ADDRESS = aa:06:00:29:9c:d0
# MODEL 330 SOFTWARE VERSION = 64A46490-A01 REV 0
# MODEL 330 HARDWARE VERSION = 0x0000
# Date=yyyy-mm-dd, Time=hh:mm:ss (24 hr).
#******************************************************************************
# Alarm History Log Format:
# INDEX, ALARM, DATE, TIME, COMMENT
# INDEX, PALARM, DATE, TIME, COMMENT
# INDEX, RTAMPER, DATE, TIME, COMMENT
# INDEX, EXT ALM, DATE, TIME, COMMENT
# INDEX, LOW VOL, DATE, TIME, COMMENT
# INDEX, NOTICE, DATE, TIME, COMMENT
# INDEX, SERVICE, DATE, TIME, COMMENT
#******************************************************************************
# Alarms in process will be logged after alarm history flash buffer is erased
#******************************************************************************
1, EXT ALM, 2012-11-02, 12:14:10, NO EXT./INPUT TAMPER ALARM
2, EXT ALM, 2012-11-02, 12:14:04, EXT. INPUT/TAMPER ALARM
3, PALARM, 2012-11-02, 12:12:52, NO ALIGN/PATH ALARM
4, ALARM, 2012-11-02, 12:12:51, MICROWAVE ALARM
5, PALARM, 2012-11-02, 12:12:45, ALIGN/PATH ALARM
6, ALARM, 2012-11-02, 12:12:30, MICROWAVE ALARM
7, RTAMPER, 2012-11-02, 12:12:18, NO RECEIVER ENCLOSURE TAMPER
8, RTAMPER, 2012-11-02, 12:12:08, RECEIVER ENCLOSURE TAMPER
9, ALARM, 2012-11-02, 12:11:44, MICROWAVE ALARM
10, SERVICE, 2012-11-02, 12:11:25, UIST II CONNECTED
11, NOTICE, 2012-11-02, 12:11:24, ALM HISTORY ERASED

Figure 6.26 – Alarm History

6.6 Software Setup and Testing


This manual has covered all the parameter settings required for system operation. The next two sections will
cover the software setup steps and testing.

The system should be installed per the MicroWave 330 Installation and Operation manual. All communications
and power wiring should be correctly connected and the proper address for the MicroWave 330 set.

102 Version H
UIST II Manual

6.6.1 Software Setup

The following procedure is a step by step process to setup the MicroWave 330. Start by connecting to the
MicroWave 330 as described in Section 3.1.1 or 3.1.2.

1. Select “Restore Factory Defaults” from the Sensor Information tab (Section 6.1.4).
2. Set the “Sensor ID Tag” from the Sensor Information tab (Section 6.1.1).
3. Set the “Sensor Date/Time” from the Sensor Information tab (Section 6.1.2).
4. Set the “Mode” from the Sensor Settings tab (Section 6.2.1).
5. Set the “Channel” from the Sensor Settings tab (Section 6.2.2).
6. Set the “Tether” from the Sensor Settings tab (Section 6.2.3).
7. Set the “Recognition Algorithm” from the Sensor Settings tab (Section 6.2.4).
8. Set the “FSA” from the Sensor Settings tab (Section 6.2.5).
9. Set the “Alarm Hold Time” from the Sensor Settings tab (Section 6.2.6).

6.6.2 Testing

After steps 1 through 9 have been completed for each MicroWave 330 and aligned, the system is now ready for
functional testing. The functional testing is based on the user’s requirements. Typically this would be walking,
running, jumping and crawling intrusion attempts to generate alarms. The testing person should weight at least
77 pounds (35 kilograms).

Make any adjustments to the system parameters that may be required from the testing results such as Gain
adjustment, Recognition Algorithm and mounting height and retest if necessary.

Monitor the system for at least a week for nuisance and false alarm activity. Retrieve the alarm history and save
(if required), evaluate and make any needed adjustments. Erase the history after evaluation.

Low Security Applications:

Typically low security applications only require detection of walking and running targets. To configure
MicroWave 330 for this type of application:

1. Ensure Channel is set in either Un-Tethered or Tethered Mode as discussed in Section 6.2.2.

2. Mounting height of transmitter and receiver should be 36 inches (.91m) or higher.

3. Set Recognition Algorithm to “Off” or “Standard” as discussed in Section 6.2.4.

4. The FSA can be “On” or “Off” as discussed in Section 6.2.5.

5. Align as discussed in Section 6.3.1.

6. Perform walk tests and run tests at 25 foot (7.62m) intervals between the transmitter and receiver while
monitoring the Target screen for alarms. Adjust the Gain and/or mounting height as required for site
detection requirements.

Medium Security Applications:

Typically medium security applications require detection of walking, running and hands and knees crawling
targets. To configure MicroWave 330 for this type of application:

103 Version H
UIST II Manual

1. Insure Channel is set in either Un-Tethered or Tethered Mode as discussed in Section 6.2.2.

2. Set Recognition Algorithm to “Standard” or “Enhanced Crawl” as discussed in Section 6.2.4.

3. The FSA can be “On” or “Off” as discussed in Section 6.2.5.

4. Align as discussed in Section 6.3.1.

5. Perform walk tests, run tests and hands and knees crawling tests at 20 foot (6.1m) intervals between the
transmitter and receiver while monitoring the Target screen for alarms. Adjust the Gain and/or mounting
height as required for site detection requirements.

High Security Applications:

Typically high security applications require detection of walking, running, jumping and prone (belly) crawling
targets. A 12 inch (30cm) sphere can be used for crawling target simulation. A typical high security zone does
not exceed 328 feet (100m) in distance. Most high security zones will utilize a “Stacked Link” configuration
(refer to MicroWave 330 manual). To configure MicroWave 330 for this type of application:

1. Ensure Channel is set to Tethered Mode as discussed in Section 6.2.2.

2. The nominal starting mounting height for the transmitter and receiver should be 30 inches (762mm).

3. Set Recognition Algorithm to “Maximum Security” as discussed in Section 6.2.4.

4. The FSA can be “On” or “Off” as discussed in Section 6.2.5.

5. Set the “Synchronization” to the correct mode if using a stacked MicroWave 330 configuration.

6. Align as discussed in Section 6.3.1.

7. Perform walk tests, run tests, jump tests and crawling tests at 10 foot (3m) intervals between the
transmitter and receiver while monitoring the Target screen for alarms.

8. Adjust the Gain and/or mounting height of transmitter or receiver as required for site detection
requirements.

For additional information on high security testing, reference Testing Document 702A.

High Speed Applications:

Typically high speed applications require detection of fast moving targets such as vehicles or aircraft. To
configure MicroWave 330 for this type of application:

1. Insure Channel is set to Tethered Mode as discussed in Section 6.2.2.

2. Set Recognition Algorithm to “Enhanced Vehicle” as discussed in Section 6.2.4.

3. The FSA can be “On” or “Off” as discussed in Section 6.2.5.

4. Align as discussed in Section 6.3.1.

104 Version H
UIST II Manual

5. Perform vehicle test at appropriate intervals between the transmitter and receiver while monitoring the
Target screen for alarms. Adjust the Gain and/or mounting height as required for site detection
requirements.

Figure 6.27 shows the Target screen with an alarm condition.

Figure 6.27 – Target Alarm

6.7 Reports
Once a MicroWave 330 has been fully configured and tested, a Configuration Report can be generated that
captures all information and settings of the receiver.

To generate the report, select the “Reports” menu from the menu bar to open the Configuration Report menu as
shown in Figure 6.28.

Figure 6.28 – Configuration Report Menu


105 Version H
UIST II Manual

Selecting the “Configuration Report” will open the “Configuration Report Generator” as shown in Figure 6.29.
This dialog box will show the download process. Once the download is completed the standard Windows dialog
box for saving files will open. Select an appropriate location to save the report. The default report name will be
based on the electronic serial number of the unit along with the date and time the report was generated and will
be in *.PDF format.

Example: MW330-AA-01-00-17-D8-9D-CONFIG-REPORT-2012-09-26-13-45-50.pdf

This file should be saved for future reference and sent to Southwest Microwave prior to any site certification
trips or to assist in any troubleshooting. The report is in English only.

Figure 6.29 – Configuration Report Generator

6.8 General
The pull down list on the menu bar allows changing available languages at any time. The “About” menu
provides information on the Digital MicroWave 330 Service Tool being used.

106 Version H
UIST II Manual

107 Version H

You might also like