cayuga r15 technical guides · 2020. 6. 4. · use also the username and password of sql server to...

CAYUGA R15

Technical Guides

Cayuga R15 Technical Guides Technical_Guides_Cayuga_R15_EN.docx

2

© Qognify GmbH

Table of content

I. Access Control ......................................................................................................................... 8

1. Continental Access Control CA3000 (Cayuga R6 or later) .................................................... 9

1.1. General Information ....................................................................................................... 9

1.2. Requirements and restrictions ....................................................................................... 9

1.3. Installation and Configuration of CA3000 ....................................................................... 9

1.4. Installation / Configuration in SeeTec ........................................................................... 15

2. Gallagher Command Centre ............................................................................................... 21

2.1. General Information ..................................................................................................... 21

2.2. SetUp Gallagher Command Centre ............................................................................. 21

2.3. Setup Video plugin ....................................................................................................... 21

2.4. Setup Middleware ........................................................................................................ 22

2.5. Setup SeeTec Cayuga Access Control Plugin ............................................................. 22

2.6. Gallagher Middleware Functionality ............................................................................. 22

3. Paxton Net2 Access Control (Cayuga R6 or later) .............................................................. 25


3.2. Requirements .............................................................................................................. 25

3.3. Installation / Configuration of SeeTec Cayuga ............................................................. 25

3.4. Configuration of alarm scenarios and buttons .............................................................. 26

4. Siemens SiPass integrated (Cayuga R4 or later) ................................................................ 28

4.1. Prerequisites / Important Information ........................................................................... 28

4.2. Installation and Configuration of SiPass ....................................................................... 29

4.3. Installation / Configuration SeeTec .............................................................................. 30

4.4. Access Control Data Editor .......................................................................................... 36

5. Connection to TDSi (Cayuga R4 or later) ............................................................................ 39


5.2. Configuration ............................................................................................................... 39

6. Siemens SiPort Integration (SeeTec Cayuga R3 or later) ................................................... 42


6.2. communication principle .............................................................................................. 42

6.3. Installation and configuration ....................................................................................... 44

6.4. Summary of the main points ........................................................................................ 47

7. Maxxess (SeeTec Cayuga R11 or later) ............................................................................. 49

7.1. System requirements ................................................................................................... 49

7.2. Required software packages, licences and features: ................................................... 49


3

© Qognify GmbH

7.3. Installation ................................................................................................................... 49

7.4. Installation SeeTec SDK .............................................................................................. 52

7.5. Add SeeTec Server to Viewpoint ................................................................................. 55

7.6. Troubleshooting & Remarks......................................................................................... 56

II. Intruder Detection ................................................................................................................... 58

1. Aritech Alarm Center Connection (Cayuga R4 or later) ....................................................... 59


1.2. IMPORTANT (Troubleshooting) ................................................................................... 59

1.3. Installation / Configuration ........................................................................................... 59

2. Connecting Siemens SPC Alarm Center using the EDP protocol (Cayuga R3 or later) ....... 62


2.2. Configuration ............................................................................................................... 62

2.3. Response to a dropped Connection ............................................................................. 69

2.4. User rights to send SPC commands ............................................................................ 69

III. PSIM (Physical Security Information Management) ............................................................ 70

3. Configuration of SeeTec Cayuga in MM8000 (Cayuga R3 or later) ..................................... 71

3.1. Important notes ............................................................................................................ 71

3.2. Requirements .............................................................................................................. 71

3.3. Configuration ............................................................................................................... 74

3.4. MM8000 Configuration ................................................................................................. 74

3.5. MM8000 Client ............................................................................................................ 80

4. SeeTec Connection to WinGuard (Cayuga R3 or later) ....................................................... 82


4.2. Important notes ............................................................................................................ 82

4.3. Requirements .............................................................................................................. 82

4.4. Installation of WinGuard ............................................................................................... 82

4.5. WinGuard Configuration .............................................................................................. 83

5. Honeywell WINMAG plus Integration (Cayuga R3 or later) ................................................. 88


5.2. Requirements / Important information .......................................................................... 88

5.3. Communication overview ............................................................................................. 88

5.4. Customize your WINMAG plus installation ................................................................... 89

5.5. SeeTec SDK installation .............................................................................................. 89

5.6. WINMAG plus interface configuration .......................................................................... 90

5.7. Import SeeTec Cayuga data ........................................................................................ 92

5.8. Driver Debug-mode ..................................................................................................... 93

5.9. CayugaViewer ............................................................................................................. 93

5.10. Troubleshooting ....................................................................................................... 94


4

© Qognify GmbH

5.11. WINMAG plus I/O device- & data point type definitions ............................................ 95

6. SeeTec Cayuga & Prysm AppVision ................................................................................... 97

6.1. SeeTec Cayuga SDK ................................................................................................... 97

6.2. Prysm Appvision .......................................................................................................... 97

IV. Edge Storage .................................................................................................................... 103

7. Edge Storage for Axis devices (Cayuga R4 or later) ......................................................... 104

7.1. Supported Axis cameras ............................................................................................ 104

7.2. Configuration on the camera ...................................................................................... 104

7.3. Speed settings for import ........................................................................................... 104

8. Edge Storage for Bosch devices (Cayuga R3 or later) ...................................................... 105

8.1. Supported Bosch cameras ......................................................................................... 105


9. Edge Storage for Samsung devices (Cayuga R7 or later) ................................................. 107

9.1. Supported Samsung Cameras ................................................................................... 107


9.3. Speed settings for import ........................................................................................... 108

V. Analytics & LPR.................................................................................................................... 110

10. Installing LPR Engines in SeeTec Cayuga .................................................................... 111

10.1. General Information................................................................................................ 111

10.2. Installation on 64-bit Operating Systems ................................................................ 111

10.3. Installation on 32-bit Operating Systems ................................................................ 111

11. LPR Expert Mode .......................................................................................................... 113

11.1. Enabling LPR Expert mode .................................................................................... 113

11.2. Supported properties .............................................................................................. 113

12. Cayuga Interface to BriefCam (from Cayuga R11) ........................................................ 117

12.1. Requirements ......................................................................................................... 117

12.2. Installation of BriefCam VMS Integration Plugin ..................................................... 117

12.3. Setup SeeTec ........................................................................................................ 125

12.4. Setup BriefCam ...................................................................................................... 126

12.5. Remarks & troubleshooting .................................................................................... 127

VI. VoIP & SIP / Audio Communication .................................................................................. 128

13. Installation / Configuration Brekeke PBX V3.x & SeeTec SIP (Cayuga R3 or later) ....... 129

13.1. Prerequesites ......................................................................................................... 129

13.2. Installation Brekeke PBX ........................................................................................ 129

13.3. Configuring the SeeTec client (extension) .............................................................. 131

13.4. Configuring the SeeTec server ............................................................................... 132

13.5. Audio functionality in Surveillance Mode ................................................................ 132

13.6. Audio functionality in Archive Mode ........................................................................ 133


5

© Qognify GmbH

13.7. Appendix ................................................................................................................ 134

14. Commend / Schneider Intercom ICX interface connection (Cayuga R4 or later) ............ 137

14.1. General information ................................................................................................ 137

14.2. Configuration .......................................................................................................... 137

14.3. Commend /Schneider Intercom devices in the SeeTec system .............................. 137

14.4. Alarm scenario configuration .................................................................................. 138

VII. Other ................................................................................................................................ 140

15. Virus Scanning & Firewalls ............................................................................................ 141

15.1. Virus Scanning ....................................................................................................... 141

15.2. Firewalls ................................................................................................................. 141

16. Flat File Logging (Cayuga R6 or later) ........................................................................... 142

16.1. Examples ............................................................................................................... 142

16.2. Recommendation ................................................................................................... 142

16.3. Enabling and configuring flat-file logging ................................................................ 142

16.4. System notification for flat-file logging errors .......................................................... 144

17. Customize Localization Tool (Cayuga R5 or later) ......................................................... 145

17.1. Preamble ................................................................................................................ 145

17.2. Requirements and restrictions ................................................................................ 145

17.3. Export neutral language resources ......................................................................... 145

17.4. Translate texts into customized language ............................................................... 146

17.5. Generate customized resources ............................................................................. 146

17.6. Import customized resources into Cayuga and activate language .......................... 146

18. SeeTec AlarmWatchDog ............................................................................................... 148

18.1. Notes ..................................................................................................................... 148

18.2. Configuration SeeTec Server ................................................................................. 148

18.3. Configuration / Operation Alarm Watchdog ............................................................ 149

19. SCCM Installation (Cayuga R3 or later) ......................................................................... 152

19.1. Preamble ................................................................................................................ 152

19.2. System requirements ............................................................................................. 152

19.3. General procedure call ........................................................................................... 152

19.4. Supported MSI Properties ...................................................................................... 152

19.5. Examples ............................................................................................................... 154

20. OPC Service (Cayuga R3 or later) ................................................................................ 156

20.1. Important notes ...................................................................................................... 156

20.2. Installation and Configuration Cayuga OPC Service .............................................. 156

20.3. Installation and Configuration OPC UA Server ....................................................... 157

20.4. OPC UA Server ...................................................................................................... 157

20.5. OPC Classic & OPC UA Tools ............................................................................... 161


6

© Qognify GmbH

20.6. MM8000 & Others .................................................................................................. 161

21. Reset installation ID (Cayuga R7 or later) ..................................................................... 163

21.1. General Information................................................................................................ 163

21.2. Resetting the installation id..................................................................................... 163

22. Cluster Installation (Cayuga R3 or later) ........................................................................ 164

22.1. Overview ................................................................................................................ 164

22.2. Prerequesites ......................................................................................................... 164

22.3. Installation / Configuration (Core Service MASTER Server or Core Service SLAVE Server) 164

23. Connection to eyevis Wall (Cayuga R3 or later) ............................................................ 173

23.1. Introduction ............................................................................................................ 173

23.2. About eyevis software and hardware ...................................................................... 173

23.3. Configuration and Integration ................................................................................. 174

23.4. Configuration of the eyecon software ..................................................................... 174

23.5. Configuration of the SeeTec software .................................................................... 175

23.6. Establish a connection between SeeTec and eyevis Wall ...................................... 177

23.7. Display camera-streams on the eyevis wall ............................................................ 179

23.8. Remarks & troubleshooting .................................................................................... 180

24. OPTEX – Cayuga interaction ........................................................................................ 181

24.1. OPTEX RLS 2020S ................................................................................................ 181

25. Vi3xx26 PoE switch - TCP Alert functionality ................................................................. 185

25.1. Tested Hardware .................................................................................................... 185

25.2. Configuration .......................................................................................................... 185

25.3. SeeTec configuration ............................................................................................. 186

26. PRTG Network Monitor ................................................................................................. 188

26.1. Installation .............................................................................................................. 188

26.2. Configuration .......................................................................................................... 188

Cayuga R15 Technical Guides

7

© Qognify GmbH

Changelog

Version Date Changes

1.0.0 14.12.2018 Release Version – added: PRTG, Interface to BriefCam, Maxxess,

Adjustments “Schneider Intercom”

1.0.1 07.01.2018 Adjustments of Winguard Installation


8

© Qognify GmbH

I. Access Control


9

© Qognify GmbH

1. Continental Access Control CA3000 (Cayuga R6 or later)

1.1. General Information

Continental Access Control (CA3000) is an access control system by Continental Instruments. Events which

are received from the access control system can be used to trigger alarm scenarios in SeeTec Cayuga.

1.2. Requirements and restrictions

▪ The system software of CA3000 version 2.9.88 must be installed and configured correctly before SeeTec

Cayuga can be installed.

▪ You also must install the CA3000 license file first.

Please refer the documentation of Continental Access Control for installation instructions.

1.3. Installation and Configuration of CA3000

1.3.1. CA3000 Software installation

▪ The CA3000 (CardAccess 3000) software is spitted into 3 parts:

▪ Database Server

▪ On this machine the Microsoft SQL Server is installed.

▪ Use the IP address of this machine to configure the ODBC data source (see below).

▪ Use also the username and password of SQL Server to configure the Cayuga module (see below).

▪ CA3000 Server

▪ Use the IP address of this machine to configure the Cayuga module (see below).

▪ On this machine the socket notification tool is running.

▪ (Optional) CA3000 Workstation

It is possible to install all components on the same machine. Please refer to the documentation of

Continental Access Control for recommendations.

http://www.cicaccess.com/


10

© Qognify GmbH

To install the software required for the access control system please follow the manufacturer-documentation

or ask your distributor

1.3.2. Configure the ODBC connection on the machine where the SeeTec Module is

running

▪ Make sure the port for the SQL Server (default 1433) is open.

▪ Create ODBC DSN name (On a 64-bit computer, you must use the odbcad32.exe in the SysWow64

folder.

▪ Go to C:\Windows\SysWOW64.

▪ Run odbcad32.exe.

▪ This will bring up the dialog box as shown below.

▪ Select tab System DSN.

▪ Click the Add button to create a new DSN name.


11

© Qognify GmbH

▪ In the next screen, select SQL Server driver. Click Finish.

▪ In the next dialog box, enter the DSN name CardAccess3000 and choose the SQL Server where the

cardAcccess3000 software database is installed.

▪ Click Next.


12

© Qognify GmbH

▪ In the next screen activate With SQL Server authentication… and enter the Login ID cic and

password Cic!23456789. (This is the default SqlExpress user name and password in CardAccess

3000 V2.8.2 and V2.9).

▪ Click Next.

▪ In the next screen, activate Change the default database to.

▪ Select the CardAcccess3000 live database from the dropdown list.

▪ Leave all other settings unchanged.

▪ In the Final screen keep all defaults settings

▪ Click Finish.


13

© Qognify GmbH

▪ The Test Data Source screen is shown

▪ Click Test Data Source

▪ TESTS COMPLETELY SUCCESSFULLY should be shown.

If there are any failures verify that all previous steps are configured properly.

1.3.3. Prerequisites to receive events in Cayuga

▪ Activate socket notification in the CardAccess 3000 software.

▪ Run CA3000 Launcher.

▪ Navigate to System → System Settings → Alerts.


14

© Qognify GmbH

.

▪ Enable Use Socket Alert Notify

▪ You can change the port for the socket notification optionally.

▪ Open the file

C:\Program Files (x86)\CardAccess3000\caSocketNotify.exe.config

with a text editor

▪ Change the port number (Default port: 9090)

▪ Run the socket notification server program

▪ Open the Windows Explorer and navigate to the folder

C:\Program Files (x86)\CardAccess3000

▪ Run the application caSocketNotify.exe as Administrator

▪ Let the program running continuously

Attention: If you close this window no events can received in SeeTec Cayuga anymore!


15

© Qognify GmbH

1.4. Installation / Configuration in SeeTec

▪ If you use another DSN name in the ODBC configuration (see previous pages). You must change it also

in the configuration file for the Cayuga ACS plug-in:

▪ Open the file

C:\Program Files\SeeTec\VersatileApplications\AccessControlPlugins\

SeeTec.ACSPluginContinental\

SeeTec.ACSPluginContinental.dll.config

with a text editor as Administrator

▪ Change the value for DSN in the connectionstring (use the same name as above) and save the file

▪ Extract the AccessControler Plug-In continental_x86.zip and copy the content into C:\Program

Files\SeeTec\VersatileApplications\AccessControlPlugins

▪ Create a Generic Access Control Module

▪ Open SeeTec VA Administration Tool on the machine where the module should run

▪ Add a new module: Generic Access Control


16

© Qognify GmbH

▪ Enter the correct Core server IP

▪ On x64 systems make sure the checkbox Enforce 32bit is enabled.

▪ Test the connection (Button Connection test)and click Save


17

© Qognify GmbH

▪ Configure the Generic Access Control Module in Cayuga

▪ Change to Configuration Mode and select

Server → [Name of the module you just created]

▪ Select the plug-in for Continental Access Control (CI CardAccess3000)

▪ Add the Access Control hardware to the SeeTec Cayuga Server.

▪ Open the SeeTec Client, change to Configuration Mode and create a new device, manufacturer:

SeeTec, Type: Generic access control


18

© Qognify GmbH

▪ The Host IP is the address of the machine where the Notification tool is running (this is the CA3000

Server)

▪ Change the username and password if necessary. These are the credentials of the SQL Server.

▪ The Port is the port of the Notification tool on CA3000 Server (Default if necessary). It must be the

same that is specified in the file

C:\Program Files (x86)\CardAccess3000\caSocketNotify.exe.config (see above).


19

© Qognify GmbH

After the new hardware is created the list of doors will be shown

▪ Create alarm scenarios

▪ Create an alarm scenario

As start trigger select the event for one or more access points (doors)

▪ In SeeTec Cayuga you can create alarm scenarios that are triggered by the access point events. The

mapping of the events is listed in the following table.

SeeTec Event Continental Event

Access denied Badge violate void

Badge violate time of day

Badge violate APB

Badge violate void at panel

Access granted Badge valid

Badge Entry

Badge Exit

Sabotaged Door is open to long


20

© Qognify GmbH

SeeTec Event Continental Event

Door forced open

State changed All other door state change events


21

© Qognify GmbH

2. Gallagher Command Centre


Based on the SeeTec Cayuga SDK, the interface between the Gallagher Command Centre and SeeTec

Cayuga contains the possibility of viewing video footage from SeeTec Cayuga in Gallagher Command

Centre, controlling PTZ cameras as well as selecting in Cayuga preconfigured preset positions using Cayuga

own player functionalities as well as using Gallagher Command Centre specific functionalities. Furthermore,

this interface contains a second component relied to the access control specific event types resulting from

the Gallagher Command Centre which are mapped on all currently available SeeTec event types offered by

the Cayuga Generic Access Control Interface. The event types coming from Gallagher Command Centre

containing [event type], [door ID], [Card ID] and [time stamp] are used in Cayuga for triggering so called

Alarm Scenarios.

2.2. SetUp Gallagher Command Centre

▪ Add new External System (In the Configuration Client: Configure/External System, right click →New →

External System).

▪ Setup tab

▪ “Controller”: Choose Controller that will relay the events.

▪ Input “Middleware PC Name/IP Address” of the machine that runs the middleware. (If it’s the same

machine that runs Gallagher Command Centre you cannot use “localhost”, it must be the IP address of

the machine. Command Centre has to be configured to be able to run the middleware on the same

machine as itself, please see the Gallagher documentation.)

▪ “Identity” has to match the “System Name” configured in the middleware. (see 0)

▪ Add new External System Item (In the Configuration Client: Configure/External System, right click →

New → External System Item)

▪ Setup tab

▪ “External System”: Choose the external system that was just created.

▪ “Identification” has to match the “Item Name” configured in the middleware (see 0)

▪ “Access Zone”: Choose the Access Zone of the doors that should fire events.

▪ Trigger – Events

▪ Input the following string:

▪ [Source:[ES]][Holder:[CH]] [Type:[ET]]

▪ [ES], [CH] and [ET] must be inserted through the “Event details” in the “Insertable Fields” box. Just copy-

pasting above string will not properly set up the Command Centre!

▪ Event Response tab

▪ “Alarm Zone for all Events”: Set alarm zone that will fire the desired events.

2.3. Setup Video plugin

▪ Unzip the archive „SeeTec.GallagherCCVMSPlugin.zip“ to directory.

“Gallagher Command Centre Install Directory}\Client\Plugins”


22

© Qognify GmbH

▪ In the unzipped folder run the batch script „gallagherCCVMSRegistration.bat“ (right-click, “Run as

administrator”).

This script adds entries for the video plugin to the windows registry and registers the SeeTecCCVMS.dll

assembly. Additionally, it moves the files

▪ WPFToolkit.dll”

▪ Xceed.WPF.Toolkit.dll

to directory “gallagher Command Centre Install Directory}\Client

Should the SeeTec SDK DLLs change, they have to be replaced in the plugin directory.

2.4. Setup Middleware

▪ Unzip the archive „STGMiddleware_v1.0.0.0_2017-09-12.zip” to a freely chosen directory. The

user running the Middleware must have read/write permissions to this folder!

▪ Set up the Middleware as per 2.6.4.

▪ If the Middleware does not run on the same machine as the Gallagher Command Centre server, the

license file of the server must be copied to the

C:\Windows directory of the machine running the Middleware

2.5. Setup SeeTec Cayuga Access Control Plugin

▪ On the Cayuga System unzip the archive SeeTec.ACSPluginGallagher_v1.0.0.0.zip

to “C:\Program Files\SeeTec\VersatileApplications\AccessControlPlugins\”

▪ Use the “SeeTec VA Administration Tool” to create a new Generic Access Control module

▪ On Cayuga client, go to Configuration Mode → Access Control

▪ Create a new device with the following configuration

▪ Access control module: The Generic Access Control module created in the previous step

▪ Username and password are unused for now

▪ Port: The port on which the plugin will listen for incoming Gallagher events

▪ IP: The interface the plugin will listen on (the local IP in most cases)

▪ Once the plugin is started, and the SeeTec-Gallagher middleware is running, the plugin will receive all

available doors and corresponding events automatically

▪ For further setup details please refer to the SeeTec Cayuga user manual

2.6. Gallagher Middleware Functionality

2.6.1. Main Application Window

Gallagher Command Centre

Shows the status of the connection to Gallagher Command Centre. Possible statuses:

▪ Not connected: No connection to Gallagher Command Centre. The connection is opened by the

Command Centre itself, the middleware can’t actively connect but waits passively for a connection.


23

© Qognify GmbH

▪ Connected (not registered): Connection to Command Centre established but the External System Item

is not registered with Command Centre. Registration is done by Command Centre itself, the middleware

can’t actively register but waits passively to receive the registration.

▪ Connected (registered): Connection to Command Centre is established and the External System Item

is registered with Command Centre.

After the connection to Command Centre is established the middleware tries to establish a connection to

SeeTec Cayuga.

SeeTec Cayuga

Shows the status of the connection to SeeTec Cayuga plugin. Possible statuses:

▪ Waiting for Gallagher: The middleware is waiting for the connection to Gallagher Control Centre to be

established before trying to connect to the plugin.

▪ Offline: No connection to the plugin can be established.

▪ Online (not configured): Connection to the plugin is established, but the plugin has not yet received the

door configuration.

▪ Online (configured): Connection to the plugin is established and the plugin has at some point received

a configuration. This does not guarantee that the received configuration and middleware configuration

match! The plugin has to be restarted to be able to receive a changed configuration.

▪ Online (error): Connection to the plugin is established, but there was an error sending events from the

middleware to the plugin. The plugin should be restarted.

Log

Shows the log of the middleware activity (connections, relayed events, etc.).

▪ Only show critical messages checkbox: toggles between showing all activity and showing only

irregular activity (errors, warnings, etc.)

2.6.2. Door configuration

Shows the doors that will be sent to the SeeTec Cayuga plugin for configuration.

▪ Multiple doors at a time can be added with the “Add” button, separated by a carriage return (enter key).

▪ Multiple doors can be selected (Shift + left mouse button / Ctrl + left mouse button) and removed with the

“Remove” button.

▪ The “Cancel” button dismisses any changes.

▪ The “Save” button saves the door list and prints the changes to the log window.

2.6.3. Match configuration

Shows the matches of event strings sent by Gallagher Command Centre to SeeTec Cayuga events. Matches

for the IGNORE event will not be relayed to the SeeTec Cayuga plugin.

▪ “Map default events to” allows for selection of the event that non-matched strings will be mapped to.

▪ With a specific event selected, the “Add” button allows for adding exact string matches to the selected

event.

▪ Multiple events can be selected (Shift + left mouse button / Ctrl + left mouse button) and removed with

the “Remove” button.

▪ The “Cancel” button dismisses any changes.


24

© Qognify GmbH

▪ The “Save” button saves the match list and prints the changes to the log window.

2.6.4. SeeTec/Gallagher configuration

Allows for plugin/middleware specific configuration.

Gallagher Command Centre

▪ “System Name” should match the Identity of the External System that is configured with the External

System Item in Command Centre.

▪ “Item Name” should match the Identification of the External System that is configured in Command

Centre to relay messages to the middleware.

SeeTec Cayuga

▪ “Host/IP” should match either the host name or the IP address of the machine running SeeTec Cayuga.

▪ “Port” should match the port configured in the SeeTec Cayuga Access Control device configuration (see

2.5). Depending on the machine this port may have to be opened in the machine’s firewall settings.

▪

2.6.5. Logging Configuration

Allows for configuration of the logging behavior.

▪ “Number of log files to keep” is the number of old log files that will be kept after the current log file is split.

▪ “Maximum file size in MB” is the size the current log file can reach before being split into a new file. On

reaching this limit a new log file will be opened, and the old logs saved.


25

© Qognify GmbH

3. Paxton Net2 Access Control (Cayuga R6 or later)


Paxton Net2 is an access control system by Paxton Access Ltd.

In SeeTec Cayuga events from the access control system can be used to trigger alarm scenarios and

buttons can be configured to control access points.

3.2. Requirements

To integrate the Paxton Net2 access control system in Cayuga, the Net2 Software and at least its server

component must be installed.

The recommended version of the software to use is Paxton Net2 Access Control V5.3.2818.3674.

For more information about the Paxton Net2 Software, e.g. hard- and software requirements or installation

instructions, please refer to the Paxton Net2 documents.

3.3. Installation / Configuration of SeeTec Cayuga

The following steps describe how to configure Cayuga to use a Net2 access control system:

▪ For x64 Systems extract the archive file paxton_x64.zip and copy the content into the directory:

C:\Program Files\SeeTec\VersatileApplications64\AccessControlPlugins

▪ For x86 Systems extract archive file paxton_x86.zip and copy the content into the directory:

C:\Program Files\SeeTec\VersatileApplications\AccessControlPlugins

▪ Create a Generic Access Control Module in the SeeTec VA Administration

▪ Configure the Generic Access Control Module in Cayuga

▪ Switch to Configuration Mode and select “Server” →[Name of the module you just created]

▪ Select the Paxton plug-in “Paxton Net2"

▪ Add the Access Control hardware to the SeeTec Cayuga Server.

▪ Open the SeeTec Client, change to Configuration Mode / Access control and create a new device,

manufacturer: SeeTec, Type: Generic access control

▪ As IP address enter the IP of the machine where the Net2 Software is running

▪ Configure the Access Control hardware

▪ Switch to Configuration Mode and select “Access Control” → [Name of the Access Control hardware you

just created]

http://www.paxton.co.uk/


26

© Qognify GmbH

▪ As Plugin select Paxton Net2

▪ Change the connection parameters (the default port of the Net2 Software is 8025)

▪ Change the authentication parameters:

The default username is depending on the language set in Net2 Software. If the language is English, the

default username is System engineer.

If the language is German, the default username is System-Techniker.

The default password is net2

▪ If the configuration of the Access Control Module and the Access Control Hardware is correct, all access

points will be listed.

3.4. Configuration of alarm scenarios and buttons

In Cayuga you can create alarm scenarios that are triggered by the access point events. The mapping of the

events is listed in the following table:

SeeTec Event Net2 Event

Access denied Access denied

Access denied with invalid card

Access denied with invalid PIN

Access denied with invalid code

Access denied with invalid license plate

Access denied with following lockdown progress

Access granted Access permitted

Access permitted with card only

Access permitted with card and code

Access permitted with PIN only

Access permitted with code only

Access permitted with license plate

(and if it is not sure that an access was made)

Access not taken Access permitted

Access permitted with card only

Access permitted with card and code

Access permitted with PIN only

Access permitted with code only

Access permitted with license plate

(and if it is sure that an access was not made)

Sabotaged Battery critically low

Door forced


27

© Qognify GmbH

SeeTec Event Net2 Event

Door open too long

Intruder alarm

Mains failed

Reader tamper

Tamper

State changed All other events

These events can be used in an alarm scenario. It is also possible to create SeeTec buttons that control

access point. The control possibilities are listed in the following table

SeeTec Control Net2 Control

Access Open a door temporarily. The time is configured

in the Net2 Software.

Unlock Open a door permanently.

Lock Close a door.


28

© Qognify GmbH

4. Siemens SiPass integrated (Cayuga R4 or later)

4.1. Prerequisites / Important Information

This document describes the interface between SiPass integration and SeeTec. It includes all necessary

steps to install and configure everything in SeeTec.

You should already have a SiPass server up and running prior to do the configuration on SeeTec side. For

more information about SiPass installation and configuration please refer to the SiPass documentation.

SeeTec implemented the SiPass Management Station API to retrieve events from SiPass. Every SiPass

event can be used within a SeeTec alarm scenario.

Please note that the communication between SiPass and SeeTec is unidirectional from SiPass to SeeTec.

The SiPass Client is only needed to check the connection between SeeTec Client and SiPass Server by

using the Management- / HR API (DCOM).

▪ SiPass integrated version 2.65 and above supported, if you have an older version installed an upgrade to

2.65 (Firmware and Software) will be necessary.

▪ SiPass integrated installation and configuration must be done prior to the SeeTec installation!

▪ SiPass requires the Management Station API license activated as well as one additional workstation

license is needed, for SeeTec the access control license is needed (this is included in Cayuga S100 and

higher).


29

© Qognify GmbH

▪ SiPass integrated needs the Microsoft .NET Framework 4.0 (shipped with the SiPass CD and installed

automatically if necessary).

▪ The SiPass Client has to be installed on the system where DM/MDB will be installed. Additionally the

SiPass Client has to be installed on each system where a SeeTec Client should is used for configuring

the SiPass interface in SeeTec.

▪ The hostname and IP address of the SiPass server has to be defined during SiPass installation and must

not be changed!

▪ All Systems need to be a member of the same Workgroup or Domain.

▪ On each System where a SiPass Client or Server is installed a Windows user has to be created, the user

needs to be a member of the Administrator group. The username and password need to be the same

on all systems. This user has to be logged on if you want to start the SeeTec client. If this user is not

logged in the SeeTec Client will not establish a connection with the SiPass Server.

▪ After the Installation of the SiPass Client you need to establish a connection to the SiPass Server. This is

needed in order to make sure that the SiPass Client is able to connect SiPass Server. Communication

between SeeTec and SiPass will only work once this is successful.

▪ SeeTec recommends to install the software on a dedicated 32-bit OS since SiPass is only providing a

32-bit interface. An installation on 64-bit OS is also possible but not recommended. I this case you have

to use the 32-bit setup package of Cayuga.

▪ You must not manage any camera at the SiPass system with installed DM and MDB service because

specific DLLs are used for SiPass.

▪ Cayuga supports only one SiPass server.

▪ It is possible to integrate up to 1500 door contacts.

▪ Up to 3000 rules are supported.

4.2. Installation and Configuration of SiPass

The installation and configuration will be done by your Integrator.

The following instructions are only the settings to establish a connection between SeeTec Cayuga and

SiPass.

4.2.1. SiPass Hardware: Configuration (Access Controller)

Open a telnet connection to your SiPass hardware and add the desired IP Address over a telnet command:

▪ telnet

▪ User: SIEMENS

▪ Password: spirit

▪ (User and password are case-sensitive)

▪ Enter this command:

▪ s h Example: s h 192.168.112.15

4.2.2. SiPass Server Software: Installation

▪ Installation Type: Complete (Install Server and Client)

All other configuration steps depend on the used SiPass version.


30

© Qognify GmbH

4.2.3. SiPass Server Software: Configuration

Perform the following step (Configuration of the DCOM Interface) and restart the SiPass Server service:

Configuration DCOM Interface

▪ Open Control Panel → Administrative Tools →Component Services → DCOM Config

At the advaNTage Server properties change Authentication to default

4.2.4. SiPass Client Software: Configuration

The installation is carried out by your integrator; the most important settings are listed below:

▪ Installation type: User Defined (do not install the Server component)

▪ When specifying the SiPass server, enter the host name of the server. This must NOT be changed later!

4.3. Installation / Configuration SeeTec

RECOMMENDATION:

We strongly recommend using a 32-bit System only!

4.3.1. Installation on a 32-bit operating system

IMPORTANT:

▪ The SeeTec Software must be installed machine where a SiPass Client is already installed.

▪ Installation:

▪ Start the installation with the setup.exe file

▪ As Setup Type choose Distributed Server

▪ Click Next

▪ As Management Server enter the IP address of your SeeTec Core Server

▪ At IP address/host for name for server communication select the IP address of your local system

The above described steps will install the SeeTec services DeviceManagement (VMS_DM) and

MultimediaDatabase (VMS_MDB). The installation directory path is C:\Program Files\SeeTec.

4.3.2. Installation on a 64-bit operating System

IMPORTANT:

▪ On a 64-bit operating system you have to use the Cayuga 32-bit setup package!


31

© Qognify GmbH

▪ The SeeTec Software has to be installed machine where a SiPass Client is already installed.

▪ The SeeTec DM service for SiPass is running as a 32-bit process on 64-bit operating systems. We

strongly recommend using a 32-bit System only!

▪ Installation:

▪ Start the installation with the setup.exe file

▪ As Setup Type choose Distributed Server

▪ Click Next

▪ As Management Server enter the IP address of your SeeTec Core Server

▪ At IP address/host for name for server communication select the IP address of your local system

The above described steps will install the SeeTec services DeviceManagement (VMS_DM) and

MultimediaDatabase (VMS_MDB). The installation directory path is C:\Program Files (x86)\SeeTec.

4.3.3. Configure DM service to communicate with SiPass

The user which is used for SiPass also must be used as User for the VMS_DM service.

▪ Make sure that both machines are in the same domain or workgroup

▪ Make sure that the user exists on both machines

▪ Stop the service VMS_DM ether with SeeTec ServiceManager or with the Windows service configuration

▪ Open the configuration for the service VMS_DM

▪ Go to tab Log On and change the user settings

▪ Click OK and restart the service


32

© Qognify GmbH

4.3.4. Configuration of the SiPass interface inside the SeeTec System

IMPORTANT:

The configuration can only be done on PCs on which the SiPass client software is installed.

Before you start the SeeTec installation please make sure that the SiPass Client software can establish a

connection to the SiPass Server.

In order to setup the interface from SeeTec to SiPass you need to add a SiPass hardware in SeeTec

configuration mode.

▪ Open the SeeTec Client and change to configuration mode

▪ Go the Other hardware

▪ Add a new hardware,

Manufacturer: 3rd Party Interface

Type: SiPass Access Conrol Software

As DeviceManager select the server where you have previously installed the distributed server

component.

▪ As username and password use the login data of your SiPass system (Standard: username: siemens,

password: spirit).

▪ Press OK

Open the SiPass device that you just added and configure it as follows:

General

You can change the name of the device, DeviceManager, user and password if needed.

Event Groups

At Event groups you can combine several events in a group. This group can be used as start event in an

alarm scenario:

▪ Add a Group; At Event groups change the name of the group

▪ Choose the event(s) for the group

Doors

At Doors you can give the doors a custom specified name and choose icons to represent the doors and their

states on a SeeTec map.

You can integrate a maximum of 400 doors.


33

© Qognify GmbH

▪ SiPass name: Reset the name of the door to the name from the SiPass system (optionally).

▪ Each door has six states (Locked, Unlocked, Forced open, Open too long, Alarmed, Tampered).

▪ For each state you can choose an icon in the dropdown list.

▪ Apply to all doors maps the selected icons to all doors.

Rules

Add the desired number of rules (You will find the configuration tree that you already know from SiPass):

▪ Choose an event for each rule (or an event group). You can specify the individual hardware

components in Level 1 to Level 5 optionally.

NOTE:

You have to configure a rule for each door if want to receive events from this location.

▪ Save your settings

NOTES:

▪ If you open the SiPass device again you should receive an Infobox with the message that a connection

to SiPass server is established.


34

© Qognify GmbH

▪ If you do not receive this message a connection to SiPass Server is not possible – in that case, you

should check communication between SiPass Server and Client.

▪ Each rule can be used as start event for an alarm scenario.

4.3.5. Alarm scenario configuration

In order to use the configured rules (see previous chapter) create an alarm scenario in configuration mode.

To define a start event for the SeeTec alarm scenario select the SiPass rule from the Select events tree in

the Event selection dialog.

To configure the complete alarm scenario please see the SeeTec manual.

4.3.6. Information on access events

The SiPass system sends additional information to the DeviceManagement service (DM) if an access event

occurs.

▪ Trying to access a door without permission

▪ Access with an invalid card

If the rule is fired and an alarm is triggered (which contains the rule as start condition) the following additional

information will be transmitted and stored in the alarm:

▪ First and last name of card owner

▪ Card number

▪ Location (door) where the event occurred

▪ Description

4.3.7. Searching for additional information

In Archive Mode you can search the additional information.


35

© Qognify GmbH

4.3.8. Showing doors on Maps

To display the state of the doors open add a map to your SeeTec configuration:

▪ Place doors from Hardware → SiPass on the Map with drag and drop.

▪ To show the state and name as text permanently activate the checkbox Show text.

▪ Save the changes with Apply or Save.

Open the map in Surveillance mode


36

© Qognify GmbH

If the state of a door is changed, the icon and text of the door will changed immediately.

With a left click on a door icon a context menu will be shown to control the door:

▪ Allow Access: Open the door temporary for a short time (defined in the SiPass system)

▪ Unlock Access Point: Open the door permanently, the input readers will be disabled

▪ Lock Access Point: Lock the door, the input readers are active again

4.4. Access Control Data Editor

4.4.1. Prerequisites

The SiPass Integrated client software needs to be installed on the machine where the data editor will be

used.

4.4.2. Connecting to SiPass Integrated

Open the data editor (Menu View in the SeeTec Cayuga client).

A separate login to the SiPass system is required (menu bar of the data editor).

Activate auto-connect to store the login details locally and login automatically.

The standard login data are:

Host: [IP address of your SiPass PC]

Port: 4200

User: siemens

Password: spirit


37

© Qognify GmbH

4.4.3. Functionalities

Data editor

▪ Adding/removing card holders

▪ Edit card holders (via button or via double-click on the item)

▪ Connection information

▪ Login information

▪ Display card holder data

▪ Status

▪ First name

▪ Last name

▪ Image (can be hidden via the menu bar)

▪ Access group

▪ Workgroup

▪ Validity

Item editor

Via the item editor the following cardholder information can be accessed and changed:

▪ First name

▪ Last name

▪ Access group

▪ Workgroup

▪ Image

▪ Validity

▪ General information (like address, phone, mail etc.)

▪ Add/remove access tokens

▪ Add/remove access rights

▪ Add/remove of license plates


38

© Qognify GmbH

4.4.4. Authentication and user-rights

To access the data editor, the appropriate right has to be set within the user- or group-rights section in the

SeeTec Cayuga configuration.

To login to SiPass integrated please use one of the configured users there. The authentication is done by the

SiPass system.

4.4.5. Card reader integration

Entering the card’s ID in the “access tokens“ tab can be done using a USB card reader.

Currently supported models are:

▪ HID Cardman 5x21.

Whenever the editor is opened and a card put in or onto the reader, the item editor opens automatically with

the card ID entered, the “access tokens” tab will be selected by default.

Supported card types are:

▪ Mifare 1K

▪ Mifare 4K


39

© Qognify GmbH

5. Connection to TDSi (Cayuga R4 or later)


5.1.1. About TDSi

TDSi is an access control system from Time and Data Systems International Limited, http://www.tdsi.co.uk/.

5.1.2. TDSi connection

The SeeTec connection to the TDSi system is done by the export of the text-files by TDSi which are then

read-out by the SeeTec system.

5.2. Configuration

5.2.1. TDSI configuration

The TDSi-configuration is done by the EXgarde Event Exporter (Menu File -> Export Settings).

Each event has to be stored in a directory which is fully read- and writable by the SeeTec

DeviceManagement Service.

General

▪ As Export Destination choose Text File.

▪ Configure both as Export Data Definition.

The EXgarde Event Exporter will save each event as RAW and as human readable format in the file.

Data Options

▪ As Data Format choose Character separated Value.

▪ Choose Comma Separated as separator between two events.

Destination Options

▪ At Destination Folder choose the directory which is used for exporting the events.

The SeeTec server will then access this folder and read the events.

▪ As filename choose: _#1.txt.

▪ Set the Max Record Count to 1.

So, each event will be stored in a separate file. (SeeTec needs each event in a separate file)

5.2.2. TDSI configuration in the SeeTec System

At Configuration Mode create a new Hardware, Manufacturer: 3rd Party Interface, Type: TDSi access

Control.

General

▪ Enable or disable access control by selecting the Activated checkbox. You can also change the name of

the device.

▪ Select the DeviceManagement to manage the TDSi connection.

▪ In the TDSi export directory dialog, specify the directory where the EXgarde Event Exporter will store

events.

If the directory was not created locally on the SeeTec server enter the full UNC path.

▪ Enter the TDSi export delimiter (see also previous chapter TDSi Configuration).

▪

http://www.tdsi.co.uk/


40

© Qognify GmbH

Event Groups

Creating event groups is optional. Event groups will be used in a rule as starting event for alarm scenarios.

You can determine that always the same alarm scenario is started, regardless of whether event A occurs, B

or C.

▪ To create a new event group, click Add.

▪ Enter the name of the event group in the text field.

▪ In the Event group list, select one or more events assigned to the event group.

Rules

▪ Use the Add one rule or Add 10 rules button to add one or 10 rules at once.

▪ Set the name of the rule in the Name column of the table.

▪ For the event select a single event or an event group that you have previously created.

The Source, Detail 1, Detail 2 and Detail 3 fields are optional. They correspond to the fields in the EXgarde

Explorer overview.

EXAMPLE:

Door opened is chosen as Event, Front Entrance as Source and user Testuser as Detail 1.

The corresponding alarm scenario will only be started if user Testuser opens the door Front Entrance.

If the fields are not used the corresponding alarm scenario will be started if an event occurs.


41

© Qognify GmbH

IMPORTANT:

The case (upper/lower case) in the Source field as well as Detail 1 through Detail 3 must be the same in the

EXgarde Event Exporter and the SeeTec configuration. Otherwise the alarm scenario will not be triggered.


42

© Qognify GmbH

6. Siemens SiPort Integration (SeeTec Cayuga R3 or later)

This document describes the interface between SeeTec and SiPort. It contains all important steps to

establish communication between SiPort and SeeTec via the OPC interface. In general, the integration is

done only via OPC data points. These data points are evaluated in SiPort via routines. This evaluation can

be used to start SiPort internal actions as well as to set certain SeeTec OPC data points. Writeable SeeTec

OPC data points can in turn start actions and scenarios in SeeTec.

For this reason, a functioning SiPort system or a plan for the required data points and the action planned for

them should already be available before this interface is set up.


SIPort is a Siemens system for access control and time management. This allows authorized persons -

whether employees or visitors - to move freely in the building or on a campus. At the same time unauthorized

persons are kept safe. SiPort can be used both locally for one location, but also in globally networked

branches.

SiPort is modularly expandable and can use supplementary modules to integrate it into other systems such

as hazard and building management systems, 3D sensor technology for person detection, room reservation,

access control by license plate recognition, and video management systems (SeeTec Cayuga).

The Cayuga OPC interface can also be used to integrate integrated components of the VMS such as VMS.

Intrusion detection systems (SiPass) with SiPort couple and can thus result in dependencies on various

actions.

6.1.1. Important Informationen

The following is required for operation

▪ A SeeTec OPC license with sufficient data points

▪ SiPort OPC license

▪ An OPC-UA Gateway (preferably Unified Automation)

This is chargeable. The license must be purchased.

▪ Communication between SiPort and SeeTec takes place:

▪ SiPort communicates with OPC Client

▪ OPC client communicates with UA Gateway

▪ UA Gateway communicates with SeeTec OPC UA Server

▪ Each SeeTec entity can provide several data points.

▪ Secure and encrypted communication can only be done via the UAGateway and SeeTec OPC UA

Service.

6.2. communication principle

Essentially, SiPort works independently of SeeTec as an independent solution. This means the access

control roles and time management are managed standalone by the SiPort server and controller.

With the communication via OPC to SeeTec, the functions of SiPort can be extended by the functions of

SeeTec VMS and additional dependencies of states can be realized.

Since the SiPort OPC Client (Babylon OPC Client) is an OPC Classic application, communication can only

take place via a UA gateway.


43

© Qognify GmbH

The principle of communication is to translate the data points of SeeTec OPC into BI (Binary Inputs) so that

they can be used by the SiPort server. At the same time, these BIs are again translated into OPC data

points, e.g. Alarm scenarios can be started on the SeeTec VMS.

6.2.1. Communication UA Gateway – Babylon OPC Client

Since the UA Gateway is the only one which allows a secure connection to the SeeTec OPC Server and the

Babylon OPC Client is an OPC Classic application, for security reasons both components should be used on

the same computer.

The UA Gateway manages and translates all communication to the OPC server so that an OPC Classic

application can use the data points. The gateway provides a port and process for this which the Babylon

OPC client can us

6.2.2. Communication SiPort (Babylonserver) – Babylon OPC Client

The Babylon OPC Client translates the created data points into binary inputs (BI) and communicates them to

the server. The server in turn decides what these data points are used for, processes them accordingly and

can either start internal actions or in turn send the command to the OPC client to write the attributes of these

data points. The writing of the attributes is again sent via the gateway to the Cayuga OPC server and thereby

e.g. Alarm scenarios are started / stopped.

Routinen

The use of the BI attributes takes place via routines. This means that sequence routines are programmed

which query the individual states of the BI attributes and, if necessary, can also be set. Thus, various

dependencies can be realized.

e. g.


44

© Qognify GmbH

▪ BI 0 = State Alarm SPC (arm / disarm)

▪ BI 1 = SeeTec Alarm started attribute (allows the alarm to be started)

▪ BI 2 = SeeTec Alarm stoped attribute (allows the alarm to be stopped)

It is possible to check via SeeTec whether the SPC alarm system is armed. If, for example, someone gains

unauthorized access to an area that is checked by SiPort internal contacts (such as door contact), SiPort can

start an alarm scenario via BI 1 in addition to its own functions at SeeTec and stop again via BI 2, thus

recording an alarm drive.

Through these routines, both internal contacts and functions of the SiPort as well as external contacts and

functions of the SeeTec, including SeeTec integrations, can be made dependent on the third party and

corresponding measures and functions can be used both internally and externally.

Redundancy through routines

Through these routines it is possible to realize a reliability. For SeeTec, an OPC service must be installed on

another server. In the Babylon OPC Client, the data points are created by both OPC services. The routine

must be programmed to poll the same data point on the redundancy service if the main service fails to

communicate. This also requires twice the number of data points.

6.3. Installation and configuration

6.3.1. SiPort Server

Basically, the installation of the SiPort server is done by a certified partner. Installation instructions and

update instructions are included with the software. Important during the installation is that this "Custom" is

installed and the correct database is selected after the installation. (DB20 = access control only, DB30 =

access control + time management)

From the installation instructions as well as the homepage of Autec (OEM manufacturer), http://www.autec-

gmbh.de/, the current minimum requirements and compatibilities can be taken.

It is best to choose a specific directory and install all installations in this directory. As a result, updates can be

easily installed, since the exchange of directories is enough for an update. Current drivers and firmware are

also on the homepage of Autec.

IMPORTANT!

When installing the dongle driver, you should make sure that this installation step is not done via the remote

desktop, but directly on the SiPort server. A remote installation can cause problems with the proper operation

of the dongle.

Virtualization

In order to be able to use the SiPort server in a virtual environment, a door controller is used instead

of the physical service dongle. For this, a virtual service dongle must be ordered when ordering.

When ordering, the serial number of a door controller is required. Based on this serial number, a LIC

file is created and this can be implemented in the virtual environment. This turns the door controller

http://www.autec-gmbh.de/http://www.autec-gmbh.de/


45

© Qognify GmbH

with its unique serial number into a service dongle. This also means that if this door controller is

defective, also the function as a service dongle is no longer given.

Peripherie

The SiPort server can scan and manage its components in the network. To do this, you can see the found

components in the "Network Administration" and configure them with the tool U3SetIp. The number is the

decisive one. After setting the correct IP address, the IP address can be set by "Change K32 IP Settings".

A more detailed description can be found in the supplied documentation directory.

6.3.2. Connection SiPort – Babylon OPC Client

That the SiPort server can communicate with the Babylon OPC client, it is configured in the SiPort server via

the "W3Port" program. The values set here must match the "BabOPCClient.ini" of the Babylon OPC Client.

It is important that the entry "Type 16 Generic Type" has been selected and the IP address of the computer

on which the OPC Client is running. The number of this index must match the MBOXID in BabOPCClient.ini.


46

© Qognify GmbH

If all settings match, the IP address of the SiPort server appears in the OPC client. A more detailed

description can be found under "G_OPC-Client.pdf"

6.3.3. Connection Babylon OPC Client – UA Gateway

Since the Babylon OPC Client is installed on the same computer, the Gateway Gateway is activated, can

search for a server locally after selecting the "BabOPCClient.exe" and select the installed gateway.

The following configuration of the data points can be ignored, as they are quite difficult to configure via the

GUI. The next point describes how the data points are configured via the config file.

After a successful connection, it is possible to recognize in the OPC client that the manufacturer of the OPC

Classic server (in this case the gateway) and the OPC server are connected and the number of data points

which are monitored. (currently 0).

Configuration of the data points in the Babylon OPC Client

For reading the data points, the OPC Explorer from Matrikon is very well suited. Start this and connect to the

gateway. Then create a group to merge the data points together.

In the next step you can display the entire Cayuga OPC tree and merge the desired data points by drag &

drop


47

© Qognify GmbH

If you have adjusted all the data points, you can confirm this with "OK" and then export.

From the export file, only the ItemID's are needed, so you have to copy them out separately and paste them

into the file "BabOPCClient.opc".

It is important that only the ItemID is inserted and the remaining information from the exported file is omitted.

6.4. Summary of the main points

▪ Operation requires a UA gateway. This translates the communication between OPC UA (SeeTec) and

OPC - Classic.

▪ The Babylon OPC Client translates OPC Classic ID's communication into binary inputs (SiPort)

▪ An encrypted connection can only be established between OPC UA (SeeTec) and UA Gateway.

▪ For virtualization you are licensed the serial number of a door controller. This door controller then acts as

a dongle


48

© Qognify GmbH

▪ Redundancy from the OPC server can only be achieved by duplicate OPC services and data points. The

evaluation of these multiply available data points must be done by the OPC client (or routines on the

SiPort server).

▪ Due to the OPC connection, SiPort is able to use the functions in SeeTec integrated third-party

manufacturers.

▪ At least one SeeTec S100 with the additional option "OPC server" is required for operation.

▪ SiPort licensing must also include an OPC connection.


49

© Qognify GmbH

7. Maxxess (SeeTec Cayuga R11 or later)

7.1. System requirements

Please get in touch with Maxxess for latest requirements

7.2. Required software packages, licences and features:

▪ Maxxess eFusion Installer Package

▪ SeeTec Cayuga R11 or higher

▪ SeeTec Cayuga S100 license or higher

▪ SeeTec SDK license

7.3. Installation

▪ Download the zip file with the Maxxess installation package and extract it.

▪ Mount the extracted ISO image as a CD/DVD.

▪ Execute the Setup.exe on the ISO image.

The window to install workstation feature appears.

▪ Check the following features:

▪ SQL Server,


50

© Qognify GmbH

▪ Workstation,

▪ and from ViewPoint Integrators select SeeTec Cayuga.

▪ Click Configure.

▪ The Database Setup should be configured as shown in the screenshot:

▪ Click Configure. The window Configure Communication Modules appears.


51

© Qognify GmbH

▪ Click the Close.

7.3.1. License Activation

Maxxess eFusion must be activated and registered prior to first use. For more detailed instructions regarding

the activation process refer to the License Activation chapter in the Maxxess User Manual.

▪ Double click on the Desktop Startup icon

▪ In the Help Menu, open About Desktop.

▪ Click Register

▪ Fill out the registration window and send the Registration key that is provided to Maxxess.

▪ Drag & Drop the registration file which is send by Maxxess onto the registration window.


52

© Qognify GmbH

Once the Maxxess software is installed and registered you can run the SeeTec installation package to install

SeeTec SDK 32-bit.

7.4. Installation SeeTec SDK

▪ Start the SeeTec Setup.

▪ Click Next.

▪ Accept the terms of the license agreement and click Next.

▪ Accept the destination directory for the installation and click Next.

▪ Select Custom as Setup type and click Next.


53

© Qognify GmbH

▪ Uncheck the Client components and the Server components.

▪ Check SDK (32-bit) item.

▪ Then click Next.

▪ Define the update service and click Next.


54

© Qognify GmbH

▪ Click Install.

7.4.1. Use the latest SDK files

NOTE

This step is needed and recommended after every released patch of SeeTec SDK

▪ Go to SeeTec SDK (32-bit) Path (C:\Program Files\SeeTec\SeeTecSDK\libsdk_x86) and copy the

necessary files (all beginning with SeeTec.x).


55

© Qognify GmbH

▪ Paste the files into the Maxxess plugin folder (replace the files if needed):

…\Maxxess\AXxess Workstation\Bin\SeeTecCayuga

7.5. Add SeeTec Server to Viewpoint

▪ Run Viewpoint Client

▪ Open Configuration page (1.)

▪ Click on Servers (2.)

▪ Login with user credentials

▪ Click on save icon


56

© Qognify GmbH

7.6. Troubleshooting & Remarks

7.6.1. Troubleshooting

The output status window in ViewPoint will show successful operations as well as abnormal ones. It can be

used to troubleshoot problems with ViewPoint or an integrator. In the ViewPointFile menu, there are options

to enable logging of the status box, to delete the log and to display the log.


57

© Qognify GmbH

7.6.2. Additional Notes Regarding the SeeTec Cayuga Integrator used in the

ViewPoint Software

The PTZ control feature for a camera is auto-detected at Server\Camera load time. This means that the PTZ

control setting for a Camera in the ViewPoint Camera Properties screen is not used/not applicable.

The PTZ Presets must be configured via the ViewPoint software to be used. Any PTZ Presets configured via

the NVR/DVR device software will not work in ViewPoint. Alternately, making the names of the PTZ presets

be numbers, i.e. “1”, “2”, “3”, etc. in the SeeTec VMS will also allow the ViewPoint application to call the

correct presets.

The Focus Near and Focus Far features are dependent on the camera capabilities.

The Iris Open and Iris Closed features are dependent on the camera capabilities.

Check with the factory for any updates to the SeeTec Cayuga SDK for any fixes and/or new features.

7.6.3. Necessary Files

The file SeeTecCayuga.axch provides the primary interface between the SMS system and the SeeTec

Cayuga interface files.

Additional files necessary to interface to the SeeTec Cayuga system are stored in the following folders.

1. …\Maxxess\AXxess Workstation\Bin\SeeTecCayuga

a. SeeTecCayuga.axch version 6.1.0.14107 or later.

b. SeeTecCayuga.cnf

c. SeeTecCayuga.dll version 6.1.3.16193 or later.


59

© Qognify GmbH

1. Aritech Alarm Center Connection (Cayuga R4 or later)


The Aritech Alarm Center can send alarms and events to the SeeTec system by using the OH Network

Receiver.

The status of the Aritech is not known to SeeTec at any time other than when an alarm / event is sent,

therefore you cannot use it as a precondition in an alarm scenario.

1.1.1. Used protocol version

Security Communications – “SIA Format” Protocol - for Alarm System Communications, SIA DC-03-

1990.01(R2003.10).

1.1.2. Internal communication

The communication between the SeeTec System and the Aritech Control Center is done over the OH

Network Receiver and a logging appender (OH Logging Appender).

The connection is unidirectional; the SeeTec System will only receive Events.

1.2. IMPORTANT (Troubleshooting)

If you have problems with the connection and you are not receiving any events in Cayuga please consider

this information (First read the configuration and setup part, this is just for trouble shooting):

▪ Deactivate the firewall and all antivirus applications and test the connection

▪ Stop the OH service and look with the OH Network Receiver if it successfully starts and a connection to

the ATS is established and events are received like desired

▪ Check the correct port configuration at the ATS web interface, OH Network Receiver, the logging

appender and Cayuga Device

▪ Sometimes the OH Network Receiver did not start properly because of problems with port 80. Try to

close or stop all programs using this port like IIS or skype to test the connection

1.3. Installation / Configuration

NOTES

▪ The OH Network Receiver has to be installed on the SeeTec Server.

▪ Perform a 32-bit installation.

▪ Do not install the OH Network Receiver as a service!

1.3.1. General

1. Install the OH Network Receiver (UTC):

2. Start the OH Network Receiver (Start -> All Programs -> UTC F&S) and change the following settings:

▪ Menu Setup -> Automation: Deactivate Automation Present

▪ Menu Setup -> Line cut timeouts: Supervision Port [1]: Raise to minimum 3 minutes.

3. Open the folder /tools/ohloggingappender/ within the SeeTec Installation directory.

▪ Run the file RegisterOHService.exe.

▪ Enter the installation directory of the OH Network Receivers.


60

© Qognify GmbH

HINTS:

▪ The file RegisterOHService.exe performs the needed steps to establish the communication between

the OH Network Receiver and the SeeTec System (Copying the needed files, adjusting the files for

logfile-output, add the service OH_Service)

The service will be started automatically.

▪ In the SeeTec installation directory you will also find the file unregister_OH_service.bat (in

/tools/ohloggingappender/).

This file will unregister the service if needed.

4. Get Access to the alarm panel over a Web browser.

▪ At Network Setup -> Central Station Network Parameters enter the following values:

▪ IP Address: SeeTec Server IP

▪ Protocol: TCP

▪ Port:

Please choose a port to communicate with the OH Network Receiver. Also apply this port to the OH

Network Receiver.

▪ Event Type: SIA

▪ Encryption: Triple DES

▪ In the SeeTec Software now add an Aritech Alarm Center.

1.3.2. Configuration of Aritech Alarm Center

The configuration of the Aritech Alarm Centers is done over its interface independently from SeeTec. For

configuration issues please refer to the Aritech Alarm Center manual.

1.3.3. Configuration of Aritech Alarm Center in SeeTec

Add hardware

▪ Add a new other hardware; Manufacturer: 3rd Party Interface, type: Aritech Alarm Center

▪ Choose which DeviceManager Server should manage the Alarm Center (The Aritech System has to

send its events to this SeeTec Server).


61

© Qognify GmbH

General

▪ Enter the OH Port for the events to be sent to from the OH Network Receiver via the logging

appender.

The port can be found in the file seetec.properties. This file can be found in the installation directory of

the OH Network Receiver.

▪ Enter the Central ID. You will receive this ID from the Installer of your Aritech Alarm Center.

Rules

A rule consists of a Name, a Zone ID, an Area ID and an Event

The following from the Aritech Alarm Center events can be used in a rule in the SeeTec System:

▪ Alarm [SIA Code: BA]: Alarm

▪ Tamper [SIA Code: TA]: Tamper events

▪ Armed [SIA Code: CL]: Alarm center is armed

▪ Disarmed [SIA Code: OP]: Alarm center is unarmed

▪ Mask [SIA Code: BT]: A sensor reports that a zone is masked

▪ Excluded [SIA Code: BB]: Zone was deleted.

▪ Arm Forced [SIA Code: CF]: Alarm center is armed although there are open problems

To create a rule please proceed as follows:

▪ Click on Add one rule or on Add 10 rules

▪ Activate the rule

▪ Enter a name

▪ Enter Zone ID to the corresponding Zone.

▪ Enter Area ID to the corresponding Area.

▪ Choose the desired Event (Column ‘1’- ‘7’), multiple selections are possible

HINT

You will receive the Zone ID and Area ID from the Installer of your Aritech Alarm Center.

Alarm scenario configuration

Create an alarm scenario. Choose the according rule as start-event.

The rest of the alarm scenario is configured as described in the SeeTec manual.

cayuga r15 technical guides · 2020. 6. 4. · use also the username and password of sql server to...

Documents