XProtect Express 1.1; Administrator's Manual - Milestone

More documents

Recommendations

Info

Milestone XProtect ® Express 1.1Administrator's Manualin the Management Application, you should verify whether the problem may be due to audio being disabled on thehardware device itself.Recording settingsNameAlwaysFollow videoNeverDescriptionAlways record audio on all applicable cameras.Record audio only when video is recorded.Never record audio on any cameras. Note that even though audio is neverrecorded, it is still be possible to listen to live audio in the Smart Client.Events and outputAbout input and outputHardware input, such as door sensors, can be attached to input ports on hardware devices. Input from suchexternal hardware input units can be used for generating events in XProtect Express.Hardware output units can be attached to output ports on many hardware devices, allowing you to activatelights, sirens, and more from XProtect Express. Such hardware output can be activated automatically by events,or manually from clients.Before you specify use of hardware input and hardware output units on a hardware device, verify that sensoroperation is recognized by the hardware device. Most hardware devices are capable of showing this in theirconfiguration interfaces, or via CGI script commands. Also check the XProtect Express release notes to verify thatinput and output controlled operations are supported for the hardware device and firmware used.You do not have to configure hardware input units separately, any hardware input units connected to hardwaredevices are automatically detected when you add the hardware devices to XProtect Express. The same goes forhardware output, but hardware output does require some simple configuration in XProtect Express.If you want to configure hardware output and automatically trigger output when events occur, so that, forexample, lights are switched on when a door is opened or when motion is detected in video, see Add a hardwareoutput (on page 112) and Configure hardware output on event.About events and outputEvents and output of various types can be used for automatically triggering actions in XProtect Express.Examples of actions: starting or stopping recording on cameras, switching to a particular video frame rate,triggering e-mail notifications, making PTZ cameras move to specific preset positions, etc. Events can also beused for activating hardware output.You can also configure events and output to generate alarms (see "About alarms" on page 152).Events can be divided in to:Internal events (system-related): for example, motion, server responding/not responding, archivingproblems, lack of disk space, etc.External events (integrated): for example, MIP plug-in events.www.milestonesys.com 110 Advanced configuration
Milestone XProtect ® Express 1.1Administrator's ManualOverview of events and outputTypes of events:NameDescriptionHardware input events:Events based on input from hardware input units attached tohardware devices are called hardware input events.Some hardware devices have their own capabilities for detectingmotion, for detecting moving and/or static objects, etc. (configuredin the hardware devices' own software; typically by accessing abrowser-based configuration interface on the hardware device's IPaddress). When this is the case, XProtect Express considers suchdetections as input from the hardware, and you can use suchdetections as input events as well.Lastly, hardware input events can be based on XProtect Expressdetecting motion in video from a camera, based on motiondetection settings in XProtect Express.This type of hardware input events is also called system motiondetection events or VMD (Video Motion Detection) events. Inearlier XProtect Express versions, VMD events were an event typeof their own; now they are simply considered a type of hardwareinput event.Events may be generated manually by the users selecting them in theirclients. These events are called manual events.Manual events can be of the type Global events or Timer events:Manual events:Global events apply to all hardware whereas timer events are separateevents, triggered by the hardware input event, manual event or genericevent under which they are defined. Timer events occur a specified numberof seconds or minutes after the event, under which they are defined, hasoccurred. Timer events may be used for a wide variety of purposes,typically for stopping previously triggered actions.Example:A camera starts recording based on a hardware input event, for examplewhen a door is opened; a timer event stops the recording after 15 seconds.Before you configure events of any type, configure general event handling, such as which ports XProtectExpress should use for event data. Normally, you can just use the default values, but it is a good idea to verifythat your organization is not already using the ports for other purposes. See Configure general event handling (onpage 113).When you are ready to configure events, see Add a hardware input event (on page 111) , and Add a manualevent (on page 112). If you want to use timer events with your other events, see Add a timer event (on page 113).Add a hardware input eventWith hardware input events, you can turn input received from input units attached to hardware devices into events(see "Overview of events and output" on page 111) in XProtect Express.Before you specify input for a hardware device, verify that sensor operation is recognized by the hardware device.Most hardware devices are capable of showing this in their configuration interfaces, or via CGI script commands.Also check the release notes to verify that input-controlled operation is supported for the hardware device andfirmware used.To add and/or configure a hardware input event, do the following:www.milestonesys.com 111 Advanced configuration
Page 1 and 2:
Milestone SystemsXProtect ® Expres
Page 3 and 4:
Milestone XProtect ® Express 1.1Ad
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 18 and 19:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60: Milestone XProtect ® Express 1.1Ad
Page 109: Milestone XProtect ® Express 1.1Ad
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183:
About Milestone SystemsFounded in 1
show all

XProtect Express 1.1; Administrator's Manual - Milestone

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?