honeywell digital video manager user guide

Honeywell Digital Video ManagerUser Guide

Release 200

2

NoticeThis document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell Limited Australia.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer.

In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice.

Honeywell suggests the user of this product satisfy themselves that their intended use does not contravene any national or local law. Honeywell accepts no responsibility for any loss occasioned to any person acting or refraining from action as a result of the customer using this product in a manner contrary to governing laws.

Copyright 2005 – Honeywell Limited Australia

Honeywell trademarksExperion PKS®, SafeBrowse®, TotalPlant® and TDC 3000® are U.S. registered trademarks of Honeywell International Inc.

Honeywell Digital Video Manager™ and Honeywell Enterprise Buildings Integrator™ are trademarks of Honeywell International Inc.

Other trademarksMicrosoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

iOmniscient and IQ140 are either registered trademarks or trademarks of the iOmniscient company in the United states and/or other countries.

Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention of trademark infringement.

Document Release Issue DateZD36-003-200 200 0 September 2005

3

Digital signatures introduction/disclaimerHoneywell DVM R200 provides the ability to digitally sign exported video and audit logs to help verify that the files have not been tampered with after export. The main use for these digitally signed files is use as evidence in court.

A digital signature is not a requirement for submitting digital video as evidence and having a digital signature will not automatically guarantee that a court will accept the signed video as evidence.

The default signature provided with Honeywell DVM will provide the court with an assurance that the video and associated audit log has not been altered in any way after it was exported. The use of a third-party signature will provide the same guarantee of authenticity as the default signature, however, as the signature will be unique to one DVM system, a third-party signature can also provide a guarantee of origin—the video and audit log can only have come from that one system. Both of these may cause the court to assign more weight to the evidence if they accept it but will in no way guarantee that the evidence will be accepted, as acceptance of evidence is always a matter for the court to decide.

A detailed description of the legal rules of evidence is beyond the scope of this manual and any commentary here may not be applicable to your local legal system. If you require further advice on the use of video as evidence, please contact you local Honeywell representative or seek advice from a legal professional.

Honeywell Digital Video Manager User Guide 5

Contents

1 About this guide 13

2 Overview 15Basic architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Integration with EBI or Experion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17The user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Planning 19Network design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Network architecture options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Conventional design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Dedicated network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About multicasting and unicasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Network design tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Calculating storage and bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About Image Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28About MPEG and Motion JPEG compression types. . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Calculating the disk storage requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Calculating the bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Typical storage and bandwidth requirements for video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Axis 205, 206/206W and 210/210A with Motion JPEG. . . . . . . . . . . . . . . . . . . . . . . . . 37Axis 206M and 207 with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Axis 210/210A with MPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Axis 211/211A with MPEG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Axis 211/211A with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Axis 213, 231D, 232D, 240Q, 241S/241SA and 241Q/241QA with Motion JPEG. . . . 53Axis 221 with MPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Axis 221 with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Axis 231D, 232D, 241S/241SA and 241Q/241QA with MPEG. . . . . . . . . . . . . . . . . . . 64Axis 2100 and 2110 with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Axis 2120, 2130, 2400 1.x, 2400 2.x, 2401 1.x, 2401 2.x and 2420 with Motion JPEG 70Axis 2400+, 2401+ and 2411 with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75CamStation CS100 with MPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80CamStation CS-3001V with MPEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83MegaChips OpennetView and MD-100 with Motion JPEG . . . . . . . . . . . . . . . . . . . . . . 87

Typical storage and bandwidth requirements for audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Contents

6 Release 200

EBI or Experion integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Areas (Assets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Security types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Windows security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96About the specialized Windows accounts and groups used by Honeywell DVM . . . . . 98About Honeywell DVM security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Digital signatures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107About Honeywell DVM servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Database Server redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Custom applications and scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Recording audio with Axis streamers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Supporting video intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Camera and video requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Camera types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Camera streamer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Summary of camera streamer capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

4 Guidelines for video analytics 123About video analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

About the Honeywell DVM video analytics algorithms . . . . . . . . . . . . . . . . . . . . . . . . 125About regions of interest and minimum object size . . . . . . . . . . . . . . . . . . . . . . . . . . . 126About Video Analytics Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Choosing the appropriate algorithm for the task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Basic requirements of video analytics algorithms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Example scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Detecting vehicles that are moving in the wrong direction. . . . . . . . . . . . . . . . . . . . . . 135Monitoring a perimeter fence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Monitoring the entrance of a secure room. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Monitoring people who enter the utilities room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Monitoring the direction of objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Checklist for successfully implementing video analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Guidelines for choosing cameras and streamers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Streamers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Guidelines for lighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Guidelines for placing cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Basic guidelines for placing cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151In outdoor locations, avoid distant views with small objects . . . . . . . . . . . . . . . . . . . . 156In indoor locations, place the camera as high as practicable. . . . . . . . . . . . . . . . . . . . . 157In indoor locations, avoid placing cameras at corners or under ceilings . . . . . . . . . . . 158Avoid fixtures that split a critical region into separate zones . . . . . . . . . . . . . . . . . . . . 159Avoid splitting a critical region into heavily shadowed and brightly lit zones . . . . . . . 160

Contents


Avoid placing a camera in a confined space with inadequate lighting . . . . . . . . . . . . . 161Avoid placing a camera opposite elevator or automatic doors . . . . . . . . . . . . . . . . . . . 162Avoid placing a camera opposite phone booths, ATMs or vending machines . . . . . . . 163Avoid placing a camera to the side of stairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Avoid highly reflective, glass-like surfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165In outdoor locations, shade the camera lens from the sun. . . . . . . . . . . . . . . . . . . . . . . 166Avoid large regions of continuous motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Guidelines for adjusting the field of view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Restrict the field of view to what you want to monitor. . . . . . . . . . . . . . . . . . . . . . . . . 169Orientate the camera to avoid a skewed field of view. . . . . . . . . . . . . . . . . . . . . . . . . . 171Adjust the camera for maximum video clarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Avoid zones where objects are likely to start-stop in an erratic manner . . . . . . . . . . . . 175Ensure that only far-field views contain intersections or footpaths . . . . . . . . . . . . . . . 176

Guidelines for defining regions of interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177General guidelines for defining regions of interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Case 1: road junction and parked cars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Case 2: road junction with pedestrians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Case 3: outdoor carpark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Case 4: carpark and entrance road. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Case 5: pedestrian crossings in carpark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Case 6: building lobby with lifts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Case 7: shopping mall (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Case 8: shopping mall (example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Guidelines for defining the minimum object size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Case 1: outdoor far-field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Case 2: outdoor mid-field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Case 3: outdoor near-field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Case 4: indoor far-field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Case 5: indoor mid-field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

5 Installation and upgrade 201Using the checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202New installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Installation checklist: Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Installation checklist: Camera Server or Video Analytics Server . . . . . . . . . . . . . . . . . 206Installation checklist: single (non-redundant) EBI or Experion server . . . . . . . . . . . . . 207Installation checklist: redundant EBI or Experion servers . . . . . . . . . . . . . . . . . . . . . . 208Installation checklist: Console Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Installation checklist: Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Installation checklist: Internet Explorer client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Upgrade checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Upgrade checklist: from Honeywell DVM R160.1 or R160.2 . . . . . . . . . . . . . . . . . . . 214Upgrade checklist: from Honeywell DVM R150.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Installation and setup tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Setting up the Honeywell DVM installation account . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Contents

8 Release 200

Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Configuring Internet Explorer for use with Honeywell DVM . . . . . . . . . . . . . . . . . . . 221Synchronizing the date and time on the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Installing the Honeywell DVM Database Server components on a non-redundant server.

224Installing the Honeywell DVM Database Server components on redundant servers . . 226Installing the Honeywell DVM Camera Server components . . . . . . . . . . . . . . . . . . . . 230Installing the Honeywell DVM host components on the EBI or Experion server . . . . 232Installing the Honeywell DVM host components on a Console Station . . . . . . . . . . . . 233Installing the Honeywell DVM client components on a Station computer. . . . . . . . . . 234Configuring Station for use with Honeywell DVM . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Installing the Honeywell DVM client components for an Internet Explorer client computer

237Updating the hosts file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Pinging a device on the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Installing and configuring camera streamers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Axis 205, 206, 206M, 206W, 207, 210/210A, 211/211A, 221, 2100, 2110, 2120, 2411 and

2420 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Axis 213, 231D, 232D and 2130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Axis 2400 1.x, 2400 2.x, 2400+, 2401 1.x, 2401 2.x and 2401+ . . . . . . . . . . . . . . . . . 245Axis 240Q, 241S, 241SA, 241Q and 241QA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Defining the user name and password of an Axis streamer in Honeywell DVM . . . . . 255CamStation CS100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256CamStation CS-3001V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261MegaChips MD-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267MegaChips OpennetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Installing and configuring PTZ cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Pelco cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Sensomatic cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273VCL Orbiter dome cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Honeywell KD6 digital dome cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Hernis Industrial cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Planning for an upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Uninstalling your existing Honeywell DVM components . . . . . . . . . . . . . . . . . . . . . . 280

Uninstalling Honeywell DVM R200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

6 Configuration 287Configuring security for Honeywell DVM in a domain environment . . . . . . . . . . . . . . . . . . . 289Configuring a camera . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Camera Definition tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Record Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Camera Control tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Configuring privacy zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Configuring tours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Contents


Creating a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Deleting a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Creating a quad view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Creating a sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Configuring video analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Configuring motion detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Configuring object tracking and classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Specifying the folder for snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Configuring the audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Configuring disk space administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Configuring event-activated recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Configuring multi-monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Configuring the monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Configuring alarm monitor cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Configuring a digital certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Installing the digital certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Checking that the digital certificate has been installed correctly . . . . . . . . . . . . . . . . . 344Configuring Honeywell DVM to use the digital certificate . . . . . . . . . . . . . . . . . . . . . 345

Defining special presets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Configuring Axis Streamers for audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Configuring the Axis 2191 Audio Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Configuring the streamer for audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Fine tuning audio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Audio operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Configuring CamStation CS-3001V for audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Hardware configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Audio operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Configuring a camera to receive audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Configuring Honeywell DVM for video intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Audio hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Alarm configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Audio settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Setting up Honeywell DVM for video intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

7 Operation 359Using Station to view live video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Using Internet Explorer to view live video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Using the live video controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Using the live video mouse PTZ controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Using presets and tours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369About the camera symbols in the Navigation Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370About the video analytics symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371About snapshot files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Viewing recorded video. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Contents

10 Release 200

Using the playback controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Viewing a quad view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377Viewing a sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Using the intercom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Initiating a call from the field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Answering a field-initiated call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Initiating a call by an operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380Terminating a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Adjusting audio for live and recorded video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Adjusting the volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Disabling audio on a scheduled recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Disabling audio on a background recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Exporting video with audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Searching for recorded video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Doing a simple search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Doing an advanced search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Viewing the search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Preventing a video clip from being deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Preventing a video clip from being archived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Using the numeric keypad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

8 Administration 393Giving users access to Honeywell DVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Giving a user access: Internet Explorer in a domain environment . . . . . . . . . . . . . . . . 395Giving a user access: operator-based security with integrated accounts in a domain

environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Giving a user access: operator-based security without integrated accounts in a domain

environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Giving a user access: Station-based security in a domain environment . . . . . . . . . . . . 398Giving a user access: Internet Explorer in a workgroup environment . . . . . . . . . . . . . 399Giving a user access: operator-based security with integrated accounts in a workgroup

environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Giving a user access: operator-based security without integrated accounts in a workgroup

environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401Giving a user access: Station-based security in a workgroup environment . . . . . . . . . 403Creating a Windows user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404Adding a user to the domain group for Honeywell DVM users . . . . . . . . . . . . . . . . . . 405Giving a user access to Honeywell DVM through Internet Explorer . . . . . . . . . . . . . . 406Adding Windows accounts to the DVM_Users group . . . . . . . . . . . . . . . . . . . . . . . . . 409Adding Windows accounts to the Honeywell Administrators group . . . . . . . . . . . . . . 410

Exporting video clips and audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Exporting a video clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Exporting the audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412Audited events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412Exporting the audit log with a video clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Contents


Packaging the exported files into a zip file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415Verifying the exported Honeywell DVM files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Archiving and restoring video clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417Automatically archiving video clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417Manually archiving video clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Restoring video clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Viewing the status of the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420Viewing the status of the Camera Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421Viewing the disk usage details of a Camera Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Manually resynchronizing redundant Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Re-synchronizing the date and time on the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425Viewing basic information about your Honeywell DVM system . . . . . . . . . . . . . . . . . . . . . . 426Changing the Honeywell DVM license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

9 Troubleshooting 429Using the Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Configuring the Engineering Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

General problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438Problems specific to CS-3001V video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442Problems specific to audio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443Problems specific to EBI or Experion integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Contents

12 Release 200


1About this guide

This guide describes how to set up and use Honeywell Digital Video Manager (Honeywell DVM), and contains the following chapters:

• Overview. Describes Honeywell DVM’s main features and basic architecture.

• Planning. Provides planning and design guidelines.

• Guidelines for video analytics. Provides guidelines for using video analytics.

• Installation and upgrade. Describes how to install Honeywell DVM.

• Configuration. Describes how to configure cameras and video displays, and how to integrate with Honeywell Enterprise Buildings Integrator (EBI) or Experion.

• Operation. Describes how to use Honeywell DVM on a day-to-day basis.

• Administration. Describes tasks which need to be completed by the system administrator.

• Troubleshooting. Describes how to solve common problems.

1 – About this guide

14 Release 200


2Overview

Honeywell Digital Video Manager (Honeywell DVM) combines the advantages of digital video with the latest Web and networking products to provide a flexible and scalable Closed Circuit Television (CCTV) system.

Major features and benefits of Honeywell DVM include:

• Flexibility. Use of standard hardware and software makes it easier and less costly to expand and modify your system.

• Integration with EBI or Experion. Integration means, for example, that EBI or Experion alarms and events can initiate recordings.

• Ease of viewing. No special monitors are required because video is viewed on standard Windows-based computers.

• Video management. Operators can search for recordings based on numerous criteria including camera name, time, event and operator notes.

To learn about: Go to:The basic Honeywell DVM architecture page 16

Integration with EBI or Experion page 17

The user interface page 18

2 – Overview

16 Release 200

Basic architecture The following figure shows the basic architecture of a typical Honeywell DVM system. A typical Honeywell DVM system comprises a Database Server, one or more Camera Servers, clients, camera streamers and IP cameras. The system can optionally be integrated with an EBI or Experion system.

The TCP/IP network interconnects cameras, servers and Stations (the EBI or Experion user interfaces). This network-based design enables video signals to be managed, transmitted and viewed like any other type of information.

Figure 1 Basic Honeywell DVM architecture

Stations

EBI /Experion Server

TCP/IP Network

IP Streaming CameraCameras

Camera Streamer

Database Server Internet ExplorerClients

Camera Servers

Integration with EBI or Experion


Integration with EBI or ExperionHoneywell DVM is tightly integrated with two other Honeywell products:

• Honeywell Enterprise Buildings Integrator (EBI)—for building management and security-related applications.

• Experion—for industrial applications.

Integration with these Honeywell products provides the following benefits:

• Alarms and events can initiate recordings. These recordings can even show what happened before an alarm/event occurred, so that operators can see what preceded the incident as well as its consequences.

• Honeywell DVM shares the EBI or Experion user interface (Station), which means that operators do not need to learn two applications.

• Users can view Honeywell DVM videos on any Station on the network.

• Honeywell DVM uses EBI or Experion security features that, for example, allow you to define each operator’s viewing rights.

• Honeywell DVM system alarms and events are automatically sent to EBI or Experion for inclusion in the Alarm and Event Summaries.

• Recordings associated with EBI or Experion alarms and/or events can be viewed directly from the EBI or Experion Alarm or Event Summary.

• An operator Station can control dedicated surveillance monitors.

• Alarms can be associated with video content and displayed on video alarm monitors.

2 – Overview

18 Release 200

The user interface Honeywell DVM includes an easy-to-use Web-based interface which runs on standard Windows computers. Depending on your requirements, you can access the displays (pages) using either Station or Internet Explorer.

The following figure shows a typical display. The tree-style menu on the left makes it easy to navigate through complex systems with large numbers of cameras and servers. The video window provides all the controls appropriate to the selected camera, such as PTZ, presets and snapshot buttons.

Figure 2 Typical Live Video Page


3Planning

This chapter describes how to plan for and design your Honeywell DVM system.

Issue CommentsNetwork design Ensure that you select an appropriate network

architecture and install suitable network hardware.See “Network design” on page 21.

Storage and bandwidth requirements

Estimate your disk storage and network bandwidth requirements.See “Calculating storage and bandwidth requirements” on page 27.

Integration with EBI or Experion

If you have EBI or Experion, decide how you are going to integrate it with Honeywell DVM.See “EBI or Experion integration” on page 91.

Security Determine your operational security requirements.See “Security” on page 94.

Digital signatures Decide whether you need to digitally “sign” exported videos and audit logs.See “Digital signatures” on page 107.

Honeywell DVM servers Determine your hardware and software requirements for Honeywell DVM servers.See “About Honeywell DVM servers” on page 108 and “Hardware and software requirements” on page 116.

Redundancy Decide whether you need redundant Database Servers.See “Database Server redundancy” on page 109.

3 – Planning

20 Release 200

Video analytics Decide whether you can enhance the functionality of your system by making use of Honeywell DVM’s video analytics capabilities. (Video analytics includes motion detection and object tracking/classification).For an introduction to video analytics and usage guidelines, see “Guidelines for video analytics” on page 123.

Custom applications and scripts Decide whether you can enhance the functionality of your Honeywell DVM system by writing custom applications and scripts.See “Custom applications and scripts” on page 111.

Audio recording Determine your audio recording requirements.See “Recording audio with Axis streamers” on page 112.

Video intercom Determine your video intercom requirements.See “Supporting video intercom” on page 113.

Cameras and video recordings Determine your camera and video recording requirements, such as camera types, frame rates and recordings.See “Camera and video requirements” on page 114.

Hardware and software Make sure that your hardware and software meets the requirements of Honeywell DVM.See “Hardware and software requirements” on page 116.

Streamers Determine which streamers meet your requirements.See “Summary of camera streamer capabilities” on page 120.

Issue Comments

Network design


Network designHoneywell DVM requires a well-designed and well-managed network to ensure that:

• Network availability meets your video performance requirements.

• Other network applications are not affected.

Issue CommentsNetwork architecture Select the network architecture that best meets your

needs. See “Network architecture options” on page 22.

Optional multicast traffic If you choose to use multicasting, make sure that you consider the network design issues.See “About multicasting and unicasting” on page 24.

Network management Ensure that you have the appropriate tools to manage the network.See “Network management” on page 25.

Design tips See “Network design tips” on page 26.

Network bandwidth Estimate the network bandwidth requirements.See “Calculating storage and bandwidth requirements” on page 27.

3 – Planning

22 Release 200

Network architecture optionsYou can use either of the following network architecture options to maintain network integrity.

Conventional designA conventional design has no physical or logical protection between the various types of traffic. The following figure shows how it is possible for Honeywell DVM to share a network with an MIS system.

In a well-managed environment, this should be satisfactory. However, if the network grows rapidly, or if an application puts an unusually high load on the network, one or all of the applications may be compromised.

Network architecture option Go to:Use a conventional network design, but pay particular attention to video traffic. This option may require regular monitoring to ensure integrity.

page 22

Set up Virtual LANs (VLANs) which allow applications to share network hardware.

page 23

Install a dedicated network for Honeywell DVM. This option maximizes integrity of Honeywell DVM by ensuring it is not competing with other applications.

page 23

EBI / ExperionServer

Ethernet Switch Ethernet SwitchEthernet Switch

Ethernet Switch

Station

Station MISTerminal

MISTerminal StationCamera CameraCamera

MIS ServerDatabase andCamera Servers

Edge switches withfast uplinks

Network architecture options


VLANVirtual LANs (VLANs) allow you to logically organize Ethernet ports according to use, even though they share the same network hardware. In the following figure, the Honeywell DVM and EBI or Experion components (shaded) would be in one VLAN, and the MIS components (unshaded) would be in another.

Dedicated networkInstalling a dedicated network for Honeywell DVM ensures that existing network applications are unaffected. But a dedicated network is obviously more expensive, especially if you have only a few cameras.

EBI / Experion PKSServer

Ethernet Switch Ethernet SwitchEthernet Switch

Ethernet Switch

Station

Station MISTerminal

MISTerminal StationCamera

MIS ServerDatabase andCamera Servers

Camera Camera

3 – Planning

24 Release 200

About multicasting and unicastingHoneywell DVM uses two transmission techniques:

• Multicasting. This involves sending information from one device to multiple devices. For example, from the Honeywell DVM servers to two Stations.

• Unicasting. This involves sending information to only one device.

Although multicasting is a very useful transmission technique, it can have very significant effects on the network. Without special configuration, most equipment sends multicast traffic to all devices in the network, resulting in high network utilization across the whole network, rather than in only the relevant segments.

Honeywell DVM uses multicasting and unicasting as follows:

• Transmission from the camera streamer to the Camera Server is unicast.

• Transmission from the Camera Server to Stations can be either unicast or multicast:

- Unicast is always used for playing back recorded video.

- Live video viewing can be configured on a camera-by-camera basis to be either multicast or unicast. Multicast is more efficient because several Stations can view the same live video without increasing the network usage. Unicast is less efficient because it requires a separate network stream for every Station.

Sophisticated network switches are required to correctly handle multicast traffic. Note that some network switches, such as LANE1 ATM, turn a multicast message into a broadcast one, which may quickly overload the network.

Routers have special configuration requirements to enable them to handle multicast traffic. Contact your vendor for these configuration requirements.

Network management


Network managementNetwork management is a complex topic that is beyond the scope of this guide. However, Honeywell DVM requires an appropriate set of network management tools that provide information such as:

• Network utilization, including real-time and history reports.

• Warning if utilization reaches a user-defined threshold.

• Notification if a switch fails.

3 – Planning

26 Release 200

Network design tips• Use ATM, Gigabit or Fast Ethernet.

• Minimize the number of switches.

• Use switches, not hubs.

• Minimize the number of routers.

• Do not use 10 Mbps hubs. 100 Mbps hubs may be acceptable, depending on the rest of the network equipment.

• Isolate, as far as possible, video traffic for individual Camera Servers.

• Isolate, as far as possible, EBI or Experion from traffic between camera streamers and Camera Servers.

• Place camera streamer traffic and Station traffic on different LANs or VLANs.

• Consider placing multiple network cards in the Honeywell DVM servers. Camera streamers can reside on more than one VLAN.

• Consider using load-sharing network cards in the Database and Camera Servers.

Calculating storage and bandwidth requirements


Calculating storage and bandwidth requirementsBecause of the potentially large storage and bandwidth requirements of digital video, you need to carefully estimate your storage and bandwidth requirements.

Storage and bandwidth requirements depend on:

• Image size. For example, a 640 × 480 image is four times larger than a 320 × 240 one.

• Frame rate. The standard frame rate for smooth video is 25 fps (PAL) or 30 fps (NTSC), but much lower frame rates—even 1 fps—may be acceptable.

• Streamer type. The streamer type has a major impact on storage and bandwidth requirements. See “Typical storage and bandwidth requirements for video” on page 35.

• Compression type. MPEG4 requires less bandwidth and storage than Motion JPEG. See “About MPEG and Motion JPEG compression types” on page 30.

• Compression level. The greater the compression, the smaller the file size, but the lower the image quality.

• Image complexity. Visually complex images produce larger file sizes than visually simple images. See “About Image Complexity” on page 28.

• Image type (color or black and white). A color image is slightly larger than its black and white equivalent.

• Audio. Video with audio will require more bandwidth and storage than video without audio. See “Typical storage and bandwidth requirements for audio” on page 90.

3 – Planning

28 Release 200

About Image Complexity The following figures show what constitutes the three levels of image complexity: complex, medium-complexity and simple. (These definitions are used in the storage and bandwidth requirements tables.)

Complex imageA “complex” image is one that contains numerous irregular patterns and wide ranges of color, for example, outside scenes and crowds of people.

Medium-complexity imageA “medium-complexity” image is one that contains regular patterns and a range of colors, for example, corridors and general office scenes.



Simple imageA “simple” image is one that contains large areas of consistent color without patterns, for example, lift lobbies and areas with a narrow field of vision.

3 – Planning

30 Release 200

About MPEG and Motion JPEG compression typesAn MPEG streamer sends a Group of Pictures (GOP), which consists of a complete video frame followed by a series of delta frames; whereas a Motion JPEG streamer sends a complete image each frame.

In MPEG, the complete video frame is called an I-Frame (Index Frame), and every other frame (known as delta frames) contains the differences between the current frame and the previous one. Because delta frames are much smaller than a complete video frame, MPEG requires less network bandwidth and storage than Motion JPEG.

I-Frame recording allows you to record video at a lower frame rate than the connection frame rate. This is achieved by recording only the I-Frames, not the deltas.

To find out which compression type(s) a streamer supports, see “Typical storage and bandwidth requirements for video” on page 35.

Differences between MPEG (I-Frame) and Motion JPEG

MPEG (I-Frame) Motion JPEGSends a GOP, which includes a complete video frame, plus delta frames.

Sends a complete image for every video frame.

Compression rate—greater than Motion JPEG, because a delta frame is smaller than a complete video frame image.

Compression rate—lower than an MPEG because the complete image is larger than a delta frame.

The maximum frame rate for recording is limited by the live view frame rate. See “Recording frame rates using MPEG” on page 297.

The live view and record frame rates are independent. For example, you can view at a low frame rate, but record at a high frame rate.



Calculating the disk storage requirementsThis topic describes how to calculate the disk storage requirements.

You must calculate the storage requirements for each camera. Your total storage requirements are equal to the sum of the individual camera storage requirements.

Calculating the storage requirements for a camera

Prerequisites• You have estimated how many hours of alarm and background recording

recording you want to keep online for the camera. These values are system specific and depend on factors such as:

- The frequency and importance of alarms

- The importance of what is in the camera field of view—you may only want background recording if a continuous record of the field of view is essential

To calculate a storage requirements for a camera:1 Determine the level of image complexity—see “About Image Complexity” on

page 28.

2 Select the table for the streamer to which the camera is connected—see “Typical storage and bandwidth requirements for video” on page 35.

3 From the table, select the value that corresponds with your settings. (In a similar manner to that shown in the following example.)

3 – Planning

32 Release 200

4 Calculate your storage requirements per hour for background recording. If the streamer uses:

• Motion JPEG, multiply the value obtained from the table by the number of frames per second (fps) used for background recording. This is the BackgroundStoragePerHour value.

• MPEG, the value obtained from the table is the BackgroundStoragePerHour value.

5 If the camera has audio, include the audio requirement in BackgroundStoragePerHour. See “Typical storage and bandwidth requirements for audio” on page 90.

6 Calculate your storage requirements per hour for alarm recording. If the streamer uses:

• Motion JPEG, multiply the value obtained from the table by the number of frames per second (fps) used for event-activated recording. This is the AlarmStoragePerHour value.

• MPEG, the value obtained from the table is the AlarmStoragePerHour value.

7 If the camera has audio, include the audio requirement in AlarmStoragePerHour. See “Typical storage and bandwidth requirements for audio” on page 90.

8 Use you estimate for how many hours of background recording you want to keep online as your BackgroundRecordingHours value.

9 Use your estimate of how many hours of alarm recording you want to keep online as your AlarmRecordingHours value.

10 Calculate the storage requirement (MB) for the camera using the following formula:(BackgroundStoragePerHour x BackgroundRecordingHours)

+ (AlarmStoragePerHour x AlarmRecordingHours)



Calculating the bandwidth requirementsThis topic describes how to calculate the bandwidth requirements for individual cameras and for the network.

Calculating the bandwidth requirements for a camera

To calculate the bandwidth requirements for a camera:1 Determine the level of image complexity—“About Image Complexity” on

page 28.

2 Select the table for the streamer to which the camera is connected—see “Typical storage and bandwidth requirements for video” on page 35.

3 From the table, select the value that corresponds your settings. (In a similar manner to that shown in the following example.)

4 If the streamer uses:

• Motion JPEG, multiply the value obtained from the table by the highest frame rate you want to use for the camera. This is the bandwidth requirement for the camera (Kbps).(With Motion JPEG, you can specify different frame rates for live video and background recording. For example, if you specify 12 fps for live video and 24 fps for recording, you would use 24 fps in your calculation.)

• MPEG, the value obtained from the table is the bandwidth requirement for the camera (Kbps).

5 If the camera has audio, add the audio requirement to the value obtained in step 4. See “Typical storage and bandwidth requirements for audio” on page 90.

3 – Planning

34 Release 200

Calculating the bandwidth requirements for the networkYou can calculate the bandwidth requirements for the network after you have calculated the bandwidth requirements for each camera.

To determine the bandwidth requirements for the network:1 Sketch out a design of your network (or proposed network).

2 For each Ethernet link, sum the total demand across all the cameras utilizing that Ethernet link.

3 For each router, sum the total demand across all the cameras utilizing that router.

4 Compare the calculated demand with the rating of your network equipment. Ensure the network has greater capacity than that demanded by Honeywell DVM.

Typical storage and bandwidth requirements for video


Typical storage and bandwidth requirements for video The following table lists the camera streamers that supported by Honeywell DVM. The detailed storage and bandwidth requirements for each streamer are shown on the specified pages.

Type of camera streamer: For Motion JPEG:

For MPEG:

Axis 205 page 37 Not supported

Axis 206/206W page 37 Not supported

Axis 206M page 40 Not supported


Axis 210/210A page 37 page 44

Axis 211/211A page 50 page 47


Axis 221 page 61 page 58

Axis 231D page 53 page 64

Axis 232D page 53 page 64

Axis 240Q page 53 Not supported

Axis 241Q/241QA page 53 page 64

Axis 241S/241SA page 53 page 64





Axis 2400 1.x page 70 Not supported


Axis 2400+ page 75 Not supported



Axis 2401+ page 75 Not supported



CamStation CS100 Not supported page 80

CamStation CS-3001V Not supported page 83

3 – Planning

36 Release 200

MegaChips MD-100 page 87 Not supported

MegaChips OpennetView page 87 Not supported

Type of camera streamer: For Motion JPEG:

For MPEG:



Axis 205, 206/206W and 210/210A with Motion JPEGThe following data was collected using the Axis 205, 206/206W and 210/210A camera streamer for three levels of image complexity. The Axis 210A supports audio, see “Recording audio with Axis streamers” on page 112.

Complex image

Resolution Compression Image Size (KB)

Max Frame Rate (fps)

Bandwidth per fps (Kbps)

1-hour recording disk space per fps (MB)

(160 × 120) Maximum 1.9 18 15.43 6.78

High 2.4 18 19.15 8.42

Medium 4.4 18 35.07 15.41

Low 6.8 18 54.27 23.85

Minimum 12.3 18 98.67 43.36

(320 × 240) Maximum 5.5 18 43.80 19.25

High 7.1 18 57.13 25.11

Medium 14.2 18 113.90 50.05

Low 23.0 18 184.12 80.91

Minimum 42.0 18 336.08 147.69

(640 × 360) Maximum 13.9 18 111.3 48.92

High 17.9 18 143.64 63.12

Medium 34.7 18 277.81 122.09

Low 55.3 18 442.82 194.60

Minimum 103.3 18 826.28 363.10

(640 × 480) Maximum 18.6 18 148.40 65.22

High 23.9 18 191.52 84.16

Medium 46.3 18 370.42 162.79

Low 73.8 18 590.42 259.46

Minimum 137.7 18 1101.70 484.14

3 – Planning

38 Release 200

Medium-complexity image





(160 × 120) Maximum 1.3 21 10.27 4.51

High 1.4 21 11.60 5.10

Medium 2.1 21 16.89 7.42

Low 3.0 21 23.36 10.27

Minimum 5.1 21 40.77 17.85

(320 × 240) Maximum 3.0 21 24.48 10.76

High 3.4 21 27.55 12.11

Medium 5.5 21 44.16 19.41

Low 8.3 21 66.63 29.28

Minimum 15.9 21 127.36 55.97

(640 × 360) Maximum 7.2 21 58.08 25.53

High 8.1 21 65.52 28.79

Medium 13.2 21 105.99 46.58

Low 20.2 21 161.88 71.13

Minimum 40.8 21 326.15 143.33

(640 × 480) Maximum 9.7 21 77.45 34.04

High 10.9 21 87.36 38.39

Medium 17.7 21 141.33 62.11

Low 27.0 21 215.84 94.85

Minimum 54.4 21 434.87 191.11



Simple image





(160 × 120) Maximum 1.1 25 8.93 3.92

High 1.2 25 9.78 4.30

Medium 1.6 25 12.77 5.61

Low 2.0 25 16.57 7.28

Minimum 3.4 25 27.55 12.11

(320 × 240) Maximum 2.6 25 20.52 9.02

High 2.7 25 21.66 9.52

Medium 3.7 25 29.54 12.98

Low 5.1 25 40.69 17.88

Minimum 10.1 25 80.48 35.37

(640 × 360) Maximum 6.15 25 49.20 21.62

High 6.45 25 52.02 22.86

Medium 8.55 25 68.39 30.06

Low 12.075 25 96.84 42.56

Minimum 25.2 25 201.45 88.53

(640 × 480) Maximum 8.2 25 65.61 28.83

High 8.6 25 69.37 30.48

Medium 11.4 25 91.19 40.08

Low 16.1 25 129.13 56.75

Minimum 33.6 25 268.61 118.04

3 – Planning

40 Release 200

Axis 206M and 207 with Motion JPEGThe following data was collected using the Axis 206M (Megapixel) and 207 camera streamer for three levels of image complexity.

Complex image





(320 × 240) Maximum 5.5 10 43.80 19.25

High 7.1 10 57.13 25.11

Medium 14.2 10 113.90 50.05

Low 23.0 10 184.12 80.91

Minimum 42.0 10 336.08 147.69

(640 × 360) Maximum 13.9 10 111.3 48.92

High 17.9 10 143.64 63.12

Medium 34.7 10 277.81 122.09

Low 55.3 10 442.82 194.60

Minimum 103.3 10 826.28 363.10

(640 × 480) Maximum 18.6 10 148.40 65.22

High 23.9 10 191.52 84.16

Medium 46.3 10 370.42 162.79

Low 73.8 10 590.42 259.46

Minimum 137.7 10 1101.70 484.14

(1280 × 720) Maximum 42.6 10 340.53 149.66

High 53.6 10 430.17 189.03

Medium 100.8 10 806.67 354.51

Low 168.7 10 1349.87 593.20

Minimum 350.4 8 2804.07 1232.24

(1280 × 960) Maximum 55.3 10 441.22 193.91

High 67.1 10 538.47 236.62

Medium 125.8 10 1006.64 442.39

Low 215.8 10 1726.99 758.92

Minimum 491.5 6 3933.01 1728.35




(1280x1024) Maximum 58.4 10 466.11 251.25

High 71.6 10 574.12 296.19

Medium 135.6 10 1085.07 552.06

Low 234.1 10 1872.91 970.95

Minimum 490.2 6 3922.17 2424.20









(320 × 240) Maximum 3 10 24.48 10.76

High 3.4 10 27.55 12.11

Medium 5.5 10 44.16 19.41

Low 8.3 10 66.63 29.28

Minimum 15.9 10 127.36 55.97

(640 × 360) Maximum 7.2 10 58.08 25.53

High 8.1 10 65.52 28.79

Medium 13.2 10 105.99 46.58

Low 20.2 10 161.88 71.13

Minimum 40.8 10 326.15 143.33

(640 × 480) Maximum 9.7 10 77.45 34.04

High 10.9 10 87.36 38.39

Medium 17.7 10 141.33 62.11

Low 27 10 215.84 94.85

Minimum 54.4 10 434.87 191.11

(1280 × 720) Maximum 22.2 10 177.73 78.11

High 24.4 10 196.22 86.23

Medium 38.5 10 307.78 135.26

Low 61.7 10 493.47 216.85

Minimum 138.4 8 1106.84 486.42

3 – Planning

42 Release 200

Simple image

(1280 × 960) Maximum 28.8 10 230.28 101.21

High 30.6 10 245.62 107.94

Medium 48.1 10 384.08 168.79

Low 78.9 10 631.34 277.44

Minimum 194.2 6 1552.46 682.25

(1280×1024) Maximum 30.4 10 243.26 131.14

High 32.6 10 261.88 135.11

Medium 51.8 10 414.00 210.63

Low 85.6 10 684.68 354.95

Minimum 193.6 6 1548.19 956.93









(320 × 240) Maximum 2.6 25 20.52 9.02

High 2.7 25 21.66 9.52

Medium 3.7 25 29.54 12.98

Low 5.1 25 40.69 17.88

Minimum 10.1 25 80.48 35.37

(640 × 360) Maximum 6.15 25 49.2 21.62

High 6.45 25 52.02 22.86

Medium 8.55 25 68.39 30.06

Low 12.075 25 96.84 42.56

Minimum 25.2 25 201.45 88.53

(640 × 480) Maximum 8.2 25 65.61 28.83

High 8.6 25 69.37 30.48

Medium 11.4 25 91.19 40.08

Low 16.1 25 129.13 56.75

Minimum 33.6 25 268.61 118.04



(1280 × 720) Maximum 18.8 10 150.56 66.16

High 19.3 10 155.81 68.46

Medium 24.8 10 198.59 87.28

Low 36.8 10 295.23 129.75

Minimum 85.5 8 683.67 300.44

(1280 × 960) Maximum 24.3 10 195.07 85.72

High 24.1 10 195.04 85.70

Medium 30.9 10 247.82 108.92

Low 47.0 10 377.71 166.00

Minimum 119.9 6 958.92 421.40

(1280×1024) Maximum 25.7 10 206.08 111.06

High 25.7 10 207.95 107.27

Medium 33.3 10 267.12 135.92

Low 51.0 10 409.62 212.37

Minimum 119.6 6 956.28 591.05





3 – Planning

44 Release 200

Axis 210/210A with MPEGThe following data was collected using the Axis 210/210A camera streamer for three levels of image complexity.

Complex image

Resolution Compression Maximum frame rate

Bandwidth (Kbps) at full frame rate (25 fps PAL, 30 fps NTSC)

1-hour recording disk space (MB) at full frame rate (25 fps PAL, 30 fps NTSC)

No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 46.1 69.1 92.2 20.25 30.38 40.51

High 25 65.9 98.8 131.7 28.94 43.41 57.89

Medium 25 102.7 154.1 205.5 45.15 67.72 90.29

Low 25 234.8 352.1 469.5 103.16 154.74 206.32

Minimum 25 312.2 468.3 624.4 137.20 205.80 274.40

(320 × 240) Maximum 25 126.5 189.8 253.0 55.60 83.40 111.20

High 25 195.1 292.6 390.1 85.72 128.58 171.44

Medium 25 336.1 504.2 672.3 147.72 221.58 295.44

Low 25 894.6 1341.8 1789.1 393.11 589.67 786.23

Minimum 25 1181.0 1771.6 2362.1 519.01 778.52 1038.02

(640 × 360) Maximum 25 251.7 377.5 503.3 110.59 165.89 221.19

High 25 397.5 596.3 795.0 174.69 262.03 349.37

Medium 25 681.3 1021.9 1362.6 299.39 449.09 598.78

Low 25 1819.8 2729.8 3639.7 799.73 1199.60 1599.47

Minimum 25 2520.6 3781.0 5041.3 1107.70 1661.55 2215.40

(640 × 480) Maximum 22 335.5 503.3 671.1 147.46 221.19 294.92

High 22 530.0 795.0 1060.0 232.92 349.37 465.83

Medium 22 908.4 1362.6 1816.8 399.19 598.78 798.38

Low 22 2426.5 3639.7 4852.9 1066.31 1599.47 2132.63

Minimum 22 3360.9 5041.3 6721.7 1476.94 2215.40 2953.87







No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 33.2 49.7 66.3 14.57 21.85 29.14

High 25 39.8 59.8 79.7 17.51 26.26 35.02

Medium 25 52.6 78.9 105.3 23.13 34.69 46.26

Low 25 97.4 146.1 194.8 42.79 64.19 85.59

Minimum 25 124.9 187.3 249.8 54.88 82.32 109.76

(320 × 240) Maximum 25 79.1 118.6 158.2 34.76 52.14 69.52

High 25 98.6 147.9 197.1 43.32 64.97 86.63

Medium 25 143.3 215.0 286.6 62.98 94.47 125.96

Low 25 319.3 479.0 638.7 140.34 210.51 280.67

Minimum 25 442.0 663.0 884.0 194.24 291.36 388.47

(640 × 360) Maximum 25 144.5 216.8 289.0 63.50 95.26 127.01

High 25 178.3 267.4 356.6 78.35 117.53 156.70

Medium 25 264.4 396.6 528.7 116.18 174.27 232.36

Low 25 637.8 956.7 1275.6 280.28 420.42 560.56

Minimum 25 787.2 1180.8 1574.4 345.94 518.91 691.89

(640 × 480) Maximum 25 192.7 289.0 385.4 84.67 127.01 169.35

High 25 237.7 356.6 475.4 104.47 156.70 208.94

Medium 25 352.5 528.7 705.0 154.91 232.36 309.81

Low 25 850.4 1275.6 1700.8 373.71 560.56 747.42

Minimum 25 1049.6 1574.4 2099.2 461.26 691.89 922.51

3 – Planning

46 Release 200

Simple image




No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 28.8 43.3 57.7 12.67 19.01 25.35

High 25 33.0 49.5 66.0 14.50 21.76 29.01

Medium 25 41.0 61.5 82.1 18.03 27.05 36.06

Low 25 60.4 90.5 120.7 26.53 39.79 53.05

Minimum 25 73.1 109.7 146.3 32.14 48.22 64.29

(320 × 240) Maximum 25 69.6 104.4 139.2 30.58 45.86 61.15

High 25 78.5 117.7 157.0 34.50 51.74 68.99

Medium 25 96.9 145.4 193.9 42.60 63.90 85.20

Low 25 169.6 254.4 339.3 74.55 111.82 149.09

Minimum 25 220.2 330.3 440.4 96.76 145.14 193.52

(640 × 360) Maximum 25 127.8 191.7 255.6 56.15 84.23 112.31

High 25 142.5 213.8 285.0 62.62 93.93 125.24

Medium 25 176.2 264.3 352.3 77.42 116.13 154.84

Low 25 317.4 476.2 634.9 139.50 209.26 279.01

Minimum 25 443.7 665.5 887.3 194.97 292.46 389.94

(640 × 480) Maximum 25 170.4 255.6 340.8 74.87 112.31 149.75

High 25 190.0 285.0 380.0 83.50 125.24 166.99

Medium 25 234.9 352.3 469.8 103.23 154.84 206.45

Low 25 423.3 634.9 846.5 186.01 279.01 372.01

Minimum 25 591.6 887.3 1183.1 259.96 389.94 519.93



Axis 211/211A with MPEGThe following data was collected using the Axis 211/211A camera streamer for three levels of image complexity.

Complex image




No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 46.1 69.1 92.2 20.25 30.38 40.51

High 25 65.9 98.8 131.7 28.94 43.41 57.89

Medium 25 102.7 154.1 205.5 45.15 67.72 90.29

Low 25 234.8 352.1 469.5 103.16 154.74 206.32

Minimum 25 312.2 468.3 624.4 137.20 205.80 274.40

(240 × 180) Maximum 25 103.7 155.5 207.4 45.57 68.36 91.14

High 25 148.2 222.3 296.4 65.12 97.68 130.24

Medium 25 231.1 346.7 462.3 101.58 152.37 203.16

Low 25 528.2 792.3 1056.4 232.11 348.17 464.23

Minimum 25 702.5 1053.7 1404.9 308.70 463.05 617.40

(320 × 240) Maximum 25 126.5 189.8 253.0 55.60 83.40 111.20

High 25 195.1 292.6 390.1 85.72 128.58 171.44

Medium 25 336.1 504.2 672.3 147.72 221.58 295.44

Low 25 894.6 1341.8 1789.1 393.11 589.67 786.23

Minimum 25 1181.0 1771.6 2362.1 519.01 778.52 1038.02

(480 × 360) Maximum 25 284.7 427.0 569.3 125.10 187.65 250.20

High 25 438.9 658.3 877.8 192.87 289.30 385.73

Medium 25 756.3 1134.5 1512.7 332.37 498.55 664.74

Low 25 2012.7 3019.1 4025.5 884.51 1326.76 1769.01

Minimum 25 2657.3 3986.0 5314.7 1167.78 1751.66 2335.55

(640 × 480) Maximum 22 335.5 503.3 671.1 147.46 221.19 294.92

High 22 530.0 795.0 1060.0 232.92 349.37 465.83

Medium 22 908.4 1362.6 1816.8 399.19 598.78 798.38

Low 22 2426.5 3639.7 4852.9 1066.31 1599.47 2132.63

Minimum 22 3360.9 5041.3 6721.7 1476.94 2215.40 2953.87

3 – Planning

48 Release 200





No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 33.2 49.7 66.3 14.57 21.85 29.14

High 25 39.8 59.8 79.7 17.51 26.26 35.02

Medium 25 52.6 78.9 105.3 23.13 34.69 46.26

Low 25 97.4 146.1 194.8 42.79 64.19 85.59

Minimum 25 124.9 187.3 249.8 54.88 82.32 109.76

(240 × 180) Maximum 25 74.6 111.9 149.2 32.78 49.17 65.56

High 25 89.6 134.5 179.3 39.40 59.09 78.79

Medium 25 118.4 177.6 236.8 52.04 78.06 104.08

Low 25 219.1 328.7 438.2 96.29 144.43 192.57

Minimum 25 281.0 421.5 562.0 123.48 185.22 246.96

(320 × 240) Maximum 25 79.1 118.6 158.2 34.76 52.14 69.52

High 25 98.6 147.9 197.1 43.32 64.97 86.63

Medium 25 143.3 215.0 286.6 62.98 94.47 125.96

Low 25 319.3 479.0 638.7 140.34 210.51 280.67

Minimum 25 442.0 663.0 884.0 194.24 291.36 388.47

(480 × 360) Maximum 25 178.0 266.9 355.9 78.20 117.31 156.41

High 25 221.8 332.7 443.6 97.46 146.19 194.92

Medium 25 322.5 483.7 644.9 141.71 212.56 283.42

Low 25 718.5 1077.8 1437.1 315.76 473.64 631.52

Minimum 25 994.5 1491.7 1989.0 437.03 655.55 874.07

(640 × 480) Maximum 25 192.7 289.0 385.4 84.67 127.01 169.35

High 25 237.7 356.6 475.4 104.47 156.70 208.94

Medium 25 352.5 528.7 705.0 154.91 232.36 309.81

Low 25 850.4 1275.6 1700.8 373.71 560.56 747.42

Minimum 25 1049.6 1574.4 2099.2 461.26 691.89 922.51



Simple image




No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 28.8 43.3 57.7 12.67 19.01 25.35

High 25 33.0 49.5 66.0 14.50 21.76 29.01

Medium 25 41.0 61.5 82.1 18.03 27.05 36.06

Low 25 60.4 90.5 120.7 26.53 39.79 53.05

Minimum 25 73.1 109.7 146.3 32.14 48.22 64.29

(240 × 180) Maximum 25 64.9 97.3 129.8 28.52 42.78 57.04

High 25 74.3 111.4 148.5 32.63 48.95 65.27

Medium 25 92.3 138.5 184.6 40.57 60.86 81.14

Low 25 135.8 203.7 271.6 59.68 89.52 119.36

Minimum 25 164.6 246.9 329.2 72.32 108.49 144.65

(320 × 240) Maximum 25 69.6 104.4 139.2 30.58 45.86 61.15

High 25 78.5 117.7 157.0 34.50 51.74 68.99

Medium 25 96.9 145.4 193.9 42.60 63.90 85.20

Low 25 169.6 254.4 339.3 74.55 111.82 149.09

Minimum 25 220.2 330.3 440.4 96.76 145.14 193.52

(480 × 360) Maximum 25 156.6 234.8 313.1 68.80 103.19 137.59

High 25 176.6 264.9 353.2 77.62 116.42 155.23

Medium 25 218.1 327.1 436.2 95.84 143.77 191.69

Low 25 381.7 572.5 763.3 167.73 251.59 335.46

Minimum 25 495.4 743.1 990.8 217.71 326.56 435.42

(640 × 480) Maximum 25 170.4 255.6 340.8 74.87 112.31 149.75

High 25 190.0 285.0 380.0 83.50 125.24 166.99

Medium 25 234.9 352.3 469.8 103.23 154.84 206.45

Low 25 423.3 634.9 846.5 186.01 279.01 372.01

Minimum 25 591.6 887.3 1183.1 259.96 389.94 519.93

3 – Planning

50 Release 200

Axis 211/211A with Motion JPEGThe following data was collected using the Axis 211/211A camera streamer for three levels of image complexity. The Axis 211A supports audio, see “Recording audio with Axis streamers” on page 112.

Complex image





(160 × 120) Maximum 1.9 25 15.43 6.78

High 2.4 25 19.15 8.42

Medium 4.4 25 35.07 15.41

Low 6.8 25 54.27 23.85

Minimum 12.3 25 98.67 43.36

(240 × 180) Maximum 3.1 25 24.63 10.83

High 4.0 25 32.13 14.12

Medium 8.0 20 64.07 28.15

Low 13.0 20 103.57 45.51

Minimum 23.7 20 189.05 83.08

(320 × 240) Maximum 5.5 25 43.80 19.25

High 7.1 25 57.13 25.11

Medium 14.2 20 113.90 50.05

Low 23.0 18 184.12 80.91

Minimum 42.0 16 336.08 147.69

(480 × 360) Maximum 9.7 20 77.86 34.22

High 12.7 20 101.56 44.63

Medium 25.3 16 202.49 88.98

Low 40.9 14 327.33 143.84

Minimum 74.7 12 597.48 262.56

(640 × 480) Maximum 18.6 14 148.40 65.22

High 23.9 12 191.52 84.16

Medium 46.3 12 370.42 162.79

Low 73.8 11 590.42 259.46

Minimum 137.7 7 1101.70 484.14








(160 × 120) Maximum 1.3 25 10.27 4.51

High 1.4 25 11.60 5.10

Medium 2.1 25 16.89 7.42

Low 3.0 25 23.36 10.27

Minimum 5.1 25 40.77 17.85

(240 × 180) Maximum 1.7 25 13.77 6.05

High 1.9 25 15.50 6.81

Medium 3.1 25 24.84 10.92

Low 4.7 20 37.48 16.47

Minimum 8.9 20 71.64 31.48

(320 × 240) Maximum 3.0 25 24.48 10.76

High 3.4 25 27.55 12.11

Medium 5.5 20 44.16 19.41

Low 8.3 20 66.63 29.28

Minimum 15.9 17 127.36 55.97

(480 × 360) Maximum 5.4 20 43.53 19.12

High 6.1 20 48.98 21.52

Medium 9.8 16 78.51 34.51

Low 14.8 14 118.45 52.05

Minimum 28.3 12 226.41 99.50

(640 × 480) Maximum 9.7 14 77.45 34.04

High 10.9 14 87.36 38.39

Medium 17.7 12 141.33 62.11

Low 27.0 11 215.84 94.85

Minimum 54.4 10 434.87 191.11

3 – Planning

52 Release 200

Simple image





(160 × 120) Maximum 1.1 25 8.93 3.92

High 1.2 25 9.78 4.30

Medium 1.6 25 12.77 5.61

Low 2.0 25 16.57 7.28

Minimum 3.4 25 27.55 12.11

(240 × 180) Maximum 1.4 25 11.54 5.08

High 1.5 25 12.18 5.35

Medium 2.1 25 16.62 7.30

Low 2.9 25 22.89 10.06

Minimum 5.7 25 45.27 19.90

(320 × 240) Maximum 2.6 25 20.52 9.02

High 2.7 25 21.66 9.52

Medium 3.7 25 29.54 12.98

Low 5.1 25 40.69 17.88

Minimum 10.1 20 80.48 35.37

(480 × 360) Maximum 4.6 25 36.48 16.04

High 4.8 25 38.51 16.92

Medium 6.6 20 52.51 23.07

Low 9.0 18 72.34 31.78

Minimum 17.9 16 143.08 62.88

(640 × 480) Maximum 8.2 18 65.61 28.83

High 8.6 18 69.37 30.48

Medium 11.4 16 91.19 40.08

Low 16.1 15 129.13 56.75

Minimum 33.6 14 268.61 118.04



Axis 213, 231D, 232D, 240Q, 241S/241SA and 241Q/241QA with Motion JPEG

The following data was collected using the Axis 213, 231D, 232D, 240Q, 241S, 241SA, 241Q and 241QA Motion JPEG camera streamers for three levels of image complexity. The Axis 241SA and 241QA support audio, see “Recording audio with Axis streamers” on page 112.

Considerations• The Axis 241Q streamer supports up to four cameras, with the total available

frame rate and bandwidth shared across the cameras.

• The 231D/232D is a PTZ camera with built in streamer.

• When viewed, a 4CIF Expanded image is the same size as a 4CIF Interlaced image. However, a 4CIF Expanded image is transmitted and stored in a compressed format (768 × 288) for PAL or (640 × 240) for NTSC and then expanded at the Client (768 × 576) for PAL or (640 × 480) for NTSC.

• The Axis 240Q supports a maximum of 5 fps for PAL and 6 fps for NTSC for each of the four ports.

Complex image





QCIFPAL(192 × 144)

Maximum 2.5 25 20.37 8.95

High 3.2 25 25.28 11.11

Medium 5.8 25 46.29 20.34

Low 9.0 25 71.63 31.48

Minimum 16.3 25 130.24 57.23

CIFPAL(384 × 288)

Maximum 7.2 25 57.81 25.41

High 9.4 25 75.41 33.14

Medium 18.8 25 150.35 66.07

Low 30.4 25 243.04 106.80

Minimum 55.5 25 443.63 194.95

3 – Planning

54 Release 200

4CIF - ExpandedPAL(768 × 576)

Maximum 13.4 25 103.99 47.02

High 17.5 25 140.11 61.57

Medium 35.2 25 281.92 123.89

Low 55.4 25 443.31 194.81

Minimum 98.7 15 789.97 347.16

4CIF - InterlacedPAL(768 × 576)

Maximum 24.5 22 195.89 86.09

High 31.6 20 252.80 111.09

Medium 61.1 17 488.96 214.88

Low 97.4 12 779.36 342.49

Minimum 181.8 11 1454.24 639.07

QCIFNTSC(160 × 120)

Maximum 2.1 30 16.98 7.46

High 2.7 30 21.07 9.26

Medium 4.8 30 38.58 16.95

Low 7.5 30 59.69 26.23

Minimum 13.6 30 108.53 47.69

CIFNTSC(320 × 240)

Maximum 6.0 30 48.18 21.18

High 7.8 30 62.84 27.62

Medium 15.7 30 125.29 55.06

Low 25.3 30 202.53 89.00

Minimum 46.3 30 369.69 162.46

4CIF - ExpandedNTSC(640 × 480)

Maximum 11.2 30 86.66 39.18

High 14.6 30 116.76 51.31

Medium 29.3 30 234.93 103.24

Low 46.2 30 369.43 162.34

Minimum 82.3 16 658.31 289.30

4CIF - InterlacedNTSC(640 × 480)

Maximum 20.4 22 163.24 71.74

High 26.3 21 210.67 92.58

Medium 50.9 18 407.47 179.07

Low 81.2 12 649.47 285.41

Minimum 151.5 12 1211.87 532.56












QCIFPAL(192 × 144)

Maximum 1.7 25 13.55 5.95

High 1.9 25 15.31 6.73

Medium 2.8 25 22.29 9.80

Low 3.9 25 30.83 13.55

Minimum 6.7 25 53.81 23.56

CIFPAL(384 × 288)

Maximum 4.0 25 32.32 14.20

High 4.5 25 36.37 15.98

Medium 7.3 25 58.29 25.62

Low 11.0 25 87.95 38.65

Minimum 21.0 25 168.11 73.88


Maximum 6.7 25 53.87 23.67

High 7.6 25 60.64 26.65

Medium 12.4 25 98.83 43.43

Low 19.1 25 152.59 67.05

Minimum 37.6 25 300.75 132.16


Maximum 12.8 25 102.24 44.93

High 14.4 25 115.31 50.67

Medium 23.3 25 186.56 81.98

Low 35.6 13 284.91 125.20

Minimum 71.8 12 574.03 252.26


Maximum 1.4 30 11.29 4.96

High 1.6 30 12.76 5.61

Medium 2.3 30 18.58 8.17

Low 3.3 30 25.69 11.29

Minimum 5.6 30 44.84 19.63

CIFNTSC(320 × 240)

Maximum 3.3 30 26.93 11.83

High 3.8 30 30.31 13.32

Medium 6.1 30 48.58 21.35

Low 9.2 30 73.29 32.21

Minimum 17.5 30 140.09 61.57

3 – Planning

56 Release 200

Simple image


Maximum 5.6 30 44.89 19.73

High 6.3 30 50.53 22.21

Medium 10.3 30 82.36 36.19

Low 15.9 30 127.16 55.88

Minimum 31.3 30 250.63 110.13


Maximum 10.7 30 85.20 37.44

High 12.0 30 96.09 42.23

Medium 19.4 30 155.47 68.32

Low 29.7 13 237.43 104.33

Minimum 59.8 13 478.36 210.22









QCIFPAL(192 × 144)

Maximum 1.5 25 11.79 5.18

High 1.6 25 12.91 5.67

Medium 2.1 25 16.85 7.41

Low 2.7 25 21.87 9.61

Minimum 4.5 25 36.37 15.98

CIFPAL(384 × 288)

Maximum 3.4 25 27.09 11.91

High 3.6 25 28.59 12.56

Medium 4.9 25 38.99 17.13

Low 6.7 25 53.71 23.60

Minimum 13.3 25 106.24 46.69


Maximum 5.8 25 46.35 20.37

High 6.1 25 48.64 21.38

Medium 8.0 25 64.32 28.27

Low 11.2 25 89.39 39.28

Minimum 23.1 25 184.48 81.07




Maximum 10.8 25 86.61 38.06

High 11.4 25 91.57 40.24

Medium 15.0 25 120.37 52.90

Low 21.3 22 170.45 74.91

Minimum 44.3 16 354.56 155.81


Maximum 1.3 30 9.83 4.32

High 1.3 30 10.76 4.73

Medium 1.8 30 14.04 6.18

Low 2.3 30 18.23 8.01

Minimum 3.8 30 30.31 13.32

CIFNTSC(320 × 240)

Maximum 2.8 30 22.58 9.93

High 3.0 30 23.83 10.47

Medium 4.1 30 32.49 14.28

Low 5.6 30 44.76 19.67

Minimum 11.1 30 88.53 38.91


Maximum 4.8 30 38.63 16.98

High 5.1 30 40.53 17.82

Medium 6.7 30 53.60 23.56

Low 9.3 30 74.49 32.73

Minimum 19.3 30 153.73 67.56


Maximum 9.0 30 72.18 31.72

High 9.5 30 76.31 33.53

Medium 12.5 30 100.31 44.08

Low 17.8 22 142.04 62.43

Minimum 36.9 16 295.47 129.84





3 – Planning

58 Release 200

Axis 221 with MPEGThe following data was collected using the Axis 221 camera streamer for three levels of image complexity.

Complex image




No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 57.6 86.4 115.2 25.31 37.97 50.62

High 25 82.3 123.5 164.6 36.17 54.25 72.34

Medium 25 128.4 192.6 256.8 56.42 84.63 112.84

Low 25 293.4 440.0 586.7 128.92 193.38 257.84

Minimum 25 390.2 585.2 780.3 171.46 257.19 342.91

(240 × 180) Maximum 25 129.6 194.4 259.2 56.95 85.42 113.90

High 25 185.2 277.8 370.4 81.38 122.07 162.76

Medium 25 288.9 433.3 577.7 126.94 190.41 253.88

Low 25 660.1 990.1 1320.1 290.07 435.10 580.14

Minimum 25 877.9 1316.8 1755.7 385.78 578.67 771.56

(320 × 240) Maximum 25 158.1 237.2 316.2 69.48 104.22 138.96

High 25 243.8 365.6 487.5 107.12 160.68 214.24

Medium 25 420.1 630.1 840.1 184.60 276.90 369.20

Low 25 1117.9 1676.9 2235.8 491.27 736.90 982.53

Minimum 25 1475.9 2213.9 2951.8 648.60 972.90 1297.20

(480 × 360) Maximum 25 355.7 533.6 711.5 156.33 234.50 312.66

High 25 548.5 822.7 1096.9 241.02 361.53 482.04

Medium 25 945.2 1417.7 1890.3 415.35 623.03 830.71

Low 25 2515.3 3772.9 5030.6 1105.35 1658.02 2210.69

Minimum 25 3320.8 4981.2 6641.6 1459.34 2189.02 2918.69

(640 × 480) Maximum 25 419.3 629.0 838.7 184.28 276.41 368.55

High 25 662.3 993.5 1324.7 291.07 436.60 582.14

Medium 25 1135.2 1702.8 2270.4 498.86 748.29 997.72

Low 25 3032.3 4548.4 6064.6 1332.55 1998.82 2665.10

Minimum 22 4200.0 6300.0 8400.0 1845.69 2768.54 3691.39







No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 41.4 62.1 82.9 18.21 27.31 36.41

High 25 49.8 74.7 99.6 21.88 32.82 43.76

Medium 25 65.8 98.7 131.5 28.90 43.35 57.81

Low 25 121.7 182.5 243.4 53.48 80.22 106.96

Minimum 25 156.1 234.1 312.1 68.58 102.87 137.17

(240 × 180) Maximum 25 93.2 139.8 186.4 40.97 61.45 81.93

High 25 112.0 168.0 224.1 49.23 73.85 98.47

Medium 25 148.0 222.0 296.0 65.03 97.55 130.06

Low 25 273.8 410.7 547.6 120.33 180.49 240.65

Minimum 25 351.1 526.7 702.3 154.31 231.47 308.62

(320 × 240) Maximum 25 98.8 148.3 197.7 43.44 65.15 86.87

High 25 123.2 184.8 246.4 54.13 81.20 108.26

Medium 25 179.1 268.7 358.2 78.71 118.06 157.41

Low 25 399.1 598.6 798.2 175.38 263.06 350.75

Minimum 25 552.4 828.5 1104.7 242.73 364.10 485.47

(480 × 360) Maximum 25 222.4 333.6 444.8 97.73 146.60 195.46

High 25 277.2 415.7 554.3 121.80 182.69 243.59

Medium 25 403.0 604.5 806.0 177.09 265.64 354.18

Low 25 897.9 1346.9 1795.9 394.60 591.89 789.19

Minimum 25 1242.8 1864.2 2485.6 546.15 819.23 1092.30

(640 × 480) Maximum 25 240.8 361.2 481.6 105.81 158.72 211.63

High 25 297.1 445.6 594.2 130.55 195.83 261.10

Medium 25 440.5 660.8 881.0 193.58 290.37 387.17

Low 25 1062.7 1594.1 2125.4 467.02 700.52 934.03

Minimum 25 1311.7 1967.5 2623.4 576.42 864.63 1152.84

3 – Planning

60 Release 200

Simple image




No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 25 36.0 54.1 72.1 15.84 23.76 31.68

High 25 41.2 61.9 82.5 18.13 27.19 36.25

Medium 25 51.3 76.9 102.6 22.53 33.80 45.07

Low 25 75.4 113.1 150.9 33.15 49.72 66.30

Minimum 25 91.4 137.1 182.8 40.17 60.25 80.34

(240 × 180) Maximum 25 81.1 121.6 162.2 35.64 53.46 71.28

High 25 92.8 139.2 185.6 40.78 61.17 81.56

Medium 25 115.4 173.1 230.8 50.70 76.05 101.40

Low 25 169.7 254.6 339.4 74.58 111.88 149.17

Minimum 25 205.7 308.5 411.3 90.38 135.57 180.76

(320 × 240) Maximum 25 86.9 130.4 173.9 38.21 57.32 76.42

High 25 98.1 147.1 196.2 43.11 64.66 86.22

Medium 25 121.1 181.7 242.3 53.23 79.85 106.47

Low 25 212.0 318.0 424.0 93.16 139.74 186.32

Minimum 25 275.2 412.7 550.3 120.92 181.38 241.84

(480 × 360) Maximum 25 195.6 293.5 391.3 85.97 128.96 171.95

High 25 220.7 331.1 441.4 97.00 145.49 193.99

Medium 25 272.6 408.8 545.1 119.77 179.66 239.55

Low 25 477.0 715.5 953.9 209.61 314.41 419.21

Minimum 25 619.1 928.7 1238.2 272.07 408.10 544.13

(640 × 480) Maximum 25 212.9 319.4 425.8 93.57 140.35 187.13

High 25 237.4 356.2 474.9 104.34 156.52 208.69

Medium 25 293.5 440.3 587.1 129.00 193.50 258.00

Low 25 528.9 793.4 1057.9 232.45 348.67 464.89

Minimum 25 739.3 1108.9 1478.5 324.87 487.31 649.74



Axis 221 with Motion JPEGThe following data was collected using the Axis 221 camera streamer for three levels of image complexity.

Complex image





(160 × 120) Maximum 2.28 45 18.516 8.136

High 2.88 45 22.98 10.104

Medium 5.28 45 42.084 18.492

Low 8.16 45 65.124 28.62

Minimum 14.76 45 118.404 52.032

(240 × 180) Maximum 3.72 42 29.556 12.996

High 4.8 42 38.556 16.944

Medium 9.6 42 76.884 33.78

Low 15.6 42 124.284 54.612

Minimum 28.44 42 226.86 99.696

(320 × 240) Maximum 6.6 40 52.56 23.1

High 8.52 40 68.556 30.132

Medium 17.04 40 136.68 60.06

Low 27.6 40 220.944 97.092

Minimum 50.4 40 403.296 177.228

(480 × 360) Maximum 11.64 36 93.432 41.064

High 15.24 36 121.872 53.556

Medium 30.36 36 242.988 106.776

Low 49.08 36 392.796 172.608

Minimum 89.64 36 716.976 315.072

(640 × 480) Maximum 22.32 30 178.08 78.264

High 28.68 30 229.824 100.992

Medium 55.56 30 444.504 195.348

Low 88.56 30 708.504 311.352

Minimum 165.24 30 1322.04 580.968

3 – Planning

62 Release 200






(160 × 120) Maximum 1.56 45 12.324 5.412

High 1.68 45 13.92 6.12

Medium 2.52 45 20.268 8.904

Low 3.6 45 28.032 12.324

Minimum 6.12 45 48.924 21.42

(240 × 180) Maximum 2.04 43 16.524 7.26

High 2.28 43 18.6 8.172

Medium 3.72 43 29.808 13.104

Low 5.64 43 44.976 19.764

Minimum 10.68 43 85.968 37.776

(320 × 240) Maximum 3.6 41 29.376 12.912

High 4.08 41 33.06 14.532

Medium 6.6 41 52.992 23.292

Low 9.96 41 79.956 35.136

Minimum 19.08 41 152.832 67.164

(480 × 360) Maximum 6.48 38 52.236 22.944

High 7.32 38 58.776 25.824

Medium 11.76 38 94.212 41.412

Low 17.76 38 142.14 62.46

Minimum 33.96 38 271.692 119.4

(640 × 480) Maximum 11.64 32 92.94 40.848

High 13.08 32 104.832 46.068

Medium 21.24 32 169.596 74.532

Low 32.4 32 259.008 113.82

Minimum 65.28 32 521.844 229.332



Simple image





(160 × 120) Maximum 1.32 45 10.716 4.704

High 1.44 45 11.736 5.16

Medium 1.92 45 15.324 6.732

Low 2.4 45 19.884 8.736

Minimum 4.08 45 33.06 14.532

(240 × 180) Maximum 1.68 43 13.848 6.096

High 1.8 43 14.616 6.42

Medium 2.52 43 19.944 8.76

Low 3.48 43 27.468 12.072

Minimum 6.84 43 54.324 23.88

(320 × 240) Maximum 3.12 42 24.624 10.824

High 3.24 42 25.992 11.424

Medium 4.44 42 35.448 15.576

Low 6.12 42 48.828 21.456

Minimum 12.12 42 96.576 42.444

(480 × 360) Maximum 5.52 40 43.776 19.248

High 5.76 40 46.212 20.304

Medium 7.92 40 63.012 27.684

Low 10.8 40 86.808 38.136

Minimum 21.48 40 171.696 75.456

(640 × 480) Maximum 9.84 35 78.732 34.596

High 10.32 35 83.244 36.576

Medium 13.68 35 109.428 48.096

Low 19.32 35 154.956 68.1

Minimum 40.32 35 322.332 141.648

3 – Planning

64 Release 200

Axis 231D, 232D, 241S/241SA and 241Q/241QA with MPEGThe following data was collected using the Axis 231D, 232D, 241S, 241SA, 241Q and 241QA streamers using MPEG video format for three levels of image complexity. This data is based on a GOP (Group of Pictures) value of 8 (the default value used by Honeywell DVM).

The levels of motion are defined as follows:

• No motion is a constant image.

• Low motion is when approximately 25% of the image is continually changing.

• High motion is when approximately 50% of the image is continually changing.

Considerations • The Axis 241Q streamer supports up to four cameras, with the total available


• The 231D/232D is a PTZ camera with built in streamer.


Complex image




No motion

Low motion

High motion

No motion

Low motion

High motion

QCIF PAL (192 × 144) NTSC(160 × 120)

Maximum 25 82.6 124 165.3 36.32 54.49 72.65

High 25 118.1 177.2 236.2 51.91 77.87 103.82

Medium 25 184.2 276.4 368.5 80.97 121.46 161.95

Low 25 421 631.6 842.1 185.03 277.55 370.07

Minimum 25 560 840 1120 246.03 369.14 492.18




CIF PAL (384 × 288) NTSC(320 × 240)

Maximum 25 226.9 340.3 453.8 99.75 149.58 199.45

High 25 349.8 524.8 699.7 153.75 230.62 307.5

Medium 25 602.9 904.4 1205.8 264.96 397.44 529.92

Low 25 1604.5 2406.8 3209 705.11 1057.67 1410.23

Minimum 25 2118.4 3177.6 4236.8 930.93 1396.40 1861.87

4CIF - ExpandedPAL(768 × 576)NTSC(640 × 480)

Maximum 25 415.2 622.8 830.4 182.46 273.69 364.92

High 25 657.6 986.4 1315.2 288.98 433.47 577.96

Medium 25 1161.6 1742.4 2323.2 510.46 765.70 1020.93

Low 25 3203.7 4805.6 6407.4 1407.89 2111.83 2815.78

Minimum 25 4420.2 6630.4 8840.5 1942.5 2913.75 3885

4CIF - InterlacedPAL(768 × 576) NTSC(640 × 480)

Maximum 18 601.8 902.8 1203.7 264.49 396.73 528.98

High 18 950.6 1426 1901.3 417.77 626.66 835.54

Medium 18 1629.3 2444 3258.6 716.01 1074.02 1432.03

Low 18 4352.2 6528.4 8704.5 1912.61 2868.92 3825.23

Minimum 18 6028.2 9042.4 12056.5 2649.14 3973.71 5298.28




No motion

Low motion

High motion

No motion Low motion

High motion

QCIF PAL (192 × 144) NTSC(160 × 120)

Maximum 25 59.4 89.2 118.9 26.13 39.19 52.26

High 25 71.46 107.2 142.9 31.40 47.10 62.81

Medium 25 94.4 141.6 188.8 41.48 62.22 82.96

Low 25 174.6 262 349.3 76.75 115.13 153.51

Minimum 25 224 336 448 98.43 147.65 196.87




No motion

Low motion

High motion

No motion

Low motion

High motion

3 – Planning

66 Release 200

Simple image

CIF PAL (384 × 288) NTSC(320 × 240)

Maximum 25 141.8 212.8 283.7 62.34 93.51 124.68

High 25 176.8 265.2 353.6 77.62 116.54 155.39

Medium 25 257 385.6 514.1 112.94 169.45 225.93

Low 25 572.8 859.2 1145.6 251.76 377.57 503.43

Minimum 25 792.8 1189.2 1585.6 348.34 522.59 696.79

4CIF ExpandedPAL(768 ×576) NTSC(640 × 480)

Maximum 25 237.8 356.8 475.7 104.53 156.79 209.06

High 25 296 444 592 130 195.11 260.15

Medium 25 431.2 646.8 862.4 189.42 284.23 378.98

Low 25 1070.1 1605.2 2140.2 470.27 705.41 940.54

Minimum 25 1493.6 2240.4 2987.2 656.38 984.55 1312.73


Maximum 21 345.6 518.4 691.2 151.83 227.81 303.76

High 21 426.4 639.6 852.8 187.36 281.07 374.76

Medium 21 632.2 948.4 1264.5 277.84 416.77 555.70

Low 21 1525.3 2288 3050.6 670.36 1005.45 1340.62

Minimum 21 1882.6 2824 3765.3 827.38 1241.01 1654.68




No motion

Low motion

High motion

No motion

Low motion

High motion

QCIF PAL (192 × 144) NTSC(160 × 120)

Maximum 25 51.7 77.6 103.4 22.73 34.10 45.468

High 25 59.2 88.8 118.4 26.015 39.02 52.031

Medium 25 73.6 110.4 147.2 32.34 48.51 64.68

Low 25 108.2 162.4 216.5 47.57 71.36 95.15

Minimum 25 131.2 196.8 262.4 57.65 86.48 115.31




No motion

Low motion

High motion

No motion Low motion

High motion



CIF PAL (384 × 288) NTSC(320 × 240)

Maximum 25 124.8 187.2 249.6 54.84 82.26 109.68

High 25 140.8 211.2 281.6 61.87 92.81 123.75

Medium 25 173.8 260.8 347.7 76.40 114.60 152.81

Low 25 304.2 456.4 608.5 133.71 200.56 267.42

Minimum 25 394.9 592.4 789.8 173.55 260.33 347.10

4CIF ExpandedPAL(768 ×576) NTSC(640 × 480)

Maximum 25 207.7 311.6 415.4 91.28 136.93 182.57

High 25 232.5 348.8 465 102.18 153.28 204.37

Medium 25 287.2 430.8 574.4 126.21 189.31 252.42

Low 25 509.3 764 1018.6 223.82 335.74 447.65

Minimum 25 713.6 1070.4 1427.2 313.59 470.39 627.18


Maximum 25 305.6 458.4 611.2 134.29 201.44 268.59

High 25 340.8 511.2 681.6 149.76 224.64 299.53

Medium 25 421.3 632 842.6 185.15 277.73 370.31

Low 25 759.2 1138.8 1518.4 333.63 500.44 667.26

Minimum 25 1061 1591.6 2122.1 466.28 699.43 932.57




No motion

Low motion

High motion

No motion

Low motion

High motion

3 – Planning

68 Release 200

Axis 2100 and 2110 with Motion JPEGThe following data was collected using the Axis 2100 and 2110 camera streamer for three levels of image complexity.

Complex image






Medium(320 × 240)

Maximum 4.2 15 33.70 14.81

High 5.5 13 43.36 19.05

Medium 11.0 13 87.60 38.49

Low 18.3 12 146.55 64.40

Minimum 86.1 10 688.85 302.72

Large(640 × 480)

Maximum 14.5 13 116.28 51.10

High 19.0 12 151.88 66.74

Medium 38.6 12 309.17 135.86

Low 63.0 10 503.39 221.22

Minimum 281.3 5 2250.42 988.95





Medium(320 × 240)

Maximum 2.5 15 20.28 8.92

High 3.0 13 23.36 10.27

Medium 4.6 13 36.97 16.25

Low 7.0 13 56.36 24.77

Minimum 53.2 11 425.37 186.93

Large(640 × 480)

Maximum 8.7 14 69.73 30.64

High 9.7 12 77.73 34.16

Medium 16.0 12 127.64 56.09

Low 25.7 11 205.30 90.22

Minimum 244.0 6 1952.28 857.94



Simple image





Medium(320 × 240)

Maximum 2.1 15 17.17 7.55

High 2.3 15 18.46 8.11

Medium 3.3 14 26.95 11.84

Low 4.9 13 39.27 17.26

Minimum 47.2 12 377.73 166.00

Large(640 × 480)

Maximum 7.6 15 60.85 26.74

High 8.1 13 64.77 28.46

Medium 10.8 12 86.79 38.14

Low 16.9 11 135.15 59.39

Minimum 219.2 7 1753.82 770.72

3 – Planning

70 Release 200

Axis 2120, 2130, 2400 1.x, 2400 2.x, 2401 1.x, 2401 2.x and 2420 with Motion JPEG

The following data was collected using the Axis 2120, 2130, 2400 1.x, 2400 2.x, 2401 1.x, 2401 2.x and 2420 camera streamer for three levels of image complexity.

Considerations• Axis 2120 only supports PAL resolution.

• The Axis 2400 streamer supports up to four cameras, with the total available frame rate and bandwidth shared across the cameras.

• Not all camera streamers support all resolutions.

• The Axis 2400 1.x and 2401 1.x streamers do not support the 4CIF-Expanded resolution. The 4CIF-Expanded resolution is only supported using the latest streamer firmware for the other streamers listed.

Complex image





QCIF PAL (176 × 144) Small

Maximum 2.1 25 16.85 7.41

High 2.6 25 20.64 9.07

Medium 5.0 25 39.79 17.48

Low 7.9 25 63.25 27.80

Minimum 32.6 25 261.01 114.70

CIF PAL (352 × 288) Medium

Maximum 5.6 25 44.48 19.55

High 7.2 25 57.23 25.15

Medium 14.5 25 115.63 50.81

Low 24.2 21 193.44 85.01

Minimum 113.7 12 909.28 399.59

4CIFExpandedPAL(704 × 576)

Maximum 10.9 16 87.48 38.44

High 14.3 16 114.27 50.21

Medium 29.0 16 232.62 102.22

Low 47.3 16 378.75 166.44

Minimum 211.6 8 1693.21 744.08



4CIFInterlacedPAL(704 × 576)Large

Maximum 19.2 8 153.49 67.45

High 25.1 8 200.48 88.10

Medium 51.0 8 408.11 179.34

Low 83.1 8 664.48 292.01

Minimum 371.3 4 2970.56 1305.42

QCIF NTSC (176 × 112) Small

Maximum 1.8 30 14.04 6.18

High 2.2 30 17.20 7.56

Medium 4.2 30 33.16 14.57

Low 6.6 30 52.71 23.17

Minimum 27.2 30 217.51 95.58

CIF NTSC (352 × 240) Medium

Maximum 4.7 30 37.07 16.29

High 6.0 30 47.69 20.96

Medium 12.1 30 96.36 42.34

Low 20.2 22 161.20 70.84

Minimum 94.8 13 757.73 332.99

4CIFExpandedNTSC(704 × 480)

Maximum 9.1 16 72.90 32.03

High 11.9 16 95.22 41.84

Medium 24.2 16 193.85 85.18

Low 39.5 16 315.62 138.70

Minimum 176.3 10 1411.01 620.07

4CIFInterlacedNTSC(704 × 480)Large

Maximum 16.0 8 127.91 56.21

High 20.9 8 167.07 73.42

Medium 42.5 8 340.09 149.45

Low 69.3 8 553.73 243.34

Minimum 309.4 5 2475.47 1087.85





3 – Planning

72 Release 200







Maximum 1.6 25 12.43 5.46

High 1.8 25 14.08 6.19

Medium 2.6 25 21.07 9.26

Low 3.7 25 29.60 13.01

Minimum 19.8 25 158.45 69.63


Maximum 3.3 25 26.77 11.77

High 3.9 25 30.83 13.55

Medium 6.1 25 48.80 21.45

Low 9.3 25 74.40 32.70

Minimum 70.2 14 561.49 246.75


Maximum 6.5 14 52.46 23.05

High 7.2 14 58.48 25.70

Medium 12.0 14 96.03 42.20

Low 19.3 14 154.46 67.88

Minimum 183.5 7 1468.89 645.51


Maximum 11.5 8 92.05 40.45

High 12.8 8 102.61 45.09

Medium 21.1 8 168.48 74.04

Low 33.9 8 270.99 119.09

Minimum 322.1 4 2577.01 1132.48


Maximum 1.3 30 10.36 4.55

High 1.5 30 11.73 5.16

Medium 2.2 30 17.56 7.72

Low 3.1 30 24.67 10.84

Minimum 16.5 30 132.04 58.03


Maximum 2.8 30 22.31 9.81

High 3.3 30 25.69 11.29

Medium 5.1 30 40.67 17.88

Low 7.8 30 62.00 27.25

Minimum 58.5 15 467.91 205.63



Simple image


Maximum 5.4 14 43.7247 19.2147

High 6.1 14 48.7407 21.4206

Medium 10.0 14 80.028 35.169

Low 16.1 14 128.7231 56.5668

Minimum 152.9 7 1224.081 537.9261


Maximum 9.6 8 76.71 33.71

High 10.7 8 85.51 37.58

Medium 17.6 8 140.40 61.70

Low 28.3 8 225.83 99.24

Minimum 268.4 4 2147.51 943.73










Maximum 1.3 25 10.67 4.69

High 1.4 25 11.52 5.06

Medium 2.0 25 16.32 7.17

Low 2.7 25 21.49 9.45

Minimum 17.1 25 136.48 59.98


Maximum 2.8 25 22.67 9.96

High 3.0 25 24.37 10.71

Medium 4.4 25 35.57 15.63

Low 6.5 25 51.84 22.78

Minimum 62.3 12 498.61 219.12


Maximum 5.7 14 45.78 20.12

High 6.0 14 48.72 21.41

Medium 8.1 14 65.29 28.69

Low 12.7 14 101.68 44.68

Minimum 164.9 9 1319.57 579.88

3 – Planning

74 Release 200


Maximum 10.0 8 80.32 35.30

High 10.7 8 85.49 37.57

Medium 14.3 8 114.56 50.34

Low 22.3 8 178.40 78.40

Minimum 289.4 5 2315.04 1017.35


Maximum 1.1 30 8.89 3.91

High 1.2 30 9.60 4.22

Medium 1.7 30 13.60 5.98

Low 2.3 30 17.91 7.88

Minimum 14.3 30 113.73 49.98


Maximum 2.3 30 18.89 8.30

High 2.5 30 20.31 8.93

Medium 3.7 30 29.64 13.03

Low 5.4 30 43.20 18.98

Minimum 51.9 14 415.51 182.60


Maximum 4.7 14 38.15 16.76

High 5.0 14 40.60 17.84

Medium 6.7 14 54.41 23.91

Low 10.6 14 84.74 37.23

Minimum 137.4 9 1099.64 483.24


Maximum 8.3 8 66.93 29.42

High 8.9 8 71.24 31.31

Medium 11.9 8 95.47 41.95

Low 18.6 8 148.67 65.33

Minimum 241.2 5 1929.20 847.79







Axis 2400+, 2401+ and 2411 with Motion JPEGThe following data was collected using the Axis 2400+, 2401+ and 2411 camera streamer for three levels of image complexity.

Considerations• The Axis 2400+ streamer supports up to four cameras, with the total available



• The Axis 2411 does not provide support for controlling PTZ cameras.

Complex image





QCIFPAL(176 × 144)

Maximum 2.1 25 16.85 7.41

High 2.6 25 20.64 9.07

Medium 5.0 25 39.79 17.48

Low 7.9 25 63.25 27.80

Minimum 32.6 25 261.01 114.70

CIFPAL(352 × 288)

Maximum 5.6 25 44.48 19.55

High 7.2 25 57.23 25.15

Medium 14.5 25 115.63 50.81

Low 24.2 25 193.44 85.01

Minimum 113.7 13 909.28 399.59


Maximum 10.8 13 86.24 37.90

High 14.1 13 112.91 49.62

Medium 29.1 13 232.91 102.35

Low 47.3 13 378.61 166.38

Minimum 237.1 8 1897.17 833.72

3 – Planning

76 Release 200


Maximum 19.2 8 153.49 67.45

High 25.1 8 200.48 88.10

Medium 51.0 8 408.11 179.34

Low 83.1 8 664.48 292.01

Minimum 371.3 5 2970.56 1305.42


Maximum 1.8 30 14.04 6.18

High 2.2 30 17.20 7.56

Medium 4.2 30 33.16 14.57

Low 6.6 30 52.71 23.17

Minimum 27.2 30 217.51 95.58

CIFNTSC(352 × 240)

Maximum 4.7 30 37.07 16.29

High 6.0 30 47.69 20.96

Medium 12.1 30 96.36 42.34

Low 20.2 30 161.20 70.84

Minimum 94.8 15 757.73 332.99


Maximum 9.0 15 71.87 31.58

High 11.8 15 94.09 41.35

Medium 24.3 15 194.09 85.29

Low 39.4 15 315.51 138.65

Minimum 197.6 10 1580.98 694.77


Maximum 16.0 10 127.91 56.21

High 20.9 10 167.07 73.42

Medium 42.5 10 340.09 149.45

Low 69.3 10 553.73 243.34

Minimum 309.4 5 2475.47 1087.85












QCIFPAL(176 × 144)

Maximum 1.6 25 12.43 5.46

High 1.8 25 14.08 6.19

Medium 2.6 25 21.07 9.26

Low 3.7 25 29.60 13.01

Minimum 19.8 25 158.45 69.63

CIFPAL(352 × 288)

Maximum 3.3 25 26.77 11.77

High 3.9 25 30.83 13.55

Medium 6.1 25 48.80 21.45

Low 9.3 25 74.40 32.70

Minimum 70.2 13 561.49 246.75


Maximum 6.0 13 48.21 21.19

High 6.7 13 53.87 23.67

Medium 11.0 13 87.73 38.55

Low 17.24 13 139.41 61.27

Minimum 163.8 8 1310.35 575.84


Maximum 11.5 8 92.05 40.45

High 12.8 8 102.61 45.09

Medium 21.1 8 168.48 74.04

Low 33.9 8 270.99 119.09

Minimum 322.1 5 2577.01 1132.48


Maximum 1.3 30 10.36 4.55

High 1.5 30 11.73 5.16

Medium 2.2 30 17.56 7.72

Low 3.1 30 24.67 10.84

Minimum 16.5 30 132.04 58.03

CIFNTSC(352 × 240)

Maximum 2.8 30 22.31 9.81

High 3.3 30 25.69 11.29

Medium 5.1 30 40.67 17.88

Low 7.8 30 62.00 27.25

Minimum 58.5 15 467.91 205.63

3 – Planning

78 Release 200

Simple image


Maximum 5.0 15 40.18 17.66

High 5.6 15 44.89 19.73

Medium 9.2 15 73.11 32.13

Low 14.4 15 116.18 51.06

Minimum 136.5 10 1091.96 479.87


Maximum 9.6 10 76.71 33.71

High 10.7 10 85.51 37.58

Medium 17.6 10 140.40 61.70

Low 28.3 10 225.83 99.24

Minimum 268.4 5 2147.51 943.73









QCIFPAL(176 × 144)

Maximum 1.3 25 10.67 4.69

High 1.4 25 11.52 5.06

Medium 2.0 25 16.32 7.17

Low 2.7 25 21.49 9.45

Minimum 17.1 25 136.48 59.98

CIFPAL(352 × 288)

Maximum 2.8 25 22.67 9.96

High 3.0 25 24.37 10.71

Medium 4.4 25 35.57 15.63

Low 6.5 25 51.84 22.78

Minimum 62.3 13 498.61 219.12


Maximum 5.3 13 42.51 21.19

High 5.7 13 45.55 23.67

Medium 7.8 13 62.35 38.55

Low 11.7 13 93.6 61.27

Minimum 147.3 8 1178.67 575.84




Maximum 10.0 8 80.32 35.30

High 10.7 8 85.49 37.57

Medium 14.3 8 114.56 50.34

Low 22.3 8 178.40 78.40

Minimum 289.4 5 2315.04 1017.35


Maximum 1.1 30 8.89 3.91

High 1.2 30 9.60 4.22

Medium 1.7 30 13.60 5.98

Low 2.3 30 17.91 7.88

Minimum 14.3 30 113.73 49.98

CIFNTSC(352 × 240)

Maximum 2.3 30 18.89 8.30

High 2.5 30 20.31 8.93

Medium 3.7 30 29.64 13.03

Low 5.4 30 43.20 18.98

Minimum 51.9 15 415.51 182.60


Maximum 4.4 15 35.43 17.66

High 4.8 15 37.96 19.73

Medium 6.5 15 51.96 32.13

Low 9.8 15 78.00 51.06

Minimum 122.8 10 982.23 479.87


Maximum 8.3 10 66.93 29.42

High 8.9 10 71.24 31.31

Medium 11.9 10 95.47 41.95

Low 18.6 10 148.67 65.33

Minimum 241.2 5 1929.20 847.79





3 – Planning

80 Release 200

CamStation CS100 with MPEGThe following data was collected using the CamStation CS100 camera streamer for three levels of image complexity.

Considerations• No motion is considered to be a reasonably constant image.



Complex image

Resolution Compression Bandwidth (Kbps) at full frame rate (25 fps PAL, 30 fps NTSC)


No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 148 222 296 65.16 97.74 130.32

High 164 246 328 72.19 108.28 144.38

Medium 189 283 378 83.20 124.80 166.40

Low 212 318 424 93.16 139.74 186.32

Minimum 244 366 488 107.46 161.19 214.92

(320 × 240) Maximum 294 441 588 129.61 194.41 259.22

High 328 492 656 144.14 216.21 288.28

Medium 385 577 770 169.22 253.83 338.44

Low 479 718 958 210.82 316.23 421.64

Minimum 598 897 1196 263.09 394.63 526.18

(640 × 480) Maximum 473 709 946 208.24 312.36 416.48

High 524 786 1048 230.63 345.94 461.26

Medium 612 918 1224 269.18 403.77 538.36

Low 761 1141 1522 334.45 501.67 668.90

Minimum 943 1414 1886 414.49 621.73 828.98




Simple image



No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 109 163 218 48.16 72.24 96.32

High 112 168 224 49.45 74.17 98.90

Medium 114 171 228 50.51 75.76 101.02

Low 122 183 244 53.79 80.68 107.58

Minimum 128 192 256 56.37 84.55 112.74

(320 × 240) Maximum 206 309 412 90.94 136.41 181.88

High 210 315 420 92.46 138.69 184.92

Medium 219 328 438 96.33 144.49 192.66

Low 235 352 470 103.48 155.22 206.96

Minimum 251 376 502 110.39 165.58 220.78

(640 × 480) Maximum 273 409 546 120.35 180.52 240.70

High 282 423 564 123.98 185.97 247.96

Medium 290 435 580 127.50 191.25 255.00

Low 307 460 614 135.12 202.68 270.24

Minimum 324 486 648 142.73 214.09 285.46



No motion

Low motion

High motion

No motion

Low motion

High motion

(160 × 120) Maximum 100 150 200 44.18 66.27 88.36

High 101 151 202 44.77 67.15 89.54

Medium 104 156 208 45.94 68.91 91.88

Low 107 160 214 47.11 70.66 94.22

Minimum 111 166 222 49.1 73.65 98.20

3 – Planning

82 Release 200

(320 × 240) Maximum 180 270 360 79.34 119.01 158.68

High 185 277 370 81.45 122.17 162.90

Medium 188 282 376 82.97 124.45 165.94

Low 196 294 392 86.13 129.19 172.26

Minimum 229 343 458 101.02 151.53 202.04

(640 × 480) Maximum 245 367 490 108.05 162.07 216.10

High 250 375 500 110.16 165.24 220.32

Medium 253 379 506 111.45 167.17 222.90

Low 264 396 528 116.02 174.03 232.04

Minimum 275 412 550 120.94 181.41 241.88



No motion

Low motion

High motion

No motion

Low motion

High motion



CamStation CS-3001V with MPEGThe following data was collected using the CamStation CS-3001V camera streamer for three levels of image complexity.

Considerations• When viewed, a 4CIF Expanded image is the same size as a 4CIF Interlaced

image. However, a 4CIF Expanded image is transmitted and stored in a compressed format (704 × 288) for PAL or (640 × 240) for NTSC and then expanded at the Client (704 × 576) for PAL or (640 × 480) for NTSC.

• No motion is considered to be a reasonably constant image.



• Depending on the complexity of the image, the CS-3001V may not support all combinations of resolution and compression.

Complex image



No motion

Low motion

High motion

No motion

Low motion

High motion

CIFPAL(352 × 288)NTSC(320 × 240)

Maximum 161 241.5 322 71.02 106.53 142.04

High 275 412.5 550 121.05 181.57 242.10

Medium 363 544.5 726 159.73 239.59 319.46

Low 427 640.5 854 187.73 281.59 375.46

Minimum 852 1278 1704 374.77 562.15 749.54


Maximum 343 514.5 686 151.05 226.57 302.10

High 617 925.5 1234 271.52 407.28 543.04

Medium 796 1194 1592 350.16 525.24 700.32

Low 975 1462.5 1950 428.55 642.82 857.10

Minimum 1675 2512.5 3350 736.29 1104.43 1472.58

3 – Planning

84 Release 200


4CIF - InterlacedPAL(704 × 576)NTSC(640 × 480)

Maximum 430 645 860 189.14 283.71 378.28

High 920 1380 1840 404.41 606.615 808.82

Medium 1214 1821 2428 533.91 800.86 1067.82

Low 1522 2283 3044 669.26 1003.89 1338.52

Minimum - - - - - -

D1 - ExpandedPAL(720 × 576)NTSC(720 × 480)

Maximum 236 354 472 103.96 155.94 207.92

High 505 757.5 1010 222.28 333.42 444.56

Medium 667 1000.5 1334 293.46 440.19 586.92

Low 837 1255.5 1674 367.85 551.77 735.70

Minimum 1493 2239.5 2986 656.25 984.37 1312.50

D1 - InterlacedPAL(720 × 576)NTSC(720 × 480)

Maximum 390 585 780 171.75 257.62 343.50

High 835 1252.5 1670 367.22 550.83 734.44

Medium 1103 1654.5 2206 484.80 727.2 969.60

Low - - - - - -

Minimum - - - - - -



No motion

Low motion

High motion

No motion

Low motion

High motion



No motion

Low motion

High motion

No motion

Low motion

High motion

CIFPAL(352 × 288)NTSC(320 × 240)

Maximum 75 112.5 150 33.06 49.59 66.12

High 95 142.5 190 41.85 62.77 83.70

Medium 111 166.5 222 48.91 73.36 97.82

Low 166 249 332 72.95 109.42 145.90

Minimum 318 477 636 139.93 209.89 279.86




Maximum 160 240 320 70.31 105.46 140.62

High 214 321 428 93.87 140.80 187.74

Medium 244 366 488 107.23 160.84 214.46

Low 379 568.5 758 166.52 249.78 333.04

Minimum 625 937.5 1250 274.92 412.38 549.84


Maximum 136 204 272 59.78 89.67 119.56

High 290 435 580 127.82 191.73 255.64

Medium 384 576 768 168.74 253.11 337.48

Low 481 721.5 962 211.52 317.28 423.04

Minimum 877 1315.5 1754 385.55 578.32 771.10


Maximum 75 112.5 150 32.86 49.29 65.72

High 160 240 320 70.25 105.37 140.50

Medium 211 316.5 422 92.75 139.12 185.50

Low 265 397.5 530 116.26 174.39 232.52

Minimum 482 723 964 211.91 317.86 423.82


Maximum 123 184.5 246 54.28 81.42 108.56

High 264 396 528 116.06 174.09 232.12

Medium 349 523.5 698 153.23 229.84 306.46

Low 437 655.5 874 192.07 288.10 384.14

Minimum 797 1195.5 1594 350.09 525.13 700.18



No motion

Low motion

High motion

No motion

Low motion

High motion

3 – Planning

86 Release 200

Simple image



No motion

Low motion

High motion

No motion

Low motion

High motion

CIFPAL(352 × 288)NTSC(320 × 240)

Maximum 56 84 112 24.79 37.18 49.58

High 60 90 120 26.38 39.57 52.76

Medium 102 153 204 45.06 67.59 90.12

Low 114 171 228 50.36 75.54 100.72

Minimum 204 306 408 90.01 135.01 180.02


Maximum 120 180 240 52.73 79.09 105.46

High 134 201 268 59.18 88.77 118.36

Medium 224 336 448 98.79 148.18 197.58

Low 261 391.5 522 114.96 172.44 229.92

Minimum 402 603 804 176.84 265.26 353.68


Maximum 88 132 176 38.45 57.67 76.90

High 187 280.5 374 82.22 123.33 164.44

Medium 246 369 492 108.54 162.81 217.08

Low 309 463.5 618 136.06 204.09 272.12

Minimum 564 846 1128 247.99 371.98 495.98


Maximum 48 72 96 21.13 31.69 42.26

High 102 153 204 45.19 67.78 90.38

Medium 135 202.5 270 59.66 89.49 119.32

Low 170 255 340 74.78 112.17 149.56

Minimum 310 465 620 136.31 204.46 272.62


Maximum 79 118.5 158 34.92 52.38 69.84

High 169 253.5 338 74.65 111.97 149.30

Medium 224 336 448 98.56 147.84 197.12

Low 281 421.5 562 123.54 185.31 247.08

Minimum 512 768 1024 225.19 337.78 450.38



MegaChips OpennetView and MD-100 with Motion JPEGThe following data was collected using the MegaChips OpennetView (ONV) and MD-100 camera streamer for three levels of image complexity.

Considerations• The MegaChips MD-100 supports up to four cameras with the total available


Complex image





Small (160 × 120)

Maximum 1.7 25 13.55 5.95

High 2.8 25 22.24 9.77

Medium 4.6 25 36.69 16.13

Low 7.1 19 57.01 25.05

Minimum 10.4 13 83.47 36.68

Medium (320 × 240)

Maximum 6.1 22 48.75 21.42

High 9.8 14 78.29 34.41

Medium 15.6 9 124.53 54.73

Low 16.9 4 135.20 59.41

Minimum 17.3 2 138.77 60.98

Large (640 × 240)

Maximum 6.1 22 48.75 21.42

High 9.7 14 77.81 34.20

Medium 15.5 9 123.68 54.35

Low 17.3 4 138.67 60.94

Minimum 17.6 2 140.69 61.83

3 – Planning

88 Release 200


Simple image





Small (160 × 120)

Maximum 1.0 25 7.68 3.38

High 1.3 25 10.61 4.66

Medium 1.9 25 15.52 6.82

Low 2.8 25 22.40 9.84

Minimum 4.3 25 34.77 15.28

Medium (320 × 240)

Maximum 2.9 25 22.88 10.05

High 3.9 25 30.93 13.59

Medium 5.5 25 44.37 19.50

Low 8.4 16 67.52 29.67

Minimum 13.7 10 109.33 48.05

Large (640 × 240)

Maximum 2.9 25 22.88 10.05

High 3.9 25 31.09 13.66

Medium 5.6 25 44.69 19.64

Low 8.4 16 67.52 29.67

Minimum 13.6 10 108.59 47.72





Small (160 × 120)

Maximum 0.7 25 5.28 2.32

High 0.9 25 6.88 3.02

Medium 1.2 25 9.39 4.13

Low 1.6 25 13.01 5.72

Minimum 2.5 25 19.84 8.72



Medium (320 × 240)

Maximum 4.5 25 36.11 15.87

High 4.6 25 37.07 16.29

Medium 4.7 25 37.76 16.59

Low 4.9 25 39.20 17.23

Minimum 7.7 18 61.33 26.95

Large (640 × 240)

Maximum 2.0 25 16.05 7.05

High 2.5 25 20.00 8.79

Medium 3.3 25 26.03 11.44

Low 4.6 25 36.69 16.13

Minimum 7.7 18 61.81 27.16





3 – Planning

90 Release 200

Typical storage and bandwidth requirements for audio If you use audio, you must add the following audio requirements to the video requirements:

• 42 Kbps for the bandwidth

• 5KB per second for storage

EBI or Experion integration



Issue CommentsEvent-activated recording Determine which alarms and events need video

recordings. You also need to determine the quality requirements (frame rate, recording duration and so on) for each event-activated recording.

Stations Determine which Stations need to view cameras.See “Stations” on page 92.

Areas (assets) Areas (assets) need to be configured in EBI or Experion before they can be assigned in Honeywell DVM.See “Areas (Assets)” on page 93.

Security Consider your security requirements for an integrated system.See “Security” on page 94.

Custom displays Determine whether you want to include Honeywell DVM functionality in custom displays.See the Honeywell DVM Object Model Reference.

3 – Planning

92 Release 200

StationsDetermine which Stations need to show video. Although any Station can, in principle, show video, such Stations need to be well equipped for satisfactory performance. Also keep in mind that excessive use of video may degrade network and system performance.

See “Hardware and software requirements” on page 116 for the hardware and software requirements for Stations that show video.



Areas (Assets)An area (also called asset) can represent a physical part of a building or plant, or a particular process. (The terminology differs according to product: in EBI it is area; whereas in Experion it is asset.)

Areas enable you to restrict access to:

• Cameras

• Quad views

• Camera Sequences

• Alarms (Operators can filter out alarms that do not belong to their area.)

• Points

• Stations (A Station assigned to a particular area can only access cameras, points, custom displays and reports that are assigned to the same area.)

• Operators, if you use operator-based security

• Custom displays

• Reports

If you use areas, you must carefully assign areas to the various components so that your system works as required. For example, event-activated recording will only work as expected if the following are assigned to the same area as the point:

• The camera used for event-activated recording

• The Station(s) or Internet Explorer client(s) used to view the recorded video

• The operator(s) that need to view the recorded video

Notes• For more information about areas, refer to the EBI or Experion Configuration

Guide.

• You must configure areas in EBI or Experion before you can assign them in Honeywell DVM.

3 – Planning

94 Release 200

SecurityYou need to choose a security setup that best meets your needs. Honeywell DVM provides a range of security features, and supports both domain and workgroup security.

Issue CommentsSecurity types Honeywell DVM supports several types of security.

Select the type that best meets your needs.See “Security types” on page 95.

Windows security Honeywell DVM supports domain and workgroup security. Select the security model that best meets your needs.See “Windows security” on page 96.

Specialized Windows accounts and groups

Learn about the specialized Windows accounts and groups used by Honeywell DVM.See “About the specialized Windows accounts and groups used by Honeywell DVM” on page 98.

Honeywell DVM security levels

Determine how you are going to use Honeywell DVM security levels.See “About Honeywell DVM security levels” on page 100.

Areas (assets) If you have EBI or Experion, decide whether you want to divide your system up into areas (assets).See “Areas (Assets)” on page 93.

Security


Security types Honeywell DVM supports three types of security:

• Internet Explorer security

• Operator-based security (only applicable if you have EBI or Experion)

• Station-based security (only applicable if you have EBI or Experion)

Internet Explorer securityFor Internet Explorer users, Honeywell DVM uses normal Windows security, but with the addition of Honeywell DVM security levels (see page 100).

Operator-based securityYou can use operator-based security if you are using Honeywell DVM in conjunction with EBI or Experion.

Notes• You must configure operator-based security within EBI or Experion before

you can configure security for Honeywell DVM.

• Users can only view live video and recordings for areas that have been assigned to them.

For detailed information about operator-based security, see the EBI or Experion Configuration Guide.

Station-based securityYou can use Station-based security if you are using Honeywell DVM in conjunction with EBI or Experion.

Notes• You must configure Station-based security within EBI or Experion before you

can configure security for Honeywell DVM.

• If you use Station-based security, there are no user IDs, only security levels. When users start Station, they are immediately assigned OPER level. If required, they can then change to a higher level providing they know the password for that level on that Station.

• Users can only view live video and recordings for areas that have been assigned to the Station.

For detailed information about Station-based security, see the EBI or Experion Configuration Guide.

3 – Planning

96 Release 200

Windows security Honeywell DVM supports both domain and workgroup security.

For larger systems, and for systems that include EBI or Experion, we recommend domain security because it significantly simplifies the management of user accounts.

Rules and guidelines for domain security• All Honeywell DVM servers, EBI or Experion servers and client computers

must belong to the same domain. (You cannot, for example, have some client computers outside the domain.)

• On the domain controller, you must create a domain user group for Honeywell DVM users. You must also:

- Add this domain user group to the local group, DVM_Users, on each Database Server and Camera Server.

- Add each user account this domain user group.

• If you use EBI or Experion:

- We recommend the use of integrated accounts because it significantly simplifies the management of user accounts. (An integrated account combines a user's Windows account with the user's operator ID.)

- Stations must run under an account that belongs to the domain user group for Honeywell DVM users.

- If a user needs to access Station on the EBI or Experion server (the “server Station”), that user’s account must also belong to the Honeywell Administrators group.

Rules and guidelines for workgroup security• Each user’s account must exist on:

- Every Database Server and Camera Server

- Every client computer on which the user accesses Honeywell DVM

• Each user’s account must belong to the DVM_Users group on each Database Server and Camera Server.

• The password for each user’s account must be the same on every computer.

• If you have EBI or Experion:

Security


- Each user’s account must belong to the Honeywell Users group (for EBI) or Engineers group (for Experion)

- If a user needs to access Station on an EBI or Experion server (the “server Station”), that user’s account must also belong to the Honeywell Administrators group on that server.

3 – Planning

98 Release 200

About the specialized Windows accounts and groups used by Honeywell DVM

The following table describes the purpose of the specialized Windows accounts and groups used by Honeywell DVM. (Except where specified, these accounts and groups are created when installing Honeywell DVM.)

Note that if you have EBI or Experion, it also uses a number of specialized Windows accounts and groups in addition to the mngr account. For details, see the associated documentation.

Account/group DescriptionWindows accountsDVM_Manager Honeywell DVM services run under this account.

DVM_Logger Honeywell DVM uses this account to write to log files.

mngr Only applicable if you have EBI or Experion. Honeywell DVM uses this account to communicate with EBI or Experion. (It is equivalent to the DVM_Manager account because EBI or Experion services run under this account.).Note: The password for this account must be the same on all Honeywell DVM and EBI or Experion computers.

Honeywell DVM installation account

In order to install any Honeywell DVM components on a computer, you must create a specialized installation account (called the “Honeywell DVM installation account”) on that computer. (For details about the account’s requirements, see “Setting up the Honeywell DVM installation account” on page 217.)This account is only required during installation. When you have completed all installation tasks, you can remove the account if its existence is not approved of by your organization's security policies.

Windows groupsDVM_Users The group to which anyone who uses Honeywell

DVM must belong.

Security


The following table shows where the specialized accounts and groups are used.

Computer Accounts GroupsDatabase Server DVM_Manager

DVM_Logger

mngr

DVM_Users

Camera Server DVM_Manager

DVM_Logger

mngr

DVM_Users

EBI or Experion server - -

Station DVM_Logger

Console Station - -

Internet Explorer client DVM_Logger -

3 – Planning

100 Release 200

About Honeywell DVM security levels The following table describes Honeywell DVM’s security levels. These apply to both Station and Internet Explorer.

Notes• If you use Station-based security, you can “jump” to a particular security level

by entering the password for that level on that Station.

• If you use operator-based security, each person is given an operator ID and assigned a specific security level.

• Honeywell DVM does not support LVL1 or LVL2 access if your system is divided into areas. For example, if you give LV1 operators access to a particular area, they will effectively have OPER security level within that area.

Access rights for operator-based securityThe following table shows the default access rights for Honeywell DVM functions when using operator-based security.

Security level Security level number

Description

LVL1 0 Only allows viewing. This level is only available with operator-based security.

LVL2 1 Only allows alarm acknowledgement. This level is only available with operator-based security.

OPER 2 The standard operator level that allows alarm acknowledgement and routine control.

SUPV 3 Provides access to supervisor-level functions.

ENGR 4 Provides access to engineer-level functions.

MNGR 5 Provides unrestricted access to all functions.

Security


Function LVL1 LVL2 OPER SUPV ENGR MNGRCamera View camera

configuration detailsYes Yes Yes

Add a camera Yes Yes

Delete a camera Yes Yes

Enable/Disable cameras Yes Yes Yes

Edit camera configuration details

Yes Yes

Add a schedule Yes Yes

Delete a schedule Yes Yes

Edit schedule details Yes Yes

Delete a video clip Yes Yes

Export a video clip Yes Yes

Add/Delete a preset Yes Yes Yes

(VCL Orbiter cameras only)Add/Delete a privacy zone

Yes Yes

(VCL Orbiter cameras only)Add/Delete/Configure a tour

Yes Yes

Quad Views View configuration details Yes Yes Yes Yes

Add a quad view Yes Yes Yes

Delete a quad view Yes Yes Yes

Edit configuration details Yes Yes Yes

Sequences View definitions Yes Yes Yes Yes

Add a sequence Yes Yes Yes

Delete a sequence Yes Yes Yes

Change definitions Yes Yes Yes

Audit Log Configure Yes Yes

Export Yes Yes

Search Search for a clip Yes Yes Yes Yes

Redundancy View Redundancy details Yes Yes

Configure the settings Yes Yes

Performance Monitor

View Yes Yes

3 – Planning

102 Release 200

Archive Perform the archive operation

Yes Yes

Video Export Perform the export operation

Yes Yes

Honeywell KD6 Special Presetsi

Run tour 1 Yes Yes Yes Yes



Program tour 1 Yes Yes



Return to manual camera control

Yes Yes

Run vectorscan 1 Yes Yes



Setup menu Yes Yes

Toggle error display Yes Yes

Toggle iris Yes Yes Yes Yes

Toggle backlight control Yes Yes Yes Yes

Toggle nightshot Yes Yes Yes Yes

Freeze Yes Yes Yes Yes

Flashback Yes Yes Yes Yes

Camera reset Yes Yes

Disk space View configuration details Yes Yes

Edit configuration details Yes Yes

Video Analytics

View configuration details Yes Yes

Add object tracking/classification conditions

Yes Yes

Delete object tracking/classification conditions

Yes Yes


i You can configure these security levels. See “Defining special presets” on page 346.

Function LVL1 LVL2 OPER SUPV ENGR MNGR

Security


Access rights for Station-based securityThe following table shows the default access rights for Honeywell DVM functions when using Station-based security.

Function OPER SUPV ENGR MNGRCamera View camera configuration details Yes Yes Yes




Edit camera configuration details Yes Yes







(VCL Orbiter cameras only)Add/Delete a privacy zone Yes Yes

(VCL Orbiter cameras only)Add/Delete/Configure a tour Yes Yes










Export Yes Yes




Performance Monitor View Yes Yes

Archive Perform the archive operation Yes Yes

Video Export Perform the export operation Yes Yes

3 – Planning

104 Release 200

Access rights for Internet ExplorerThe following table shows the default access rights for Honeywell DVM functions when using Internet Explorer.


Run tour 1 Yes Yes

Run tour 2 Yes Yes

Run tour 3 Yes Yes

Program tour 1

Program tour 2

Program tour 3

Return to manual camera control

Run vectorscan 1

Run vectorscan 2

Run vectorscan 3

Setup menu

Toggle error display

Toggle iris Yes Yes

Toggle backlight control Yes Yes

Toggle nightshot Yes Yes

Freeze Yes Yes

Flashback Yes Yes

Camera reset



Video Analytics View configuration details Yes Yes

Add video object tracking/classification conditions

Yes Yes

Delete video object tracking/classification conditions

Yes Yes



Function OPER SUPV ENGR MNGR

Security


Security levelFunction 1 2 3 4 5Camera View camera configuration

detailsYes Yes Yes




Edit camera configuration details Yes Yes







(VCL Orbiter cameras only)Add/Delete a privacy zone Yes Yes

(VCL Orbiter cameras only)Add/Delete/Configure a tour Yes Yes










Export Yes Yes




Performance Monitor

View Yes Yes

Archive Perform the archive operation Yes Yes

Video Export Perform the export operation Yes Yes

3 – Planning

106 Release 200








Return to manual camera control Yes Yes




Setup menu Yes Yes

Toggle error display Yes Yes

Toggle iris Yes Yes Yes Yes

Toggle backlight control Yes Yes Yes Yes

Toggle nightshot Yes Yes Yes Yes

Freeze Yes Yes Yes Yes

Flashback Yes Yes Yes Yes

Camera reset Yes Yes



Video Analytics

View configuration details Yes Yes

Add object tracking/classification conditions

Yes Yes

Delete object tracking/classification conditions

Yes Yes



Security levelFunction 1 2 3 4 5

Digital signatures


Digital signaturesA digital signature is the electronic equivalent of a traditional signature. Honeywell DVM uses digital signatures to authenticate exported videos and audit logs. (When used in conjunction with chain-of-custody processes and procedures, digital signatures greatly enhance the evidential weight of exported videos in legal proceedings.)

Honeywell DVM uses a digital certificate, a specialized file used to “sign” exported videos and audit logs. Depending on your organization’s digital signature requirements, you can use:

• The default digital certificate which is installed on all Honeywell DVM client computersAlthough the default certificate creates a valid signature, its evidential/legal value is reduced because it is used on many Honeywell DVM sites and therefore does not allow you to uniquely identify the computer used to export video clips/audit logs.

• Purchase digital certificate(s) from a certification authority, such as VeriSignSuch digital certificates are recommended if you intend to use videos and audit logs as evidence. (For information about purchasing a certificate from VeriSign, see http://www.verisign.com.)

• Create your own digital certificate(s)If you use Window 2000 Server or Window 2003 Server, you can create your own digital certificates. This may be appropriate if your organization has an IS department with experience in creating digital certificates.

To help assess your digital certificate requirements, contact your local Honeywell representative.

3 – Planning

108 Release 200

About Honeywell DVM serversEvery Honeywell DVM system includes two types of server:

• Database Server. This server is responsible for:

- Storing the configuration and runtime information of the Honeywell DVM system

- Distributing state information to the clients

- Accepting requests from Honeywell DVM clients to view video

• Camera Server. This server is responsible:

- Connecting to video sources

- Transmitting video from the cameras to the clients

- Storing recorded video

- Notifying the Database Server of the system state

If you server-based video analytics to detect motion or to track/classify objects, you also need one or more Video Analytics Servers. See “About Video Analytics Servers” on page 128.

Notes• Although you can install a Database Server and Camera Server on the same

computer, such a configuration is only suitable for small systems.

• Because the server-based video analytics imposes an extremely high processing load on a computer, we strongly recommend that your Video Analytics Servers are on dedicated computers.

• For server hardware and software requirements, see “Hardware and software requirements” on page 116.

• For information about determining the storage requirements for Camera Servers, see “Calculating storage and bandwidth requirements” on page 27.

• You can have redundant Database Servers. See “Database Server redundancy” on page 109.

Database Server redundancy


Database Server redundancyRedundancy is a configuration that allows a backup Database Server to automatically continue the role of the master (referred to as preferred) Database Server in the event of a hardware or software failure on the master Database Server.

The preferred Database Server is the Database Server Honeywell DVM clients will connect to if available.

The backup Database Server is fully operational and ready to take over the role of Database Server if the preferred Database Server fails. The backup Database Server is constantly synchronizing with the preferred Database Server.

ConsiderationsHoneywell DVM only supports redundancy for Database Servers; it does not support redundancy for Camera Servers.

• Honeywell DVM Database Server Redundancy uses SQL Server Merge Replication to keep the SQL Database synchronized. Therefore, after a failover it is possible the data on the backup Database Server might not be consistent with that on the preferred Database Server.When the preferred Database Server is working again, the data can be synchronized between the two servers so they are restored to their correct state.

• It is possible to install a Camera Server on a redundant server. However, we do not recommend this configuration for large systems.

ClientCamera Server Client Client Camera ServerClient

PreferredDatabase Server

BackupDatabase Server

3 – Planning

110 Release 200

• When the primary server is restarted after a failover, it automatically resynchronizes with the backup server, providing it has not been down for more than 14 days. If it has been down for more than 14 days, you must manually resynchronize the servers (see “Manually resynchronizing redundant Database Servers” on page 423.)

• The date and time on all servers must be synchronized to ensure that all dates and/or times associated with events in the database are consistent between servers.

Custom applications and scripts


Custom applications and scripts You can write custom applications and scripts that use the Honeywell DVM Object Model to control Honeywell DVM. For example, you can:

• Integrate Honeywell DVM capabilities into your own applications

• Create custom views and user interfaces for live or recorded video

You can write custom applications in Visual Basic and C++, and scripts in Internet Explorer scripting languages.

If you have EBI or Experion, you can also write display and server scripts that use the Honeywell DVM Object Model. For example, you can:

• Use server scripts to control PTZ cameras when points go into alarm

• Use display scripts to provide specialized controls in custom displays

For more details, see the Honeywell DVM Object Model Reference.

3 – Planning

112 Release 200

Recording audio with Axis streamers Many Axis streamers are capable of supporting audio, either built into the streamer, or available as an external audio module. To find out which streamers support audio, see “Summary of camera streamer capabilities” on page 120.

Supporting video intercom


Supporting video intercomHoneywell DVM supports video intercom functionality using the Megachips MD-100 streamer.

The intercom conversation can be initiated from the field via a push button connected to the MegaChips MD-100 or by an operator from the Honeywell DVM live video page.

3 – Planning

114 Release 200

Camera and video requirements

Camera typesHoneywell DVM supports analog cameras (conventional cameras) and network cameras (cameras with a built-in streamer).

If you have an existing CCTV system, you can integrate it into your Honeywell DVM system by connecting the cameras to the network using camera streamers and standard coaxial cable.

The same distance limitations apply for the coaxial cable as in a conventional CCTV system. Depending on the brand of camera and video streamer, pan tilt and zoom functions are supported via a serial cable from the camera to the streamer.

Issue CommentsNumber and types of camera Determine the number of cameras needed to adequately

monitor your installation. You may be able to reduce the number of cameras by installing PTZ (pan tilt and zoom) cameras rather than fixed cameras.See “Camera types” on page 114 and “Camera streamer types” on page 115.

Viewing requirements Select an appropriate frame rate for each camera. You may prefer 25 fps PAL (30 fps NTSC), but you can substantially reduce storage and networking requirements by selecting a lower frame rate, such as 10 or 15 fps.

Recording requirements Determine the number of frames per second for each camera, and the time for which you need to store the images.Determine the number of frames per second for alarm conditions. Try to set a very conservative rate for background recording (for example, 1 frame every 2 seconds), and use a higher rate (such as 15 fps) for event-activated recording.

Camera control Determine the number of cameras that require PTZ control.

Camera and video requirements


Camera streamer typesHoneywell DVM supports several types of camera streamers (see “Summary of camera streamer capabilities” on page 120), and all supported types of camera streamers can co-exist on the same system.

These camera streamers have an RJ45 network connector that supports 10 Mbps or 100 Mbps Ethernet.

3 – Planning

116 Release 200

Hardware and software requirements

Database Server hardware• Pentium IV 3.2 GHz or higher processor

• At least 512 MB of RAM (1 GB recommended)If you use pre-record you will require more than 512 MB. Contact your local Honeywell representative to discuss your requirements.

• Two hard drives (This enables you to load the Windows OS and executables on one drive, and use the second hard drive for the Honeywell DVM database.)

• If you use this computer as a client, a graphics card which supports 24-bit color or higher.

Remarks• The server should be optimized for hard disk storage. For example, use RAID

and SCSI buses. To configure RAID for your server, refer to the computer documentation.

• Although you can install both the Database Server and Camera Server components on the same computer, such a configuration is only suitable for a small system with low recording requirements. (Note that if you do choose such a configuration, you need a third hard drive for video recording.)

Camera Server hardware• Pentium IV 3.2 GHz or higher processor

• At least 512 MB of RAM (If you use pre-record you will require more than 512 MB. Contact your local Honeywell representative to discuss your requirements.)

• Two hard drives (This enables you to load the Windows OS and executables on one drive, and use the second hard drive for video recording.)

• Use NTFS formatting for video recording.

• If you use this computer as a client, a graphics card which supports 24-bit color or higher.

• Online and offline storage, such as DAT/DLT. This is only required if video clips are to be archived.



Remarks• The server should be optimized for hard disk storage. For example, use RAID

and SCSI buses. To configure RAID for your server, refer to the computer documentation.

Video Analytics Server hardware• Pentium IV 3.2 GHz or higher processor

• At least 1 GB of RAM

• Two hard drives (This enables you to load the Windows OS and executables on one drive, and use the second hard drive for video analytics.)

Database Server software• Either:

- Windows 2000 Server, with Service Pack 4

- Windows 2000 Professional, with Service Pack 4


- Windows XP Professional, with Service Pack 2

• Microsoft Internet Information Server (IIS)

• Microsoft Internet Explorer 6.0, with Service Pack 1, or higher

Remarks• Microsoft SQL Server 2000 license is included with Honeywell DVM.

Camera Server software• Either:






• If used as a client, a graphics card which supports 24-bit color or higher.

3 – Planning

118 Release 200

Video Analytics Server software• Either:






Remarks• Windows 2003 Server or Windows 2000 Server is recommended if the Video

Analytics Server has a dual-core CPU.

EBI hardware and software• EBI R300.1 SP1 or R310.1

• The standard EBI hardware and software requirements apply, except where otherwise specified in this guide. For details, refer to the EBI documentation.

• A graphics card which supports 24-bit color or higher for EBI Stations viewing Honeywell DVM video

Experion hardware and software• Experion R210 Update 1 or R300

• The standard Experion hardware and software requirements apply, except where otherwise specified in this guide. For details, refer to the Experion documentation.

• A graphics card which supports 24-bit color or higher for Experion Stations viewing Honeywell DVM video

Station hardware and softwareStations used extensively for video need to be well equipped to avoid operator dissatisfaction. The recommendations for such Stations are:

• At least 512 MB of RAM

• At least a Pentium III processor

• A graphics card which supports 24-bit color or higher

• Either:








CamerasHoneywell DVM supports:

• PAL and NTSC format

• Analog (conventional) and digital cameras

• PTZ cameras

Camera streamersSee “Summary of camera streamer capabilities” on page 120.

3 – Planning

120 Release 200

Summary of camera streamer capabilities The following table summarizes the capabilities of camera streamers when used with Honeywell DVM. The table was accurate at the time of printing, but may change. For the latest details, contact your local Honeywell representative.

Basic features Compression type Video Analytics AudioStreamer type

Netw

orkC

amer

a(c

amer

a with

a st

ream

er b

uilt

in)

Vide

oSt

ream

er

Num

bero

f vid

eo in

puts

Motio

n JP

EG

MPEG

1

MPEG

4

prop

rieta

ry

Prem

ium

Stan

dard

Stre

amer

-bas

ed

Objec

t Tra

ckin

g

Objec

t Tra

ckin

g an

d Cl

assif

icatio

nSi

ngle

dire

ctio

nal

Bidi

rect

iona

l (In

terc

om)

Axis 205 Yes (Fixed) Yes Yes Yes Yes Yes

Axis 206/206W Yes (Fixed) Yes Yes Yes Yes Yes

Axis 206M Yes (Fixed) Yes Yes Yes Yes Yes

Axis 207i Yes (Fixed) Yes Yes Yes Yes Yes Yes Yes Yes

Axis 210/210A Yes (Fixed) Yes Yes Yes Yes Yes Yes Yes Yesii

Axis 211/211A Yes (Fixed) Yes Yes Yes Yes Yes Yes Yes Yesiii

Axis 213 Yes (PTZ) 1iv Yes Yes Yes Yes Yes Yes Yesiv

Axis 221 Yes (Fixed) Yes Yes Yes Yes Yes Yes Yes

Axis 231D/232D Yes (PTZ Dome) Yes Yes Yes Yes Yes Yes

Axis 240Q Yes 4 Yes Yes Yes Yes Yes Yes

Axis 241S/241SA Yes 1 Yes Yes Yes Yes Yes Yes Yes Yesv

Axis 241Q/241QA Yes 4 Yes Yes Yes Yes Yes Yes Yes Yesvi

Axis 2100vii Yes (Fixed) Yes Yes Yes Yes Yes Yesviii

Axis 2110vii Yes (Fixed) Yes Yes Yes Yes Yes Yesviii

Axis 2120 Yes (Fixed) Yes Yes Yes Yes Yes Yes Yesviii

Axis 2130 Yes (PTZ) Yes Yes Yes Yes Yes

Axis 2400 1.xvii Yes 4 Yes Yes Yes Yes Yes

Axis 2400 2.xvii Yes 4 Yes Yes Yes Yes Yes Yesviii

Axis 2400+vii Yes 4 Yes Yes Yes Yes Yes Yesviii

Summary of camera streamer capabilities


Axis 2401 1.xvii Yes 1 Yes Yes Yes Yes Yes

Axis 2401 2.xvii Yes 1 Yes Yes Yes Yes Yes Yesviii

Axis 2401+vii Yes 1 Yes Yes Yes Yes Yes Yesviii

Axis 2411vii Yes 1 Yes Yes Yes Yes Yes

Axis 2420 Yes (Fixed) Yes Yes Yes Yes Yes Yes Yesviii

CS100 Yes 1 Yes Yes

CS-3001V Yes 1 Yes Yes Yes

MD-100vii Yes 1 Yes Yes Yes Yes Yes Yes Yes

OpennetViewvii Yes 1 Yes Yes Yes Yes Yes

i The Axis 207 has not been qualified for this release.ii Only for Axis 210A streaming Motion JPEGiii Only for Axis 211A streaming Motion JPEGiv Using the Axis 213CM Communication Modulev Only for Axis 241SA streaming Motion JPEGvi Only for Axis 241QA streaming Motion JPEGvii These streamers are discontinued and no longer available from the manufacturer. They are supported in Honeywell DVM

for backwards compatibility.viii Using Axis 2191 audio module. (Honeywell DVM only supports single directional audio (simplex-listen) using this

module.)

Basic features Compression type Video Analytics AudioStreamer type

Netw

orkC

amer

a(c

amer

a with

a st

ream

er b

uilt

in)

Vide

oSt

ream

er

Num

bero

f vid

eo in

puts

Motio

n JP

EG

MPEG

1

MPEG

4

prop

rieta

ry

Prem

ium

Stan

dard

Stre

amer

-bas

ed

Objec

t Tra

ckin

g

Objec

t Tra

ckin

g an

d Cl

assif

icatio

nSi

ngle

dire

ctio

nal

Bidi

rect

iona

l (In

terc

om)

3 – Planning

122 Release 200


4Guidelines for video analytics

This chapter provides guidelines for making best use of Honeywell DVM’s video analytics capabilities.

This chapter also includes:

• A number of example scenarios that describe, in a step-by step manner, how to use video analytics to solve real-life problems

• A checklist to help you successfully implement video analytics

CautionThe basic guideline for successfully using video analytics is to be realistic as to its strengths and weaknesses. Compared with human operators, video analytics has a very low “error tolerance”—for example, it can be fooled by sudden changes in lighting or by objects that stop and start in an erratic manner.In order to obtain satisfactory results from video analytics, you must carefully follow the guidelines in this chapter.

4 – Guidelines for video analytics

124 Release 200

About video analyticsVideo analytics involves using specialized algorithms to detect movement in the video and, optionally, to track and classify moving objects. These algorithms attempt to replicate the way in which security personnel analyze and react when they detect motion in a video.

Figure 3 A typical video, in which objects are being tracked and classified

About video analytics


About the Honeywell DVM video analytics algorithmsHoneywell DVM includes the following algorithms, each of which have their own features:

• Motion detection algorithms

• Object tracking algorithm

• Object tracking and classification algorithm

Motion detection algorithmsThe motion detection algorithms only detect motion—in essence, they detect changes in the video between adjacent frames.

The motion detection algorithms run on either the server (server-based motion detection) or the streamer (streamer-based motion detection).

Server-based motion detection imposes an extremely high load on the server because the server must decompress the incoming video and perform motion detection on each frame.

Streamer-based motion detection does not impose any load on the server. (Note, however, that not all streamers support streamer-based motion detection. To find out which streamers do, see “Summary of camera streamer capabilities” on page 120

The server-based motion detection algorithms are:

• Standard algorithm: designed for indoor use or in scenes where the background is completely stationary

• Premium algorithm: designed for scenes where there is some background movement (such as trees and clouds), it can filter out this movement to prevent false alarms

Object tracking algorithmThe object tracking algorithm attempts to track an object as it moves about, after it has detected the initial movement.

Object tracking and classification algorithmThe object tracking and detection algorithm extends the capabilities of the object tracking algorithm by classifying objects as “person”, “vehicle” and so on.


126 Release 200

About regions of interest and minimum object sizeDepending on the algorithm, you may be able to define one or more regions of interest, and the minimum size of the objects you want the algorithm to detect.

Regions of interestA region of interest (ROI) is a region within the field of view that you want the algorithm to monitor. In practice, ROIs allow you to exclude regions that you don’t want to monitor, such as sky, trees and sides of buildings.

You define region of interests when configuring an algorithm by drawing one or more rectangles or polygons over the video image.

The following figure shows a region of interest that excludes buildings from analysis.

Minimum object sizeThe minimum object size (MOS) is the smallest object that the algorithm is instructed to detect. You typically use the MOS to:

• Prevent false motion detection caused by small objects, such as leaves and rubbish

• Prevent detection of people, when you only want to detect vehicles

You define the MOS when configuring an algorithm by drawing a rectangle over the video image. (Note that the position of the MOS is not relevant.)



The following figure shows a MOS—the magenta rectangle—that is sufficiently small to allow the detection of pedestrians near the end of the carpark.


128 Release 200

About Video Analytics ServersBecause most of the server-based video algorithms impose an extremely high processing load on a computer, we strongly recommend that you use dedicated servers for video analytics—these are called Video Analytics Servers.

Such an architecture not only improves the performance of video analytics, it also ensures that peaks in video analytics processing load (which occur when a lot of objects are being detected/tracked) do not compromise your system’s recording or viewing functions.

The following figure shows the basics of the recommended architecture.

Notes• From a software point of view, a Video Analytics Server is actually a Camera

Server that is reserved for running video analytics algorithms.

• Because the standard algorithm does not impose a heavy processing load, you can run it on a Camera Server, providing you carefully monitor CPU loading.

Processing capacity of a Video Analytics ServerThe number of video signals (server-based algorithms) a Video Analytics Server can simultaneously process depends on a number of factors, such the algorithms you use and the size of the ROIs with respect to the field of view.

The following table specifies the approximate capacity of a Video Analytics Server that meets the hardware and software requirements specified in “Video Analytics Server hardware” on page 117, and which is processing CIF video signals.

Ethernet SwitchCamera Camera Server

Video AnalyticsServer

AttentionFor maximum reliability, we recommend that the steady state CPU loading of a Video Analytics Server does not exceed 70%.



The following table specifies the approximate capacity of a Dual Xeon 3.2 GHz Video Analytics Server processing CIF video signals.

Algorithm Recommended frame rate (fps) for the algorithm

Capacity (video signals)

Standard 3 >60

Premium 3 30

Object tracking 5 4

Object tracking and classification

Algorithm Recommended frame rate (fps) for the algorithm

Capacity (video signals)

Premium 3 45

Object tracking 5 8



130 Release 200

Choosing the appropriate algorithm for the taskYou need to choose the appropriate algorithm for each task. The following table summarizes the relative advantages and disadvantages of each algorithm.

For examples of when to use the various algorithms, see “Example scenarios” on page 134.

Algorithm Advantages Disadvantages SummaryStreamer-based • Lowest cost.

• Does not require any Video Analytics Servers.

• Not generally suited to outdoor use.

• Higher risk of false detections.

A very cost-effective choice for low-priority motion detection.

Standard • Fairly low cost.• Low processing load on

Video Analytics Server.

• Not generally suitable for outdoor use.

• Higher risk of false detections.

A cost-effective choice for low-priority indoor motion detection, where your streamers do not support motion detection.

Premium • Suitable for indoor and outdoor use.

• Several configurable parameters that help minimize the rate of false detections.

• Medium processing load on Video Analytics Server.

Appropriate for indoor/outdoor motion detection where greater reliability is required.

Object tracking • Can specify the minimum size of an object you want to track.

• Can raise alarms based on direction of object movement.

• High processing load on Video Analytics Server.

Allows you to raise alarms based on direction of object movement.


• Distinguishes between different types of object.

• Can specify the minimum size of an object you want to track.

• Can raise alarms based on direction of object movement.

• High processing load on Video Analytics Server.

Allows you to raise alarms based the type of object.



Basic requirements of video analytics algorithmsThe reliability of video analytics is heavily dependent on the suitability of the video it is analyzing. Consequently, when assessing your video analytics needs, you need to pay particular attention to the following factors:

• Minimum number of video frames required

• Frame rate and effective speed of moving objects

• Size/shape of moving objects

• Separation between moving objects

• Objects that become occluded

• Objects that split and merge

• Configurable algorithm properties

Minimum number of video frames requiredIn practical terms, the video analytics algorithms require:

• 4 frames to detect motion, and (in the case of the object tracking algorithm) to assign a track ID

• 7 to 12 frames to assign a track ID and classify an object (the algorithm assigns a track ID within 4 frames, and requires an extra 3 to 8 frames to classify the object)

Frame rate and effective speed of moving objectsIn order to detect motion, the video analytics algorithms require an object to move at a reasonably constant rate and above a minimum speed.

Note that, in the current context, “speed” means the change in the object’s position between frames. For example, if the algorithm can detect an object when the frame rate is 5 fps, it may no longer be able to detect it if you increase the frame rate to 20 fps—because you have reduced the object’s apparent speed by a factor of four.

AttentionAs a general rule, the recommended (and default) frame rates are:• 3 fps for the standard and premium algorithms• 5 fps for the object tracking and object tracking and classification algorithms


132 Release 200

Common problems relating to object speed include:

• If an object moves at a very low speed or starts/stops erratically, the algorithm may interpret it as several objects (each corresponding to separate bursts of motion as it moves across the field of view). In the case of the object tracking and classification algorithm, this will also result in multiple track IDs.

• If an object moves at a very high speed, the object tracking and classification algorithm may not have time to assign a track ID.

Size/shape of moving objectsFor reliable video analytics operation, the shape and size of an object should change in a steady manner as it moves within the field of view.

There are many reasons why an object can appear to suddenly change shape or size—some common examples are:

• The object passes behind/in front of other moving objects—for example, people moving about in a crowded hotel lobby

• The object repeatedly starts/stops or changes direction—for example, people using vending machines or cars entering/exiting a carpark

• The object moves very close to a camera, resulting in large amounts of optical distortion

• The light level in the field of view suddenly changes—for example, a cloud passes overhead or car lights flash across the field of view

Separation between moving objectsIf there are several objects, the algorithm requires that they are separated by at least three pixels for reliable operation.

If they are separated by less than three pixels, the algorithm will merge the objects. In the case of the object tracking and classification algorithm, the algorithm may also incorrectly classify the merged object.

Objects that become occludedAn object may become occluded for a number of reasons, for example:

• The object moves behind a static object such as a pillar or tree

• The object moves sufficiently far from the camera to become smaller than the minimum object size

• The object stops moving

• The object merges with another object



In all these cases, video analytics maintains the track ID it has assigned to the object for 10 frames. If the object reappears during this time period, video analytics continues tracking it. If video analytics cannot redetect the object, the track is deleted—for example if a car stops for more than 10 frames and then starts moving, it will get a new track ID.

Objects that split and mergeIf several closely positioned objects—for example, a family group—enter the scene, video analytics will treat them as a single object. If the objects later separate, video analytics will create new a track ID as each object separates from the group.

If two objects with different track IDs move sufficiently close to each other, resulting in a single “blob” of motion, video analytics assumes that one of the objects has been occluded. If the objects separate within 10 frames, both track IDs are maintained. If the objects continue to move together for more than 10 frames, video analytics will assign a single track ID. If they later separate, one of them will get a new track ID.

Configurable algorithm propertiesEach algorithm has a number of properties that determine how it operates—such as its sensitivity, the level of alarm it raises when it detects motion and the Station/monitor to which it sends the video signal. For details of these properties, see “Configuring video analytics” on page 313.


134 Release 200

Example scenariosThis section describes how you can use video analytics to solve a wide range of real-life problems.

Example scenarios


Detecting vehicles that are moving in the wrong direction

ScenarioBecause of traffic congestion, some drivers who know the layout of your site have attempted to drive the wrong way in a one-way lane. You want to use video analytics to detect such attempts, so that security personnel can alert traffic wardens before the driver causes too much chaos.

SolutionYou decide to use the object tracking and classification algorithm because it can detect movement in a particular direction, and because it can discriminate between vehicles and people.

The main steps in implementing the solution are as follows:

1 You place a camera so that it has a clear view of the lane near the exit (that is, near the illegal entrance).

2 You select the object tracking and classification algorithm.

3 You then define the region of interest and minimum size of an object (MOS) that can be detected as shown in the following figure.Because this region of interest excludes the footpaths, it will exclude most pedestrians. Also, the MOS is large enough to ensure that pedestrians who cross the road do not trigger false alarms.


136 Release 200

4 You define the following condition, and configure it so that it raises an urgent alarm when this condition is met.

Example scenarios


Monitoring a perimeter fence

ScenarioYou want to monitor a perimeter fence to ensure that no one climbs over it into a restricted area. The security guard is notified whenever there is movement in the region of interest.

SolutionYou decide to use the premium algorithm because it continually learns the scene, adapting to the environment. This allows it to ignore environmental changes such as rain, trees swaying and gradual light changes.


1 You place the camera so that it has a clear view of the top of the fence.

2 You select the premium algorithm.

3 You then define the region of interest as shown in the following figure.


138 Release 200

4 You set the algorithm’s:

• Sensitivity property to Outdoor (Low)

• Minimum object size property to the maximum allowable (64 pixels) to minimize the change of birds causing false detections.

Example scenarios


Monitoring the entrance of a secure room

ScenarioYou want to monitor the entrance of your secure room. There are guards watching these cameras 24 hours a day. Whenever there is a motion in front of the entrance, the guard will be notified and he has to verify that the activities are normal and authorized.

SolutionYou decide to use the standard algorithm because it is suitable for simple indoor scenes.


1 You place the camera so that it has a clear view of the entrance you are monitoring.

2 You select the standard algorithm.


140 Release 200

3 You then define the region of interest as shown in the following figure.

4 You set the algorithm’s:

• Optimize for movement property to To/from camera.

• Sensitivity property to 5 (You set the sensitivity to a low value so that wind-induced vibration of the door does not result in false detections.)

Example scenarios


Monitoring people who enter the utilities room

ScenarioFor auditing purposes, you want to keep a recording of everyone who enters the utilities room, which is off a hallway.

Because you do not want to raise an alarm when motion is detected, you are willing to tolerate some “false positives” (people who trigger motion detection, but who do not enter the utilities room).

SolutionTo keep costs down, you decide to use streamer-based motion detection. You position the camera so that it has a good view of people passing or entering the utilities room.

1 You place the camera so that it has a good view of people as they approach the door to the utilities room.

2 You select the streamer-based algorithm for your streamer.

3 You configure the camera’s When motion is detected properties as appropriate. For example, you set Pre-record for to 10 seconds, to maximize the change of being able to identify everyone who enters the utility room.


142 Release 200

Monitoring the direction of objects

ScenarioYou want to monitor cars moving in the wrong direction in a car park. Classification is not required because you know the moving objects are vehicles.

SolutionYou decide to use the object tracking algorithm.


1 You place the camera so that it has a clear view of the section of the car park you are monitoring.

2 You select the object tracking algorithm.

Example scenarios


3 You then define the region of interest and minimum size of an object (MOS) that can be detected as shown in the following figure.

4 You define the following condition, and configure it so that it raises an urgent alarm when this condition is met:Vehicle enters from top to bottom.


144 Release 200

Checklist for successfully implementing video analyticsThis checklist summarizes the main tasks applicable to successfully implementing video analytics.

Task Go to: Done?Assessment phaseAssess your video analytics requirements for your site.To get an idea of how you can use video analytics, see “Example scenarios” on page 134.

Planning and design phaseBased on your assessment, for each video analytics task:

• Choose an appropriate type of camera and streamer. page 145

• Assess the lighting to ensure that it does not affect the reliability of video analytics.

page 148

• Decide where to place the camera. page 150

• Decide how to optimize the camera’s field of view. page 168

• Choose the appropriate algorithm. page 130

• Define the region(s) of interest within the field of view. page 177

• Define the minimum size of objects you want to detect. (Only applicable to the object tracking algorithms.)

page 195

If you have chosen any server-based algorithms, estimate the number of Video Analytics Servers you require.

page 128

Implementation phaseInstall the cameras as planned.

If you need any Video Analytics Servers, install and configure them.

page 128

Configure the cameras (and video analytics) as planned. page 290

Check the real-life operation of video analytics for each camera.If the operation is not satisfactory—for example, it raises too many false alarms—tune the configuration. For example, change the field of view, the size and shape of the region(s) of interest, and the minimum object size.

On each Video Analytics Server, use the Windows Task Manager to check that the steady state CPU loading is not greater than 70%.

Guidelines for choosing cameras and streamers


Guidelines for choosing cameras and streamersThis section provides guidelines for choosing cameras and streamers.

You must ensure that you choose suitable cameras and streamers because video analytics is much more sensitive to the quality of the video signal than human operators.

AttentionThe reliability of video analytics is highly dependent on the quality of the cameras and streamers. You must therefore purchase cameras/streamers that are suited to your video analytics tasks.


146 Release 200

Cameras

Use fixed cameras in preference to PTZ camerasFor reliability reasons, we strongly recommend that you use fixed cameras for video analytics.

Although you can use PTZ cameras, the algorithm’s reliability will be affected because it has to relearn the scene each time an operator uses the PTZ controls. Even if the camera has a “home” preset, camera tolerances may mean that the camera’s configuration may vary each time it returns to the home preset.

If operators need to control a camera, consider using two cameras:

• A fixed camera, used exclusively for video analytics

• A PTZ camera for operator survelliance

Use image stabilization cameras if there is any possibility of camera vibrationA camera that is mounted on tall pylon may provide an excellent view of a scene, but wind induced vibration may prevent reliable video analytics operation because the algorithms cannot not discriminate between camera movement and object movement.

Consequently, in such a scenario, you should use an image stabilization camera.

Consider using day/night cameras if you need to monitor a scene after duskA day/night camera automatically switches from color to black and white (B/W) when light falls below a predefined level.

In practice, video analytics cannot reliably analyze color signals when the light level falls below about 300 lux; however, it can handle B/W signals down to about 170 lux.

You should consider using day/night cameras if, for example, you need to monitor a carpark after dusk.

Consider using infrared or thermal cameras for night-time survellianceInfrared cameras require the scene to be illuminated with infrared lights (typically banks of infrared LEDs).

Thermal cameras detect the infrared radiation emitted by warm objects. Consequently, they are suitable for large-area survelliance, such as perimeter fences and large factory sites.

Guidelines for choosing cameras and streamers


Streamers

Power supply filteringVideo analytics is highly sensitive to any noise in the video signal, which can be caused by spikes in the power grid. You should therefore consider filtering streamer power supplies to minimize such interference.

Dual-signal streamersConsider using dual-signal streamers because they can simultaneously send:

• A Motion JPEG signal to the Video Analytics Server—Motion JPEG is more suitable for video analytics algorithms

• An MPEG signal to the Camera Server for viewing and recording—MPEG is generally better for recording because it requires less disk space


148 Release 200

Guidelines for lightingEven if you cannot control the lighting, you still need to assess how it will affect the reliability of video analytics.

Ensure that the lighting level is adequateIn practice, video analytics cannot reliably analyze color signals when the light level falls below about 300 lux; however, it can handle B/W signals down to about 170 lux. (The level of video noise (“snow”) increases rapidly below these levels, reducing the reliability of video analytics.)

If you need to monitor a scene where the lighting level falls below 300 lux, such as a carpark after dusk, you should consider using a day/night camera. If you want to monitor a scene at night, you should consider using an infrared or thermal camera.

Indoors, ensure that the lighting minimizes shadowsTry to ensure that the lighting is even and minimizes shadows. For example, instead of using one bright light (which produces very strong shadows), use several lower powered, widely spaced lights.

Outdoors, consider how prominent shadows move and change during the day and over the seasonsThe reliability of video analytics can be affected if a scene is divided up into separate zones by prominent shadows—video analytics has difficulty tracking objects as they move between sunny and shaded zones.

You therefore need to pay particular attention to the behavior of shadows throughout the day and from season to season. For example, it is possible to place a camera such that video analytics operates well during summer; but operates erratically during winter because prominent shadows intrude into the field of view.

Guidelines for lighting


Bad exampleThe view contains long horizontal shadows because the camera is pointed due North or South.


150 Release 200

Guidelines for placing camerasThis section provides guidelines for addressing the specialized camera placement requirements for video analytics, and includes:

• Basic guidelines for placing cameras

• Practical examples that show both good and bad camera placement

AttentionThe position of a camera is much more important for video analytics than it is for human operators. A camera that is well placed for use by human operators may not be suitable for video analytics.

Guidelines for placing cameras


Basic guidelines for placing cameras

Determine the predominant direction of movement of objectsVideo analytics works best when objects move either left/right across the field of view or directly towards/away from the camera.

Good exampleThe camera is placed such that its field of view is perpendicular to the road and footpath, which means that cars and most people move directly across the field of view.


152 Release 200

Ensure there is sufficient separation between objectsAs described in “Separation between moving objects” on page 132, video analytics needs at least three pixels separation between objects to reliably detect and track them. In most cases, this means mounting the camera high above the scene.

Good exampleThe high camera position improves the separation between people, allowing video analytics to detect and track them even if they are close together.

Bad exampleThe low camera position means that people will often be occluded as they move behind other people.



Control the near-view to far-view rangeAlthough human operators can easily identify and track very small and very large objects, you can improve the reliability of video analytics if you control the near-view to far-view range so that no object is too small, or too big.

If you need to monitor a large area, consider using several cameras, each of which is zoomed in on a critical region.

Good exampleThe range in sizes between the nearest and most distant objects is small.

Bad examplesDistant objects are too small and near objects too big.


154 Release 200

Vehicles at the far end of the road are very small (even vehicles at the gate—the critical region within the field of view—would be small).

Avoid including obstructions within critical regions of the field of viewThe reliability of video analytics can be affected if objects become occluded by even seemingly minor obstructions. (Even if an object is not completely occluded, it will—from the point of view of video analytics—seem to change shape as it first “merges” with the obstruction and then “splits off” from it.)



Good exampleThis camera angle provides a clear view of the vehicles entering and travelling along the road and is free from obstructions.

Bad exampleThe traffic lights split the pedestrian crossing into two zones. (Note that such a minor obstruction would not worry human operators.)


156 Release 200

In outdoor locations, avoid distant views with small objectsIn outdoor locations, distant views typically result in objects that video analytics cannot reliably detect or track.

Good examplesThe camera has a good view of road and vehicles as the approach the gate.

Bad exampleVehicles beyond the checkpoint are too small to be effectively detected/tracked, and even those at the checkpoint are small.



In indoor locations, place the camera as high as practicableIn indoor locations, you generally need to mount cameras has high as practicable to:

• Increase the separation between people

• Minimize differences in size between people who are near to/far from the camera (This also minimizes optical distortion caused when people get too close to the camera.)

Good examplesThe high camera position gives it a good view of people on the concourse.

Bad exampleThe camera is too low. Consequently, people close to the camera are much larger than those who are far away. Also, optical distortion means that people change shape as they approach the camera.


158 Release 200

In indoor locations, avoid placing cameras at corners or under ceilingsPlacing a camera in a corner or under a ceiling may reduce the reliability of video analytics because of the way in which objects distort and change shape as they move about the field of view. The effect is particularly noticeable with wide-angle lenses.

Examples of such distortion include people whose heads “swell” as the move close to the lens, or who “bend” as they enter/leave the field of view.

Bad exampleThe camera’s position and wide-angle lens means results in significant distortion (change in shape) as people move around the field of view.



Avoid fixtures that split a critical region into separate zonesTry to place the camera so that fixtures, such as pillars, do not split a critical region into separate zones. If an object becomes occluded, video analytics may treat the object as two objects—a first object that disappears when it moves behind the pillar, and a second one that appears on the other side.

In the following figure, the traffic lights split the pedestrian crossing into two zones.

In the following figure, the columns split the lane on the left into several zones.


160 Release 200

Avoid splitting a critical region into heavily shadowed and brightly lit zones

Try to position the camera so that it does not cover both brightly lit and heavily shadowed zones. As an object moves from one zone to another, its color properties will change dramatically, making video analysis harder and less reliable.

Bad examplesA scene in which both people and vehicles frequently move between two zones—one brightly sunlit and the other deeply shadowed.

A scene in which direct sunlight splits pedestrian mall into three zones.



Avoid placing a camera in a confined space with inadequate lightingTry not to place the camera in a confined space with inadequate lighting, such as narrow passages and stairs.

Bad exampleThe field of view contains a large amount of background scenery, in which the lighting produces complex variations in color and brightness.


162 Release 200

Avoid placing a camera opposite elevator or automatic doorsTry not to place the camera opposite elevators or automatic doors because video analytics will treat each opening/closing door as a moving object.

If you want to monitor people as they use such doors, place the camera to one side.

Bad exampleThe constantly opening/closing elevator doors will result in the numerous false detections.



Avoid placing a camera opposite phone booths, ATMs or vending machines

Avoid including phone booths, ATMs or vending machines in critical regions of the scene. Video analytics is not reliable near such devices because people tend to stop and move in an erratic manner when using them. For example, video analytics will typically create at least two objects when someone uses an ATM—a first object as someone approaches the ATM and a second object as the person leaves the ATM.

Bad exampleThe view includes people queuing and using an ATM.


164 Release 200

Avoid placing a camera to the side of stairsIf you want to monitor stairs, try to place the camera in such a position that the hand rails (and hand rail pillars) do not break the view into separate zones. For example, if the hand rail wall is transparent, video analytics will treat each person as two objects—one object above the hand rail and another below the hand rail.

Bad exampleThe hand rail and pillars divide the stairs up into many zones.



Avoid highly reflective, glass-like surfacesVideo analytics will not operate effectively if there are highly reflective, glass-like surfaces within critical regions of the scene. Video analytics cannot distinguish between “real” objects and their reflections, resulting many false detections.

Bad exampleThe lobby’s floor is highly polished, which makes video analysis very difficult. (Also, the automatic doors will compound the problem.)

The highly reflective wall on the left may cause video analytics to classify reflections as separate objects.


166 Release 200

In outdoor locations, shade the camera lens from the sunEnsure that the camera’s lens is well shaded from the sun (or its reflections) at all times of the year.

Bad exampleThe lens is not properly shaded, causing “flare” (loss of definition in contrast and color).



Avoid large regions of continuous motionAvoid placing a camera so that it includes large regions of continuous motion such as busy roads or rivers. (If you cannot avoid including such regions in the field of view, when configuring the algorithm, you will need to use one or more ROIs to exclude them from video analysis.)

Bad exampleMost of the view is occupied by the busy road, whereas you only want to monitor the parking bay.


168 Release 200

Guidelines for adjusting the field of viewThis section provides guidelines for adjusting the field of view of a camera that has already been installed. (For camera placement guidelines, see “Guidelines for placing cameras” on page 150.)

Ideally, you should adjust the field of view so that it:

• Only includes what you want to monitor

• The predominant direction of motion of objects is either to the left/right or towards/away from the camera

Guidelines for adjusting the field of view


Restrict the field of view to what you want to monitorAdjust the camera orientation and lens zoom setting so that the objects you want to monitor occupy most of the field of view.

Good examplesA far-field view, suitable for monitoring both the road and the parked cars.

A near-field view, suitable for monitoring the road junction.


170 Release 200

Bad examplesThe trees occupy far too much of the field of view.

Much of the field of view includes walls and sky, which are of no interest.



Orientate the camera to avoid a skewed field of viewVideo analytics operates most effectively when objects move either horizontally or vertically across the field of view.

A highly skewed field of view causes significant “distortion” when objects are near the corners of the field of view—this effect is particularly noticeable when objects are close to the camera.

Good examplesMost people move directly towards or away from the camera.

Most people move towards or away from the camera.


172 Release 200

Bad ExamplesVehicles become severely distorted when they are close to (almost under) under the camera.

People become severely distorted as they approach the door on the right.



People become severely distorted as the approach the bottom corners of the field of view.


174 Release 200

Adjust the camera for maximum video clarityAdjust the camera’s video settings to maximize the clarity of the video signal. Typical faults you should eliminate include:

• The lens is not focused

• The brightness/contrast adjustment is incorrect

• The lens is unshaded—for example, sun shines onto the lens and cause “flare”

Good examplesThe signal from a correctly adjusted camera.

Bad examplesA poor quality signal, which is badly focused and too bright.



Avoid zones where objects are likely to start-stop in an erratic mannerTry to avoid zones where objects are likely to move in an erratic manner—for example, near phone booths, vending machines and taxi ranks. (If you cannot avoid including such zones in the field of view, when configuring the algorithm, you will need to use one or more ROIs to exclude them from video analysis.)

Bad examplesThe bottom right-hand corner contains a vending machine, where people frequently stop.

The taxi rank will result in a large number of duplicated moving objects because taxis are starting and stopping and people are getting into/out of them.


176 Release 200

Ensure that only far-field views contain intersections or footpathsIf you want to monitor intersections or footpaths, they should only appear as far-field views

Bad examplesA typical outdoor scene containing a corner or turning of a busy road, along with a footpath—such a combination will cause frequent occlusions and track intersections.

Guidelines for defining regions of interest


Guidelines for defining regions of interestThis section provides guidelines to defining regions of interest (ROIs).

ROIs enable you to define which regions within the field of view you want video analytics to monitor—more importantly, they enable you to define which regions you don’t want to monitor. Typical regions you don’t want to monitor include sky, trees and sides of buildings.


178 Release 200

General guidelines for defining regions of interest• The larger the ROI, the longer the object remains in it—which therefore

improves the algorithm’s ability to track objects. So, in cases where you have a choice between defining one large ROI or several small ones, you should define one large one.

• Irregular ROIs (polygons) are a very effective means of excluding regions of the field of view that are of no interest (such as sky or walls), or that the algorithm would have difficulty analyzing (such as dark corners or heavily shadowed/extremely bright regions).



Case 1: road junction and parked cars

Good exampleThe ROI includes the road and carpark, and excludes the building and sky.

Bad examplesAlthough the ROI includes carpark, it also include the building and sky which are of no interest.


180 Release 200

The ROI does not include the whole road junction, and includes the pole (which splits the ROI into two zones).



Case 2: road junction with pedestrians

Good examplesThe ROI includes the zone where people/vehicle movement exists, and excludes the vending machine where people tend to stand/move very slowly (Note that in this scene, vehicles would be too large to be effectively monitored.)

The ROI only includes the top half of the field of view, which contains the footpath and pedestrian crossing, and excludes the bottom half which is prone to excessive people movement, many occlusions and objects that intersect.


182 Release 200

Bad examplesThe ROI includes the vending machine which may result in too many slow-moving/standing human objects causing split tracks and incorrect classification.

The ROI excludes almost everything of interest, such as the footpath and pedestrian crossing.



Case 3: outdoor carpark

Good examplesThe ROI includes the horizontal section of the road so that video analytics can monitor all vehicles moving into/out of the carpark; it also excludes very small, distant objects and the tops of the trees.

The ROI only includes the central region of the carpark, and excludes all trees.


184 Release 200

Bad examplesThe ROI includes most of the far-field scene, which mostly contains very small objects and trees.

The ROI is drawn in such a way that it excludes most of the carpark and road (Also, when cars reverse out of the parking space they will be moving slowly and will only be in the ROI for a few frames).



Case 4: carpark and entrance road

Good examplesThe ROI includes the road, and excludes the top and right of the field of view which mostly contain static objects or trees.

The ROI, although a simple rectangle, includes most of what was included.


186 Release 200

Bad examplesThe ROI includes very small (far-field) objects which will pass behind the trees.

The ROIs include mostly static objects such as trees and the building (as in, the top ROI includes very small objects which pass behind trees, and the bottom ROI includes only a small portion of the road).



Case 5: pedestrian crossings in carpark

Good examplesThe ROI excludes static objects such as pillars and posts, and also excludes very bright and dark regions.

The ROI only includes the central portion of the frame, where the object movement is easiest to detect and classify, and excludes peripheral regions where objects become distorted due to the camera’s position.


188 Release 200

Bad examplesThe ROI includes only the exit region of the carpark, which does not allow tracking of vehicles; it also contains columns, which split the ROI into separate zones.

The ROI only includes part of the pedestrian crossing, a part of which is dominated by bright light. Also, because it is located near a corner, objects in this ROI will be distorted.



Case 6: building lobby with lifts

Good examplesThe ROI excludes the elevator doors, and the stair’s hand rail and pillars.


190 Release 200

Bad examplesThe ROI includes the elevator doors, which will cause false motion alarms.

The ROI includes the stair’s hand rail and pillars.



Case 7: shopping mall (example 1)

Good examplesThe ROI excludes the left and right sides of the shops (where the probability of people standing or moving slowly is high), but includes the central passage way, except the far-field region at the top of the frame.

The ROI only includes the central passage way, were objects are quite large (this type of ROI could also lead to missing tracks/merger of tracks if groups of people pass through the ROI).


192 Release 200

Bad examplesThe ROI includes shop windows which include reflective surfaces, and where people are likely to frequently start/stop.

The ROI includes regions where people are likely to start/stop.



Case 8: shopping mall (example 2)

Good examplesThe ROI excludes all peripheral regions, which are badly illuminated and contain static objects.


194 Release 200

Bad examplesThe ROI includes the busy shop-front (where people start/stop) and which is badly illuminated.

The ROI only includes a small region dominated by bluish light and a thick pillar. (In such a small ROI, objects may not reside long enough for reliable tracking).

Guidelines for defining the minimum object size


Guidelines for defining the minimum object sizeThis section provides guidelines to defining the minimum object size (MOS)—video analytics will not detect or track objects smaller that the MOS.

You need to define a MOS of an appropriate size to prevent excessive false detections, which can be caused by very small objects such as leaves and wind-blown rubbish. In practical terms, the example in “Case 1: outdoor far-field” on page 196 represents the smallest MOS you should define—a smaller MOS would significantly increase the frequency of false detections.

AttentionThe MOS is only applicable to the object tracking and object tracking and classification algorithms.


196 Release 200

Case 1: outdoor far-fieldThe MOS is small enough to enable detection of people who are almost at the end of the carpark.

In practical terms, this example represents the smallest MOS you should define—a smaller MOS would significantly increase the frequency of false detections.



Case 2: outdoor mid-fieldThe MOS enables detection of people who are at the end of the laneway.


198 Release 200

Case 3: outdoor near-fieldThe MOS enables detection of people on the far side of the road.



Case 4: indoor far-fieldThe MOS enables detection of people on the far side of the arcade.


200 Release 200

Case 5: indoor mid-fieldThe MOS enables detection of people in the center of the arcade.


5Installation and upgrade

This chapter describes how to install or upgrade Honeywell DVM, including associated hardware and software.

Start here to successfully install or upgrade your Honeywell DVM system!

Preliminary tasksComplete the tasks in the following order.

CautionThis chapter uses checklists to guide you through installation/upgrade tasks. You must use them to avoid installation/upgrade problems.

Task Go to: Done?Learn how to use the checklists. page 202

Read readme.txt for any last-minute instructions.It is on the Honeywell DVM CD.

Select the appropriate checklists:

• If you are installing a new Honeywell DVM system page 204

• If you are upgrading an existing Honeywell DVM system

page 213

5 – Installation and upgrade

202 Release 200

Using the checklists This guide makes extensive use of checklists to guide you through installation/upgrade tasks. You must use them to avoid installation/upgrade problems.

Tips• Print a copy of the checklists applicable to you, to make it easier to keep track

of your progress.

• Check that you have satisfied the Prerequisites before you start the first task.

• Complete the tasks in order shown, unless specified otherwise.

• When you complete each task, return to the checklist and insert a tick in the Done column.

Using the checklists


Figure 4 A typical checklist


204 Release 200

New installation checklistThis is the top-level checklist for installing a new Honeywell DVM system.

Prerequisites• You have read readme.txt, which is on the Honeywell DVM CD.

• The computers meet the hardware and software requirements (page 116).

• Honeywell DVM CD.

• System Number and Authorization Key.

Considerations• In addition to this checklist, there is a separate checklist for each major

installation task, such as installing Honeywell DVM on a Camera Server. Before starting, you should print a copy of the relevant checklists to make it easier to keep track of progress.

TasksComplete the tasks in the following order.

Task Go to: Done?Install Honeywell DVM on the Database Server(s). page 205

Install Honeywell DVM on the Camera Server(s). page 206

If you want to use any server-based video analytics, install Honeywell DVM on the Video Analytics Server(s).

page 206

If you have an EBI or Experion system, install the Honeywell DVM host components on the server(s):

• Single (non-redundant) EBI or Experion server page 207

• Redundant EBI or Experion servers page 208

If you have an EBI or Experion system, install the:

• Honeywell DVM host components on each Console Station. (Only applicable to Experion.)

page 210

• Honeywell DVM client components on each Station. page 211

If you want Internet Explorer clients to access Honeywell DVM, install the Honeywell DVM client components on the client computers.

page 212

Install and configure camera streamers. page 242

Install and configure PTZ cameras. page 271

New installation checklist


Installation checklist: Database ServerThis is the installation checklist for a new Database Server.

Prerequisites• You have read readme.txt, which is on the Honeywell DVM CD.

• The computer meets the hardware and software requirements (page 116).


• System Number and Authorization Key.

Considerations• If you have redundant Database Servers, you must first install the preferred

Database Server, and then install the backup Database Server.

TasksComplete the tasks in the following order:

TipPrint a copy of this checklist to make it easier to keep track of where you are in the installation process.

Task Go to: Done?Preliminary tasksSet up the Honeywell DVM installation account. page 217

Synchronize the date and time. page 222

Install Internet Information Server (IIS). page 218

If you have a workgroup environment, update the hosts file.

page 240

If you have redundant Database Servers, check that you can ping the other Database Server using the computer name.

page 241

Install the Honeywell DVM componentsIf you have a:

• Non-redundant system, install a non-redundant Database Server.

page 224

• Redundant system, install a redundant Database Server. page 226


206 Release 200

Installation checklist: Camera Server or Video Analytics ServerThis is the installation checklist for a new Camera Server or Video Analytics Server.

Prerequisites• You have installed the Database Server(s).

• The computer meets the hardware and software requirements (page 116).




Task Go to: Done?Preliminary tasksIf this is a Video Analytics Server, turn Hyper threading on.

Set up the Honeywell DVM installation account. page 217



page 240

Check that you can ping the Database Sever using the computer name. (If you have redundant Database Servers, ping both servers.)

page 241

Install the Honeywell DVM componentsInstall the Camera Server. page 230



Installation checklist: single (non-redundant) EBI or Experion serverThis is the checklist for installing the Honeywell DVM host components on a single (non-redundant) EBI or Experion server.

Prerequisites• You have installed and configured your EBI or Experion server in accordance

with the EBI or Experion documentation.

• You have installed the Database Server(s) and Camera Server(s).






Configure Internet Explorer for use with Honeywell DVM. page 221


page 240


page 241

Install the Honeywell DVM host componentsInstall the Honeywell DVM host components. page 232

Post-installation tasksRestart the EBI or Experion server computer(s).

If you want the server Station (Station on this server) to access Honeywell DVM, install the Honeywell DVM client components.

page 234

If you installed the Honeywell DVM client components, configure Station for use with Honeywell DVM.

page 236


208 Release 200

Installation checklist: redundant EBI or Experion serversThis is the checklist for installing the Honeywell DVM host components on redundant EBI or Experion servers.

Prerequisites• You have installed and configured your EBI or Experion server in accordance

with the EBI or Experion documentation.





Task Go to: Done?Preliminary tasksSet up the Honeywell DVM installation account on both servers.

page 217

Synchronize the date and time on both servers. page 222



page 240

On each server, check that you can ping the Database Sever using the computer name. (If you have redundant Database Servers, ping both servers.)

page 241

Install the Honeywell DVM host componentsCheck that the primary server is running as primary.

Install the Honeywell DVM host components on the primary server.

page 232

Manually fail over to the backup server.For details, see the EBI or Experion Configuration Guide.

Restart the primary server.

Install the Honeywell DVM host components on the backup server.

page 232



Manually fail over again so that the primary server is running as primary.

Restart the backup server.

Post-installation tasksIf you want the server Station (Station on this server) to access Honeywell DVM, install the Honeywell DVM client components.

page 234

If you installed the Honeywell DVM client components, configure Station for use with Honeywell DVM.

page 236

Task Go to: Done?


210 Release 200

Installation checklist: Console StationThis is the checklist for installing the Honeywell DVM host components on a Console Station.

Prerequisites• You have installed and configured the Console Station in accordance with the

Experion documentation.








page 240


page 241

Install the Honeywell DVM host componentsInstall the Honeywell DVM host components. page 233

Post-installation tasksInstall the Honeywell DVM client components. page 234

Restart the Console Station computer.

Configure Station for use Honeywell DVM. page 236



Installation checklist: StationThis is the checklist for installing the Honeywell DVM client components on a Station computer.

Prerequisites• You have installed and configured Station in accordance with the instructions

in the EBI or Experion documentation.

• You have installed:

- The Database Server(s) and Camera Server(s)

- The Honeywell DVM host components on the EBI or Experion server(s)

• A digital certificate. (Only required if this computer is to be used for exporting “signed” videos and audit logs, and you want to use your own digital certificate.)






page 240


page 241

Install the Honeywell DVM componentsInstall the Honeywell DVM client components. page 234

Post-installation tasksConfigure Station for Honeywell DVM. page 236

Give this Station (and its users) access to Honeywell DVM. page 394

If this Station is to be used for exporting “signed” videos and audit logs and you have your own digital certificate, configure the digital certificate.

page 343


212 Release 200

Installation checklist: Internet Explorer clientThis is the checklist for installing the Honeywell DVM client components on an Internet Explorer client computer.

Prerequisites• You have installed the Database Server(s) and Camera Server(s).

• You have a Honeywell DVM license for the client.

• A digital certificate. (Only required if this computer is to be used for exporting “signed” videos and audit logs, and you want to use your own digital certificate.)






page 240


page 241

Install the Honeywell DVM componentsInstall the Honeywell DVM client components. page 237

Post-installation tasksGive the users of this Internet Explorer client access to Honeywell DVM.

page 394

If this computer is to be used for exporting “signed” videos and audit logs and you have your own digital certificate, configure the digital certificate.

page 343

Upgrade checklists


Upgrade checklists This section contains a separate top-level checklist for each upgrade scenario.

(If you want to install a new Honeywell DVM system, see “New installation checklist” on page 204.)

If you are upgrading from: Go to:Honeywell DVM R150.3 page 215

Honeywell DVM R160.1/160.2 page 214


214 Release 200

Upgrade checklist: from Honeywell DVM R160.1 or R160.2This is the top-level checklist for upgrading from Honeywell DVM R160.1 or R160.2.

Prerequisites• You have planned for the upgrade. See “Planning for an upgrade” on

page 279.


TipPrint a copy of this checklist to make it easier to keep track of where you are in the upgrade process.

Task Go to: Done?Shut down/close every Honeywell DVM client.

Remove the existing Honeywell DVM components from your servers and clients.

page 280

Upgrade your servers and clients so that they meet the new hardware and software requirements. (As specified in “Hardware and software requirements” on page 116.)

Uninstall SQL Server from the Database Server.

Install Honeywell DVM R200. page 205

Upgrade checklists


Upgrade checklist: from Honeywell DVM R150.3This is the top-level checklist for upgrading from Honeywell DVM R150.3.

Prerequisites• You have planned for the upgrade. See “Planning for an upgrade” on

page 279.


TipPrint a copy of this checklist to make it easier to keep track of where you are in the upgrade process.

Task Go to: Done?Shut down/close every Honeywell DVM client.

If you have EBI or Experion, stop the EBI or Experion server

Remove the existing Honeywell DVM components from your servers and clients.

page 280

Upgrade your servers and clients so that they meet the new hardware and software requirements. (As specified in “Hardware and software requirements” on page 116.)

Uninstall SQL Server from the Database Server.

Install Honeywell DVM R200. page 205


216 Release 200

Installation and setup tasksThis section contains installation and setup tasks.

AttentionOnly complete a task in this section if you are instructed to do so by the appropriate checklist.

Installation and setup tasks


Setting up the Honeywell DVM installation account You must use a specialized installation account to install any Honeywell DVM component on any computer. (This account is called the “Honeywell DVM installation account” in this guide.)

The requirements for the Honeywell DVM installation account are:

• The password for the account is the same on all computers

• The account has administrator privileges on all computers

• If you have EBI or Experion, the account belongs to the Honeywell Administrators group (Note that this is a local group, which exists on EBI or Experion servers and Console Stations.)

If you use domain security, you can use a domain administrator account as the Honeywell DVM installation account, providing all the computers are part of the domain and it has local administrator privileges.

If you do not use domain security, you can configure the default Administrator account on every computer as the Honeywell DVM installation account.

Notes• The Honeywell DVM installation account is only required during installation.

When you have completed all installation tasks, you can remove the account if its existence is not approved of by your organization’s security policies.

You have completed this task. Return to the checklist you came from.


218 Release 200

Installing Internet Information Services (IIS)This task describes how to install and configure Microsoft Internet Information Services (IIS).

Installing IIS for Windows 2000 Professional

Prerequisites• The Windows CD, unless you are installing from a network. (If you are

installing from a network, ask your network administrator for help.)

• The Windows 2000 Certificate of Authenticity, which contains your Product Identification number.

To install IIS:1 Insert the Windows CD into the CD-ROM drive.

2 Select Start > Settings > Control Panel > Add/Remove Programs > Add/Remove Windows Components.

3 Select Internet Information Services (IIS).

4 Click Next.

5 Follow the on-screen instructions to complete the installation.

Installing IIS for Windows 2000 Server

To install IIS:1 Select Start > Control Panel > Add/Remove Programs.

2 Click the Add/Remove Windows Components on the left pane.

3 Select Internet Information Services (IIS) and click Details.

If you have: Go to:Windows 2000 Professional page 218

Windows 2000 Server page 218

Windows XP Professional page 219

Windows 2003 Server page 219




4 Select the following IIS components and subcomponents:(To select subcomponents of a component, select the component and click Details.)

• Internet Information Services Snap-in

• World Wide Web Server

5 Click Next.


Installing IIS for Windows XP Professional



3 Select Internet Information Services (IIS) and click Details.


• Internet Information Services Snap-in

• World Wide Web Services> Printers Virtual Directory> World Wide Web Services

5 Click Next.


Installing IIS for Windows 2003 Server






220 Release 200

3 Select Application Server and click Details.


• Internet Information Services (IIS)> Common Files> Internet Information Service Manager> World Wide Web Service>> Active Server Pages>> World Wide Web Service> SMTP Service

5 Click Next.





Configuring Internet Explorer for use with Honeywell DVMThis task describes how to add the name(s) of the Database Server(s) to Internet Explorer’s trusted sites list.

To add the names to the trusted sites list:1 Open Internet Explorer.

2 Choose Tools > Internet Options.

3 Click the Security tab, select Trusted Sites and click Sites.

4 Clear the Require server verification (https:) for all sites in this zone check box.

5 In the Add this Web site to this zone field:

a. Type http://DVM_ServerA and click Add.where DVM_ServerA is the name of the preferred Database Server.

b. If you have redundant Database Servers, type http://DVM_ServerB and click Add.where DVM_ServerB is the name of the backup Database Server.

6 Click OK to close the Trusted Sites dialog box.

7 Click OK to close the Internet Options dialog box.

8 Close Internet Explorer.



222 Release 200

Synchronizing the date and time on the servers

This task describes how to synchronize the date and time on the servers. (The dates and time must be synchronized to ensure that all dates and/or times associated with events in the database are consistent between servers.)

Synchronizing the date and time involves selecting and setting up a “preferred time source server”, and then configuring every other server so that it synchronizes with that server.

Considerations• If you are using Honeywell DVM in conjunction with EBI or Experion, we

recommend that you use the EBI or Experion server as the preferred time source server.

• If you have a redundant stand-alone Honeywell DVM system (without EBI or Experion), your preferred time source server can be the preferred Database Server, the backup Database Server or a network time source.

Setting up an EBI or Experion server as the preferred time source server

To set up an EBI or Experion server as the preferred time source server:1 Choose Start > Run and run settimesource.vbs, which is located in

the server\run folder. This program is silent if successful.

2 Choose Start > Settings > Control Panel > Administrative Tools > Services.

3 Right-click Windows Time service and select Properties.

4 Set the startup type to Automatic.

5 If the Windows Time service is running, stop it.

6 Restart the Windows Time service.

AttentionYou do not need to complete this procedure if the Database Server belongs to a Windows 2000 or Windows 2003 domain, because time synchronization is already configured.



Synchronizing the time on the other servers

To synchronize the time on the other servers:1 On the other servers, open a Command Prompt window and type:

net time /setsntp:preferredtimesource

where preferredtimesource is the machine name of the preferred time source server.

2 Choose Start > Settings > Control Panel > Administrative Tools > Services.

3 Right-click Windows Time service and select Properties.

4 Set the startup type to Automatic.

5 If the Windows Time service is running, stop it.

6 Restart the Windows Time service.



224 Release 200

Installing the Honeywell DVM Database Server components on a non-redundant server

This task describes how to install the Honeywell DVM Database Server components on a non-redundant server.

Considerations• If you have a small system, you can also install the Camera Server.

To install:1 Log on using the Honeywell DVM installation account.

2 Insert the Honeywell DVM CD into the computer. The “autorun” setup wizard starts. (If the wizard doesn’t start, open Windows Explorer, navigate to the Server folder on the CD and double-click setup.exe.)

3 If requested, click Restart to upgrade the version of Windows Installer.When the computer restarts, log on again using the Honeywell DVM installation account.

4 When the Welcome screen appears, click Next.

5 Read the installation notes and then click Next.

6 Enter your name and your company name, and then click Next.

7 If you are installing:

• The Database Server, select Database Server.

• The Database Server and Camera Server, select Database Server and Camera Server.

8 Click Next.

9 Enter the Honeywell DVM System Number and Authorization Key from your Honeywell DVM software license and then click Next.

10 Select a folder for the Honeywell DVM software and then click Next.Choose the drive on which Windows is installed (typically the “C” drive).

11 Select a folder for the Honeywell DVM database and then click Next.Choose the hard drive on which Windows is not installed (typically the “D” drive).

12 If you are:

• Only installing a Database Server, go to step 15.

• If you are installing a Database Server and Camera Server go to step 13.



13 Select a folder where the video clips are to be stored, and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

14 Select a folder where the video clips are to be archived, and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

15 If Microsoft SQL Server 2000 has not been installed, select a folder to install the software and then click Next.Choose the drive on which Windows is installed (typically the “C” drive).

16 If requested, enter and confirm the password for the Windows mngr account and then click Next.

17 Confirm the details and then click Next to begin the installation.

18 Agree to restart the computer and click Finish.



226 Release 200

Installing the Honeywell DVM Database Server components on redundant servers

This task describes how to install the Honeywell DVM Database Server components on redundant servers.

You must separately install the components on each server. Note that the first server on which you install the components becomes the “preferred” Database Server.

Installing the Honeywell DVM Database Server on the first (preferred) server



3 If requested, click Restart to upgrade the version of Windows Installer.When the computer restarts, log on using the Honeywell DVM installation account.



6 Enter your name and your company name and then click Next.




8 Click Next.

9 Enter the Honeywell DVM System Number and Authorization Key from your Honeywell DVM software license, and then click Next.

10 Select I wish to install the first Database Server of a redundant pair.





13 If you are:


• If you are installing a Database Server and Camera Server, go to step 14.

14 Select a folder where the video clips are to be stored and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

15 Select a folder where the video clips are to be archived and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

16 If Microsoft SQL Server 2000 is not already installed, select a folder to install the software and then click Next.Choose the drive on which Windows is installed (typically the “C” drive).



19 If requested, agree to restart the computer and log on using the Honeywell DVM installation account.

20 If requested, agree to continue the installation.

21 When the Installation Wizard Complete screen appears, agree to restart the computer and click Finish.

Installation of the preferred Database Server of a redundant pair is now complete.

Installing the Honeywell DVM Database Server on the second server








228 Release 200




8 Click Next.

9 Enter the Honeywell DVM System Number and Authorization Key from your Honeywell DVM software license, and then click Next.

10 Select I wish to create a redundant pair with an existing Database Server. Click Next.

11 Enter the computer name of the first (preferred) Database Server computer and then click Next.



14 If you are:


• If you are installing a Database Server and Camera Server, go to step 15.

15 Select a folder where the video clips are to be stored and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

16 Select a folder where the video clips are to be archived and then click Next.Choose the hard drive on which Windows and the Honeywell DVM database are not installed (typically the “E” drive).

17 If Microsoft SQL Server 2000 is not already installed, select a folder to install the software and then click Next.Choose the drive on which Windows is installed (typically the “C” drive).



20 If requested, agree to restart the computer and log on using the Honeywell DVM installation account.



21 If requested, agree to continue the installation.

22 When the Installation Wizard Complete screen appears, agree to restart the computer and click Finish.



230 Release 200

Installing the Honeywell DVM Camera Server componentsThis task describes how to install the Honeywell DVM Camera Server components on a Camera Server.

Prerequisites• The name of the Database Server. (If you have redundant Database Servers,

use the name of the preferred Database Server.)


2 Insert the Honeywell DVM CD into the computer. The “autorun” setup wizard starts. (If the wizard doesn’t start, open Windows Explorer and double- click setup.exe on the CD.)

3 If requested, click Restart to upgrade the version of Windows Installer.After restarting, log on using the Honeywell DVM installation account.



6 Enter your name and your company name, and then click Next.

7 Select Camera Server, and then click Next.

8 Select a folder for the Honeywell DVM software, and then click Next.Choose the drive on which Windows is installed (typically the “C” drive).

9 Select a folder where the video clips are to be stored, and then click Next.Choose the hard drive on which Windows is not installed (typically the “D” drive).

10 Select a folder where the video clips are to be archived, and then click Next.Choose the hard drive on which Windows is not installed (typically the “D” drive).

11 If requested, enter and confirm the password fro the Windows mngr account, and then click Next.

12 Enter the name of the Honeywell DVM Database Server, and then click Next.



13 Confirm the details and then click Next to begin the installation.If a dialog box appears informing you that the Database Server is not available, check that you have entered the correct name and click OK.

14 Agree to restart the computer if requested.



232 Release 200

Installing the Honeywell DVM host components on the EBI or Experion server

This task describes how to install the Honeywell DVM host components on an EBI or Experion server.



• EBI or Experion is running.

• mngr password for the EBI or Experion server.

To install the Honeywell DVM host components:1 Log on to the EBI or Experion server using the Honeywell DVM installation

account.

2 Check that EBI or Experion is running.






8 Select Host Components and then click Next.

9 Enter and confirm the password for the Windows mngr account and then click Next.

10 Enter the name of the Database Server, and then click Next.

11 Confirm the installation details and then click Next to begin the installation.

12 Click Finish.




Installing the Honeywell DVM host components on a Console StationThis task describes how to install the Honeywell DVM host components on a Console Station.



• The Console Station is running.

• mngr password for the EBI or Experion server.

To install the Console Station host components:1 Log on using the Honeywell DVM installation account.

2 Ensure that Experion Console Station is running.






8 Select Host Components and then click Next.

9 Enter and confirm the password for the Windows mngr account and then click Next.

10 Enter the name of the Database Server and then click Next.

11 Confirm the installation details and then click Next to begin the installation.

12 Click Finish.



234 Release 200

Installing the Honeywell DVM client components on a Station computerThis task describes how to install the Honeywell DVM client components on a Station computer.

To install the client components:1 Log on to the computer using the Honeywell DVM installation account.

2 Log on to Station with MNGR security level.

3 Click on Station’s toolbar to call up the System Menu.

4 Click (the Honeywell Digital Video Manager icon) on the System Menu. Station connects to the Honeywell DVM system.(If you have an EBI system, the icon appears under Access Control and Security. If you have an Experion system, the icon appears under Options.)

5 If requested, agree to trust information from Honeywell.

6 When the Digital Video Client setup screen appears, click Next.

7 Select a location for the client files and then click Next.

8 Check the settings and then click Next to start the installation.The Importing a new private signature key screen appears. By default, the security level is set to Medium.

9 If:

• This security level is correct, click OK and go to step 11.

• You want to change the security level, click Set Security Level. Select the required security level (as described in the following table) and click Next.

10 Click Finish and then click OK.

11 Click Finish.

Security Level DescriptionMedium Users will be prompted to confirm that the digital

certificate is to be used for signing.All users will have access to the digital certificate for signing.

High Users will be required to enter a password to access the digital certificate when it is to be used for signing.Only users with the password will have access to the digital certificate for signing.



12 Restart Station and click OK to refresh the screen.An error screen indicating that you do not have permission to access Honeywell DVM appears.

13 Log on as a Station user who has been assigned Honeywell DVM user privileges.



236 Release 200

Configuring Station for use with Honeywell DVMThis task describes how to configure Station for use with Honeywell DVM.

To configure Station:1 Log on to the computer using the Honeywell DVM installation account.

2 Start Station.

3 Choose Station > Connection Properties. The Connection Properties dialog box opens.

4 Click the Web Access tab and the click Advanced to display all properties.

5 Select The following URLs only.

6 Click Add and type the address of each Database Server. The format of the address is:http://DVM_ServerA/*

http://DVM_ServerB/*

where DVM_ServerA is the name of the preferred Database Server and DVM_ServerB is the name of the backup Database Server. (Note that if you omit the asterisk, operators will only be able to access the home page.)

7 Click Save to save your changes to the current Station setup file.




Installing the Honeywell DVM client components for an Internet Explorer client computer

This task describes how to install the Honeywell DVM client components on a client computer that uses Internet Explorer to access Honeywell DVM.

Prerequisites• The computer meets the software requirements (page 116).

To install the client components:1 Log onto Windows using the Windows account from which you installed

Honeywell DVM (the Honeywell installation account).

2 Open Internet Explorer.

3 Choose Tools > Internet Options.

4 Go to the Security page, select Trusted Sites and click Sites.

5 Clear the Require server verification (https:) for all sites in this zone check box.

6 In the Add this Web site to this zone field, type:

a. http://DVM_ServerA and click Add.where DVM_ServerA is the name of the preferred Honeywell DVM Database Server.

b. http://ServerB and click Add.where DVM_ServerB is the name of the backup Honeywell DVM Database Server.

c. Click OK.

7 Click OK to close the Internet Options dialog box.

8 Enter the URL to Honeywell DVM’s main page (for example, http://machinename/dvm) and press ENTER.Where machinename is the name of the Honeywell DVM Database Server (in a redundant server system, the name of the preferred Honeywell DVM Database Server).

AttentionYou do not need to complete this task if Station is on the computer, and it has been configured to access Honeywell DVM.


238 Release 200

9 If you have Windows 2000 or Windows XP, Agree to trust information from Honeywell and go to step 10.If you have Windows 2003, Internet Explorer displays a dialog that says, “Microsoft Internet Explorer’s Enhanced Security Configuration is currently enabled on your server...”.

a. Check In the future, do not show this message. Click OK.Internet Explorer displays a logon dialog.

b. Enter the Honeywell installation account user name and password.Internet Explorer displays a yellow information bar across the top of the Web page stating, “The previous site might require the following ActiveX control: ‘DVSClient.cab’ from ‘Honeywell Limited’...”.

c. Click on the information bar.A menu appears.

d. Select Install the ActiveX control.Internet Explorer shows the Internet Explorer - Security Warning dialog that says, “Do you want to install this software?”.

e. Click Install.Honeywell DVM’s main page appears.

10 The Digital Video Client setup screen appears. Click Next.

11 Select a location for the Client files. Click Next.

12 If you agree with the current setting, click Next to start the installation.The Importing a new private signature key screen appears. By default, the security level is set to Medium.

13 If:

• This security level is correct, click OK and go to step 14.

• You want to change the security level, click Set Security Level. Select the required security level (as described in the following table) and click Next.

Security Level DescriptionMedium Users will be prompted to confirm that the digital

certificate is to be used for signing.All users will have access to the digital certificate for signing.

High Users will be required to enter a password to access the digital certificate when it is to be used for signing.Only users with the password will have access to the digital certificate for signing.



14 Click Finish and then click OK.

15 Click Finish and agree to restart your system if requested, otherwise close and restart Internet Explorer.



240 Release 200

Updating the hosts fileIf you have a workgroup environment, you must update a computer’s hosts file to include an “IP address/computer name” entry for every other Honeywell DVM computer in your system. The following table specifies the names you must include for each type of computer.

The hosts file is in %SystemRoot%\system32\drivers\etc, where %SystemRoot% is normally c:\winnt or c:\windows.

Notes• Use Windows Notepad, or similar text editing tool, to update the hosts file.

• You should ping the other computers to check that your entries are correct. See “Pinging a device on the network” on page 241.

ExampleIf the name of the Database Server is “DVMServer” and its IP address is 192.168.0.1, you would add the following entry:

192.168.0.1 DVMServer

For this type of computer Include the IP address/name of the following:Database Server or Camera Server • Every other Database Server and Camera Server

• Every Honeywell DVM Station and Internet Explorer client computer

• Every EBI or Experion server (if used in conjunction with EBI or Experion)

• Every Console Station (if used in conjunction with Experion)

Client computer (Station or Internet Explorer)

• Every Database Server and Camera Server

EBI or Experion server • Every Database Server and Camera Server

Console Station (only applicable to Experion)

• Every Database Server and Camera Server




Pinging a device on the network“Pinging” is a basic test that checks whether a device—such as a computer or network camera—is connected to the network.

To ping a device:1 Choose Start > Programs > Accessories > Command Prompt to open a

Command Prompt window.

2 At the c:\> prompt, type ping DeviceNamewhere, DeviceName is the name of the device

If the device is connected, the results will be similar to the following:Pinging DeviceName …

Reply from nnn.nnn.nnn.nnn: bytes=32 time<1ms TTL=128

.

.

Ping statistics for nnn.nnn.nnn.nnn:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms



242 Release 200

Installing and configuring camera streamers This section only contains installation and configuration information that is specific to Honeywell DVM. See the manufacturer’s documentation for detailed installation and configuration instructions.

AttentionThe Axis documentation refers to its streamers as “camera servers”. In this, and other Honeywell DVM documents, they are referred to as “camera streamers”.

To install and configure: Go to:Axis 205 page 243

Axis 206/206W page 243

Axis 206M page 243

Axis 207 page 243

Axis 210/210A page 243

Axis 211/211A page 243

Axis 213 page 244

Axis 221 page 243

Axis 231D/232D page 244

Axis 240Q page 250

Axis 241S/241SA page 250

Axis 241Q/241QA page 250

Axis 2100 page 243

Axis 2110 page 243

Axis 2120 page 243

Axis 2130 page 244

Axis 2400 1.x page 245


Axis 2400+ page 245



Axis 2401+ page 245

Axis 2411 page 243

Installing and configuring camera streamers


Axis 205, 206, 206M, 206W, 207, 210/210A, 211/211A, 221, 2100, 2110, 2120, 2411 and 2420

Considerations• Use the Axis-supplied tools to configure the streamer.

• Test the video viewing capability of the streamer using the Axis Web pages before connecting to Honeywell DVM.

• The Axis 205, 206, 206M, 206W, 207, 210/210A, 211/211A, 221, 2100, 2110, 2120 and 2420 are camera streamers with built-in cameras. Hence they can be considered as fixed cameras. There are no Honeywell DVM specific setup tasks required for fixed cameras.

• The Axis 2411 is a camera streamer that does not support PTZ Control. Hence it can be considered to be a fixed camera. There are no Honeywell DVM specific setup instructions required for fixed camera operation.

• Configuring the Axis through the Axis Web pages often requires a user name and password, these are set by Axis and are often root and pass, respectively. To change the user name and password, refer to the Axis documentation for your streamer.

• You must define the streamer’s user name and password in Honeywell DVM. See “Defining the user name and password of an Axis streamer in Honeywell DVM” on page 255.

Axis 2420 page 243

CamStation CS100 page 256

CamStation CS-3001V page 261

MegaChips MD-100 page 267

MegaChips OpennetView page 268

To install and configure: Go to:


244 Release 200

Axis 213, 231D, 232D and 2130



• All these Axis streamers contain a built-in PTZ-capable camera.To enable Honeywell DVM to control this camera, you must define the Camera Control Type as Use streamer settings. This is done when you configure the camera in Honeywell DVM. For more information, see “Camera Control tab” on page 299.

• Configuring the Axis through the Axis Web pages often requires a user name and password, these are set by Axis and are often root and pass, respectively.

• To change the user name and password, refer to the Axis documentation for your streamer.




Axis 2400 1.x, 2400 2.x, 2400+, 2401 1.x, 2401 2.x and 2401+



• There are no Honeywell DVM-specific setup instructions required for fixed camera operation.

• There are no specific baud rates.

• Configuring the Axis through the Axis Web pages often requires a user name and password, these are set by Axis and are often root and pass, respectively. To change the user name and password, refer to the Axis documentation for your streamer.


Configuring a streamer for Pelco P protocol PTZ cameras

To configure a streamer:1 Connect to the streamer directly using Internet Explorer. This causes a series

of Axis pages to be shown.

2 Log on as root with a password of pass (or the new password you entered on page 245).

3 Navigate to the serial port settings page.

4 Change the camera control type to Generic.

5 Change the protocol to RS485.

6 Change the baud rate to 9600 unless otherwise stated in your camera manual.

7 Change the data bits to 8.

8 Change the stop bits to 1.

9 Set the parity to None.

10 Click Save.

11 Set the network protocol to TCP/IP.

12 Set the port to 5001.

13 Click Save and restart the camera streamer.

14 View using a Honeywell DVM client and test.


246 Release 200

After performing the above procedure, you will not be able to control the camera using the Axis Web pages because Axis and Honeywell DVM uses a different mechanism for camera control.

The following figure is a wiring diagram for half-duplex communication between the Axis streamer and the Pelco camera.

Configuring a streamer for Sensomatic PTZ cameras











Figure 5 Pelco Spectra II Dome-Axis Wiring Diagram for Axis 2400 1.x, 2400 2.x, 2400+, 2401 1.x, 2401 2.x and 2401+

7 8

Rx+Tx+Rx-Tx-

Pelco Dome

Axis Streamer

AttentionMake sure that Rx- and Tx- are both connected to pin 7 of the Axis streamer. Rx+ and Tx+ are both connected to pin 8.



10 Click Save.



13 Save the settings and restart the camera streamer.


After performing the above procedure, you will not be able to control the camera using the Axis Web pages because Axis camera control of Sensomatic PTZ cameras is not natively supported by Axis Web pages.

The following figure is a wiring diagram for half-duplex communication between the Axis streamer and the Sensormatic camera.

The Jumper pin (J1) must be set to terminated/unterminated according to the Sensormatic instructions.

If there is only one camera connected on the RS-485, or if the camera is the last one on the daisy chain, it should be terminated.

If there are multiple cameras connected on the RS-422, and it is not the last camera, it should be set to unterminated.

Figure 6 Sensormatic SpeedDome Ultra IV-Axis Wiring Diagram for Axis 2400 1.x, 2400 2.x, 2400+, 2401 1.x, 2401 2.x and 2401+

RS-422

1 2 3 4 5 6Da

ta In

+

Data

In -

Data

Out +

Data

Out -

P7

P3P8

J1

I/O Board

7 8

Axis Streamer


248 Release 200

Configuring a streamer for VCL protocol PTZ cameras







6 Change the baud rate to 9600.




10 Click Save.



13 Save the settings and restart the camera streamer.


Figure 7 VCL Orbiter Gold/Lite-Axis Wiring Diagram for Axis 2400 1.x, 2400 2.x, 2400+, 2401 1.x, 2401 2.x and 2401+

7 8

D+

D-VCL Orbiter Gold/Lite

Axis Streamer

AttentionMake sure that D- is connected to pin 7 of the Axis streamer and D+ is connected to pin 8.



Configuring a streamer for Hernis Industrial camerasSpecific hardware is required to support the interface with Honeywell DVM.

For information and wiring diagrams, please contact your local Honeywell representative.

Configuring a streamer for streamer-based PTZTo configure the streamer to use streamer-based PTZ, go to: http://www.axis.com/techsup/cam_servers/ptz/index.htm. This site contains all the required wiring and configuration information.


250 Release 200

Axis 240Q, 241S, 241SA, 241Q and 241QATo define the name and password of the streamer in Honeywell DVM, see “Defining the user name and password of an Axis streamer in Honeywell DVM” on page 255.


• If you have previously used the camera, log onto the Axis streamer’s configuration Web pages, and delete all the entries from Event Servers and Event Types.



• There are no specific baud rates.

• Configuring the Axis through the Axis Web pages often requires a user name and password, these are set by Axis and are often root and pass, respectively. To change the user name and password of the streamer, refer to the Axis documentation for the streamer.


Configuring a streamer for Pelco P protocol PTZ cameras




3 Navigate to the RS485 port settings page.

4 Change the port usage to Generic TCP/IP.





9 Set the Listener port to 5001.



10 Click Save.

11 Connect via Station and Honeywell DVM and test.

After performing the above procedure, you will not be able to control the camera using the Axis Web pages because Axis and Honeywell DVM use a different mechanism for camera control.

The following figure is a wiring diagram for half-duplex communication between the Axis streamer and the Pelco camera.

Configuring a streamer for Sensomatic PTZ cameras





4 Change the port usage to Generic TCP/IP.




Figure 8 Pelco Spectra II Dome-Axis Wiring Diagram for Axis 241S and 241Q

Rx+Tx+Rx-Tx-

Pelco Dome

11 12

Axis Streamer

AttentionMake sure that Rx+ and Tx+ are both connected to pin 11 and Rx- and Tx- are both connected to pin 12 of the Axis streamer.


252 Release 200



10 Click Save.


After performing the above procedure, you will not be able to control the camera using the Axis Web pages because Axis camera control of Sensomatic PTZ cameras is not natively supported by Axis Web pages.

The following figure is a wiring diagram for half-duplex communication between the Axis streamer and the Sensormatic camera.

The Jumper pin (J1) must be set to terminated or unterminated according to the Sensormatic instructions.

If there is only one camera connected on the RS-485 or if the camera is the last one on the daisy chain, it should be terminated.

If there are multiple cameras connected on the RS-422 and it is not the last camera it should be set to unterminated.

Configuring a streamer for VCL protocol PTZ cameras




Figure 9 Sensormatic SpeedDome Ultra IV-Axis Wiring Diagram for Axis 241S and 241Q

P7

P3P8

J1

I/O Board

11 12

Axis Streamer

RS-422

1 2 3 4 5 6Da

ta In

+

Data

In -

Data

Out +

Data

Out -




4 Change the camera control type to Generic TCP/IP.

5 Change the baud rate to 9600.





10 Click Save.


Configuring a streamer for Hernis Industrial camerasSpecific hardware is required to support the interface with Honeywell DVM.

For information and wiring diagrams, please contact your local Honeywell representative.

Figure 10 VCL Orbiter Gold/Lite-Axis Wiring Diagram for Axis 241S and 241Q

D+

D-VCL Orbiter Gold/Lite

11 12

Axis Streamer

AttentionMake sure that D- is connected to pin 12 of the Axis streamer and D+ is connected to pin 11.


254 Release 200

Configuring a streamer for streamer-based PTZ

To configure a streamer for streamer-based PTZ:1 Connect to the streamer directly using Internet Explorer. This causes a series



3 Navigate to the RS485 port settings page or the RS232 port settings page depending on the type of communications to the camera.

4 Change the port usage to Pan Tilt Zoom.

5 Click on the Upload button to upload a PTZ driver to the streamer. PTZ drivers are available from:http://www.axis.com/techsup/cam_servers/ptz/drivers.php.

6 Click on the Port Options to configure the necessary baud rate, data bits, stop bits and parity to communicate to the camera.



Defining the user name and password of an Axis streamer in Honeywell DVM

You must define the user name and password of Axis streamers in Honeywell DVM.

To define the name and password:1 On the Database Server, choose Start > Programs > Microsoft SQL Server

> Enterprise Manager.

2 In the Console Tree, expand the Microsoft SQL Servers group as follows:Microsoft SQL Servers > SQL Server Group > DatabaseServerName > Databases > DVM > Tableswhere DatabaseServerName is the name of the Database Server

3 Right-click tblCamera and choose Open Table > Return All Rows.

4 In the StreamerUsername field for the camera, enter the name that you entered on the Axis Web page.

5 In the StreamerPassword field for the camera, enter the password that you entered on the Axis Web page.


256 Release 200

CamStation CS100

Prerequisites• Set up the IP address of the CamStation CS100 streamer, using the

CamStation software supplied with the streamer. For more information, see the CamStation User Manual.

Considerations• No Honeywell DVM-specific setup tasks are required on the CamStation

CS100 streamer unless you are using camera control. Defining camera control is done when you add and configure the cameras.For more information, see “Camera Control tab” on page 299.

• You must ensure that the dip switch on the CS100 streamer is set to RS485. This is regardless of whether you are using RS-232 or not. RS-232 is not supported in Honeywell DVM and the streamer must be set to RS485.

• You must ensure that the CS100 streamer is configured for Generic camera control which is explained below. In short, you will need to Telnet to the streamer and use the command Set generic and then select Honeywell camera control.



RS-485 connectionThe following diagram shows the pin-out at the back of the CamStation CS100 streamer.

A RS-485 connector must be used to wire the camera control head to the CamStation CS100 streamer.

The following table identifies where the wires need to be connected.

The jumper setting on the front of the CamStation CS100 streamer must be set to RS485. If it is not set to RS485, change it and power the streamer off and on.

To check if the streamer has been wired correctly, use the CamStation CS100 software to see if the video is streaming and can be viewed. If it is, the wiring is correct.

CamStation CS100 streamer Pelco P camera Sensomatic cameraRX+ TX+ Data Out+

RX- TX- Data Out-

TX+ RX+ Data In+

TX- RX- Data In-

RS-232 10BASE-TALARM I/O

ALarm (Out-) GND GND TX-

ALARM (Out +) Sensor (IN) TBD RX+

RX-

TX+

LAN PortI/O PortDC Input5V

REAR


258 Release 200

Pelco P or Sensormatic PTZ cameras

Considerations• When you configure the Camera Control settings, you must define the

Camera Control Type as either Pelco Dome or Sensormatic.

To configure the streamer for Pelco P or Sensormatic PTZ cameras:1 Choose Start > Run to open the Run dialog box.

2 Type telnet a.b.c.d and click OK, where a.b.c.d is the IP address of the CamStation CS100 streamer.

3 At the login prompt, type CamStation and press ENTER.

4 At the Password prompt, type CamStation and press ENTER.

5 At the CamStation prompt, type set generic and press ENTER.

6 Select the same baud rate setting which is configured on the camera head and press ENTER.

7 Do not change the default printing mode. press ENTER.

8 Select the Honeywell PTZ Control Mode setting and press ENTER.

9 For the Generic PTZ Port Number, type 5001 and press ENTER.

10 When you have finished, type exit to end the Telnet session.

ExampleThis is an example of what the Telnet session could look like.

CamStation> set generic

The command of this field is only for Honeywell company.

Baud Rate Setting

Current Baud Rate : 4800

Choose Baud Rate(1.2400, 2.4800, 3.9600, 4.19200, 5.38400) : 2

Printing Mode Setting.

Current Printing Mode : printing

Choose printing mode(1.printing, 2.no printing):

PTZ Control Mode Setting.

Current PTZ Control: sjcnc ptz

Choose PTZ Control(1.sjcnc ptz, 2.honeywell ptz) : 2

Generic PTZ Port Number[5001] : 5001

CamStation>



Streamer-based PTZ


Camera Control Type as Use streamer settings. This is done when you configure each camera in Honeywell DVM. For more information, see “Camera Control tab” on page 299.

• Step pan, tilt and zoom are the only camera control movements supported by streamer-based control for a CamStation CS100 streamer.

To configure the streamer for streamer-based PTZ:1 Choose Start > Run to open the Run dialog box.

2 Type telnet a.b.c.d and click OK, where a.b.c.d is the IP address of the CamStation CS100 streamer.



5 At the CamStation prompt, type set ptz and press ENTER.A list of cameras will appear, including their current PTZ control settings.

6 To change the PTZ settings, enter the number of the cameras you want to change and press ENTER.

7 Type Y to confirm you want to change the setting and press ENTER.

8 Leave the default PTZ Address number and press ENTER.

9 Repeat steps 7 and 8, until you have changed the setting on all the required cameras.

10 From the list of available camera heads, select the type that the CamStation CS100 will support.


ExampleThis is an example of what the Telnet session could look like

login: camstation

Password: camstation

CamStation> set ptz

[PTZ Control Settings]

Camera 1 PTZ Control : N



260 Release 200



PTZ Controller : Sungjin

Number of Camera to change setting (0-all, 1 - 4) : 0

Camera 1 PTZ Control [N](Y/N) : y

PTZ Address number[1] :







PTZ Controller - [Sungjin]

(1.SUNGJIN, 2.PELCO P, 3.SMARTSCAN, 4.V1311RB_3W, 5.PELCO D) : 5

CamStation>



CamStation CS-3001V

Prerequisites• Set up the IP address of the CamStation streamer, using the CamStation

software supplied with the streamer. For more information, see the CamStation User Manual.

Considerations• Honeywell DVM client computers need to have at least 16MB of video

memory to be able to view video from the CS-3001V streamer. If there is not enough video memory, client computers will display a black image.

• No Honeywell DVM-specific setup tasks are required on the CamStation streamer unless you are using camera control. Defining camera control is done when you add and configure the cameras. For more information, see “Camera Control tab” on page 299.

• An audio source can be connected to the CS-3001V streamer by plugging the audio source into the input audio channel on the rear panel of the streamer. The CS-3001V expects an amplified signal as an input as it does not have an internal pre-amp.

• You must ensure that the dip switch on the CS-3001V streamer is set to RS485. This is regardless of whether you are using RS-232 or not. RS-232 is not supported in Honeywell DVM and the streamer must be set to RS485.

• You must ensure that the CS-3001V streamer is configured for Generic camera control which is explained below. In short, you will need to Telnet to the streamer and use the command Set generic and then select Honeywell camera control.

NetworkThe CS-3001V streamer is a half duplex streamer. Any traffic sent to the streamer can cause network collisions and interrupt the video stream being sent to Honeywell DVM. This can cause a significant degradation in the streamer’s ability to deliver high frame rates to Honeywell DVM. For this reason, care should be taken to minimise traffic to the streamers.

This traffic usually comes from three sources:

• Communications from the Honeywell DVM system. This is required for normal operation and is minimal. The streamer can easily handle this level of return traffic with no loss of performance.

• Broadcast traffic on the LAN.

• Mishandled multicast traffic on the LAN.


262 Release 200

While the streamer can handle the return traffic produced by Honeywell DVM, if there is significant broadcast activity and/or the network is not set up correctly for multicast traffic (multicasts are treated as broadcast), there can be significant loss of performance if this traffic is allowed to reach the network segments containing the streamers.

You can identify an issue with the network if there are a lot of collisions happening on the port CamStation is connected to. This is usually indicated by an orange flashing LED on most network switches.

Possible remedies for this issue are:

• Use managed network switches that can handle multicast and broadcast traffic properly. Note that not all network switches are capable of doing this and generally send all multicast packets to all network ports. This can cause collisions at the port the CamStation is connected to. You will need to ensure that the switch you select stops such packets from going to the port that the CamStation is connected to.

• Use VLANs to segregate the CamStations from the rest of the network. This will minimise the amount of return traffic and stop multicast packets from reaching the CamStation streamers and hence maximise performance.



RS-485 connectionThe following diagram shows the pin-out at the back of the CamStation CS-3001V streamer.

A RS-485 connector must be used to wire the camera control head to the CamStation CS-3001V streamer.

The following table identifies where the wires need to be connected.

The jumper setting on the front of the CamStation CS-3001V streamer must be set to RS485. If it is not set to RS485, change it and power the streamer off and on.

To check if the streamer has been wired correctly, use the CamStation CS-3001V software to see if the video is streaming and can be viewed. If it is, the wiring is correct.

CamStation CS100 streamer PelcoP camera Sensomatic cameraRX+ TX+ Data Out+

RX- TX- Data Out-

TX+ RX+ Data In+

TX- RX- Data In-

RS-232 10BASE-TALARM I/O

ALarm (Out-) GND GND TX-

ALARM (Out +) Sensor (IN) TBD RX+

RX-

TX+

LAN PortI/O PortDC Input5V

REAR


264 Release 200

Pelco P or Sensormatic PTZ cameras


Camera Control Type as either Pelco Dome or Sensormatic.

To configure the streamer for Pelco P or Sensormatic PTZ cameras:1 Choose Start > Run to open the Run dialog box.

2 Type telnet a.b.c.d and click OK, where a.b.c.d is the IP address of the CamStation CS-3001V streamer.



5 At the CamStation prompt, type set generic and press ENTER.

6 Select the same baud rate setting which is configured on the camera head and press ENTER.

7 Do not change the default printing mode. press ENTER.

8 Select the Honeywell PTZ Control Mode setting and press ENTER.

9 For the Generic PTZ Port Number, type 5001 and press ENTER.



CamStation> set generic

The command of this field is only for Honeywell company.

Baud Rate Setting

Current Baud Rate : 4800

Choose Baud Rate(1.2400, 2.4800, 3.9600, 4.19200, 5.38400) : 2

Printing Mode Setting.

Current Printing Mode : printing

Choose printing mode(1.printing, 2.no printing):

PTZ Control Mode Setting.

Current PTZ Control: sjcnc ptz

Choose PTZ Control(1.sjcnc ptz, 2.honeywell ptz) : 2

Generic PTZ Port Number[5001] : 5001

CamStation>



Streamer-based control


Camera Control Type as Use streamer settings. This is done when you configure each camera in Honeywell DVM. For more information, see “Camera Control tab” on page 299.

• Step pan, tilt and zoom are the only camera control movements supported by streamer-based control for a CamStation CS-3001V streamer.

• For information setting up the audio configuration, see “Configuring CamStation CS-3001V for audio” on page 351.

To configure the streamer for streamer-based control:1 Choose Start > Run to open the Run dialog box.

2 Type telnet a.b.c.d and click OK, where a.b.c.d is the IP address of the CamStation CS-3001V streamer.



5 At the CamStation prompt, type set ptz and press ENTER.A list of cameras will appear, including their current PTZ control settings.

6 To change the PTZ settings, enter the number of the cameras you want to change and press ENTER.

7 Type Y to confirm you want to change the setting and press ENTER.

8 Leave the default PTZ Address number and press ENTER.

9 Repeat steps 7 and 8, until you have changed the setting on all the required cameras.

10 From the list of available camera heads, select the type that the CamStation CS-3001V will support.



login: camstation

Password: camstation

CamStation> set ptz

[PTZ Control Settings]


266 Release 200





PTZ Controller : Sungjin

Number of Camera to change setting (0-all, 1 - 4) : 0









PTZ Controller - [Sungjin]

(1.SUNGJIN, 2.PELCO P, 3.SMARTSCAN, 4.V1311RB_3W, 5.PELCO D) : 5

CamStation>



MegaChips MD-100

Considerations• Follow the MegaChips instructions for setting up the MD-100.


Streamer-based PTZ

To configure the streamer for streamer-based PTZ: 1 Start Internet Explorer.

2 Enter the IP address of the OpennetView streamer.

3 Click System Settings > Device Settings and the Enter Network Password dialog box will appear.

4 Enter the User name, the default is administrator, and click OK. (There is no password.)

5 In the Camera Type field, select the required camera and click the Submit button.

Pelco P Protocol PTZ cameras

To configure the streamer for Pelco P Protocol PTZ cameras:1 Start Internet Explorer.


3 Click System Settings > Device Settings and the Enter Network Password dialog box will appear.

4 Enter the User name, the default is administrator, and click OK. (There is no password.)

5 In the Camera Type field, select TYPE B and click the Submit button.


268 Release 200

MegaChips OpennetView

Considerations• Follow the MegaChips instructions for setting up the OpennetView.


Streamer-based control

To configure the streamer for streamer-based control:1 Start Internet Explorer.


3 Click Environment Setup and the Enter Network Password dialog box will appear.

4 Enter the User name, the default is administrator and click OK (there is no password).

5 In the Camera Type field, select the required camera and click the Submit button.

Pelco P Protocol PTZ cameras

To configure the streamer for Pelco P Protocol PTZ cameras:1 Start Internet Explorer.


3 Click Environment Setup and the Enter Network Password dialog box will appear.

4 Enter the User name, the default is administrator and click OK (there is no password).

5 In the Camera Type field, select TYPE B and click the Submit button.

The OpennetView streamer communicates to PTZ cameras via RS-232 while the Pelco uses RS-485. Hence a RS-232 to RS-485 converter is required. The recommended converter is a Black Box IC109A.



The following table shows the pin wiring between the IC109A and the Pelco camera.

IC109A to OpennetView cableIf you experience problems sending PTZ commands, try the following cable solution with a pinout box.

Table 1 IC109A to Pelco Cable Connections

IC109A PelcoTxA Rx-

RxA Tx-

TxB Rx+

RxB Tx+

Figure 11 Cable Solution with Pinout Box

OpennetViewIC109APinoutBox

25-pin

25 to 9-pinConverter

Straight-ThroughCables

PelcoDome

RS-422(4-wire)


270 Release 200

Configuring the IC109AControl of Pelco cameras requires conversion of the OpennetView RS-232 signal to RS-485. You can convert the signals using the IC109A converter from Black Box. The configuration details for the IC109A are as shown in the following tables.

Figure 12 Pinout Box Wiring

(25 Pin) (25 Pin)

Tx 2 2 Tx

Rx 3 3 RxSG 7 7 SG

RTS 4CTS 5

DSR 6CD 8

DTR 20 20 DTR8 CTS6 DSR

5 CTS4 RTS

IC109A OpennetView

Table 2 Switch/Jumper Settings

Switch/Jumper SettingXW1 A position & DCE

S1 Switch Normal position

S2 Switch Off

S3 Switch Off

W5 Jumper BC position (RTS/CTS/CD)

W8 Jumper AB position (4 wire)

W9 Jumper D position (CTS follows RTS)

W15 Jumper AB (RTS/CD enabled)

W16 Jumper A (0 ms)

W17 E (0.15 ms)

Installing and configuring PTZ cameras


Installing and configuring PTZ cameras This section only contains installation and configuration information that is specific to Honeywell DVM. See the manufacturer’s documentation for detailed installation and configuration instructions.

Camera type Go to:Pelco cameras page 272

Sensomatic cameras page 273

VCL Orbiter dome cameras page 274

Honeywell KD6 page 275

Hernis Industrial cameras page 277


272 Release 200

Pelco cameras

Considerations• Some Pelco cameras use DIP switch positions, other than the ones listed

below. If this is the case, configure them to: P type protocol. There are no specific settings for the Address and Baud rate, but the settings must match those selected in the streamer.

The following settings are required for a Pelco camera to communicate with Honeywell DVM.

Switch bank SettingsSW1 1 = Off

2-8 = On (P type protocol)

SW2 1-5 = Off (Address = 1)6 = On7-8 = Off (4800 Baud)



Sensomatic camerasTo enable the Sensomatic camera to communicate with Honeywell DVM, set the address switches on the base of the removable camera unit to 0.


274 Release 200

VCL Orbiter dome cameras

To enable the VCL Orbiter cameras to communicate with Honeywell DVM using the VCL protocol, set the protocol switch settings as follows.

AttentionHoneywell Video Solutions’ Orbiter dome cameras are referred to in this guide as “VCL cameras”, or as “VCL Orbiter cameras”.

Switch FunctionS1 OFF

S2 OFF

S3 OFF

S4 OFF



Honeywell KD6 digital dome camerasHoneywell KD6 digital dome cameras have an inbuilt Axis streamer.

The following instructions complement the instructions in the camera’s user manual.

Setting the hardware addressConfigure switches S1 through S3 to a unique address for your installation. Valid addressing range is 1-989.

Setting the communications protocolSet the camera to communicate via VCL or Pelco protocols by setting the camera according to the following table. (Note that: ON = CLOSED, OFF = OPEN.)

Switch FunctionS1 Ones digit

S2 Tens digit

S3 Hundreds digit

Protocol Switch S4 Communications1 2 3 4 5 6 7 8 Baud Parity Data

BitsStop Bits

VCL ON OFF ON OFF OFF ON OFF OFF 9600 N 8 1

Pelco OFF OFF ON OFF ON OFF OFF OFF 4800 N 8 1


276 Release 200

Setting the IP addressIf your Honeywell KD6 camera has a digital dome, you need to assign an IP address to it. To do this, refer to the camera’s user guide.

To configure for Honeywell DVM:1 When you are installing a digital dome, select the streamer type to match your

camera from the following table.

2 Under camera control, select either VCL or Pelco, to match the protocol you configured on the camera.

Camera Streamer typeKD6i-VIP Axis2401+

HD6i-VIP Axis241S



Hernis Industrial camerasTo enable a Hernis Industrial camera to communicate with Honeywell DVM, you must configure it as a Pelco Dome (Pelco P protocol). When configuring the camera, in the Camera control type list (on the Camera Control tab) select Pelco Dome.


278 Release 200

Upgrade tasksThis section contains upgrade tasks.

AttentionOnly complete a task in this section if you are instructed to do so by an upgrade checklist.

Upgrade tasks


Planning for an upgrade This topic describes planning issues you need to address before you start upgrading Honeywell DVM.

Issue CommentsHardware and software Upgrade your hardware and software as necessary. To

check whether your existing hardware or software needs updating, see “Hardware and software requirements” on page 116.

Steamer firmware Check whether the streamer manufacturers have issued any updates for your streamers. Install updates as necessary. (Contact your local Honeywell representative for details about supported firmware versions.)

readme.txt Read this for any last-minute information that may affect the upgrade. It is on the Honeywell DVM CD.

EBI or Experion If you use Honeywell DVM in conjunction with EBI or Experion, check whether you also need to upgrade it. See “Hardware and software requirements” on page 116.

Changes to the definitions for start and end of recording

Previous releases of Honeywell DVM calculated the Delete after and Archive after durations from the start of a recording. Honeywell DVM now calculates these durations from the end of the recording.Consequently, if you do not adjust the Delete after and Archive after values, the storage requirements will increase by the amount recorded during the length of an average recording.

Changes to the Object Model The following properties are no longer supported. (consequently, you will have to update any scripts/applications that use these properties):• LowDiskSpaceAlarmLimitMB• LowLowDiskSpaceAlarmLimitMB• StartRecordingLimitMB• StopRecordingLimitMB

Custom applications Custom applications built for your existing system that use the Honeywell DVM Object Model must be re-compiled and re-linked using an appropriate development environment.


280 Release 200

Uninstalling your existing Honeywell DVM componentsThis task describes how to uninstall your existing Honeywell DVM components. You must uninstall the existing components before you install the new Honeywell DVM components.

Considerations• Depending on which version of Honeywell DVM you are removing, the

uninstall wizard may indicate the release number (“Rxxx”). For example, if you are removing the client components, you may be prompted to select “Honeywell DVM Rxxx—Client” or “Honeywell DVM Client”.


Removing the Honeywell DVM client from a Camera Server

To remove the Honeywell DVM client:1 Choose Start > Settings > Control Panel.

2 Double-click Add/Remove Programs.

3 Select Honeywell DVM Rxxx—Client and click Change/Remove.

4 Click Yes (or OK) to confirm you want to uninstall that application.

5 Close the Add/Remove Programs dialog box.

6 Restart the computer.

Task Go to: Done?Remove the Honeywell DVM client from the Camera Server(s).

page 280

If you have separate Camera Servers (not combined with a Database Server), remove Honeywell DVM from those Camera Servers.

page 281

Remove the Honeywell DVM client from each client computer (including Station computers if you have EBI or Experion).

page 281

If you have EBI or Experion, remove the Honeywell DVM host components from the EBI or Experion servers.

page 281

Remove Honeywell DVM from the Database Server (or combined Database and Camera Server).

page 282

Upgrade tasks


Removing Honeywell DVM from a Camera Server

To remove Honeywell DVM:1 Choose Start > Settings > Control Panel.


3 Select Honeywell DVM Rxxx and click Change/Remove.

4 Click Yes to continue with the uninstall.

5 Click Yes to confirm you want to uninstall that application.

6 When the uninstall is complete, click Finish.



Removing the Honeywell DVM client from a client computer



3 Select Honeywell DVM Rxxx—Client and click Change/Remove.






Removing the Honeywell DVM host components from the EBI or Experion servers

To remove the Honeywell DVM host components:1 Choose Start > Settings > Control Panel.


3 Select Honeywell DVM Rxxx.

4 Click Change/Remove.



7 When the uninstall is complete, click OK.


282 Release 200



Removing Honeywell DVM from the Database Server (or combined Database and Camera Server)



3 Depending on the release, select:

• Honeywell DVM R150—Primary Video Server and click Change/Remove.

• Honeywell DVM R160.2—Database Server and Camera Server and click Change/Remove.

4 Click OK to continue with the uninstall.A message appears, asking whether you want to back up your existing Honeywell DVM database and Windows account.

5 If you are upgrading or re-installing Honeywell DVM on this computer:

a. Click Yes.

b. Enter the name of the folder where you want to back up the database, and then click Next.

Note that backing up the database takes several minutes.

6 When the uninstall is complete, select Yes, I want to restart and click Finish.


Uninstalling Honeywell DVM R200


Uninstalling Honeywell DVM R200 Prerequisites• The Honeywell DVM client must not be running on any Database Servers,

Camera Servers or any client computers (Stations or Internet Explorer clients).

Considerations• Uninstalling Honeywell DVM from a Camera Server, does not remove the

folders that contain recordings.


Removing the Honeywell DVM client from Database Servers and Camera Servers

To remove Honeywell DVM client:1 Choose Start > Settings > Control Panel.


3 Select Honeywell DVM Client 200.x and click Change/Remove.

4 Click OK to continue with the uninstall.



Task Go to: Done?Remove the Honeywell DVM client from Database Servers and Camera Servers.

page 283

If you have separate Camera Servers (not combined with a Database Server), remove Honeywell DVM from those Camera Servers.

page 284

Remove the Honeywell DVM client from each client computer (including Stations if you have EBI or Experion).

page 284

If you have EBI or Experion, remove the Honeywell DVM host components from the EBI or Experion servers.

page 284

If you have Experion, remove the Honeywell DVM Server host components from each Console Station.

page 285

Remove the Honeywell DVM Database Server (and Camera server, if applicable) from the Database Server (or the combined Database and Camera Server).

page 285


284 Release 200

Removing the Honeywell DVM Camera Server from the Camera Servers



3 Select Honeywell DVM Server 200.x—Camera Server and click Change/Remove.


5 If you are upgrading or re-installing Honeywell DVM, select Yes to keep the DVM Users Group. Otherwise select No.




Removing the Honeywell DVM client from a client computer



3 Select Honeywell DVM Client 200.x and click Change/Remove.






Removing the Honeywell DVM host components from the EBI or Experion server

To remove the host component:1 Choose Start > Settings > Control Panel.


3 Select Honeywell DVM Server 200.x—Host Components.




Uninstalling Honeywell DVM R200





Removing the Honeywell DVM host components from a Console Station

To remove the host components:1 Choose Start > Settings > Control Panel.


3 Select Honeywell DVM Server 200.x—Host Components.







Removing Honeywell DVM from the Database Server (or combined Database and Camera Server)



3 Select Honeywell DVM Server 200.x—Database Server or Honeywell DVM Server 200.x—Database Server and Camera Server and click Change/Remove.

4 Click OK to continue with the uninstall.A message appears, asking whether you want to back up your existing Honeywell DVM database and Windows account.

5 If you are upgrading or re-installing Honeywell DVM on this computer:

a. Click Yes.

b. Enter the name of the folder where you want to back up the database, and then click Next.

Note that backing up the database takes several minutes.


286 Release 200

6 When the uninstall is complete, select Yes, I want to restart and click Finish.



6Configuration

This chapter describes how to configure your Honeywell DVM system.

TasksThe following checklist lists the major configuration tasks for Honeywell DVM.

Perform the mandatory tasks in the specified order. You can perform the optional tasks in any order. (Note that some tasks may not be applicable to your system.)

Task Go to: Done?Mandatory tasksIf you have a domain environment, configure security for Honeywell DVM.

page 289

Give engineers access to Honeywell DVM, so that they can configure the system.

page 394

Configure each camera. page 290

Optional tasksCreate schedules. page 306

Create quad views. (A quad view shows four videos, which switch cameras at regular intervals.)

page 309

Create sequences. (A sequence shows one video, which switches cameras/presets at regular intervals.)

page 311

Configure video analytics (motion detection, and object tracking and classification

page 313

Specify the default folder for snapshots. page 331

Configure the audit log. page 332

Configure disk space administration. page 333

Configure event-activated recording. page 335

Configure multi-monitors. page 338

Configure the digital certificate. page 343

6 – Configuration

288 Release 200

Define special presets (pre-programmed functions specific to each type of camera).

page 346

Configure Axis Streamers for audio. page 348

Configure the Axis 2191 Audio Module. page 349

Configure the CamStation CS-3001V for audio. page 351

Configure Honeywell DVM for video intercom. page 354

Task Go to: Done?

Configuring security for Honeywell DVM in a domain environment


Configuring security for Honeywell DVM in a domain environment

This topic is only applicable if you use domain security.

This topic describes how to create a special domain group for Honeywell DVM users. (Only users who have been added to this group can access Honeywell DVM.)

After configuring security, you can give users access to Honeywell DVM—see “Giving users access to Honeywell DVM” on page 394.

Prerequisites• You must have access rights on the domain controller that allow you to create

user groups.

To configure security:1 Log on to the domain controller with a suitable account.

2 Create a domain user group for Honeywell DVM users. For example, create a group called “DVM Domain Users”.

3 On each Database Server and Camera Server:

a. Log on as a local administrator. (For example, log on using the Honeywell DVM installation account you created before installing Honeywell DVM.)

b. Add the domain user group you created in step 2 to the local group, DVM_Users.

6 – Configuration

290 Release 200

Configuring a cameraConfiguring a camera involves defining how it is set up and how operates within your Honeywell DVM system.

Prerequisites• You must have ENGR or MNGR security level to perform this task.

To add and configure a camera:1 Navigate to the Honeywell DVM pages.

2 In the Navigation Pane, click Camera > New. The Camera display opens at the Camera Definition tab.

3 Fill in the relevant details on this tab and then click New. See “Camera Definition tab” on page 291.The new camera appears under Camera in the Navigation Pane.

4 Configure the other camera properties, as appropriate.

To configure: Go to:Recording page 295

Camera controls (such as presets and tours) page 299

Schedules page 306

Video analytics (motion detection, or object tracking and classification) page 313

Configuring a camera


Camera Definition tabThis tab defines the camera’s main parameters.

Property DescriptionCamera name The camera’s name. The name can contain a maximum

of 16 characters and they must all be alphanumeric.The name appears in the Navigation Pane so that users can easily select the camera. It must be unique.

Camera number The unique number that identifies the camera. By default, Honeywell DVM automatically allocates the next available number.Operators can use the number to quickly view live video from the camera. See “Using the numeric keypad” on page 391.

Camera server The name of the Camera Server on which video for this camera is managed and stored.If you change servers, video stored on the old server is not lost because the Honeywell DVM database stores the location of every piece of captured video.

Location You can make it easier for users to find cameras by defining the same location for related cameras. For example, you may want to group cameras according to “Car park”, “Factory”, “Office” and so on.The camera is listed under its location in the Navigation Pane.

Description A 255-character description of the camera. This appears above all displays relating to the camera.

Hostname or IP address The IP address (or name if you have a Domain Name Server) of the camera streamer sending video from the camera to the Camera Server. See “Installing and configuring camera streamers” on page 242.

Camera streamer type The type of device used to connect the camera to the network.

Compression format The type of compression used in transmitting the video. If your streamer only supports one type, you will not need to make a selection.The supported types are:• Motion JPEG

• MPEG1

• MPEG4

6 – Configuration

292 Release 200

Limit stream by The type of data limiting your streamer allows. If your streamer only supports one type, you will not need to make a selection.The supported types are:• Frame Rates

• Bandwidth

MPEG4 streamers do not support bandwidth streaming.

Stream type Defines whether audio is streamed with your video or not. If your streamer only supports one type, you will not need to make a selection. The options are:• Video Only

• Audio/Video

• Intercom/Video

Frame delivery The transmission technique. The supported types are:• Unicast

• Multicast

See “About multicasting and unicasting” on page 24.

Streamer video input number (Only applicable to Axis 240Q, Axis 241Q, Axis 2400 1.x, Axis 2400 2.x, Axis 2400+ and MD-100)Enter the port number that the video is to be streamed from.

Area The area (if you have EBI) or asset (if you ave Experion) to which the camera belongs. See “Areas (Assets)” on page 93.

Control level The EBI or Experion control level. Used to determine operator security privileges. Determines if a user is allowed to operate the PTZ controls for a camera.See “Security types” on page 95. For general information about areas, see the EBI or Experion documentation.

Camera reservation period When a particular user is controlling a camera, no other user can control that camera until this reservation period has expired. The period can be between 0 and 255 seconds.

Video Clip Directory The folder on the Camera Server where the video clips are stored.Use a UNC path (a UNC path is of the format \\computername\folderpath.Note: This folder must already exist on the Camera Server. Do not terminate the path with a backslash.

Property Description



Video Format The video format, which must match the camera’s format. The supported types are:• PAL

• NTSC

Resolution The resolution of the image that is streamed from the camera streamers. Supported resolutions depend on the streamer selected, for example:For Axis 2401 1.x in NTSC, supports:• Small

• Medium

• Large

For Axis 241S in PAL, supports:• QCIF (192 × 144)

• CIF (384 × 288)

• 4 CIF Expanded (768 × 576)

• 4 CIF Interlaced (768 × 576) The actual pixel resolution is dependent on the streamer and color standard (PAL or NTSC). Refer to the streamer documentation.

Compression ratio The compression ratio affects the size of the digital image files sent by the camera streamer. The higher the compression ratio the smaller the file size—which means that less network bandwidth to transmit images and disk space to store images are required. The trade-off is that higher compression ratios result in lower image quality (as bits of data are lost to make the image smaller). The supported ratios are:• Minimum (not recommended as the image size is

very large therefore requiring greater bandwidth and disk space whilst the image resolution is much the same as Low compression)

• Low (recommended—excellent quality, but images are bigger than Medium)

• Medium (highly recommended—best compromise between image quality and image size)

• High • Maximum (not recommended—the compression

causes the image to lose a lot of detail)

Color (Only applicable to Axis 2100, 2400 1.x and 2401 1.x)Image type: Color or Monochrome.


6 – Configuration

294 Release 200

GOP (Only applicable to some streamers when they are connected using an MPEG compression format) Group of pictures. This is the number of frames between successive I-Frames. For more information, see “About MPEG and Motion JPEG compression types” on page 30.

Frame rate The rate at which video frames are sent by the camera streamer when someone is viewing live video. The supported rates vary, depending on which streamer is chosen.

Smoothness Correction (Only applicable to some streamers when they are connected using an MPEG compression format) The interval between frames sent by some camera streamers is not constant. This can be corrected when live video is displayed by applying smoothness correction. The correction is applied by introducing a small degree of latency between frames so that Honeywell DVM can render each frame at a regular interval. A higher smoothness correction level introduces more latency but results in smoother video.Higher smoothness correction may be inappropriate for PTZ cameras as the latency introduced may affect the responsiveness of the PTZ commands.




Record Settings tabThis tab defines the camera’s recording-related properties for the following types of recording:

• User-activated recording. Recording that occurs when an operator clicks the Record button while viewing live video.

• Background recording. Recording that occurs continuously in the background.

• Event-activated recording. Recording that occurs in response to an alarm or event in EBI or Experion.

For the recording properties related to video analytics, see “Configuring video analytics” on page 313.

Property DescriptionUser ActivatedPre-record for The duration of video that Honeywell DVM keeps in

memory for user-activated recording.When a user activates a recording, Honeywell DVM inserts this pre-record segment at the start of the recording. The pre-record period on the recording allows you to view what was happening immediately before the user-activated the recording. For example if you set this to 10 seconds, the recording shows the 10 seconds of video before the recording was activated by the user.

Record for The duration for which recording takes place after the user action.

Record frame rate The frame rate at which video is recorded for user-activated recordings.If you are using MPEG compression (defined by the Compression format property on the Camera Definition tab), see “Recording frame rates using MPEG” on page 297.

Archive after The period for which user-activated recordings are available for playback before they are automatically archived. If set, this must be less than the Delete after period. The duration commences at the video clip’s end date and time.

Delete after The duration for which user-activated recordings are stored before being automatically deleted. The duration commences at the video clip’s end date and time.

6 – Configuration

296 Release 200

Background RecordingStart background recording Background recording occurs if you select this check

box.

Clip duration The duration of background recording video clips. For practical reasons, background recording is broken into a series of discrete clips of the specified duration. Choose a duration that results in a easily manageable clip size. To calculate clip size, see “Typical storage and bandwidth requirements for video” on page 35.

Record frame rate The frame rate at which video is recorded for background recordings.If you are using MPEG compression (defined by the Compression format property on the Camera Definition tab), see “Recording frame rates using MPEG” on page 297.

Archive each clip after The period for which background recordings are available for playback before they are automatically archived. If set, this must be less than the Delete each clip after period. The duration commences at the clip’s end date and time.

Delete each clip after The duration for which background recordings are stored before being automatically deleted. The duration commences at the clip’s end date and time.

Event ActivatedPre-record for The duration of video that Honeywell DVM keeps

buffered in memory for event-activated recording.When an event activates a recording, Honeywell DVM inserts this pre-record segment at the start of the recording. The pre-record period on the recording allows you to view what was happening immediately before the event activated the recording. For example if you set this to 10 seconds, the recording will show the 10 seconds of video before the recording was activated by the event.

Record frame rate The frame rate at which video is recorded for event-activated recordings.If you are using MPEG compression (defined by the Compression format property on the Camera Definition tab), see “Recording frame rates using MPEG” on page 297.




Recording frame rates using MPEGIf you use MPEG compression and set the Record frame rate property to Full frame-rate, the record frame rate is the same as the live view frame rate (the Frame rate property on the Camera Definition tab).

However, if you set Record frame rate to a value other than Full frame-rate, the record frame rate is defined using the following formula:

LiveViewFrameRate/(AdjustmentFactor x GOP)

where:

• LiveViewFrameRate is camera’s live view frame rate.

• AdjustmentFactor is adjustment factor for the selected record frame rate:

• GOP is the Group of Pictures value used by the camera streamer to which the camera is attached.

Archive events after The period for which event-related recordings are available for playback before they are automatically archived. If set, this must be less than the Delete events after period. The duration commences at the clip’s end date and time.

Archive low alarms afterArchive high alarms afterArchive urgent alarms after

The period for which each level of alarm-related recordings are available for playback before they are automatically archived. If set, this must be less than the corresponding delete alarm after period.

Delete events after The duration for which event-related recordings are stored before being automatically deleted. The duration commences at the clip’s end date and time.

Delete low alarms afterDelete high alarms afterDelete urgent alarms after

The period for which each level of alarm-related recordings are stored before being deleted.


Adjustment factor Record frame rate value1 Every I-Frame

2 Every Second I-Frame

3 Every Third I-Frame

6 – Configuration

298 Release 200

For example, if you set Frame rate to 25 and Record frame rate to Every third I-Frame, and the GOP is 10, the record frame rate would be 0.833, that is: 25/(3*10).

For Axis MPEG4-capable streamers, the GOP is always 8.

For CamStation CS100 and CS-3001V streamers, the GOP varies according to the Frame rate setting, as specified in the following table.

Table 3 Recording frame rates for CamStation CS100 and CS-300V streamers

Frame rate (fps) GOP Recording frame rates for the following settingsFull frame-rate

Every I-Frame

Every Second I-Frame

Every Third I-Frame

PAL video format25 16 25 1.56 0.78 0.52

12.5 8 12.5 1.56 0.78 0.52

6.25 8 6.25 0.78 0.39 0.26

3 4 3 0.75 0.38 0.25

1 4 1 0.25 0.13 0.08

NTSC video format30 16 30 1.88 0.94 0.63

15 8 15 1.88 0.94 0.63

7.5 8 7.5 0.94 0.47 0.31

3.75 4 3.75 0.94 0.47 0.31

1 4 1 0.25 0.13 0.08



Camera Control tabThis tab defines the characteristics of the camera controls.

Considerations• VCL Orbiter Lite is also known as Ademco RapidDome.

• VCL Orbiter Gold is also known as Ademco RapidDome Gold.

• The following table shows the differences between the VCL Orbiter Lite and the VCL Orbiter Gold.

Feature VCL Orbiter Lite VCL Orbiter GoldPresets 64 128

Tours 2 4

Presets per tour 128 128

Privacy zones 1 28

Property DescriptionCamera ControlCamera control type Specifies the type of camera control protocol supported

by this camera. The types are:• Pelco Dome = supports Pelco P protocol • Fixed Camera = no camera control • Sensormatic = supports Sensormatic RS-485

protocol• VCL Orbiter Gold • VCL Orbiter Lite • Use streamer settings (If you select this you

must go to the Web page for your streamer and enter the type of camera. For more information, see the streamer manufacturer’s documentation.)

• Honeywell KD6 (Pelco)

• Honeywell KD6 (VCL)

Enabling camera control causes the PTZ controls to appear on the Live Video tab.

6 – Configuration

300 Release 200

Pan speedTilt speedZoom speedFocus speedIris speed

(Only applicable to the PTZ live video controls and indicators.)These properties only appear if they are appropriate to the selected Camera Control Type.They specify the speed at which a user can change the camera’s movement or focus. The values range between 0 and 100. (The larger the value, the faster the camera movement/focus changes.)You need to optimize these values by testing the camera’s operation.

Continuous Pan/Tilt speed The speed of the mouse and joystick controls. A higher speed results in the mouse or joystick shifting the camera’s pan and tilt faster.

Camera hardware ID (Only applicable to Honeywell KD6 (Pelco) and Honeywell KD6 (VCL), Pelco Dome Camera Control Type, and VCL)Identifies the camera on a multi-dropped cable. This is configured on the PTZ head.

PresetsPresets Lists the presets, special presets and privacy zones

configured for the camera. To configure:• Presets, see “Using presets and tours” on page 369• Special presets, see “Defining special presets” on

page 346

Delete Preset Deletes the selected preset or privacy zone. (To delete a special preset, see “Defining special presets” on page 346.)

Home Preset/Tour (Only applicable if at least one preset has been defined for the camera.)The preset to which the camera returns after control is completed and the length of time specified in Return to home preset has elapsed.The operator can select a VCL tour to be a home preset.If special presets are configured to be used as presets or tours, the operator can select a special preset to be a home preset. For more information on special presets, see, “Defining special presets” on page 346.

Return to home preset The number of seconds the camera waits after its reservation has expired before returning to the home preset or tour. The values range between 0 and 600.




Receive Data Enable (Only applicable to Pelco Dome, Honeywell KD6 (Pelco), Use streamer settings and Sensormatic Camera control type)Select this if you want Honeywell DVM to wait for an ACK before sending the next command.

Flip camera when tilt angle is at 90 degrees

(Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Auto-flip feature. This allows the dome to rotate 180 degrees and reposition itself for continuous viewing of a person who passes directly beneath the dome.

Allow Digital Zoom (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)If you select Allow Digital Zoom, digital zooming is used when an camera reaches its optical zoom range.Note: Loss of picture quality will occur in the digital zoom range.

Reset Camera Deletes the presets, privacy zones and tours from the camera, before re-applying the settings for the camera in Honeywell DVM. This is used to resynchronize the camera’s and Honeywell DVM’s settings.

Enable infrared sensitive mode in low light

(Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Optimizes the image quality for infrared lighting sources.Select this if an infrared light source is used to illuminate the camera’s field of view.

Tours (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)List of configured VCL tours.For more information, see “Configuring tours” on page 304.

New (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Creates a new tour. The default name is VCL_Tourx where x is the number of the tour. For more information, see “Configuring tours” on page 304.


6 – Configuration

302 Release 200

Delete (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Deletes the selected tour.For more information, see “Configuring tours” on page 304.

Preset Name (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Name of the preset.For more information, see “Configuring tours” on page 304.

Speed (1-100) (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)The PTZ speed the camera will move at to reach the next preset.The default is 50. This is a relative value where 1 is the slowest speed and 100 is the fastest speed.For more information, see “Configuring tours” on page 304.

Dwell Time (s) (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)The time in seconds the camera will spend at that preset.The default is 50 and the maximum value is 120. For more information, see “Configuring tours” on page 304.

Insert (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Allows you to add presets to a tour.For more information, see “Configuring tours” on page 304.

Remove (Only applicable to VCL Orbiter Gold and VCL Orbiter Lite Camera control type)Removes the selected preset from the tour.For more information, see “Configuring tours” on page 304.




Configuring privacy zones A privacy zone is a section of live video which is covered with a grey box to prevent operators from viewing that section. You must have a VCL camera to configure privacy zones. (In practical terms, a privacy zone is a specialized preset.)

Only VCL cameras support privacy zones.

Prerequisites• You must have MNGR security level to perform this task.

Considerations• By default, privacy zones are not listed in the presets/tours list

in the live video window.

To configure one or more privacy zones:1 Navigate to the Honeywell DVM pages.

2 In the Navigation Pane, click the camera under Camera.

3 Use the camera’s controls to zoom in to the section you want to define as the privacy zone.

4 Click the list and type an appropriate name.

5 Click .

6 Repeat steps 3 to 5 to create more privacy zones.

7 If you want to make the privacy zone(s) visible to operators:

a. Click the Camera Control tab.

b. In the Presets list, clear the Hidden check box for each privacy zone you want to make visible.

To delete a privacy zone:1 Click the Camera Control tab.

2 Select it in the Presets list and click Delete Preset.

6 – Configuration

304 Release 200

Configuring tours A tour is a predefined sequence of presets stored in a camera. When a tour is activated the camera moves through the presets. Each preset has a dwell time and PTZ speed.


• You must create the presets before you can add them to a tour. See “Using presets and tours” on page 369.

Considerations• Tours are only supported by VCL Camera control type.

• Tours can be specified as the Home position for a camera. This means that a camera can return to a tour after the camera control reservation period and return to home preset period have expired.

• The default name is VCL_Tourx where x is the number of the tour. You can change this to a more appropriate name.

• When you add a preset to a tour, by default the first preset name is added. After it has been added you can change it to the required preset.

• The default PTZ speed is 50.The slowest speed is 1 and the fastest is 100.

• The default dwell time is 50. The maximum dwell time is 120 seconds.

To create a tour:1 Click New.

2 Select the default tour name and enter an appropriate name.

3 Click Insert to add a preset to the tour.

4 To change the preset, select the preset name and the list of preset names will be available. Select the required preset name.

5 To change the speed, select the value and enter the required speed.

6 To change the dwell time, select the value and enter the required dwell time.

7 Repeat steps 3 to 6 until all of the required presets have been added to the tour.

To remove a preset from a tour:1 Select the Preset Name you want to remove.

2 Click Remove.



To delete a tour:1 Select the tour from the Tours list.

2 Click Delete.

6 – Configuration

306 Release 200

Creating a scheduleA schedule defines when recording or video analytics functions are performed for a camera. A recurring schedule is a schedule that occurs at regular intervals.


Considerations• Video Analytics schedules must not overlap.

• If you want to create a recurring schedule with long-duration recordings, you should consider using background recording instead, because background recording requires significantly less management effort. Background recording is configured on the camera’s Record Settings tab.

To create a schedule:1 Navigate to the Honeywell DVM pages.


3 Click the Schedule tab, and then click Create a new schedule.The schedule properties appear.

4 Specify the schedule details as described in the following table.

5 Click OK.

Property DescriptionSchedule DetailsType The type of schedule:

• Recording = records video as specified on this tab.• Video Analytics = controls when video

analytics is enabled for the camera. See “Configuring video analytics” on page 313.

StartEnd

The date/time at which the schedule starts and stops.To specify the times, click each unit (hour and minute) and type the appropriate value.

Notes Any comments about the schedule. (When searching for recordings associated with this schedule, you can enter words and phrases contained in these notes—see “Searching for recorded video” on page 383.)

Creating a schedule


Frame rate (Only applicable to a Recording schedule.)The frame rate at which the video is recorded.

Archive after (Only applicable to Recording schedule.)The period for which scheduled recordings are available for playback before they are automatically archived. If set, this must be less than the Delete After period.

Delete after (Only applicable to Recording schedule.)The time the recording is kept before it is automatically deleted.

Recurrence DetailsRecurring Select No if you only want one recording.

Otherwise, select how often you want the recording to take place:• Daily • Weekly • Monthly

End after (Only applicable if you select a recurrence.)The number of days the before the schedule expires.


6 – Configuration

308 Release 200

Deleting a schedule


To delete a schedule:1 Navigate to the Honeywell DVM pages.


3 Click the Schedule tab.

4 In Schedules on, select the start day for the schedule. The schedules for that day appear in the list.

5 From the list, select the schedule you want to delete. The schedule’s details appear below.

6 Click the Delete button, and click Yes in response to the confirmation prompt.

To delete a recurring schedule:1 Navigate to the Honeywell DVM pages.


3 Click the Schedule tab.

4 In Schedules on, select the start day for the schedule. The schedules for that day appear in the list.

5 From the list, select the schedule you want to delete. The schedule’s details appear below.

6 If you only want to delete the schedule for that day, click Delete.If you want to delete all occurrences of the schedule, click Delete all occurrences. (This button only appears when you select a recurring schedule.)

Creating a quad view


Creating a quad viewA quad view simultaneously shows four live videos. Each quadrant (window) shows the video stream from a single camera or switches between video streams from many cameras at predefined intervals.


Considerations• A quad view can result in a large processing load on the client computer if you

select many cameras that are set to a resolution other than Medium (set on the Camera Definition tab tab). If a video is not set to this resolution, the client computer must convert the video from the specified resolution to Medium so that it can be shown in quad view.

• If you do not need to simultaneously view several video streams, consider creating a sequence (see “Creating a sequence” on page 311).

To create a quad view:1 Navigate to the Honeywell DVM pages.

2 In the Navigation Pane, click Quad Views >New.

3 Specify the following properties.

Property DescriptionName The name of the quad view.

Number The unique number that identifies the quad view. By default, Honeywell DVM automatically allocates the next available number.Operators can use the number to quickly call up the quad view. See “Using the numeric keypad” on page 391.

Area The area to which the quad view belongs. Only operators assigned to this area can see it.Note: All the cameras in the quad view must also be assigned to the operator’s area.

Switch view every The time (in seconds) that a video is shown before switching to the next video.Note: This property only appears if you add more than one camera to a quadrant.

6 – Configuration

310 Release 200

4 Add one or more cameras to each quadrant in the required order:

a. In Available cameras list, select a camera.

b. Click the appropriate Add button to add it to the quadrant list.

5 Click Save.

Creating a sequence


Creating a sequence A sequence shows live video which switches at a specified interval to the next camera/preset in the sequence list.


• Presets have been defined for the cameras if you want to include them in the sequence. See “Using the live video controls and indicators” on page 364.

Considerations• You can include special presets in a sequence—these are shown enclosed

within parentheses, for example: (Setup menu). For more information on special presets, see “Defining special presets” on page 346.

• As an alternative to a sequence, consider creating a quad view (see “Creating a quad view” on page 309).

To create a sequence:1 Navigate to the Honeywell DVM pages.

2 In the Navigation Pane, click Sequences > New. The Sequence display opens at the Definition tab.

3 Specify the following properties.

Property DescriptionName The name of the sequence.

Number The a unique number that identifies the sequence. By default, Honeywell DVM automatically allocates the next available number.Operators can use the number to quickly call up the sequence. See “Using the numeric keypad” on page 391.

Area The area to which the sequence belongs. Only operators assigned to this area can see it.Note: All the cameras in the sequence must also be assigned to the operator’s area.

Switch view every The time (in seconds) that a video is shown before switching to the next video.Note: This property only appears after you add the second camera to the sequence.

6 – Configuration

312 Release 200

4 Add each camera/preset to the sequence in the required order:

a. In Available cameras list, select a camera and click Add to add it to the list on the left.

b. If the camera has a preset, select it from the Preset column.

5 Click Save.

Configuring video analytics


Configuring video analytics Configuring video analytics involves using specialized algorithms to analyze video streams and take appropriate action when pre-determined events are detected.

For an introduction to video analytics and usage guidelines, see “Guidelines for video analytics” on page 123.

To configure: Go to:Motion detection page 314

Object tracking, or object tracking and classification page 322

6 – Configuration

314 Release 200

Configuring motion detection Configuring motion detection involves defining one or more regions of interest—rectangles or polygons in the field of view, and then “tuning” the operation of the motion detection algorithm within those regions.



• A license if you want to use the Premium algorithm. To find out whether your system is licensed to use the Premium algorithm, see “Viewing basic information about your Honeywell DVM system” on page 426.

Considerations• If the streamer supports streamer-based motion detection, use it instead to

reduce the load on the computer. See “Summary of camera streamer capabilities” on page 120.

• To learn about the motion detection symbols (and other video analytics symbols), see “About the video analytics symbols” on page 371.

• Motion detection recording and alarming is disabled while you are configuring motion detection (when you click Start Tuning).

• If you select the Premium algorithm, the algorithm uses the first 20 frames to learn the statistics of the field of view, and the next 60 frames to set up the information that was learned during the first 20 frames. Therefore motion will not be detected in the field of view during the first 80 frames.

Figure 13 A typical scene with two regions of interest (marked by white borders)



To configure motion detection:1 Navigate to the Honeywell DVM pages.


3 Click the Video Analytics tab.

4 Select the Video Analytics enabled check box.

5 Configure the General properties as appropriate. See “General properties” on page 316.

6 Click Start tuning.

7 Define one or more regions of interest. See “Defining regions of interest” on page 315.

8 Configure the algorithm’s Tuning properties as appropriate:

- “Standard (Low CPU) Algorithm Tuning Properties” on page 317

- “Premium (High CPU) Algorithm Tuning Properties” on page 318

- “Streamer-based (No CPU) Algorithm Tuning Properties for Axis Streamers” on page 319

- “Streamer-based (No CPU) Algorithm Tuning Properties for CamStation Streamers” on page 320

9 Check that the algorithm is operating as required. (Tuning the algorithm’s operation is typically an iterative task—you may have to change the values several times before you achieve satisfactory results.)

10 When you are satisfied, click Finish tuning.

11 Configure the When motion is detected properties as appropriate. See “When motion is detected properties” on page 320.

Defining regions of interestNote that there is a default region of interest—you can move and modify it as appropriate.

To define a rectangular region of interest:1 Drag the pointer diagonally over the area you want Honeywell DVM to track

and classify objects. As you drag a box marks the region of interest.

2 In the Region name box, type a suitable name for the region.

To define an irregular region of interest:1 Move the pointer to the location of the first vertex and then click to mark its

location.

2 Move the pointer to the second vertex and click again.

6 – Configuration

316 Release 200

3 Repeat step 2 for each other vertex, except the last vertex.

4 Double-click to mark the last vertex.


To select a region of interest• Click it. (If regions of interest overlap, click the edge of the region of interest

you want to select.)

To modify a region of interest:1 Click the region of interest to select it. Selection handles appear.

2 Drag a selection handle as required. The vertices move as you drag.

To move a region of interest:1 Click the region of interest to select it.

2 Drag it required. (Do not drag it by a selection handle because this will change its shape.)

To delete a region of interest:1 Click the region of interest to select it.

2 Press DELETE.

General properties

TipYou can cancel defining a region of interest at any time by right-clicking, or pressing ESC

Property DescriptionAlgorithm Select either:

• Premium (High CPU)

• Standard (Low CPU)

• Streamer Based (No CPU)

Motion server (Only applicable to server-side algorithms.)Select the Video Analytics Server you want to use to run the algorithm. See “About Video Analytics Servers” on page 128.



Standard (Low CPU) Algorithm Tuning Properties

Detection type Specifies when motion detection occurs:• Continuous = 24 hours a day, 7 days a week.• Scheduled = the time(s) at which motion detection

is enabled is specified in one or more schedules. See “Creating a schedule” on page 306.

Note: Changing from Scheduled to Continuous will delete all video analytics schedules for the camera.The default is Continuous.


Property DescriptionDetection frame rate The frame rate you want the motion detection algorithm

to run at. (An object is considered to be “moving” if it moves inside a region of interest for at least two consecutive frames.)The chance of motion being detected depends on:• The frame rate—a higher frame rate increases the

chance of motion being detected.• The size of the region of interest—the larger the

region of interest, the longer the object takes to move through it.

• The speed of the object—the faster the object moves the shorter the amount of time required to pass through the region of interest.

The default is 3 frames per second.Note: This setting has a high impact on the loading of the server (the higher the frame rate the higher the load on the CPU) and also impacts the bandwidth used by the streamer when motion detection is activated.

Optimize for movement (Applicable to the selected region of interest)Allows you to optimize the algorithm to more successfully detect movement either across or down the field of view.The options are:• In any direction (the default) • Across field of view • To/from camera

6 – Configuration

318 Release 200

Premium (High CPU) Algorithm Tuning Properties

Sensitivity (Applicable to the selected region of interest)Indicates how sensitive the algorithm should be to detecting movement. Values are between 1 and 100 and the higher the value the more sensitive to motion. The default is 40%.Note: If the viewing resolution is changed it will affect this value.


Property DescriptionDetection frame rate The frame rate you want the motion detection algorithm

to run at. (An object is considered to be “moving” if it moves inside a region of interest for at least three consecutive frames.)The chance of motion being detected depends on:• The frame rate—a higher frame rate increases the

chance of motion being detected.• The size of the region of interest—the larger the

region of interest, the longer the object takes to move through it.

• The speed of the object—the faster the object moves the shorter the amount of time required to pass through the region of interest.

The default is 3 frames per second.Note: This setting has a high impact on the loading of the server (the higher the frame rate the higher the load on the CPU) and also impacts the bandwidth used by the streamer when motion detection is activated.

Sensitivity Specify whether the camera is aimed at an Indoor (High) or Outdoor (Low) scene. The default is Indoor (High).



Streamer-based (No CPU) Algorithm Tuning Properties for Axis Streamers

Sub-sampling Reduces the effective resolution of the image used for detecting motion. The greater the level of sub-sampling, the lower the load on the CPU required for motion detection. The values are:• 1 = no sub-sampling (the resolution of the image is

not changed)• 2 = the resolution of the image and the load on the

CPU are halved• 4 = the resolution of the image and the load on the

CPU are quarteredThe default is 2.Note: Reducing the resolution of the image may increase the chance of a false motion detection.

Minimum object size The minimum size of an object for which motion can be detected, expressed in pixels.The minimum size you can specify is limited by the Sub-sampling property, according to the following formula: 4 x (sub-sampling)2. For example, if you set Sub-sampling to 2, the minimum object size you can specify is 16 pixels.The maximum object size is 64 pixels.


Property DescriptionSensitivity (Applicable to the selected region of interest)

Defines how subtle a change of color or variation needs to be before motion is detected.For example, motion is detected for normal colored objects on normal backgrounds when this is set to a higher value. If it is set to a low value, motion will only be detected for very bright objects on a dark background.The values are between 1% and 100%. The default is 85%.

Minimum object size (Applicable to the selected region of interest)Defines how large a moving object must be before motion is detected. The value selected is relative to the size of the area defined in the motion detection window.The values are between 1% and 100%. The default is 10%.

6 – Configuration

320 Release 200

Streamer-based (No CPU) Algorithm Tuning Properties for CamStation Streamers

When motion is detected properties

History (Applicable to the selected region of interest)Defines elapsed time between the current image and the image which it is compared against.If your value is low, the camera will compare the image with the one taken previously. A low level setting will cause the reference image to update frequently. Therefore, any object in the image area will only be active for a short period before being seen as identical to the updated reference image. This setting is useful for when you do not want slight variations in the motion detection area to activate an alarm.If your value is high, the camera will compare the image with one taken over an hour ago. A high level setting means the image is updated very infrequently. Therefore, any significant change in the image initiates an alarm that remains active for a long period of time.The values are between 1% and 100%. The default is 75%.


Property DescriptionSensitivity Defines how sensitive the algorithm is to identifying

motion.The values are between 1% and 100%. The default is 50%.

Property DescriptionGenerate an alarm Sends an alarm to the EBI or Experion server at the

specified Alarm level when motion is detected.Note: The alarm is not latched to a point.



Alarm level Select either:• Urgent • High • Low • Journal (the default)All alarms, except for Journal, appear in Station’s Alarm Summary. Journal alarms do not appear in the Station Alarm Summary, but are written to the event file and appear in the Event Summary.Ensure that all operators who are required to view these alarms have access to the EBI or Experion system area in which the alarms are being raised.

Start a recording Starts a recording when motion is detected. Selecting this allows you to specify Pre-record for, Record frame rate, Record for and Archive after and Delete after properties for video clips created when motion is detected.

Pre-record for The duration of video that Honeywell DVM keeps in memory for motion detection recordings.When motion is detected and a recording is started, Honeywell DVM inserts this pre-record segment at the start of the recording. The pre-record period on the recording allows you to view what was happening immediately before the motion was detected and a recording started. For example if you set this to 10 seconds, the recording will show the 10 seconds of video before the recording was activated.

Record for The length of time (in seconds) recording takes place for, after motion is detected.If you select Until motion finishes, the recording will continue until no motion is detected in the scene for the length of time specified in the Consider motion finished after property.

Record frame rate The frame rate at which video is recorded for motion detection recordings.

Archive after The period for which a motion detection recording is available for playback before being archived. The duration commences at the video clip’s end date and time.


6 – Configuration

322 Release 200

Configuring object tracking and classification Configuring object tracking and classification involves defining one or more regions of interest—rectangles or polygons in the field of view, and then “tuning” the operation of the associated tracking algorithm within those regions.

In addition to defining the region(s) of interest, you must also define:

• The minimum size of the object that is to be tracked

• The condition(s) that an object must meet for each region of interest before Honeywell DVM takes the specified action—such as raising an alarm or starting a recording


Delete after The duration for which motion detection recordings are stored before being automatically deleted. The duration commences at the clip’s end date and time.

Send video to station(s) If selected, video is automatically shown in the specified Station(s) when motion is detected.If a Station has an alarm monitor, the video is displayed on the alarm monitor.

Station number The number of the Station video is sent to if you select the Send video to Station(s) check box.

All stations in area The area containing the Stations video is sent to if you select the Send video to Station(s) check box.

Consider motion finished after The length of time, after motion was last deduced, that motion is considered to have stopped. This property affects the other When motion is detected properties as follows:• A new alarm will not be generated until after this

time has expired.• A new recording will not start until after this time has

expired. Also, if you set the Record for property to Until motion finishes, recording will continue until this time has expired.

• Video will not be resent to a Station until after this time has expired.





• A license for the algorithm. To find out whether your system is licensed to use the algorithm, see “Viewing basic information about your Honeywell DVM system” on page 426.

Considerations• To learn about the object tracking and classification symbols (and other video

analytics symbols), see “About the video analytics symbols” on page 371.

• Video analytic-triggered recording and alarming is disabled while you are configuring object tracking and classification (when you click Start tuning).

Figure 14 A typical scene with two regions of interest (marked by white borders) and the minimum object size rectangle

Figure 15 A typical condition—Honeywell DVM will take the specified action if an object meets this condition

6 – Configuration

324 Release 200

To configure object tracking and classification:1 Navigate to the Honeywell DVM pages.


3 Click the Video Analytics tab.

4 Select the Video Analytics enabled check box.

5 Configure the General properties as appropriate. See “General properties” on page 324.

6 Click Start tuning.

7 Define one or more regions of interest. See “Defining regions of interest” on page 315.

8 Define the minimum size of an object that is to be tracked. See “Defining the minimum object size” on page 326.

9 Configure the algorithm’s Tuning properties. See “Tuning properties” on page 327.For an introduction to the motion detection symbols, see “About the video analytics symbols” on page 371.

10 Define the condition(s) moving objects must meet for each region of interest. See “Defining conditions” on page 327.

11 When you are satisfied, click Finish tuning.

12 Configure the When tracking is detected properties as appropriate. See “When motion is detected properties” on page 320.

General properties

Property DescriptionAlgorithm Select the algorithm:

• Object Tracking—tracks objects• Object Tracking and

Classification—tracks and attempts to classify objects

Motion server (Only applicable to server-side algorithms)Select the Video Analytics Server you want to use to run the algorithm. See “About Video Analytics Servers” on page 128.



Defining regions of interestInitially, there is a default region of interest—you can move and modify it as appropriate.

To define a rectangular region of interest:1 Drag the pointer diagonally over the area you want Honeywell DVM to track

and classify objects. As you drag a box marks the region of interest.


To define an irregular region of interest:1 Move the pointer to the location of the first vertex and then click to mark its

location.

2 Move the pointer to the second vertex and click again.

3 Repeat step 2 for each other vertex, except the last vertex.

4 Double-click to mark the last vertex.


To select a region of interest• Click it. (If regions of interest overlap, click the edge of the region of interest

you want to select.)

Detection type Specifies when object tracking and classification occurs:• Continuous = 24 hours a day, 7 days a week.• Scheduled = the time(s) at which object

tracking is enabled is specified in one or more schedules. See “Creating a schedule” on page 306.

Note: Changing from Scheduled to Continuous will delete all video analytics schedules for the camera.The default is Continuous.


TipYou can cancel defining a region of interest at any time by right-clicking, or pressing ESC.

6 – Configuration

326 Release 200

To modify a region of interest:1 Click the region of interest to select it. Selection handles appear.

2 Drag a selection handle as required. The vertices move as you drag.

To move a region of interest:1 Click the region of interest to select it.

2 Drag it to required position. (Do not drag it by a selection handle because this will change its shape.)

To delete a region of interest:1 Click the region of interest to select it.

2 Press DELETE.

Defining the minimum object sizeThe minimum object size that is tracked by the algorithm is defined by the magenta rectangle. (Note that the position of the rectangle is not relevant.)

To define the minimum object size:1 Select the rectangle. Its selection handles appear.

2 Drag a selection handle until the rectangle is of the required size and shape.



Tuning properties

Defining conditions

To define a condition:1 Select a region of interest by clicking it.

2 Click New.A condition row is added to list.

Property DescriptionDetection frame rate The rate at which you want the algorithm to run. The

default is 5 frames per second.This setting has a high impact on the loading of the server. The higher the frame rate, the higher the load on the CPU. It also impacts the bandwidth used by the streamer when object tracking is activated.The chance of an object being tracked/classified depends on:• The frame rate—a higher frame rate increases the

chance of and object being tracked/classified• The size of the region of interest—the larger the

region of interest the longer the object takes to move through it.

• The speed of the object—the faster the object moves the shorter the amount of time it will take to pass through the region of interest.

Sensitivity Indicates whether the scene is indoor or outdoor.

Shadow correction If there are many shadows in the scene, turn shadow correction on to reduce the risk false detections.

Processing type Indicates whether the algorithm analyzes the entire image (Full Frame) or only the regions of interest drawn (ROI Only).Full Frame processing provides more accurate results—especially for small regions of interest—because the algorithm has more time (more frames) to analyze objects. However, it does increase the load on the CPU.Note: Even if you select Full Frame, the conditions (and associated responses, such as raising alarms) only apply when the object enters a region of interest.

6 – Configuration

328 Release 200

3 Define the condition by selecting appropriate values for the three condition properties: Object type, Behavior and Direction. (As you select a value for each property, the condition in the list is updated.)

4 Configure the remaining properties in the following table to define what happens when a object satisfies the condition.

Property DescriptionCondition propertiesObject type The type of object you want the algorithm to detect.

Valid types are:• person

• vehicle

• other Object

• any Object

When any Object is selected, it detects any moving object greater than the minimum object size.Note: You cannot select Object type when using the object tracking algorithm. It is available only when using the object tracking and classification algorithm.

Behavior The object’s behavior that triggers the event. Valid behaviors are:• enter—enters the region• exit—exits the region• start—starts moving within the region• stop—stops moving within the region• any behavior—matches any behaviorstart and stop are only applicable if the Processing type property is set to Full Frame.

Direction The direction in which the object must move in order to trigger the event (the exact wording depends on whether you set Behavior to enter or exit):• to/from the Right

• to/from the Left

• to/from the Bottom

• to/from the Top

• any Direction—detects movement from any direction

Note: Direction is with respect to the field of view—not the ROI, which may have an irregular shape.

These properties define what happens when an object satisfies the selected condition



Generate an alarm Sends an alarm to the EBI or Experion server at the specified Alarm level when an object satisfies the condition.Note: The alarm is not latched to a point.

Alarm level The level of the alarms that are generated:• Urgent • High • Low • Journal (the default)All alarms, except for Journal, appear in Station’s Alarm Summary. Journal alarms do not appear in the Station Alarm Summary, but are written to the event file and appear in the Event Summary.Ensure that all operators who are required to view these alarms have access to the EBI or Experion system area in which the alarms are being raised.

Start a recording Selecting this allows you to specify Pre-record for, Record frame rate, Record for and Archive after and Delete after properties for video clips created when an object satisfies the condition.

Pre-record for The duration of video that Honeywell DVM keeps in memory for motion detection recordings.When motion is detected and a recording is started, Honeywell DVM inserts this pre-record segment at the start of the recording. The pre-record period on the recording allows you to view what was happening immediately before the motion was detected and a recording started. For example if you set this to 10 seconds, the recording will show the 10 seconds of video before the recording was activated.

Record for The length of time (in seconds) recording takes place for, after motion is detected.If you select Until motion finishes, the recording will continue until no motion is detected in the scene for the length of time specified in the Consider motion finished after property.

Record frame rate The frame rate at which video is recorded for motion detection recordings.


6 – Configuration

330 Release 200

Archive after The period for which a motion detection recording is available for playback before being archived. The duration commences at the video clip’s end date and time.

Delete after The duration for which motion detection recordings are stored before being automatically deleted. The duration commences at the video clip’s end date and time.

Send video to station(s) If selected, video is automatically shown in the specified Station(s) when an object satisfies the condition.If a Station has an alarm monitor, the video is displayed on the alarm monitor.

Station number The number of the Station video is sent to if you select the Send video to Station(s) check box.

All stations in area The area containing the Stations video is sent to if you select the Send video to Station(s) check box.

Do not raise repetitive events for the same object for

The length of time, after the object has moved outside the region of interest, that new alarms, recordings and video streams to Station are inhibited. This property affects the other properties in this table as follows:• A new alarm will not be generated until after this

time has expired.• A new recording will not start until after this time

has expired. Also, if you set the Record for property to While object in the region, recording will continue until this time has expired.

• Video will not be resent to a Station until after this time has expired.


Specifying the folder for snapshots


Specifying the folder for snapshotsA snapshot is a single video frame that is captured and stored in the snapshot folder on the computer on which the snapshot was taken.

The default folder is: \Program Files\Honeywell\EBI or Experion\Client\DigitalVideoClient\snapshot. However, if you want to save snapshots to another folder, you need to specify it in the Windows Registry.

To specify the folder for snapshots:1 Choose Start > Run.

2 Type regedit and click OK.This starts the Registry Editor.

3 Locate the entry:HKEY_Local_Machine\Software\Honeywell\DVM\Client

4 Choose Edit > New > String Value.

5 Type Snapshotfilepath.

6 Select Snapshotfilepath and choose Edit > Modify.

7 In the Value Data box enter the name of the folder.

8 Click OK.

6 – Configuration

332 Release 200

Configuring the audit log Honeywell DVM uses the audit log to provide an audit trail of all user actions and system events. The audit log is stored in the Honeywell DVM database.

You cannot configure which types of events are recorded in the audit log; however, you can configure length of time events are kept.

The size of the audit log depends on how often events are generated and the length of time they are kept. To avoid using unnecessary disk space, you should only keep events for as long as is necessary. A recommended setting is between a week and a month.

Prerequisites• You must have ENGR or MNGR level access to perform this task.

To configure the audit log: 1 Navigate to the Honeywell DVM pages.

2 In the Navigation Pane, click Administration.

3 Select the Audit Log tab.

4 In the Audit Log tab, enter the length of time audit events are kept.

This value is checked at approximately midnight, and any audit events that are older than the specified period are deleted.

Configuring disk space administration


Configuring disk space administration Disk space administration controls system policies when disk space runs low. Honeywell DVM can raise host alarms, automatically begin deleting video clips, or even stop recording onto a disk when free space drops below the configured minimum levels.

Video clips can be automatically deleted before their configured deletion dates in order to reclaim free space for new recordings. The clips closest to their deletion dates are selected for automatic deletion. Clips marked “Keep Forever” are never deleted.

Automatic clip deletion provides the administrator with an effective means of managing available space. Ideally, having configured the system correctly, space should never be unavailable.

Prerequisites• You must have ENGR or MNGR level access to perform this task.

Considerations• Even after you have configured disk space administration, the disk can still

run out of space if:

- The rate at which recordings are being made is greater than the rate at which old recordings are being deleted

- No clips suitable for automatic deletion can be found on the disk

• If you configure the deletion threshold at a value larger than the volume of the disk, Honeywell DVM disables automatic clip deletion for that disk. A host alarm is raised to notify the operator that automatic clip deletion is disabled for the drive.

• When Honeywell DVM determines that there is a need for automatic clip deletion on a disk, it raises a host alarm. Host alarms are raised each time Honeywell DVM begins automatic clip deletion. Alarms are then raised every ten minutes until the available disk space exceeds the configured automatic clip deletion value. This may mean that alarms are raised more frequently if the amount of free disk space oscillates around the automatic clip deletion value.

To configure disk space administration:1 Navigate to the Honeywell DVM pages.


3 Click the Disk Space tab.

6 – Configuration

334 Release 200

4 In the Camera server box, select the Camera Server whose disk space you want to configure.

5 In the Disk box, select the disk whose space you want to configure.

6 Configure the properties as appropriate.

Property DescriptionRaise a low disk space alarm when free disk space reaches

Honeywell DVM raises a low disk space host alarm if the free disk space falls below this value (MB).Minimum value is 1000.

Automatically delete clips when free disk space reaches

If selected, Honeywell DVM automatically deletes video clips when the free space on the disk falls below this value (MB).Minimum value is 1000. This value must be less than the low disk space alarm value.

Allow deletion of clips marked for archiving

If selected, Honeywell DVM deletes video clips that are marked for archiving, even if they have not been archived.

Raise a very low disk space alarm when free disk space reaches

Honeywell DVM raises a very low disk space alarm if the free disk space falls below this value (MB).Note: If this type of alarm is raised, the system administrator must manually intervene to prevent Honeywell DVM from suspending recording due to lack of free disk space.Minimum value is 1000. This value must be less than the automatic clip deletion alarm value.

Start recording again when free disk space reaches

The minimum free disk space required before Honeywell DVM will resume recording after having stopped recording due to insufficient free space.Minimum value is 1000. This value must be less or equal to the value for very low disk space alarm.

Stop recording when free disk space reaches

Honeywell DVM will stop recording if the minimum free space falls below this value.Minimum value is 1000. This value must be less than the start recording again value.

Disk Usage These are read-only properties for the selected Camera Server. For details about these properties, see “Viewing the disk usage details of a Camera Server” on page 422.

Configuring event-activated recording


Configuring event-activated recordingEvent-activated recording is the technique of starting a recording when an associated EBI or Experion point changes to a specific state—typically, when a point goes into an alarm state.

You configure event-activated recording when configuring the point in Quick Builder. (Quick Builder is the main configuration tool supplied with EBI or Experion.)

The following procedure only describes the steps specific to configuring event-activated recording. For detailed information on configuring points and using Quick Builder, see Quick Builder’s help.

Considerations• Do not use a special preset with event-activated recording unless you know

that it is suitable. (Most special presets are not suited for use with event activation.)

To configure a point in Quick Builder:1 Add the point to a Quick Builder project in the normal manner.

2 Click the Main tab.

3 In the Action Algo box, select:

• Algo 71 - Access Point Task Request if this is an access point (only applicable to EBI)

• Algo 71 - Queued Task Request if this is a status point and you have Experion

• Algo 92 - Queued Task Request if this is a status point and you have EBI

4 Click the Action Algo tab.

AttentionIn order for event-activated recording to work, you must ensure that the following are also assigned to the same area as the point:• The camera used for event-activated recording• The Station(s) and Internet Explorer client(s) used to view the recorded video• The operator(s) that need to view the recorded video

6 – Configuration

336 Release 200

5 Configure the algorithm’s properties as appropriate. See:

• “Algorithm properties for an access point” on page 336

• “Algorithm properties for a status point” on page 336

6 Configure the point’s other properties in the normal manner.

7 Save and download the project in the normal manner.

Algorithm properties for an access point

Algorithm properties for a status point

Property DescriptionLRN of requested task Set to 181.

States to request task Select the states that cause event-activated recording, for example “Denied: expired card”.

Parameter BlockWord 1 The camera number, as specified in the Camera

number property on the Camera Definition tab.

Word 2 This number represents a set of control flags that specify what action(s) to perform when an event occurs. See “Word 2 control flags” on page 337.

Word 3 The Station or area ID.

Word 4 Preset number.

Word 5 Pre-record period in seconds.Note that the Event Activated Pre-record for property on the Record Settings tab defines the upper limit. For example, if you set Word 5 to 30 s, but and Event Activated Pre-record for is set to 10 s, only 10 s of pre-record will be collected.

Word 6 Post-record period in seconds.If you set both Word 5 and Word 6 to zero, the recording is a snapshot (single frame).

Property DescriptionLRN of requested task Set to 181.

States to request task Select the states that cause event-activated recording.

Parameter BlockWord 1 The camera number, as specified in the Camera

number property on the Camera Definition tab.

Configuring event-activated recording


Word 2 control flagsThe Word 2 control flags specify what action is performed when an event occurs. (A number is used to represent the control flags. For example the decimal value “3” means that bits 0 and 1 are set and bit 2 is unset.)

ExampleIf you set Word 2 to 3 (decimal), bits 0 and 1 are set, and bit 2 is unset. This causes recording to occur and a display change for the Station specified in the param block to the specified camera.

Word 2 This number represents a set of control flags that specify what action(s) to perform when an event occurs. See “Word 2 control flags” on page 337.

Word 3 to Word 5 (Internal use only)

Word 6 Station or area ID.

Word 7 Pre-record period in seconds.

Word 8 Post-record period in seconds.If you set both Word 7 and Word 8 to zero, the recording is a snapshot (single frame).

Word 9 Preset number.

Word 10 Not used.


Control flag ActionBit 0 (least significant bit) Start a recording. 1 = record.

Bit 1 Change display. 1 = change display.If you set this bit and an alarm monitor is configured for the Station specified in Word 3 (access points) or Word 6 (status points), the camera is displayed on the alarm monitor. If a queue of alarm monitors is configured for the Station, the camera is displayed at an appropriate position within the queue of monitors according to alarm priority and time of activation. (For more information see “Configuring multi-monitors” on page 338.)

Bit 2 Display change option:0 = change display on a Station1 = change display on all Stations in an areaBit 2 is ignored if Bit 1 is not set.

6 – Configuration

338 Release 200

Configuring multi-monitorsHoneywell DVM’s multi-monitor capabilities allows an operator to use a single keyboard to control the viewing of cameras on multiple monitors. It allows a Station to be set up to mimic a traditional CCTV workstation. Typically a multi-monitor operator Station will consist of one or more monitors driven by one or more computers installed with the Honeywell DVM client components. A computer may support multiple monitors depending on the graphics card installed.

Monitors can be:

• Surveillance monitors—the camera displayed on the monitors is controlled by the operator.

• Alarm monitors—the camera displayed on the monitors is controlled by the event-activation task or video motion detection. (For more information see “Configuring event-activated recording” on page 335.)

Following are some examples of typical multi-monitor scenarios and configuration:

• Bank of surveillance monitors—an operator has a bank of monitors, each configured as a surveillance monitor. From the single operator keyboard, the operator is able to “throw” a camera onto any of the monitors.

• Single alarm monitor—a single monitor is configured as an alarm monitor. When event-activation or video analytic detection occurs in EBI or Experion, the camera associated with the event-activation or video motion detection is displayed on the monitor. Camera views cycle when more than one activated camera view is sent to the alarm monitor. The operator is able to clear camera views from the alarm monitor using the operator keyboard.

• Queue of alarm monitors—a queue of monitors are configured as alarm monitors. When event-activation or video motion detection occurs in EBI or Experion, the camera associated with the event-activation or video analytics is placed at an appropriate position within the queue of monitors according to alarm priority and time of activation. All existing camera views are shifted to accommodate the new camera view. The monitor at the end of the queue cycles when there are more activated camera views than there are configured monitors. The operator is able to clear camera views from any monitor in the alarm queue using the operator keyboard.

For more information on carrying out multi monitor tasks using the operator keyboard see “Using the numeric keypad” on page 391.

Configuring multi-monitors


Prerequisites• A static Station (Rotary Stations are not suitable because their Station number

changes at each connection.)

• Each computer that hosts a multi-monitor must have the Honeywell DVM client components installed.

• Each computer hosting a multi-monitor must be able to ping the Database and Camera Servers using their computer names.

6 – Configuration

340 Release 200

Configuring the monitors You configure monitors in the SQL server table, tblMultiMonitor.

Prerequisites• You must have Windows administrator privileges to perform this task. (For

example, use the Database Server’s default Administrator account, or the Honeywell DVM installation account.)

Considerations• The live video will expand to fill the entire viewing area of the physical

monitor.

To define the placement and assignment of monitors:1 Log on to the Database Sever.

2 Choose Start > Programs > Microsoft SQL Server > Enterprise Manager.


4 Right-click tblMultiMonitor and choose Open Table > Return All Rows.

5 In the tblMonitor window, configure the fields as described in the following table.

6 Close the tblMultiMonitor window.

Field DescriptionStationNumber The Station number assigned to the Station in EBI or

Experion.

MachineName The name of the computer the monitor is physically connected to.

WindowNumber The Windows monitor number as defined in Windows Control Panel > Display > Settings.

Configuring multi-monitors


ExampleThe following entries assign surveillance monitors to two physical monitors on Machine1 when accessed from EBI or Experion Station number 1. The single monitor on Machine2 is assigned CallupID 3 as both a survelliance monitor and an alarm monitor when accessed from Station number 1.

CallupID A number that identifies the monitor. It must be unique for each monitor that is assigned to the same Station. The number starts at 1.Use of CallupID is different for each monitor type:• Surveillance Monitors—the CallupID identifies the

monitor.For example, the keyboard command “+5<Enter>” on Station number 2 shows the currently viewed camera on Station number 2 onto the monitor identified in tblMultiMonitor where StationNumber=2 and CallupID=5. For more information, see “Using the numeric keypad” on page 391.

• Alarm Monitors—requires that event-activation or video motion detection is configured to change display on that Station in the event of an alarm. The incremental sequencing of CallupIDs form a queue of alarm monitors. Newly activated alarm views are placed at an appropriate position within the alarm queue. All existing alarm views are shifted in the queue to accommodate the new view.

Surveillance Determines whether the monitor is used as a surveillance monitor:0 = No1 = Yes

Alarm Determines whether a monitor is used as an alarm monitor:0 = No1 = Yes

rowguid For system use only.

Field Description

StationNumber MachineName WindowNumber CallupID Surveillance Alarm1 Machine1 1 1 1 0

1 Machine1 2 2 1 0

1 Machine2 1 3 1 1

6 – Configuration

342 Release 200

Configuring alarm monitor cycle time If there are more activated camera views in a queue than there are monitors to display them, the last monitor cycles the surplus camera views. By default, the cycle time is set to ten seconds.

You configure the cycle time in the SQL server table, tblConfiguration.


example, use the Database Server’s default Administrator account, or the Honeywell DVM installation account.)

To configure alarm monitor cycle time:1 Log on to the Database Sever.



4 Right-click tblConfiguration and choose Open Table > Return All Rows.

5 In the tblConfiguration window, complete the fields as follows:

In this field EnterAlarmMonitorCycleTime Time in seconds that each camera view is displayed in

a cycling monitor.

Configuring a digital certificate


Configuring a digital certificate You only need to perform these tasks if you want to use a digital certificate other than the default digital certificate supplied with Honeywell DVM. (For an introduction to digital certificates, see “Digital signatures” on page 107.)

You can obtain a digital certificate from a third party such as VeriSign, or generate one using the certificate authority component in Windows 2000 Server or Windows 2003 Server. (To find out how to create a digital certificate using Windows 2000 Server or Windows 2003 Server, contact your local Honeywell representative.)

Considerations• You must configure the digital certificate on each computer that is used to

export signed videos and audit logs.

Tasks

Installing the digital certificate

Prerequisites• You must log on using the Windows account that will be used to export (sign)

files.

• Your private key.

Considerations• The certificate must be installed in the certificate store.

• The procedure for installing the digital certificate will vary depending on the format the certificate file is delivered in. Contact your local Honeywell DVM representative if the following procedure does not apply to you.

Task Go to: Done?Install the digital certificate. page 343

Check that the digital certificate is installed correctly. page 344

Configure Honeywell DVM to use the digital certificate. page 345

6 – Configuration

344 Release 200

• If the Enable strong private key protection option is selected the user is required to confirm (medium security) or enter a password (high security) before each signing can proceed.

• If the Mark this key as exportable option is selected, the certificate’s private key can be extracted from the computer. It is recommended that this is not selected.

To install the digital certificate:1 Log on using the account that will be used to export files.

2 Open Windows Explorer and double-click the certificate file to start the wizard which will guide you through the installation.

3 Select or clear the Enable strong private key protection check box.

4 Select or clear the Mark this key as exportable check box.

Checking that the digital certificate has been installed correctly

To confirm that the digital certificate has been installed correctly:1 Choose Start > Run to open the Run dialog box.

2 Type mmc.exe and click OK.

3 Choose Console > Add/Remove Snap-in. When the Add/remove Snap-in dialog box appears, click Add.

4 Select Certificates from the list of available snap-ins and click Add.

5 Select My user account and click Finish.

6 Click Close to close the Add Standalone Snap-in dialog box.

7 Click OK to close the Add/Remove Snap-in dialog box.

8 In the MMC console, under Console Root, choose Certificates - Current User > Personal > Certificates.The certificate you installed should be listed in the right pane.

9 Double-click the certificate to view its details.On the General tab the words You have a private key that corresponds to this certificate should appear.

10 On the Details tab, write down the thumbprint of the certificate. You need this when you configure Honeywell DVM to use this digital certificate.

Configuring a digital certificate


Configuring Honeywell DVM to use the digital certificate


example, use the computer’s default Administrator account, or the Honeywell DVM installation account.)

• The thumbprint for your digital certificate (This is 40 characters long and can be entered as 20 groups of 2 characters, separated by spaces or 10 groups of 4 characters separated by spaces.)

To configure Honeywell DVM to use the digital certificate:1 Log on to the Database Sever.



4 Right-click tblConfiguration and choose Open Table > Return All Rows.

5 In the tblConfiguration window, in the ClientCertificateID box enter the thumbprint.

6 Close the tblConfiguration window and close Microsoft SQL Server.

6 – Configuration

346 Release 200

Defining special presetsA special preset is a pre-programmed function that is specific to each type of camera. Special presets are usually reserved for programming, setup and special control functions.

If the special presets for your cameras are not pre-defined in Honeywell DVM, you need to define them. (Currently, special presets are only defined for Honeywell KD6 cameras.)

Requirements• You must have Windows administrator privileges to perform this task. (For

example, use the computer’s default Administrator account, or the Honeywell DVM installation account.)

• The documentation from the camera manufacturer, which specifies the details about each pre-programmed function.

Considerations• If you have Honeywell KD6 cameras, you may want to change the default

operator-related settings—for example, hide some special presets from operators.

• If you do not hide a special preset from operators, it is shown enclosed within parentheses to distinguish it from normal presets, for example: (Setup menu).

To define or modify special presets:1 Log on to the Database Sever.



4 Right-click tblCameraTypeSpecialPreset and choose Open Table > Return All Rows.

5 If you are defining a new special preset, enter the details in the first blank row. (The row with the button.)

Defining special presets


Property DescriptionCameraTypeID Honeywell DVM’s identification for the type of

camera being addressed, as listed in the CameraTypeID field of the tblCameraTypes table.

PresetNumber The camera’s preset number, as defined in the documentation from the camera manufacturer.

PresetName The name that is shown to the operators. Do not include parentheses or square brackets.You can include international characters, but special presets do not support language toggling.

SecurityLevel The minimum security level required by an operator to access the special preset:• 0 = LVL1• 1 = LVL2• 2 = OPER• 3 = SUPV• 4 = ENGR• 5 = MNGRFor more information about security, see “Giving a user access: operator-based security with integrated accounts in a workgroup environment” on page 400.

Hidden Whether or not the special preset is hidden from operators.

CanActLike The special preset can act like:• 0 = A special preset. You can call this from within

Honeywell DVM, but it cannot be used as part of a tour, sequence, intercom or home preset.

• 1 = A real preset. Select this if you want to set up a sequence, home preset or a preset for intercom.

• 2 = A tour. Select this if it is the home preset on the camera control display.

rowguid For system use only.

6 – Configuration

348 Release 200

Configuring Axis Streamers for audio When audio is enabled, audio is heard when the live video from the camera is displayed. It is recorded along with video for user and event recordings. If required, audio can also be recorded with scheduled and background recordings.

To find out which Axis streamers support audio, and whether a separate audio module is required, see “Summary of camera streamer capabilities” on page 120.

Note that each type of Axis streamer is configured in its own way. For details, see the associated Axis documentation.

To configure the associated cameras to receive audio, see “Configuring a camera to receive audio” on page 353.

Configuring the Axis 2191 Audio Module


Configuring the Axis 2191 Audio Module To configure a camera with audio in Honeywell DVM, the streamer must be configured for audio operation and Honeywell DVM must be configured to receive audio from the streamer.

Configuring the streamer for audio

To change the streamer for audio:1 Configure the streamer's serial port for the Axis 2191. The exact steps

required to do this are streamer specific. Please refer to your streamer documentation.

2 Connect the Axis 2191 to the streamer. For detailed instructions see the Axis 2191 User Guide.

3 Connect the audio source to the Axis 2191.Make sure the dip switch on the rear panel is set to “int” (to use the built-in microphone) or “ext” (to use the line input).

4 Connect power to the Axis 2191.

5 Configure the associated cameras to receive audio, see “Configuring a camera to receive audio” on page 353.

Fine tuning audioTo compensate for differing input signal levels, the Axis 2191 has a level adjustment trimpot.

• To compensate for a low level signal, turn clockwise (more gain), for stronger signals turn anti-clockwise (less gain).

• Adjust the trimpot so that the “Level In” LED shows yellow occasionally but not red. Red indicates that the input is overloaded and the audio is clipped. Adjust the input levels using the audio environment that the device is exposed to under normal use.

• Adjust the output level of the Honeywell DVM client computer’s sound card using the Microsoft Windows volume control so that the sound is clear and at the desired level.

6 – Configuration

350 Release 200

Audio operationWhen audio is enabled, audio is heard when the live video from the camera is displayed. It is recorded along with video for user and event recordings. If required, audio can also be recorded with scheduled and background recordings.

When live or recorded video from a camera with audio enabled is displayed in the video player, an audio icon is shown on the video player.

To adjust the volume of the audio:1 Click on the audio icon.

2 Adjust the volume control slider that appears by clicking on it and moving the mouse either up or down.Clicking off the slider will cause it to disappear again.If there is a problem obtaining the audio stream from the streamer, the audio icon will show a failed indication. For more information, see “Using the live video controls and indicators” on page 364.

To save on disk space, it is possible to disable the recording of audio on a scheduled recording. To do this, clear the Audio Enabled check box when creating the schedule, or clear the check box on the Schedules tab for an existing schedule.

Configuring CamStation CS-3001V for audio


Configuring CamStation CS-3001V for audio Prerequisites• You configured a Camstation CS-3001V streamer (see “CamStation

CS-3001V” on page 261.)

Hardware configurationThe CS-3001V streamer has an audio input port where an audio source may be connected. The streamer does not have an audio pre-amp and hence expects an amplified signal as input. Please ensure that this is the case. It is recommended that when installing the streamer, you test the audio signal with a portable audio device where the audio signal is known to be amplified.

To configure the associated cameras to receive audio, see “Configuring a camera to receive audio” on page 353.

Audio operationThe CS-3001V audio operates in a similar way to the Axis 2191 audio. When audio is enabled, it is heard when the live video from the camera is displayed. It is recorded along with video for user and event recordings. If required, audio can also be recorded with scheduled and background recordings.

When live or recorded video from an audio-enabled camera is displayed, an audio icon is shown on the video player.

Considerations• If a recording is performed using a low frame rate or an I-frame rate and audio

is enabled, the whole audio stream is recorded. If you are doing an I-frame recording, audio can comprise a large portion of the video clip.

To adjust the volume of the audio:1 Click on the audio icon.

2 Adjust the volume control slider that appears by clicking on it and moving the mouse either up or down.Clicking off the slider will cause it to disappear again.If there is a problem obtaining the audio stream from the streamer, the audio icon will show a failed indication. For more information, see “Using the live video controls and indicators” on page 364.

6 – Configuration

352 Release 200

To save on disk space, it is possible to disable the recording of audio on a scheduled recording. To do this, clear the Audio Enabled check box on the Schedule details display when creating or editing a schedule.

Configuring a camera to receive audio


Configuring a camera to receive audio To configure a camera to receive audio:1 Navigate to the Honeywell DVM pages


3 Click the Camera Definition tab.

4 Set Stream type to Audio/Video.

6 – Configuration

354 Release 200

Configuring Honeywell DVM for video intercom Considerations• Although the MegaChips MD-100 supports 4 video inputs, it only supports

one audio input/output. Without dedicated multiplexing or mixing electronics Honeywell DVM is limited to a single audio input/output point in the field per MD-100 streamer.

Audio hardwareThe digital inputs on the rear of the MD-100 are used to notify Honeywell DVM of a request for intercom connection from the remote site. Connect a push button switch to one of the digital inputs of the MD-100. (The pinouts of the rear terminal block can be found in the MD-100 documentation.)

Considerations• Up to four intercom cameras can be configured on an MD-100, they will all

use the same audio input/output point and may only be connected (operational) one at a time. The digital input’s number corresponds to the intercom number configured in Honeywell DVM, not the video input number on the MD100.

Alarm configuration fileThe MegaChips MD-100 must also be configured to notify Honeywell DVM when the state of that digital input changes.

To perform this configuration:1 Choose Start > Run to open the Run dialog box.

2 Type cmd in the box and click OK.

3 When the command prompt appears, type ftp md100ipaddress and then press ENTER, where md100ipaddress is the address of the MD-100.

4 Log into the MD-100. The default username is Administrator, with no password. press ENTER.

5 Use the ascii command to set the transfer mode.

6 Upload the file almconf.cfg, using the command get almconf.cfg.

7 Once the file has been transferred, use the quit command to exit FTP.The following example of an FTP session is provided for reference.

Configuring Honeywell DVM for video intercom


C:\> ftp xxx.yyy.zzz.qqq

Connected to xxx.yyy.zzz.qqq.

220 eWatch MD-100 FTP Service

User (xxx.yyy.zzz.qqq:(none)): Administrator

331 Password required for "administrator"

Password: <enter>

230 User "administrator" login ok.

ftp> ascii

200 TYPE command successful.

ftp> get almconf.cfg

200 PORT command successful.

150 Opening ASCII mode data connection for Client.

226 Transfer complete.

ftp: 216 bytes received in 0.13Seconds 1.66Kbytes/sec.

ftp> quit

221 QUIT command successful.

8 Open almconf.cfg in an editor.

In this file there are four sections which correspond to the four digital inputs. Each section begins with an [almconf] heading. These sections are ordered from input 1 at the top of the file to input 4 at the bottom of the file.Each section looks like the following:[almconf]

time=0

dly=0

log=1

web=0

id=23

eof

[in_inport]

pno=1

mode=1

one=0

ons=15

ond=0

ofe=1

CautionThe almconf.cfg file will not display correctly in Notepad. It can be edited in Notepad successfully if the word wrap option is switched on. The Edit editor that is available through the command prompt will work correctly as will most third party text editors.

6 – Configuration

356 Release 200

ofs=600

ofd=0

min=0

time=0

web=0

eof

[call]

ip1=xxx.yyy.zzz.qqq

tcp1=14599

tel1=

sub1=

no=1

intv=10

msg=

wfg=0

dly=0

web=0

eof

9 Locate the section that corresponds to the input to which the push button was attached. Under the [call] heading, replace the xxx.yyy.zzz.qqq with the IP address of the Camera Server to which the MD-100 streamer is connected. Save the file.

10 FTP to the MD-100 again and use the Put command to load the file back to the streamer. The following example of an FTP session is provided for reference.C:\ >ftp xxx.yyy.zzz.qqq

Connected to xxx.yyy.zzz.qqq.

220 eWatch MD-100 FTP Service

User (xxx.yyy.zzz.qqq:(none)): administrator

331 Password required for "administrator"

Password:

230 User "administrator" login ok.

ftp> ascii

200 TYPE command successful.

AttentionA new streamer will not have default settings for these alarm configuration sections. You must add one copy of the above example for each intercom button Honeywell DVM should respond to.If the streamer is ever moved to a new Camera Server, this file will need to be re-edited to reflect the new Camera Server.

Configuring Honeywell DVM for video intercom


ftp> put almconf.cfg

200 PORT command successful.

150 Opening ASCII mode data connection for Client.

226 Transfer complete.

ftp: 216 bytes sent in 0.00Seconds 216000.00Kbytes/sec.

ftp> quit

221 QUIT command successful.

11 Power cycle the MD-100 streamer.

Audio settings

To configure the MegaChips MD-100 audio settings:1 Connect a speaker and microphone to the MD-100 on either the front or rear

panel inputs.

2 Using Internet Explorer, navigate to the MD-100’s Web pages: http://md100ipaddress.

3 When the Web pages appear, select the System settings button at the top.

4 Select Video/Audio Settings. Login to the streamer. The default username is Administrator with a blank password.

5 Navigate to System settings.

6 Set Audio output mode to On.

7 Set Audio input mode to Hi Quality.

8 Set the Volume to 5 and the front or rear input as appropriate.

Setting up Honeywell DVM for video intercom

Prerequisite• To be able to listen and talk to the field, the Station or Honeywell DVM client

must be equipped with a speaker and microphone.

To configure the camera:1 Configure the camera using the Camera Definition display.

2 Set the Stream type to Intercom/Video. This will enable the intercom on that camera and enable a new Intercom Definition tab.

6 – Configuration

358 Release 200

3 Go to the Intercom Definition tab and check boxes for intercoms corresponding to digital inputs configured previously. Set Alarm levels and preset positions as required for each intercom. If special presets are configured to be used as presets, select the appropriate special preset on the right. (Special presets are enclosed within parentheses, for example: (Setup menu).) For more information on configuring special presets, see “Defining special presets” on page 346.


7Operation

This chapter describes how to perform standard Honeywell DVM tasks in Station or Internet Explorer.

7 – Operation

360 Release 200

Using Station to view live video You use the Live Video tab on the Camera display to view and record live video for a particular camera.

To view live video:1 Click on Station’s toolbar to call up the System Menu (the “home page”

for EBI or Experion).

2 Click to call up the Live Video tab of the Camera display.Initially, the video for the first camera listed in the Navigation Pane is shown.

3 To see video for another camera, click it in the Navigation Pane. If the cameras are in groups, click the “+” sign to see the cameras in that group.To learn about the meaning of the camera symbols, see “About the camera symbols in the Navigation Pane” on page 370.

Figure 16 Typical Live Video in Station (The cameras are listed in the Navigation Pane on the left.)

Using Station to view live video


4 If you want to use the controls, see:

• “Using the live video controls and indicators” on page 364.

• “Using presets and tours” on page 369.

TipYou can navigate between cameras using the PAGE UP and PAGE DOWN keys.

7 – Operation

362 Release 200

Using Internet Explorer to view live video You use the Live Video tab on the Camera display to view and record live video for a particular camera.

Prerequisites• Your administrator has configured Internet Explorer security so that you can

view live video.

To view live video:1 Log on to your computer.

2 Start Internet Explorer and type the following URL:http://machinename/dvm

where machinename is the name of the Database Server. If you have a redundant Database Server, machinename is the name of the preferred server.The Honeywell DVM Live Video tab of the Camera display appears. This tab initially shows the video for the first camera listed in the Navigation Pane.

Figure 17 Typical Live Video in Internet Explorer (The cameras are listed in the Navigation Pane on the left.)

Using Internet Explorer to view live video


3 To see video for another camera, click it in the Navigation Pane. If the cameras are in groups, click the “+” sign to see the cameras in that group.To learn about the meaning of the camera symbols, see “About the camera symbols in the Navigation Pane” on page 370.

4 If you want to use the controls, see:

• “Using the live video controls and indicators” on page 364.

• “Using presets and tours” on page 369.

TipYou can navigate between cameras using the PAGE UP and PAGE DOWN keys.

7 – Operation

364 Release 200

Using the live video controls and indicators Note that the controls you see depend on the type of camera and the way in which your system has been configured. For example, the PTZ controls will not appear if you select a fixed camera, or if you have not been given access to those controls.

Control/indicator Description

(Appears if user-activated recordings have been enabled.)

Snapshot. Each time you click this button, Honeywell DVM creates a single-frame snapshot file of the video.For details about snapshot files see, “About snapshot files” on page 372.


Record. Starts recording the current video.Recording continues until you click the Stop button, or if a recording period has been specified for the camera, the recording period expires. The amount of time remaining until the recording terminates is shown in black.


Stop. Stops recording.

The current time and date of the camera.

This only appears when another user is controlling the camera—for example, using the PTZ controls.If your controls are grayed out, it means that you cannot control the camera while the other person has control. (Depending on how your system is configured, the name on the right is the operator ID or the Station that currently has control.)The time on the left is a countdown timer, which indicates how much longer before you can get control of the camera.

(Only appears if video analytics is enabled.)

Video analytics. Flashes blue when Honeywell DVM detects movement.

Using the live video controls and indicators


(Only appears if video analytics is enabled, and it has “regions of interest”.)

Regions of interest. Click this button to show or hide regions of interest.

(Only appears on PTZ cameras.)

Presets and tours.See “Using presets and tours” on page 369.


Focus. Controls the camera’s focus (so that you can clearly see an object).


Iris. Controls the camera’s iris. (The iris controls the amount of light that reaches the camera sensor.)


Zoom. Controls zooming of the camera lens.


Pan and Tilt. Controls the camera’s pan and tilt positions.

Enable. Video for the camera is visible while this check box is selected. Clear this check box to disable the camera, and stop the Camera Server processing its video.

(Only appears on intercom or audio-enabled cameras.)

Volume. To adjust the volume of the audio, click and adjust the volume control slider. Clicking somewhere other than the slider causes it to disappear.If you see a flashing warning icon .it means there is a problem with the audio signal.

(Only appears on intercom or audio-enabled cameras.)

Intercom. Click a button to commence a conversation. Click again to end the conversation.The button flashes red if there is a call waiting.


7 – Operation

366 Release 200

Annotations display mode. Click the button to shift it to the next mode. The three modes are:• All annotations• No annotations• Event annotationsThe button shows the mode currently being displayed.This button appears only on video streams that are currently running algorithms that support annotations. Algorithms that support annotations are: • Object tracking• Object tracking and classificationWhen annotations are switched on for object tracking and classification, it highlights all the objects being tracked and classified in the scene.The event annotation mode highlights objects that satisfy a configured condition.For a description of the symbols that appear in the video, see “About the video analytics symbols” on page 371.


Using the live video mouse PTZ controls


Using the live video mouse PTZ controlsThis topic is only applicable to cameras that support continuous PTZ.

You can use your mouse to control the positioning of a camera, and zoom in or zoom out.

When you move the mouse pointer over the video, the icon changes to an arrow or a magnifying glass. This depends upon the area of the video your mouse is hovering over. An arrow shows the direction the camera will move to and the magnifying glass will allow you to zoom in or out.

The figure below shows the directions you can move the camera and the approximate zoom area. Within the circle, the mouse pointer becomes a magnifying glass, enabling you to zoom in or out.

Controlling the camera movementTo control the movement of the camera with your mouse, move it over the video until you see the icon change to an arrow. There are two methods which can be used to move the camera. They are:

• A single click will move the camera in the direction of the arrow.

• Hold down the left mouse button and drag the mouse in the direction you want the camera to move to.

The speed the camera moves depends on where you click in relation to the centre of the video. The closer you are to the edge of the video, the faster the movement of the camera.

+-

7 – Operation

368 Release 200

Zooming inTo zoom in, move your mouse just above the centre of the video. When the magnifying glass appears with a “+”, click your left mouse button.

To continuously zoom in, hold down your left mouse button. To increase the speed of the zoom, drag the icon towards the top of the video and to decrease the speed drag back towards the centre of the video.

Zooming outTo zoom out, move your mouse just below the centre of the video. When the magnifying glass appears with a “-”, click your left mouse button.

To continuously zoom out, hold down your left mouse button. To increase the speed of the zoom, drag the icon towards the bottom of the video and to decrease the speed drag towards the centre of the video.

Using presets and tours


Using presets and tours You use these controls for presets and tours.

A preset is a defined PTZ setup for a camera. For example, if you frequently need to check the main entrance to a building, you could create a preset called “main entrance” that caused the camera to quickly zoom in on the main entrance. (A special preset is a pre-programmed function that is specific to each type of camera. Special presets are usually reserved for programming, setup and special control functions.)

A tour is a predefined sequence of presets. When you activate a tour, the camera moves from one preset to the next in a specified manner.

Notes• The names of special presets are enclosed in parentheses, for

example: (Road); and the names of tours are enclosed in square brackets, for example: [Trainline].

• If a part of the camera’s field of view is obscured by a gray box, this is a privacy zone. (Privacy zones are typically used to obscure private parts of change rooms.)

To view a preset:1 Click to the right of the list box to see the presets and tours.

2 Select the preset from the list—the camera then pans, tilts and zooms to the specified position.

To start a tour:1 Click to the right of the list box to see the presets and tours.

2 Select the tour from the list—the camera then starts the tour.

To create a preset:1 Set up the camera as required, using the pan, tilt and zoom controls.

2 Click the list.

3 Type an appropriate name, such as “Side Door”, and then click . (Do not include parentheses or square brackets in the name).

To delete a preset:1 Select it from the list.

2 Click .

7 – Operation

370 Release 200

About the camera symbols in the Navigation Pane

Symbol DescriptionThe camera is operating normally.

The camera’s video is currently being recorded.

Video analytics is currently being performed on the camera’s video.

The camera has been disabled.

The camera has failed.

There is an unknown problem, possibly with the Camera Server to which the camera is attached.

Someone is using intercom associated with the camera.

About the video analytics symbols


About the video analytics symbols Video analytics is the process of analyzing video signals to detect motion, or to track objects (and, optionally, classify of those objects).

Honeywell DVM includes a range of video analytics functions (also called “algorithms”), each of which is optimized for a specific purpose.

Honeywell DVM uses the following symbols to help you interpret the results of video analytics. Note that the symbols you see will depend on what video analytics functions are used in your system, and how they have been configured.

Symbol DescriptionWhite square or polygon that doesn’t move

Only applicable to motion detection.The “region of interest” in which Honeywell DVM attempts to detect movement.

Blue square or polygon that doesn’t move

Only applicable to motion detection.Indicates that Honeywell DVM has detected movement in the region of interest.

Red rectangle Only applicable to motion detection, and only visible while configuring motion detection or when replaying a recording.The red rectangle marks the section within the region of interest where Honeywell DVM has detected motion.

Moving white rectangle with symbol and number

Only applicable to object tracking and classification.The white rectangle marks the object that is being tracked. The symbol indicates the classification Honeywell DVM has given the object (car or person). A question mark means that Honeywell DVM was not able to classify the object.The number is the unique ID that Honeywell DVM has assigned to that object.

7 – Operation

372 Release 200

About snapshot files When you take a snapshot by clicking on the Live Video tab, Honeywell DVM creates a snapshot file and stores it in the snapshot folder on the computer. Having created a snapshot, you can then, for example, attach it to an email.

By default, snapshot files are stored in \Program Files\Honeywell\EBI or Experion\Client\DigitalVideoClient\snapshot.

Each snapshot file is named as follows:CameraName(Number)_yAAAAmBBdCChDDmEEsFFmsGGG.bmp

Where:

• CameraName is the camera name

• Number is the camera number

• yAAAAmBBdCChDDmEEsFFmsGGG is the year, month, day, hour, minute, second, milli-second when the snapshot was taken

Viewing recorded video


Viewing recorded videoIf you want to perform a more sophisticated search, see “Searching for recorded video” on page 383.

Considerations• When you choose to view full size video, another window is opened, showing

the Honeywell DVM video player. Your Station or Internet Explorer client is still displayed in the background.

• Gray text indicates that the video has been archived. Blue text indicates that the recording has been restored from archive.

To view a recording:1 In the Navigation Pane, click the camera whose recordings you want to view.

2 Click the Recordings tab to see the recordings for that camera. Initially, the recordings for the current day are shown.

3 If the recording was done on another day, select the date from Recordings on.The recordings for that day appear in the list.

TipYou can see the recordings for the next/previous day by clicking the buttons on either side of the date.

7 – Operation

374 Release 200

4 Select a video clip from the list, you will see it appear paused in the video player. To check that you have selected the correct video, you can press the play button.If the video clip selected had pre-record defined, the frame shown is the frame which was recorded when the operator pressed record or the video analytic, EBI or Experion event occurred, not the first frame of the recording.

5 You can also:

• Type any relevant comments in Notes. (Adding a note can be useful because you can use the notes to retrieve the video clip—see “Doing an advanced search” on page 384.)

• Archive it immediately by clicking the Archive button, or change the default archive instructions by changing the Archive on values.

• Delete it immediately by clicking the Delete button, or change the default deletion instructions by changing the Delete on values.

• Prevent a video clip being archived or deleted by clearing the Archive on or Delete on check boxes.

• Export a video clip. For more information about exporting, see “Exporting a video clip” on page 411.

• Take a snapshot of part of the video clip by clicking . For more information, see “Using the live video controls and indicators” on page 364.

• View full size video by clicking on the View full size video link. This is useful when the resolution of the recorded video clip is greater than the resolution being displayed.

Using the playback controls and indicators


Using the playback controls and indicators When you view recorded video, following the instructions in “Viewing recorded video” on page 373, the video player displays the following controls and indicators.

Control/Indicator DescriptionPlay. Plays the recording.

Stop. Stops the video.

Pause. Pauses the video.

Snapshot. Exports a single frame of the video.

Fast rewind. Rewinds the video at a speed determined by the number of times you click the button. Clicking the button once rewinds the video at normal playback speed. Clicking the button two or more times increases the rewind speed as follows:• 2 = 4 times normal playback speed• 3 = 16 times normal playback speed• 4 = 64 times normal playback speed• 5 = 256 times normal playback speed• 6 = 1024 times normal playback speedTo slow the video, right-click the button one or more times (each right-click halves the playback speed).Fast forward and Fast rewind occur at the same speed.

Frame rewind. Moves the video back a single frame.

Frame Forward. Moves the video forward a single frame.

7 – Operation

376 Release 200

Fast Forward. Plays the video at a speed determined by the number of times you click the button. Clicking the button once plays the video at normal playback speed. Clicking the button two or more times increases the playback speed as follows:• 2 = 4 times normal playback speed• 3 = 16 times normal playback speed• 4 = 64 times normal playback speed• 5 = 256 times normal playback speed• 6 = 1024 times normal playback speedTo slow the video, right-click the button one or more times (each right-click halves the playback speed).Fast forward and Fast rewind occur at the same speed.

(Appears when video analytics is enabled only.)

Regions of interest. Shows/hides regions of interest.This button appears only on video streams that are currently running algorithms that supporting regions of interest.See “About the video analytics symbols” on page 371.

(Appears when annotations are enabled only.)

Annotations display mode. Controls the annotation mode. Each time you click the button, the mode shifts as follows:• All annotations• No annotations• Event annotationsThe button shows the current annotation mode.This button appears only on video streams that are currently running algorithms that support annotations:• Object tracking• Object tracking and classificationWhen annotations are switched on, the objects being tracked and classified are highlighted. See “About the video analytics symbols” on page 371.

Control/Indicator Description

Viewing a quad view


Viewing a quad viewA quad view simultaneously shows four live videos.

To call up a quad view:• In the Navigation Pane, click Quad Views.

• Click the quad view you want to view.

TipDouble-clicking on a camera in the quad view will change the display to show only the selected camera.

7 – Operation

378 Release 200

Viewing a sequenceA sequence shows live video that switches cameras and camera presets at a specified interval.

To call up a sequence:1 In the Navigation Pane, click Sequences.

2 Click the sequence you want to view.

Using the intercom


Using the intercom

Initiating a call from the fieldCalls can be initiated from the field via the push button or by the operator from the live video page for the intercom camera.

Answering a field-initiated callWhen someone in the field presses the push button, Honeywell DVM:

• Sends an alarm to EBI or Experion

• Underlines the camera’s name in the Navigation Pane

• Flashes (and turns red) the intercom button on the live view

Considerations• A recording is automatically started when the call is answered. Audio from

the field is recorded along with video but audio from the operator to the field is not recorded.

To answer the call, click the intercom button on the video player. The button will turn green to indicate a call in progress. Audio from the field can be heard from the speaker at the Station and the operator can speak to the field via the microphone at the Station.

7 – Operation

380 Release 200

Initiating a call by an operatorTo manually initiate a call, click the intercom button on the video player. The button will turn green to indicate a call in progress.

Terminating a callTo terminate a call, click the intercom button on the video player or navigate away from the live video page for the camera.

Adjusting audio for live and recorded video


Adjusting audio for live and recorded video When audio is enabled on an Axis, MD-100 or CS-3001V streamer, both live and recorded video can play the audio. (Honeywell DVM must be configured to record audio for scheduled and background recordings.)

When live or recorded video from a camera with audio enabled is displayed in the video player, the video player displays an audio icon.

The audio icon will show a failed indication if there is a problem obtaining the audio stream from the streamer, the audio icon will show a failed indication. For more information, see “Using the live video controls and indicators” on page 364 or “Using the playback controls and indicators” on page 375.

Adjusting the volume

To adjust the volume:1 Click on the audio icon. The volume control slider appears.

2 Drag the volume control slider up or down as appropriate.

Clicking off the slider causes it to disappear.

Disabling audio on a scheduled recordingTo reduce recording disk storage, it is possible to disable the recording of audio on a scheduled recording. To do this, clear the Record Audio check box when creating the schedule, or clear the check box on the Schedule details tab for an existing schedule. (For more information on configuring a schedule, see “Creating a schedule” on page 306.)

Disabling audio on a background recordingThere are two ways to disable audio for background recording.

To disable audio recording:1 In the Navigator, select the camera you want to configure.

2 Select the Camera Definition tab.

3 Set the camera to Video only.The audio is now disabled.

7 – Operation

382 Release 200

To let an operator disable audio recording:1 In the Navigator, select the camera you want to configure.

2 Select the Camera Definition tab.

3 Set the camera to Audio/Video.

4 Select the Recordings tab.

5 Clear the Audio Enabled check box (in the Background Recording section).

Exporting video with audioIf a recording contains audio, it is automatically included in an exported video clip.

Considerations• If an exported video clip containing audio is played on a computer without

audio capabilities, Windows Media Player displays an error. You can still play the video by acknowledging this error.

Searching for recorded video


Searching for recorded videoIf you know the day on which a video clip was recorded, you can do a simple search (page 383). If you have only partial information about the recording, such as the event that initiated the recording, you need to do an advanced search (page 384).

Note that Honeywell DVM only “finds” video clips that you are allowed to view.

Doing a simple searchA simple search searches for video clips that were recorded on a particular day, or a range of days.

To do a basic search:1 In the Navigation Pane, click Search.

2 Select the time range you want to search, as described in the following table and then click Go.

Select this: To find videos that were recorded:Today Today, starting from midnight.

Yesterday Yesterday, from midnight to midnight.

Last Week For the last 7 days, from midnight to midnight.

7 – Operation

384 Release 200

3 View the results of your search. See “Viewing the search results” on page 387.

Doing an advanced searchAn advanced search allows you to specify a wide range of search criteria including the camera that recorded the video and the user that initiated the recording.

To do an advanced search:1 In the Navigation Pane, click Search.

2 Click the Advanced Search hyperlink.

Last Month From the same calendar date last month until today. For example, if today is the August 13, the videos will be from July 13 to August 13.

On A particular day. You must select the date from a calendar.

On or before On or before a specific date. You must select the date from a calendar.

Between A range of dates. You must select the start and end dates from a calendar.

Select this: To find videos that were recorded:



3 Specify your search criteria, as described in the following table, and then click Go.If you specify more than one search criteria, make sure they do not conflict. For example, do not select both Activated by and Event because a video cannot be both user-activated and event-activated.

Use this: To find videos:Video recorded Recorded on a particular day, or between specified dates.

The values are:• Today = Today, starting from midnight.• Yesterday = Yesterday, from midnight to

midnight.• Last Week = For the last 7 days, from midnight to

midnight.• Last Month = From the same calendar date last

month until today.• On = A particular day. You must select the date from

a calendar.• On or before = On or before a specific date. You

must select the date from a calendar.• Between = A range of dates. You must select the

start and end dates from a calendar.

On cameras Associated the cameras listed in the left-hand box.To add all cameras to the left-hand box, click Add All.To add a specific camera to the left-hand list, click a camera in the right-hand box and then click Add. Repeat as necessary for other cameras.To remove a camera from the search, click the camera in the left-hand box and then click Remove.Note: If you do not select any cameras, the search will run on all cameras.

Activated by Filter based on what started the recording. Choose between:• All

• Schedule

• Event

• Operator

• Video Analytics

• Background

• Intercom

7 – Operation

386 Release 200

4 View the results of your search. See “Viewing the search results” on page 387.

Useri Associated with a particular user.

Point IDi Associated with a particular point.

Descriptioni Whose description contains the specified text.

EventSubpriorityi

Associated with a particular event/alarm level and subpriority.

Valuei Associated with a particular point value. The values, such as “fail” and “tamper”, are the same as those that appear in the Alarm Summary display.

Areai Associated with a particular area.

Notesi Whose notes contain the specified text.

i You do not need to enter the complete details if you want to search using these fields. For example, if you enter “smi” in User, the search will return recordings initiated by “jsmith”, “smithson” and so on.

Use this: To find videos:



Viewing the search resultsThe Search Results display lists all recorded videos that match your search criteria, and which you are allowed to view.

A blue entry indicates that the video has been restored from archive; a gray entry indicates that the video is stored offline, and must be restored before you can view it. (If you need to restore an archived video, see “Restoring video clips” on page 418.)

To view a video:1 Click an entry in the list to see a single frame in the video. (This is generally

the first frame. However, if pre-record was defined, it is the frame that corresponds to the time at which the operator clicked Record, or the EBI or Experion event occurred.)

2 If you want to view the video, use the playback controls.

7 – Operation

388 Release 200

3 Having selected a video clip, you can:

• Type any relevant comments in Notes. (Adding a note can be useful because you can them to retrieve the video clip for later searches.)

• Archive the video clip immediately by clicking Archive. (Alternatively, change the default archive instructions by changing the Archive on values.)

• Delete the video clip immediately by clicking Delete. (Alternatively, change the default deletion instructions by changing the Delete on values.)

• Prevent the video clip being archived or deleted by clearing the Archive on or Delete on check boxes.

• Export the video clip. For details, see “Exporting a video clip” on page 411.

• Take a snapshot of a particular frame in the video clip by clicking .

• View the video in full size by clicking the View full size video hyperlink. This is useful when the resolution of the recorded video clip is greater than the resolution being displayed.

4 If you do not find the video you are looking for, click the Search again hyperlink at the top-right of the display. (This redisplays your original search criteria, which you can then modify before performing another search.)

Preventing a video clip from being deleted


Preventing a video clip from being deleted Honeywell DVM deletes video clips when:

• the deletion date for the clip has been reached

• the disk becomes full, triggering automatic deletion of the oldest clips

To prevent an important video clip from being deleted:1 Locate the clip, either through the Recordings tab, or through the Search

screen, see “Searching for recorded video” on page 383.

2 Clear the Delete on check box.Honeywell DVM will now not delete the clip.

7 – Operation

390 Release 200

Preventing a video clip from being archived Honeywell DVM archives video clips when the archive date for the clip is reached.

To prevent a video clip from being archived:1 Locate the clip, either through the Recordings tab, or through the Search

screen, see “Searching for recorded video” on page 383.

2 Clear the Archive on check box.Honeywell DVM will now not archive the clip.

Using the numeric keypad


Using the numeric keypadWhen you become familiar with Honeywell DVM, you can use the numeric keypad to quickly perform many tasks. This includes the ability to call up camera views on a local Station, or display and clear multi-monitor camera views. For example, to call up camera 7 on monitor 3, you would use the following key sequence:

7 + 3 Enter

(This is shorthand for typing the camera number, pressing the “+” key, typing the monitor number and then pressing the Enter key.)

The following table describes the purpose of the “command” keys.

Considerations• Make sure the Num Lock key is turned on before entering commands using

the numeric keypad.

To: Press: Example:Specify camera n n Call up camera 7 on the main monitor:

7 Enter

Specify preset n . n Call up preset 2 for the current camera on the main monitor:

. 2 Enter

Specify monitor n + n Call up camera 5 on monitor 3:5 + 3 Enter

Clear camera on monitor n - n Clear the surveillance camera on monitor 3:

- 3 Enter

In the case of an alarm monitor with cycling camera views, the currently displayed camera view will be cleared. To ensure the correct camera view is cleared, avoid executing a clear command near the end of a view cycle.

Specify a quad view n * n Call up quad view 5 on the main monitor:* 5 Enter

Specify a sequence n / n Call up sequence 2 on the main monitor:/ 2 Enter

7 – Operation

392 Release 200

More examplesCall up camera 27 on monitor 3:

27 + 3 Enter

Call up camera 17, preset 2 on the main monitor:17 . 2 Enter

Call up camera 27, preset 2 on monitor 3:27 . 2 + 3 Enter

Call up quad view 4 on monitor 3:* 4 + 3 Enter

Call up sequence 2 on monitor 3:/ 2 + 3 Enter


8Administration

This chapter describes how to perform administrative tasks.

8 – Administration

394 Release 200

Giving users access to Honeywell DVM This section describes how to give users access to Honeywell DVM.

The tasks you must perform to give a user access to Honeywell DVM depend on how security has been configured for your system. Use the following table to select the appropriate checklist.

If you use: And you want to give the user access to:

And you use this type of Station security:

And you use integrated accounts:

Go to:

Domain security Internet Explorer N/A N/A page 395

Station (and also Internet Explorer if required)

Operator-based Yes page 396

No page 397

Station-based N/A page 398

Workgroup security Internet Explorer N/A N/A page 399

Station (and also Internet Explorer if required)

Operator-based Yes page 400

No page 401

Station-based N/A page 403

Giving users access to Honeywell DVM


Giving a user access: Internet Explorer in a domain environment


Task Go to: Done?Add the user’s Windows account to the domain group for Honeywell DVM users.

page 405

Add the user to the list of Honeywell DVM users in the Honeywell DVM database.

page 406


396 Release 200

Giving a user access: operator-based security with integrated accounts in a domain environment

Prerequisites• The user has an integrated account, and can access EBI or Experion. (For

details about setting up an integrated account for a user, see the EBI or Experion documentation.)

Considerations• Honeywell DVM does not support Ack Only and View Only area access.


Task Go to: Done?Add the user’s Windows account to the domain group for Honeywell DVM users.

page 405

If the user needs to access Honeywell DVM through Station on the EBI or Experion server or through a Console Station, add the user’s account to the Honeywell Administrators group on the domain controller.

If the user needs to access Honeywell DVM through Internet Explorer, add the user to the list of Honeywell DVM users in the Honeywell DVM database.

page 406



Giving a user access: operator-based security without integrated accounts in a domain environment

Prerequisites• The user has an operator ID, and can access EBI or Experion. (For details

about setting up an operator ID for a user, see the EBI or Experion documentation.)



Task Go to: Done?If the user logs on to:

• The Station computer using a Windows account before logging on to Station, add that Windows account to the domain group for Honeywell DVM users.

page 405

• Station without first logging on to the computer, add the Windows account under which Station runs to the domain group for Honeywell DVM users.

Note: If the user uses several such Stations, you must add each of these “Station Windows accounts” to the domain group.

page 405

If the user needs to access Honeywell DVM through Station on the EBI or Experion server or through a Console Station, add the Windows account under which Station runs to the Honeywell Administrators group on the domain controller.

If the user needs to access Honeywell DVM through Internet Explorer:

• Add the user’s Windows account the domain group for Honeywell DVM users.

page 405

• Add the user to the list of Honeywell DVM users in the Honeywell DVM database.

page 406


398 Release 200

Giving a user access: Station-based security in a domain environment

Prerequisites• Station has been configured as described in the EBI or Experion

documentation.


Task Go to: Done?Add the Windows account under which Station runs to the domain group for Honeywell DVM users.Note: If the user uses several such Stations, you must add each of these “Station Windows accounts” to the domain group.

page 405

If the user needs to access Honeywell DVM through Station on the EBI or Experion server or through a Console Station, add the Windows account under which Station runs to the Honeywell Administrators group on the domain controller.


• Add the user’s Windows account to the domain group for Honeywell DVM users.

page 405


page 406



Giving a user access: Internet Explorer in a workgroup environment

Considerations• If you change a user’s security level while the user is accessing a Honeywell

DVM display, the changes will not take effect until the user refreshes the display.


AttentionThe name and password of the user’s Windows account must be the same on all Database and Camera Servers and on all client computers on which the user accesses Honeywell DVM.

Task Go to: Done?Create the user’s Windows account on every client computer used to access Honeywell DVM.

Create the user’s Windows account on every Database Server and Camera Server.

page 404

Add the user’s Windows account to the DVM_Users group on every Database Server and Camera Server.

page 409

Add the user to the list of Honeywell DVM users in the Honeywell DVM database.

page 406


400 Release 200

Giving a user access: operator-based security with integrated accounts in a workgroup environment

Prerequisites• The user has an integrated account, and can access EBI or Experion. (For

details about setting up an integrated account for a user, see the EBI or Experion documentation.)



AttentionThe name and password of the user’s Windows account must be the same on all computers that need that account.

Task Go to: Done?Create the user’s Windows account on every Database Server and Camera Server.

page 404

Add the user’s Windows account to the DVM_Users group on all Database Servers and Camera Servers.

page 409

Create the user’s Windows account on the EBI or Experion Servers and Console Stations.

page 404

Add the user’s Windows account to the Honeywell Administrators group on the EBI or Experion Servers and Console Stations.

page 410

If the user needs to access Honeywell DVM through Internet Explorer, add the user to the list of Honeywell DVM users in the Honeywell DVM database.

page 406



Giving a user access: operator-based security without integrated accounts in a workgroup environment

Prerequisites• The user has an operator ID, and can access EBI or Experion. (For details

about setting up an operator ID for a user, see the EBI or Experion documentation.)



AttentionThe name and password of each Windows account must be the same on every computer that needs that account.

Task Go to: Done?If the user logs on to:

• The Station computer using a Windows account before logging on to Station, create the user’s Windows account on every Database Server and Camera Server.

page 404

• Station without first logging on to the computer, create the Windows account under which Station runs on every Database Server and Camera Server.

Note: If the user uses several such Stations, you must create each of these “Station Windows accounts” on every Database Server and Camera Server.

page 404

Add the account(s) identified above to the DVM_Users group on all Database Servers and Camera Servers.

page 409


• Create the user’s Windows account on every Database Server and Camera Server.

page 404


page 406


402 Release 200

• Add the user’s Windows account to the DVM_Users group on all Database Servers and Camera Servers.

page 409

Task Go to: Done?



Giving a user access: Station-based security in a workgroup environment

Prerequisites• Station has been configured as described in the EBI or Experion

documentation.


AttentionThe name and password of each Windows account must be the same on every computer that needs that account.

Task Go to: Done?Create the Windows account under which Station runs on on every Database Server and Camera Server.Note: If the user uses several Stations, you must create each of these “Station Windows accounts” on every Database Server and Camera Server.

page 404

Add the Windows account under which Station runs to the DVM_Users group on all Database Servers and Camera Servers.Note: If the user uses several Stations, you must add each of these “Station Windows accounts” to the DVM_Users group on all Database Servers and Camera Servers.

page 409

If the user needs to access Honeywell DVM through Station on the EBI or Experion server or through a Console Station, add the Windows account under which Station runs to the Honeywell Administrators group on the server.

page 410


• Create the user’s Windows account on every Database Server and Camera Server.

page 404


page 406

• Add the user’s Windows account to the DVM_Users group on all Database Servers and Camera Servers.

page 409


404 Release 200

Creating a Windows user account

Prerequisites• The name and password of the Windows account, as specified on client

computers.

To create a user account: 1 Log on to Windows as an administrator.

2 Choose Start > Settings > Control Panel > Administrative Tools > Computer Management to open the Computer Management dialog box.

3 Under Local Users and Groups, click Users.

4 Choose Action >New User.

5 Enter the account name and password (both must be the same as that specified on client computers).

6 Enter an appropriate full name and description.

7 Click Create and then click Close.

8 Log out and back in for the changes to take effect.



Adding a user to the domain group for Honeywell DVM usersThis topic is only applicable if you use domain security.

This topic describes how to add user’s Windows account to the domain group for Honeywell DVM users. (Only users who have been added to this group can access Honeywell DVM.)

Prerequisites• The domain group for Honeywell DVM has been configured. (See

“Configuring security for Honeywell DVM in a domain environment” on page 289.)

• You have access rights on the domain controller that allow you to add users to groups.

To add a user to the Honeywell DVM user group:1 Log on to the domain controller with a suitable account.

2 Add the user to the group that was created for Honeywell DVM users.

3 Log out and back in for the changes to take effect.


406 Release 200

Giving a user access to Honeywell DVM through Internet ExplorerTo give a user access to Honeywell DVM through Internet Explorer, you must add their details to the following tables in the Honeywell DVM database:

• tblOper

• tblOperArea—only applicable if you use areas (assets)


example, use the account used to install Honeywell DVM.)

Considerations• Data you enter is case sensitive—this is critical in the case of Windows

accounts and areas.

• Delete any spaces at the beginning of a field.

To give an Internet Explorer user access:1 Log on to the Database Server.



4 Right-click tblOper and choose Open Table > Return All Rows.

5 In the tblOper window, complete the fields as follows:

Field DescriptionOperNumber The user’s unique identification number. A number

equal to or greater than 5001.

OperName The name of the user’s Windows account.



6 Close the tblOper window.

7 If you use areas, right-click tblOperArea and choose Open Table > Return All Rows.

8 In the tblOperArea window, complete the fields as shown in the following table.

9 If the user has access to more than one area, repeat step 8 for the other areas. (A separate row is required for each area the user needs to access.)

10 Close the tblOperArea window.

ExamplesIf “jsmith” is working on a domain and requires access to engineer-level functions and has a control level of 240, the database entry would be:

OperLevel The user’s security level number, which must correspond with the security level defined in EBI or Experion.:0 = LVL11 = LVL22 = OPER3 = SUPV4 = ENGR5 = MNGR

OperControlLevel The user’s control level, as configured in EBI or Experion. This ranges from 0 to 255.

In this field EnterOperNum The user’s unique identification number, as specified in

tblOper.

AreaCode The area code, as defined in EBI or Experion.

Field Description

OperNumber OperName OperLevel OperControlLevel5001 jsmith 4 240


408 Release 200

If “jsmith” (whose OperNumber is 5001) was allowed to access areas A1 and A3, the database entries would be:

OperNum AreaCode5001 A1

5001 A3



Adding Windows accounts to the DVM_Users group

To add Windows accounts:1 Choose Start > Settings > Control Panel > Administrative Tools >

Computer Management to open the Computer Management dialog box.

2 Under Local Users and Groups, click Groups.

3 Double-click DVM_Users and click Add.

4 Select the account and click Add.Repeat this step until you have listed all the accounts in the lower box.

5 Click OK.

6 Click Apply in the DVM_Users properties dialog box, then click Close.

7 Log out and log back in for the changes to take effect.


410 Release 200

Adding Windows accounts to the Honeywell Administrators group

To add Windows accounts:1 Choose Start > Settings > Control Panel > Administrative Tools >

Computer Management to open the Computer Management dialog box.

2 Under Local Users and Groups, click Groups.

3 Double-click Honeywell Administrators and click Add.

4 Select the user, click Add.

5 Click OK.

6 Click Apply in the Honeywell Administrators properties dialog box, then click Close.

7 Log out and log back in for the changes to take effect.

Exporting video clips and audit logs


Exporting video clips and audit logs When you export files, Honeywell DVM digitally signs the exported files. The digital signature file has a .sig extension and is saved in the same folder as the exported video and audit log files. For more information, see “Configuring a digital certificate” on page 343.

Exporting a video clipHoneywell DVM can export video clips in Windows Media Format which can then be viewed using Windows Media Player.

You can export either a whole clip or part of a clip from the Recordings tab or the Search Results page.

You can also export the Honeywell DVM audit log. For more information see, “Exporting the audit log” on page 412.

When you export a video clip, up to four files can be generated. Honeywell DVM can package these files into a single zip file. For more information, see, “Packaging the exported files into a zip file” on page 415.

Considerations• If you want to export more than one MPEG4 video clip, you should wait until

the current clip has been exported before exporting the next clip. (During the export process, the video clip is compressed which dramatically increases the load on the CPU. Simultaneously compressing two clips may result in corrupted exported files.)

To export a video clip:1 Select the clip you want to export from the Recordings tab or Search Results

page. Click Export.

2 Select the section of the clip you want to export. Click Export.

3 Specify the filename and folder you want the file saved to. Click Save.The Status dialog box will appear.

4 Once the file has been exported, click OK.

5 Click Go back to return to the Recordings tab or Search Results page.

ExampleIf you export a video clip with a filename Frontdoor, the following files will be generated:


412 Release 200

Exporting the audit logThe Honeywell DVM audit log traces users’ actions and system events and provides an audit trail.

These audit events are stored in the Honeywell DVM database.

When you export the audit log, system events and the events for the appropriate camera are exported.

Audited eventsThe following table lists the events that are audited.

Filename File contains:Frontdoor.wmv The video clip

Frontdoor.wmv.sig The digital signature for the video clip

Frontdoor.log The text file containing the audit log

Frontdoor.log.sig The digital signature for the audit log

Event group EventCamera events start viewing camera

enable camera

disable camera

add camera

delete camera

move camera to a preset

change camera setting

Quad view events start viewing a quad view

stop viewing a quad view

add quad view

delete quad view

change quad view property

add camera to a quad view

delete camera from a quad



Camera sequence events start viewing camera sequence

stop viewing camera sequence

add camera sequence

delete camera sequence

change camera sequence property

add camera (and preset) to a camera sequence

delete camera (and preset) from a camera sequence

Schedule events add a recording schedule

add a video analytics schedule

delete a recording schedule

delete a video analytics schedule

change a recording schedule

change a video analytics schedule

Recording events start user-activated recording

end user-activated recording

start scheduled recording

end scheduled recording

start event-activated recording

end event-activated recording

delete a user-activated recording

delete a scheduled recording

delete a background recording video clip

delete an event-activated recording

delete a video analytics recording

Export events request export of video clip

request export of audit log

Honeywell DVM camera service events

start the Honeywell DVM camera service

stop the Honeywell DVM camera service

Multimonitor surveillance camera sent to multi-monitor screen

camera cleared from multi-monitor screen

sequence view sent to multi-monitor screen

quad view sent to multi-monitor screen

alarm view sent to multi-monitor screen

Event group Event


414 Release 200

Exporting the audit log with a video clipYou can export the Honeywell DVM audit log when you export a video clip. When you export the audit log you can specify how much of the audit log to export with the video clip.

Considerations• Exporting a large number of events will use a large amount of your system

resources. The Export display indicates the limit of events that can be exported.

• If you want to export more than one MPEG4 video clip, you should wait until the current clip has been exported before exporting the next clip. (During the export process, the video clip is compressed which dramatically increases the load on the CPU. Simultaneously compressing two clips may result in corrupted exported files.)

To export the audit log with a video clip:1 Select the clip you want to export, click Export.

2 Select the section of the clip you want to export.

Streamer events streamer not responding

streamer back to normal

Video analytics events enable video analytics

disable video analytics

start video analytics schedule

end video analytics schedule

start video analytics activated record

end video analytics activated record

enter video analytics tuning mode

exit video analytics tuning mode

start video analytics activity

end video analytics activity

change video analytics setting

Clip deletion video clip deletion

Event group Event



3 Select Export audit log and specify the part of the audit log to be exported as described in the following table:

4 Click Export.

5 Specify the filename and folder you want the files saved to. Click Save.The Status dialog box will appear. Both files will have the same filename, but the audit log will be saved with a .log extension.

6 Once the files have been exported, click OK.


Packaging the exported files into a zip fileUp to four files are generated during the export operation, therefore you might want to package all the exported files into a single zip file.

The zipped exported files are saved in the same folder as the exported files and will have the same filename with a .zip extension.

To package the exported files into a zip file:1 Select the video clip you want to export, click Export.

2 Select the section of the video clip you want to export.

3 Select Package up exported files into a single zip file.

4 If you want to export the audit log, select Export audit log and specify the part of the audit log to be exported as described in the following table:

Property Descriptionbetween these dates and times Exports the events which occurred during the

specified date and times.

from the start date and time onwards

Exports the events which occurred from the date and time specified in the Export from property.

up to the end date and time Exports events which occurred prior to the to property.

Property Descriptionbetween these dates and times Exports the events which occurred during the

specified date and times.

from the start date and time onwards

Exports the events which occurred from the date and time specified in the Export from property.

up to the end date and time Exports events which occurred prior to the to property.


416 Release 200

5 Click Export.

6 Specify the filename and folder you want the files saved to. Click Save.The Status dialog box will appear. All files will have the same filename, but the audit log will be saved with a .log extension and the zip file will be saved with a .zip extension.

7 Once the files have been exported, click OK.


ExampleIf you export a video clip named Frontdoor.wmv, the zipped file will be named Frontdoor.zip.

Verifying the exported Honeywell DVM filesExported Honeywell DVM files containing a digital signature can be verified by using the Honeywell DVM Video Export Player application.

To verify an exported Honeywell DVM file:1 Choose Start > Run, type HWDVSVerifyExports.exe and click OK.

The Honeywell DVM Video Export Player will start.

2 Click Browse, select the video clip file and click Open.Honeywell DVM Video Export Player will load the video and any attached audit log file and will attempt to verify the digital signature on the files.

Archiving and restoring video clips


Archiving and restoring video clips You use any suitable form of media to archive video clips off-line, such as DVD, CD or tape.

As a first step to archiving video clips off-line, Honeywell DVM moves the clips to the archive folder (specified during installation of Honeywell DVM). When Honeywell DVM moves a clip, the clip is longer available from the short or medium term storage, and its status changes to “off-line”.

You can then archive the clips in the archive folder to the media using any backup program, for example NTBackup.

Prerequisites• You must have ENGR or MNGR security level to perform these tasks.

Automatically archiving video clips

To automatically archive video clips:You can use the Archive After period to set a default period after which the recording clip will be archived. On this date, the clip is archived without operator intervention.

You can set the archive after property of every type of recording. (See the Configuration chapter to learn how to configure each recording type’s Archive After period.)

Operators can modify this date by viewing the recording details and changing the Archive on value for the individual recording.

When archived, each clip has its own folder and uses the following naming convention:

XXXX_mmddyyhhmmss_TTTTTTT_zzzz

where

• XXXX is the camera number

• mmddyyhhmmss is the date and time the recording was activated by an event or a person.

• TTTTTTT is the type of recording. The types are user, schedule, event or motion

• zzzz is the duration in seconds


418 Release 200

Manually archiving video clips

To manually archive video clips:1 Go to the Recordings tab.

2 Select the clips, on the clip selection grid. (You can select multiple clips for archiving.)

3 Click Archive.Each clip has its own folder and uses the following naming convention:XXXX_mmddyyhhmmss_TTTTTTT_zzzz

Where:

• XXXX is the camera number

• mmddyyhhmmss is the date and time the recording was activated by an event or a person

• TTTTTTT is the type of recording. The types are user, schedule, event or motion

• zzzz is the duration in seconds

Once the clips have been moved, the clip data is no longer available from the short or medium term storage and marked as off-line in the Honeywell DVM database. The text will also be grayed in the clip grid.

Restoring video clips

Prerequisites• The files you want to restore must be in the folder to which they were

archived. Use the Restore to original location option in your backup package to copy the files from the off-line storage media to the original folder.

To restore video clips:1 Go to the Recordings tab.

2 Select the off-line recording in the Recordings grid. (You restore recordings one at a time.)

3 Click Restore.If all the files for the recording are available, it will be restored.

The video clip is now marked in the Honeywell DVM database as restored and is displayed in blue in the clip grid. The status is the same as the original clip type.

Archiving and restoring video clips


Next time the restored clip is selected for archiving, a second copy will not be made on tape. The data is deleted from short or medium term storage and the clip is marked as off-line in the clip grid.

If an archived clip is selected for deleting, the record in the database and all files that exist on the Honeywell DVM system for that clip (restored or in the archive buffer on disk) are deleted.


420 Release 200

Viewing the status of the Database Server If you have a redundant Database Servers, you use the Redundancy display to view the servers’ redundancy status. You can also specify which server is the preferred Database Server.


To view the redundancy status:1 Navigate to the Honeywell DVM pages.


3 Click the Redundancy tab.

To change the preferred Database Server:1 Navigate to the Honeywell DVM pages.


3 Click the Redundancy tab.

4 From the Preferred server list, select the Database Server you want to make the preferred Database Server.

Property DescriptionPreferred server The name of the current preferred Database Server.

Database Servers A list of the available Database Servers and their status.

Replication status Shows if the servers are replicating correctly.

Redundant pair connected Shows if the redundant pair is still connected.

Viewing the status of the Camera Servers


Viewing the status of the Camera Servers You use the Server Status display to view the status of each camera server, which is either: OK or Software Fault.

Note that this display is dynamically updated.


To view the status of the Camera Servers:1 Navigate to the Honeywell DVM pages.


3 Click the Server Status tab.


422 Release 200

Viewing the disk usage details of a Camera Server Prerequisites• You must have ENGR or MNGR level access to perform this task.

To view disk space details:1 Navigate to the Honeywell DVM pages.


3 Click the Disk Space tab.

4 In the Camera Server box, select the Camera Server whose disk usage you want to view.The disk usage details are shown in the Disk Usage table. Each row shows the details for a folder that the Camera Server is currently writing to. (To learn about the other properties, see “Configuring disk space administration” on page 333.)

5 If you want to update the details as you are viewing it, click Refresh. (The details are not automatically updated.)

Property DescriptionDirectory The folder in which video clips are stored.

DVM Clips (GB) The amount of space (GB) used by completed video clips. (Video clips that are still being recorded are not included in this value.)

Free Space (GB)Free Space (%)

Remaining free disk space, expressed in (GB) and as a percentage.

Hourly Usage (MB/hr) An indication of the rate at which videos are being stored on the disk.Note that the value is only based on the usage rate for the minute before you called up the display, or since you last clicked Refresh.

Disk Health Indicates the disk’s health, either: OK or Fault.

Manually resynchronizing redundant Database Servers


Manually resynchronizing redundant Database Servers This topic is only applicable if you have redundant Database Servers and one of the servers (primary or backup) has not been in service for more than 14 days. (If a server has been out of service for less than 14 days, the servers will automatically resynchronize when the server is returned to service.)

In this procedure, “publisher” refers to the primary (preferred) server and “subscriber” refers to the backup (secondary) server.

To synchronize the servers:1 On the “publisher” server, choose Start > Programs > Open SQL

Enterprise Manager.

2 Choose Tools > Replication > Show Replication Monitor Group to show the Replication Monitor Group in the tree on the left.

3 Expand the Replication Monitor Group until you can see Publishers > DatabaseServerName > DVM:DVM.

4 Right-click DVM:DVM and choose Properties.

5 If an introductory window appears, click OK.

6 Click the Subscriptions tab.

7 Click Push New.

8 Click Next on the wizard’s startup window.

9 When Choose Subscribers appears, select the “subscriber” server in the Enabled Subscribers group.

10 Click Next.

11 Check that the Subscription Database Name is DVM and then click Next.

12 When Set Merge Agent Schedule appears, click Change and set the properties as follows:

• Occurs Daily

• Every 1 day(s)

• Occurs every 1 minute Starting at 12:00:00AM Ending at 11:59:00PM

• Start date: current date

• No end date

13 Click Next.

14 When Initialize Subscription appears, select No, the Subscriber already has the schema and data and then click Next.


424 Release 200

15 When Set Subscription Priority appears, select Use the Publisher as a proxy for the Subscriber when resolving conflict and then click Next.

16 Check that the SQLServerAgent is running and click Next.

17 Click Finish.

18 When the wizard has finished, choose Replication Monitor Group> Agents > Snapshot Agents.

19 Right-click DVM in the right pane and choose Start Agent.

20 Wait till the agent has started (“A snapshot … was generated” appears in Last Action.)

21 Choose Replication Monitor > Agents > Merge Agents.

22 Right-click DVM in the right pane and choose Start Agent.

23 Wait till the agent has started.

24 Exit SQL Server Enterprise Manager.

Re-synchronizing the date and time on the servers


Re-synchronizing the date and time on the serversThe Time Service synchronizes the system time with the preferred time source server every hour.

If you change the time on the preferred time source server (or if it has been down for time), and you want all other computers to synchronize immediately, you need to stop and restart the Time Service on each computer.

To re-synchronize the time:1 Choose Start > Settings > Control Panel.

2 Double-click Administrative Tools and open Services.

3 Right-click on the Windows Time service and select Stop.

4 Right-click on the Windows Time service again and select Start.


426 Release 200

Viewing basic information about your Honeywell DVM system

The About display shows basic details about your Honeywell DVM system.


To view the license details:1 Navigate to the Honeywell DVM pages.


3 Click the About tab.

Property DescriptionVersion InformationVersion The version of Honeywell DVM you use.

Host InformationHost Name Either:

• The name of the EBI or Experion server if Honeywell DVM is used in conjunction with EBI or Experion

• <None> if Honeywell DVM is not used in conjunction with EBI or Experion

General License InformationCameras The number of cameras licensed for your system.

IE Clients The number of Internet Explorer clients licensed for your system.

Redundancy Indicates whether Database Server redundancy is licensed for your system.

Video Analytics License InformationPremium Algorithm Indicates whether the premium algorithm is licensed for

your system.

Object Tracking Algorithm The number of cameras licensed to use the object tracking algorithm.

Object Tracking and Classification Algorithm

The number of cameras licensed to use the object tracking and classification algorithm.

Stationary Object Detection Algorithm

The number of cameras licensed to use the stationary object detection algorithm.

Viewing basic information about your Honeywell DVM system


Third Party License InformationThird Party Licenses Click View Licenses to see the license details for third

party products used by Honeywell DVM for specialized tasks, such as video compression.



428 Release 200

Changing the Honeywell DVM license This section describes how to change the Honeywell DVM license.

Prerequisites• The new Honeywell DVM license.

Considerations• If you have a redundant server system, you have to perform this procedure on

each Database Server.

To change the Honeywell DVM license:1 Log on to the Database Server as a Windows Administrator.

2 Choose Start > Run.

3 Type regedit and click OK.

4 Locate the key:HKEY_LOCAL_MACHINE\software\Honeywell\DVM\Server

5 Double-click System Number, enter the System Number and click OK.

6 Double-click Authorization Key, enter the Authorization Key and click OK.

7 Exit the Registry.

8 Restart all Database and Camera Servers.


9Troubleshooting

This chapter describes how to use the Performance Monitor and open the log file. It also describes how to overcome common problems.

To: Go to:Use the Performance monitor page 430

Configure the Engineering log page 435

Troubleshoot common problems page 437

Troubleshoot EBI or Experion integration page 444

9 – Troubleshooting

430 Release 200

Using the Performance MonitorYou use the Performance Monitor to check a range of information, including:

• Camera status

• Requested and sent frame rates

• Frame sizes received by the Camera Server

• Network traffic (some network cards support this feature)

The following procedure describes how to add a camera parameter, such as Measured frames per second to the Performance Monitor chart. For more information about the Performance Monitor, refer to its Help.

You can add a camera parameter (page 430) or a playback parameter (page 431) to the Performance Monitor.

To open Performance Monitor:1 In Windows, select Start > Run.

The Run box appears.

2 Type perfmon and click OK.The performance monitor appears.

Adding a camera parameter to the list

To add a camera parameter to the list:1 Click the “+” icon on the toolbar to open the Add to Chart dialog box.

2 Click Select counters from computer.

3 Either select a Camera Server from the list or type the name of the Camera Server the camera belongs to.

4 Select DVM Camera from the Performance object list.

5 Click Select counters from list and select the required counter.The following table describes the Honeywell DVM Camera counters.

Counter DescriptionCurrent camera status Current camera status may be 0 (disabled), 1 (enabled),

2 (connecting), 3 (failed), 4 (disconnecting).

Frame size (bytes) Frame size is the average number of bytes per frame during the last sampling period.

Using the Performance Monitor


6 Click Select instances from list and select the instance.

7 Click Add then click Close.

8 Right-click on the counter and select Properties to open the System Monitor Properties dialog box.

9 Change the properties as required, click Apply then click OK.

The camera parameter appears in the chart.

Adding a playback parameter to the list

To add a playback parameter to the list:1 Click the “+” icon on the toolbar to open the Add to Chart dialog box.

2 Click Select counters from computer.

3 Either select a Camera Server from the list or type the name of the Camera Server the camera belongs to.

4 Select DVM Playback from the Performance object list.

5 Click Select counters from list and select the required counter.The following table describes the Honeywell DVM Camera counters.

Measured bandwidth (Kbps) Measured bandwidth is the bandwidth at which frames were streamed from the digital camera.

Measured frames per second Measured frames per second is the rate at which frames were streamed from the digital camera.

Measured packets per second Measured packet rate is the rate at which packets are being read from the streamer.

Recorded bandwidth (Kbps) Recorded bandwidth is the bandwidth that was requested to be stored to disk.

Recorded frames per second Recorded frames per second is the frame rate that is currently being recorded to disk.

Recorded packets per second Recorded packets per second is the packet rate that is currently being recorded to disk.

Requested bandwidth (Kbps) Requested bandwidth is the bandwidth that was requested of the digital camera.

Requested frames per second Requested frames per second is the frame rate that was requested of the digital camera.

Counter Description


432 Release 200

6 Click Select instances from list and select the instance.

7 Click Add then click Close.

8 Right-click on the counter and select Properties to open the System Monitor Properties dialog box.

9 Change the properties as required, click Apply then click OK.

The playback parameter appears in the chart.

Adding a new counter logYou may want to create a new counter log and add the variables to that log. Creating a new log enables you to record the performance of a system, and to load the performance statistics into the System Monitor.

Counter DescriptionCurrent playback speed Current playback speed is the ratio of playback

frame rate to the recorded frame rate.

Current playback status Current playback status may be 0 (paused), 1 (forward play), 2 (reverse play).

Measured frames per second Measured frames per second is the rate at which frames were streamed from the Camera Server.

Measured playback packets per second

Measured packet rate is the rate at which packets were streamed from the Camera Server as specified on the Camera Definition tab.

Using the Performance Monitor


To add a new counter log in Windows 2000:1 From the Windows Start menu, select Run.

The Run dialog appears.

2 Type perfmon and then press ENTER.

3 From the left-hand pane, right-click on Counter Logs, and select New Log Settings.The New Log Settings dialog appears.

4 Enter the name of your counter log.The log file configuration window appears.

5 Click the Add button.

6 Select the target computer from the Select counters from computer.

7 Select the target Performance object. (Look for DVM Camera, DVM Camera Manager Server, DVM Camera Server, etc.)

8 Either select All Counters, or, holding down the Ctrl key, select all the individual counters you want recorded.


10 Click the Close button.

11 Click OK.

The new counter log immediately begins collecting data.

To add a new counter log in Windows XP and Windows 2003:1 From the Windows Start menu, select Run.

The Run dialog appears.

2 Type perfmon and then press ENTER.

3 From the left-hand pane, right-click on Counter Logs, and select New Log Settings.The New Log Settings dialog appears.

4 Enter the name of your counter log.The log file configuration window appears.

5 Click the Add Counters button.

6 Select the target computer from the Select counters from computer.

7 Select the target Performance object. (Look for DVM Camera, DVM Camera Manager Server, DVM Camera Server, etc.)

8 Either select All Counters, or, holding down the Ctrl key, select all the individual counters you want recorded.


434 Release 200


10 Click the Close button.

11 Click OK.

The new counter log immediately begins collecting data.

Configuring the Engineering Log


Configuring the Engineering LogThe Engineering Log records events and error messages that can help you solve problems.

The default filename of the Engineering Log is DVM.log and its default location is as follows.

You configure the Engineering Log using hwdvslogconfig.exe, which is located in the following folders.

You can configure the following aspects of the Engineering Log:

• Basic settings, such as the log’s name, location and maximum file size.

• The paranoid levels. Each paranoid relates to a Honeywell DVM sub-system and determines what is included in the Engineering Log. The levels range from 0 to 100, the higher the level, the more information is captured in the log. The default is 10.

To configure the Engineering Log:1 Navigate to and then double-click hwdvslogconfig.exe.

2 Click Modify.

3 Change the log settings and paranoid levels as appropriate.

AttentionThe Engineering Log is not the same as the audit log—the audit log contains an audit trail of user and system actions. See “Configuring the audit log” on page 332.

Computer Default locationDatabase and Camera Servers \Honeywell\digitalvideomanager\logs

Client computers \Honeywell\digitalvideoclient\logs

Computer LocationDatabase and Camera Servers \DigitalVideoManager\Bin

Client computers \DigitalVideoClient


436 Release 200

4 Click Save.If you made changes that require the DVM Logger Service to be restarted, a message will prompt you to restart the service.

5 Click OK and then restart the DVM Logger Service.

To restart the DVM Logger Service:1 Choose Start > Settings > Control Panel > Administrative Tools to open

the Administrative Tools dialog box.

2 Double-click Services.

3 Right-click DVM Logger and choose Restart.A message appears informing you which other services will also be restarted.

4 Click Yes to restart the services.

5 Close the Services dialog box and then close the Administrative Tools dialog box.

Common problems


Common problemsThis section describes how to solve common problems. They are categorized as follows:

• General problems

• Problems specific to CS-3001V video

• Problems specific to audio

• Problems specific to EBI or Experion integration


438 Release 200

General problems

Text does not appear in displaysIf the text labels do not appear on the displays, restart IIS on the Database Server.

To restart the Web site:1 On the Database Server, choose Start > Control Panel > Administrative

Tools > Internet Service Manager.

2 Right-click on the computer name and select Restart IIS.

3 Click OK when the dialog is displayed and wait for IIS to be restarted.

4 Once IIS has restarted, go to the client and start Internet Explorer.

5 From the Tools menu select Internet Options.

6 Click the Delete Files button on the General tab.

7 When the Delete Files dialog box appears, click OK then click OK again to close the Internet Options dialog box.

Video quality changes erraticallyIf the video is not streaming smoothly, check the network cards are set to full duplex and you have the latest network drivers installed.

Cannot see live videoIf you cannot see live video from a camera, try the following:

1 Ping the camera. If you receive time-outs then the network may not be properly configured.

2 Navigate to the streamer Web pages. Check whether video can be streamed directly from the streamer Web pages.

Cannot record video for a cameraIf the camera will not record, check the following:

1 Make sure that there is sufficient disk space on the Camera Server.

2 Check the area of the hard drive that you are recording to is NTFS.

Common problems


Cannot access Honeywell DVMYou get the following message when you attempt to access Honeywell DVM:

You do not have permission to access DVM.

If you received this message when you attempted to access the Honeywell DVM Web site, check the following:

1 Check all Windows accounts and passwords have been configured correctly. For more information about security, see “Giving users access to Honeywell DVM” on page 394.

2 If account names and passwords were changed, reboot the computers the changes were made on.

3 Make sure the Honeywell DVM client was installed after Station was installed.

Text is in English instead of in your languageIf text is in English instead of the specified language, check the following:

1 The version of Honeywell DVM installed on your system is an internationalized version.

2 The appropriate language pack has been installed on the server and client computers.

3 Restart the Web server. See “Text does not appear in displays” on page 438, for details.

Recording icon does not appear on a live viewIf the recording icon does not appear on a live view, check you have specified record for on the Recordings tab for user-activated recordings.

Live video mouse PTZ controls do not appearCheck whether the camera supports continuous PTZ.

Video does not appear in quad viewIf the video does not appear, check the camera is in an area that the operator is allowed to view.

Zip file is not created when attempting to package exported files into a single zip fileIf the Honeywell DVM client has recently been installed, try closing and restarting Internet Explorer client or rebooting the Honeywell DVM client computer.


440 Release 200

Cannot view live videoWhen you attempt to view live video, you get the following error message.

The camera is unavailable due to problems with the camera’s server

Check the following:1 Check that the camera service on the camera’s Camera Server is running.

2 If Honeywell DVM is configured to work in a workgroup environment, add the IP address and name of all Database and Camera Servers to the following hosts files:

- Camera Servers

- EBI or Experion servers

- Stations

- Internet Explorer clientsFor details, see “Updating the hosts file” on page 240.

Live video window is blank except for a “no video” messageA “NO VIDEO” message appear in the live video window.

Some streamers (such as Axis 241S and Axis 241Q) notify Honeywell DVM when they detect video loss. In such cases, Honeywell DVM changes the camera icon in the Navigation Pane to the failed camera icon.

To restore the camera to operation, find out why the streamer detects no signal from the camera.

Recorded video window is blank except for a “no video” messageAfter performing a search, you find that some clips are black and display the “NO VIDEO” message. This means that the camera failed during recording, but recording continued despite the failed camera.

Camera continues to move after the last controlThis can occur on cameras that do not support, or have not been wired for, duplex communications.

To fix the problem you need to change the value of the CommandRepeat field in Honeywell DVM Database. The value specifies how many times Honeywell DVM repeats the last sent command. Generally, the last sent command is the stop command—in which case, the camera is instructed to stop the camera movement multiple times.

Common problems


To change the CommandRepeat field on the Database Server:1 On the camera’s Camera Control tab, clear the Receive Data Enabled check

box.

2 On the Database Server, choose Start > Programs > Microsoft SQL Server > Enterprise Manager.

3 In the Console Tree, double-click Microsoft SQL Servers > SQL Server Group.

4 Expand the name of the Database Server in Databases > DVM > Tables.

5 Right-click tblCamera and choose Open Table > Return All Rows.

6 Select the row for the camera which is having problems and press END.

7 In the CommandRepeat box for that camera, enter a value greater than 1.

8 Test whether the problem still occurs. If it does, increase the value again.


442 Release 200

Problems specific to CS-3001V video

Video window is black, and clicking the Record button seems to work, but no video is recordedCheck that your video signal works and is not simply a black video stream by making sure it is focused correctly and shows the images you expect.

Check that you have enough video RAM on your client computer. The CS-3001V requires that you have at least 16MB of video memory on your video card.

The camera does not fail when the video cable is pulled out of the CamStationPulling the video cable out of the CamStation streamer should cause the camera to fail in Honeywell DVM. Check that the 75ohm resistance is set to ON.

Sporadic bursts of colorful blocks appear in the videoThe CS-3001V streamer is sensitive to video signals, and any voltage surge or voltage imbalances can cause the video image to become “blocky” with various colors (usually pink, green and purple).

Test the CS-3001V streamer on an isolated system to ensure that it is not the streamer that is faulty. If you find that image “blockiness” and various colors do show up – try shielding the electronic equipment and check that the power supplies and other equipment are not faulty.

Video on the CamStation is very jerky, even at low resolutionsThe CS-3001V streamer may have difficulty handling high-resolution images (4CIF and D1) when the scene is complex and full of motion. This is because it is unable to process the large amount of data in this particular case. So this jerky effect on the video can be normal in certain situations.

If you are finding the images are extremely jerky or are still jerky at low resolutions (CIF or 4CIF Expanded) then it could be the network that is the problem. The first thing to do is monitor the amount of collisions happening on your network. The simplest test is to see if the port on the network switch that the CamStation is connected to is flashing orange or indicating that there are collisions. Please refer to the “Network” section of the CS-3001V User Guide for possible causes of this and possible remedies to this situation.

Common problems


Problems specific to audio

Cannot to hear audioCheck that the audio source is an amplified signal. You can test this by increasing the volume of the audio source or connecting another device, where it is known that the signal is amplified.

Try playing audio from Windows Media Player to verify that the Windows operating system on the client is capable of playing audio signals. When this is confirmed, try going to the Honeywell DVM pages again.

Loud squealing when listening to audioThis is most likely caused by audio feedback. Position the microphone further away from the speakers and/or reduce the output volume.

Audio is unclear with a lot of noise/staticAdjust the volume of the audio source to ensure that the audio levels are not too high.


444 Release 200

Problems specific to EBI or Experion integration

Error messages related to Honeywell DVM are being raisedYou see one or more of these error messages in Station:

Unable to contact DVM server. The server may be down.

orError initializing DVM

If you receive either or these error messages, check the following:

1 Check that the Windows accounts and passwords have been set up correctly. See “Windows security” on page 96.

2 Close and restart Station.

Event-activated recording does not work correctly

Check the following:1 Check that the following items associated with the event belong to the same

area:

• The point that triggered the event

• The camera that records in response to the event

• The Station or Internet Explorer client computer used when attempting to view the recorded video

• The operator who wanted to view the recorded video

2 Make sure that the point has been configured correctly. See “Configuring event-activated recording” on page 335.

3 Check that the data and time on the Honeywell DVM and EBI or Experion servers are synchronized. See “Synchronizing the date and time on the servers” on page 222.

4 Check that the Windows mngr account exists on all Honeywell DVM Database Servers and Camera Servers, and that it uses the same password as used in EBI or Experion Server. (The password for this account must be the same throughout your system.)

Common problems


5 Check that evtact is running on the EBI or Experion server by typing the following in a Command Prompt window: Usrlrn -a -pThis lists all the tasks that are running on the server.

6 If evtact is not listed, start it by typing: addtsk evtact 181(181 is the LRN reserved for used by evtact.)

Cannot see a video clipSee “Event-activated recording does not work correctly” on page 444.

Cannot access Honeywell DVMYou see the following message:

Unable to contact DVM server. The server may be down.

There are two possible causes:

• Honeywell DVM may not have been correctly installed on the client computer. Check the setup by clicking the DVM icon in the Station System Menu display. If an error occurs, reinstall the client as specified in “New installation checklist” on page 204.

• Security between Station, EBI or Experion server and Honeywell DVM servers has not been correctly configured. Check whether:

- Windows accounts have been correctly configured. See “Windows security” on page 96.

- If you use operator-based security, it may not be correctly configured. See “Giving a user access: operator-based security with integrated accounts in a workgroup environment” on page 400.

- If you use Station-based security, Station may not be correctly configured. See “Giving users access to Honeywell DVM” on page 394.

The video window is blank, without an error messageThe operator does not have access to the area in which the alarm was generated. (The operator may have an adequate security level to view the alarm, but does not have access to the area in which the alarm was raised.) See “Event-activated recording does not work correctly” on page 444.


446 Release 200


Index

Aaccess points, configuring event-activated

recording 335access to Honeywell, giving 394accounts, Windows

specialized Honeywell DVM 98user 394

administration 393alarm monitor cycle time, configuring 342algorithms

motion detection 125object tracking 125object tracking and classification 125

architecture, system 16archiving

configuring off-line storage 417preventing 390

areas (assets), described 93assets (areas), described 93audio

adjusting for live and recorded video 381configuring Axis 2191 Audio Module 349configuring Axis streamers 348configuring CamStation CS-3001V 351

audit logaudited events 412configuring 332exporting 411

Axis 2191 Audio Module, configuring 349Axis streamers, configuring for audio 348

Bbandwidth requirements

audio 90calculating 33

factors affecting 27video 35

CCamera Servers

described 16, 108disk usage, viewing 422requirements for 108viewing the status of 421

camera streamerscapabilities of supported types 120described 16support for 115

camerasadding 290configuration tabs

Camera Control 299Camera Definition 291Recording Presets 295

configuring 290controls 364disabling and enabling 365requirements 114streamers 115symbols in the Navigation Pane 370types of 114viewing its video 360, 362

cameras, guidelines for video analytics 146CamStation CS-3001V, configuring for

audio 351checklist for implementing video analytics 144configuration tasks 287controls and indicators

audio 381live video 364mouse PTZ 367numeric keypad 391

448 Release 200

Index

playback 375custom applications, writing 111

DDatabase Servers

described 16, 108redundancy 109requirements for 108viewing the status of 420

design and planning of Honeywell DVM system 19

digital certificatechecking correct installation 344configuring 343configuring third-party digital certificate 345installing a third party certificate 343

disabling a camera 365disk space administration, configuring 333displays, described 18domain security 96

EEBI

described 17integration issues 17, 91server 16

enabling a camera 365error log 435event-activated recording, configuring 335events that are audited 412Experion

described 17integration issues 17, 91

exporting video and audit logs 411

Ggroups, Windows

specialized Honeywell DVM 98

Hhardware and software requirements 116Honeywell DVM installation account,

described 217Honeywell DVM license

changing 428viewing 426

Honeywell DVM Object Model 111Honeywell DVM version, viewing 426

Iimage complexity, described 28installation

camera streamers 242checklists

described 202top-level 204

PTZ cameras 271start here 201

integration with other productsEBI 17Experion 17

intercom, videosupport for 113using 379

Kkeypad, using the numeric 391

Llicense, Honeywell

viewing 426license, Honeywell DVM

changing 428lighting guidelines for video analytics 148logs

audit 332error 435

Index


Mminimum object size (MOS), described 126motion detection

configuring 314symbols 371

motion detection algorithms 125Motion JPEG, described 30mouse, using to control PTZ camera 367MPEG, described 30multicasting 24multi-monitors, configuring 340

Nnetwork cameras, described 114networks

architectureconventional 22dedicated 23types of 22VLAN 23

designissues 21tips 26

management 25numeric keypad, using 391

Oobject tracking algorithm 125object tracking and classification

configuring 322symbols 371

object tracking and classification algorithm 125operation (using Honeywell DVM) 359operator-based security

described 95overview of Honeywell DVM 15

Ppan and tilt, using 365performance monitor 430planning and design of Honeywell DVM

system 19points, configuring event-activated

recording 335presets

adding 369defining special 346described 369recordings 295using 369

privacy zonesconfiguring 303described 369

PTZ controls 367

Qquad views

creating 309described 287viewing 377

Rrecorded videos

presets 295scheduling 306searching 383viewing 373

recording controls 364redundancy, Database Servers 109region of interest (ROI), described 126regions of interest

defining for motion detection 314defining for object tracking and

classification 322described 371symbols 371

restoring archived video clips 418resynchronizing redundant Database Servers 423

Sschedules

creating 306deleting 308

450 Release 200

Index

scripting 111searching recorded videos 383, 387security

levels 100managing users 394types of 95Windows 96

sequencescreating 311viewing 378

serversCamera 108Database 108Video Analytics 128

snapshotslocating 372recording 364specifying the folder for 331

software and hardware requirements 116special presets

defining 346described 369

Station-based securitydescribed 95

Stationsdescribed 17requirements 92

status points, configuring event-activated recording 335

storage requirementsaudio 90calculating 31factors affecting 27video 35

symbolscamera 370video analytics 371

Ttime and date, resynchronizing 425tours

configuring 304described 369

using 369transmission techniques 24troubleshooting 429types of 125

Uunicasting 24uninstalling Honeywell DVM 283upgrades

checklistsdescribed 202top-level 213

planning 279start here 201

user interface, Honeywell DVM 18users, giving access to Honeywell DVM 394

Vversion of Honeywell DVM, viewing 426video analytics

algorithms 125basic characteristics 131choosing between 130

configuring 313example scenarios 134guidelines for

cameras and streamers, choosing 145cameras, placing 150checklist 144field of view, adjusting 168introduction 123lighting 148MOS, defining 195ROIs, defining 177

introduction 124minimum object size (MOS), described 126region of interest (ROI), described 126symbols 371Video Analytics Server 128

video intercom 113configuring 354setting up Honeywell DVM 357

Index


video requirements 114videos

exporting 411preventing archiving 390preventing deletion 389searching recorded 383viewing live 360, 362viewing recorded 373

viewinglive video

Internet Explorer 362Station 360

recorded videos 373VLAN, described 23

WWindows accounts and groups

giving a user access to Honeywell DVM 394specialized Honeywell DVM 98

Windows security 96workgroup security 96

honeywell digital video manager user guide

Documents