This document covers Milestone XProtect Basis+ from a surveillance system administrator’s
perspective. It is solely aimed at XProtect Basis+ system administrators, and administrator rights
are likely to be required in order to be able to access the majority of features described in this
document.
This document provides detailed descriptions of XProtect Basis+ system administration features. It
furthermore provides a large number of targeted “how-to” examples, guiding administrators
through completing common administration tasks in XProtect Basis+.
This document contains very limited end-user related documentation. Administrators requiring
information about end-user related applications, such as the remote access clients, should refer to
the targeted manuals available on the XProtect Basis+ software DVD as well as from
www.milestonesys.com.
Users who do not have surveillance system administrator responsibilities—such as users of the
Viewer, Remote Client or Smart Client—will find that this manual is not of relevance to them. Such
users will be able to find information targeted at their needs in the separate manuals available on
the XProtect Basis+ software DVD as well as from www.milestonesys.com.
XPB+65-AM-3(c1)-301109
www.milestonesys.com Target Audience for this Document
XProtect is a registered trademark of Milestone Systems A/S.
Microsoft
All other trademarks mentioned in this document are trademarks of their respective owners.
Disclaimer
This document is intended for general information purposes only, and due care has been taken in
its preparation.
Any risk arising from the use of this information rests with the recipient, and nothing herein should
be construed as constituting any kind of warranty.
Milestone Systems A/S reserve the right to make adjustments without prior notification.
All names of people and organizations used in this document’s examples are fictitious. Any
resemblance to any actual organization or person, living or dead, is purely coincidental and
unintended.
®
and Windows® are registered trademarks of Microsoft Corporation.
XProtect Basis+ is an essential single-server video system managing up to 25 cameras per server,
including flexible remote access tools. Designed with all the basic features required for small
implementations, it is an inexpensive entry-level product.
Several Targeted Components in One
XProtect Basis+ consists of a number of components, each targeted at specific tasks and user
types:
•The Administrator (see page 26): The main application used by surveillance system
administrators for configuring the XProtect Basis+ surveillance system server, upon
installation or whenever configuration adjustments are required, e.g. when adding new
cameras or users to the system.
•The Recording Server (see page 61): A vital part of the surveillance system; video
streams are only transferred to XProtect Basis+ while the recording server is running. The
recording server is automatically installed as a service (the Milestone Recording Server
service), which will run in the background on the XProtect Basis+ surveillance system
server. You are able to manage the service through the Recording Server Manager.
•The Image Server (see page 109): Handles access to the surveillance system for
remote users logging in with the Remote Client, or Smart Client (see page 140). The Image Server itself does not require separate hardware; it runs as a service on the surveillance
system server. Surveillance system administrators handle Image Server configuration,
including remote users’ access rights, through the Image Server Administrator application.
•The Download Manager (see page 118): Lets surveillance system administrators
manage which XProtect Basis+-related features your organization’s users will be able to
access from a user-targeted welcome page on the surveillance system server.
•The Remote Client and Smart Client (see page 137): Choice of two types of remote
access clients, each providing users with intuitive remote access to the surveillance system.
The Remote Client and Smart Client let users view live video, play back recorded video,
activate outputs, print and export evidence, etc. The Remote Client is accessed straight
from the surveillance system server through an Internet Explorer browser. The extra
feature-rich Smart Client should always be downloaded and installed on remote users’ PCs.
Updates
Milestone Systems regularly release service updates for our products, offering improved
functionality and support for new devices.
If you are an XProtect Basis+ system administrator, it is recommended that you check the
Milestone Systems website www.milestonesys.com for updates at regular intervals in order to
make sure you are using the most recent version of XProtect Basis+.
The following are minimum system requirements for running XProtect Basis+ and associated
applications:
Surveillance System Server
Operating
System
CPU Intel
RAM Minimum 1 GB (2 GB or more recommended).
Network Ethernet (1 Gbit recommended).
Graphics
Adapter
Hard Disk Type E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
Hard Disk
Space
Software DirectX 9.0 or newer required to run Playback Viewer application.
* Running as a 32 bit service/application.
Tip: To check which DirectX version is installed on a computer, click Start, select Run..., and
type dxdiag. When you click OK, the DirectX Diagnostic Tool window will open; version information
is displayed near the bottom of its System tab. If the server requires a DirectX update, the latest
versions of DirectX are available from http://www.microsoft.com/downloads/
Microsoft® Windows® 2008 Server (32 bit or 64 bit*), Windows
Server 2003 (32 bit or 64 bit*), Windows Vista® Business (32 bit or
64 bit*), Windows Vista Enterprise (32 bit or 64 bit*), Windows Vista
Ultimate (32 bit or 64 bit*), Windows XP Professional (32 bit or 64
bit*).
®
Pentium® 4, 2.4 GHz or higher (CoreTM 2 recommended).
AGP or PCI-Express, minimum 1024 x 768, 16 bit colors.
Minimum 80 GB free (depends on number of cameras and recording
settings).
Microsoft .NET 1.1 Framework required to run Recording Server
Manager.
Smart Client
Operating
System
CPU Intel Core2™ Duo, minimum 2.4 GHz or higher.
RAM Minimum 512 MB (1 GB recommended for larger views, 1 GB
Network Ethernet (100 Mbit or higher recommended).
www.milestonesys.com Page 14 Requirements and Prerequisites
Microsoft Windows XP Professional (32 bit or 64 bit*) and Windows
Server 2003 (32 bit or 64 bit*), Windows Vista Business (32 bit or
64 bit*), Windows Vista Enterprise (32 bit or 64 bit*) and Windows
Vista Ultimate (32 bit or 64 bit*).
Software Microsoft .NET 2.0 Framework and DirectX 9.0 or newer.
* Running as a 32 bit service/application.
AGP or PCI-Express, minimum 1024 x 768 (1280 x 1024
recommended), 16 bit colors.
Minimum 100 MB free.
Remote Client
Operating
System
CPU Intel Pentium 4, 2.4 GHz or higher.
RAM Minimum 256 Mbyte (512 MB recommended for larger views, 1 GB
Network Ethernet (100 Mbit or higher recommended).
Microsoft Windows XP Professional (32 bit or 64 bit*) and Windows
Server 2003 (32 bit or 64 bit*), Windows Vista Business (32 bit or
64 bit*), Windows Vista Enterprise (32 bit or 64 bit*) and Windows
Vista Ultimate (32 bit or 64 bit*).
If running Windows Vista, the Remote Client must be added as a
trusted site in your browser.
recommended on Microsoft Windows Vista).
Graphics
Adapter
Hard Disk
Space
Software DirectX 9.0 or newer.
* Running as a 32 bit service/application.
Tip: To check which DirectX version is installed on a computer, click Start, select Run..., and
type dxdiag. When you click OK, the DirectX Diagnostic Tool window will open; version information
is displayed near the bottom of its System tab. If the server requires a DirectX update, the latest
versions of DirectX are available from http://www.microsoft.com/downloads/.
AGP or PCI-Express, minimum 1024 x 768 (1280 x 1024
recommended), 16 bit colors.
Minimum 10 Mbyte free.
Important Port Numbers
XProtect Basis+ uses particular ports when communicating with other computers, cameras, etc.
What is a port? A port is a logical endpoint for data traffic. Networks use different ports for
different types of data traffic. Therefore it is sometimes, but not always, necessary to specify which
port to use for particular data communication. Most ports are used automatically based on the
types of data included in the communication. On TCP/IP networks, port numbers range from 0 to
65536, but only ports 0 to 1024 are reserved for particular purposes. For example, port 80 is used
for HTTP traffic which is used when viewing web pages.
When using XProtect Basis+, make sure that the following ports are open for data traffic on your
network:
www.milestonesys.com Page 15 Requirements and Prerequisites
•Port 20 and 21 (inbound and outbound): Used for FTP traffic. FTP (File Transfer
Protocol) is a standard for exchanging files across networks. FTP uses the TCP/IP standards
for data transfer, and is often used for uploading or downloading files to and from servers.
•Port 25 (inbound and outbound): Used for SMTP traffic. SMTP (Simple Mail Transfer
Protocol) is a standard for sending e-mail messages between servers. This port should be
open since, depending on configuration, some cameras may send images to the
surveillance system server via e-mail.
•Port 80 (inbound and outbound): Used for HTTP traffic between the surveillance server
and cameras, Remote Clients and/or Smart Clients, and the default communication port for
the surveillance system’s Image Server. HTTP (Hypertext Transfer Protocol) is a standard
for exchanging files across networks; widely used for formatting and transmission of data
on the world wide web.
•Port 1024 and above (outbound only): Used for HTTP traffic between cameras and the
surveillance server.
• Any other port numbers you may have selected to use, for example if you have changed
the Image Server’s port from its default port number (80) to another port number.
Tip: Consult the administrator of your organization’s firewall if in doubt about how to open
ports for traffic.
If you wish to install, configure and run XProtect Basis+ on a Windows Vista computer, it is very
important that you have administrator rights. If you only have standard user rights, you will not be
able to configure the software or stop and start the Recording Server service. However, you are
still able to view live and recorded video via the Smart Client.
These restrictions are a part of the User Account Control, a security component in Windows Vista.
Note, however, that it is possible to disable the User Account Control. For more information visit
www.microsoft.com, and search for Vista User Account Control or similar.
Time Server Recommended
All images are time-stamped by XProtect Basis+ upon reception, but since cameras are separate
units which may have separate timing devices, power supplies, etc., camera time and XProtect
Basis+ system time may not correspond fully, and this may occasionally lead to confusion.
If supported by your cameras, we thus recommend you auto-synchronize camera and system time
through a time server for consistent synchronization.
For information about configuring a time server searching www.microsoft.comservice, or similar.
www.milestonesys.com Page 16 Requirements and Prerequisites
This chapter outlines the tasks typically involved in setting up a working XProtect Basis+ system.
The information in this chapter is primarily aimed at system administrators.
Note that although information in this chapter is presented as a checklist, a completed checklist
does not in itself guarantee that the XProtect Basis+ system will match the exact needs of your
organization. To make the system match the needs of your organization, it is highly recommended
that you monitor and adjust the system once it is running.
For example, it is often a very good idea to spend time on testing and adjusting the motion
detection sensitivity settings for individual cameras under different physical conditions (day/night,
windy/calm, etc.) once the system is running. The setup of events and associated actions (see
About Input, Events & Output … on page 73) is another example of configuration which depends
entirely on your organization’s needs.
; You may check the boxes in this checklist as you go along.
Verify Initial Configuration of Devices. Make sure the devices (IP network cameras or
IP video encoders) you are going to use are configured with IP addresses, passwords, etc.
as specified by the manufacturer.
Such initial configuration is required in order to be able to connect the devices to the
network and the XProtect Basis+ solution.
Register software and obtain Device License Keys. You must have a Device License
Key (DLK) for each device (IP network camera or IP video server) to be used with the
XProtect Basis+ solution.
You obtain DLKs as part of the software registration process on the Milestone Systems
website, www.milestonesys.com:
● Click the Software Registration link.
● Log in to the online registration system. If you do not yet have a login, click the New To
The System? link, and follow the instructions. When ready, log in using the registered email address and password. The DLKs will be e-mailed to the e-mail address specified in
your login, so it is a good idea to use a single e-mail account for all persons who should
be able to retrieve DLKs.
● If you have not yet registered your SLC (Software License Code; listed on your product
license sheet), do so by clicking the Add SLC link and completing the SLC registration
steps before proceeding.
● When ready, click the link representing the SLC.
● For each device required on your system, click the Add new MAC link and specify the
device’s MAC address and a description. The MAC address is a 12 digit hexadecimal
(example: 0123456789AF), referred to as a serial number by some vendors. For
information about how to find the MAC address for a specific device, refer to the manual
for the device in question.
● For video encoder devices, specify the number of cameras to be used with the device.
Note that you are allowed to install only the number of cameras listed on your product
license sheet. For example, a fully used four-port video server counts as four cameras
www.milestonesys.com Page 17 Requirements and Prerequisites
even though the cameras are connected through a single device—therefore a fully used
four-port video server will use four licenses.
● Click Submit. The device is added to a list of devices under your SLC.
● If more devices are required, click the Add New MAC link and repeat the process.
● When ready, click the Get DLKs by e-mail link to have DLKs for all the devices
registered under your SLC e-mailed to you.
Install XProtect Basis+ (see Installation on page 20).
Import Device License Keys (see How to Import Device License Keys (DLKs) on page
31).
Add IP Devices (see How to Add a device on page 32). In XProtect Basis+ you do not
have to worry about having to add individual cameras to the system. This is because
cameras area connected to IP devices, so once you have added the required devices to
your XProtect Basis+ system, all cameras connected to the devices are connected to the
system as well.
Configure Cameras on XProtect Basis+. You are able to specify a wide variety of
settings for each camera connected to the XProtect Basis+ system.
Your entry point for configuring cameras is the Administrator window, the main window in
XProtect Basis+’s Administrator application (see page 26).
To configure a camera, first select the required device in the Administrator window’s Device
Manager section, then click the plus sign next to the device to view a list of cameras
attached to the device, as illustrated in the following:
Select the required camera from the list, and click the
Administrator window’s Settings button. This will open the
Camera Settings for [Device Name] [Camera Name] window, in
which you are able to specify settings for the camera in question.
Settings include the highly important motion detection sensitivity
settings. They also include PTZ (Pan/Tilt/Zoom) preset position
settings for any PTZ cameras supporting preset positions. The
Camera Settings for [Device Name] [Camera Name] window is
described in detail on page 39.
Configure XProtect Basis+’s General Settings. The Administrator application’s General
Settings window lets you configure a number of important settings related to user rights,
logging, e-mail and SMS accounts, etc.
The General Settings window is described in detail on page 68.
Configure Scheduling. You may want some cameras to be transferring video to XProtect
Basis+ at all times, whereas you may want other cameras to transfer video only within
specific periods of time, or when specific events occur. With XProtect Basis+’s scheduling
feature, you are able to specify when each camera should transfer video. You are also able
to specify whether alerts should be triggered if motion is detected during specific periods of
time.
For PTZ cameras with patrolling (the automatic movement of a camera between several
preset positions), you are furthermore able to specify whether any specific patrol schemes
should be used during specific periods of time.
www.milestonesys.com Page 18 Requirements and Prerequisites
You configure scheduling in the Administrator application’s Camera/Alert Scheduler
window, described in detail on page 64.
Configure Archiving. By default, video received from cameras is stored by XProtect
Basis+ in a database for each camera. However, the camera databases are each capable of
containing a maximum of 40 GB or 600,000 records before the oldest records are deleted.
By using XProtect Basis+’s archiving feature, you are able to overcome these limitations by
automatically moving the contents of camera databases to specified archiving locations one
or more times every day. With archiving the amount of records you will be able to store will
thus be limited only by your available hardware storage capacity.
By using archiving, you will also be able to back up archived records on backup media of
your choice, using your preferred backup software.
Archiving is described in detail on page 101.
Configure the Image Server. The Image Server is the service handling Remote Client
and Smart Client access to the XProtect Basis+ system.
Remote Clients (see separate manual) and Smart Clients (see separate manual) are
included in your XProtect Basis+ license, and provide flexible, client/server
based, remote access to the XProtect Basis+ system, with viewing live or recordings
from multiple servers simultaneously. If you are going to use Remote Clients or Smart
Clients, configuring the Image Server is a prerequisite. Configuration includes specifying
whether the Image Server should be accessible from the internet, specifying user rights,
etc.
You configure the Image Server through the Image Server Administrator window,
described in detail on page 109.
Configure the Download Manager. The Download Manager lets you manage which
XProtect Basis+-related features your organization’s users will be able to access from a
user-targeted welcome page on the surveillance system server. Such features include the
highly important access clients, additional language versions, etc.
Tip: The Download Manager comes with a default configuration ensuring that users get
access to Smart Clients (see page 140) and Remote Clients (see page 142) on the welcome
page without you having to configure anything.
Read more about the Download Manager, the welcome page, users’ language options, etc.
on page 118.
www.milestonesys.com Page 19 Requirements and Prerequisites
If you wish to install, configure and run XProtect Basis+ on a Windows Vista computer, it is
important that you have administrator rights. If you only have standard user rights, you will not be
able to configure the software.
These restrictions are a part of the User Account Control, a security component in Windows Vista.
Note, however, that it is possible to disable the User Account Control. For more information, search
www.microsoft.com for Vista User Account Control or similar
Installing the Server Software
If upgrading from a previous version, make sure you read the upgrade information on
page 21 before you begin upgrading.
Note: Do not install XProtect Basis+ on a mounted drive (i.e. a drive attached to an empty folder
on an NTFS (NT File System) volume, with a label or name instead of a drive letter). If using
mounted drives, critical system features may not work as intended; you will, for example, not
receive any warnings if the system runs out of disk space.
Prerequisites: Shut down any existing Milestone software.
1. Insert the XProtect Basis+ software DVD, wait for a short while, select required language,
then click the Milestone XProtect Basis+ installation link.
Alternatively, if you are installing a version downloaded from the internet, run the
downloaded installation file from the location you have saved it to.
Tip: Depending on your security settings, you may receive one or more security
warnings (Do you want to run or save this file?Do you want to run this software? or
similar). When this is the case, click the Run button.
2. When the installation wizard starts, click Next to continue.
3. Read and accept the End User License Agreement, then click Next.
4. If an earlier XProtect Basis+ version (6.0a or later) is present on the server, you will be
asked to accept that it is automatically removed during installation of the new version. The
automatic removal will not delete any existing recordings or configuration. If asked, we
recommend answering Yes, since this will ensure that old versions will not interfere with
your new version. XProtect Basis+ versions earlier than 6.0 must be removed manually
before installing the new version, see Upgrading from a Previous Version on page 21.
5. Select Typical installation (advanced users can select Custom installation, and choose which
features to install and where to install them).
6. Select the Install licensed Version option, and specify your user name, organization, and
Software License Code (SLC; printed on your Product License Sheet). When ready, click
Next.
7. Click the Install button to begin the software installation. During the process, all the
necessary components will be installed one after the other.
● XProtect Basis+’s Administrator window may appear on your screen during
installation. When this is the case, the window will automatically close again after a
short while.
●If a Status Information window appears on your screen during installation, click its
OK button (the window simply provides a summary of your installation).
8. Click Finish on the last step to complete the installation.
When installation is complete, you can begin configuring your XProtect Basis+ solution: Doubleclick the Administrator desktop shortcut or select Start > All Programs > Milestone XProtect Basis+
> Administrator to open the Administrator window.
Tip: If you want to make additional language versions of the Smart Client and Remote Client
(such as Spanish, French, or Japanese versions) available to your organization’s users, you can
quickly do this once you have installed XProtect Basis+. See more in the description of the
Download Manager on page 118.
Upgrading from a Previous Version
Upgrading XProtect Basis+ is an easy task, and you need not worry about spending hours
reconfiguring your software.
The following information applies if upgrading from one XProtect Basis+ version to another as well
as if upgrading to XProtect Basis+ from a lower product in the XProtect product portfolio.
Prerequisites
• Take note of your SLC (Software License Code). The SLC will change when the software
version number changes.
• If your SLC has changed, so have your DLKs (Device License Keys). Go to the Milestone
website, www.milestonesys.com
Under the properties for your license, click the Get DLKs by e-mail link. When you receive
the .dlk file, save it on the computer running the XProtect Basis+ server.
• If you do not already have the new XProtect Basis+ new, go to www.milestonesys.com,
and download the most current version which you are allowed to install with your SLC.
Backing Up Your Current Configuration
It is generally a good idea to make regular backups of your server configuration as a disaster
recovery measure. Upgrading your server is no exception. While it is rare to lose your configuration
(cameras, schedules, views, etc), it can happen under certain circumstances. Luckily, it takes only
a minute to back up your existing configuration:
1. Create a folder called Backup on the desktop of your XProtect Basis+ server, on a network
drive, or on removable media.
2. Open My Computer, and navigate to C:\Program Files\Milestone\Milestone Surveillance.
, and log in to the Software Registration Service Center.
3. Copy the following files and folders into your Backup folder:
• All configuration (.ini) files
• All scheduling (.sch) files
• The file users.txt (not found in most installations)
• The folder SmartClientViewGroups and all of its content
• The folder RemoteClientViewGroups and all of its content
Note that some of the folders may not exist if upgrading from old software versions.
Removing the Current Version
XProtect Basis+ versions 6.0a or later can automatically be removed during installation of the new
version. When installing the new version, simply answer Yes if asked if you accept such automatic
removal. The automatic removal will not delete any existing recordings or configuration.
XProtect Basis+ versions older than 6.0 as well as lower products in the XProtect product portfolio
must be removed manually before installing the new version. Manually removing the old version
involves removing two components on the server. Removing these components will not remove
your configuration files.
1. From Windows’ Start menu, select Control Panel > Add or Remove Programs.
2. Remove Milestone XProtect Basis+ (or the lower XProtect product).
3. When asked if you want to remove database files or registry settings, you should normally
not select any of the check boxes.
You may choose to remove database files if you wish, but removing registry settings may
mean that the new software version will not be able to utilize the existing configuration.
4. Remove Video Device Driver/Pack Vx.x (where x.x refers to the version number).
Installing the New Version
Once the old version of the software is removed, you can run the installation file for the new
software version. Select the installation options that best fit your needs.
There are some recent software changes that you should be aware of:
• It is now possible to install the software as a service, and as of XProtect Basis+ 6.5 this is
the only option since the Monitor application has been discontinued. When the software
runs as a service, the Recording Server runs as a background process, and any viewing
either locally or remotely will be done through either a Smart Client (see page 140), or
through a Remote Client (see page 142)
• The HTTP Server/Realtime Feed Server (very basic alternative to the Smart Client/Remote
Client) can only be used when the software is installed as an application. Since installing as
an application is no longer possible in current XProtect Basis+ versions, the HTTP Server
and Realtime Feed Server have been discontinued. Use the much superior Smart Client or
Remote Client instead.
•XProtect Basis+’s Administrator window (see page 26) may appear on your screen during
installation. When this is the case, the window will automatically close again after a short
while.
• In the most recent software version, a Download Manager (see page 118) is introduced,
and you will have the option of opening the Download Manager during installation. The
Download Manager is used for managing which features your organization’s users will be
able to access from a targeted welcome page on the surveillance system server. You can
open the Download Manager if you like, but you can just as easily make changes through
the Download Manager once installation is completed.
Restoring a Configuration Backup (if Required)
If for some reason after installing the new software version you have lost your old configuration,
you can easily restore your configuration, provided you have created a backup of your
configuration prior to upgrading the software:
1. Drag and drop the backed-up configuration files and folders into the new installation
directory, which by default is still C:\Program Files\Milestone\Milestone Surveillance\.
2. When asked if you wish to overwrite the existing files, cli ck Yes.
3. Restart your server.
Updating Video Device Drivers
Video device drivers are small programs used for controlling/communicating with the camera
devices connected to an XProtect Basis+ system.
Video device drivers are installed automatically during the initial installation of your XProtect
Basis+ system. However, new versions of the video device drivers, so-called Device Packs, are
released and made available for free on the Milestone website from time to time.
We therefore recommend that you visit the Milestone website (www.milestonesys.comSupport > Downloads) and download the latest Device Pack.
; look under
Upgrading Smart Clients
Smart Client users should now remove their old Smart Client versions and install the new one:
1. On the required computers, open Windows’ Add or Remove Programs dialog (Start >
Control Panel > Add or Remove Programs).
2. In the Add or Remove Programs dialog, select the Milestone XProtect Smart Client entry,
and click the Remove button. A wizard window will open. Follow the wizard’s steps, and
click Finish when ready.
3. Now open a browser and connect to XProtect Basis+ at the following address:
http://[IP address or hostname of server]:[Image Server port number; default is 80]
Example: http://123.123.123.123:80
4. From the welcome page that appears, download and install the latest Smart Client version.
5. If required, download and install any Smart Client plugins needed.
To use XProtect Basis+’s built-in help system, simply press the F1 key on your keyboard
whenever you are working with the Administrator application or Image Server Administrator.
When you press F1, the help system will open in a separate window, allowing you to easily switch
between help and XProtect Basis+ itself.
The help system is context sensitive. This means that when you press F1 for help while working in
a particular window or with a particular task, the help system automatically displays the help topic
describing that window or task.
Navigating the Built-in Help System
Even though the help system initially takes you to a topic describing the window you are working
in, you are always able to freely navigate between the help system’s contents. To do this, simply
use the help window’s three tabs, Contents, Search and Glossary, or use the links inside the help
topics.
Contents Tab
The Contents tab lets you navigate the help system based on a
tree structure. Many users will be familiar with this type of
navigation from, for example, Windows Explorer.
Search Tab
The Search tab lets you search for help topics containing particular
terms of interest. For example, you can search for the term zoom,
and every help topic containing the term zoom will be listed in the
search results. Clicking a help topic title in the search results list
will open the required topic.
The Search tab contains a number of advanced search features;
among these are the ability to quickly run previous searches, the
ability to search topic titles only as well as the ability to display
search results ranked according to presumed relevance.
Glossary Tab
What do abbreviations such as DLK, PTZ or VMD stand for? The Glossary tab in the help window’s
navigation pane provides a glossary of common surveillance and network-related terms. Simply
select a term to view a corresponding definition in the small window below the list of terms.
Links in Help Topics
The actual content of each help topic is displayed in the right pane of the help window. Help topic
texts may contain various types of links, notably so-called expanding drop-down links.
www.milestonesys.com Page 24 Using the Built-in Help System
Clicking an expanding drop-down link will display detailed information. The detailed information will
be displayed immediately below the link itself; the content on the page simply expands. Expanding
drop-down links thus help save space.
Tip: If you wish to quickly collapse all texts from expanding drop-down links in a help topic,
simply click the title of the topic on the help system’s Contents tab.
Printing Help Topics
To print a help topic, navigate to the required topic and click the help window’s Print button.
When you click the Print button, a dialog box may ask you whether you wish to print the selected
topic only or all topics under the selected heading. When this is the case, select Print the selected topic and click OK.
When printing a selected help topic, the topic will be printed as you see it on your screen.
Therefore, if a topic contains expanding drop-down links (see Links in Help Topics in the previous),
click each required drop-down link to display the text in order for it to be included in your printout.
This allows you to create targeted printouts, containing exactly the amount of information you
require.
www.milestonesys.com Page 25 Using the Built-in Help System
For users without administrator rights, access to certain features in
XProtect Basis+ may in some organizations have been restricted. When
this is the case, you will be asked to specify the administrator password
in the Administrator Login window in order to get access to the restricted
features.
You will only be asked to specify the administrator password when you open the Administrator
application, by selecting it from Windows’ Start menu or by clicking the Administrator shortcut on
the desktop. This will only be the case when access to the Administrator application has been
password-protected.
Administrator Window
The Administrator window, the main window in the Administrator application, is used by the
surveillance system administrator for configuring XProtect Basis+ upon installation or whenever
configuration adjustments are required, e.g. when adding new cameras to the system.
You access the Administrator application by selecting it from Window’s Start
menu or by clicking the Administrator shortcut on the desktop. Access to
the Administrator application may be password protected, in which case you
will be asked to provide the administrator password in the Administrator Login window (see above).
IMPORTANT: Changes you make in the Administrator application are not applied on your
surveillance system until you exit the Administrator application. This allows you to try out various
settings before making them take effect.
Tip: Clicking the icon in the left corner of the Administrator window’s title bar, gives you access
to a small menu. Selecting About Adm ... from the menu will display a dialog with your system’s
version number and Software License Code. This is valuable information, should you ever need to
contact product support.
Administrator
desktop shortcut
Device Manager Section
The Device Manager section—located in the middle of the Administrator
window—lists all added devices with attached cameras and microphones.
The Device Manager section thus provides you with an overview of your
surveillance system.
Until you have added devices, the Device Manager section will be empty.
The illustration to the right shows a detail from the Administrator window’s
Device Manager section—two devices have been added; the first device
has a single camera attached, whereas the second device has four
cameras attached.
You add devices through an intuitive Device Setup Wizard, available by clicking the Administrator
window’s Add Device button (see also How to Add a Device on page 32). When devices have been
added, they will be listed in the Device Manager section. Clicking the plus sign
the Device Manager section will list cameras attached to the device.
next to a device in
Editing Settings for Devices
To edit settings for a device listed in the Device Manager section, select the device, then click the
Edit device... button to open the Edit device settings window (see page 34).
Editing Settings for Cameras
To edit the settings for a camera listed in the Device Manager section,
click the plus sign
attached, select the required camera, then click the Settings button to
open the Camera Settings for [Device name] [Camera Name] window
(see page 39).
Renaming Cameras
next to the device to which the camera is
To rename a camera, right-click the camera name in question, then sele
Edit from the menu that appears. This will open the Camera Name and Number window (see page 57), in which you are able to overwri
existing camera name with a new one.
te the
ct
Assigning Shortcut Numbers to Cameras
Users of the Smart Client (see page 140) can take advantage of a range of keyboard shortcuts,
some of which let the users toggle between viewing different cameras. Such keyboard shortcuts
include number
ach camera.
e
To assign a shortcut number to a camera, right-click the camera name in
question, then select Edit from the menu that appears. This will open the
Camera Name and Number window (see page 57), in whic
specify a shortcut number to be used with the camera
to
Note: Camera shortcut numbers are only used in the Smart Client (see page 140). In other
applications, such as the Remote Client (see page 142), the camera shortcuts cannot be used.
Tip: More information about using the keyboard shortcuts is available in the documentation for
the Smart Client.
s, which are used to identify each camera. Shortcut numbers must be unique for
h you are able
.
Editing Settings for Audio Sources
To edit the settings for an audio source (that is a microphone) listed in the Device Manager sect
click the plus sign next to the device to which the audio source is attached, select the required
source, and then click the Settings button to open the Microphone Settings window (see page
audio
9).
5
IMPORTANT: The use of microphones will impact the database capacity for storing video; see
Important Information (on page 59) about Using Audio for more information.
ion,
Disabling/Enabling Cameras and Audio Sources
Individual cameras and audio sources listed in the Device Manager section are by default disabled,
meaning that video from cameras and audio from attached microphones is by default transferred t
XProtect Basis+—provided that the cameras are marked as online in the Camera/Alert Scheduler
Window (also default) – see page 64 .
Note: On some devices, audio can also be enabled/disabled on the device itself, typically through
the device’s own configuration web page. If audio on a device does not work after enabling it in the
Administrator application, you should thus verify whether the problem may be due to audio being
disabled on the device itself.
If required, you can disable individual cameras and audio sources lis
ted
in the Device Manager section. When a camera or audio source is
disabled, no video/audio will be transferred from the camera/audio
source to XProtect Ba
ick the required camera or audio source in the Device Manager section,
cl
sis+. To disable a camera or audio source, rightthen select Disable.
When a camera or audio source is disabled, it will be indicated as follows:
To enable a previously disabled camera or audio source, simply right-click the required camera or
audio source in the Device Manager section, then select Enable:
Tip: Individual cameras can also be disabled/enabled in the Camera Settings for [Device Name]
[Camera Name] Window (see page 39). Individual audio sources can also be disabled/enabled in the Microphone Settings window (see page 59).
Administrator Window’s Buttons
Button Description
Service Opens the Service Manager window (see page 63), which lets you
pause/resume the MilestonManager... e Recording Server service. Pausing the service is
necessary in order to access some features, for example configuration of PTZ
(Pan/Tilt/Zoom) cameras.
IMPORTANT: While the service is paused, no video or audio will be recorded.
Scheduler... Opens the Camera/Alert Scheduler window (see page 64), in which you
specify online periods for each camera.
You are also able to specify if cameras should go online when specific events
occur (e.g. when a door is opened), and if e-mail or sound alerts should be
used if motion is detected during specific periods of time (e.g. during working
hours).
Tip: By default, all cameras are online at all times. You will only need to
modify scheduler settings if you require cameras to be online only at specific
times or events.
General Opens the General Settings window (see page 68), in which you are able to
specify a number of settings relaSettings... ted to:
Archive Opens the Archive setup window (see page 105), in which you specify
Setup...
Import Lets you import all required Device License Keys (DLKs) in one go, thus
XProtect Basis+’s archiving settings.
Archiving lets you keep recordings for
available hardware storage capacity.
avoiding the need to specify each DLK manually whenDLKs... adding devices. See
also How to Import Device License Keys on page 31.
as long as required, limited only be the
Transact... Note: The Transact button is not functional. If Milestone XProtect Transact
(add-on product for handling loss prevention through video evidence
combined with time-linked POS or ATM transaction data) is installed on the
server, use Windows’ Start menu or the Transact Administrator desktop
shortcut to access the Transact Administrator. Use with Milestone XProtect
Transact versions earlier than 2.1 is not supported.
Add Starts the Device Setup Wizard, which guides you through the process of
Device... adding a new device. See also How to Add a Device on page 32.
Edit When you have selected a device in the Administrator window’s Device
Manager section, clicking the Edit Device... button lets you edit settingDevice... s for
the selected device in the Edit device settings window (see page 34).
Remove Lets you remove a device selected in the Administrator window’s Device
Manager section. In order to prevent accidental removal oDevice f devices, you will
be asked to confirm that you want to remove the device.
Settings... Lets you specify settings for a selected camera or audio source:
•Cameras: When you have selected a camera in the Administrator
window’s Device Manager section, clicking the Settings button will
open the Camera Settings for [Device Name] [Camera Name]...
window (see page 39), in which you specify camera settings.
•Audio sources: When you have selected a microphone or a speaker in
the Administrator window’s Device Manager section, clicking the
Settings button will open the Microphone Settings window (see page
59), in which you can enable/disable the microphone and change its
name if required.
I/O Setup... Opens the I/O Setup window (see page 74), in which you are able to define
events based on input events (for example when a door sensor detects that a
door is opened) and VMD (Video Motion Detection). The I/O Setup window
also lets you specify output (e.g. a siren).
When defined, events can be used for a variety of purposes. For example, an
input event can be used for triggering output, for starting a particular camera,
and for triggering that an e-mail message is sent to a particular user, notifying
the user of the recorded event. See also the description of the I/O Control...
button below.
Event Opens the Event Buttons window (see page 85), in which you are able to
Buttons... define events for use on event buttons. Event buttons can be used in the
Smart Client for manually triggering events.
I/O Opens the I/O Control window (see page 88) where you are able to attach
Control... outputs to input events. This way you can, for example, define that a siren
should sound when a sensor detects that a door is opened.
Exit Closes the Administrator application.
Tip: Clicking the icon in the left corner of the Administrator window’s title bar, gives you acce
to a small menu. Selecting
ersion number and software license code; this is valuable information, should you ever need to
v
contact product support.
About Adm ... from the menu will display a dialog with your system’s
You must have a Device License Key (DLK) for every device (IP network camera or IP video server)
installed on your XProtect Basis+ surveillance system.
Remember that you are allowed to install and use only the number of cameras listed on your
organization’s license sheet; regardless of you number of available DLKs. For example, a fully used
four-port video encoder counts as four cameras even though the cameras are connected through a
single device—therefore a fully used four-port video encoder will use four licenses.
System administrators obtain DLKs as part of the software registration process on the Milestone
website, www.milestonesys.com. Upon registration, DLKs are sent to system administrators via email.
You are able to specify each DLK manually when adding a device (see page 32) through the Device Setup Wizard, available by clicking the Add Device... button in the Administrator window (see page
26). However, you can avoid having to specify each DLK manually by using the following procedure
to import all received DLKs into XProtect Basis+ in one go:
Prerequisites: The DLKs, received in a .dlk file, must have been saved at a location accessible by
the surveillance server, for example on a network drive or on a USB stick.
1. Open the Administrator window (see page 26).
2. In the Administrator window, click the Import DLKs... button.Browse to the location at
which you have saved the received .dlk file.
3. Select the file, and click Open. All DLKs are now automatically imported, and the relevant
DLK will automatically appear when you add a device through the Device Setup Wizard.
In XProtect Basis+ you add devices (IP video camera devices, IP video encoder devices) rather
than actual cameras. This is because devices have their own IP addresses or host names. Being IPbased, XProtect Basis+ primarily identifies units on the surveillance system based on their IP
addresses or host names.
You are able to add up to 25 cameras. If using video encoder devices on your system, bear in mind
that many video encoder devices can have more than one camera connected to them. For
example, a fully used four-port video encoder will count as four cameras.
Even though each device has its own IP address or host name, several cameras can be attached to
a single device and thus share the same IP address or host name. This is typically the case with
cameras attached to video encoder devices. You can of course configure and use each camera
individually, even when several cameras are attached to a single device.
When such I/O devices are added, they can be used in events-based system setup in the same way
as a camera. For more information about using I/O devices, see Using Dedicated I/O Devices on
page 74. For information about which I/O devices are supported, refer to the release note.
Once a device is added in XProtect Basis+, any cameras attached to the device are automatically
recognized by the software, and listed in the Administrator window's Device Manager section.
The illustration to the right shows a detail from the Administrator window’s
Device Manager section—two devices have been added; the first device
has a single camera attached, whereas the second device has four
cameras attached.
To add a device, use the following procedure:
Prerequisites: You must have configured IP address, password, etc. on
the device itself, as described by the manufacturer.
1. Open the Administrator window (see page 26).
2. In the Administrator window, click the Add Device... button. This will start the Device Setup Wizard.
3. On the first step of the wizard, identify the required device, ei ther by
• Typing the IP address of the device (to jump to the next IP address segment in the
field, press SPACE on your keyboard).
- or -
•Typing the DNS host name of the device. This requires that you select the Use
DNS host names box
www.milestonesys.com Page 32 Camera Administration
Note: By default, HTTP port 80 and FTP port 21 will be used for the device. If the device
you are adding uses other port numbers, click the Port Setup button and speci fy required
port numbers. The need for specifying different ports may often apply if the device is
located behind a NAT-enabled router or a firewall. When this is the case, also remember to
configure the router/firewall so it maps the ports and IP address used by the device.
When ready, click Next to go to the second step of the wizard.
4. If a password is used for the device, type the password for the device’s administrator
account (called the “admin” or “root” account on some devices). Leave the Autodetect Device option selected. Then click Next.
Tip: If you are in doubt about which administrator account to use for a device, look in
the Device Pack Release Notes, available from the Downloads section of the Milestone
website, www.milestonesys.com.
5. When the device has been detected, type the
Device License Key (DLK) for the device in the
DLK field.
Tip: If you have imported DLKs (see How
to Import Device License Keys on page 31),
the DLK field will already be filled with the DLK
for the device.
Click Next.
6. Assign a unique and descriptive name to the
device.
Upon completion of the wizard, the name will
be used when listing devices and associated
cameras in the Administrator window’s Device Manager section. The name may, for example,
refer to the physical location of the camera(s)
attached to the device.
Tip: You may click the Camera Setup button to access the Camera Settings for [Device
Name] window (see page 36), in which you are able to specify certain settings related to
camera name and PTZ control. The latter requires that the camera is a PTZ (Pan/tilt/Zoom)
camera.
7. Click Finish.
8. The device will be listed in the Administrator window’s Device Manager section. To view a
list of cameras attached to the device, click the plus sign
next to the device name.
www.milestonesys.com Page 33 Camera Administration
Tip: In the Administrator application’s Device Manager section (the white area in the
middle of the window), cameras are listed for each device with default names, such as
Camera 1, etc. If you want to change the name of a camera, click the plus sign next to the
required device, right-click the camera name in question, then select Edit from the menu
that appears.
Tip: Individual cameras listed in the Device Manager section are by default enabled,
meaning that video from the cameras is by default transferred to XProtect Basis+—
provided that the cameras are marked as online in the Camera/Alert Scheduler Window
(also default) – see page 64. If required, you can disable a camera listed in the Device Manager section by right-clicking the name of the camera in question. See more
information under Administrator window (see page 26).
Edit Device Settings Window
The Edit device settings window lets you edit the settings of an
already installed device.
To access the Edit device settings window (see page 34), select the
required device in the Administrator window’s (see page 26) Device Manager section, and click the Edit Device... button.
The Edit device settings window is divided into two sections:
Identify Video Device Section
The Identify Video Device section contains the following fields,
buttons, etc.:
Field,
Button, ...
Device Type Select required device type from list. XProtect Basis+ is able to automatically
Detect
Device
Device
Name
Description
detect device type as well as serial number, provided the IP
address/hostname and password of the device have been specified in the IP-
address/DNS Host Name and Root Password fields: Simply click the Detect
Device button to auto-detect device type and serial number.
Click button to auto-detect device type and serial number.
Note: Use of the auto-detect feature requires that the IP address and
password of the device have been specified in the IP-address and Root Password fields.
Name used to identify the device. To enable easy identification of devices, it is
often a good idea to use a device name that refers to the physical area
covered by the cameras attached to the device (examples: Reception Area,
Car Park B, ...).
Note: Device names must be unique; you cannot use the same name for
several devices.
www.milestonesys.com Page 34 Camera Administration
Opens the Camera Settings for [Device Name] window (see page 36), in which
you are able to specify a number of settings for cameras attached to the
device, including:
• Port through which PTZ (Pan/Tilt/Zoom) cameras are controlled
• Camera names, types, and ports
Note: The number of settings available in the Camera Settings for [Device
Name] window (see page 36) may be limited if cameras are not PTZ cameras
or connected to a video encoder device.
Device
Serial
Number
Device
License Key
Enable iPIX Enables the use of IPIX, a technology that allows viewing of 360-degree
Serial number of device; usually identical to the 12-character MAC address of
the device (example: 0123456789AF).
Tip: XProtect Basis+ is able to automatically detect serial number as well
as device type, provided the IP address/host name and password of the device
have been specified in the IP-address/DNS Host Name and Root Password
fields: Simply click the Detect Device button to auto-detect device type and
serial number.
A 16-character license key (DLK) for the device, obtained when registering the
software.
panoramic images.
Note: Use of the IPIX technology requires either a dedicated IPIX camera or a
regular camera equipped with a special IPIX camera lens for which a special
IPIX license key is required. If the device in question is for a dedicated IPIX
camera, the check box is selected by default, and you do not have to enter an
IPIX license key in the neighboring field.
iPIX License
Key
License key for using the IPIX technology, obtained when registering the
software.
Note: This information is only required if the Enable iPIX check box is selected
manually.
Network Settings for Video Device Section
The Network Settings for Video Device section contains the following fields:
Field Description
IP-address
-or-
DNS Host
Name
www.milestonesys.com Page 35 Camera Administration
IP address or DNS host name of the device in question.
Note: If Use DNS host name check box is selected, the name of the IPaddress field changes to DNS/Host Name in order to accommodate a DNS host
By selecting the check box you are able to use a DNS host name for
identifying the device instead of using the device’s IP address. When check
box is selected, the IP-address field changes its name to DNS/Host Name,
ready to accommodate a DNS host name rather than an IP address.
When selected, HTTP traffic to the device will go through the default port, port
80. If you want to use another port for HTTP traffic to the device, clear the
check box, and specify required port number in the field to the left of the
check box.
When selected, FTP traffic to the device will go through the default port, port
21. If you want to use another port for FTP traffic to the device, clear the
check box, and specify required port number in the field to the left of the
check box.
Password required in order to log in to the device using the root account
(occasionally known as an admin or administrator account).
Camera Settings for [Device Name] Window
Note: The number of settings available in the Camera Settings for [Device Name] window may be
limited if cameras are not PTZ (Pan/Tilt/Zoom) cameras or connected to a video encoder device.
The Camera Settings for [Device Name] window lets
you specify certain information about a device’s
cameras. This is primarily interesting for PTZ
cameras and cameras attached to a video encoder
device. You access the Camera Settings for [Device Name] window by clicking the Camera Settings...
button in the Edit device settings window (see page
34). The Camera Settings for [Device Name] window
is divided into a P/T/Z Camera Selection section and
a camera list:
P/T/Z Camera Selection
Section
Field Description
Some of the
connected
cameras are
Pan/Tilt/Zoom
cameras
P/T/Z type
controlled
through COM1
www.milestonesys.com Page 36 Camera Administration
Select check box if any of the cameras attached to the video encoder
device is a PTZ camera.
If the check box is not available, PTZ is not supported for the device in
question.
Field available only if Some of the connected cameras are Pan/Tilt/Zoom
cameras check box is selected. If a PTZ camera is controlled through the
COM1 port on the video encoder device, select the required PTZ camera
type from the list. If no PTZ cameras are controlled through the COM1 port,
select None.
P/T/Z type
controlled
through COM2
Field available only if Some of the connected cameras are Pan/Tilt/Zoom
cameras check box is selected. If a PTZ camera is controlled through the
COM2 port on the video encoder device, select the required PTZ camera
type from the list. If no PTZ cameras are controlled through the COM2 port,
select None.
Camera List and Fields
The camera list contains a line for each camera channel on the device. First line from the top
corresponds to camera channel 1, second line from the top corresponds to camera channel 2, etc.
To change camera settings, select the required camera channel from the list, specify required
information in the following fields, and click the Apply button:
Field Description
Camera
Name
Cam
Number
Name used to identify the selected camera. Existing names, such as the
default camera names Camera 1, Camera 2, etc. can be changed by
overwriting the existing names.
Note: Camera names must be unique for each device.
Users of the Smart Client can take advantage of a range of keyboard
shortcuts, some of which let the users toggle between viewing different
cameras. Such shortcuts include numbers, which are used to identify each
camera.
Camera shortcut numbers must be unique for each camera, must not contain
any letters or special characters, and must be no longer than eight digits.
Examples of correct camera shortcut numbers: 3, 12345678. Examples of
incorrect camera shortcut numbers: A*3, 123456789.
Note: Camera shortcut numbers are only used in the Smart Client. In other
applications, such as the Remote Client, the camera shortcuts cannot be used.
Tip: You can also assign shortcut numbers to cameras in the Camera
Name and Number window (see page 57).
Tip: More information about using the keyboard shortcuts is available in
the separate Smart Client documentation.
Camera
Type
Lets you select whether the camera on the selected camera channel is Fixed
or Moveable:
• Fixed: Camera mounted in a fixed position
• Moveable: PTZ camera
www.milestonesys.com Page 37 Camera Administration
Device Port Available only if Moveable is selected in the Camera Type field.
Lets you select which control port on the video encoder should be used for
controlling PTZ functionality on the camera.
Port
Address
Available only if Moveable is selected in the Camera Type field.
Lets you specify port address of the camera. The port address would normally
be 0 or 1. If using daisy chained PTZ cameras, the port address will identify
each of them, and you should verify your settings with those recommended in
the cameras’ manuals.
www.milestonesys.com Page 38 Camera Administration
In XProtect Basis+ you do not have to worry about having to add individual cameras to the
system: Cameras are connected to devices, so once you have added the required devices to your
XProtect Basis+ system (see How to Add a Device on page 32), all cameras connected to the
devices are connected to the system as well.
You are able to specify a wide variety of settings for each camera connected to the XProtect Basis+
system. Your entry point for such camera configuration is the Administrator window (see page 26).
To configure a camera, select the required camera in the Administrator window’s Device Manager
section, then click the Administrator window’s Settings... button. This will open the Camera Settings for [Device Name] [Camera Name] window (see below), in which you have access to
settings for the camera in question, including:
• How the camera should record (frame rate, image quality, etc.)
• Where and when to store recorded video from the camera
• Motion detection sensitivity
• Triggering of notifications and external output
• ... and more
This also applies if you want to edit the settings for an already configured camera.
Camera Settings for [Device Name] [Camera
Name] Window
The Camera Settings for [Device Name] [Camera Name] window lets you specify settings for a
particular camera.
You access the Camera Settings for [Device Name] [Camera Name] window (see page 39) from
the Administrator window (see page 26), by selecting a camera in the Device Manager section,
then clicking the Settings... button.
The window contains the following sections and buttons:
Speedup Settings
The Speedup Settings section lets you specify the required number of frames to be used when
motion is detected and/or an event occurs in this field.
•Required framerate: Specify required number of frames in the first field, and select
required unit (per Second, per Minute, or per Hour) from the list. The frame rate must be
higher than the frame rate specified in the Required framerate field in the Recording settings section which is described in the following.
www.milestonesys.com Page 39 Camera Administration
Tip: When you specify a frame rate, the interval between images is automatically calculated
and displayed to the right of the frame rate fields.
Specifically for cameras using MPEG: For MPEG cameras you can select predefined frame rates, and
it is not possible to select unit. The number of seconds between each image is still calculated.
Recording Settings
The Recording Settings section lets you specify the camera’s recording settings in the following
fields:
•Required framerate: Specify required number of frames in the first field, and select
required unit (per Second, per Minute, or per Hour) from the list. When you specify a frame
rate, the interval between images is automatically calculated and displayed to the right of
the frame rate fields.
Specifically for Cameras Using MPEG: Instead of selecting required frame rate, you are able
to select a Frame Type. Select All to record everything; that is similar to having the same
frame rate for speedup and for recording. Select Key frame if you wish only to record key
frames and ignore changes between the key frames; that means that you typically record
one frame per second.
•Enable speedup: XProtect Basis+ is able to increase the frame rate of a camera if motion
is detected, or if an event occurs. Select the check box to enable increased frame rate on
motion detection or on an event, then specify the required conditions in the following fields.
Tip: In the Camera/Alert Scheduler window (see page 64) you can specify periods in
which the camera should always speedup.
oOn motion: Available only if the Enable speedup check box is selected. Select this
check box to use a higher frame rate when motion is detected. Remember to
specify the required higher frame rate in the Speedup settings section. The camera
will return to the original frame rate two seconds after the last motion is detected.
oOn event: Available only if the Enable speedup check box is selected. Select the
check box to use a higher frame rate when an event occurs and until another event
occurs, then select required start and stop events in the Start and Stop lists. The
camera will increase its frame rate when the start event occurs, and return to the
original frame rate when the stop event occurs. Remember to specify the required
higher frame rate in the Speedup settings section.
Note: Use of speedup on event requires that at least one event (I/O or VMD event)
has been defined. Read more about events in About Input, Events & Output ... on
page 73.
•When to store images in the database: Select when video received from the camera
should be stored in the database:
o Always: Always store all received video in the database.
o Never: Never store any received video in the database. Live video will be displayed,
but, since no video is kept in the database, users will not be able to browse video
from the camera.
oConditionally: Store received video in the database when certain conditions are
met. When you select this option, specify required conditions in the following fields.
On motion: Available only when the option Conditionally is selected, i.e.
when video received from the camera should be stored in the database on
www.milestonesys.com Page 40 Camera Administration
certain conditions only. Select the check box to store all video in which
motion is detected.
On event: Available only when the option Conditionally is selected, i.e. when
video received from the camera should be stored in the database on certain
conditions only. Select the check box to store all video, regardless of motion,
when an external event occurs and until another external event occurs, then
select required start and stop events in the Start and Stop lists.
Note: Use of storage on event requires that events have been defined. Read
more about events in About Input, Events & Output ... on page 73
o[Number of] seconds pre/post recordings on event: Available only when the option
Conditionally is selected, i.e. when video received from the camera should be
stored in the database on certain conditions only.
You are able to store recordings from periods preceding and following detected
motion and/or specified events. Using such a pre/post buffer can be advantageous:
If, for example, you have defined that video should be stored when a door is
opened, being able to see what happened immediately prior to the door being
opened may be important.
Specify the numbers of seconds for which you want to store video from before and
after the storage conditions are met. Example: You have specified that video
should be stored conditionally on event, with a start event called Door Opened and
a stop event called Door Closed. With a pre/post buffer of three seconds, video will
be stored from three seconds before Door Opened occurs to three seconds after Door Closed occurs.
Note: Pre/post recording periods cannot be displayed in the timelines of the Smart
Client’s timeline browser. The fact that these periods cannot be displayed in the
timeline browser’s timelines does not affect recording.
Live Settings
The Live settings section lets you determine the frame rate with which users will view live video in
their access clients. Select either Same as recording or Same as speedup.
Note: This section is not available for cameras using MPEG. For MPEG, viewing of live video will
take place with the same frame rate as specified for speedup.
Audio
In the Audio section you are able to associate a microphone with the selected camera.
Note: The ability to associate a microphone with the selected camera requires that at least one
microphone has been attached to a device on the surveillance system.
When a microphone is associated with a camera, audio from the source will automatically be used
when video from the camera is viewed. Note that you are able to select a microphone attached to
another device than the selected camera.
To associate a microphone with the selected camera, simply select the required microphone from
the Default microphone list. For cameras attached to the same device as a microphone, the
microphone is automatically selected and cannot be changed.
www.milestonesys.com Page 41 Camera Administration
Note: Functionality in the IPIX section is only available if the use of IPIX technology has been
enabled for the device to which the camera is attached. For dedicated IPIX cameras, the use of
IPIX technology is automatically enabled. If not dealing with a dedicated IPIX camera, you enable
use of IPIX technology for a device in the Edit device settings window (see page 34), accessed by
selecting the required device in the Administrator window’s (see page 26) Device Manager section,
then clicking the Administrator window’s Edit Device... button.
The IPIX section contains the following fields and buttons:
•Enable IPIX: Select check box to enable the use of IPIX, a technology that allows viewing
of 360-degree panoramic images through an advanced fish eye lens on the particular
camera.
•IPIX Settings...: Opens the IPIX Camera Configuration window (see page 55), in which
you configure the camera’s IPIX functionality.
Motion Detection Settings
The Motion Detection Settings section contains two buttons for configuring the camera’s motion
detection:
•Motion Detection...: Opens the Adjust Motion Detection window (see page 46), in which
you are able to specify motion detection sensitivity levels.
•Exclude Regions...: Opens the Define Exclusion Regions window (see page 47) where you
are able to disable motion detection in specific areas of the camera’s images.
Disabling motion detection in certain areas may help you avoid detection of irrelevant
motion, for example if the camera covers an area where a tree is swaying in the wind or
where cars regularly pass by in the background.
Database Settings
The database for each camera is capable of containing a maximum of 600,000 records or 40 GB
per day. Note that camera databases also store recorded audio from associated audio sources; see
Important Information about Using Audio page 59 for more information.
Tip: By using archiving (see page 101) it is possible to store recordings beyond the capabilities
of the camera’s database.
The Database settings section lets you specify database settings for the camera, such as where the
database containing the camera’s recordings should be kept, how much to store, etc. You specify
this information in the following fields:
•Max records in database: Select this option to limit the database size based on a
maximum allowed number of records in the database. Specify required maximum number
of records in the neighboring field. When the database reaches the maximum number of
records, the oldest record in the database will automatically be overwritten.
Note: A database can contain a maximum of 600,000 records or 40 GB per day, regardless
of what maximum has been defined.
•Max timespan in database: Select this option to limit the database size based on the age
of records in the database. Specify the required number in neighboring field, and select
required unit (Minutes, Hours, or Days) from the list. When records become older than the
www.milestonesys.com Page 42 Camera Administration
specified number of minutes, hours, or days, they will automatically be deleted.
Note: A database can contain no more than 600,000 records or 40 GB per day, regardless
of what maximum age has been defined.
Tip: You will receive a message if—based on the recording frame rate you have
specified for the camera—XProtect Basis+ detects that the maximum number of allowed
records in the database is likely to be reached before the end of the specified time span.
•Clear Database... : Click button to delete all records stored in the database for the
camera in question. Records stored in archived databases will not be affected.
WARNING: Use with caution; all records in the database for the camera will be
permanently deleted. As a security measure, you will be asked to confirm that you want to
permanently delete all stored records for the camera.
Note: If the Milestone Recording Server service is running, the button will not be available.
To make the button available, pause the Milestone Recording Server service by clicking the
Administrator window’s (see page 26) Service Manager button, then clicking the Pause
button or by stopping the service from the Recording Server Manager icon (see page 61).
IMPORTANT: No video or audio will be recorded while the Milestone Recording Server
service is paused or stopped (see page 61).
•Archive automatically when database is full: Select this check box if you wish to
automatically archive the database when it is full.
Note: For this feature to work, you should first enable archiving in the Archive Setup
Window (see page 105).
•Database path: Specify which local directory the database for the camera should be kept
in. Default database path is the path at which the XProtect Basis+ software is installed,
typically C:\Program Files\Milestone\Milestone Surveillance\. To browse for a folder, click
the browse button next to the Database path field.
Note: Even though it is possible to specify a path to a network drive, it is highly
recommended that you specify a path to a local drive. If using a path to a network drive, it
will not be possible to save to the database in cane the network drive should become
unavailable.
Tip: If you have several cameras, and several local drives are available, performance
can be improved by distributing the databases of individual cameras across the local drives.
•In case of database failure, take the following action: .Select which action to take if
the database becomes corrupted. The number of available actions depends on whether
archiving has been enabled. You enable archiving for a camera in the Archive setup window
(see page 105), accessed from the Administrator window (see page 26) by clicking the
Archive Setup... button.
oRepair, Scan, Delete if fails: Default action. If the database becomes corrupted, two
different repair methods will be attempted: a fast repair and a thorough repair. If
both repair methods fail, the contents of the database will be deleted.
oRepair, Delete if fails: If the database becomes corrupted, a fast repair will be
attempted. If the fast repair fails, the contents of the database will be deleted.
oRepair, Archive if fails: Available only if archiving is enabled for the camera. If the
database becomes corrupted, a fast repair will be attempted. If the fast repair fails,
the contents of the database will be archived. This action is recommended if
www.milestonesys.com Page 43 Camera Administration
oDelete (no repair): If the database becomes corrupted, the contents of the
database will be deleted.
oArchive (no repair): Available only if archiving is enabled for the camera. If the
database becomes corrupted, the contents of the database will be archived.
Tip: Provided the corrupted database has been archived (see page 101), it can
be repaired by the Viewer (see page 135): Open the Viewer and attempt to browse
the archived recordings from the camera in question. Browsing will initially fail, but
this will make the Viewer start repairing the corrupt database.
When the contents of the local database for the camera are either deleted or archived, the
database is reset and will be ready for storing new recordings.
Note: Recording is not possible while the database is being repaired. For l arge
installations, a repair may take several hours, especially if the Repair, Scan, Delete if fails
action involving two different repair methods is selected, and the first repair method (fast
repair) fails.
Tip: Learn how you can help prevent the need for repairing databases in the first place;
see page 129.
Database Resizing
In case recordings for a camera get bigger than expected, or the available drive space is suddenly
reduced in another way, an advanced database resizing procedure will automatically take place:
If archives are present on the same drive as the camera’s database, the oldest archive for all
cameras archived on that drive will be deleted.
If no archives are present on the drive containing the camera’s database, the size of all camera
databases on the drive will be reduced by deleting a percentage of their oldest recordings, thus
temporarily limiting the size of all databases
When the recording server is restarted upon such database resizing, the original database sizes will
be used. You should therefore make sure the drive size problem is solved, or adjust camera
database sizes to reflect the altered drive size.
Tip: Should the database resizing procedure take place, you will be informed on-screen in the
Smart Client, in log files, and (if set up) through an e-mail alert.
Tip: For more information about how XProtect Basis+ responds to the threat of running out of
disk space, see page 102.
Image Quality…
The Image Quality... button opens the Configure Device window (see page 45), in which you are
able to configure resolution, compression, etc. for the camera.
Event Notification
The Event Notifications... button opens the Setup Notifications on Events window (see page 50), in
which you are able to select events for triggering event indications for the camera when displayed
in the Remote Client or Smart Client (see page 140).
www.milestonesys.com Page 44 Camera Administration
Note: The use of event notifications requires that at least one event has been specified for a device
on your XProtect Basis+ system; the event does not have to be specified for the particular camera.
Read more about events in About Input, Events & Output .... on page 73
Outputs…
The Outputs... button opens the Output Settings for [Device Name] [Camera Name] window (see
page 49), in which you are able to specify which outputs (e.g. the sounding of a siren or the
switching on of the lights) should be associated with motion detection and/or with output buttons
for manually triggering output when the camera is selected in the Remote Client or Smart Client
(see page 140).
Note: The use of outputs requires that at least one event has been specified for a device on your
XProtect Basis+ system; the event does not have to be specified for the particular camera. You
specify output events in the I/O Setup window (see page 74), accessed by clicking the I/O Setup...
button in the Administrator window (see page 26).
PTZ Present Position… (PTZ Cameras Only)
Available only if the camera is a PTZ (Pan/Tilt/Zoom) camera supporting PTZ preset positions, the
PTZ Preset Positions... button opens PTZ Preset Positions for [Device Name] [Camera Name]
window (see page 51), in which you are able to specify preset positions for the camera.
Note: If the Milestone Recording Server service (see page 61) is running, the button will not be
available. To make the button available, pause the Milestone Recording Server service by clicking
the Administrator window’s (see page 26) Service Manager... button, then clicking the Pause
button.
IMPORTANT: No video or audio will be recorded while the Milestone Recording Server service is
paused.
Configure Device Window
Note: Settings in the Configure Device window are to a large extent
camera-specific. The window’s contents will therefore vary from
camera to camera; descriptions in the following are thus for guidance
only.
The Configure Device window lets you specify image quality settings,
such as compression, resolution, etc. for a specific camera. You
access the Configure Device window by clicking the Image Quality...
button in the Camera Settings for [Device Name] [Camera Name]
window (see page 39). The Configure Device window is divided into a
Camera Settings section and a section with a preview image.
Camera Settings Section
The Camera Settings section will typically contain controls for
compression, bandwidth, resolution, color, contrast, brightness, rotation, and similar.
Include Date and Time in Image
The Camera Settings section may feature an Include Date and Time in Image check box. When
selected, date and time from the camera will be included in images from the camera.
www.milestonesys.com Page 45 Camera Administration
Note: As cameras are separate units which may have separate timing devices, power supplies,
etc., camera time and XProtect Basis+ system time may not correspond fully, and this may
occasionally lead to confusion. As all images are time-stamped by XProtect Basis+ upon reception
and exact date and time information for each image is thus already known, it is recommended that
you keep the Include Date and Time in Image check box cleared. Should you want to use the
Include Date and Time in Image feature, it is recommended that you click the Synchronize Time
button, if available. Clicking the Synchronize Time button will set camera time to system time, but
does not guarantee that camera time will match system time indefinitely.
Tip: For consistent synchronization, you may, if supported by the camera, auto-synchronize
camera and system time via a time server.
Preview Image
When adjusting camera settings, you are able to view the effect of your settings by clicking the
Preview Image button, located at the bottom of the window. Clicking the Preview Image button will
provide you with an image from the camera in question, as it would look with the settings specified
in the Camera Settings section. When you have found the best possible camera settings, click OK
to apply the settings for the camera.
Adjust Motion Detection Window
The Adjust Motion Detection window lets you specify motion detection
sensitivity for a specific camera. Depending on your configuration,
motion detection sensitivity settings may determine when recordings
from the camera are transferred to the surveillance system, when
alerts are generated, when external outputs (such as lights or sirens)
are triggered, etc.
Motion detection sensitivity is therefore a key element in your XProtect
Basis+ surveillance solution, and time spent on finding the best possible motion detection settings
for each camera may help you later avoid unnecessary alerts, etc.
Depending on the physical location of the camera, it may be a very good idea to test motion
detection settings under different physical conditions (day/night, windy/calm weather, etc.).
You access the Adjust Motion Detection window by clicking the Motion Detection... button in the
Camera Settings for [Device Name] [Camera Name] window (see page 39).
Note: Before you configure motion detection sensitivity for a camera, it is highly recommended
that you have configured the camera’s image quality settings, such as resolution, compression,
etc., in the Configure Device window (see page 45), and that you have specified any areas to be
excluded from motion detection (for example if the camera covers an area where a tree is swaying
in the wind or where cars regularly pass by in the background) in the Define Exclusion Regions
window (see page 47). If you later change image quality settings and/or exclusion area settings,
you should always test motion detection sensitivity settings afterwards.
The Adjust Motion Detection window features two sliders; one for setting Noise Sensitivity and one
for setting Motion Sensitivity:
Noise Sensitivity
Noise is insignificant changes in individual pixels which should not be regarded as motion.
www.milestonesys.com Page 46 Camera Administration
The Noise Sensitivity slider determines how much each pixel must change before it is regarded as
motion. Insignificant changes, which should not be regarded as motion, are considered acceptable
noise, hence the name of the slider. With high noise sensitivity, very little change in a pixel is
required before it is regarded as motion.
Tip: If you find the concept of noise sensitivity difficult to grasp, try dragging the slider to the
left towards the High position: The more you drag the slider towards the High position, the more of
the preview image becomes highlighted. This is because with high noise sensitivity even the
slightest change in a pixel will be regarded as motion.
Areas in which motion is detected are highlighted in the preview image. Select a slider position in
which only detections you consider motion are highlighted.
As an alternative to using the slider, you may specify a value between 0 and 256 in the field next
to the slider to control the noise sensitivity setting.
Motion Sensitivity
The Motion Sensitivity slider determines how many pixels must change in the image before it is
regarded as motion.
The selected motion sensitivity level is indicated by the black vertical line in the motion level
indication bar below the preview image. The black vertical line serves as a threshold: When
detected motion is above the selected sensitivity level, the bar changes color from green to red,
indicating a positive detection.
As an alternative to using the slider, you may specify a value between 0 and 10,000 in the field
next to the slider to control the motion sensitivity setting.
Define Exclusion Regions Window
The Define Exclusion Regions window lets you disable motion detection in specific areas of a
camera’s images. Disabling motion detection in certain areas may help you avoid detection of
irrelevant motion, for example if the camera covers an area where a tree is swaying in the wind or
where cars regularly pass by in the background.
The Define Exclusion Regions window, with
an exclusion area highlighted in blue
You access the Define Exclusion Regions window by clicking the Exclude Regions... button in the
Camera Settings for [Device Name] [Camera Name] window (see page 39).
www.milestonesys.com Page 47 Camera Administration
Defining Areas in which Motion Detection Should Be
Disabled
The Define Exclusion Regions window features a preview image from the camera. You define the
areas in which motion detection should be disabled in the preview image, which is divided into
small sections by a grid.
To define areas in which motion detection should be disabled, drag the mouse pointer over the
required areas in the preview image while pressing the mouse button down. Left mouse button
selects a grid section; right mouse button clears a grid section. Selected areas are highlighted in
blue.
Define Exclusion Regions Window’s Buttons and Check
Boxes
The Define Exclusion Regions window features the following buttons:
Button,
Check Box
Set All Lets you quickly select all grid sections in the preview image. This may be
Clear All Lets you quickly clear all grid sections in the preview image.
Auto By clicking the Auto button you can make XProtect Basis+ automatically
Description
advantageous if you want to disable motion detection in most areas of the
image, in which case you can simply clear the few sections in which you do
not want to disable motion detection.
detect areas with noise (insignificant changes in individual pixels which should
not be regarded as motion) in the image, and automatically mark such areas
as areas in which motion detection should be disabled.
As the automatic detection is based on an analysis of a number of images, it
may take a few seconds from you click the Auto button to noisy areas are
detected and marked as areas in which motion detection should be disabled.
Note: The automatic detection of noisy areas happens according to the noise
sensitivity setting specified in the Adjust Motion Detection window (see page
46). In order for the automatic detection of noisy areas to work as intended, it
is recommended that you specify a noise sensitivity setting that matches your
requirements before you make use of the automatic detection feature.
Show Grid With the Show grid check box selected (default), the preview image contains a
grid indicating the division of the preview image into selectable sections.
With the Show grid check box cleared, the grid in the preview image is
removed. This may provide a less obscured view of the preview image.
Selection of areas in which motion detection should be disabled takes place
the same way as when the grid is visible.
www.milestonesys.com Page 48 Camera Administration
Output Settings for [Device Name] [Camera
Name] Window
In the Output Settings for [Device Name] [Camera Name] window
you are able to associate a camera with particular external
outputs, defined in the I/O Setup window (see page 74), for
example the sounding of a siren or the switching on of lights.
The associated outputs can be triggered automatically when
motion is detected as well as manually through output buttons
available in the Remote Client and Smart Client (see page 140).
You access the Output Settings for [Device Name] [Camera Name]
window from the Camera Settings for [Device Name] [Camera Name] window (see page 39), by clicking the Outputs... button.
Associating Outputs with Manual Control and Detected
Motion
Note: Use of features in the Output Settings for [Device Name] [Camera Name] window requires
that output has been defined in the I/O Setup window (see page 74).
You have a high degree of flexibility when associating a camera with particular outputs:
• You are able to select between all available outputs, i.e. outputs defined as output events
for the camera itself as well as outputs defined as output events for other devices on the
XProtect Basis+ system
• The same output may be used for manual control through an output button as well as for
automatic triggering when motion is detected
Selecting Output for Manual Control
You are able to specify outputs to be triggered manually from a list in the Remote Client or Smart
Client (see page 140).
To specify an output for manual triggering in the Remote Client/Smart Client, do the following:
1. Select the required output in the All Outputs list in the left side of the Output Settings for
[Device Name] [Camera Name] window.
Tip: When you select an output in the All Outputs list, you can view detailed
information about the selected output under Output Information in the lower part of the
window.
2. Click the >> button located between the All Outputs list and the On Manual Control list.
This will copy the selected output to the On Manual Control list.
An unlimited number of outputs may be selected this way.
You are able to determine each output’s position in the Remote Client’s and Smart Client’s output
list by moving the selected output up or down in the On Manual Control list with the up and down
buttons located to the right of the list. The selected output is moved up one step each time you
click the up button. Likewise, each time you click the down button, the selected output is moved
down one step.
www.milestonesys.com Page 49 Camera Administration
To remove an output from the On Manual Control list, simply select the required output, and click
the << button located between the All Outputs list and the On Manual Control list.
Selecting Output for Use on Motion Detection
You are able to select outputs to be triggered automatically when motion is detected in video from
the camera.
Tip: This feature does not require that a VMD (Video Motion Detection) event has been defined
for the camera in the I/O Setup window (see page 74).
To select an output for use when motion is detected in video from the camera:
1. Select the required output in the All Outputs list in the left side of the Output Settings for
[Device Name] [Camera Name] window.
Tip: When you select an output in the All Outputs list, you can view detailed
information about the selected output under Output Information in the lower part of the
window.
2. Click the >> button located between the All Outputs list and the On Motion Detected list.
This will copy the selected output to the On Motion Detected list.
To remove an output from the On Motion Detected list, simply select the required output, and click
the << button located between the All Outputs list and the On Motion Detected list.
Setup Notifications on Events
Window
Note: The use of event notifications requires that at least one event
has been specified for a device on your XProtect Basis+ system; the
event does not have to be specified for the particular camera. You
specify events in the I/O Setup window (see page 74), accessed by
clicking the I/O Setup... button in the Administrator window (see
page 26).
The Setup Notifications on Events window lets you select events for
triggering event indications for the camera when displayed in
Remote Client and Smart Client (see page 140).
You access the Setup Notifications on Events window from the Camera settings for [Device Name] [Camera Name] window (see page 39), by clicking the Event Notifications button.
What is an Event Indication?
In the Remote Client/Smart Client, three different color indicators
are available for each camera: a yellow indicator, a red indicator,
and a green indicator. When event indication is used for a camera,
the yellow indicator will light up when the specified events have
occurred.
Event indications can be valuable for camera operators, as they will
be able to quickly detect that an event has occurred, even though
their focus was perhaps on something else the moment the event occurred
.
www.milestonesys.com Page 50 Camera Administration
Tip: The other two indicators serve the following purposes: The red indicator lights up when
motion has been detected, and the green indicator is used for indicating that video is received from
a camera.
Specifying Events for which Event Indication Should Be
Used
To specify which events should trigger an event indication for the camera, do the following for each
required event:
1. In the Available Events list, select the required event.
Tip: You are not limited to events associated with a particular device: You are able to
select between all available events (input events, timer events, event buttons) from all
cameras on the XProtect Basis+ surveillance system.
2. Click the >> button to copy the selected event to the Active Events list. When an event
listed in the Active Events list occurs, the event indicator will light up.
3. Repeat for each required event.
To remove an event from the Active Events list, select the event in question, and click the <<
button.
PTZ Preset Positions for [Device Name] [Camera
Name] Window
Available only when dealing with a PTZ (Pan/Tilt/Zoom) camera supporting PTZ preset positions,
the PTZ Preset Positions for [Device Name] [Camera Name] window lets you view and — for many,
but not all, PTZ cameras — define preset positions for the PTZ camera.
To access the PTZ Preset Positions for [Device Name] [Camera Name] window, click the PTZ Preset Positions... button in the Camera Settings for [Device Name] [Camera Name] window (see page
39). The button is only available if the camera supports PTZ preset positions. Note that if the
MilestoneRecording Server service (see page 61) is running, the button will not be available; see
the description of the Camera Settings for [Device Name [Camera Name] window for information
about how to make the button available.
Why Use Preset Positions?
Defined preset positions can be used for making the PTZ camera automatically go to particular
preset positions when particular events occur. Defined preset positions will also become selectable
in the Remote Client/Smart Client, allowing users of these applications to move the PTZ camera to
the preset positions.
Absolute and Relative Positioning PTZ Cameras
Your configuration options depend on whether the PTZ camera in question is of the absolute
positioning or relative positioning kind:
www.milestonesys.com Page 51 Camera Administration
•Absolute: For an absolute positioning PTZ camera, you are able to define up to 25 preset
positions. You define a preset position by moving the PTZ camera to the required position
with the controls in the PTZ View section, then naming the position in the window’s Preset Positions section.
•Relative: For a relative positioning PTZ camera, the number of preset positions will depend
on the camera/video encoder and PTZ driver used. For some relative positioning PTZ
cameras you will only be able to use preset positions defined on the camera/video encoder
itself (when this is the case, the preset positions are typically defined through the
camera/video server’s “built-in” web page).
For relative positioning PTZ cameras allowing definition of preset positions through the
XProtect Basis+ system, you define a preset position by moving the PTZ camera to the
required position with the controls in the PTZ View section, then naming the position in the
window’s Preset Positions section.
How to Define a Preset Position
Note: Some PTZ cameras of the relative positioning kind do not allow you to define preset
positions as described in the following; for such cameras, you should define preset positions on the
camera/video encoder itself.
1. First use the controls in the PTZ Preset Positions for [Device Name] [Camera Name]
window’s PTZ View section to move the PTZ camera to the required position.
2. Having moved the PTZ camera to the required position, select an undefined item (may be
labeled Undefined or with a position number) in the Preset Positions section’s list of preset
position names, and click the Set Position button to define a name for the preset position.
For detailed information about the functionality of PTZ Preset Positions for [Device Name] [Camera Name] window—such as the ability to test your preset positions or the ability to
combine preset positions with events—see Preset Positions for [Device Name] [Camera Name] window’s sections in the following.
You are able to define up to 25 preset positions.
Each of the PTZ Preset Positions for [Device Name] [Camera Name] window’s sections are
described in the following:
PTZ View Section
The PTZ View section lets you control the PTZ camera, and watch the PTZ camera’s movements.
You use this section to move the PTZ camera to the positions you then define as presets positions
in the Preset Positions section.
To move the PTZ camera, simply click the required position in the preview picture.
The PTZ View section also features sliders allowing you to move the PTZ camera along each of its
axes: the X-axis (allowing you to pan left/right), the Y-axis (allowing you to tilt the camera
up/down), and the Z-axis (enabling you to zoom in and out; the camera will zoom in when you
move the slider towards Tele, and zoom out when you move the slider towards Wide).
As an alternative to clicking the required position in the preview or using the sliders, you can use
the PTZ camera navigation buttons:
www.milestonesys.com Page 52 Camera Administration
Having specified a camera position in the PTZ View section, you define the required position as a
preset in the Preset Positions section:
Button,
Check Box
Use preset
positions
from
device
Set
Position
Description
Available only for cameras supporting this feature. Check box to use preset
positions defined on the camera or video encoder device. Using preset positions
from the camera or video encoder device will clear any preset positions you have
defined for the PTZ camera; you will therefore be asked to confirm your
selection.
Note: In order for preset positions from the camera or video encoder device to
work with XProtect Basis+, the names of the preset positions must contain only
the characters A-Z, a-z and 0-9, and must not contain spaces. If preset position
names on the camera or video encoder device contain other characters, or
spaces, change the preset position names on the device before selecting the Use preset positions from device feature.
Associates the preset position selected in the list with the position specified in the
PTZ View section. If the preset position selected in the list is yet undefined, you
will be asked to specify a name for the preset position.
Edit
Name...
Test Lets you test a defined preset position. Select the required preset position in the
www.milestonesys.com Page 53 Camera Administration
Lets you edit a preset position name selected in the list. Only works for an
already defined preset position name.
list, then click the Test button. The effect is displayed instantly in the PTZ View
section.
Delete Lets you delete a preset position selected in the list. When a preset position name
is deleted, it will appear as undefined in the list.
[Move up]
[Move
down]
Lets you move a preset position selected in the list up and down respectively.
The selected preset position is moved one step per click. By moving preset
position up or down, you are able to control the sequence in which available
preset positions are presented in the Remote Client and Smart Client (see page
140). In the Remote Client and Smart Client, users select preset positions from a
list. By moving a preset position up or down in the Preset Positions section’s list,
you can thus determine the sequence in which preset positions are presented in
the Remote Client’s or Smart Client’s list.
Display of preset positions in Remote Client/Smart Client. Administrators are able to specify
the sequence in which available preset positions are displayed.
Preset Position on Event Section
If you have specified input or VMD events (see page 74) or event buttons (see page 84), you are
able to make the PTZ camera automatically go to particular preset positions when particular events
occur.
To configure the use of preset positions on events, click the Setup... button. This will open the
Event window (for preset positions on event) – see page 54) – in which you are able to associate
particular preset positions with particular events.
To use preset positions on event, select the Go to preset on event check box.
Event Window (for PTZ Preset Positions on
Events)
Available only when dealing with a PTZ
(Pan/Tilt/Zoom) camera, the Event window (for
preset positions on events) lets you associate
particular preset positions with particular events,
timer events or event buttons. You are thus able to
make the PTZ camera automatically go to a
particular preset position when a particular event
occurs.
To access the Event window (for preset positions on
events), click the Setup... button in Preset Position on Events section of the PTZ Preset Positions for [Device Name] [Camera Name] window (see page
51).
www.milestonesys.com Page 54 Camera Administration
Note: To use preset positions on events, you must have specified input or VMD events (see page
74), or event buttons (see page 84) Only one PTZ preset position can be defined per event per
camera.
Associating Preset Positions with Particular Events
When associating a preset position from a particular PTZ camera with one or more events, you are
able to select between all events defined on the XProtect Basis+ system; you are not limited to
selecting events defined on a particular device.
To associate a particular preset position with a particular event, do the following:
1. Select the required preset position in the Available Preset Positions list in the left side of
the Event window.
2. Select the required event in the list of available events (the list in the middle of the
window).
3. Click the >> button located to the right of the Available Events list.
This will copy the selected event to the window’s rightmost list, in which events associated
with the selected preset position are listed. When the selected event occurs, or when the
selected event button is clicked, the PTZ camera will automatically move to the required
preset position.
You are able to associate a preset position with more than one event: Simply repeat the process
for each required association.
To end the association between a particular preset position and a particular event, simply select
the required event in the window’s rightmost list, and click the << button.
iPIX Camera
Configuration Window
Note: Use of the IPIX technology requires a
dedicated IPIX camera or a special IPIX camera
lens with a special IPIX license key, specified in
the Edit Device Settings window (see page 34).
IPIX is a technology that allows viewing of 360degree panoramic images through an advanced
“fish eye” lens. The iPIX Camera Configuration
window lets you configure the IPIX functionality of a camera.
You access the iPIX Camera Configuration window from the Camera Settings for [Device Name]
[Camera name] window (see page 39), by selecting the Enable iPIX check box, and clicking the
iPIX Settings... button.
IPIX View Adjustment
The camera’s IPIX functionality is configured by adjusting its IPIX view field—indicated by a green
ellipse in the preview image—so it encloses the actual image area of the “fish eye” lens. You do this
by specifying a number of values which will be used by the IPIX technology for converting the
elliptic image into an ordinary rectangular image.
www.milestonesys.com Page 55 Camera Administration
You are able to set the ellipse’s X-radius, Y-radius, X-center, and Y-center, either by specifying the
required values directly in the four fields or by using the following buttons to adjust the ellipse:
Button Description
R- Decreases the radius of the IPIX view field. The ellipse’s horizontal (X) and
vertical (Y) radiuses are changed at the same time, keeping the aspect ratio.
R+ Increases the radius of the IPIX view field. The ellipse’s horizontal (X) and
vertical (Y) radiuses are changed at the same time, keeping the aspect ratio.
Rx- Decreases the horizontal (X) radius of the ellipse.
Rx+ Increases the horizontal (X) radius of the ellipse.
Ry- Decreases the vertical (Y) radius of the ellipse.
Ry+ Increases the vertical (Y) radius of the ellipse.
X- Moves the ellipse to the left.
X+ Moves the ellipse to the right.
Y- Moves the ellipse up.
Y+ Moves the ellipse down.
Previewing the IPIX View
You are able to toggle between previewing the “fish eye” view and the IPIX-rendered view, i.e. the
original elliptic view as well as the “flattened” rectangular view resulting from applying the IPIX
algorithm according to your specified values. To toggle between the two different types of preview,
click the Toggle Preview button.
When previewing the IPIX-rendered view, the following navigation buttons become available for
moving around within the preview image area:
Moves the IPIX-rendered view up and to the left
Moves the IPIX-rendered view up
Moves the IPIX-rendered view up and to the right
Moves the IPIX-rendered view to the left
Moves the IPIX-rendered view to its home position
www.milestonesys.com Page 56 Camera Administration
Moves the IPIX-rendered view down and to the right
Zoom out (one zoom level per click)
Zoom in (one zoom level per click)
Ceiling Mounted Cameras
If the camera is mounted on a ceiling, you can adjust the behavior of the navigation buttons to
reflect this by selecting the Ceiling Mount check box.
Setting a View as Home Position
When previewing the IPIX-rendered view, you are able to set a particular position in the IPIXrendered view as the camera’s PTZ home position: Navigate to the required position, using the
navigation buttons and then click the Set View as Home Position button.
Image Resolution
Resolution values are automatically displayed in the lower part of the window, next to the
navigation buttons. When using IPIX, resolution will automatically be set to the highest available
resolution.
Camera Name and Number Window
The Camera Name and Number window lets you edit the name of a selected camera, and, if
required, assign a shortcut number to the selected camera.
You access the Camera Name and Number window from the Administrator
window’s (see page 26) device Manager section: Right-click the name of
the required camera, then select Edit from the menu that appears
The Camera Name and Number window contains two fields:
Field Description
:
Camera
Name
Camera
Number
www.milestonesys.com Page 57 Camera Administration
Displays the name of the camera. If required, you are able to overwrite the
existing camera name with a new one.
Users of the Smart Client (see page 140) can take advantage of a range of
keyboard shortcuts, some of which let the users toggle between viewing
different cameras. Such shortcuts include numbers, which are used to identify
each camera. Camera shortcut numbers must be unique for each camera,
must not contain any letters or special characters, and must be no longer than
If you use audio sources (i.e. microphones and/or speakers) on your XProtect Basis+ system, note
the following:
•Audio from microphones is recorded even when video is not: When a microphone is
enabled (see Microphone Settings Window described on page 59), audio from the
microphone will be recorded whenever the associated camera is online (i.e. transmitting
data to XProtect Basis+; see Camera/Alert Scheduler Window on page 64), regardless
whether video from the camera is being recorded or not.
Depending on your cameras’ recording settings, this may mean that when you play back
recordings, you may find that there are periods for which you only have audio recordings.
This will also be the case for exported recordings if audio has been included in the export.
•Audio recording affects video storage capacity: When a microphone is enabled, audio
is recorded to the associated camera’s database. This will affect the database’s capacity for
storing video. A camera’s database can contain a maximum of 40 GB or 600,000 records. It
is thus important to bear in mind that the maximum limit of the database is likely to be
reached earlier if recording audio and video than if only recording video.
o Example: If using MPEG4, each one-second video GOP (Group Of Pictures) will be
stored in one record in the database. Each second of audio will also be stored in
one record in the database. When this is the case, the database’s video storage
capacity will be reduced to a maximum of 300,000 records, because half of the
database’s total maximum of 600,000 records will be used for storing audio.
o Example: If using MJPEG, audio is stored in one record for every JPEG for as long
as the audio block size does not exceed the time between the JPEGs. The
database’s video storage capacity can thus in extreme cases be reduced to a
maximum of 300,000 records, because half of the database’s total maximum of
600,000 records will be used for storing audio. If using very high frame rates,
where there is less time between each JPEG, a smaller portion of the database will
be used for storing audio records, and consequently a larger portion will be
available for storing video.
Thus, a camera database’s maximum video storage capacity may in some cases be halved
when an associated audio source is enabled.
Note: Above examples are simplified. Since databases also have a maximum limit of 40
GB of data, the exact available video storage capacity will also depend on GOP/JPEG and
audio kilobyte size.
Tip: The Archiving feature (see page 101) enables you to store recordings beyond the
capabilities of cameras’ databases.
Microphone Settings Window
The Microphone Settings window lets you change basic settings for a microphone.
You access the Microphone Settings window from the Administrator window (see page 26): Select a
microphone in the Administrator window’s Device Manager section, then click the Settings button.
•Device name: Displays the name of the microphone. If required, you are able to overwrite
the existing audio microphone name with a new one.
•Enabled: Lets you enable/disable use of the microphone.
Tip: You can also enable/disable an audio source in the Administrator window: Right-click the
required audio source in the Administrator window’s Device Manager section, then select Disable or
Enable from the menu that appears.
Note: On some devices, a microphone can also be enabled/disabled on the device itself, typically
through the device’s own configuration web page. If a microphone on a device does not work after
enabling it in the Administrator application, you should thus verify whether the problem may be
due to the microphone being disabled on the device itself.
The Recording Server service is a vital part of the surveillance system; video streams are only
transferred to XProtect Basis+ while the Recording Server service is running.
The Recording Server Manager informs you about the state of the Recording Server service. It also
lets you manage the service.
A notification area (a.k.a. system tray) icon indicates whether the Recording Server service is
running or not. Green indicates running (default), red indicates not running.
By right-clicking the icon you can start and stop the Recording Server service, view log files, etc.
Starting and Stopping the Recording Server
To start the Recording Server service, do the following:
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Start Recording Server Service.
3. The icon changes to green.
To stop the Recording Server service, do the following:
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Stop Recording Server Service.
3. The icon changes to red.
Opening the Administrator Application
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Open Administrator.
Monitoring System Status
By right-clicking the notification area’s Recording Server icon and then selecting Show System
Status, you get access to the Status window. Alternatively, simply double-click the icon.
The Status window lets you view the status of the image server(s) and connected cameras. The
status of each server/camera is indicated by a color:
• Green indicates that the server or camera is running correctly.
www.milestonesys.com Page 61 Recording Server Service Management
•Gray indicates that the camera (not the server) is not running. Typically, a camera will be
indicated in gray in the following situations:
o The camera has been set offline in the Camera/Alert Scheduler window (see page
64)
o The Recording Server service has been paused from the Service Manager window
(see page 63)
o The Recording Server service has been stopped.
• Red indicates that the server or camera is not running. This may because it has been
unplugged or due to a network or hardware. Errors are listed in the Recording Server log
file (see the following).
By placing your mouse pointer over a camera icon in the status window, you will see detailed
information about the camera in question. The information is updated approximately every 10
seconds.
• Resolution: Shows the resolution of the camera.
• FPS: Shows the number of frames per second (i.e. the
frame rate) currently used by the camera. The number
updates each time the camera has received 50 frames.
•Frame count: Shows the number of frames received
from the camera since the Recording Server service
was last started.
•Received KB: Shows the number of kilobytes sent by
the by camera since the Recording Server service was
last started.
• Offline: Indicates the number of times the camera has been offline due to an error.
Viewing Recording Server & Image Server Log Files
To view the recording server log file, do the following:
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Open Recording Server Log File...
To view the Image Server log file, do the following:
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Open Image Server Log File...
For more information about log files, see page 123.
Accessing the Built-in Help System
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Help.
www.milestonesys.com Page 62 Recording Server Service Management
Viewing Information about Your XProtect Basis+ Version
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select About...
Knowing the version number can be useful in case you require support from your Milestone vendor.
Exiting the Recording Server Manager
1. Right-click the notification area’s Recording Server icon.
2. In the menu that appears, select Exit Recording Server Manager.
Tip: To re-open the Recording Server Manager, go to Windows’ start menu and select All
Programs > Startup > Milestone XProtect Basis+ Recording Server Manager.
Service Manager Window
The Service Manager window lets you pause/resume the Milestone Recording Server service.
Pausing the service is necessary in order to access some features, such as configuration of PTZ
(Pan/Tilt/Zoom) cameras. You access the Service Manager window by clicking the Service Manager... button in the Administrator window (see page 26).
Pausing the Milestone Recording Server
Service
To pause the Milestone Recording Server service, click the Pause button.
IMPORTANT: While the Milestone Recording Server service is paused, no video or audio will be
available; neither for live viewing, nor for recording.
Resuming the Milestone Recording Server
Service
When the service is paused, the Service Manager window closes. The next
time you open it, the Pause button will have changed to Resume. Simply
click the Resume button to resume the Milestone Recording Server service.
Tip: The service is automatically resumed when you exit the Administrator application.
What to Do if the Milestone Recording Server Service is
Stopped
If the Service Manager window informs you that the recording server is stopped, the Milestone
Recording Server service has been stopped (as opposed to paused) outside the Administrator
application, possibly through the Recording Server Manager (see page 61). You are able to start a
stopped Milestone Recording Server service through the Recording Server Manager.
www.milestonesys.com Page 63 Recording Server Service Management
The Camera/Alert Scheduler window lets you specify when each camera should be online. A camera
is online when it is transferring video to the XProtect Basis+ server for processing.
IMPORTANT: The fact that a camera is online (i.e. transferring video to the XProtect Basis+
server) will not necessarily mean that video from the camera is recorded (i.e. stored in the
camera’s database on the XProtect Basis+ server). Storage settings for individual cameras are
specified in the Camera Settings for [Device Name] [Camera Name] Window (see page 39).
You are able to specify whether cameras should be online within specific periods of time, or
whether they should start and stop transferring video when specific events occur within specific
periods of time.
You are also able to specify when the camera should speedup recording and if e-mail alerts should
be triggered if motion is detected during specific periods of time.
By default, cameras added to XProtect Basis+ will automatically be online, and you will only need
to modify the Camera/Alert Scheduler window’s settings if you require cameras to be online only at
specific times or events, or if you want to use specific alerts.
Note, however, that this default may be changed by clearing the General Settings window’s Create Default schedule for new cameras check box (see page 68): If the check box is cleared,
subsequently added cameras will not automatically be online, in which case online schedules must
be specified manually.
To access the Camera/Alert Scheduler window, click the Scheduler... button in the Administrator
window (see page 26).
Camera/Alert Scheduler Window’s Fields and Check
Boxes
Field, Check
Box
Camera Lets you select a particular camera, for which to specify or view a schedule in
Mode Select whether to add or delete periods in the calendar section:
www.milestonesys.com Page 64 Scheduling
Description
the window’s calendar section.
Note: Always verify that you have selected the required camera in the list;
even though schedules displayed in the calendar section may look—and
indeed sometimes be—similar, the displayed schedule refers specifically to the
selected camera.
• Set: Add periods. May also be used to overwrite existing periods.
Online Check the Online box when you want to set or clear online periods for the
selected camera.
Speedup Check the Speedup box when you want to set or clear when the camera
should always/never speedup recording.
Note: The Speedup check box is only available if you have enabled speedup in
the Camera Settings for [Device Name] [Camera Name] window (see page
39).
E-mail Check the E-mail box when you want to set or clear periods with motion- or
database-related e-mail alerts for the selected camera. Such alerts can
automatically be sent to one or more recipients when motion or database
events are detected.
Note: In order to be able to use e-mail alerts, the e-mail alert feature must
have been set up in the E-Mail setup window (see page 70).
Start event When you set an Online period, you will be asked whether you want the
selected camera to transfer video to the XProtect Basis+ software
continuously within the specified period (Always), or only when an event
occurs within the specified period (On Event).
If using On Event, the Start event list lets you select the required start event.
Note: The use of event-based online periods requires that events have been
defined. Read more about events in About Input, Events & Output ... on page
73.
Stop event When you set an Online period, you will be asked whether you want the
selected camera to transfer video to the XProtect Basis+ software
continuously within the specified period (Always), or only when an event
occurs within the specified period (On Event).
If using On Event, the Stop event list lets you select the required stop event.
Note: The use of event-based online periods requires that events have been
defined. Read more about events in About Input, Events & Output ... on page
73.
Camera/Alert Scheduler Window’s Calendar Section
The Camera/Alert Scheduler window’s calendar section lets you specify exact periods of time for
each option for each camera selected in the window’s Camera list.
Set and Clear Modes
Depending on your selection in the Mode list, you Set or Clear periods in the
calendar. Your selection is indicated by your mouse pointer turning into
either a pencil (Set) or an eraser (Clear) when inside the calendar section.
When placing your mouse pointer inside the day band in the top part of the calendar section you
get access to the calendar’s zoom feature. With the zoom feature you are able to toggle between
the calendar’s default seven-day view and a single-day view.
The single-day view provides you with five-minute interval indications, allowing you to specify
periods precisely.
Zoom feature allows you to toggle between seven-day and single-day views
How to Set or Clear Periods in the Calendar
To set or clear a period in the Camera/Alert Scheduler window’s calendar section, simply click at
the required start point in the calendar, and drag to set/clear a period (depending on whether you
have selected Set or Clear in the window’s Mode list).
Good to Know when You Set Online Periods
When you set an Online period, you will be asked whether you want the selected camera to
transfer video to the XProtect Basis+ software continuously within the specified period (Always), or
only when an event occurs within the specified period (On Event).
If using On Event, remember to specify required start and stop events in the Start event and Stop event lists.
Colored Bars
The calendar uses colored bars to indicate active periods for each option (Online, E-mail, SMS,
etc.):
• In the Online bar, active periods are indicated in either pink or yellow:
o Pink (•) indicates that the selected camera is continuously transferring video to the
XProtect Basis+ software.
o Yellow (•) indicates that the selected camera transfers video to the XProtect Basis+
software when a specified event occurs.
• In the Speedup bar, active periods are indicated by olive green (•).
• In the E-mail bar, active periods are indicated in blue (•).
How to Copy and Paste Schedules
With the following buttons, you are able to copy and paste schedules, and thus save yourself
considerable time:
Button Description
Copy
Schedule
www.milestonesys.com Page 66 Scheduling
Lets you copy the schedule displayed in the calendar section. When used in
combination with the Paste Schedule button, you are able to quickly re-use
schedules from one camera to another.
Lets you paste a copied schedule for use with the selected camera. The same
copied schedule can be pasted to several cameras simply by selecting and
pasting to, one camera after the other.
Tip: If you want to use a schedule for all cameras, specify a schedule for
one camera, then use the Copy and Paste to All button to copy the schedule
and paste it to all cameras in one go.
Lets you copy the schedule displayed in the calendar section and paste it to all
cameras in one go.
The General Settings window lets you manage a variety of settings, such as user rights, e-mail
settings, logging, etc. To access the General Settings window, click the General Settings... button
in the Administrator window (see page 26).
Administrator Settings
The Administrator Settings section lets you password protect access to the Administrator
application. Whe n th e Enable Protection check box is selected, users must supply the administrator
password in order to be able to access the Administrator application, and in order to be able to use
any of the features to which access has been restricted.
Changing the Administrator Password
To change the administrator password, click the Change Password... button to open the Change
Password window (see page 70). When an administrator password is in use, users accessing the
Administrator application, or wishing to use protected features, must type the administrator
password in the window before access is granted.
Manual Start Recording Settings
In the Manual start recordings settings section you can enable the possible to manually start
recording in the Smart Client (see page 140). Select the check box Enable manual start recording
to enable manually start of recording.
In the Default duration of manual recording [secs.]: field you can specify the number of seconds
the recording should last. Note that the minimum number of seconds you can specify is 30.
The Maximum duration of manual recording [secs.]: field is reserved for future use.
Logfile Settings
The Logfile Settings section lets you specify where to keep the general log files containing
information about activity in the Administrator and the Recording Server (see page 61), and for
how long. Separate log files are generated for the Administrator and Recording Server service.
Logfile Path
By default, the Administrator and Recording Server log files are stored in the folder containing the
XProtect Basis+ software, typically C:\Program Files\Milestone\Milestone Surveillance\. To specify
another location for your log files, type the path to the required folder in the Logfile Path field, or
click the browse button next to the field to browse to the required folder.
Days to Log
A new log file is created every day. A log file older than the number of days specified in the Days to
log field is automatically deleted. By default, the log file will be stored for five days. To specify
another number of days, simply overwrite the value in the Days to log field. The current day’s
activity is always logged, even with a value of 0 in the Days to log field. The maximum number of
days to log is 9999.
Tip: Read more about logging on page 123.
Event Recording Settings
As opposed to the general log files, which contain information about activity on the surveillance
system itself, event log files contain information about registered events (for more information
about events, see About Input, Events & Output ... on page 73). The Event Recording Settings
section lets you specify where to keep event log files, and for how long. Event log files should be
viewed using the Smart Client (see page 140) or Viewer (see page 135):
•Smart Client: In the Browse tab’s Alerts section, select the required event, then click the
Get List button to see when the event in question was detected.
•Viewer: Select the Viewer’s Alarm Overview control panel, then click the Events button to
view the events log.
Path
By default, event log files are stored in the folder containing the XProtect Basis+ software, typically
C:\Program Files\Milestone\Milestone Surveillance\. To specify another location for your log files,
type the path to the required folder in the Path field, or click the browse button next to the field to
browse to the required folder.
Days to Keep
A new event log file is created every day. Event log files older than the number of days specified in
the Days to keep field are automatically deleted. By default, event log files will be stored for five
days. To specify another number of days, simply overwrite the value in the Days to keep field. The
current day’s activity is always logged, even with a value of 0 in the Days to keep field. The
maximum number of days to log is 9999.
Tip: Read more about logging on page 123.
Advanced
Check Box Description
Don’t send
e-mail on
camera
failures
If selected, no e-mail alerts will be sent if XProtect Basis+ loses contact with a
camera. Otherwise, e-mail alerts will, provided the e-mail alert feature has
been enabled in the E-Mail setup window (see page 70), automatically be sent
if XProtect Basis+ loses contact with a camera, regardless of any e-mail alerts
periods defined in the Camera/Alert Scheduler window (see page 64).
Cameras may be stopped, for example because they have reached the end of
an online schedule (see page 64), in which case Remote Client (see page 142)
and Smart Client (see page 140) users will not be able to view live video from
the cameras.
However, if Start cameras on remote live requests is selected, Remote Client
and Smart Client users will be able to start the camera in order to view live
video from the camera.
If selected (default), a schedule specifying that the camera is always online
(i.e. transferring video to XProtect Basis+) will automatically be created in the
Camera/Alert Scheduler window (see page 64). The automatically created
schedule can be edited manually at any time.
If not selected, no schedule will automatically be created; meaning that the
camera will not automatically be transferring video to XProtect Basis+. When
required, schedules can be added manually in the Camera/Alert Scheduler
window (see page 64).
Email Settings
Clicking the Email Settings... button opens the E-Mail setup window (see page 70), in which you
enable and configure the use of e-mail alerts.
Change Password Window
The Change Password window lets you change the administrator password for your XProtect Basis+
solution. To access the Change Password window, click the Change Password... button in the
General Settings window (see page 68).
How to Change the Administrator Password
1. Specify the current administrator password in the Old password field
2. Specify the new administrator password in the New password field
3. Repeat the new administrator password in the New password (confirm) field
4. Click OK.
E-Mail Setup Window
The E-Mail setup window lets you enable and configure the use
of e-mail alerts. Such e-mail alerts can automatically be sent to
one or more recipients when motion is detected or specific
events (see About Input, Events & Output ... on page 73) occur.
By default, SMTP (Simple Mail Transfer Protocol) is used when
sending e-mail alerts. Compared with other mail transfer
methods, SMTP has the advantage that you will avoid
automatically triggered warnings from your e-mail client when
an e-mail alert is to be sent. Such automatically triggered
warnings may otherwise inform you that your e-mail client is
trying to automatically send e-mail messages on your behalf.
To access the E-Mail setup window, click the Email Settings...
button in the General Settings window (see page 68).
You enable the use of e-mail alerts separately for the Milestone Recording Server (see page 61)
and—if applicable—the Viewer application (see page 135):
Note: When enabling e-mail alerts, also consider the e-mail alert schedules configured for each
camera in the Camera/Alert Scheduler window (see page 64).
•Enable E-Mail (Recording Server): Select check box to enable the use of e-mail alerts
when the Milestone Recording Server is running. E-mail alerts will then be sent when the
following conditions apply:
o the Milestone Recording Server is running
o motion is detected or an event, for which the sending of an e-mail alert has been
defined, occurs
o motion is detected within a period of time for which an e-mail alert schedule has
been defined
•Enable E-Mail (Viewer): Select check box to enable the use of e-mail alerts in the Viewer
application. In effect, this will display the E-Mail Report button in the Viewer’s toolbar,
enabling users to send evidence via e-mail. If you clear the check box, the E-Mail Report
button will not be available in the Viewer’s toolbar.
Use of the e-mail feature is only possible when the Viewer is run on the surveillance system
server itself; not in a Viewer exported with video evidence.
Specifying Recipients
You specify the e-mail addresses to which e-mail alerts should be sent in the Recipient(s) field. If
specifying more than one e-mail address, separate the e-mail addresses with semicolons (example:
aa@aa.aa;bb@bb.bb;cc@cc.cc).
Note: If e-mail alerts are enabled for the Viewer, the content you specify in the Recipient(s) field
will appear as the default value in the Viewer’s dialog for sending evidence via e-mail. Users will be
able to overwrite this default value.
Specifying Sender Settings
Note: SSL (Secure Socket Layer) is not supported; if the sender belongs on a server that requires
SSL, the e-mail alerts will not work properly. Also, you may be required to disable any e-mail
scanners that could prevent the application sending the e-mail alert.
•Sender e-mail address: Type the e-mail address you wish to appear as the sender of the
e-mail alert.
•Outgoing mail (SMTP) server name: Type the name of the SMTP server which will be
used for sending the e-mail alerts.
•Server requires login: Select check box if a user name and password is required to use
the SMTP server.
•Username: Field available only when Server requires login is selected. Type the user name
required for using the SMTP server.
•Password: Field available only when Server requires login is selected. Type the password
• Subject text: Specify required subject text for e-mail alerts.
• Message text: Specify required message text for e-mail alerts. Note that camera
information as well as date and time information is automatically included in e-mail alerts.
Note: If e-mail alerts are enabled for the Viewer, the content you specify in the Subject text and
Message text fields will appear as default values in the Viewer’s dialog for sending evidence via e-
mail. Users will be able to overwrite these default values.
Specifying Image and Interval Options
You are able to specify whether e-mail alerts should include images, and how much time should
pass between alerts per camera:
•Include Image: Select check box to include images in e-mail alerts. When selected, a JPG
image from the time the triggering event occurred will be attached to each alert e-mail.
•Time btw. motion-related mails (minutes): Specify required minimum time (in
minutes) to pass between the sending of each e-mail alert per camera. Note that this
interval only applies for e-mail alerts generated by detected motion or database-related
events; e-mail alerts generated by other types of events will still be sent out whenever the
events occur.
Examples: If specifying 5, a minimum of five minutes will pass between the sending of
each motion- or database-related e-mail alert per camera, even if motion or database
events are detected in between. If specifying 0, e-mail alerts will be sent each time motion
or database events are detected, potentially resulting in a very large number of e-mail
alerts being sent. If using the value 0, you should therefore consider especially the motion
detection sensitivity configured for each camera in the Adjust Motion Detection window
(see page 46).
Testing Your E-Mail Alert Configuration
You are able to test your e-mail alert configuration by clicking the Test button. This will send a test
e-mail to the specified recipients. If Include Image is selected, the test e-mail will have a test JPG
image attached.
Input received from a wide variety of sources can be used to generate events in XProtect Basis+.
Events can in turn be used for automatically triggering actions in XProtect Basis+, such as starting
or stopping recording on cameras, triggering e-mail notifications, making PTZ cameras move to
specific preset positions, etc. Events can also be used for activating output.
Output units can be attached to output ports on many devices, allowing you to activate lights,
sirens, etc. from XProtect Basis+. Such external output can be activated automatically by events,
or manually from the Remote Client / Smart Client.
Types of Events
You specify which types of input should generate which types of events. Basically, three types of
events exist:
• On many devices you are able to attach external input units to input ports on the device.
Events based on input from such external input units—typically sensors attached to doors,
windows, etc.—are called input events. Some devices also have their own capabilities for
detecting motion, for detecting moving and/or static objects, etc. (typically configured in
the devices’ own software), in which case you are also able to use such detections from the
device as input events.
• Events may be based on XProtect Basis+ detecting motion on a camera. Such events are
called VMD (i.e. Video Motion Detection) events.
• Finally, events may be generated manually by users selecting them in their access clients.
Such manually selectable events are traditionally called event buttons.
Specifying Input, Events and Output
In XProtect Basis+, your main entry point for configuration of input, event and output handling is
the Administrator window (see page 26:
• By clicking the Administrator window’s I/O Setup... button, you open the I/O Setup window
(see page 74), in which you are able to specify each individual input event, VMD event
and output.
• By clicking the Administrator window’s Event Buttons... button, you open the Event Buttons
window (see page 85), in which you are able to specify event buttons for manually
triggering events-controlled activity.
• By clicking the Administrator window’s I/O Control... button, you open the I/O Control
window (see page 88), in which you are able to associate specific events with specific
output. This way you can, for example, specify that when motion is detected on a camera
(typically specified as a VMD event) a siren should automatically sound (output). If you
want users to be able to manually activate output when operating specific cameras, you
specify this in the Output Settings for [Device Name] [Camera Name] window (see page
Note: Before you specify use of external input and output units on a device, verify that sensor
operation is recognized by the device. Most devices are capable of showing this in their
configuration interfaces, or via CGI script commands. Also check the Milestone release notes to
verify that input and output controlled operations are supported for the device and firmware used.
Using Dedicated I/O Devices
In addition to IP video camera devices and IP video encoder devices it is possible to add a number
of dedicated I/O (input/output) devices to XProtect Basis+ (see How to Add a Device on page 32).
For information about which I/O devices are supported, refer to the release note.
When such I/O devices are added, input on the I/O devices can be used to generate events in
XProtect Basis+, and events in XProtect Basis+ can be used for activating output on the I/O
devices. This means that I/O devices can be used in your events-based system setup in the same
way as a camera.
Note: When using some I/O devices it is necessary for the surveillance system to regularly check
the state of the devices’ input ports in order to detect whether input has been received. Such state
checking at regular intervals is called polling. The interval between state checks, called a polling frequency, is specified in the Advanced window (see page 83). For such I/O devices, the polling
frequency should be set to the lowest possible value (one tenth of a second between state checks).
For information about which I/O devices require polling, see the release note.
I/O Setup
I/O Setup Window
You access the I/O Setup window by clicking the I/O Setup... button
in the Administrator window (see page 26). The I/O Setup window
lets you define input events, VMD (Video Motion Detection) events
and output for devices on your surveillance system. When events
occur, they can trigger one or more actions:
•Input events occur when input from an external input unit is received on a device’s input
port, for example when an external sensor detects that a door is opened. Some devices
also have their own capabilities for detecting motion, for detecting moving and/or static
objects, etc. (configured in the devices’ own software; typically by accessing a browserbased configuration interface on the device’s IP address), in which case such detections
from the device can also be used as input events.
• VMD events occur when XProtect Basis+ detects motion on a particular camera.
• Outputs are used for activating external output units, for example for switching on lights or
sounding a siren.
The I/O Setup window is used for defining which input events, VMD events and outputs should be
available on your system. Input and VMD events can be used for triggering outputs or for
triggering various actions on the surveillance system itself, such as for starting or stopping
cameras (configured in the Camera/Alert Scheduler window – see page 64) or for moving a PTZ
camera to a particular preset position (configured in the Event window (for PTZ preset positions on
event) – see page 54).
Once you have defined input events, VMD events and outputs, you are able to associate specific
input events or VMD events with specific outputs in the I/O Control window(see page 88), so that,
for example, lights are switched on when a door is opened or when motion is detected on a
camera. Outputs may also be triggered by motion detection on a specific camera—even without a
defined VMD event—or manually through the Smart Client (see page 140); both are configured in
the Output Settings for [Device Name] [Camera Name] window (see page 88).
Note: Before you specify inputs and outputs for a device, verify that sensor operation is recognized
by the device. Most devices are capable of showing this in their configuration interfaces, or via CGI
script commands. Also check Milestone’s release notes to verify that input and output controlled
operations are supported for the device and firmware used.
Using the I/O Setup Window’s Defined Events List and Buttons
The I/O Setup window features a Defined events list, in which input, output and VMD (Video Motion
Detection) events defined for each device are listed. The window furthermore features a number of
buttons for use when adding and configuring the events:
Button Description
Add new
event...
Used for defining input events on the device selected in the Defined events
list. Depending on the type of device, you may be able to define one or more
input events on the device. Some devices do not support input/output at all.
Refer to the release notes for device-specific information.
Devices Capable of Handling One Input Event Only
If the device is capable of handling one input event only, the button will open
the Add New Event window (for devices capable of handling one input event
only) – see page 77 – in which you define the input event, and any e-mail
alerts to be associated with it.
If you have already defined an input event on a device capable of handling
one input event only, the Add new event... button will not be available when
the device is selected in the Defined events list.
However, if you click the plus sign next to the device in the Defined events
list, and select the defined input event, the Add new event... button becomes
available for defining timer events (see Timer Events in the following).
Devices Capable of Handling Several Input Events
If the device is capable of handling more than one input event, the button will
open the Multiple Input Events window (see page 78), in which you define
which of the device’s possible input events should be enabled, and whether
any alerts should be associated with enabled input events.
Timer Events
When you click the plus sign next to the device in the Defined events list, and
select a defined input event, the Add new event... button becomes available
for defining timer events: When clicked, the button will open the New Timer
window (see page 81), in which you are able to specify the settings for timer
events.
Timer events are separate events, triggered by the input event under which
they are defined. Timer events occur a specified number of seconds or
minutes after the input event under which they are defined. Timer events may
be used for a wide variety of purposes; the following are examples only:
• A camera starts based on an input event, e.g. when a door is opened,
a timer event stops the camera after 15 seconds
• A camera starts and the lights are switched on based on an input
event, e.g. when a door is opened, a timer event stops the camera
after one minute, and another timer event switches the lights off after
two minutes
Add new
output event...
Add VMD
Event (Motion
Detection)
Opens the Add New Output window (see page 82), in which you are able to
specify a name for the required output event, which of the device’s output
ports to use, and how long to keep the output for.
Lets you add a VMD (Video Motion Detection) event to the device selected in
the Defined Events list. VMD events are events triggered when XProtect
Basis+ detects motion on a specific camera, based on the motion detection
settings defined in the Adjust Motion Detection window (see page 46).
Note: In addition to XProtect Basis+’s motion detection, some devices also
have their own capabilities for detecting motion (configured in the devices’
own software; typically by accessing a browser-based configuration interface
on the device’s IP address). Events based on motion detected on a device itself are not VMD Events; they are input events, since they are based on
input from the device.
VMD events can be used just like regular input events. For example, a PTZ
(Pan/Tilt/Zoom) camera could move to a specific preset position when a VMD
event occurs. Only one VMD event can be defined per camera. In order to
avoid the risk of an excessively high number of VMD events being generated,
a VMD event cannot occur more frequently than every five seconds.
The Add VMD Event (Motion Detection) button works slightly different
depending on whether the selected device is a single-camera device or a
multi-camera device, such as a video encoder:
•Single-camera devices: Clicking the Add VMD Event (Motion
Detection) button will instantly add a VMD event to the selected
device, provided a VMD event has not already been defined for the
device.
•Multi-camera devices: Clicking the Add VMD Event (Motion
Detection) button will open a simple dialog in which you select the
required camera. This way you are able to define a VMD event for
each camera on a multi-camera device.
Edit selected... Lets you edit the settings for an item selected in the Defined events list.
For devices capable of handling a single input event only, the button will open
the Edit Event window (for editing input events) – see page 80.
For devices capable of handling several input events, the button will open the
Multiple Input Events window (see page 78).
If the selected item is a timer event, the button will open the New Timer
window (see page 81).
If the selected item is an output, the button will open the Edit Output window
(see page 83).
Lets you remove an event selected in the Defined events list.
Note: The selected event will be removed without further warning.
Opens the Advanced window (see page 83), in which you are able to specify
network settings to be used in connection with event handling: which ports to
use for FTP, alerts and SMTP input/output events as well as which polling
frequency to use on devices requiring polling.
Add New Event Window (for Devices Capable of Handling
One Input Only)
The Add New Event window (for devices capable of handling one input event only) lets you specify
the settings for an input event on devices capable of handling one input event only. You access the
Add New Event window (for devices capable of handling one input event only) by selecting the
required device and clicking the Add new event... button in the I/O Setup window (see page 74).
Note that this only applies when the selected device is capable of handling a single input event
only. Some devices are capable of handling several input events, in which case a different window,
the Multiple Input Events window (see page 78), will open when the Add new event... button is
clicked.
Note: Before you specify input events for a device, verify that sensor operation is recognized by
the device. Most devices are capable of showing this in their configuration interfaces, or via CGI
script commands. Also check the XProtect Basis+ release note to verify that input-controlled
operations are supported for the device and firmware used.
Add New Event Window’s Fields
The Add New Event window (for devices capable of handling one input event only) contains the
following fields:
Field, Check
Box
External
sensor
connected
to
Sensor
connected
through
Event occurs
when input
goes
Description
Read-only field, displaying the name of the device on which the input event is
defined.
Lets you select which of the device’s input ports the sensor used for the input
event is connected to.
Lets you select whether input event should be triggered when the signal on
the input sensor rises or falls:
• Low: Trigger input event when the signal on the sensor is falling
• High: Trigger input event when the signal on the sensor is rising
For exact information about what constitutes a falling and a rising signal
respectively, refer to documentation for the sensor and device in question.
Lets you specify a name for the input event.
Note: Event names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support event names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
Select check box to send an e-mail alert when the input occurs. In order to be
able to use e-mail alerts, the e-mail alert feature must have been set up in the
E-Mail setup window (see page 70).
Available only if the Send e-mail if this event occurs check box is selected.
Select check box to include an image, recorded at the time the input event is
triggered, in the e-mail alert, then select the required camera in the list next
to the check box.
Multiple Input Events Window
The Multiple Input Events window is used for devices capable of handling several input events. It
lets you define which of the device’s possible input events should be enabled, and whether any
alerts should be associated with enabled input events.
Note: Before you specify input events for a device, verify that sensor operation is recognized by
the device. Most devices are capable of showing this in their configuration interfaces, or via CGI
script commands. Also check Milestone’s release notes to verify that input and output controlled
operations are supported for the device and firmware used.
You access the Multiple Input Events window by clicking the Add new event... button in the I/O Setup window (see page 74). Note that this only applies when the device selected in the I/O Setup
window is capable of handling several input events. Some devices are capable of handling a single
input event only, in which case a different window, the Add New Event window (for devices capable
of handling one input event only) – see page 77, will open when the Add new event... button is
clicked.
Read-only field, displaying the name of the device on which the input events
are defined.
Lists available input events for the device, typically with an input event for
rising and falling signals on each of the device’s input ports. For exact
information about what constitutes the various input events, refer to
documentation for the sensors and device in question.
My list contains event related to motion and/or object detection;
what’s this? Some devices have their own capabilities for detecting motion
and/or moving/static objects. A motion or object detection-related input event
is very likely to be an option from such a device. The settings determining this
kind of detection are configured on the device itself; typically by accessing a
browser-based configuration interface on the device’s IP address. For more
information, refer to the documentation for the device in question.
Enabled
Input
Event(s)
>> You enable an event by selecting it in the Available Input Event(s) list, then
<< Lets you move an input event selected in the Enabled Input Event(s) list to
Edit Lets you edit the settings for an input event selected in the Enabled Input
Lists enabled input events for the device. You enable an event by selecting it
in the Available Input Event(s) list, then clicking the >> button. See
description in the following.
clicking the >> button to open the Add New Event window (for devices
capable of handling several input events) – see page 79 – in which you specify
a name for the input event, and any e-mail or SMS alerts to be associated
with it. When you click OK in the Add New Event window (for devices capable
of handling several input events), the selected input event is automatically
transferred from Available Input Event(s) list to the Enabled Input Event(s)
list.
the Available Input Event(s) list, thus disabling it.
Event(s) list.
Add New Event Window (for Devices Capable of Handling
Several Inputs)
The Add New Event window (for devices capable of handling several input events) lets you specify
the settings for a particular input event on devices capable of handling several input events. You
access the Add New Event window (for devices capable of handling several input events) by
clicking the >> button in the Multiple Input Events window (see page 78).
Note: Before you specify input events for a device, verify that sensor operation is recognized by
the device. Most devices are capable of showing this in their configuration interfaces, or via CGI
script commands. Also check Milestone’s release notes to verify that input and output controlled
operations are supported for the device and firmware used.
Add New Event Window’s Fields
The Add New Event window (for devices capable of handling several input events) contains the
following fields:
Field, Check
Box
External
event name
Description
Lets you specify a name for the particular input event.
Note: Event names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support event names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
Select check box to send an e-mail alert when the input occurs. In order to be
able to use e-mail alerts, the e-mail alert feature must have been set up in the
E-Mail setup window (see page 70).
Available only if the Send e-mail if this event occurs check box is selected.
Select check box to include an image, recorded at the time the input event is
triggered, in the e-mail alert, then select the required camera in the list below
the check box.
Edit Event Window (for Editing Input Events)
The Edit Event window (for editing input events) lets you edit the settings for an existing input
event on devices capable of handling one input event only. You access the Edit Event window (for
editing input events) by selecting the required device and clicking the Edit selected... button in the I/O Setup window (see page 74). Note that this only applies when the selected device is capable of
handling a single input event only. Some devices are capable of handling several input events, in
which case a different window, the Multiple Input Events window (see page 78), will open when the
Edit selected... button is clicked.
Edit Event Window’s Fields
The Edit Event window (for editing input events) contains the following fields:
Field Description
External
sensor
connected
to
Sensor
connected
through
Event occurs
when input
goes
External
event name
Read-only field, displaying the name of the device on which the input event is
defined.
Lets you select which of the device’s input ports the sensor used for the input
event should be connected to.
Lets you select whether the input event should be triggered when the signal
on the input sensor rises or falls:
• Low: Trigger input event when the signal on the sensor is falling
• High: Trigger input event when the signal on the sensor is rising
For exact information about what constitutes a falling and a rising signal
respectively, refer to documentation for the sensor and device in question.
Lets you edit the name of the input event.
Note: Event names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support event names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
Select check box to send an e-mail alert when the input occurs. In order to be
able to use e-mail alerts, the e-mail alert feature must have been set up in the
E-Mail setup window (see page 70).
Available only if the Send e-mail if this event occurs check box is selected.
Select check box to include an image, recorded at the time the input event is
triggered, in the e-mail alert, then select the required camera in the list next
to the check box.
New Timer Window
The New Timer window lets you specify the settings for timer events. Timer
events are separate events, triggered by the input event, VMD event or event
button under which they are defined.
seconds or minutes after the event under which they are defined has occurred or
the event button under which they have been defined has been clicked.
Timer events may be used for a wide variety of purposes; the following are
examples only:
• A camera starts recording based on an input event, e.g. when a door is opened; a timer
event stops the recording after 15 seconds
• Lights are switched on and a camera starts recording based on a VMD event, i.e. when
motion is detected; a timer event stops the recording after one minute, and another timer
You are able to access the New Timer window in three ways:
event switches the lights off after two minutes
● If dealing with input and VMD events in the I/O Setup window (see page 74): When you click
the plus sign (
event, you are able to click the Add new event... button to access the New Timer window.
● If dealing with event buttons in the Event Buttons window (see page 85): When selecting an
already specified event button in the Defined Events list, you are able to click the Add new event... button to access the New Timer window.
) next to a device in the window’s Defined events list, and select a defined
Read-only field, displaying the name of the event or event button under which
the timer event is defined.
Lets you specify a name for the timer event.
Note: Event names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support event names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
Lets you specify the amount of time that should pass between the event
occurring/event button being clicked and the timer event. Specify the required
amount of time in either seconds or minutes. Example:
• The timer event should occur 15 seconds after the event under which
it is defined has occurred
• The timer event should occur 2 minutes after the event button under
which it has been defined has been clicked
Add New Output Window
The Add New Output window lets you specify the settings for an output
on a device
required device and clicking the Add new output event... button in the
I/O Setup window (see page 74). If the device does not support output,
the button will not be available.
Note: Before you specify output for a device, verify that the output is supported by the device.
Most devices are capable of showing this in their configuration interfaces, or via CGI script
commands. Also check the XProtect Basis+ release note to verify that output is supported for the
device and firmware used.
. You access the Add New Output window by selecting the
Add New Output Window’s Fields
Field Description
External
output
connected
to
Output
connected
on
Keep output
for
External
output name
Read-only field, displaying the name of the device on which the output event
is defined.
Lets you select which of the device’s output ports the output is connected to.
Many cameras only have a single output port; in that case simply select
Output 1.
Lets you specify the amount of time for which the output should be applied.
Specify the required amount of time in either 1/10 seconds or
seconds.Example: The output should be kept for five tenths of a second.
Note: Some devices are only able to apply outputs for a relatively short time,
for example max. five seconds. Refer to the documentation for the device in
question for exact information.
Lets you specify a name for the output. The name will appear on the
button/list with which users will be able to manually trigger the output.
Note: Output names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support output names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
When you have defined settings for the output in question, you are able to test the output by
clicking the Test Output button.
Edit Output Window
The Edit Output window lets you specify the settings for an output on a
device. You access the Edit Output window by selecting the required
output in the I/O Setup window (see page 74), then clicking the Edit selected... button.
Edit Output Window’s Fields
Field Description
External
output
connected
to
Output
connected
on
Keep output
for
External
output name
Read-only field, displaying the name of the device on which the output event
is defined.
Lets you edit which of the device’s output ports the output is connected to.
Lets you edit the amount of time for which the output should be applied.
Specify the required amount of time in either 1/10 seconds or seconds.
Example: The output should be kept for five tenths of a second.
Note: Some devices are only able to apply outputs for a relatively short time,
for example max. five seconds. Refer to the documentation for the device in
question for exact information.
Lets you edit the name of the output.
Note: Output names must not contain the following characters: < > & ‘ " \ / :
* ? | [ ]. Some camera devices only support output names of a certain length
and/or with a certain structure. Refer to the camera’s documentation for exact
details.
Testing the Defined Output
When you have defined settings for the output in question, you are able to test the output by
clicking the Test Output button.
Advanced Window
The Advanced window lets you specify network settings to be used in
connection with event handling.
clicking the Advanced... button in the I/O Setup window (see page
Alert Port Lets you specify port number to use for handling event-based alerts. Default
SMTP Port Lets you specify port number to use for sending event information from the
Polling
Frequency
[1/10 sec]
Lets you specify port number to use for sending event information from the
device to the surveillance system via FTP. Default port is port 21.
port is port 1234.
device to the surveillance system via SMTP. Default port is port 25.
For a small number of devices, primarily I/O devices (see Using Dedicated I/O
Devices on page 74), it is necessary for the surveillance system to regularly
check the state of the devices’ input ports in order to detect whether input has
been received. Such state checking at regular intervals is called polling. The
Polling Frequency field lets you specify the interval between state checks.
Interval is specified in tenths of a second. Default value is 10 tenths of a
second (i.e. one second).
For I/O devices it is highly recommended that the polling frequency is set to
the lowest possible value (one tenth of a second between state checks).
For information about which devices require polling, see the release note.
Event Buttons
What Is an Event Button?
Event buttons let users manually trigger events from the Smart Client (see page 140). In the
Smart Client, event buttons are actually not buttons; instead users manually trigger events by
selecting them from a list.
You are able to configure event buttons to suit the exact needs of your organization. Your main
entry point for configuring event buttons is the Administrator window (see page 26): Clicking the
Administrator window’s Event Buttons... button will open the Event Buttons window (see below), in
which you specify each individual event button.
Event buttons can be used for a wide variety of purposes, for example:
• As start and stop events for use in the Camera/Alert Scheduler window (see page 64). For
example, you can make a camera start or stop transferring video to the surveillance
system when an event button is selected.
• As start and stop events for use in the Camera Settings for [Device Name] [Camera Name]
window (see page 39). For example, you can make a camera use a higher frame rate when
an event button is selected, or you can use an event button for manually triggering PTZ
preset positions on event (see page 54).
• For triggering outputs. Particular outputs can be associated with the clicking of an event
button; you do this in the I/O Control window (see page 88).
• In combinations. For example, the clicking of an event button could make a camera start
transferring video to the surveillance system while two outputs are triggered and an e-mail
Event buttons can be global (available for all cameras) or tied to a particular camera (only available
when the camera in question is selected).
alert is sent to relevant people.
Event Buttons Window
The Event Buttons window lets you specify event buttons. When
specified, event buttons become available in the Smart Client –
see page 140 (in the Smart Client, event buttons are actually not
buttons; instead users manually trigger events by selecting them
from a list). Event buttons can be global (available for all cameras)
or tied to a particular camera (only available when the camera is
selected). You access the Event Buttons window by clicking the
Event Buttons... button in the Administrator window (see page
26).
Defined Events List
The Event Buttons window features a list of specified event buttons. When event buttons have
been defined, you are able to expand elements in the list (by clicking
defined event buttons; global event buttons as well as event buttons specified for individual
cameras. Example:
Example: A global event button with an associated
timer event has been specified. Also, two ev ent
buttons have been specified for an individual camera.
) to get an overview of all
Specifying Event Buttons and Timer Events
To specify an event button, first determine whether you want the event button to be available
globally or for a particular camera only.
Specifying Global Event Buttons
To specify a global event button, select the Global entry at the top of the Defined Events list, then
click the Add new event... button. This will open the Add New Event window (for adding event
buttons) – see page 86, in which you specify a name for the event button as well as whether the
event button should trigger any e-mail alerts when clicked. When you click OK in the Add New Event window (for adding event buttons), you are returned to the Event Buttons window, in which
your new event button will appear in the Defined Events list.
Specifying Camera-Specific Event Buttons
To specify an event button for a specific camera, select the required camera in the Defined Events
list, then click the Add new event... button. This will open the Add New Event window (for adding
event buttons) – see page 86, in which you specify a name for the event button as well as whether
the event button should trigger any e-mail alerts when clicked. When you click OK in the Add New
Event window (for adding event buttons), you are returned to the Events window (for specifying
event buttons), in which your new event button will appear in the Defined Events list.
Specifying Timer Events
When you have specified an event button, you are able to associate timer events with the event
button. Timer events are separate events, occurring a specified number of seconds or minutes after
the event button has been clicked. Timer events may be used for a wide variety of purposes; the
following are examples only:
• A camera starts when an event button is selected in the Smart Client (see page 140); a
timer event stops the camera after 15 seconds
• A camera starts and the lights are switched on when an event button is selected in the
Smart Client; a timer event stops the camera after one minute, and another timer event
switches the lights off after two minutes
To define a timer event for an event button, select the required event button in he Defined Events
list, then click the Add new event... button. When you click the Add new event... button while an
already specified event button is selected in the Defined Events list, the New Timer window (see
page 81) opens, allowing you to specify the required timer event.
Tip: You may specify several timer events under a single event button. However, you cannot
use a timer event under another timer event.
Editing Event Buttons and Timer Events
To edit an event button, or a timer event specified under an event button, select the required
event button or timer event in the Defined Events list, then click the Edit selected... button. If you
have selected an event button, clicking the Edit selected... button will open the Edit Event window
(for editing event buttons) – see page 87. If you have selected a timer event, clicking the Edit selected... button will open the New Timer window (see page 81).
Associating Event Buttons with External Outputs
As is the case with input events (see External Input & Output described on page 73), you are able
to associate an event button with specific external outputs. This way, external output, for example
the sounding of a siren, can be triggered automatically when an event button is clicked. Like with
input and VMD events, the association between event buttons and outputs is made in the I/O Control window (see page 88).
Add New Event Window (for Adding Event Buttons)
The Add New Event window (for adding event buttons) lets you specify the settings for an event
button. You access the Add New Event window (for adding event buttons) from the Event Buttons
window (see page 85): Select an entry (either global or for a specific camera) in the Defined Events list, then click the Add new event... button.
Lets you specify a name for the event button.
Note: Event button names must not contain the following characters: < > & ‘
" \ / : * ? | [ ]
Select check box to send an e-mail alert when the event button is clicked. In
order to be able to use e-mail alerts, the e-mail alert feature must have been
set up in the E-Mail setup window (see page 70).
Available only if the Send e-mail if this event occurs check box is selected.
Select check box to include an image, recorded at the time the event button is
clicked, in the e-mail alert, then select the required camera in the list below
the check box.
Edit Event Window (for Editing Event Buttons)
The Edit Event window (for editing event buttons) lets you edit the settings for an existing event
button
.
You access the Edit Event window (for editing event buttons) from the Event Buttons window (see
page 85), by first selecting the required event button in the Defined Events list, then clicking the
Edit selected... button.
Edit Event Window’s Fields
The Edit Event window (for editing event buttons) contains the following fields:
Field Description
Button
related to
Manual
event name
Send e-mail
if this event
occurs
Include
image from
camera
Read-only field, displaying the name of the camera for which the event button
has been specified.
If the field displays Global, the event button is a global event button (available
for all cameras).
Lets you edit the name of the event button.
Note: Event button names must not contain the following characters: < > & ‘
" \ / : * ? | [ ]
Select check box to send an e-mail alert when the event button is clicked. In
order to be able to use e-mail alerts, the e-mail alert feature must have been
set up in the E-Mail setup window (see page 70).
Available only if the Send e-mail if this event occurs check box is selected.
Select check box to include an image, recorded at the time the event button is
clicked, in the e-mail alert, then select the required camera in the list below
the check box.
In the I/O Control window you are able associate particular
events and event buttons with one or more particular
outputs. This way you are able to define that when a
selected event occurs, or when a particular event button is
clicked, one or more selected outputs will be triggered.
Note: Use of features in the I/O Control window requires
that events and outputs have been specified (see About Input, Events & Output ... on page 73).
You access the I/O Control window from the Administrator
window (see page 26), by clicking the I/O Control...
button.
Associating Event with Particular Outputs
When associating an event with one or more outputs, you are able to select between all outputs
defined on the XProtect Basis+ system; you are not limited to selecting outputs defined on a
particular device.
To associate a particular event with a particular output, do the following:
1. Select the required event in the Available Events list in the left side of the I/O Control
window.
Tip: Events as well as event buttons may be listed. When you select an event or event
button in the Available Events list, you can view detailed information about the selected
event or event button under Event Information in the lower part of the window.
2. Select the required output in the list of available outputs (the list in the middle of the
window).
3. Click the >> button located below the Selected Outputs list. This will copy the selected
output to the Selected Outputs list. When the selected event occurs, or when the selected
event button is clicked, the selected output will be triggered.
You are able to associate an event or an event button with more than one output: Simply repeat
the process for each required output. To remove an output from the Selected Outputs list, simply
select the required output, and click the << button located below the Selected Outputs list.
Output Settings for [Device Name]
[Camera Name] Window
In the Output Settings for [Device Name] [Camera Name]
window you are able to associate a camera with particular
external outputs, defined in the I/O Setup window (see page
74), for example the sounding of a siren or the switching on of
lights. The associated outputs can be triggered automatically
when motion is detected as well as manually through output
buttons available in the Remote Client (see page 142) and Smart
Client (see page 140).
You access the Output Settings for [Device Name] [Camera Name] window from the Camera Settings for [Device Name] [Camera Name] window (see page 39), by clicking the Outputs...
button.
Associating Outputs with Manual Control and Detected Motion
Note: Use of features in the Output Settings for [Device Name] [Camera Name] window requires
that output has been defined in the I/O Setup window (see page 74).
You have a high degree of flexibility when associating a camera with particular outputs:
• You are able to select between all available outputs, i.e. outputs defined as output events for
the camera itself as well as outputs defined as output events for other devices on the XProtect
Basis+ system
• The same output may be used for manual control through an output button as well as for
automatic triggering when motion is detected
Selecting Output for Manual Control
You are able to specify outputs to be triggered manually from a list in the Remote Client (see page
142) or Smart Client (see page 140).
1. Select the required output in the All Outputs list in the left side of the Output Settings for
[Device Name] [Camera Name] window. When you select an output in the All Outputs list,
you can view detailed information about the selected output under Output Information in
the lower part of the window.
2. Click the >> button located between the All Outputs list and the On Manual Control list.
This will copy the selected output to the On Manual Control list. An unlimited number of
outputs may be selected this way.
You are able to determine each output’s position in the Remote Client’s and Smart Client’s output
list by moving the selected output up or down in the On Manual Control list with the up and down
buttons located to the right of the list. The selected output is moved up one step each time you
click the up button. Likewise, each time you click the down button, the selected output is moved
down one step.
To remove an output from the On Manual Control list, simply select the required output, and click
the << button located between the All Outputs list and the On Manual Control list.
Selecting Output for Use on Motion Detection
You are able to select outputs to be triggered automatically when motion is detected in video from
the camera. This feature does not require that a VMD (Video Motion Detection) event has been
defined for the camera in the I/O Setup window (see page 74).
1. Select the required output in the All Outputs list in the left side of the Output Settings for
[Device Name] [Camera Name] window.
Tip: When you select an output in the All Outputs list, you can view detailed
information about the selected output under Output Information in the lower part of the
window.
2. Click the >> button located between the All Outputs list and the On Motion Detected list.
This will copy the selected output to the On Motion Detected list.
To remove an output from the On Motion Detected list, simply select the required output, and click
the << button located between the All Outputs list and the On Motion Detected list.
Events can be used for automatically triggering actions in XProtect Basis+, such as starting or
stopping recording on cameras, triggering e-mail notifications, making PTZ cameras move to
specific preset positions, activating output, etc.
Several types of events exist (see About Input, Events & Output ... on page 73). In the following
you will see how to define events based on input received from external input units—such as
sensors attached to doors, windows, etc.—connected to cameras or other devices on an XProtect
Basis+ system.
To add an input-based event, do the following:
1. In the Administrator window (see page 26), click the I/O Setup button.
This will open the I/O Setup window (see page 74).
2. In the I/O Setup window, first select the camera or other
device to which the input unit is connected, then click
the Add new event... button. This will open the Add New Event window.
Note: Some cameras/devices are capable of handling
one input event only; others are capable of handling
several input events. The content of the Add New Event
window varies accordingly. For simplicity reasons, the
following steps will describe adding an event on a
camera/device capable of handling one input event only.
3. In the Add New Event window (for devices capable of handling one input event only), see
page 77, the External sensor connected to field will show the name of the selected camera
or other device. Now specify information in the following fields:
• Sensor connected through: Select the camera/device input port on which the input
• Event occurs when input goes: Select whether the input event should be triggered
• External event name: Specify a name for the event. Note that event names must
• (Optional) If requiring an e-mail alert to be sent automatically when the event
When ready, click OK. This will return you to the I/O Setup window (see page 74).
4. In the I/O Setup window, your newly defined event is now listed (you may have to click the
expand icon
unit is connected. Some cameras/devices only have a single input port; in that case
simply select Input 1.
when the signal on the input sensor rises (High) or falls (Low).
not contain the following characters: < > & ‘ " \ / : * ? | [ ]
occurs, select the Send e-mail if this event occurs check box. Note that in order to
be able to use e-mail alerts, the e-mail alert feature must have been set up in the
E-Mail setup window (see page 70). If requiring an image (recorded at the time of
the event) to be included in the e-mail alert, also check the Include image from camera check box and select the required camera in the list next to the check box.
in front of the name of the camera or other device to see the listing):
Click OK to close the I/O setup window and return to the Administrator window (see page
26). For system administrators defining actions to be triggered by events, the event will
now be selectable in line with other events defined on XProtect Basis+.
How to Add an Event Button
Events can be used for automatically triggering actions in XProtect Basis+, such as starting or
stopping recording on cameras, triggering e-mail notifications, making PTZ cameras move to
specific preset positions, activating output, etc. An event may also trigger several actions
simultaneously.
Several types of events exist (see About Input, Events & Output ...on page 73). In most cases,
events occur and actions are triggered without the need for human intervention by XProtect Basis+
users: System administrators define the criteria for each event, for example a certain amount of
detected motion or input from a specific sensor; when the criteria are met, the system interprets it
as an event, and automatically triggers the required actions.
However, you may also want users to be able to manually force an event to occur. For this
purpose, XProtect Basis+ lets you define event buttons. Event buttons let users manually trigger
events from the Smart Client. In the Smart Client, event buttons are actually not buttons; instead
users manually trigger events by selecting them from a list. See also 84 for examples of the many
ways in which you can use event buttons.
To add an event button, do the following:
1. In the Administrator window (see page 26), click the Event Buttons... button.
This will open the Event Buttons window (see page 85).
2. In the Event Buttons window, first select the camera or other
device for which you want the event button to be available,
then click the Add new event... button.
Note that you are also able to make the event button
globally available (i.e. available to users regardless of which
camera/device they have selected in the Smart Clients.
To make the event button globally available, simply select
Global (at the top of the list) instead of a particular
camera/device. This will open the Add New Event window (for adding event buttons) – see
page 86.
3. In the Add New Event window (for adding event buttons), the Button related to field will
show the name of the selected camera or other device. If you are adding a globally
available event button, the field will display Global. Now specify information in the following
fields:
●Manual event name: Specify a name for the event button. Note that event names
must not contain the following characters: < > & ‘ " \ / : * ? | [
● (Optional) If requiring an e-mail alert to be sent automatically when the event
occurs, select the Send e-mail if this event occurs check box. Note that in order to be
able to use e-mail alerts, the e-mail alert feature must have been set up in the E-Mail setup window (see page 70). If requiring an image (recorded at the time of the
event) to be included in the e-mail alert, also check the Include image from camera
check box and select the required camera in the list next to the check box.
When ready, click OK. This will return you to the Event buttons window (see page 85).
4. In the Event Buttons window, your newly defined event button is now listed (you may have
to click the expand icon
listing):
in front of the name of camera or other device to see the
Click OK to close the Event Buttons window and return to the Administrator window (see
page 26). The defined event button will now be available in the Smart Client (see page
140), as described in the beginning of this text. Note that individual users’ rights may
prevent them from accessing specific cameras and/or events in the Smart Client; such
rights are defined through the Image Server Administrator window (see page 109). For
system administrators defining actions to be triggered by events, the event button will now
be selectable in line with other events defined on XProtect Basis+.
How to Add a VMD Event
Events can be used for automatically triggering actions in XProtect Basis+, such as starting or
stopping recording on cameras, triggering e-mail notifications, making PTZ cameras move to
specific preset positions, activating output, etc. An event may also trigger several actions
simultaneously. Several types of events exist (see About Input, Events & Output ... on page 73). In
the following, you will see how to define an event based on XProtect Basis+ detecting motion on a
particular camera (VMD simply means Video Motion Detection). Once the VMD event is defined,
you will be able to select it when further configuring XProtect Basis+.
Tip: If you are specifically looking for information about how to configure motion detectiontriggered activation of an output device only (such as a siren, a strobe light, etc.), see How to Add
a Motion-Triggered Output on page 98.
Note: In addition to XProtect Basis+’s motion detection, some devices also have their own
capabilities for detecting motion (configured in the devices’ own software; typically by accessing a
browser-based configuration interface on the device’s IP address). Events based on motion
detected on a device itself are not VMD Events; they are input events, since they are based on
input from the device.
Note: Your motion detection settings for the camera in question will entirely determine when
motion is detected, and thus when the VMD event will occur. See the description of the Adjust Motion Detection window (page 46) for more information. Also note that in order not to generate
an excessively high number of VMD events during periods with lots of motion, a VMD event cannot
occur more frequently than every five seconds.
1. In the Administrator window (see page 26), click the I/O Setup button.
This will open the I/O Setup window (see page 74).
2. In the I/O Setup window, first select the device on which
motion must be detected in order for the event to occur,
then click the Add VMD Event (Motion Detection) button.
This will automatically add a VMD event to the selected
device (unless the selected device is a video encoder,
see below).
o If the selected device is a video encoder,
several cameras may be attached to the device,
and a separate dialog will prompt you to select
the required camera:
3. In the I/O Setup window (see page 74), your newly defined VMD event will now be listed
(you may have to click the expand icon
in front of the name of the device to see the
listing):
Click OK to close the I/O Setup window (see page 74) and return to the Administrator
window (see page 26). For system administrators defining actions to be triggered by
events, the VMD event will now be selectable in line with other events defined on XProtect
Basis+.
Tip: For video encoder devices, you are able to define a VMD event for each connected
camera; simply repeat above process.
How to Add a Timer Event
Timer events are separate events, triggered by the input event, VMD event or event button under
which they are defined. Timer events occur a specified number of seconds or minutes after the
event under which they are defined has occurred or the event button under which they have been
defined has been clicked.
Timer events may be used for a wide variety of purposes; the following are examples only:
• A camera starts recording based on an input event, e.g. when a door is opened; a timer
event stops the recording after 15 seconds
• Lights are switched on and a camera starts recording based on a VMD event, i.e. when
motion is detected; a timer event stops the recording after one minute, and another timer
event switches the lights off after two minutes
To define a timer event, do the following:
1. A timer event requires that an input event, VMD event or event button has already been
defined. Begin by selecting the required event or event button:
• If Adding the Timer Event under an Already Defined Input or VMD Event:
Click the Administrator window’s (see page 26) I/O Setup... button to open the I/O
Setup window (see page 74): In the I/O Setup window’s Defined events list, click
the plus sign (
) next to the required device, select the required input or VMD
event, then click the Add new event... button to open the New Timer window (see
page 81).
•If Adding the Timer Event under an Already Defined Event Button: Click the
Administrator window’s (see page 26) Event Buttons... button to open the Event
Buttons window (see page 85): In the Event Buttons window’s Defined Events list,
select the required event button, then click the Add new event... button to open
the New Timer window.
2. In the New Timer window (see page 81), the Timer event is started by field will show the
name of the selected event or event button. Now specify information in the following fields:
•Timer event name: Specify a name for the timer event.
Note that event names must not contain the following
characters: < > & ‘ " \ / : * ? | [ ]
•Timer event occurs after: Specify the amount of time that
should pass between the event occurring/event button being
clicked and the timer event, in either seconds or minutes.
When ready, click OK.
3. In the window from which you opened the New Timer window (see page 81), your newly
defined timer event will now be listed:
imer event (in this example associated with a
VMD event) listed in I/O Setup window (see
page 74). You may have to click the expand
icon
in front of the name of the required
device as well as the required main event to
see the timer event.
imer event (associated with an event button)
listed in Event Buttons window (see page 85).
You may have to click the expand icon
front of the name of the required device as
well as the required main event to see the
timer event.
in
Click OK to return to the Administrator window (see page 26).
For system administrators defining actions to be triggered by events, the timer event will
now be selectable in line with other events defined on XProtect Basis+.
How to Add a Manually Controlled Output
Output (e.g. lights, sirens, etc.) connected to cameras or other devices can be triggered manually
when viewing live video in the Remote Client (see page 142) and Smart Client (see page 140). In
the Remote Client and Smart Client, the output is triggered by selecting the required output from a
list on the client’s Live tab.
The output does not necessarily have to be physically connected to the specific camera from which
a Remote Client /Smart Client user views live video; the output can be connected to any device on
your XProtect Basis+ system.
To add an output for manual control, do the following:
Note: In the following, it is assumed that the required output unit has been connected to the
output port on the required camera or other device, but that it has not yet been defined on your
XProtect Basis+ system. If you have already defined the output on your system, begin at step 5.
1. In the Administrator window (see page 26), click the I/O Setup button.
This will open the I/O Setup window (see page 74).
2. In the I/O Setup window, first select the camera or other device to which the output unit is
connected, then click the Add new output event... button:
This will open the Add New Output window (see page 82).
3. In the Add New Output window, the External output connected to field will show the name
of the selected camera or other device. Now specify information in the following fields:
•Output connected on: Select the camera/device output port on which the output
unit is connected. Many cameras/devices only have a single output port; in that
•Keep output for: Specify the amount of time for which the output should be active
when triggered, in either 1/10 seconds or seconds.
Note: Some devices are only able to apply outputs for a relatively short time, for
example max. five seconds. Refer to the documentation for the device in question
for exact information.
•External output name: Specify a name for the output. The name will appear on
the list with which users will be able to manually trigger the output. Note that
output names must not contain the following characters: < > & ‘ " \ / : * ? | [ ]
In the example to the right, we have specified that a
siren connected on a camera’s Output 1 port should
sound for five seconds when triggered:
Tip: You are able to test the output by clicking the
Test Output button.
When ready, click OK. This will return you to the I/O
Setup window (see page 74).
4. In the I/O Setup window, your newly defined output is now listed (you may have to click
the expand icon
in front of the name of the camera or other device to see the listing):
Click OK to close the I/O setup window and return to the Administrator window (see page
26).
5. In the Administrator window (see page 26), first select the camera for which the output
should be available, then click the Settings... button.
This will open the Camera Settings for [Device Name] [Camera Name] window (see page
39).
6. In the Camera Settings for [Device Name] [Camera Name] window, click the Outputs...
button:
This will open the Output Settings for [Device Name] [Camera Name] window (see page
88).
7. In the All Outputs list in the window’s left side, select the required output, then click the
>> button located between the All Outputs list and the On Manual Control list:
This will copy the selected output to the On Manual Control list, which lists all outputs
available for manual control when viewing live video from the camera in question.
Good to know:
• You are not limited to selecting output connected to the camera itself. If output has
been defined on other cameras/devices on the XProtect Basis+ system, this output
will also be selectable in the All Outputs list.
• An unlimited number of outputs may be selected this way.
• If you have specified several outputs in the On Manual Control list, you are able to
control the sequence in which the outputs will be displayed in the Remote Client
(see page 142) and Smart Client (see page 140). By using the up and down
buttons located to the right of the list, you can change a selected output’s position
in the sequence.
• The Output Settings for [Device Name] [Camera Name] window (see page 88) also
lets you select output for automatic triggering on detected motion. This is further
described in How to Add a Motion-Triggered Output on page 98.
8. When ready, click the Output Settings for [Device Name] [Camera Name] window’s Exit
button to return to the Camera Settings for [Device Name] [Camera Name] window (see
page 39).
9. In the Camera Settings for [Device Name] [Camera Name] window, click OK to return to
the Administrator window (see page 26).
10. Close the Administrator. The defined output will now be available in the Remote Client
Client/Smart Client, as described in the beginning of this text. Note that individual users’
rights may prevent them from accessing specific cameras and/or output in the Remote
Client and Smart Client; such rights are defined through the Image Server Administrator
window (see page 109).
How to Add a Motion-Triggered Output
Note: Access to features in the Administrator application, including those described in the
following, may require administrator rights.
Output (e.g. lights, sirens, etc.) connected to cameras or other devices can be triggered
automatically when motion is detected by a camera. The output does not necessarily have to be
physically connected to the motion-detecting camera.
Note: The following describes one way of adding a motion-triggered output, namely through the
Output Settings for [Device Name] [Camera Name] window (see page 88). Alternatively, motion-
triggered output may be based on VMD events or—if a device has its own motion detection
capabilities—on input events. Once such VMD or input events have been added, they can be tied to
output through the I/O Control window (see page 88). In the following, it is assumed that the
required output unit has been connected to the output port on the required camera or other device,
but that it has not yet been defined on your XProtect Basis+ system. If you have already defined
the output on your system, begin at step 5.
1. In the Administrator window (see page 26), click the I/O Setup button.
This will open the I/O Setup window (see page 74).
2. In the I/O Setup window (see page 74), first select the camera or other device to which the
output unit is connected, then click the Add new output event... button:
This will open the Add New Output window 82.
3. In the Add New Output window, the External output connected to field will show the name
of the selected camera or other device. Now specify information in the following fields:
•Output connected on: Select the camera/device output port on which the output
unit is connected. Many cameras/devices only have a single output port; in that
•Keep output for: Specify the amount of time for which the output should be active
when triggered, in either 1/10 seconds or seconds.
Note: Some devices are only able to apply outputs for a relatively short time, for
example max. five seconds. Refer to the documentation for the device in question
for exact information.
•External output name: Specify a name for the output. The name will appear on
the list with which users will be able to manually trigger the output. Note that
output names must not contain the following characters: < > & ‘ " \ / : * ? | [ ]
In the example to the right, we have specified that a
siren connected on a camera’s Output 1 port should
sound for five seconds when triggered:
Tip: You are able to test the output by clicking the
Test Output button.
When ready, click OK. This will return you to the I/O
Setup window (see page 74).
4. In the I/O Setup window, your newly defined output is now listed (you may have to click
the expand icon
in front of the name of the camera or other device to see the listing):
Click OK to close the I/O setup window (see page 74) and return to the Administrator
window (see page 26).
5. In the Administrator window (see page 26), first select the camera for which the output
should be available, then click the Settings... button.
This will open the Camera Settings for [Device Name] [Camera Name] window (see page
39).
6. In the Camera Settings for [Device Name] [Camera Name] window, click the Outputs...
button:
This will open the Output Settings for [Device Name] [Camera Name] window (see page
88).
7. In the All Outputs list in the window’s left side, select
the required output, then click the >> button located
between the All Outputs list and the On Motion Detected list:
This will copy the selected output to the On Motion Detected list, which lists all outputs to be automatically
triggered when motion is detected by the camera.
Good to know:
• You are not limited to selecting output
connected to the camera itself. If output has
been defined on other cameras/devices on the
XProtect Basis+ system, this output will also
be selectable in the All Outputs list.
• An unlimited number of outputs may be selected this way.
• The Output Settings for [Device Name] [Camera Name] window also lets you select
output for manual triggering in the Remote Client and Smart Client. This is further
described in How to Add a Manually Controlled Output on page 95.
8. When ready, click the Output Settings for [Device Name] [Camera Name] window’s Exit
button to return to the Camera Settings for [Device Name] [Camera Name] window.
9. In the Camera Settings for [Device Name] [Camera Name] window, click OK to return to
the Administrator window.
10. Close the Administrator. The defined output will now be triggered automatically when
motion is detected by the selected camera. Note that the automatic output triggering will
be controlled entirely by your motion detection settings for the camera in question. See the
description of the Adjust Motion Detection window (page 46) for more information.