Installation manual iProtect video

1

• Configuration

• Programming

• Procedures

• License plate recognition

• NVR-software functions

iProtect™ Video

Installation manual

Document date: 25-06-2018

2

Publication

June 2017

Keyprocessor BV

Paasheuvelweg 20

1105BJ Amsterdam

The Netherlands

www.keyprocessor.com

Tel.: +31 (0)2 04 62 07 00

This instruction manual is based on knowledge relevant at the above-mentioned date.

Keyprocessor is constantly working towards the improvement of its products. For information

on the most recent technological, please contact your consultant or distributor.

Table of contents

Publication .................................................................................................................... 1 Table of contents ........................................................................................................... 2 List of images ............................................................................................................... 4 1 Introduction ................................................................................................... 5 1.1 Version compatibility ................................................................................... 5 2 Configuration .................................................................................................. 7 2.1 Video network ............................................................................................. 7 2.2 Server ports ............................................................................................... 7 2.2.1 Camera pictures .......................................................................................... 7 2.2.2 Configuration data ....................................................................................... 8 2.2.3 PTZ control ................................................................................................. 8 2.3 Multiple locations......................................................................................... 8 3 Programming .................................................................................................. 9 3.1 Video server activation ................................................................................. 9 3.2 Browser settings ......................................................................................... 9 3.2.1 Google Chrome ........................................................................................... 9 3.2.2 Internet Explorer ......................................................................................... 9 3.3 Configuration in iProtect™ Aurora ................................................................. 10 3.3.1 Line configuration ....................................................................................... 10 3.3.2 Node configuration ..................................................................................... 10 3.3.3 System settings ......................................................................................... 11 3.3.4 Sense Network Video Recorder..................................................................... 11 3.3.5 Cameras in iProtect™ .................................................................................. 12 3.3.6 Camera preset in iProtect™ & Sense ............................................................. 13 3.3.7 Camera group ............................................................................................ 14 3.3.8 Multiview ................................................................................................... 15 3.3.9 Keymap .................................................................................................... 15 3.3.10 Actions ...................................................................................................... 16 4 Keybadge™ camera ........................................................................................ 18 4.1 Assignment of Keybadge™ camera ............................................................... 18 4.2 Use of Keybadge camera ............................................................................. 18 5 Procedures in case of Sense events .................................................................. 19 5.1 Sense camera input events .......................................................................... 19 5.2 ObjectR events .......................................................................................... 19 5.3 SceneR events ........................................................................................... 20 6 License plate recognition ................................................................................. 21

http://www.keyprocessor.com/

3

6.1 Requirements and initial steps ..................................................................... 21 6.2 iProtect™ Aurora setup ............................................................................... 21 6.2.1 License plate settings .................................................................................. 21 6.2.2 Card coding setup ...................................................................................... 22 6.2.3 Camera setup ............................................................................................ 22 6.2.4 Reader setup ............................................................................................. 22 6.2.5 License plate configuration .......................................................................... 22 6.3 Potential malfunctions ................................................................................. 23 7 Sense failover ................................................................................................ 24 7.1 iProtect™ settings ...................................................................................... 26 8 NVR-software functions ................................................................................... 28 8.1 Sense NVR ................................................................................................ 28

4

List of images

Figure 1: Video network diagram ..................................................................................... 7 Figure 2: Video architecture ............................................................................................ 8 Figure 3: Procedure ..................................................................................................... 13 Figure 4: Camera preset ............................................................................................... 13 Figure 5: Camera group ............................................................................................... 14 Figure 6: Multi-view ..................................................................................................... 16 Figure 7: group in a view .............................................................................................. 17 Figure 8: Scene rules ................................................................................................... 20 Figure 9: Failover settings ............................................................................................ 24 Figure 10: Advanced server settings .............................................................................. 25 Figure 11: Advanced settings menu ............................................................................... 25 Figuur 12: Advanced settings description ....................................................................... 26 Figure 13: Failover NVR changed to default .................................................................... 27

5

1 Introduction

The information in this manual is based on iProtect™ Aurora version 8.04. New features in

version 8.04 are:

• license plate detection before a vehicle has been registered on a detection loop

• support for Sense API 2.7.2

• support for five new Siqura camera series based on ONVIF.

• As an extra security feature, the default password for every camera must be changed

before pictures can be processed.

Note: If more than four camera displays should be viewed within the iProtect environment, a

Network Video Recorder (NVR) must be added to the iProtect™ server across the video

network.

Note: The management of the NVR-servers is affected by means of NVR-management

software (Sense of Milestone). If a connection with iProtect is desired, a difference in

functionalities between Sense and Milestone must be considered beforehand. Which software

has what functionality is described in chapter 6.

iProtect™ can control multiple NVR’s at different sites.

Connection to the Sense (previously DIVA) NVR is possible from the iProtect™ environment:

• Database version: iProtect™ Aurora 7.03

• GUI version: iProtect™ Aurora 7.03

Connection to the Milestone NVR is possible from the iProtect™ Aurora environment:

• Database version: iProtect™ Aurora 7.02

• GUI version: iProtect™ Aurora 7.02

1.1 Version compatibility

iProtect™ DIVA iProtect™ version DIVA version

DIVA 1 DIVA 2 API Comment

7.03 – 7.05 X X X

7.06 DIVA 1.17.8 DIVA 2.1+2.3 1.6.2

8.00 – 8.03 X DIVA 2.1+2.3 1.6.2

8.04 X DIVA 2.4+2.5 2.7.2

6

Common enrolling in iProtect™ Version 8.00 Version 8.01 – 8.03 Version 8.04 Comment

Enrolling DIVA cameras Yes Yes Yes In version 8.2 full or predefined

Enrolling DIVA layouts Yes Yes Yes In version 8.2 full or predefined

Enrolling DIVA pre-sets No (manual) Yes Yes In version 8.2 full or predefined

Enrolling DIVA macros No Yes Yes In version 8.2 full or predefined

Video in iProtect™ Version 8.00 Version 8.01 – 8.03 Version 8.04 Comment

Live video in JPEG format YES Yes Yes

Live video in H264 in iProtect™ format

No No No from DIVA 2.3.10 onwards DIVA encodes it to JPEG

Live video in H264 transcoded to JPEG in iProtect™

YES Yes Yes In DIVA setting is H264

Recorded video in JPEG format YES Yes Yes

Recorded video in H264 format

No No No

YES (from DIVA 2.3.10 onwards) DIVA encodes it to JPEG

Recorded video in H264 transcoded to JPEG in iProtect™

YES Yes Yes In DIVA setting H264

Events in iProtect™ Version 8.00 Version 8.01 – 8.03 Version 8.04 Comment

Connect/Disconnect from camera

No Yes Yes

Camera input No Yes Yes

Motion detection Yes Yes Yes

Trip wire / Virtual Fence No (only observation Tripwire)

Yes Yes

License plate recognition Yes Yes Yes

Face recognition Yes Yes Yes

Control Functions Version 8.00 Version 8.01 – 8.03 Version 8.04 Comment

PTZ Control on Diva camera Yes Yes Yes

Pre-sets Yes Yes Yes

Layouts Yes Yes Yes

Macros No Yes Yes Viewer + server

7

2 Configuration

2.1 Video network

Figure 1: Video network diagram

The office network, technical network and video network must be structured separately to

ensure sufficient bandwidth for the various connections.

2.2 Server ports

Two applications run in the iProtect™ GUI. The iProtect™ user interface application, which uses

a Tomcat server with port 8443 (HTTPS), and the iProtect™ maintenance interface, which uses

an Apache server with TCP-port 443 (HTTPS).

2.2.1 Camera pictures

Camera pictures can be sent to the iNVR, where they can be saved, either directly or via a

separate video server like Sense. The default port used by the cameras and video servers to

send pictures is TCP port 80. The iProtect™ GUI receives the pictures straight from the iNVR.

These can be live or saved pictures. The iNVR uses TCP port 4040 to send pictures to the

iProtect™ GUI.

8

Figure 2: Video architecture

2.2.2 Configuration data

The configuration data for the iNVR and associated cameras is communicated from the

database across the node manager. Communication between the node manager and the

database proceeds via a unique protocol using TCP port 20201. Events follow the same route

back and use TCP-port 20100. Communication between the node manager and the iNVR uses

TCP-port 19000.

2.2.3 PTZ control

PTZ camera control takes place directly via the iNVR or the Sense server. Communication

proceeds across HTTP TCP port 4040 to the iNVR and across HTTP TCP port 80 to the cameras.

If PTZ control takes place according to automatic procedures, these are sent to the iNVR

across port 19000 via the node manager.

2.3 Multiple locations

If cameras at various locations are connected to a single centre that houses the iProtect™

server, the network will be overloaded with camera traffic. In such a case, the iNVR can be

locally installed on a separate server, so that only pictures used by the iProtect™ GUI are sent.

A local controller (node manager) must also be installed for the transport of configuration data.

9

3 Programming

3.1 Video server activation

So that video can be used, this option must be activated on the iProtect™ server. If multiple

servers at different locations are used, both the GUI and the database must be supplied with

the same software version.

iProtect™ (GUI and database) server:

1. Browse the iProtect™ server; a login page will be displayed.

2. Click on the gearwheel to open the iProtect™ maintenance page.

3. Login with username “atlas”.

4. In the maintenance menu, select “iProtect™” and go to “Configuration”.

5. Select “Yes” for “Video” and click on “Save”.

6. Make sure that all users are logged out.

7. In the maintenance menu, select “iProtect™” and go to “General”.

8. Click on the “Restart user interface” button. The webserver will restart.

3.2 Browser settings

3.2.1 Google Chrome

Follow the below steps to enter the right settings:

1. Open the Google Chrome browser.

2. Go to “Menu” > “Settings” > “Advanced” > “Open proxy settings”.

3. Then go to “Security” > “Local intranet” > “Sites” > “Advanced”.

4. Enter the iProtect™ URL and the URLs of all video management servers.

Example

• https://192.168.1.1

• http://192.168.2.2 (Sense of Milestone NVR)

5. Click on “Close”.

6. Click on “OK”.

7. Under Local intranet, select “Modified level”.

8. Select “Access data sources across domains” and choose “Enable”.

9. Select “Display mixed content” and choose “Enable”.

10. Now click twice on “OK”, close the browser and restart it.

3.2.2 Internet Explorer

Follow the below steps to enter the right settings:

1. Open the Internet Explorer browser.

2. Go to “Tools” > “Internet options” > “Security” > “Local intranet”.

3. Select “Websites” and go to “Advanced”.

4. Now follow the steps as described in section 3.2.1 point 4.

https://192.168.1.1/

http://192.168.2.2/

10

3.3 Configuration in iProtect™ Aurora

3.3.1 Line configuration

1. In the iProtect™ Aurora menu, go to “Installation” > “Hardware” > “Line”.

2. Right-click on the line menu and select “Add line”. The details pane will open.

3. Give the line a practical name, such as “Camera server”

4. Select the following specifications

• Type : “Server”

• Mode : “Keyprocessor”

• Active : (mark field)

• Active (with nodes): (mark field)

• IP address : leave this field blank (local host)

5. Click on “Save”.

3.3.2 Node configuration


2. Click on the “Search” button.

3. In the browse window, right-click on the line to which the node should be added and select

“Add node”. The details pane will open.


• Node type : “iNVR”

• Max disk usage : 80 (recommended)

• Active : (mark field)

• HTTP port : 4040 (default value)

• IP address : the iProtect™ server IP address from which the server can retrieve

the pictures; From the video management server or directly from

the cameras.

• GUI IP address : the IP address from which iProtect™ clients should retrieve pictures.

During local use, the IP address used by the GUI to connect to the

server appears here. If an additional external connection is also in

place (e.g. across a router), a host name instead of an IP address

will appear. This name should also be configured in the local host

list in all clients; To do this, go to:

c:\windows\system32\drivers\etc\hosts and open it in notepad. At

the bottom of the list, add the IP address that you use to access

iProtect™ Aurora (can be a router address) and enter the same host

name as configured in iProtect™ Aurora.


11

3.3.3 System settings

1. In the iProtect™ Aurora menu, go to “Installation” > “Settings” > “General settings”.

2. In the browse window, click on the plus symbol in front of “Camera popup”.

3. Choose “Refresh picture (times/sec)”. The details pane will open, where a value from 1 –

25 can be allocated. The recommended number of pictures per second is 10.

4. Choose “Display play/stop buttons” and select “Value”.

5. Choose “Default width” and enter the desired width of the camera display screen.

6. Choose “Default height” and enter the desired height of the camera display screen.

7. Save your specifications.

NOTE System settings can be configured per system user. To do this, go to

“Installation” > “Authorisation” > “System user”

3.3.4 Sense Network Video Recorder

If a Sense Network Video Recorder (NVR) is used, the following steps must be followed:



3. In the browse window, click on the plus symbol in front of the line (Camera server) where

an NVR should be added. The node under this line will appear.

4. In the browse window, right-click on the node under which the NVR should be added and

select “Add network video recorder”. The details pane will open.

5. Give the line a practical name, such as “Sense NVR”


• Type : Sense

• IP address : The IP address of the Sense server

• Port : 80

• Name (NVR login) : The username of a user in Sense (user with full rights)

• New password : The password belonging to this user

NOTE The “Default” button can be used if the default login name and password are

used. The default credentials are iProtect / Root77. You are advised to create a

profile with username “iProtect” and password “Root77” and to grant full rights to

this profile.


8. Download and install the latest version of VDG Sense Setup from the VDG Security

website.

9. Open the Sense Client, select the “Sense manager” tab and go to “HTTP Server” >

“Advanced” and make sure that the API is set to 2.7.2.

10. Click on Import. All cameras and layouts in Sense will be imported to iProtect™ Aurora.

Choose the “Specify” option if you want to choose what to import. Here, Cameras,

Layouts, Pre-sets, Macros and Viewers can be selected and added.

12

3.3.5 Cameras in iProtect™

Cameras can be configured directly in iProtect™. In addition, the Milestone NVR server can

also be defined. If the cameras are controlled with a VDG Sense server, go to chapter 5.



3. In the browse window, click on the plus symbol in front of the line (Camera server) where

a camera should be added. The node under this line will appear.

4. In the browse window, right-click on the node under which the camera should be added

and select “Add camera”. The details pane will open.

5. Give the camera a practical name, such as “Camera entrance”


• Sub-number : Choose the desired sub-number; Camera 1 is sub-number 1

• Type : Choose the desired brand / type

• IP address : The IP address of the camera / Milestone server (client network)

• Port : 80

• Camera from group: The camera group that should be displayed in the Multiview if an

event is captured by this camera

• Before the event : The number of seconds before an event for which you want to see

pictures

• After the event : The number of seconds after an event for which you want to see

pictures

• On “Camera” tab

➢ Name : The username of the camera. In case of connection with Milestone,

enter the username of a Milestone user (with full rights) here

➢ Password : The password belonging to this camera or user

➢ Active : Mark ‘active’ field

➢ Check connection every: Here, specify at what intervals the connection should be

checked, e.g. every second

➢ Pictures : Here, specify the number of pictures per second, such as 5

pictures per second for a clear display that avoids system overload

NOTE The “Default” button can be used if the default login name and password are

used. The default credentials are iProtect / Root77. You are advised to create a

profile with username “iProtect” and password “Root77” and to grant full rights to

this profile.


8. If an ONVIF camera is used, it can automatically be located by the iNVR node.

13

3.3.6 Camera preset in iProtect™ & Sense

1. In iProtect ™ Aurora, select via the menu "Installation"> "Hardware"> "Camera">

"Camera"

2. Click the "Search" button.

3. Click with the right mouse button on the camera, on which the preset is to be set. Click

on "Add presetting". The details window opens.

4. Give the preset a logical description.

5. Place the camera in the desired position using the camera positioning.

6. When the camera position is correctly set, press the "Save" button.

7. This preset will now be stored in sense.

3.3.6.1 Default PTZ bij een lezer of Input

Since 9.00 we can determine the PTZ directly at the reader or input, without having to create a

procedure for each preset.

Requirement:

- Preferably a Dummy Camera with a preset below it as described above in chapter 3.3.6.

- That we have 1 manual procedure with the action "pantilt go to preset position", like

the following action:

Figure 3: Procedure

Then we can select the "camera preset" in the reader or input dialogue directly at the camera.

Figure 4: Camera preset

14

3.3.7 Camera group

A camera group makes it possible to display multiple camera pictures in the Multiview in case

of an event. A camera group consists of numerous cameras and/or camera split displays. In

case of an event, single camera pictures from the camera group, or a combination of pictures

from the camera group, can be displayed (see illustration).

1. In the iProtect™ Aurora menu, go to “Installation” > “Hardware” > “Camera” > “Camera

group”

2. Right-click on the camera group menu and select “Add group”. The details pane will open.

3. Give the camera group a practical name, such as “Cameras entrance”

4. Specify the number of rows and columns

5. Select the desired cameras from the “Camera / camera view” list.

6. The order of the cameras / split displays can be changed using the right-hand mouse

button.

Figure 5: Camera group

7. Example of a camera group (centre) with 2x3 camera pictures and split displays; In

‘Multiview’ (4x4 pictures in this example), the pictures from the group are either displayed

as single pictures (top-right), or combined into one display (top-left)

15

3.3.8 Multiview

A Multiview is a display of multiple pictures in a matrix consisting of rows and columns. The

number of rows and columns can be configured according to preference.

In the iProtect™ Aurora menu, go to “Installation” > “Hardware” > “Camera” > “Multiview”

and assign a practical name. Enter the desired number of columns and rows for the Multiview.

When “PTZ control” is activated, a PTZ symbol will appear at the bottom-right of the Multiview.

When you select a camera by clicking in the Multiview, you can change the camera’s focal

point with the PTZ control unit.

Using “Start-up camera group”, you can define the camera group that should display pictures

when the Keymap starts up or is reset. If you leave this field blank, pictures will only be

displayed in Multiview in case of events – Until events take place, only black fields will be

displayed.

If a Sense server is used, it is possible to link the Multiview visual to a Sense layout. This will

mean that the camera pictures are displayed in the same way in both iProtect™ Aurora and

Sense, e.g. 3x4 pictures with every picture in the same position.

In the iProtect™ Aurora menu, go to “Installation” > “Hardware” > “Line” and click on the plus

symbol in front of the NVR server in the left window. Then click on the plus symbol in front of

the node that appears and right-click on “Sense”.

In this way, an “external Multiview” can be configured or an existing external Multiview can be

selected. Then you can connect the Multiview in iProtect™ Aurora with a layout in Sense. In

the external Multiview, choose the iProtect™ Multiview and, in case of a new external

Multiview, the layout in Sense. Make sure that both have the same number of camera pictures.

In Sense, the Live and Playback panels can be used to drag pictures into the layout. In Sense,

always start with panel 1 and proceed to 2, 3, etc.

NOTE Do not rename the panels in Sense. This will disrupt the connection between

iProtect™ and Sense.

3.3.9 Keymap

The Multiview can be integrated into a background, or a different background image can be

used.

1. In the iProtect™ Aurora menu, go to “General” > “Settings” > “Keymap” > “Floorplan”.

The details pane will open.

2. Give the floorplan a practical name. Such as “Cameras entrance”

3. Specify the right height and width of the background image

4. Click on the “Preview” window. The “Show image” screen will appear

5. Select the desired image

6. Click on the “Save” button

7. Then click on the plus symbol in front of the floorplan. The “Position widget” pane will

appear.

8. Configure a Multiview by right-clicking on the “Position widget” details pane and then gong

to “Hardware” > “Camera matrix” > “View index”.

9. The right size can be specified with the mouse, or exact dimensions can be entered in the

“Widget size” tab.

16

3.3.10 Actions

There are two different actions to be completed, i.e. filling a Multiview with camera pictures or

carrying out an external action.

The appearance of pictures in Multiview forms part of an ‘action’. An action is initiated by an

event.

Go to “General” > “Settings” > “Action” and create a new record.

In “Select action”, you can choose from three Multiview variations:

• Multiview reset : Reset Multiview. If you have defined a start-up camera group,

the pictures from this group will appear. If a start-up camera

group has not been defined, the camera pictures will

disappear.

• Single-camera Multiview : Just the picture from the specified camera will be displayed.

• Camera group Multiview : All pictures from the camera group of the selected camera are

displayed.

Settings in the details pane:

Camera: Select the desired camera (from ‘Camera group Multiview’: a camera from the

desired camera group). If you leave this field blank, pictures will automatically be retrieved

from the camera assigned to the reader or event input.

Figure 6: Multi-view

Events (*) take place at a reader or input, to which a camera (1) can be assigned. You can

allocate the camera to a camera group (3). If you leave the ‘Camera from group’ field blank,

only the pictures from this camera will be displayed in the Multiview (2).If you specify a

camera group in the ‘Camera from group’ field, all pictures from this camera group will be

displayed in the Multiview in case of an event (4).Here, there are two options (see ‘display’).

Multiview : Define which Multiview should be associated with this action.

Display : Define whether the pictures should be display separately or as

group in a single field.

Display length (sec) : Enter the number of seconds over which the pictures should be

displayed. If you do not enter a value, the pictures will be

displayed constantly.

17

Figure 7: group in a view

Display. Left: group in a single display; Right: individual cameras.

It is also possible to carry out an external action (macro). This involves a server macro or

viewer macro configured in Sense. The macros must first be read into iProtect™.

Go to “General” > “Settings” > “Action” and create a new record.

From “Select action”, you can choose: “External procedure”, followed by the desired

procedure. In case of a viewer macro, you must also specify the viewer to which the action

applies.

18

4 Keybadge™ camera

The Keybadge™ camera is used to take photographs for access cards.

4.1 Assignment of Keybadge™ camera

To configure a Keybadge™ camera in iProtect™, a line (paragraph 3.3.1), a node (paragraph

3.3.2) and a camera (paragraph 3.3.5) must be in place.

1. In the iProtect™ Aurora menu, go to “Access” > “Keybadge™” > “Card layout”.

2. Right-click on the browse window and select “Add card layout”. The details pane will open.

3. Give the card layout a practical name.

4. By right-clicking on the card layout, a text, image or barcode field can be configured.

• If the text option is chosen, a “Text settings” tab will appear, in which default fields can

be selected or custom text entered.

• If the image option is chosen, an “Image settings” tab will appear, in which an image

can be loaded across the network, or a field for the card photograph can be defined.

• If the barcode option is chosen, a “Barcode” tab will appear, in which a choice can be

made from a number of default barcode types.

5. The result can be checked using the preview button.

6. In the iProtect™ Aurora menu, go to “Access” > “Keybadge™” > “Card template”.

7. Right-click on the browse window and select “Add card template”. The details pane will

open.

8. Give the card template a practical name.

9. In “Camera”, select the camera configured for taking of card photographs.

10. In “Card layout”, select the desired / configured layout.

11. Save your specifications.

4.2 Use of Keybadge camera

In the iProtect™ Aurora menu, go to “Access” > “Keybadge™” > “Card assignment”.

1. Click on Search and select the card template. The details pane will open.

2. A card photograph can be created and linked in the second tab of the “Photograph” details

pane.

19

5 Procedures in case of Sense events

In iProtect™ Aurora, you can set up procedures that will automatically trigger actions in

iProtect™ Aurora in case of events encountered by specific Sense cameras. The desired actions

will be assigned to the procedure.

5.1 Sense camera input events

A camera linked to Sense has an input to which a sensor or pressure switch can be connected.

Events that are generated can trigger actions in iProtect™ Aurora by means of a procedure.

You can configure such a procedure for a maximum of four camera inputs.

1. In the iProtect™ Aurora menu, go to “General” > “Settings” > “Procedure”.

2. Right-click in the browse window and select “Add procedure”.

3. Choose “Video event”.

4. Enter the following values:

• Data 1: “iNVR event type” Value 1: “Input”

• Data 2: “Number” Event 2: “1”

5. The actions added to this procedure will be triggered in case of an event taking place at

input 1.

5.2 ObjectR events

In Sense, there are six different Object events. They are characterised by the method (“Object

rule”) in which they are generated:

• Tripwire

• Area of interest

• Scene change

• Multi-tripwire

• Multi-segment tripwire

• Segment tripwire.

You can configure a maximum of five methods per camera/encoder. Every method is allocated

a “rule number” in the order of the configured methods.

iProtect™ Aurora takes over the events generated in Sense, but ignores the type of method.

Instead, events generated in Sense are characterised by the ‘rule number’.



3. Select the event: “Video event”.


• Data 1: “iNVR event type” Value 1: “Object detected with Sense”


• Actions associated with this procedure are therefore triggered by a “rule number” 1

event in Sense (regardless of the type of method).

http://212.123.221.51/command?command=streamEvents

http://212.123.221.51/command?command=streamEvents

20

5.3 SceneR events

There are four SceneR events in Sense, characterised by changes to the full picture. This can

be activated in Sense by marking an option.



3. Select the event: “Video event”.


• Data 1: “Event type” Value 1: “Scene detected with Sense”


• Actions associated with this procedure are therefore triggered by an event matching

Scene rule no. 1 in Sense.

• The Scene rule numbers can be “interpreted” as follows:

No. 1 SceneRCameraAngleChange Picture rotated in relation to previous picture.

No. 2 SceneRSceneLoss Picture not the same as previous picture.

No. 3 SceneRCameraAngleChangeRef Picture rotated in relation to reference picture.

No. 4 SceneRSceneLossRef Picture not the same as reference picture. Figure 8: Scene rules

Actions associated with this procedure are triggered when the picture rotates in relation

to the previous picture.

21

6 License plate recognition

iProtect™ Aurora can independently recognise license plates, but number plate recognition

across a connection with Sense video control software is also possible. If this is the case, the

cameras used for license plate recognition must also be controlled by a Sense video server

(NVR). Cameras connected directly to iProtect™ Aurora can only be used for recognition by

iProtect™ Aurora.

6.1 Requirements and initial steps

For effective license plate recognition, the following is necessary:

1. Make sure that a license plate recognition license is in place for every iProtect™ Aurora

camera (ID: 1100).

2. Make sure that infrared lighting has been installed.

3. Make sure that the camera used for license plate recognition has a resolution of at least

1.3 Megapixels.

4. A daylight filter should be used.

5. Mount the camera used for license plate recognition within a distance of 11 metres from

the license plate. The angle between the license plate surface and the camera must not

exceed 40°.

6. In iProtect™ Aurora, configure the camera picture in such a way that a regular vehicle in

the entrance fills the entire width of the picture.

6.2 iProtect™ Aurora setup

For license plate recognition via Sense, specific parameters must be set.

6.2.1 License plate settings

1. In the iProtect™ Aurora menu, go to “Installation” > “Hardware” > “Camera” > “License

plate recognition”.

2. Right-click in the browse window and select “Add license plate setting”. The details pane

will open.

3. Give the card template a practical name.

4. Enter 90% into the precision field.

5. Select the camera that should be used to read the license plate.

6. Click on “Save”. This completes the license plate setting.

In the Sense Client installation menu, go to the “Plugins” > “http server” > “Advanced” tab

and make sure that “Skip license timeout” is set to 5000.

22

6.2.2 Card coding setup

Open menu item “Access” > “Settings” > “Card coding” > “Card number presentation”

1. Configure a new Card number entry (right-click in the browse window on the left).

2. For “Format”, select: “License plate” and enter a length of “0” into ‘calculated length’ to

ensure a dynamic range.

3. Save the new card entry with a practical name (e.g. “License plate NL”).

4. Now go to the newly-entered card number in the tree view and configure Card number

interpretation (right-click in the browse window on the left).

5. For “Default card data interpretation”, select: “license plate”. Now click on “Set”.

6. Save the new card interpretation with a practical name (e.g. “License plate NL”).

6.2.3 Camera setup

Open menu item “Installation” > “Hardware” > “Camera” > “Camera”.

1. In the browse window, click on the camera used to recognise the license plate.

2. The “Camera” details pane will appear.

3. Open the “Others” tab.

4. Under “Card data interpretation”, select the configured card coding for the reading of

license plates.

5. Under “License plate recognition settings”, select the configured license plate setting.

6. Into the “Read license plate for loop” field, enter 100 ms.

7. License plate transactions can be activated by marking the field

6.2.4 Reader setup

Open menu item “Installation” > “Hardware” > “Reader”.

1. Select the reader that controls the boom at the entrance.

2. Under “General”, select the camera configured above.

3. Choose the 'Camera Access Mode' in the “Others” tab.

4. Go to the input/output tab and configure a loop.

6.2.5 License plate configuration

To iProtect™ Aurora, a license plate is a type of access card. As soon as the license plate

enters the camera’s field of vision, the vehicle/driver is granted access depending on access

rights. If you want to assign access rights to a certain license plate, you must add the license

plate as a card to the “card” menu element.

Open menu item “Access” > “Card”.

1. Configure a new card (right-click in the browse window to the left).

2. Under “Card number entry”, select the “License plate” previously configured as a license

plate entry.

3. Into “Card number”, enter the country code followed by a comma, then the license plate

number without any hyphens (e.g. “NL,11FGT9”).

4. Now enter the remaining details as you would for a regular card.

5. Mark the “Link card with card” field. This will prevent problems with APB or clocking

functions if, for example, someone enters an area using license plate recognition and

leaves it using a card.

23

6.3 Potential malfunctions

License plate not read

Sense license plate recognition:

• Make sure that the right version of Sense has been installed (≥ 2.3.8).

• Check the Sense settings.

• Check the positioning of the camera.

• Check the connection with iProtect™ Aurora. Are there live and historic camera pictures?

iProtect™ license plate recognition:

• Check the positioning of the camera.

• Check the camera license plate recognition settings.

• Check the camera connections. Are there live and historic camera pictures?

iNVR notification: error-111

Reason:

• The camera reader network device (iPU/Polyx) cannot access the IP address of the iNVR

node.

Solution:

• Open the iNVR node in iProtect™. Into “IP address” in the details pane (on the left), enter

the IP address of the server used by the line of the reader to which the camera for license

plate recognition has been assigned. Save your specifications.

No license plates numbers found

Check:

• Whether loop input has been configured for the reader.

• Whether license plate coding has been configured for the camera and whether license plate

recognition settings are correct (Others tab).

No picture

Check:

• For the line on which the iNVR server has been configured: Is the quality set to 100%?

• For the node on which the iNVR server has been configured: Is maximum disk usage set to

100%? The maximum setting is 90%.

• On the iProtect™ maintenance page, select iProtect™, and go to “Configuration”. The

status is displayed under “Video” in “Active Services”. This must be set to “Yes”. If this is

not the case, see chapter 4.1.

• Is the IP address of the GUI (node iNVR) the address (same IP series) set on the

workstation?

• Are the Internet Explorer settings correct?

24

7 Sense failover

This chapter consists of information from the VDG Sense Knowledge Base.

This chapter explains the function of the Failover tab. The Failover tab shows the list of

configured Failover servers on the left side, the list of monitored server of the selected Failover

server in the middle and the configuration of the selected failover server on the right side. In

the lower left corner of the screen are plus and minus buttons are there to add or remove

failover servers or to add and remove monitored servers.

See below for an example of a failover server and associated monitored servers, in this case

the failover server is monitoring two servers:

Figure 9: Failover settings

Setup

• Daily Backup

Enable or disable daily backup of settings. It is recommended to enable this setting as

this will ensure the Failover server always has the latest settings.

• UTC time

Time when the settings backup needs to take place

• Local time

This is a translation of the UTC time to local time

• Backup all servers

Do a settings backup of all server. If one or more servers are not available the Last

backup colon will show 'failed backup'.

• Automatically take over server

If enabled the failover server will automatically takeover the monitored server which

has failed.

• Automatically restore server

If enabled the failover server will automatically restore the original configuration when

the monitored server is restored.

• Take over server

Manually take over server, assuming it is offline

• Reset restored server

Manually restore server

• Advanced

Open dialog for Advanced failover settings, see below

https://vdgsecurity.com/downloads/manuals/

25

Figure 10: Advanced server settings

Advanced

In VDG Sense 2.4.24 and higher, you can modify the timeout settings for the failover server.

Click the 'Advanced' button, to open the following dialog.

Figure 11: Advanced settings menu

26

Type Default value Min. value

Max. value Decription

Connected 5 min. 5 min. 60 min. A network connection has

been made, but the first

startup message has not been

received

Started 5 min. 5 min. 60 min. The startup message has been

received, but the first keep-

alive message has not been

received

Keep alive 30 sec. 30 sec. 300 sec. No new keep-alive message is

received

Normal

shutdown

15 min. 5 min. 60 min. The server has been shut

down normally, but has not

restarted yet

Abnormal

shutdown

5 min 5 min. 60 min. The server has exited

with an error and has

not restarted yet Figuur 12: Advanced settings description

Storage

To access the recorded video data on the failover server, the monitored server needs to know

where to find it. This is done by adding a configuration parameter to the file ‘DivaServer.ini’ for

DIVA or 'SenseVideoManager.ini' for Sense, which can be found in the server settings folder.

The syntax of the configuration parameter is as follows:

[FailoverStorePath]

Value=<Failover server address><monitored server address>

For example, if the Failover server has IP address ‘192.168.204.151’ and the monitored server

has IP address ‘192.168.205.2’ the configuration option in DivaServer.ini/

SenseVideoManager.ini on the monitored server looks like this:

7.1 iProtect™ settings

The failover functionality of Sense is supported from iProtect version 9.01.

When a connection with the Sense server fails, iProtect automatically logs into the failover

server.

Open the “Network videorecorder details” dialog:

• Type : Sense

• IP address : IP-address of the Sense server

• Check connection : Connection check with Sense server

• Current address used : Where iProtect logs in

• Failover Netwerk Video Recorder : IP-address of the failover server

• Time-out before switching over : Duration of losing the connection / switching over

• Default : Back to the original state.

27

Example:

When a server (previously broken management server) brought back from repair and is

returned, it must be ensured that this server is provided with the correct (original) data.

Within iProtect, press the button "Default". iProtect will use the original IP address which is

entered in "Network video recorder details".

Figure 13: Failover NVR changed to default

28

8 NVR-software functions

8.1 Sense NVR

Except for events, all the functions which are described below is standard functionality in

iProtect™:

• Live and historic pictures

• Sense specification function

• Matrix control

• Pictures retrieved in local matrix as well as in Sense layout in case of an alert

• License plate recognition

• Pre-sets (control and specification in Sense)

• PTZ control

• Execution of macros

Documents

Installation manual iProtect video