Panasonic WJ-ASC8501 Operating Instructions

Page 1
Administration Console
INFORMATION
(
)
OPERATEOPERATE
TL
OPERATEOPERATE
RESETRESET
FAN ALARMFAN ALARM
HDDHDD
ACTIVEACTIVE
Users' Guide
Model No. WJ-ASC8501
Before attempting to operate this product,
please read these instructions carefully and save this manual for future use.
Page 2
Admin Console
Software Version 1.5
for use with an SX850 Surveillance Control System
Installation & Configuration
Document Version 1.5 for System Administrators
installing and configuring the Admin Console
Admin Console 1.5
Page 3
Admin Console CONTENTS
INTRODUCTION 5 DOCUMENT CONVENTION 6
WHAT IT DOES 7
By Clock, Calendar, and Event 7 In Response to Emergencies 8
HOW IT WORKS 8
Configuration Management 8 User Control 8 Installation 8
PLATFORM 10
Hardware Requirements 10 Operating System Requirements 10
Video Display Setting Requirements 10 FROM DISKETTES 11 FROM CD-ROM 11 WHAT TO DO NEXT 11
WORKSHEET TASKS 12 INSTRUCTIONS 13 CHECKLIST 13 LOGIN 15 FIRST-TIME OPERATION 16
CPU Setup 16
Scheduled Modes 19 MAIN MENU 21 DATABASE MANAGEMENT 22
Database Archive 23
Create a Database 23
Select a Database 24
Copy a Database 25
Rename a Database 26
Delete a Database 27
Backup or Restore a Database 28
Get Current Database 32
Load a Database 32
System Configuration 35 INPUT TO SCREEN 41
SCS CPU Configuration 42
3 Admin Console CONTENTS
Page 4
Matrix Frames 42 COMPONENTS 46
Cameras 47
System Controllers 58
Monitors 63
Alarm Input/Output 67
Alarms 71
Operators 85 SEQUENCES 91
Tour Sequences 92
Group Presets 98
Group Sequences 104 AREAS 111
Monitor Surveillance Area 111 EVENT SCHEDULER 112 MANAGEMENT 115
Log Manager 116
AC Log 121
Account Manager 123
Help 126
ACRONYMS 127 TERMS 129
INSTRUCTIONS 139 TEAMWORK 140 CHECKLIST 140
Page 5
Admin Console WELCOME
INTRODUCTION
Welcome to the SX850 Admin Console. This guide is organized in a logical step-by-step seq uence th at will allow for both an easy and accurate configuration. First, an explanation o f what the Admin Console is and how it works in a Security Surveillance System (SCS) is presented in general terms. Next, you will be guided through installing the software, creating a configuration database, and loading the database into the Security Control System CPU.
While creating the configuration d atabase, you will find that many components interact with each other, and are dependent on specific values. It will be important to utilize th e worksheets p rovided at th e end of this manual to gather the data necessary to create the configuration database, and to develop an understanding of your Security Control System. These worksheets, once completed, should also be utilized when making updates or changes to the system’s configuration, to ensure accurate results.
This part of the process will b e explained in th e Con figuration section o f this manual, which is divided into three phases: physical planning, worksheet tasks, and keying in the data.
5 Admin Console WELCOME
Page 6
DOCUMENT CONVENTION
This guide uses the following conventions when describing the use and operation of this product.
Component or Sequence Definition
Field Data
This box will describe each field in a definition screen.
Warning: Text with this appearance suggests potential
problems or situations that you may encounter when attempting to do something in the Admin Console.
Note: Text with this appearance is a special instruction, rule,
or side comment related to the topic.
Tip: Text with this appearance offers suggestions or hints to
make using the Admin Console easier.
6
Page 7
Admin Console WHAT AND HOW
Admin Console enables an administrator and other users to closely control the operation of a Surveillance Contro l System ( SCS). Such a system can include as many as 8,192 cameras and 1,024 monitors. You will be guided through the process of installing the Admin Console to manage an SCS, creating the databases that dictate the operation of the SCS, and allowing an administrator to easily change the system’s configuration when necessary.
WHAT IT DOES
Admin Console enables an administrator to utilize an SCS’s performance capabilities to meet the surveillance needs of a facility during initial installation, as well as when conditions change.
By Clock, Calendar, and Event
The SCS can be configured to help security personnel respond in different ways using the Admin Console utility. For example, based o n:
Time of day - such as open to the public, closed, and after-
hours cleaning and maintenance.
Night quiet time.Quiet day of the week - which would be a 24-hour period
of quiet time without any activity except security personnel doing rounds.
Special business activity - such as taking physical
invent ory, re stocking , and doin g routine m aintena nce o f special equipment.
Visits by celebrities, dignitaries, or officials, with or
without entourage - protective or otherwise.
7 Admin Console WHAT AND HOW
Page 8
In Response to Emergencies
The SCS can be configured u sing the Admin Console u tility to allo w for quick responses to unexpected disruptions of normal activity that could be caused by power, fire, police, health, or other emergencies.
HOW IT WORKS
The Admin Console maintains tracking, reporting, and functional relationships between the various components in a surveillance control system.
Configuration Management
It is possible for the Admin Console to maintain several separate configurations for a given system. They could be very similar or differ greatly.
One configuration, for example, could be very different than the typical configuration used, because its purpose may be to watch over a particular activity, such as the taking of an equipment and supplies invent ory when the facility is closed to the public.
User Control
In addition to controlling individual cameras, the Admin Console provides the user with selections from lists of presets and sequences.
If the user chooses a preset, a group of monitors will
display a set of video outputs from a group of cameras at preset positions.
A sequence, on the other hand, is a self-generated series of
views - one of several cameras on one monitor (a Tour Sequence) or of group presets (a Group Sequence).
Installation
Installing the Admin Console so ftware only takes a few minutes and is very simple to complete. Whether installing from a CD-ROM or floppy diskettes, a series of Windows’ dialogue boxes guide the installation onto the PC.
The subsequent task of configuring the so ftware, once installed, can ra nge from modest, for a small system, to complex, for a very large, complicated system, such as in an airport.
8
Page 9
Admin Console WHAT AND HOW
When it comes to security surveillance, all potential contingencies sh ould be considered when p lanning a system’s functionality. The Admin Console is the tool that simplifies this process.
9 Admin Console WHAT AND HOW
Page 10
Admin Console INSTALLATION
Part of installing the Admin Console means copying program files from either a CD-ROM or a set of floppy diskettes onto th e hard d rive o f a dedicated PC. The Admin Console is a tool that allows an administrator to configure the SCS (Surveillance Control System) with information compiled about components and users, and to use well-planned presets and sequences.
PLATFORM
As with any PC application that must be reliable, Admin Console should be the primary program running on the computer it is installed on. There should be little other than Admin Console running on the same computer.
The PC used for Admin Console should have the following characteristics:
Hardware Requirements
IBM PC or 100% compatible, Pentium-133MHz or higher, 16MB RAM, 20MB of available hard drive space for the installation of the Admin Console, with additional space available for conf iguration database (.adm) and log files.
In addition, the Admin Console PC must be equipped with an Ethernet network interface card using the TCP/IP protocol.
Operating System Requirements
Microsoft Windows 95 OSR 2, 98 SE, NT 4.0, 2000
Video Display Setting Requirements
256 colors or higher800 x 600 resolution
10 Admin Console INSTALLATION
Page 11
Admin Console INSTALL
FROM DISKETTES
1. Insert diskette 1 into the floppy drive.
2. From the Windows’ Start menu, select Run.
3. Type a:\setup, then click OK or press the Enter key.
4. Respond to the dialogue boxes that appear by following the
directions given.
5. Remove each diskette when prompted, and replace it with the
next one.
The last diskette asks you to click Fin ish in order to complete setu p.
FROM CD-ROM
Insert the CD-ROM program disk into the CD-ROM drive on your computer. The Admin Console program will begin installing automatically. Respond to the dialog boxes by following th e directions given.
WHAT TO DO NEXT
The next section will guide you through the phases involved with the setup and configuration of the Admin Console.
11 Admin Console INSTALL
Page 12
Admin Console CONFIGURATION
The tasks covered in the Installation section, beginning on page 10, must be completed before attempting to configure the Admin Console.
The Admin Console configuration is a three-step process:
Mark copies of drawings of the facility under
surveillance.
Fill in the appropriate worksheets p rovided at the end
of this manual. (This will result in a survey of all the components in your system, and how they interact with one another.)
Enter the values collected on the worksheets into the
Admin Console. (The v alues entered determine th e operation of the Surveillance Control System (SCS) in complete detail by creating relationships among all of the components, including th e users.)
Once existing copies o f the facility’s drawings are marked, there is a basis for assigning logical or area/local numbers, titles, and practical names for the various components o f the surveillance system . With this information, you can then continue with the Admin Console worksheet tasks indicated below.
WORKSHEET TASKS
The Admin Console worksheets aid in the collection and organization of information needed to configure the SCS. One person can complete all of the worksheets in a smaller system, but to speed up any installation, consider assigning a team of several individuals to compl ete different worksheets concurrently.
12 Admin Console CONFIGURATION
Page 13
Admin Console CONFIGURATION
Perhaps the surveillance system you are working with is small enough for you to collect the required information, and input those values d irectly on to the Admin Console screens.
However, if the system is more complex, it is best to gather and write down the information needed for the initial configuration of Admin Console.
If settings need to be modified or updated in the future because of a change in surveillance needs, or changes made in the components of the system, the worksheets can be used to track past, current, and to-be configurations. The worksheets make it very easy to do this, regar dless of the size of your system.
As with any system conf iguration, it is wise to keep initial and updated worksheets on file, just in case there is ever a need to re-enter the data, or trouble shoot th e system.
INSTRUCTIONS
The title of each worksheet is the sam e as the title of the Admin Console window it supports. For example, the “Operators” worksheet supports the “Operators” window. T he fields th at need to be filled in on the various Admin Console windows correspond to the sequence presented on the worksheets.
1. Reproduce the worksheets supplied with the system.
You may only need a single copy of a certain worksheet, but dozens of copies of others, depending on the size and components that make up your surveillance system .
Copy pages from the actual worksheets located in the back of this manual.
CHECKLIST
Worksheets are arranged alphabetically to make them easy to find. However, the checklist below indicates a workable sequence for completing them.
For a team approach to information collection, use b est judgment to decide how to distribute the worksheet among several individuals.
SCS-CPU Setup
13 Admin Console CONFIGURATION
Page 14
Matrix FrameCamerasSystem ControllersMonitorsAlarm Input/OutputOperatorsTour SequencesCamera PresetsGroup Pr esetsGroup SequencesAlarm Definition(s)Alarm Target Definition(s)Alarm Target Assignment(s)
Camera -to- Monitor Permission(s)Controller -to-Camera View Permission(s)Controller -to-Camera Control Permission(s)Controller -to-Monitor Permission(s)Controller -to-Group Sequence Permission(s)Controller -to- Alarm IO Permission(s)Controller -to- Alarm Permission(s)Operator -to- Contr olle r Per missi onsEvent Scheduler
14
Page 15
Admin Console CONFIGURATION
LOGIN
When running Admin Console after having installed it, and each subsequent tim e that it is r un, this lo gin screen will appear.
Enter the user login name (default = admin) and user password (default = sx850) to open the application.
Note: Both the user login name and password fields are case
sensitive.
It is recommended that after entering the Admin Console th e first time, that the user login name and password are changed from the defaults, in order to control administrative access.
During the configuration, add user names and passwords at various access levels as needed. See the Account Manager section.
15 Admin Console CONFIGURATION
Page 16
FIRST-TIME OPERATION
CPU Setup
When Admin Console is run the first time, the following window will appear after you enter the default login name and password.
On this window you must match the CPU configuration in the software with the actual CPU running the SCS.
1. Enter the IP address for the Main A CPU.
Ask your installer or network administrator for the IP address for the Main A CPU. This will let the Admin Console software k now where to load the configuration database, when initiated later.
16
Page 17
Admin Console CONFIGURATION
2. If your system is equipped with a redundant CPU, then
check the “Redundant” box and enter the IP address
for the Main B CPU.
Ask your installer or network administrator for the IP address for the Main B CPU. If the system has just a single CPU, leave th e redundant check box blank. The Main B CPU I P address will n ot be required.
3. Click the green check mark to save this setting.
4. Decide on the operational mode for the SCS CPU.
Click the “Size” tab on the right side o f the CPU System Configuratio n window. This is where you will specify the size of your CPU. As you click on Standard, Enhanced, or High-Speed, each will display its maximum capacities. The maximum capacity is th e largest su pported number of each of the components listed. You must match the MCPU capacity with the capacity in this window.
Standard
If any of the components in your system exceed the maximum capacity listed, you must choose the next highest system type. For example, if the number of each of your system’s components are less than the maximums listed for “Standard”, but you have 65 monitors, you would need to select “Enhanced” as your system type.
Enhanced
This is the next SCS CPU type available. Using the Enhanced CPU type will increase the capacity of the system. This can be chosen as long as your system MCPU is the correct v ersion f or this type.
17 Admin Console CONFIGURATION
Page 18
High-Speed
This is the largest CPU type available, providing th e capacity for handling the largest number of components.
5. Click on Standard, Enhanced, or High-Speed, and then
click the green check mark to save.
6. You can then click on the EXIT button to leave this
window.
18
Page 19
Admin Console CONFIGURATION
Scheduled Modes
If the Scheduled Modes check box is selected on the CPU System Configuration window’s “Size” tab, an administrator can configure up to four different modes of operation that can then be scheduled to become active as desired. The configuration of these modes are programmed, or set by an administrator during the configuration of the system’s compone nts th rough Adm in Consol e.
19 Admin Console CONFIGURATION
Page 20
VIEWING AND PROGRAMMING
In each of the components’ permissions tabs that contain a section like the one shown to the left, modes can be viewed and programmed.
Clicking the View option button allows you to view permissions for the mode chosen, and defaults to programming for the same mode. In the case of the graphic to the left, mode 1 is set for viewing, and thereby programming.
The permissions grid reflects the contents of the mode whose view is selected with the View o ption b utton. In the image below, the p ermission grid is displaying the contents of mode 2.
More than one mode can be programmed at the same time by clicking on the Prog check boxes of the other mode numbers that you wish to program simult aneously. This will append, o r add any p ermissions that are then changed on the permissions grid, but will not duplicate entire modes or overwrite existing permissions in the other modes.
The image to the left indicates that the permissions grid would now be displaying the contents of mode 3 (which is also by default being
20
Page 21
Admin Console CONFIGURATION
programmed), and would simultaneously be programming any subsequent changes into modes 1 and 4 as well.
It is not necessary to perform a Save for each mode viewed or programmed. Saving permissions, when completed, automatically saves all four modes, regardless of the current View or Prog selection. Permissions are described on page 47.
MAIN MENU
After entering the CPU IP address, selecting your system’s size, and exiting, the following window will appear, which is the Admin Console main menu. This window will be the first one you see from now on whenever you enter the Admin Console.
The main menu is the heart of the Admin Console configuration soft ware. Each component, sequence, setup, and management task will be accessed from this main window.
Each section will be utilized in order to configure and maintain th e SCS.
To view information about this application, such as the version of the software, click on the Panasonic logo. An “About” window will appear.
21 Admin Console CONFIGURATION
Page 22
DATABASE MANAGEMENT
The active database for this system is the one r esiding within the Surveillance Control System (SCS). Admin Console is used to create that database initially, and from that point forward works with copies of it in order to establish and maintain useful variations.
AT INSTALLATION
When Admin Console is first installed, an administrator must create and name a new database. The database is stored on the Admin Console computer’s hard drive.
The administrator then enters all the information available about frames, components, users, and sequences, and sav es these details into the database using the Database Manager.
Create a Database on page 23 for initial and subs equent d atabase
See
creations.
22
Page 23
Admin Console CONFIGURATION
Database Archive
The Database Archive section of the Database Manager window is where each configuration file (database) is manipulated. Several functions that can be performed with th e configuration files are selecting, creating, copyin g, rena ming, or dele ting.
This section also incl udes o ptions to backup or restore a configuration file to or from removable media or an alternate location, such as a floppy
diskette or network drive.
Select
New
Copy
Rename
Delete
Restore
Backup
Create a Database
Database Manager is entered in to b y clicking the first icon o n the “Management” row of the main menu – the picture of the open folder. When entering Database Manager for the first time, there will not be any .adm files listed, as none have yet been created. An administrator must create and name a new database for configuration.
1. Click on the Database Manager button on the main
menu.
23 Admin Console CONFIGURATION
Page 24
2. Click on the “New” button – the 2nd button under the
Database Archive section.
3. Type in a new name for the new database in this field
4. Click the green check mark.
Enter any name that f its in the space p rovided. It is best if the name is practical, and easy to understand by anyone using the system. You will be returned to the main menu after naming the database.
This database will reside in the Admin Console. Adding and saving information about the components and desired operation of the system will configure it.
Select a Database
VIEWING AND RECONFIGURING
Whenever you wish to view or edit settings from the components, sequences, or setup choices on the main menu, you must have the database whose contents you wish to work with open. If you have just entered Admin Console, and click on one of those options, you will automatically be prompted to select a database. The database you choose will open, and will immediately be followed by the option window you have chosen. The database you select becomes the default database for all settings until you go back to Database Manager to choose or create a different one.
1. Highlight the name of a database.
24
Page 25
Admin Console CONFIGURATION
2. Click the Select button - the 1st button under the
Database Archive section, or double click on the
desired database.
When changing the database you are working with, Admin Console will open the selected database, making it the default, and will close the Database Manager win dow. You will b e returned to th e main menu, ready for the configuration or review of the database you just selected.
Copy a Database
MAKING SIMILAR OR ALTERNATIVE DATABASES
An administrator can make copies of a database, as desired, and name them to reflect their purpose. This would normally be done to enable the system to respond to changing conditions and su rveillance needs with out having to completely recreate a database to accommodate these changes.
1. Highlight the name of the database you wish to copy
in the Database Manager window.
25 Admin Console CONFIGURATION
Page 26
2. Click the Copy button - the 3rd button under the
Database Archive section.
3. Name the copy in the space provided
4. Click the green check mark.
Enter any name that f its the sp ace provided. It is best if the name is practical and easy to understand by anyone using the system.
Rename a Database
Renaming a database is useful when creating several configurations to fit the needs of specific occasions, and changing the name to ensure each file has been updated. For example, if date codes or initials are used in the name or description of a database, an administrator may want to revise the date code or user initials as necessary.
1. To rename a database, highlight a database name.
26
Page 27
Admin Console CONFIGURATION
2. Click the Rename button - the 4th button under the
Database Archive section.
3. In the “Rename to:” box, type the new name desired.
4. Click the green check mark
Delete a Database
In order to reduce the number of configuration files listed in Database Manager, and thereby decrease the potential for confusion as to which file is loaded on the SCS CPU, outdated or unused configuration files can be deleted. If the files may be needed again in the future, it is recommended that you backup the files to an alternate location (
page 26), so they
see
can be deleted from the Admin Console, and restored later if necessary.
1. To delete a database, highlight the database name.
27 Admin Console CONFIGURATION
Page 28
2. Click the Delete button - the 5th button under the
Database Archive section.
The following confirmation message will appear:
3. Click Yes to delete, or No to cancel.
Backup or Restore a Database
It may be necessary at times to save a copy of a particular database for backup, e-mail, troubleshooting, or other purposes. The Admin Console allows an administrator to perform both backup and restore functions in order to maintain copies of the configuration files outside of the Admin Console system .
28
Page 29
Admin Console CONFIGURATION
BACKUP A DATABASE
1. Within Database Manager, highlight a database name
and click the Backup button - the 6
Database Archive section.
2. The following window will appear.
th
button under the
3. Choose the drive and folder you wish to backup to,
just as you would in Windows Explorer.
4. Click OK.
This procedure will only copy the highlighted configuration file to the specified location. It will not remove it from the Admin Console.
29 Admin Console CONFIGURATION
Page 30
RESTORE A DATABASE
In addition to backing u p a configuration f ile, it may also be necessary at times to restore a copy of a particular database from a backup, an e-mail, or from troubleshooting personnel. The Admin Console allows an administrator to perform a database restore from a source outside of the Admin Co ns ole .
1. Within Database Manager, click the Restore button -
the last button under the Database Archive section.
2. The following window will appear.
30
Page 31
Admin Console CONFIGURATION
3. Choose the drive and folder that contains the
desired .adm file, just as you would in Windows
Explorer.
4. Click OK.
Because you may have multiple files saved in the same location, the restore feature allows an administrator to choose which file to restore.
5. Select the desired file to restore, and click the green
check mark.
The left side of the Database Manager window represents the configuration files already stored within the Admin Console. The right side of the window represents the files stored in the folder that you have just specified.
This procedure will copy the selected configuration f ile into the Admin Console from removable media or an alternate location, but will not remove it from its current location.
31 Admin Console CONFIGURATION
Page 32
Get Current Database
In order to retrieve a copy of the configuration currently running on the SX850 system, and to bring it into the Admin Console, an administrator must retrieve it using the Database Transfer section’s “GET from CPU” option. This option allows the administrator to view, mod ify, copy, or create new versions of the current configuration once it is imported into the Admin Co ns ole.
1. From the pull-down menu in the Database Transfer
section select either Main A or Main B CPU.
2. Click the “GET from CPU” button - the left button
under Database Transfer.
3. Enter the new name for this particular database in the
“Save to:” box
4. Click the green check mark.
A copy of the database that is currently running on the selected SCS CPU is now saved on the Admin Console computer’s hard d rive. It will not be removed from the Main CPU. At this time, you may view or modify the configuration.
Load a Database
In order to copy a configured database from the Admin Console onto the SCS Main CPU, an administrator would need to use the Database Transfer section’s “PUT to CPU” option.
32
Page 33
Admin Console CONFIGURATION
Although not mandatory, first saving the current database residing on the CPU would allow for a comparison of any differences p rior to loading th e new database. (Unless this is a first tim e operation.)
Warning: Putting a configuration database onto the SCS CPU
will overwrite its entire existing database. It is recommended that you save the database currently running on the Main CPU under a distinctive name before loading a new database.
The following instruction will guide you through loading a database from the Admin Console to the CPU.
See
the
Get Current Database
section to save
the database that is curr ently loaded in th e CPUs.
1. Select the name of the database to load.
2. From the pull-down menu, select the proper CPU.
For a redundant CPU system, you must load the database onto both CPUs to insure they are each using the same configuration.
For single CPU system s, choose Main A.
3. Click “PUT to CPU” - the right button under the
Database Transfer section.
A “Confirm PUT Transfer” window will appear. If you choose to continue, the new database will be loaded, overwriting th e exiting database, and it will remain on the CPU to run the SCS according to the configuration.
4. Click Yes to continue the transfer, or No to cancel.
33 Admin Console CONFIGURATION
Page 34
Admin Console CONFIGURATION
System Configuration
The system (sys.ini) file resides on the main system CPU, and contains information that is critical for proper operation. On systems with a redundant CPU, it may be necessary to modify the system file on both of the SCS CPUs individually, in order to m aintain p roper o peration.
modify th is file u nless instructed to do so b y qualified p ersonnel.
NOT
DO
The Admin Console uses the System Configuration utility to allow an administrator to work with th is file. When instr ucted, follow the step s below for viewing, modifying, b acking up, and restoring the sys.ini file.
SYSTEM TRANSFER
When performing a file transfer in the System Configuration u tility, the system file is written to the Admin Console computer’s hard drive as Main A.ini and Main B.ini - depending on which CPU this function was performed. In most cases, the system file residing on the Admin Console computer’s hard drive will be an exact duplicate of the file being used on the system’s CPU( s).
It is possible for the file on the lo cal drive to differ from th e one being used by the system, when using the restore function. An administrator must be very careful when using the backup and restore functions, as well as when retrieving and replacing the system file on the CPU(s). It is very important that the administrator be aware of which CPU is being updated at all times.
35 Admin Console CONFIGURATION
Page 35
RETRIEVE SYSTEM FILE FROM MAIN CPU
1. From the CPU System Configuration window (accessed from
the CPU icon from the main menu’s Setup row), click on the
SYS tab on the right side of the window.
2. The following window will appear.
3. Choose from the SYS Transfer pull-down menu “Main A”.
4. Click the “GET from CPU” button – the left button under SYS
Transfer.
The Admin Console will retrieve the system file from the selected CPU, and display it in the window p rovided.
At the same time, the system file is saved in the Program Files\Panasonic\SX850ac folder as “Main A.ini” (or Main B.ini if from the redu nd ant CPU) .
36
Page 36
Admin Console CONFIGURATION
5. Modify the system file as needed.
Modifications will not be saved on the Admin Console computer’s h ard drive until a “PUT to CPU” is performed, which replaces the system file in the CPU selected.
“Replace System File in Main CPU” below, in
See
order to send the updated f ile information to th e system CPU.
REPLACE SYSTEM FILE IN MAIN CPU
1. From the CPU System Configuration window (accessed from
the CPU icon from the main menu’s Setup row), click on the
SYS tab on the right side of the window.
2. Choose from the SYS Transfer pull-down menu “Main A”.
3. Click the “PUT to CPU” button – the right button under SYS
Transfer
This will replace the exiting system file in the specified CPU with the modified one.
4. A “Confirm PUT Transfer” windows will appear. Click Yes to
continue with the transfer, or No to cancel the transfer.
5. Repeat steps 3-8 for Main B CPU, as needed, selecting “Main
B” from the pull-down menu in steps 3 and 8.
Note: It will be necessary to reboot each CPU when finished so
that the updated information is read and executed correctly.
Warning: Main A and Main B system files differ slightly. It is
not recommended that identical system files be loaded into both Main A and Main B CPUs.
37 Admin Console CONFIGURATION
Page 37
SYSTEM ARCHIVE
After the Main A and Main B CPU system files have been retrieved for the first time, it will be possible to view th ese files at a later date without actually performing a transfer. These files (Main A.ini and Main B.ini) will be stored in the Program Files\Panaso nic\SX850ac folder on the Admin Console computer’s hard drive.
Select
In order to view the system file stored on the Admin Console computer’s hard drive
1. From the CPU System Configuration window (accessed from
the CPU icon from the main menu’s Setup row), click on the
SYS tab on the right side of the window.
2. Choose from the SYS Archive pull-down menu “Main A”.
3. Click the Select button.
38
Page 38
Admin Console CONFIGURATION
Backup
After the Main A and Main B CPU system files have been retrieved for the first time, it will be possible to save th ese files to a different location, such as to floppy diskette. These files (Main A.ini and Main B.ini) are stored in the Program Files\P anasonic\SX8 50ac folder o n th e Admin Console computer’s hard drive. Performing a backup from the SYS Archive section will save a copy of the specified system file to an alternate location of your choice.
1. Choose from the SYS Archive pull-down menu “Main A”.
2. Click the Backup button under the SYS Archive section.
3. When the “Browse for Folder” window appears, browse to
the desired location.
4. Click the OK button.
5. Repeat for “Main B” system file.
Restore
39 Admin Console CONFIGURATION
Page 39
At some time, it may be necessary to restore or replace the current system files with a saved (backed up) version, for example, during system troubleshooting. The restore function will copy the Main A.ini and Main B.ini files from the location you specify, and put them into the Program Files\Panasonic\SX850ac directory on the Admin Console computer’s hard drive.
1. Choose from the SYS Archive pull-down menu “Main
A”.
2. Click the Restore button under the SYS Archive
section.
3. When the “Browse for Folder” window appears,
browse to the location that the saved system file
resides.
This would the location you backed the file up to.
4. Click the OK button.
The system file (Main A.ini) th at is stor ed in the Program Files\Panasonic\SX850ac folder will be replaced with the file from th e location that you specified.
5. Load the restored file into the Main A CPU if desired.
“Replace System File in Main CPU” section on page 34.
See
6. Repeat for “Main B” system file, choosing “Main B” in
step1.
Wizard
When you want to make changes to the system file’s [System] sectio n ­which defines the values for Cameras, Monitors, and Keyboards - you can use the wizard function in the SYS Archive section o f the CPU Configuration Window to do this automatically.
If the values for these components already exist in your system file, they will be edited, if necessary, to reflect the recommended settings. If the values for these components do not already exist in your system file, the wizard will add them to th e system file.
1. Choose from the SYS Archive pull-down menu “Main
A”.
2. Click the Wizard button under the SYS Archive section.
40
Page 40
Admin Console CONFIGURATION
3. When the Confirm window opens for you to confirm
the changes to be made, click Yes to continue and
edit the file, or click No to cancel the wizard function.
The Wizard button’s appearance will change to indicate if any changes to the system file are recommended. The gauge ar ea on the lef t side o f this icon indicates if the [System] components’ settings are: A) too low for the CPU size selected (yellow), B) matching the CPU size selected (yellow and green), or C) too high for the CPU size selected (yellow, green, and red).
Too low for CPU
setting
Matches
CPU
setting
Too high
for CPU
setting
When the icon displays yellow and green, indicating that the settings match the CPU size selected, there is no action required. If the icon indicates settings ar e too low or too high, click the Wizard button to have the settings changed to match your system. You will then be prompted to confirm that you want the suggested modifications of the system file to take place.
INPUT TO SCREEN
You will begin configuring the database with these Setu p row buttons off the main menu:
Matrix Frame
41 Admin Console CONFIGURATION
Areas
CPU
Configuration
Event
Scheduler
Page 41
SCS CPU Configuration
This configuration has already been made at the end of CPU Setup on page 17. If this needs to be changed, r e turn to CPU Setu p starting on page 15.
Tip: The title bar of each option window you enter will show
the name of the main menu option being displayed, followed by the name of the current default database (.adm) file being viewed or edited. In the case below, the option being displayed is matrix frames, and the database file being used is std.adm.
Main menu
option you are
working with.
Database (.adm)
file you are
working with.
Matrix Frames
These processor nodes provide access to the system’s matrix-switching devices.
DEFINITION
1. Click on the Matrix Frame button on the main menu.
42
Page 42
Admin Console CONFIGURATION
Note: Each field preceded by purple text must be given a unique
number - different from other configured frame records.
2. Click the Add Record button.
3. Enter all information required about each Matrix Frame.
MATRIX FRAMES - Definition
Field Data
ID Unique record ID assigned by the Admin Console as a frame is
added, in order to identify one frame to the system. 1 to 1,098.
The Admin Console automatically generates this number in consecutive order. Upon adding frames, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers.
Sys ID Usually the number 1. In the case of a very large physical installation,
such as an airport with several buildings, the surveillance system may be divided into several smaller systems — with numbers 2, 3, etc. assigned by an SCS administrator.
I/F Numeric Ethernet interface number identifying a port on a CPU where
the matrix frame will connect. 0 to 15, though generally 0, 1, or 2.
IPA Unique Internet Protocol address assigned by the system
administrator. Dotted decimal, 15 characters. Example:
128.010.050.125
43 Admin Console CONFIGURATION
Page 43
MATRIX FRAMES - Definition
Field Data
Name A name for the matrix frame, easy to remember, and practical.
Alphanumeric, 16 characters.
Boot The name of the file used by the frame’s booting process. Use the
default filename unless instructed to do so by qualified personnel.
Be sure to check a frame type first, such as controller, OSD, switch, or alarm I/O so that the default frame boot name will be filled in automatically.
If the boot name field is filled in before the type is selected, the default boot name will not be inserted.
Location A name for the matrix frame, easy to remember, and practical.
Alphanumeric, 16 characters.
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
MXCONT
MXOSD
MXALM Check if one (or more) Alarm Input WJ-PB85A32 or Alarm Output
LCPU Address Set the matrix frame LCPU identifier on the rotary switches SW12,
Check if one (or more) WJ-PB85X08 input cards is installed. If MXCONT (camera control function) is ’d, then select range of
numbers in Input Ports.
This range will be unique to the entire frame for the controller function, regardless of the number of input cards installed within the frame.
Check if one (or more) WJ-PB85T0B OSD cards is installed. If MXOSD (on screen display function) were ’d, you would need to
select a range of numbers in Output Ports.
This range will be unique to the entire frame for the OSD function regardless of the number of OSD cards installed within the frame.
MXSW Check if one (or more) WJ-PB85C16 video crosspoint input cards
and WJ-PB85M16 video crosspoint output cards are installed. If MXSW (switching function) were ’d, you would need to select a
range of numbers in Input Ports and Output Ports.
These ranges will be unique to the entire frame for the switching function regardless of the number of input or output cards installed within the frame.
WJ-PB85L32 card(s) is installed in this frame. If MXALM (alarm I/O function) is ’d, then select a range of numbers
in I/O Ports.
This range will be unique to the entire frame for the alarm I/O function, regardless of the number of alarm I/O cards installed within the frame.
SW10, and SW9. 0-0-1 to F-F-F.
4. Click the green check mark to save.
You will remain in the “Add” mode, allowing you to enter information about another frame.
5. To exit the “Add” mode, click the red X.
You will exit the “Add” mode.
6. To edit a configured frame, highlight a frame ID and click the
Edit button.
44
Page 44
Admin Console CONFIGURATION
Tip: You may also double click on a frame ID in the list to enter
the edit mode.
7. Edit the desired fields.
8. Click the green check mark to save and exit the edit mode, or
click the red X to cancel.
9. To delete a frame, highlight a frame ID and click the Delete
Record button.
A confirmation m essage will appear. Click No to cancel, or click Yes to delete the selected frame.
45 Admin Console CONFIGURATION
Page 45
COMPONENTS
Each one of these buttons opens a window that re quires information from one or more of the Setup Worksheets that you have completed.
Input the required information for each of these components separately: cameras, system controllers, monitors, alarm I/O ports, alarms, and operators.
Cameras
(System)
Controllers
Monitors (Alarm)
I/O Ports
Alarms Operators
46
Page 46
Admin Console CONFIGURATION
Cameras
Every camera in the system can be identified in several ways. Not only is there a physical identification to a p articular installation ( such as th e cabling run and port connection), but there is also in formation that changes when a camera is removed and/or is replaced at any given location. Each camera has a record that contains its details.
An operator calls a camera by its logical camera number. However, configurations can be viewed in the Admin Console not only by logical number, but also by ID number, control port, or video port.
DEFINITION
OR
Add, delete, edit, or replicate camera records as necessary using the four icons at the bottom of this win dow.
Note: When deleting or modifying a camera, be sure to check
the “Other” tab to find references to other sections that the camera will influence.
47 Admin Console CONFIGURATION
Page 47
Warning: Deleting a camera will automatically delete the
referenced permissions, but will not change any other references, such as sequences or alarms.
CAMERAS – Definition
Field Data
ID Unique record ID assigned by the Admin Console as a camera is
added, in order to identify one camera to the system. 1 to 8,192.
The Admin Console automatically generates this number in consecutive order. Upon adding cameras, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers.
Sys ID Usually the number 1. In the case of a very large physical installation,
such as an airport with several buildings, the surveillance system may be divided into several smaller systems — with numbers 2, 3, etc. assigned by an SCS administrator.
Logical Unique number assigned by an SCS administrator, usually designated
by combining two references, such as having the first 2 digits represent a logical group (such as a group of cameras surveying a loading dock), and up to three serial digits assigned for other logical
001, 84002, 84003, 84004;
Model Choose from the drop-down list the correct camera model connected
Ports:%%%%%%%%%%%%
Control Name/number of the input port on the Video Input Board WJ-PB85X08
Video Name/number of the input port on the Video Crosspoint Input Board
reasons. 1 to 99,999. Examples: 84
001, 36002, 36003, 36004. An operator will select cameras to
36 view by this logical number.
to the specified ports. The Admin Console will automatically enable the features available with the specific camera model, such as pan/tilt, iris control, motion detection, configuration menu, control data, zoom/focus, presets, VD2 synchronization, RS485, or function codes.
If the desired camera model is not listed, choose <Other>. Enable the appropriate features manually, according to the manufacturer’s camera description, by checking the associated check boxes.
Check the “control data” box when a control data signal should be sent to the camera.
When RS485 is chosen, the Cfg (configure) button will become enabled. Click the Cfg button to configure the RS485 port for the following settings: baud rate, parity, data length, stop bits, daisy on/off, and choosing a 2 or 4 wire connection.
Matrix Control (MXCONT) function to which the camera cable is connected. 1 to 8,192.
WJ-PB85C16 Matrix Switch (MXSW) function to which the output of the WJ-PB85X08 card is connected. 1 to 8,192.
48
Page 48
Admin Console CONFIGURATION
CAMERAS – Definition
Field Data
Video Signal%%%%%
Compensation: Cable length from camera to the video import board: short, medium, or
long. The system compensates for these three values by modifying the signal strength.
Loss Threshold
On-Screen Display
Location Practical name to help an administrator identify a camera by location.
Enter a signal level at which the system will detect video loss. 0 to 15.
Enter an alphanumeric Title to be displayed.
Chose the device that generates the time and date (T&D), the camera ID (ID), and the Title specified. Choose either MXOSD or MXCONT for each of the three components of the display.
If a WJ-PB85D01 character generator daughter board is installed on the Control Video Input Board WJ-PB85X08 you can choose MXCONT for some or all of the generation, otherwise, choose MXOSD.
Alphanumeric, 16 characters. Examples: main concourse, loading dock, boiler room.
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
49 Admin Console CONFIGURATION
Page 49
REPLICATE A CAMERA DEFINITION
1. Highlight a configured camera ID and click the
Replicate Record button.
A confirmation m essage will appear asking “Are y ou sure you want to REPLICATE this camera?” and explaining the replication rules.
[1] Records will be generated according to ID. [2] ID will be incremented to the n ext available value. [3] Logical #, Control & Video Ports will be incremented f rom a
specified base value you assign. [4] If a record already exists with a matching value for any of these
unique fields, that Target assignment will b e skipped [5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel.
3. Enter the desired amount of camera records to create
in the Target Size box.
4. Enter the beginning Base Values of the logical camera
number, control port, and video port from where you
wish to begin incrementing.
5. Click the green check mark to add the series of
cameras, or click the red X to cancel.
Note: After clicking the green check mark, a Replication Summary
window will appear, which will let you know how many records were actually generated, and indicate if any records could not be created due to a conflict with an exiting record. If any of the required unique v alues involved are already in use, the entire record will be skipped; existing records will not be overwritten.
If a conflict exists, you will be asked if you wish to see a list of the records that were skipped. Click Yes to see the Replication Activi ty Log list, or click No if you do not wish to see the list. It is recommended that
50
Page 50
Admin Console CONFIGURATION
you view the list, so that you can modify the conflicting value(s) as necessary, and add the record(s) you desire.
51 Admin Console CONFIGURATION
Page 51
PERMISSIONS
The permission tabs allow an administrator to easily permit or deny components’ access to o ther components.
By default, all components are allowed to access all other components. An administrator must deny permissions.
1. Highlight a camera and click on the Cam Ctrl
permission tab.
The
Cam Ctrl
permission tab allows an administrator to permit or deny a system controller to control specific cameras. The Modes section of this tab is described on page 18.
Note: Allowing a system controller to control a certain camera
will automatically allow the same controller to view the
specified camera.
Cameras are displayed in th e list on th e left by ID number, b ut can also be viewed by logical number, control port, or video port. The grid on the right represents the f ollowing:
First row = controller IDs 0-9, second row = controller IDs 10-19, etc.
52
Page 52
Admin Console CONFIGURATION
Green blocks indicate an allowed permission, and white blocks indicate that permission is denied.
2. Double click on a specific controller to invert or
alternate between permit or deny.
Note: Be sure to click the save button (the picture of the floppy
disk) before exiting each particular permission tab to ensure the changes will be saved correctly.
3. Highlight a row, a column, or click and drag to
highlight a group of controllers.
4. Click the Invert Grid Selection button to change the
state of the permission for the highlighted group, or
5. Click on the Permit All button to turn the entire grid
green – allowing all controllers permission to control
the specified camera, or
6. Click on the Deny All button to turn the entire grid
white – denying all controllers permission to control
the specified camera, or
7. Click on the Copy Grid button to copy the permission
grid from a specific camera to other cameras.
Warning: Copying Cam Ctrl permissions to other cameras will
also copy Cam View permissions to the specified cameras.
A confirmation m essage will appear asking “Are y ou sure you want to COPY the Cam Ctrl & Cam View permission for this Camera?” and explaining the copying rules.
[1] Permissions will be copied by Camera ID. [2] If permission already exists for a Camera th at falls within the T arget
range, that original permission will be overwritten.
8. Click Yes to continue or No to cancel.
53 Admin Console CONFIGURATION
Page 53
The copy source is the highlighted camera ID from where the Cam Ctrl permissions will b e copied.
9. Enter the Target ID range of camera ID numbers, with
the beginning number in the START box, and the
ending number in the END box.
Warning: Permissions existing for cameras within the specified
range will be overwritten.
10. Repeat steps 1-9 for all other permission tabs.
The
Cam View
permission tab allows an administrator to permit or deny
a system controller to view specific cameras. The Modes section of this
Warning: Denying a system controller to view a certain
camera will automatically deny the same controller to control the specified camera.
tab is described on page 18. The
Monitor
permission tab allows an administrator to permit or deny a camera the ability to be displayed on a monitor. A monitor ID can be determined by its area\local number by entering each value into the appropriate box, and then clicking the “Search for Monitor by Area & Local” button.
11. Component Definition button.
Highlight a component within the permission grid, and click the definition button. A window will appear; giving a quick view of that component’s configured definition.
54
Page 54
Admin Console CONFIGURATION
This button is available in each of the permission tabs for each component, on the “Other” tab in the Cameras window, and the Areas window.
12. Click on the “x” in the upper right corner to close.
OTHER
The “Other” tab shows which other SCS components or sequences are configured to include the highlighted camera.
This section is informational only. Changes cannot be made to other components or sequences from this window. Changes must be made from each specific component o r sequence’s menu option.
On the image below, for example, tour sequence n umber 1 is configured to include camera ID 1. The tour sequence section of this tab for camera ID 1 was automatically upd ated when to ur sequence 1 was cr eated to include this camera. To remove camera 1 from tour sequence 1, you would need to exit the Cameras window, and enter the Tour Sequences window from the main menu, and edit sequence number 1.
55 Admin Console CONFIGURATION
Page 55
CAMERA POSITIONS
An operator, from a system controller, can control each camera in the system that supports Presets by pressing th e Camera Positio n button o n the controller. The operator cannot define positions, but rather, can only recall positions (which are a combination of Camera ID and CPreset numbers) that have already been defined.
The Camera Positions setting in Admin Console allows administrators to define and consolidate the Camera ID and CPreset numbers into a Position ID number that the operator can then conveniently call from the system controller .
56
Page 56
Admin Console CONFIGURATION
1. Click on the down arrow in the lower right corner of the
Cameras icon on the main menu, and choose Positions.
The Position ID is automatically inserted and in cremented by the application.
2. Enter a Logical number for the position record you are
creating.
3. Click in the Camera field. A list of available cameras
that support Presets will appear on the right of this
window.
4. Choose the desired camera by double-clicking on its
ID number.
5. Click in the CPreset field and type in the desired
preset number.
6. Click in the Scene field and enter a description of the
camera view in that position, if desired.
You can add, edit, delete, or replicate Position IDs as n eeded using the four icons at the bottom of this win dow.
57 Admin Console CONFIGURATION
Page 57
System Controllers
A system controller is a device used by an operator to control specific components within the SCS, such as: cameras, monitors, alarms, alarm outputs, etc. Controllers ar e generally identified to an operator using their ID number, but can be viewed in the Admin Console by ID, IPA, EA, or Area.
DEFINITION
Add, edit, or delete controller records as n ecessary using the three icons at the bottom of this window.
58
Page 58
Admin Console CONFIGURATION
SYSTEM CONTROLLERS – Definition
Field Data
ID Unique record ID assigned by the Admin Console as a system
controller is added, in order to identify one controller to the system.
The Admin Console automatically generates this number in consecutive order. Upon adding controllers, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 128.
Area Unique number identifying a Monitor Surveillance Area (MSA)
comprised of an array of monitors and one or more keyboard controllers. 1 to 128
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor. It is recommended that the use of areas be restricted to values of 1 to 128. Only use area “0” when no areas are needed within the entire system.
Click the Area button on the main window to view all components defined in a specific area.
Priority This number assigns this controller an order of precedence. Applies
only when operator priorities are the same. The controller with the lower number priority takes over the part of the system it is addressing.
If more than one controller with the same priority is operating at the same time, access is given and held for the latest call to a function, in other words, on a last-come first-served basis. Alarm priorities have precedence over operator priorities. 0 to 65,534.
Boot File The name of the file used by the Ethernet keyboard’s boot process.
Use the default filename unless instructed otherwise by qualified personnel. Alphanumeric, 12 characters.
Be sure to select WV-CU850 Controller type FIRST so that the default boot name will be filled in automatically. This is the only system controller type that will require a boot name.
If the boot name field is filled in before WV-CU850 type is selected, the default boot name will not be inserted.
Timeout Amount of time that must elapse after the user stops entering
keystrokes, before the system logs off the operator from this controller. (hr:min:sec) 00:00:00 to 11:59:59
The controller timeout works in conjunction with the operator timeout. The system will choose the lowest timeout value of the two.
Entering a “0” into this field will cause the timer to never expire regardless of the operator timeout value.
Model Pull-down and select the correct type of system controller. This will
enable or disable fields that are specific to each particular controller. CU350 (RS485), CU850 (Ethernet), PFW100 [CU350] (RS485), PFW100 [CU850] (Ethernet), PFW850 (Ethernet), RS232 (serial), or ActiveX.
59 Admin Console CONFIGURATION
Page 59
SYSTEM CONTROLLERS – Definition
Field Data
IPA Unique Internet Protocol Address assigned by the system
administrator. Dotted decimal, 15 characters. Example:
128.010.050.125. Each of the four groups of numbers with values between 0 and 255.
Depending on the model number chosen, the following will apply:
WV-CU350: If this controller is not connected to an RS485 Expander Unit, use the default IPA. If this controller is connected to an RS485 Expander Unit, enter the IPA for the expander unit.
WV-CU850: A unique IPA is necessary within the scheme of the MCPU interface IPA.
PFW100 [CU350]: Same as the WV-CU350.
PFW100 [CU850]: Same as the WV-CU850.
PFW850: Enter the IPA of the desktop computer the PFW850 is
installed, making sure it is within the scheme of the MCPU interface IPA.
RS-232: If this controller is not connected to an RS485 Expander Unit, use the default IPA. If this controller is connected to an RS485 Expander Unit, enter the IPA for the expander unit.
ActiveX: Enter the IPA of the desktop computer that ActiveX is running from, making sure it is within the scheme of the MCPU interface IPA.
EA Numeric address for an Ethernet controller. This field is only required
if Model WV-CU850 is chosen. Dotted hexadecimal Example:
23.56.82.13.60.82 (Also known as MAC address.)
Port Numeric identifier of the port used by an RS-485 controller (CU350
and PFW100A) (port 1-12) or RS232 controller (Port 1,2, or 3). Match the data port that this keyboard is connected and use the proper IPA for the MCPU default or RS485 Expander Unit.
This port address will be unique within the IPA specified for the MCPU or RS485 Expander.
Location A practical name that will identify where this controller can be found.
Alphanumeric, 16 characters.
Name A name for the controller, easy to remember, and practical.
Alphanumeric, 16 characters.
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
60
Page 60
Admin Console CONFIGURATION
PERMISSIONS
Modify or copy system controller permissions in the same manner described in the Camera Permissions section, beginning on page 52.
The
Cam Ctrl
permission tab allows an administrator to permit or deny a system controller the ability to control specific cameras. The Modes section of each of the permissions tabs is described on page 18.
Note: Allowing a system controller to control a certain camera
will automatically allow the same controller to view the
specified camera.
Warning: Copying Cam Ctrl permissions to other system
controllers will also copy Cam View permissions to the
specified controller.
The
Cam View
permission tab allows an administrator to permit or deny
a controller to v iew specific cameras.
Note: Denying a system controller to view a certain camera will
automatically deny the same controller to control the specified camera.
The
Monitor
permission tab allows an administrator to permit or deny a controller’s ability to seize a specific monitor. A monitor ID, if unknown, can be determined by its area and local number, by entering each value into the appropriate boxes, and then clicking the “Search for Monitor by
Warning: Copying Cam View permissions to other system
controllers will also copy Cam Ctrl permissions to the specified controllers.
Area & Local” button. The
Group Seq
permission tab allows an administrator to permit or deny a controller’s ability to control a group sequence. If the group sequence ID is unknown, you can enter the area and local numbers of the sequence
61 Admin Console CONFIGURATION
Page 61
in the appropriate boxes, and click th e “Search for Group Seq by Area & Local” button.
The
Alarm
controller’s ability to seize a specific alarm. The
Alarm I/O
a controller’s ability to seize a specific IO port.
permission tab allows an administrator to permit or deny a
permission tabs allows an administrator to permit or deny
62
Page 62
Admin Console CONFIGURATION
Monitors
Monitors are generally viewed within the Admin Console by ID number, but can be viewed by area\local number, since the user will operate the SCS by selecting a monitor b y local number within a specific area.
Area\local numbers are displayed in the Admin Console as one whole number. The four right-most digits represent the local number and the left-most one, two, or three digits will represent the area. For example, 10034 represents area 1 and local number 34, or 251100 represents area 25 and local number 1100.
DEFINITION
Add, edit, delete, or replicate monitor records as needed using the four icons at the bottom of this win dow.
63 Admin Console CONFIGURATION
Page 63
Note: When deleting or modifying a monitor, be sure to check
the “Other” tab to find references to other sections that the monitor will influence.
Note: When changing the Monitor Surveillance Area (MSA) of a
monitor, make sure that any affected presets or alarm action target assignments are within the same area.
Warning: Deleting a monitor will automatically delete the
referenced permissions, but will not change any other references, such as sequences, presets, etc.
MONITORS – Definition
Field Data
ID Unique record ID assigned by the Admin Console as a monitor is
added, in order to identify one programmed monitor of to the system.
The Admin Console automatically generates this number in consecutive order. Upon adding monitors, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 1,024.
Area Unique number identifying a Monitor Surveillance Area (MSA)
comprised of an array of monitors and one or more keyboard controllers. 1 to 128.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
It is recommended that the use of areas be restricted to values of 1 to
128. Only use area “0” when no areas are needed within the entire system.
Click the Area button on the main window to view all components defined in a specific area.
Local Unique number assigned by an SCS administrator, enabling operators
to address this particular monitor within an area. 1 to 9,999.
Operators will address specific monitors by selecting the local number with an area.
Location Practical name indicating where this monitor is located.
Alphanumeric.
Model Monitor model number assigned by its manufacturer.
Alphanumeric.
Ser. Monitor serial number assigned by its manufacturer.
Alphanumeric.
64
Page 64
Admin Console CONFIGURATION
REPLICATE A MONITOR DEFINITION
1. Highlight a configured monitor and click the Replicate
button.
A confirmation m essage will appear asking “Are y ou sure you want to REPLICATE this monitor within this Area?” and explaining the replication rules.
[1] Records will be generated according to ID. [2] ID will be incremented to the n ext available value. [3] Local # will be incremented from a specified base value you assign. [4] If a record already exists with a matching v alue for any of these
unique fields, that Target assignment will b e skipped [5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel.
Note: Monitors can only be replicated within an area. If you
wish to replicate monitors in several areas, at least one monitor must be configured in each area.
3. Enter the desired amount of monitors to create in the
Target Size box.
4. Enter the beginning base value if the local monitor
number that you wish to begin incrementing from.
5. Click the green check mark to add the series of
monitors, or click the red X to cancel.
After clicking the green check mark, a message will appear letting you know how many records were actually generated, indicating if any records were skipped.
note section of page 45.
See
Warning: Monitors existing within the specified range will not
be overwritten.
65 Admin Console CONFIGURATION
Page 65
PERMISSIONS
Modify or Copy Monitor permissions in the same manner described in the
Camera
Permissions section, beginning on page 52.
The
Camera
permission tab allows an administrator to permit or deny a
monitor the ability to display a specific camera. The
Controller
permission tab allows an administrator to permit or deny a system controller the ability to seize a specific monitor. The Modes section of this tab is described on page 18.
OTHER
The “Other” tab will represent additional sections that a highlighted monitor will affect.
This section is informational only, and changes cannot be made to the Group Sequences, Group Presets, or Targets the specified monitor will affect. Changes must be made within the specific Group Sequence/Preset windows, accessed from their respective main menu options.
66
Page 66
Admin Console CONFIGURATION
Alarm Input/Output
Alarm input and alarm output ports are used for alarm action purposes, and although each has a specific function, both are configured within this section. Each I/O card supplies 32 relay circuits in banks of 8. Because of this, 8 consecutive IDs must be configured with the same directional type - either input or output. For example, if ID 1 is configured as an input port, then IDs 2-8 must be input ports as well.
Then, port 9 through port 16 can be configured as output ports if desired. The port type option b uttons will be grayed o ut until a group of 8 ports is configured.
Although the system controller o perator must control the I/O ports by logical number, these ports are viewable within the Admin Console by both ID and logical port numbers.
DEFINITION
Add, Edit, Delete, or Replicate alarm I/O p ort records as needed u sing the four icons at the bottom of this win dow.
67 Admin Console CONFIGURATION
Page 67
A l a r m I/O PORTS – Definition
Field Data
ID Unique record ID assigned by the Admin Console as an I/O port is
added, in order to identify one port to the system.
The Admin Console automatically generates this number in consecutive order. Upon adding I/O ports, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 1,024.
Logical Assigned by an SCS administrator, enabling operators to address this
port. An operator will select alarm I/O ports by logical number. 1 to 65,534.
Type Click on either Input or Output. Input Example: Fire exit door opening.
Output Examples: Unlock/lock a door. Alarm to firefighters. Call for
police. Call for medical rescue.
Each type must be configured in groups of 8.
Dwell Time Time available for a momentary output. Up to 59:59.999
(min:sec.millisec)
Dwell time will only be enabled for output type I/O circuits.
68
Page 68
Admin Console CONFIGURATION
REPLICATE AN I/O PORT DEFINITION
1. Highlight a configured port and click the Replicate
Record button.
A confirmation m essage will appear asking “Are y ou sure you want to REPLICATE this port?” and explaining the replication rules.
[1] Records will be generated according to ID. [2] ID will be incremented to the n ext available value. [3] Logical # will be in cremented from a specified base value you assign. [4] If a record already exists with a matching v alue for any of these
unique fields, that Target assignment will b e skipped [5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel.
3. Enter the amount of ports to create in the Target Size
box.
4. Enter the beginning Base Value of the logical port
number that you wish to begin incrementing from.
5. Click the green check mark to add the series of ports,
or click the red X to cancel.
After clicking the green check mark, a message will appear letting you know how many records were actually generated, indicating if any records were skipped.
Warning: I/O ports existing within the specified range will not
be overwritten.
note section page 45.
See
69 Admin Console CONFIGURATION
Page 69
PERMISSIONS
Modify or copy I/O port permissions in the same manner described in the
Camera
Permissions section, beginning on page 52.
The
Controller
permission tab allows an administrator to permit or deny a system controller the ability to seize a specific I/O port. The Modes section of this tab is described on page 18.
The
tab shows which Alarm ID numbers are using a particular
Other
Alarm I/O port.
70
Page 70
Admin Console CONFIGURATION
Alarms
Alarms play an important role within an SCS. Alarms can automatically trigger up to ten actions, such as camera spots, tour sequences, or group sequence, in any combination. These actions allow the system to open or close a contact connected to an I/O port that will start a siren or poss ibly turn on a spotlight. They also can alert the operator on a monitor during a triggered alarm.
In order to configure alarms successfully, an administrator must first create the alarm targets, and then create re cords that will in itiate th e actions. Targets are defined as a group of monitors. The alarm actions are then linked to available alarm targets.
The following are rules to follow when configuring alarms:
An alarm can invoke up to ten actions.
A monitor can be a member of only one target.
A target can contain several monitors exclusively.
Many targets can be linked to each alarm.
The same target can be assigned to more than one
alarm.
Defining an alarm can be a cumbersome task. ID numbers identify each alarm, source, action ty pe, and target. The following p rocedure will explain each step so that an alarm target can be defined, an alarm can be identified by the source, actions can be taken when the alarm is triggered, and a target can be defined and assigned to display the specified action.
71 Admin Console CONFIGURATION
Page 71
ALARM TARGET
An alarm target is an ID number that defines a group of one or more monitors.
Alarm targets are assigned to alarms in order to link alarm actions to specific monitors. At least one alarm target must be created before you can create an alarm.
When an alarm is triggered, an action will occur. For example, causing a camera spot (configured in th e alarm definition) to display on an array o f monitors assigned to a specific target.
Warning: Be careful when assigning monitors across areas to
the same target. This will be important when assigning a target that contains monitors in a different area than the Alarm Action Tour Sequence.
1. Click on the down arrow in the lower right corner of the
Alarms icon on the main menu, and choose Target Setup.
2. Click the Add Record button to add a target record.
72
Page 72
Admin Console CONFIGURATION
3. Double click on each monitor ID that you wish to add to
this target record.
As you double click on a monitor ID number’s corresponding box, the representative box will turn green, indicating that it is now part of this record.
First row = monitor IDs 0-9, second row = monitor IDs 10-19, etc. Besides choosing which m onitors will be part of a specific target ID, you
must also choose either Hold or Sequence from the Display Mode section of this window to define the display mode for the entire target record. “Hold” is chosen if you wish to have alarms display on only one monitor, with additional alarms in queue for that m onitor. “Sequence” is chosen if you wish to have alarms display on a sequence of monitors.
4. Click the green check mark to add the series of monitors,
or click the red X to cancel.
Tip: The permission grid is shown by monitor ID only.
Note: A monitor can only be a member of one target.
Therefore, when adding additional targets, monitors that are already assigned to a different target appear as yellow blocks. Green blocks indicate monitors assigned
73 Admin Console CONFIGURATION
Page 73
to the highlighted target ID. White blocks are either unassigned or undefined monitor IDs.
Note: In order to re-assign a monitor to a different target, you
must first remove the specific monitor from its current target, thus making it available for re-assignment. You can determine what target ID is it currently assigned to by clicking on it and seeing the ID number that appears in the Target box under the grid.
The “Other” tab shows the alarm(s) that the selected target is assigned to. Targets are assigned to alarms from the Target tab of the Alarms (Records) window as described below.
Use the Edit Record o r Delete Record icons at the bottom o f this window to edit or delete alarm target records as needed.
Note: Targets cannot be deleted if they are assigned. The
assignment must be removed from the Alarms window prior to deleting it.
ALARM DEFINITION
An alarm record is defined by either clicking on the Alarms icon from the main menu, or clicking on the down arrow in the lower right corner of the Alarms icon and choosing Records. An Alarm Target must be created before an alarm can be defined.
74
Page 74
Admin Console CONFIGURATION
Add, edit, or delete alarm records as needed using the three icons at the bottom of this window.
Alarms – Definition
Field Data
ID Unique record ID assigned by the Admin Console as an alarm is
added, in order to identify one alarm to the system.
The Admin Console automatically generates this number in consecutive order. Upon adding alarms, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 1,024.
Logical Unique number assigned by an SCS administrator. An operator will
view alarms by this logical number.
75 Admin Console CONFIGURATION
Page 75
Alarms – Definition
Field Data
Priority Level that determines an order of precedence between alarms. Alarm
priorities work in conjunction with the operator priority and determine the order of precedence between alarms and operators. (Smaller number has higher priority)
Enable Defines whether or not an alarm is enabled. Check the box to enable
the specific alarm.
Auto Arm If checked, the specified alarm will automatically re-arm itself after
being acknowledged
Allow Disarm
One State If checked, the specified alarm, once triggered, will not be monitored
Output Port:
If checked, operator will be allowed to disarm the specified alarm.
for its return from the triggered state.
This is useful when you are only concerned that the alarm was triggered, but do not need to know the duration of the triggered state.
An alarm set for One State can be reset even if the alarm condition still exists. Without this option checked, if an alarm is triggered and you attempt to reset it, it will continuously trigger again until the triggered state has ended.
Active If checked, the indicated output port will be turned ON when this alarm
is active.
If not checked, the indicated output port will be turned OFF when the alarm is active.
Enter an output port number to specify which port will be turned ON or OFF when the alarm is active.
If no output port action is required when the alarm is active, uncheck and leave the output port number blank.
Ack If checked, the indicated output port will be turned ON when this alarm
is acknowledged.
If not checked, the indicated output port will be turned OFF when the alarm is acknowledged.
Enter an output port number to specify which port will be enabled when the alarm is acknowledged.
If no output port action is required when the alarm is acknowledged, uncheck and leave the output port number blank.
Reset If checked, the indicated output port will be turned ON when this alarm
is reset.
If not checked, the indicated output port will be turned OFF when the alarm is reset.
Enter an output port number to specify which port will be enabled when the alarm is reset.
If no output port action is required when the alarm is reset, uncheck and leave the output port number blank.
Source: %%%%%%%%%%
Type Identifies the source of the specified alarm, camera (motion detection),
or I/O (external source connected to an alarm input card), RS232 (external source connected to an RS232 port), Vid Loss (any) (detects video loss from any port in the system), or Vid Loss (port) (detects video loss only from the single specified port).
76
Page 76
Admin Console CONFIGURATION
Alarms – Definition
Field Data
ID Uniquely identifies the chosen source that will trigger the specified
alarm by its ID number. Camera = port number of camera connected to the controller card. I/O Port = port number of the Input port that the external source is connected. RS232 = port number of the external source that will be connected through the RS232 port. Vid Loss (port) = port number of the input port that will be detecting video loss. Note: When the source type is Vid Loss (any), this selection is unavailable since multiple ports on the system can serve as the source.
Acknowledge:%%%%
Mode Determines whether a user must manually respond to an alarm when
triggered or if an automatic response is generated requiring no user intervention. Choose Manual, Auto, or Both.
Delay Defines the delay in seconds when an alarm is in Auto Acknowledge
mode before the alarm is automatically acknowledged. (min:sec) Up to 59:59
On-Screen Display In the Text box enter the text that you want to appear on the screen
when an alarm is triggered. This text will be displayed on all of the monitors that are part of the actions you select on the Actions tab.
Location Practical name to help an administrator select an alarm by location.
Alphanumeric. Examples: Main concourse, loading dock, boiler room.
Reset – Mode Chooses the method by which the alarm will be reset. Manual, Auto,
and Both are options.
Delay Specify the amount of delay time prior to resetting the alarm using the
mode selected.
77 Admin Console CONFIGURATION
Page 77
ALARM ACTIONS
The
Actions
for each alarm. To add an action to the list, click anywhere on the next available empty
row (or row 0 if this is the first entry), make your action selections, and then click:
The green check mark to confirm the action, or the red “x” to cancel its entry.
tab allows an administrator to specify up to ten alarm actions
To remove an existing action from an alarm, click o n the line that contains the action you wish to remove, click in the delete check box and then the green check mark to confirm the removal of the selected action.
78
Page 78
Admin Console CONFIGURATION
Alarms – Actions
Field Data
Type Choose the type of action to perform when the alarm is triggered.
Click on the first blank box under this column, and select Cam Spot (camera spot), Tour Seq (tour sequence), Grp Seq (group sequence), or Text Only.
ID Identifies the ID number of the camera, tour sequence, or group
sequence depending on what was selected as the action type. Choose the ID number off of the list that appears at the right of the Alarms window when on this tab.
CPre CPreset. Number identifying a preset position of the camera specified.
0 to 64. This setting is only available and necessary when Cam Spot is the selected action type.
Aux Choose if an auxiliary function will take place. An auxiliary function
would require additional hardware at the chosen camera – such as a switch. If unavailable or not desired, choose None. If available and desired, choose Aux1, Aux2, or Both as the function to perform during that action. This setting is only available and necessary when Cam Spot is the selected action type.
Amount of time that a monitor maintains a view. Up to 59:59 (hr:min)
Dwell
Name Practical name given to an action, or in the case of the action type of
Text Only, specifies the text that will be displayed.
79 Admin Console CONFIGURATION
Page 79
ASSIGN AN AVAILABLE TARGET
The
Target
tab from the Alarms window allows an administrator to assign an existing target ID to a specific alarm. The existing target IDs appear under the Available section of this window.
The Monitors section of this window shows the administrator whi ch monitors are part of the highlighted target ID; and the display mode section shows the mode for the target. Monitors can also be viewed by area\local number.
1. Highlight the available target ID you wish to assign to the
selected action for the selected alarm.
2. Click the Assign Target icon to assign the selected target
to the selected action for the selected alarm.
3. Click EXIT when finished assigning targets to actions
associated with alarms.
Note: More than one alarm target can be assigned to each
action. A target can be assigned to more than one
80
Page 80
Admin Console CONFIGURATION
action. More than one alarm ID can contain the same alarm targets in its actions.
REMOVE AN ASSIGNED TARGET
From the Target tab of the Alarms win dow:
1. Highlight the alarm you wish to remove a target from.
2. Highlight the assigned target you wish to remove.
3. Click the Remove Assigned Target button.
4. Click EXIT to exit.
81 Admin Console CONFIGURATION
Page 81
ALARM PERMISSIONS
Modify or copy alarm permissions in the same manner described in the Cameras
Permissions section, beginning on page 52.
82
Page 82
Admin Console CONFIGURATION
The
Controller
permission tab allows an administrator to permit or deny a controller the ability to seize a specific alarm. The Modes section of this tab is described on page 18.
The
Modes
tab on the Alarms window allows an administrator to
determine what modes are active for an alarm. By default, all four modes
83 Admin Console CONFIGURATION
Page 83
are active, even if all four have not yet been defined. This tab will be grayed out and inaccessible unless Scheduled Modes have been selected.
page 18 for full details on modes.
See
84
Page 84
Admin Console CONFIGURATION
Operators
CLASS SETUP
An operator is one who accesses the system via a system controller, selects resources, and controls selected system resources, such as cameras, monitors, sequences, etc.
Before an operator can be defined, an operator class needs to be created. An operator class defines which functions an operator or groups of
operators have privileges to perform.
1. Click on the down arrow in the lower right corner of
the Operators icon on the main menu, and choose
Class Setup.
2. Enter an ID number and descriptive name for the class
record you are creating.
3. Choose the privileges to grant the class by checking
the boxes to the left of the desire privileges.
4. Click the green check mark to add the class of
operators, or click the red X to cancel.
You can add, edit, delete, or replicate class IDs as needed using the four icons at the bottom of this win dow.
85 Admin Console CONFIGURATION
Page 85
The “Other” tab of the Operator Classes window can be used to view a list of the operators th at are assigned to the class selected.
DEFINITION
Once a class has been created, you can then access the Operators menu to specify your system’s operators, their priorities, and their permission to access system controllers.
Enter the Operators menu by either clicking on the Operators icon from the main menu, or clicking on the down arrow in the lower right corner of the Operators icon and choosing Records.
Add, edit, delete, or replicate operators, as needed, using the four icons at the bottom of this win dow.
Note: The maximum number of operators that can be defined
for the system is 512
86
Page 86
Admin Console CONFIGURATION
OPERATORS
Field Data
Operator ID Operator logon identification. This ID is different from all other
component IDs. An administrator assigns it. It is not assigned automatically as is the case with other components. This number does not need to be sequential. This will be used as the log-on ID assigned to each operator. 1 to 65,534.
Password Operator password. After the operator has entered the logon ID to
a system controller, this numeric password must be entered to complete the logon process. 1 to 99,999.
Operator’s name, in any format. Alphanumeric, 20 characters.
Name
Class Choose the class this operator is to be added to from the classes
available on the drop-down menu.
Priority Sets precedence among operators. Alarm priority has precedence
over the operator priority. Operator priority has precedence over the system controller priority. The operator with the lower number priority takes over the part of the system being addressed. If more than one user with the same priority is operating at the same time, access is given according to the lowest controller priority number. If both priorities are the same, access is given and held for the latest call to a function, in other words, on a last-come first-served basis. 0 to 65,534.
Timeout Number of seconds that must elapse after the user stops entering
keystrokes before the system logs the operator off of this controller. Up to 11:59:59 (hr:min:sec).
The operator timeout works in conjunction with the controller timeout. The system will use the lowest timeout value of the two.
Entering a “0” into this field will cause the timer to never expire regardless of the controller timeout value.
Class privileges granted for the selected class also appear on Definition tab of this window, but cannot be changed. This sectio n is for the administrator’s reference. Changes to class privileges must be done throug h the Ope rator Clas ses win dow.
page 72 for details.
See
87 Admin Console CONFIGURATION
Page 87
REPLICATE AN OPERATOR DEFINITION
1. Highlight a configured operator ID and click the Replicate
Record button.
A confirmation m essage will appear asking “Are y ou sure you want to REPLICATE this Operator?” and explaining the replication rules.
[1] Records will be generated according to ID. [2] ID numbers will incremented to the next available value. [3] If a record already exists with a matching v alue for any of these
unique fields, that Target assignment will b e skipped. [4] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel.
The copy source is the highlighted operator ID from which the subsequent operators will be copied.
3. Enter the Target range of operator ID numbers, with the
beginning number in the START box, and the ending number
in the END box.
4. Click the green check mark to add the series of operators, or
click the red X to cancel.
After clicking the green check mark, a message will appear letting you know how many records were actually generated, indicating if any records were skipped.
note section of page 45.
See
For example, “6 records out of 6 were generated successfully”, or “8
Warning: Operator IDs existing within the specified range will
not be overwritten.
88
Page 88
Admin Console CONFIGURATION
records out of 10 were generated successfully.”
Note: The maximum number of operators that can be defined
for the system is 512.
89 Admin Console CONFIGURATION
Page 89
PERMISSIONS
Modify or copy operator permissions in the same manner described in the
Cameras Permissions section, beginning on page 52.
The
Controller
permission tab allows an administrator to permit or deny an operator the ability to login to a specific controller.
As with the Alarms window tabs, the Modes tab of the Operators window will be accessible only if Scheduled Modes have been selected. The Modes tab on the Operators window allows an administrator to determine what modes are active for an operator. By default, all four modes are active, even if all four have not yet been defined. This tab will be grayed out and inaccessible (as seen above) unless Scheduled Modes have been selected.
page 18 for full details on modes.
See
90
Page 90
Admin Console CONFIGURATION
SEQUENCES
A sequence is a pre-determined series o f views on one or several monitors, with pre-configured dwell times between views.
Tour
Sequences
Group Presets
Group
Sequences
Three different kinds of automated sequences are available so that frequently used combinations of monitors and cameras can be displayed automatically; tour sequences, group presets, and group sequences.
91 Admin Console CONFIGURATION
Page 91
Tour Sequences
A tour sequence is an automated sequence of steps that can be run on any monitor by first activating the monitor, and then initiating th e sequence. Each step in a tour consists of a specific camera aimed at a preset position, and a dwell time of a certain length of time.
The values entered in this window determine the sequence in which cameras are viewed by a single monitor when a tour is invoked.
Although an operator will call sequences or presets by local number within a specific area, an administrator can v iew these tours by ID or area\local numbers within th e Admin Console.
DEFINITION
An administrator would enter the tour sequence window by clicking on the Tour Sequences button from the main menu.
92
Page 92
Admin Console CONFIGURATION
TOUR SEQUENCES- Definition
Field Data
ID Unique record ID assigned by the Admin Console as a tour sequence
is added, in order to identify one programmed tour sequence to the system.
The Admin Console automatically generates this number in consecutive order. Upon adding tours, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 256.
Area Unique number identifying a Monitor Surveillance Area (MSA)
comprised of an array of monitors and one or more keyboard controllers.1 to 128.
Click the Area button on the main window to view all components defined in a specific area.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
It is recommended that the use of areas be restricted to values of 1 to
128. Only use area “0” when no areas are needed within the entire system.
Local Unique number within a monitor surveillance area, assigned by the
system administrator. 1 to 9,999.
Name Practical name that is easy for an administrator to remember, in order
to reference a certain tour sequence. Alphanumeric, 16 characters.
Camera ID number for a camera, previously configured, to be displayed in a
step when a tour sequence is invoked. 1 to 8,192.
CPreset Number identifying a preset position of the camera specified.
0 to 64.
Dwell Amount of time that a monitor maintains a view. Up to 86,399
seconds (23 hours, 59 minutes, 59 seconds).
AUX1 & AUX2 Used to determine if an auxiliary function will take place during a
sequence. An auxiliary function would require additional hardware at the chosen camera – such as a switch. If unavailable, leave both fields blank (for none or no function desired). If available and desired, choose On, Off, or On/Off as the function to perform during that step.
1. To add a tour sequence, click the green Add Tour
button
The following panel will appear.
93 Admin Console CONFIGURATION
Page 93
2. Fill in an area and local number.
The Admin Console will automatically assi gn the next available ID. Give the tour a descriptive name.
Warning: Be aware that changing the area may affect other
configured components such as alarm target assignments.
3. Add a camera in the Sequence of Steps.
Double click on a camera ID in the list on the right. It will automatically insert that camera number in step one. Double clicking on another camera ID will automatically insert that camera number in to step 2 , and so on.
4. Type a preset number associated with a specific
camera in the CPreset column.
Enter a “0” to indicate no preset associated with that camera.
Tip: To enter the same value in several steps, highlight desired
cells using the click and drag method. Type in a value and
94
Page 94
Admin Console CONFIGURATION
press the enter key. All highlighted cells will be filled with the typed value.
5. Type a dwell time in seconds for each step.
6. Double click on AUX1 or AUX2 to change its setting
from none (blank), to On, Off, or On/Off as desired, and
if available.
7. To add a step in the middle of a sequence, highlight a
step and click the Insert Step button.
A blank row will appear before the highlighted step.
8. To delete a step, highlight a step and click the Delete
Step button.
The entire row will be deleted.
9. After adding all desired steps, click the green check
mark to continue, or the red X to cancel.
10. Add, edit, delete, or replicate monitor tour sequences
as needed.
95 Admin Console CONFIGURATION
Page 95
REPLICATE TOUR SEQUENCE DEFINITION
Highlight a configured Tour Sequence ID and click the Replicate
Tour button.
A confirmation m essage will appear asking “Are y ou sure you want to REPLICATE this Tour within this Area?” and explaining the replication rules.
[1] Records will be generated according to ID. [2] ID will be incremented to the n ext available value. [3] Local # will be incremented from a specified base value you assign. [4] If a record already exists with a matching v alue for any of these
unique fields, that Target assignment will b e skipped. [5] All other record values will be identical to the Source record.
Click Yes to continue or No to cancel.
The copy source is the highlighted tour sequence ID from where the subsequent tours will b e copied.
Enter the amount of tours to create in the Target Size box.
Enter the starting local ID number to begin incrementing from in
the Base Values box.
Click the green check mark to add the series of tours, or click
the red X to cancel.
After clicking the green check mark, a message will appear letting you know how many records were actually generated, indicating if any records were skipped.
note section of page 45.
See
For example; “6 records our of 6 were generated successfully” o r “8 records out of 10 were generated successfully.”
96
Page 96
Admin Console CONFIGURATION
Warning: Tour Sequences existing within the specified range
will not be overwritten.
To modify the replicated Tour Sequences, use the Edit Tour
button.
The “Other” tab on the Tour Sequences window shows the Alarms th at the selected Tour Sequence ID is associated with.
97 Admin Console CONFIGURATION
Page 97
Group Presets
A Group Preset carries its own ID, and is created from the Admin Console to include a list of camera-monitor connections. An operator selecting a Group Preset is able to display a preset series of camera views over several monitors at one time. Each camera-monitor connection must also include a camera-preset position.
Group Presets must be carefully planned, keeping in mind that they may be used as elements of Group Sequences. With a focus on camera­monitor permissions, configure several Group Presets using the same sets of monitors to enable the Group Sequences to run smoothly.
DEFINITION
Add, edit, delete, and replicate Group Presets, as necessary, using the four buttons at the bottom of this window.
98
Page 98
Admin Console CONFIGURATION
GROUP PRESETS – Definition
Field Data
ID Unique record number identifying a single Group Preset assembling
several camera-monitor pairs that an operator can view at one time. The Admin Console assigns this ID as a Group Preset is added.
The Admin Console automatically generates this number in consecutive order. Upon adding Group Presets, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one component or sequence from another in row and column style. Since logical and local numbers are not necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique numbers, the Admin Console generates these ID numbers. 1 to 256.
Area Unique number identifying a Monitor Surveillance Area (MSA)
comprised of an array of monitors and one or more keyboard controllers. 1 to 128.
Click the Area button on the main window to view all components defined in a specific area.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
It is recommended that the use of areas be restricted to values of 1 to
128. Only use area “0” when no areas are needed within the entire system.
Local Unique number assigned by an SCS administrator, enabling operators
to address this particular monitor within an area. 1 to 9,999.
Name Practical name to help an operator identify a Group Preset.
Examples: FireX by flr. CashReg by flr. Alphanumeric, 16 characters.
Set of Views Specify a set of camera (with preset position) and monitor pairs that
will take place in a single shot.
Camera ID number for a camera, previously configured, to be displayed in a
step when a monitor tour is invoked. 1 to 8,192.
CPreset Number identifying a preset position of the camera specified.
0 to 64.
Monitor ID number for the monitor that will display the specified camera preset
position. 1 to 1,024.
99 Admin Console CONFIGURATION
Page 99
1. To add a group preset, click the green Add Preset
button.
The following panel will appear.
2. Fill in the area and local number.
The Admin Console will automatically assi gn the next available ID. Give the group preset a descriptive name.
3. Add camera to monitor pairs to the Set of View
section by clicking on the ID numbers for each as
needed.
Double click on a camera and a monitor from the lists on the right. It will automatically insert that camera and monitor ID in step one. Double clicking on another camera and monitor will automatically insert that camera and monitor ID into step 2, and so on.
4. Type a preset number associated with a specific
camera in the CPreset column.
Enter a “0” to indicate no preset associated with that camera.
Tip: To enter the same value in several steps, highlight desired
cells using the click and drag method. Type in a value and press the enter key. All highlighted cells will be filled with the typed value.
100
Page 100
Admin Console CONFIGURATION
5. To add a step in the middle of a sequence, highlight a
step and click the Insert View button.
A blank row will appear before the highlighted step.
6. To delete a step, highlight a step and click the Delete
View button.
The entire row will be deleted.
7. After adding all desired steps, click the green check
mark to continue, or the red X to cancel.
8. Add, edit, delete, or replicate group presets as needed.
When changing the area of an existing Group Preset, notice that
all of the pre-configured monitors are deleted. This prevents an administrator from inadvertently having monitors of different areas in a single group preset.
101 Admin Console CONFIGURATION
Loading...